Advanced Search

Just to be clear:
Changing acceleration values during Gcode execution IS possible. But the changed values are only used AFTER the interpreter has encountered a queuebuster command (eg M66 E0 L0) in the gcode which forces a synchronization between the interpreter and actual motion control.
For an example of how to use custom MCodes to change ini values (eg axes-limits, -velocity and -acceleration ) see the included 'millturn' simulation config where these values are changed using M128/M129:
github.com/LinuxCNC/linuxcnc/blob/master...millturn/mcodes/M129

The queuebuster command (ie M66 E0 L0) is located in the preceding 'M428/M429' remap that call 'M128/M129' respectively:
github.com/LinuxCNC/linuxcnc/blob/master...ap_subs/429remap.ngc

The split in MCodes is necessary because it is not possible to set halpins directly through gcode but only through a hal command. On the other hand it is not possible to issue gcode commands to synch the interpreter using a hal command.

So what all this means is that changes to axis acceleration have to be inserted into the gcode program prior to program execution.

Hello Todd,

Feed Override does work actually, but the accelerated max speed for the 3D and 2D movements are become different. For reference i have attached one image where 2 different section is marked with numbers, mark 1 section has Z movement and mark 2 do not has Z movement this makes section 2D movement.

Now, when tool slide down from the leaf of flower if feed override set to 10% then speed reduce to some speed x but when running in between leafs the machine speed reach to 3-5x due to x-y acceleration. really required is feed percentage should set all the axis speed to same level and maintain that speed between part1 and 2.

Okay, good that somebody else feels the same.

I realize the first post was rather long. The TL;DR is: why not have the HAL net command give signal names automatically in case no net name is specified. And if multiple connections is done to the same pin, simply link the following ones to the signal that is already there, without having to explicitly specify its name.

I was wrong with saturation. I'm used to small ferrite toroidal transformers wich are sensible to saturation, but your is surely iron core. Like Tommy said, the limit is the temperature.
And even with ferrite, it's only one magnetic circuit, so saturation would only appear when the total windings current exceed the maximum of the transformer.
We don't care of unbalanced current between windings.

Tommy advice is to overload it and check the temperature, I agree it works, put the right fuse after test on the output and then. Are you even sure you will overload it ? Maybe not !
I would although consider to change it because I think it's a small one (you don't say how many amps you have), and I have many unused transformers. Maybe you don't. Have a look around you, it's easy to find some...

Doing a power supply.. For me no, if you put the three in series you will have 90VAC, better to use directly 120VAC or 240VAC in this case.

But once again, I assume your transformer is a small one (300VA ?), it's not the same if it's a 2kVA one, but in this case you wouldn't need to worry for the third driver.