Good news!

I printed 3 more of the same 3D model (22 hour print ~500g of plastic PETG) and I have not had this failure since grounding the casing of only the extruder motor. So it seems that the issue was indeed ESD on the stepper driver causing it to go into a failure mode.

Thank you very much for your time and help!

I think you're on the right track with the G60 command. You don't provide any details of the trigger macros, so the rest of this post is just guessing on my part...

I assume you've read this page on setting up triggers: https://docs.duet3d.com/en/User_manual/Tuning/Triggers, and that you've set up the inputs for the two buttons using M950, and also defined triggers numbered 10 and 11 using M581. Also, you've got these commands in your config.g file so they'll be executed every time you start the machine.

The trigger10.g macro should need only one command.

;trigger10.g G60 S3

When this macro runs it will save the current machine location into slot #3.

The trigger11.g macro should looks something like this:

;trigger11.g G0 R3 X0 Y0 Z0

This commands a fast move to the stored S3 location without any offset in the X,Y,or Z positions stored in S3. If you don't have the X0 Y0 Z0 in your command, those axes won't be moved (it will look like nothing has happened when you push the second button).

An additional thing to consider in your trigger 11.g macro. If your "move to" button is pressed before the "save position" button, the default coordinates stored in slot S3 are 0,0,0 so you'll drive a move you might not want. If you are unlikely to ever save 0,0,0 with your "save location" button, you could write an IF statement into your trigger11.g macro to look at the current values saved in this slot and if they are all 0, you could do something like post a message and not make the move.

To test your trigger10.g macro without the buttons, you can send M98 P"trigger10.g" in the Web control window, then send echo state.restorePoints[3].coords to see the saved coordinates. You can also look at the object model plugin to see if the location has been stored. It will be in state > restorePoints >3

You can similarly test trigger11.g. After running trigger10, move the machine using the Web control then send M98 P"trigger11.g" in the Web control window. Your machine should move back to the stored position.

You can also test the inputs by looking at the inputs section of the object model while you press the buttons.

@Esteban said in Information on the distribution of calculations on Duet cards:

On the other hand, one last question: for very complex machines with a large number of axes, would it be more “efficient” to have a main 6XD and then add 1XDs and another 6XD in daughter mode?

If all the axes and extruders use servomotors then you should start with a 6XD. If there are more than 6 servos to connect then you will need another 6XD or some 1XD boards to drive them. If the additional axes need high step rates then another 6XD would give better performance than 1XDs.

@gsch1803 said in Unresponsive duet 3 6HC board:

@Phaedrux I believe it was purchased from Amazon in October

Who is the amazon seller?

@R006 in firmware 3.6 the code that sets the LED pin numbers correctly depending on the board version is at src/Platform/Platform.cpp starting at line 3489.

@dc42 In a closed loop, D is 0, and still, for a 0.8 nozzle, I tend to run at 30-40 mm/s, and at that speed, it is very noisy. The assisted open loop leads to shifts. Unfortunately, these parts are in production, and I just went back to open loop with reduced Acceleration and higher motor current. We will deal with the setup after this job is finished

@achrn thanks for that info. i will try at 25khz and also the pullup resistor

@dc42 the label on the fan is the right one but someone said that rat ric also had an batch with the wrong label

@R006 What is the bed surface? It needs to be metal on, or near the surface (under a PEI sheet is okay), ie not have glass on top.

Are you setting the M558.2 calibration with the SZP coil around 4mm from the bed?

When you say "the value is fluctuates between 0, 9097, and 999999" are these the only three readings? Or does it give other readings? I'd usually expect to see readings in the range 1500 (Z6) to 15000 (Z0.3). You shouldn't get 0 or 999999 readings.

Random 999999 readings can be caused by:

Interference on the SZP ribbon cable (from SZP to coil). Makes sure to route the SZP ribbon cable away from the coil, ie make sure it doesn't go over the coil Poor ribbon cable contact. Ensure it is FULLY inserted into the tiny connector, at both ends. Try reseating this if you continue to get erratic readings Make sure there is no metal in the 30mm ABOVE the coil, or it will pick this up and give false readings

What firmware version are you running on the 6HC and SZP?

Ian

@axiom only create a bed mesh of the area of the print: https://forum.duet3d.com/topic/37242/mesh-bed-leveling-only-in-printing-area-using-orca-slicer

Ian

@dc42

I just ran into the same thing... 2 of my drivers were complaining about over heating...yikes!
This is on a Duet 3 Mini 5 with 6 active stepper motors.

So, I'm off to print a backing plate with taller stand-offs and a mount for a blower fan. My stepper motors are all fairly cool, but the amperage draw makes sense. My FLIR ONE camera came in handy yet, again! ; )

Cheers!

@axiom 1736183041163-flow.jpg

@stuartofmt Thank you for the answers, everything actually works if I simply copy the IP address from Motion....sadly my new raspberry 5 said goodbye after 1 hour...despite the expensive original fan and expensive power supply

@HugoZM My guess is that you have mis-wired the endstop switch so that when it is triggered, it shorts out the 3.3V rail or the 5V rail. If that's the case then you will see the red 5V or green 3.3V LED go out when you trigger the endstop switch.

@Arkadiusz it sounds like a power supply problem to me. Send M122 a couple of times to reset the record of minimum VIN voltage; then command movements that cause the motor to stall; then send M122 again and look at the current and minimum VIN voltage in the report.

@axiom octoprint can be run on an rpi5 https://community.octoprint.org/t/raspberry-pi-5-octoprint/60487/2

@engikeneer thank you very much, then I will just print a few tests

@jay_s_uk
wow, thank you so much! That was the solution, now I just have to figure out the input shaping....have a nice Sunday, cheers, Don

@Phaedrux
Homeall.g

G91 G1 H2 Z2 F100 G1 H1 X-300 Y-300 F600 G1 H2 X5 Y5 F1000 G1 H1 X-300 Y-300 F200 G1 H2 Z-5 F100 G1 H1 Z304.1 F300 G1 H2 Z-2 F100 G1 H1 Z304.1 F100 G92 X0 Y0 G90 G92 Z304.1

homex.g

G91 G1 H2 Z2 F100 G1 H1 X-300 F600 G1 H2 X5 F600 G1 H1 X-300 F200 G1 H2 Z-2 F100 G92 X0 G90

homey.g

G91 G1 H2 Z2 F100 G1 H1 Y-300 F600 G1 H2 Y5 F600 G1 H1 Y-300 F200 G1 H2 Z-2 F100 G92 Y0 G90

homez.g

G91 G1 H2 Z2 F300 G1 H1 Z304.1 F360 G1 H2 Z-5 F240 G1 H1 Z304.1 F200 G90 G92 Z304.1

config.g

M552 S1 ;M552 S-1 M586 P0 S1 M586 P1 S0 M586 P2 S0 ; Drives M569 P0 S1 M569 P1 S1 M569 P2 S1 M569 P3 S1 M569 P4 S1 M569 P5 S1 M584 X0 Y1 Z2:3:4 E5 M350 X32 Y32 I0 M350 Z16 E16 I1 M92 X160.0 Y160.0 Z2133.33 E932.00 ;change as per machine M566 X720.00 Y720.00 Z300.00 E600.00 M203 X8400.00 Y8400.00 Z420.00 E8400.00 M201 X3000.00 Y3000.00 Z30.00 E250.00 ;M-curr M906 X1600 Y1600 Z1600 E800 I50 M84 S30 ; Axis Limits M208 X0 Y0 Z0 S1 M208 X300 Y300 Z304.1 S0 ; filament Sensor M591 D0 P7 C"exp.e3stop" R15:300 L7 E17 S1 ; Endstops M574 X1 S1 P"xstop" M574 Y1 S1 P"ystop" M574 Z1 S1 P"zstop+e0_stop+e1_stop" ; Z-Probe M950 S0 C"exp.heater3" M558 P9 C"^zprobe.in" H5 F120 T6000 G31 P500 X0 Y0 Z1.038 ; Auto level, coordinates as per motor order in M584 M671 X-17.66:297.34:140.00 Y-5.00:-5.00:327.61 S5.0 F1.2 ; define mesh grid M557 X30:300 Y30:300 S20 M376 H5 ; End Limits M950 J1 C"exp.e4stop" M581 P1 T2 R0 S1 M582 T2 M581 P-1 T2 M581 P1 T0 R0 S1 ;PA M572 D0 S0.045 ; Bed Heater M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 M950 H0 C"bedheat" T0 M307 H0 B0 S1.00 M140 H0 M143 H0 S105 ; Extuder Heater M308 S1 P"e0temp" Y"pt1000" M950 H1 C"e0heat" T1 M307 H1 B0 S1.00 M143 H1 S320 ; cooling Fans M950 F0 C"fan0" Q500 M106 P0 S0 H-1 M950 F1 C"fan1" Q500 M106 P1 S0 H-1 ; Tools M563 P0 D0 H1 F0 G10 P0 X0 Y0 Z0 G10 P0 R0 S0 M575 P1 S1 B57600 M501 M911 S21 R22.5 P"M913 X0 Y0 G91 M83 G1 Z5 E-5 F1000" M929 S3 P"/macros/SERVICE/log/STPL_DEBUG.txt"

@flopo76 I have recently built the Mercury One zeroG Hydra 1.1 conversion of an Ender 5. I have RPI driving Duet mini 5+ and a HUVUD tool board running CAN from duet USB-Can bridge.

Everything has flashed fine but I am having intermittent issues. When I try to move the bed in large movement all three Z stepper get way out of sync. I am wondering if the USB speed from RPI to Duet is limited and causing communication issues. I really want to use this board but it has been one headache after another.