Hi Guys,

i have build a large format printer (10x5x4m) and running on the duet system. I have already printed some huge print.
Now in 4 days time i've started the exact same gcdoe 4 times and the 4th time it did something very weird.
Here is the video for explanation: (problem at 2:38)
https://www.youtube.com/watch?v=Ih0jrkUJZYs

To me it looks like the Y axis just stopped working for a few seconds and then picked up again. I checked all the wiring and the other camera's for blinking lights on the boards and everything looked fine.

It is good to mention i did not turn off power to the printer these 4 days. That should not be an issue as some prints take more then 4 days to finish.
The gcode itself cannot be the problem bc that has done perfect in the past days. Now suddently out of nowhere it dit what is shown in the video.
Recreating the issue while printing would take about 6 hours and alot of $$ in material. so thats not an option.

added is the M122, about 14h later than the pause-print as i was not at the shop when it happened.

Hope someone can help figure this out.

EDIT: found out the Y axis motors are skipping steps on the belt rack system..

Kind Regards,

Sten

Hi Guys, @Aitor @dc42

Same here... Motor brakes do not engage when using M18 or M84. It seems like when you plug the power-cord in, the brakes get the 24V.

That is pretty dangerous in my set up as my Z-axis weighs around 350kg...

Also the M569.7 (configure brakes) does not support 2 brakes. so M569.7 C"out0" works fine, but M569.7 C"out0+out1" does not.
Also putting them in seperate M569.7 commands does not work.

The DWC, 1HCL expansion boards and MB6CH are on v3.4.6

Looking forward to a reply!

@droftarts Thank you for the reply, that answers my question!

Hi Guys,

I have a Large scale printer where i use 4x Nema42 motors on the Z axis. These beast have their own drivers controlled with step and direction via 4x 1XD.
Now i want to run these in Closed Loop mode via the Duet system. My question is; can i run the duet encoder on the 1HCL and run the step and direction on the 1XD or does the motor need to be connected to the 1HCL as well?

.
PS: if someone knows a closed loop motor + driver combo capable of 25+ Nm of torque (Nema34 or 42) let me know!

PS2: does anyone know if i can remove the back plate of the motor safely or is this holding something back?

PS2: if someone knows a closed loop motor + driver combo capable of 25+ Nm of torque (Nema34 or 42) let me know!

@T3P3Tony Thank you! i think this is the way, i didnt think about the Deamon file. i'm going to try it out and update this thread!

Hi Guys,

Somewhere a while ago i read about a command in the config that could lower printing speeds if the Z reaches certain heights.
I want to implement this in my printer, is there anyone that can help me find this?

PS: i dont want to do this in the slicer as i slice at an angle and post process it for my 45" degree angled printing so the gcode will be weird.

Kind Regards,
Running 1x 6CH mainboard, 5x 1HCL, 5x 1XD at 3.5b4

Please mark as solved / delete topic

@oliof Yes, at that moment. they glitch out all the time btw, bc its a ''stream'' from the security system. The camera's NVR is on a seperate fuse and on a UPS. The printer got a whole different power supply.

Hi Guys,

i have build a large format printer (10x5x4m) and running on the duet system. I have already printed some huge print.
Now in 4 days time i've started the exact same gcdoe 4 times and the 4th time it did something very weird.
Here is the video for explanation: (problem at 2:38)
https://www.youtube.com/watch?v=Ih0jrkUJZYs

To me it looks like the Y axis just stopped working for a few seconds and then picked up again. I checked all the wiring and the other camera's for blinking lights on the boards and everything looked fine.

It is good to mention i did not turn off power to the printer these 4 days. That should not be an issue as some prints take more then 4 days to finish.
The gcode itself cannot be the problem bc that has done perfect in the past days. Now suddently out of nowhere it dit what is shown in the video.
Recreating the issue while printing would take about 6 hours and alot of $$ in material. so thats not an option.

added is the M122, about 14h later than the pause-print as i was not at the shop when it happened.

Hope someone can help figure this out.

EDIT: found out the Y axis motors are skipping steps on the belt rack system..

Kind Regards,

Sten

@dc42 That is correct. When shutting down in open-loop mode what happens is: (in this order)

1. Power off by hand (unplugging power cord) or emergency stop by DWC
2. motors lose currect (lose their holding torque) and gantry moves down.
3. after a slight delay (0.5sec) brakes engage bc of loss of power and stop the gantry from falling further down.

When the gantry weight was still 250kg's the brakes couldnt stop the downward movement and it continued to fall down.
Now we have 2x 100kg's counterweights and the ''weight'' of the gantry is now 50kg's. So now they can stop it when it falls. But that doesnt happen anymore as long as i do the shutdown procedure.

Startup procedure:

1. At startup it runs the config file wich contains M569 P50.0 S0 D4. (closed-loop without tuning maneuvre so brakes are engaged)
2. after that i manually run a startup macro: M569 P50.0 S0 D0 and run open loop mode.

Shutdown procedure:

1. Run macro wich only contains 5x M569 P50.0 S0 D4. for all the motors (to engage the brakes again)
2. Power off (unplug the cord)

.
NOTE: When updating the boards to new firmware, the motors lose holding torque AND the brakes are dis-engage. wich makes the gantry fall down too. i dont know if its in open-loop or closed loop when starting the update, but i could replicate this if you like.

@dc42 Quick update, printer is running and printing, the 3,5 beta 4 runs perfectly in open loop mode. Before shutdown i switch to closed-loop (without tuning maneuvre) to engage the brakes and shutdown the system, at startup they also begin in closed loop so the gantry doesnt drop down.

Cant get the Nema34's tuned tho... it gives weird oscilations and sounds with the standard settings. also the tuning maneuvre gives incostistent values and errors.

Would love some help on this topic. bc my printer has small inconsistencies in open-loop and i want to run in closed loop.

Kind regards!

@dc42 said in 1HCL 1.0 closed loop controller:

@supertb1 the homing move or moves should aways be done in open loop mode, and should be followed by the basic tuning move before switching to closed loop.

You mean after homing, switch to closed loop and THEN do the tuning maneuvre? The documentation states it that way...?
Still having trouble with my Nema34's closed loop so i'm looking at everything right now.