No console output (sometimes)
-
@Phaedrux
Yes, DWC is 3.1.1My PanelDue is not installed yet. (how would it help?)
-
I was curious if the output was showing up reliably on the paneldue console.
-
Can I test using USB perhaps?
-
Yes the USB console should show some results.
-
Removing metal cover acting as a bit of a faraday cage, I got the signal strength up to ~-57dbm, but the intermittent response pattern continued.
Connected through the USB terminal, every command got 100% response rate.
-
Try re-uploading the 3.1.1 zip file (as is) to the /sys folder.
https://github.com/Duet3D/RepRapFirmware/releases/download/3.1.1/Duet2and3Firmware-3.1.1.zip
What browser? Might not hurt to clear the cache as well.
-
I confirmed this happens with both chrome and firefox, after cleaning the cache.
I dove a bit too deep into this and confirmed that the Duet is actually sending the relevant packet using Wireshark (spare a thought for a mechanical engineer learning to use wireshark..)Going to try the firmware update next, perhaps something is funky with my DWC?
-
@Leav Your Wireshark filter may be misleading. I suspect you have two DWC sessions running on the same computer. RRF (in stand-alone mode) keeps code replies only once per device (IP address) and if you have two sessions open, one session will get the code reply whereas the other one will get an empty one (which causes the code to be logged in green).
-
@chrishamm Oh man this could definitely be it, I'm not the best at keeping my tabs tidy... and it makes so much sense!
Currently stuck during the firmware update. I don't remember it taking this long... more than 5 minutes already.... I hope I didn't bork something...
-
@Leav If the update failed, you should be able to get it running again using bossa. See https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware#Section_Fallback_procedure_Num_3
-
Used fallback procedure 1 and all is good.
And yes, it looks like the issue was that I had multiple tabs open....
Thanks @Phaedrux and @chrishamm
