Duet control no longer shows in the browser
-
It should be under the Network section of theM122 output, something like (if your terminal line ending is not set to LF it could be truncated)
WiFi firmware version 1.21 WiFi MAC address 60:01:94:nn:nn:nn -
@drthomasw3 said in Duet control no longer shows in the browser:
I just ran M540 the MAC addresses do not match Duet looks odd a5:a5:a5:a5:a5:a5
known "bug", for wifi its part of M122.
-
The display is small there is a bunch of info about ram it is cut off at "Never u"
-
@drthomasw3 said in Duet control no longer shows in the browser:
The display is small there is a bunch of info about ram it is cut off at "Never u"
you're running the command on the PanelDue perhaps? not sure if its possible to make the whole M122 output readable there. Maybe someone else have a suggestion for that. I thought you used the USB/serial console, in which case all you need to do is set the line ending to LF (line feed or unix, no CR or carriage return)
-
So all of this is to confirm that the IP address the web browser is reaching is really the printer, correct?
Much simpler way: Power off the printer. The browser should then say that address is unreachable (as opposed to the blank screen).
-
I am printing so I can not turn off But yes when off and I type in the IP the message address can not be reached comes up.
-
Would still be interested in the wifi firmware version from m122 though
-
@drthomasw3 said in Duet control no longer shows in the browser:
I am printing so I can not turn off But yes when off and I type in the IP the message address can not be reached comes up.
OK, then the blank screen IS coming from the printer.
Duet firmware basically acts as a web server for whatever is in the /www folder. So something is wrong with that. As mentioned above, rebuild everything in /www from the latest release of DWC on github. Try a different card, etc, etc.
-
What version of DWC do you have? I had the exact same issue with 2.05 and 2.06. Upgraded to 2.07 and it appears to have fixed it.
-
Reloading the www files to new version 2.07 worked. I guess corruption is everywhere.
Thank you all!
