Duet2 WiFi Firmware on Raise 3d E2 ?
-
@Proschi78 said in Duet2 WiFi Firmware on Raise 3d E2 ?:
the display controller is also operated via this interface
they can easily just route the spi lines to the display.
that is why the full M122 output is relevant.
you probably did not update the wifi firmware when you updated to the rrf3 firmware. -
@Veti said in Duet2 WiFi Firmware on Raise 3d E2 ?:
they can easily just route the spi lines to the display.
that is why the full M122 output is relevant.
you probably did not update the wifi firmware when you updated to the rrf3 firmware.I cannot update the WiFi firmware.
because the wifi module is on a different board.
and I have no access to it via the pc -
the wifi firmware is not updated via the pc.
see
https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware#Section_Updating_WiFi_firmwarebut the M122 output is important
-
@Veti said in Duet2 WiFi Firmware on Raise 3d E2 ?:
@jay_s_uk said in Duet2 WiFi Firmware on Raise 3d E2 ?:
iap4e.bin
did you rename it to Duet2combinesIAP.bin like the error message says?
Duet2CombinedIAP is not the same as iap4e.bin! Renaming it will not work. You can get Duet2CombinedIAP.bin from one of the RRF 3.x releases.
-
@dc42 can I go back from V3.0 to V2.02 that easily?
-
@Proschi78 that'll be why the downgrade didn't work then.
use the IAP file dc42 linked to and the firmware from my google drive -
@jay_s_uk ok i will try today at noon
-
Hello everyone here who helped me. I was able to successfully install a version that was before 2.02. Then the printer could be updated via the Raise software. The whole thing was worth it for me, because now I have the possibility to control it via octoprint for whatever reason. thank you again
-
Do you think an original duet2 Wifi would work with the hardware components?
-
@Proschi78
not with the display, but you only did a third of the firmware update of rrf3. it might be that you could update the board to 3.1.1
-
Yes that may be, but then I have no chance to use the display and control board. I am currently having the problem that the Gcode is being sent from the control board to the motionboard. This causes errors and the printer pauses printing, a stutter.
-
or if you want to invest some time and since you already have an octoprint server, run klipper with mainsail os.
-
-
@Proschi78
I am currently having the problem that the Gcode is being sent from the control board to the motionboard. This causes errors and the printer pauses printing, a stutter.
do you mean octoprint by control board to motionboard?
-
No, I connected Octoprint directly to the Motionboard. As a result, I have no way of controlling it directly at the printer.
-
@Proschi78
since you are running stock configuration now, i suggest you take that up with raise 3d.
-
Do you think the error has been fixed with an original duet wifi + deux5 + display? The rest of the hardware would have to take part, since it is now based on a duet motionboard
-
I ordered a duetwifi. I'm curious how it goes
-
The duet wifi came today. I have a question about this, can I connect a second x axis instead of the second z axis?
-
Sure, board doesn't know what you're connecting, and firmware only cares about the config.
The two headers for the driver labeled Z are in series, and doesn't require any special configuration other than assigning driver 2 to x instead of z. To actually use two drivers you can follow the independent z axis instructions, just assign the drivers to x instead of z.
Alternatively you can also wire two motors in series or parallel to any of the other outputs with custom wiring as needed.