Issues Saving Files Through Web Interface

CthulhuLabs

Not really sure if this is a firmware issue or an issue with the DuetPi image. I have a Duet3 6HC running RRF 3.3rc3 with a Pi 3 as the SBC. I am running the full DuetPi image. The Pi is connected to the network via Wi-Fi. The Pi's Wi-Fi signal level is -51 dBm (so decently strong). When I edit a file from my workstation using the web interface it properly saves only about 1/3 of the time. The rest of the time I get a "Failed to upload macro1.g - Network Error" error and all of my changes are lost. When I edit files on the Pi 3 using the web interface they save properly 100% of the time. When I look in the JavaScript Error console I see this:

18:59:58.068 app.a5192fc6.js:42 Error: Network error
    at new ExtendableBuiltin (app.a5192fc6.js:42)
    at NetworkError._createSuperInternal (app.a5192fc6.js:1)
    at new NetworkError (app.a5192fc6.js:42)
    at XMLHttpRequest.K.onerror (app.a5192fc6.js:42)
_loop$ @ app.a5192fc6.js:42
18:59:58.116 machine/file/0%3A%2Fmacros%2FBitZeroV2%20XYZ.g:1 Failed to load resource: net::ERR_NAME_NOT_RESOLVED

I am also seeing errors like this:

18:37:09.432 app.a5192fc6.js:42 WebSocket connection to 'ws://duet3.local/machine' failed: 
(anonymous) @ app.a5192fc6.js:42

Which makes me think there is an issue with mDNS or something. I just switched from using the duet3.local DNS record over to the straight IP to see if that helps and will report back.

On a side note it would be nice if the built in editor had a save option that did not close out the editor. That way if the save fails you could just try to save again rather that losing everything you have worked on.

Phaedrux

Is this something that only started with 3.3 RC3?

CthulhuLabs

@phaedrux No it was happening with 3.3rc2 as well which is the version I started out with.

CthulhuLabs

@cthulhulabs said in Issues Saving Files Through Web Interface:

Which makes me think there is an issue with mDNS or something. I just switched from using the duet3.local DNS record over to the straight IP to see if that helps and will report back.

After switching to the IP from the duet3.local address I have had no issues saving files.

Phaedrux

Thanks for the update. One for @chrishamm I think.

chrishamm

@CthulhuLabs What OS are you using? Is there any way you could test it from a different device? DuetPi relies on the Avahi daemon for mDNS which is well-tested.

CthulhuLabs

@chrishamm My SBC is running the full DuetPi image. My workstation is running Windows 10. I can test from my laptop I suppose.