@maxboysdad Sorry for missing this question. The wifi behavior of being both an access point and being a client connected to another network is working as intended. Always having the AP available allows for access to the device in the event that the credentials for a host network are entered incorrectly or if the host network does not exist.
1 Like
I notice a USB-A receptacle is available. Would an EDUP dongle work with that?
The firmware does not support an external wifi device. The original idea was to enable USB mass storage device from the USB-A, but in future hardware versions that connector will be removed.
For a short time, I had connected my laptop to the access point, and the wifi network to the client and they both ran for a time, then both stopped working at the same time. I managed to re-connect the wifi just by re-sending the url, however, I have not yet been able to re-connect the access pointâs gui. The access point itself did connect to the laptop but will not give access on 192.168.4.1 again. Incidentally, the mounting for my DCs is 9 feet 3 inches to the wifi routerâs nearest antenna.
Do you not believe that the disconnecting is related to the âtuner time outâ situation as related above, then? It isnât possible that a line of code that was causing this may have moved but is still in the binary that controls the wifi section?
1 Like
I followed the excellent update instructions above and was able to update to 1.03 firmware. I also installed a 32 GB card (quick formatted to FAT32 on windows) and now appear to be downloading files.
Previously I had no SDcard installed (I thought I would test internal storage but now know thatâs not working yet) so I did not seem to download files despite good signal, and every day I would adjust the frequency by +/- 10 KHz to restore reception (I thought I was fine tuning for outside temperatureâŠbut it now appears the receiver was quitting - tuner time out). I was able to us the US default frequency button and am now able to see an APRS message stored on the files already.
A small note in case it helps anyoneâŠI have observed that the web interface gets grumpy/slow when I have 2 computers trying to observe the webpage (I am using Wifi-client mode). I now use one computer at a time and if it was messed up (no page or all dashes on values) I hold shift and hit refresh (using Chrome on Winblows).
Thanks for the updateâŠI was banging my head as to why it would quit overnight each night.
1 Like
1.0.5 is available in the flashing directory on Github. It includes logging of wifi events (to troubleshoot the problem that @maxboysdad and @kenbarbi are seeing). This version also adds a restart button in the UI and a download-logs button.
1.05 uploaded and runningâŠlove the power switch icon next to the âConnectedâ label.
Yep - - and also the ability of downloading the Log with its newly added reports on WiFi Client activity. I donât know, Bill, if youâve had connectivity problems like Jerry and I have, but at least now what ever is happening will be logged. Ken
Wonderful. I told the DC to clear the logs last night at 6:00 PM. The unit stopped responding to wifi after downloading 4776 packets, this is where I found it at 10:00 this morning. When I downloaded the log file and opened it in âNotepadâ, I have 3.5 Megabytes of apparently logs of the flash. I rebooted the unit and it appears to be working normally, except it is still logging as 01-26-2023. This thing is really a bummer.
Apparently the âClear Logsâ does not do anything, and this unit seems to be very confused about all this. I know I am.
1:15 PM MDT 01-06-23 Re-flashed unit, formatted SD card, re-started. at 5:15 PM MDT, checking the log, it took a long time for the Client to get registered with the wifi, but is now running normally and continuously for four hours. Longest time it has run and stayed connected so far. Wahoo!
5:32 PM MDT 01-06-23 It disconnected when I made the last entry above and had to be restarted with the browser.
9:25 AM MDT 02-06-23 Found unit disconnected from wifi gui. It appears that the 2301 is downloading continuously as it should, but the wifi gui shuts down and canât get restarted without manual help. This is similar behavior to the DC 3.05 and Skylark 5.8. Files continue accumulating, but the gui stops functioning. On the 3.05, the gui logged the user out, but continued to show the data, whereby on the 2301, the entire gui logs off. Re-started gui manually again.
@Syed
This a wifi event recorded in the current log. It did not receive the IP address after disconnecting, but continued to download on the radio side. Note that at 12:03:00 it says it obtained an IP address; but usually when it does this and is acting normally, it also shows that address, and the gui is re-connected. In this case, the wifi did not actually re-connect. This has been observed a number of times in the logs. Note the next one following (copied out, below) did the same thing, stating that it had sent telemetry, however, it does not show on the Othernet Status that any change was received there.
[02.06.2023 - 12:02:55] Uptime: 3597s
[02.06.2023 - 12:02:55] file progress: 17380 of 94884 bytes
[02.06.2023 - 12:02:57] file progress: 17600 of 94884 bytes
[02.06.2023 - 12:02:57] Restarting ESP to avoid Bugs, Uptime: 3600s
[02.06.2023 - 12:02:57] WIFI-Event: Disconnected from WiFi access point
[02.06.2023 - 12:02:57] WIFI-Event: WiFi clients stopped
[02.06.2023 - 12:02:57] WIFI-Event: WiFi access point stopped
[02.06.2023 - 12:02:53] WIFI AP initialization, Uptime: 1s
[02.06.2023 - 12:02:53] WIFI Client enabled, ConnectingâŠ
[02.06.2023 - 12:03:00] WIFI-Event: Completed scan for access points
[02.06.2023 - 12:03:00] WIFI-Event: Connected to access point
[02.06.2023 - 12:03:00] WIFI-Event: Obtained IP address
[02.06.2023 - 12:03:00] initialization of Radio - LR11xx, Uptime: 8s
[02.06.2023 - 12:03:11] Uptime: 19s
[02.06.2023 - 12:03:16] Uptime: 24s
[02.06.2023 - 12:03:21] Uptime: 29s
[02.06.2023 - 12:03:26] Uptime: 34s
[02.06.2023 - 12:03:31] Uptime: 39s
[02.06.2023 - 12:32:50] file progress: 19360 of 94884 bytes
[02.06.2023 - 12:32:51] file progress: 19580 of 94884 bytes
[02.06.2023 - 12:32:52] Sending Telemetry to Othernet backend, Uptime: 1800s
[02.06.2023 - 12:32:53] file progress: 19800 of 94884 bytes
[02.06.2023 - 12:32:53] Uptime: 1801s
[02.06.2023 - 12:32:53] file progress: 20020 of 94884 bytes
[02.06.2023 - 12:33:36] WIFI AP initialization, Uptime: 1s
[02.06.2023 - 12:33:36] WIFI Client enabled, ConnectingâŠ
[02.06.2023 - 12:33:43] WIFI-Event: Completed scan for access points
[02.06.2023 - 12:33:44] WIFI-Event: Connected to access point
[02.06.2023 - 12:33:44] WIFI-Event: Obtained IP address
[02.06.2023 - 12:33:44] initialization of Radio - LR11xx, Uptime: 8s
[02.06.2023 - 12:33:54] Uptime: 19s
[02.06.2023 - 13:03:35] file progress: 90640 of 485808 bytes
[02.06.2023 - 13:03:35] Sending Telemetry to Othernet backend, Uptime: 1800s
[02.06.2023 - 13:03:35] file progress: 90860 of 485808 bytes
[02.06.2023 - 13:03:36] file progress: 91080 of 485808 bytes
[02.06.2023 - 13:03:36] Uptime: 1801s
[02.06.2023 - 13:25:01] file progress: 402160 of 485808 bytes
[02.06.2023 - 13:25:02] file progress: 402380 of 485808 bytes
âg
0 {CM ( S Zïčăł) Ć92 | v? Ѷ#H s )cf)W G m $ P k %TË„gw lÚ§ B KqZ k ( " { u = # J JÈ kc 7 k a ) YqQ V
g gf{Ćâ 6 % Ja x ]|È O YkZ q | \D>e[02.06.2023 - 13:25:03] file progress: 402600 of 485808 bytes
[02.06.2023 - 13:25:04] file progress: 402820 of 485808 bytes
[02.06.2023 - 13:25:05] file progress: 403040 of 485808 bytes
NOTE THAT HERE THE UNIT DID CONNECT AND RECEIVE THE IP:
02.06.2023 - 13:33:35] Sending Telemetry to Othernet backend, Uptime: 3600s
[02.06.2023 - 13:33:35] Restarting ESP to avoid Bugs, Uptime: 3600s
[02.06.2023 - 13:33:35] WIFI-Event: Disconnected from WiFi access point
[02.06.2023 - 13:33:35] WIFI-Event: WiFi clients stopped
[02.06.2023 - 13:33:35] WIFI-Event: WiFi access point stopped
[02.06.2023 - 13:34:57] WIFI AP initialization, Uptime: 1s
[02.06.2023 - 13:34:57] WIFI Client enabled, ConnectingâŠ
[02.06.2023 - 13:35:04] WIFI-Event: Completed scan for access points
[02.06.2023 - 13:35:05] WIFI-Event: Connected to access point
[02.06.2023 - 13:35:05] WIFI-Event: Obtained IP address
[02.06.2023 - 13:35:05] Connected to WIFI, RSSI: -35, Got IP: 192.168.11.147
[02.06.2023 - 13:35:05] initialization of Radio - LR11xx, Uptime: 8s
[02.06.2023 - 13:35:15] Uptime: 19s
[02.06.2023 - 13:35:20] Uptime: 24s
[02.06.2023 - 14:03:28] file progress: 114180 of 493229 bytes
[02.06.2023 - 14:03:29] Sending Telemetry to Othernet backend, Uptime: 1800s
[02.06.2023 - 14:03:29] file progress: 114400 of 493229 bytes
[02.06.2023 - 14:03:30] file progress: 114620 of 493229 bytes
[02.06.2023 - 14:03:30] Uptime: 1801s
NOTE THAT THIS TIME IT DID NOT DRAW AN IP AFTER IT STOPPED THE WIFI, AGAIN
02.06.2023 - 14:33:27] file progress: 67760 of 493229 bytes
[02.06.2023 - 14:33:27] Uptime: 3598s
[02.06.2023 - 14:33:28] file progress: 67980 of 493229 bytes
[02.06.2023 - 14:33:29] Sending Telemetry to Othernet backend, Uptime: 3600s
[02.06.2023 - 14:33:29] Restarting ESP to avoid Bugs, Uptime: 3600s
[02.06.2023 - 14:33:29] WIFI-Event: Disconnected from WiFi access point
[02.06.2023 - 14:33:29] WIFI-Event: WiFi clients stopped
[02.06.2023 - 14:33:29] WIFI-Event: WiFi access point stopped
[02.06.2023 - 14:30:33] WIFI AP initialization, Uptime: 1s
[02.06.2023 - 14:30:33] WIFI Client enabled, ConnectingâŠ
[02.06.2023 - 14:30:40] WIFI-Event: Completed scan for access points
[02.06.2023 - 14:30:40] WIFI-Event: Connected to access point
[02.06.2023 - 14:30:40] WIFI-Event: Obtained IP address
[02.06.2023 - 14:30:40] initialization of Radio - LR11xx, Uptime: 8s
[02.06.2023 - 14:30:51] Uptime: 19s
[02.06.2023 - 15:03:29] file progress: 75240 of 110129 bytes
[02.06.2023 - 15:03:29] Sending Telemetry to Othernet backend, Uptime: 1800s
[02.06.2023 - 15:03:29] file progress: 75460 of 110129 bytes
[02.06.2023 - 15:32:25] file progress: 384340 of 493229 bytes
[02.06.2023 - 15:32:26] file progress: 384560 of 493229 bytes
[02.06.2023 - 15:32:26] file progress: 384780 of 493229 bytes
[02.06.2023 - 15:32:27] Uptime: 3537s
END OF LOGFILE (2).
ANY IDEAS?
Router is tp-link AX6600 Archer GX90 served internet by Google Fiber (DHCP) : 3 wired LAN ports; one serves a 15-position switch that has six positions occupied, including four ubiquiti mesh nodes (80 feet away) and my Samsung TV (20 feet away) plus one computer on my repair bench (off and on) (eight feet away), one serves a smart switch on my radio/mesh tower (60 feet away), one serves my Dell XPS-8950 (Win 11 pro) computer (four feet away) reserved address.
Wireless 2.4 Ghz Channel 11 serves Two IP phones, Two cell phones, One HP5C4CE9 printer, my wifeâs laptop reserved address, One Raspberry Pi Access Point, One Dreamcatcher 2301 (esp32s3 DCE5BO) reserved address. This Dreamcatcher 2301 is mounted on the wall within six inches of where the v3.05 was, and connected with the same RG6Quad to the LNB, powered with the same 5.0 volt power supply.
Would it help if I assigned a static ip address under âRoutingâ, as opposed to using a âreservedâ DHCP address?
Interesting that this stall always occurs around the time the packet count gets just above 4700, isnât it?
This was the next one:
1 Like
Clearing Logs
Donât forget - - everybody - - to clear the large Dreamcatcher Logs, go to this page and Clear Logs Ken -
Is it 4700 packets, or is that just roughly the number of packets transmitted in one hour?
Did it stay connected longer on the 1.0 firmware it came with, when dream catcher was only rebooting every 6 hours?
Alternatively, in case itâs not the reboot causing the issue, whatâs your DHCP lease time set to?
@Jonvw
The Dreamcatcher 2301 itself is consistently running and downloading in a continuous manner. However, the wifi disconnects in a short time after it is connected. It seems to be around 4700 packets downloaded. That is the number downloaded total at the time the wifi disconnects, according to the figures shown on the GUI when the âconnection errorâ takes place. It has changed in the amount of time connected. After 1.03 it did stay connected for a while longer, but still the same behavior in 1.03 and 1.05. It comes to about 80 minutes or less, depending on the Bitrate figure, and is usually right around 3 MB added to the SD Card. Right now it is stopped at 4714, and as the two examples I posted shows, this is fairly consistent. My lease time is currently set at 120 minutes. This is why I asked the question about if a static address would help, but I have seen no reply. I am not an IT mechanic, so am floundering a bit among some of this. Your input is definitely welcome!
I am open to making changes to my system if you have useful suggestions.
Jerry
1326 hrs. MDT 03-06-2023 I have reset lease time to 1440 minutes (24 hrs), to see if this helps.
1410 hrs. MDT 03-06-2023 Wifi stopped at 4680 packets downloaded. 44 minutes.
Jerry
@maxboysdad Iâve tried to research the issue as best as I can, but since it seems to be related to your local network, Iâm not having much luck. I have no idea what could be causing the same issue on both your 3.05 and your new Dreamcatcher.
Probably the best I can do at this point is to provide a refund, if you like.
To get mine to behave good and because of my wifi password length I had to setup a small wifi router just for it and port forward port 80 and set a DHCP reserve for itâs Mac address right next to the device I ended up using a glinet gl-mt300n-v2 to get it all working good
TP-Link typically provides firmware updates for routers, at least for the first few years after release. It looks like firmware updates have been released for both Version 1 and Version 1.60 of your router. You did not (as near as I can tell) indicate what firmware you are using, but you might want to consider updating the router firmware if you have not done so. Recent firmware updates have provided bug fixes, and some might be relevant to your Othernet equipment.
Make sure to use the firmware update for your particular router model and version, if you decide to do the update. I have done firmware updates on a couple of different TP-Link routers, and it is comparatively painless. Do get assistance if you think it is beyond your technical skills.
I sincerely am not interested in a refund. I also do not believe this problem has anything to do with my network. I now believe it truly has to do with the firware and its negotiation abilities with wifi. There are nine other clients that are having zero problems with the network, and at this point it appears that there is something missing from the negotiations the dreamcatcher performs during the reboot process.
Thank you for your input. I am familiar with the Glinet equipment, and have several of their routers in service currently. However, my own personal desire is to get the dreamcatcher improved to the point that extra equipment is not required to get it to function normally and remain connected to a ânormalâ home-type network, if that is possible. That will then make it perform up to the standard and goal of Syedâs plan for Othernet.
Jerry