let me get back to you in a couple days, im now using a duex board and put my fan on that board for now as a temporary solution so i have a print going and cant access it at the moment. Thank you for your reply

it is running 2.05.1

Configuration:
M106 P1 S1 I0 F500 H1 T45
M106 P2 S1 I0 F500 H1 T45

I had a print failure, filament got into the hotend fan and tore the wiring off causing a short in the 1a fuse. I replaced the fuse and i cannot get power to p1. I configured to use p2 as a work around, it powers on for a second on boot up and then I cannot get it going after that (trying temp >50c, or using m106). this is a new fan with complete new wiring and I can get this fan working on an always on fan block. Is my board destroyed or do i have any options to get it working again?

@dc42 thank you. my question now then is what is the correct procedure to get g32 and g29 values after a power cycle? do i just need to run g32 after booting, and have g29s1 in slicer? or must i redo g29 after g32 on reboot?

@PaulHew im on 2.05.1 and rrf3

thank you

I have a corexy with 4 z motors next to each of 4 rods and bltouch. I can perform g32 and g29 manually which as far as i can tell perform their function and adjust accordingly.

I have a couple problems:

1. g32 compensation does not seem to hold after reboot. i verified by running g32 after a reboot and it has to compensate each time.
   • Are these settings stored somewhere?
   • if so where, and how do i call on it?
2. after performing both tasks, and then manually move the print head around i do see that the bed is level with the paper method on a warm bed/nozzle, i then try to print a sliced file. as the nozzle moves 1/3 to 1/2 across the bed, it crashes into the build plate. I can only assume g32 and or g29 did not load.
   • must i call the result of g32 then g29s1 in my slicer?
   • if i call just g29s1, will it also take into account g32?

Ideally id want to have the duet leveled once and not before every print/reboot. if that is possible, i am at a loss at how to achieve it

bed.g
G28 ; home
M401 ; deploy Z probe (omit if using bltouch)
G30 P0 X20 Y150 Z-99999 ; probe near a leadscrew,
G30 P1 X20 Y370 Z-99999 ; probe near a leadscrew,
G30 P2 X450 Y370 Z-99999 ; probe near a leadscrew,
G30 P3 X450 Y150 Z-99999 S4 ; probe near a leadscrew and calibrate 2 motors
M402 ; retract probe (omit if using bltouch)

config.g
; Drives
M584 X0 Y1 Z7:6:5:2 E3
M569 P0 S0 ; physical drive 0 goes backwards
M569 P1 S0 ; physical drive 1 goes backwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S0 ; physical drive 3 goes backwards
M569 P4 S1 ; physical drive 4 goes forwards
M569 P5 S0 ; physical drive 4 goes forwards
M569 P6 S0 ; physical drive 4 goes forwards
M569 P7 S0 ; physical drive 4 goes forwards
M584 X0 Y1 Z7:6:5:2 E3:4 ; set drive mapping
M671 X-50:-50:560:560 Y145:370:370:145 S3 ; leadscrews at left (connected to Z) and right (connected to E1) of X axis

-Thank you