G38.x and acceleration (not stopping)
- andypugh
-
- Offline
- Moderator
-
- Posts: 23279
- Thank you received: 4933
Please note that ini.* hal pins are created too late to be used
in a [HAL]HALFILE (but they can be specified in a [HAL]POSTGUI_HALFILE
I had thought that the pins were "made" by motion, but it seems not.
Do you know which section of the docs do they appear in, for future reference?
They are regular hal pins rather than parameters? So they can be manipulated by a net, though won't be updated while a program is running?
Please Log in or Create an account to join the conversation.
- arhi
-
Topic Author
- Offline
- Senior Member
-
- Posts: 54
- Thank you received: 4

the "syntax" goes but it ain't doing nothing

arhimed@linuxCNC:~/linuxcnc/nc_files$ cat ../configs/mill25d/custom_postgui.hal
sets spindle-at-speed true
net X-accel motion.analog-out-00 => ini.0.max_acceleration
net Y-accel motion.analog-out-01 => ini.1.max_acceleration
net Z-accel motion.analog-out-02 => ini.2.max_acceleration
and the g-code:
G17
G21
#<_X-Accel-original> = #<_ini[AXIS_0]MAX_ACCELERATION>
#<_Y-Accel-original> = #<_ini[AXIS_1]MAX_ACCELERATION>
#<_Z-Accel-original> = #<_ini[AXIS_2]MAX_ACCELERATION>
T1
M6
(DEBUG, "default accel move")
F500
G1 X50
G1 X10
(DEBUG, "no accel move")
M68 E0 Q9999999
F500
G1 X50
G1 X10
(DEBUG, "slow accel move")
M68 E0 Q1
F500
G1 X50
G1 X10
(DEBUG, "restored accel move")
M68 E0 Q#<_X-Accel-original>
F500
G1 X50
G1 X10
M2
all three moves are using exactly the same acceleration

Please Log in or Create an account to join the conversation.
- dgarrett
- Offline
- Platinum Member
-
- Posts: 567
- Thank you received: 325
Do you know which section of the docs do they appear in, for future reference?
linuxcnc.org/docs/2.7/html/man/man1/milltask.1.html$ man milltask
Also:
linuxcnc.org/docs/2.7/html/config/core-c...s.html#_ini_settings
Please Log in or Create an account to join the conversation.
- dgarrett
- Offline
- Platinum Member
-
- Posts: 567
- Thank you received: 325
all three moves are using exactly the same acceleration
the acceleration value is not changed
But note that ini hal pins are not evaluated while a program
is running.
Please Log in or Create an account to join the conversation.
- arhi
-
Topic Author
- Offline
- Senior Member
-
- Posts: 54
- Thank you received: 4

unfortunately looks like no way to change those values

Please Log in or Create an account to join the conversation.
- andypugh
-
- Offline
- Moderator
-
- Posts: 23279
- Thank you received: 4933
had to try
unfortunately looks like no way to change those values
You can change them, then run a program. You just can't change them while a program is running.
Try issuing the commands from MDI.
Please Log in or Create an account to join the conversation.
- arhi
-
Topic Author
- Offline
- Senior Member
-
- Posts: 54
- Thank you received: 4

Please Log in or Create an account to join the conversation.
- andypugh
-
- Offline
- Moderator
-
- Posts: 23279
- Thank you received: 4933
will try that ... should help with G38 thing but not with everything else I wanted to use it for
I am still failing to see why, if your Z-axis can achieve a higher acceleration than you have configured, you don't simply set the Z axis to use the high acceleration all the time?
Please Log in or Create an account to join the conversation.
- arhi
-
Topic Author
- Offline
- Senior Member
-
- Posts: 54
- Thank you received: 4

Please Log in or Create an account to join the conversation.
- Rick G
-
- Offline
- Junior Member
-
- Posts: 26
- Thank you received: 155
Sounds like the best solution would be more powerful steppers / drivers to achieve the acceleration / speed you are looking for. Possible also look if you are using microstepping and go to a lower setting there.can drive XY @F500 without any acceleration (my original 3d print firmware don't support acceleration at all) but over F500 it will skip steps
Infinite acceleration is not really possible, always going to be limited by the machine.
Rick G
Please Log in or Create an account to join the conversation.