WiFi disconnects, but connects after refresh
-
This is a continuation of a problem first posted in this thread:
https://forum.duet3d.com/topic/34799/wifi-2-1beta6-from-3-5-0-rc-2-3-still-disconnecting/59When DWC gets into this state, does it stay like that until you refresh the browser (which I think you said fixes things)? It would be useful to see the M111 P14 S1 output (on the USB terminal) when DWC is in this state along with an M122 output.
Having said that, it looks like from your previous m122 output that you are running the older wifi firmware. on a 8266 module. That is not a combination that I'm likely to put a lot of development effort into going forwards. If you want to help with testing/debugging then the newer firmware is probably the one to concentrate on, I seem to remember that you had problems with that in the past, but perhaps now is the time to revisit it?
If the disconnects you are seeing are an issue for you then you might also want to consider switching to an esp32 based module, that is what most folks seem to be using and because of that is the device I test on most. Obviously I can't be certain you will not see problems if you did switch, so your call.
-
chrome diagnostic message http://octo.local
-
-
if these aren't useful let me know
-
checked log file from the usb lead nothing in there
d26f4aff-1a5d-467e-b487-64ebe2e566be-m111 log.txt -
to get connection to DWC refreshed web page , this was displayed in the chrome diagnostic window
-
DWC not responding again
![747e2eb9-e6c8-4c5b-b247-ca51fbe0f501-image.png] -
DWC stopped responding again , different error in Chrome Dev tools
Did notice at this point btncmd and plugin manager had both been stopped (not by me)
A form field element should have an id or name attribute
A form field element has neither an id nor a name attribute. This might prevent the browser from correctly autofilling the form.
To fix this issue, add a unique id or name attribute to a form field. This is not strictly needed, but still recommended even if you have an autocomplete attribute on the same element.
1 resource
Violating node -
DWC stopped responding again
-
after refesh of browser the DWC looked like this
and not like This
also btnCmd and release manager had stopped , had to restart manually
-
DWC stopped responding again very similar to the one above , btnCmd and release manager had stopped , had to restart manually.
<
-
undefined gloomyandy referenced this topic
-
Ok can you move all my other posts over to here?, i only have a few days left then im on holiday for 6 weeks so if i dont respond ill be back in April
-
@moth4017 I don't have the power to move posts on here, maybe @droftarts could move them?
-
@gloomyandy there you go
-
@jay_s_uk thamk you
-
@chrishamm Could you take a look at the debug console outputs in this thread? It seems odd that we can have a situation in which a browser refresh fixes a connection problem, any idea what may be happening?
-
@gloomyandy looking at the data on the octopus control board it says only supports 8266, which wifi module would you recommend and ill get a couple on order ?
will this be ok?
https://biqu.equipment/products/esp32u-mode-esp32e-mode -
@gloomyandy The WiFi server kills incoming connections, so DWC loses the connection to RRF (connection reset). This issue is still being investigated AFAIK. DWC is already designed to retry the same HTTP request a few times in standalone mode but if that keeps failing, the connection is eventually invalidated.
-
@chrishamm Yes but why does doing a browser "refresh" fix the problem? As far as the WiFi server is concerned it is just seeing http requests so I don't see why the refresh would fix a problem at the server side? It seems odd to me? Maybe it is just a change in the timing of requests? If we can understand why that refresh fixes things it might help us resolve the problem (if there is one) in the WiFi server.
