PrusaSlicer cannot upload to DWC 2.04/RRF 3



  • Hi @chrishamm

    On the Printer Settings tab of PrusaSlicer, I have the IP address for my Duet machine. I receive a 404 error when I attempt to upload a gcode through the app or when I go into the settings and test the connection.

    Interesting, it was still working while the machine was a Duet 2. Which also had DWC 2.04. But, the stuff from DWC 1.22.6 was still left over on the SD card.

    I recently upgraded to a Duet 3 with DWC 2.04 and RRF 3, the IP of the printer has remained the same so no config change in PrusaSlicer. I'm guessing since with the new setup there was never any DWC 1.22.6 that compatibility is broken somewhere.



  • No one else has experienced this?



  • I can't make a statement about Duet 3.
    But I can say that the upload was (is) working fine with RRF2.05/DWC 2.04 (now RRF3.0/DWC 2.04) on a Duet Maestro.
    I can weakly remember that I had issues with an older version of Prusaslicer.
    I'm currently on 2.2.0-alpha2 and that works as expected.



  • same here duetwifi 2 with rrf3 and prusaslicer 2.1.1 working



  • My question would be, did you guys upgrade from DWC 1.xx.x and still have the files on the SD card? I suspect if you set up a brand new SD card with 2.04 that it wouldn’t work.

    Same issue on both the last stable and alpha PrusaSlicer



  • I have same issue on a Duet 3 - error 404. I have PrusaSlicer V2.1.1

    I'm accessing indirectly through a Raspberry Pi B - don't know if that matters or not.



  • i have installed rrf3 over rrf2.05 with the update function



  • Mine was a clean out of the box install ....



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

    i have installed rrf3 over rrf2.05 with the update function

    I think we’re dealing more with Duet Web Control, I’m guessing you upgraded from the 1.xx.x version and still have on your SD card. Take a look under the www folder on it and you probably have reprap.html



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

    Mine was a clean out of the box install ....

    Mine too, no traces of old DWC



  • I think we’re dealing more with Duet Web Control, I’m guessing you upgraded from the 1.xx.x version and still have on your SD card. Take a look under the www folder on it and you probably have reprap.html

    yes i have dcw1 still on the sd card



  • Hi I have a brand new install. Duet3 running RRF3 and can't get prusaslicer to upload.

    I also have a Duet Wifi freshly upgraded from RRF2.04 to RRF3.
    Prusaslicer used to work on RRF2.04 but not on RRF3.

    It could well be a DWC2.04 issue.
    In prusaslicer it just says "prusaslicer has encountered an error" when trying to upload or even connect.
    I have recently upgraded prusaslicer from version 2.11 to 2.12 but the problem existed on both versions.


  • administrators

    The version of DWC is irrelevant because uploading files from a slicer doesn't involve DWC. What I suspect is that those of you experiencing this issue are using Duet 3 with an attached RPi, and the web server on the Pi isn't quite mimicking the one in RRF.



  • @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.


  • administrators

    @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)?



  • @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.



  • 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
    


  • @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.


  • administrators

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


  • administrators

    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.


Log in to reply