PrusaSlicer cannot upload to DWC 2.04/RRF 3

dc42

@chas2706 said in PrusaSlicer cannot upload to DWC 2.04/RRF 3:

@dc42

Yes at one point I suspected that but I cancelled it out after updating my DuetWifi and getting the same issue.

TBH I'm not particularly bothered because I personally think it is more reliable to upload the file from the DWC rather than uploading to the DWC.

To confirm: you have the same issue uploading to Duet WiFi? Which firmware version(s)?

chas2706

@dc42

It worked on RRF2.04 but not since I upgraded to RRF3.

I have tried deleting the connection details in prusaslicer and re-entering them but the slicer just reports an internal error.

Garfield

Had a look at the network request from Prusa and it is GET /rr_connect?password=reprap&time=

I'm not sure how this works - no username ??

the js code shows async connect(hostname, username, password) - one of the three is missing.

This is the text from syslog on the rPi for IP request

Jan 11 18:14:11 duet3 DuetWebServer[403]:       Request starting HTTP/1.1 GET http://10.100.2.243/rr_connect?password=reprap&time=2020-01-11T18:14:11
Jan 11 18:14:11 duet3 DuetWebServer[403]: #033[40m#033[32minfo#033[39m#033[22m#033[49m: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Jan 11 18:14:11 duet3 DuetWebServer[403]:       Request finished in 11.0556ms 404

This is the response using hostname - no difference - the pi is reporting the target rr_connect as inaccessible or unavailable

Jan 11 19:51:41 duet3 DuetWebServer[403]:       Request starting HTTP/1.1 GET http://duet3.local/rr_connect?password=reprap&time=2020-01-11T19:51:41
Jan 11 19:51:41 duet3 DuetWebServer[403]: #033[40m#033[32minfo#033[39m#033[22m#033[49m: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Jan 11 19:51:41 duet3 DuetWebServer[403]:       Request finished in 6.801900000000001ms 404

chas2706

@dc42

David, please ignore the part reporting Duet Wifi and RRF3. I have found the issue.

In config.g I have set up a static ip but it is not actually the one in use!
Using the correct ip address I can confirm that you can upload from prusaslicer to Duet wifi running RRF3.0.

I think there is a problem though if you using Duet3 and raspberry pi.

dc42

@Garfield, thanks for that. I have logged this issue at https://github.com/chrishamm/DuetSoftwareFramework/issues/99.

dc42 created this issue in chrishamm/DuetSoftwareFramework

closed Can't upload files from PrusaSlicer #99

chrishamm

DSF uses a different HTTP API than RRF and it looks like PrusaSlicer does not support the new API yet. It may be worth getting back to this once authentification has been fully implemented in DSF. I see no reason to send a PR to PrusaSlicer before that part is complete.

Armontrout

Any updates to this?> I have a brand new Duet3 setup and it is getting a 404 error when I try to upload from Slic3r. Is there a setup guide, do I need an API key? If so where do i find it?

Garfield

None that I know of. There's nothing you can do to resolve this short of getting into the code and building your own, unless you know both code bases intimately I wouldn't recommend it.

William

On my Mac, the only way I can get slic3r to upload g-code is to have DWC opened in the background.

mendenmh

@William That is true with slic3r, at least on the Mac, but PrusaSlicer has fixed that issue. I can upload from PrusaSlicer without keeping an open connection in a browser.

Thalios

I have Prusaslicer, on Mac, uploading direct to Duet 3 with latest firmware. Works as intended.

blt3dp

@Thalios

Are you using stand alone or SBC? I believe the issue doesn't occur with stand alone.

zapta

@chrishamm said in PrusaSlicer cannot upload to DWC 2.04/RRF 3:

I see no reason to send a PR to PrusaSlicer before that part is complete.

@chrishamm, while you interacting with Prusa, can you also ask to increase the PrusaSlicer's timeout for Duet's uploads? Last time I checked it was 10 secs which cause the upload to fail on large prints. A minute or two should be fine.

(my upload speed from DWC is ~200KB/s. Using RRF 2)