@dc42 the latest release: 3.4.6
I tried erasing with the jumper and fresh re-installing the firmware via SAMBa last night, to still receive the same errors.

@Phaedrux Hello, it is more like this issue:
All drivers, including the Z-drivers on the Duex have been outputting this errors. It was fine before on my other duet2. M906 and M913 show that the proper current is allegedly outputting.

When I try to home XY the AB motors error

And when I try to home the Z axis the Z-axis motors error.

@Phaedrux I have double checked the crimps and connection. After remapping to driver 4. The warning, as before showed up. This time I also saw both the A and B motor drivers warnings.

Warning: Driver 0 warning: phase A may be disconnected, phase B may be disconnected
Warning: Driver 4 warning: phase A may be disconnected, phase B may be disconnected

config.g

The SD card slot on my Duet 2 wifi (revision 1.04c) seemingly failed after a few years, so I purchased a new duet 2 ethernet (revision 1.06). Swapped out the board, and kept the connections identical from before. Now when I try to home any of the axes, I get the message:

Warning: Driver 1 warning: phase A may be disconnected, phase B may be disconnected

The 3-D printer is a Voron 2.4, and I have a connected duex for the Z-axis. How can I fix this? Were the motor phases changed between board revisions?

Thanks for the help.

On my duet 2 wifi + duex 5 there are two fans that cool the electronics bay. The intent is for these two fans to always match state.

Instead of wiring the fans together, I would prefer to create a software link that references both bay fan1 and bay fan2 as something like electronics bay

I would expect electronics bay to appear in the UI as a single fan, which then controls bay fan1 and bay fan2 in the background.

Hello all,

After upgrading from RRF 3.2.2 to 3.3 I had to modify my G31 command from

G31 T4 S21 P500 X0 Y0 Z-1.3;

to

G31 S21 P500 X0 Y0 Z-1.3;

was getting a new error - something along the lines of cannot use temperature coefficient of heater -1. I unwittingly started a print anyways and this led to a nozzle crash. Turns out when that error appeared the Z-offset did not apply. 1 broken Olsson Ruby nozzle later, thought I would post a warning

This does have me thinking... it would be nice if either

A.) the Z offset always applies, even if the G31 command runs into an error

or

B.) Z offset is applied via it's own special command (is this possible already?)