@CCS86 the Maestro IAP (In App Programmer) file, named “Duet2_SDiap32_Maestro.bin”, is the third required file. The IAP files weren’t in the 3.5.1 release initially, but they are now. Not sure if they made it into the release zip though.

Ian

@achrn apologies for not reporting back here - I fixed the issue a week or so ago.

@Alex-cr I just published a new Motion webcam server plugin. That version is compatible with Debian Buster and Bookworm. See https://github.com/Duet3D/MotionWebcamServerPlugin/releases/tag/v3.5.1

@Bewaren This should help:
https://docs.duet3d.com/en/User_manual/Connecting_hardware/Z_probe_auto_levelling

It shows how to use M574 to specify two endstops for 1 axis.

@curieos
Gotta run it?

@Orbital said in duet reads "Your Duet rejected the HTTP request":

I have the Duet web control file that you provided, both of which are extracted. That is all I have on my SD card.

@Phaedrux said in duet reads "Your Duet rejected the HTTP request":

https://github.com/Duet3D/RepRapFirmware/releases/download/3.2.2/DuetWebControl-SD.zip

Download that zip file and extract it's contents to the WWW folder on your SD card. Then you should be able to follow along with the rest of the getting connected guide.

If you don't have a WWW folder on the root of the SD card, create it and extract that zip file into it.

@Bewaren said in Duet2 Firmware Upgrade Issue:

I'm now getting a issue with Driver 2

'Warning: Driver 2 warning: phase A may be disconnected, phase B may be disconnected'

M584 X0 Y1 Z2 E3 ; set drive mapping

@Bailey-James said in Duet2 Firmware Upgrade Issue:

@Phaedrux I don't have anything connected to the Z axis drivers currently

Yes, but your error is coming from the driver defined for Z which you don't have anything connected to, which is what the error is telling you.

@chrishamm Thanks! Updated. I'll let it run for a while and see how it goes. I do run a VPN on the computer that is accessing the Duet board. I'll try switching that off and see if it behaves differently.

@chrishamm thanks for info ... i have installed and now is all fine again

@chrishamm Thanks - I've just spotted that back in the announcement thread. No problem.

So, I really don't like the idea of using the rc versions with past experiences. So instead of installed a fresh version of Raspbian Bookworm and then followed https://docs.duet3d.com/User_manual/Machine_configuration/DSF_Other.

The only difference here is the spi configuration appears to have changed. The /etc/modprobe.d/spidev.conf doesn't seem to be applied. So I deleted that file and added spidev.bufsize=8192 to the /boot/firmware/cmdline.txt file instead and it all works.

Still have to setup the auto launch chromium full screen, but thats not a big deal.

It does appear that 3.4.6 works just fine with Rasbian Bookworm.

@dirtybirdnj As it's a drawing machine, see my config here for the Polargraph I built. It uses a servo to raise and lower the pen. Ignore the parts about the motors and kinematics, as mine is not a cartesian machine.

Ian

Thank you, this works:

button R37 C1 F0 H0 V5 T"- Unload" A"M98 P""/macros/3_Unload filament"""

Go through these steps.

https://docs.duet3d.com/en/User_manual/Troubleshooting/Duet_wont_respond

You can d a full firmware wipe and get the board to appear as a port in BOSSA in order to reflash the firmware (from a fresh download) and try YAT again.

https://docs.duet3d.com/en/How_to_guides/Getting_connected/Getting_connected_to_your_Duet

@jay_s_uk Thanks, that's just what was needed. I had got caught up in the weeds of the wiki and never read the release notes for that release. I already had apparmor installed and configured, must have missed the 'apt install duetpimanagementplugin' bit.
This all looks to be working perfectly now, many thanks.

The heater warnings can't be "fixed" as it's more informational than an error.

@dc42 okay