Posts made by Dutchprinting

@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.

Having the same problem here, cant get my Nema34's tuned correctly, incosistent tuning backlash and so on.

motors i'm using: https://www.omc-stepperonline.com/p-series-nema-34-closed-loop-stepper-motor-12nm-1700oz-in-with-with-electromagnetic-brake-34e1kbk50-120
Datasheet: https://www.omc-stepperonline.com/download/34E1KBK50-120.pdf

Ran through the documentation about 15 times now, including the full tuning guide. but still no succes.
It runs in closed loop tho, only with alot of vibrations and oscilations.

@o_lampe Haha, Oranje boven!

Yes i was thinking of ordering a small stepper motor, i have one 1HCL and one 6ch mainboard extra so i could test with that. But then still, the forces are so diffrent from a small set up, also the ''belt system'' is not even close to a 'normal' printer. If you have experience, maybe you could come play around with the setup with me, i'm in the great city of Elburg.

I'm hoping @dc42 will chip in, he tested the 1hcl firmware with a Nema34 from stepper-online if i remember correctly.

The 1:1 scale benchy is on my wish list, we need to adjust the model to not be top heavy and suitable for an outboard engine, so we can really sail it.
i think we will break youtube (and a world record) when we do print it.

Hi Guys,

I have build a incredible big printer (9x6x4 meters)(picture below) with Nema34 motors: Stepper online.
They are all connected to 5x 1HCL expansion boards connected to a 6ch mainboard all running 3.5 beta4

In open-loop mode everything runs fine but because of the weight of the gantry i get some inconsistance in the Y axis.
I want to run in closed loop, this will work (kind of) but i cannot get it tuned properly.

My 'closed-loop-tuning' plugin displays a totally diffrent graph then the documentation examples.
I've tried walking through it multiple times but i cannot get close to a good tuning.
Also tried multiple settings and parameters in het P,I,D,V,A.

But the motors start shaking while moving or ''having trouble'' making steps.
In open loop mode there are no problems except for overshooting at high speeds.
Default settings also give the same problems in closed loop.

The best i could come up with: M569.1 P50.0 T2 S200 C1000 R100 I400 D0.05 V1000 A5000000

CONFIG:
M569.1 P50.0 T2 S200 C1000 R100 ; Configure the 1HCL board
M569.7 P50.0 C"out1" ; control the brake
M569 P50.0 S0 D4 ; physical drive 50.0 goes forwards
M350 X16 Y16 Z16 E16 I0 ; set microstepping

Hoping someone can help!
Kind Regards,

@dc42 Yes, all of them run the the 3.5 beta 4. i double checked with M115. Also the DWC and mainboard 6ch are on 3.5 beta 4

@dc42 Unfortunately i cannot edit the post above. I have tested alot more and have things sort of working now.

i'm on 3.5 beta 4. The only thing is that the brakes do not engage when M18 of M84 is send.
i can rotate the motor by hand when M18 is send. When i send M17 the motor enables and holds its torque ofcourse.

With the weight of the gantry in mind i could move it to a sort of 'stand' to rest on and then turn the power off.
The brakes will also save me in the case of a power failure.

The thing is... after a power failure, When i power the system back up, the motors AND brakes are not engaged. So the gantry drops down.

So my question is... is there a way to disable out0 at startup, and only enable when the motor is enabled? (1HCL)

@jay_s_uk i'm guessing DC knows best but maybe you can chip in?

@dc42 Bc the brake on the motor is 4Nm, turns out it is too weak. Now i've put a 9Nm brake in between the motor and the gearbox. As the brake is embedded in the motor body i cannot remove it. I think i will just put boths brakes together in a connector on 1HCL out0.

@jay_s_uk After updating to 3.5 beta 4 i have the following problem :
it looks like the brakes dont get enough power, some boards do the tuning manuever well and some error and fail, i tried it with only the motor brake and the motor brake + new brake. The one's that do work engange when M18 is send, so thats progress...
i think my best option is to switch back to v3.4.6 and try with the double brakes.

Here is my config: (some parameters are still off due to testing)

M569.1 P50.0 T2 S200 C1000 R100 I0 ; Configure the 1HCL board
M569.1 P123.0 T2 S200 C1000 R30 I2000 ; Configure the 1HCL board
M569.1 P52.0 T2 S200 C1000 R30 I2000 ; Configure the 1HCL board
M569.1 P53.0 T2 S200 C1000 R30 I2000 ; Configure the 1HCL board
M569.1 P54.0 T2 S200 C1000 R30 I2000 ; Configure the 1HCL board

M569.7 P50.0 C"out0" S1 ; control the brake
M569.7 P123.0 C"out1" S1000 ; control the brake
M569.7 P52.0 C"out1" S200 ; control the brake
M569.7 P53.0 C"out1" S1000 ; control the brake
M569.7 P54.0 C"out0" S200 ; control the brake

M569 P50.0 S1 D4 ; physical drive 50.0 goes forwards
M569 P123.0 S1 D4 ; physical drive 51.0 goes forwards
M569 P52.0 S0 D4 ; physical drive 52.0 goes forwards
M569 P53.0 S0 D4 ; physical drive 53.0 goes forwards
M569 P54.0 S0 D4 ; physical drive 54.0 goes forwards
M569 P55.0 S1 D4 ; physical drive 55.0 goes forwards

M584 X52.0 Y50.0:54.0 Z123.0:53.0 E55.0 ; set drive mapping / :54.0
M92 X25.64 Y25.64 Z25.64 E25.64 ; set steps per mm (vention 125mm per full rotation / 200 steps = 1.6)
M350 X32 Y32 Z32 I0 ; Set microstepping mode
M566 X900.00 Y900.00 Z100.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X8000.00 Y8000.00 Z4000.00 E100.00 ; set maximum speeds (mm/min)
M201 X300.00 Y300.00 Z300.00 E250.00 ; set accelerations (mm/s^2)
M906 X6000 Y6000 Z6000 E800 I100 ; set motor currents (mA) and motor idle factor in per cent
M917 X10 Y10 Z100 ;0.71 ; set closed loop axes to have current of 10 percent
M84 S1 ; Set idle timeout in seconds

---

And for a reference, this is the printer i'm building:

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!