G38.x and acceleration (not stopping)

More
30 May 2016 22:04 #75268 by arhi

It has come up before, but i know of no easy solution.


well if the M201/202/204 are not supported by the linuxCNC there's definitely no easy way to do it ... I'll figure something out in hw, just wanted to check if there are sw solutions first :)

Please Log in or Create an account to join the conversation.

More
02 Jun 2016 14:19 #75335 by andypugh

Yes, exactly what I want :D to stop "faster then set limit" ... is that possible?


No, because the whole point of the limit is to be, well, a limit.

You could look at changing the limit "on the fly" look for HAL pins called "ini.***". You could pass different values to those prior to a probe move.
The following user(s) said Thank You: arhi

Please Log in or Create an account to join the conversation.

More
02 Jun 2016 16:02 #75340 by arhi
yes, but having a different limit for different operations also makes sense

Thanks for the HAL pins tip, off to gogle :D

Please Log in or Create an account to join the conversation.

More
02 Jun 2016 20:14 #75359 by arhi

You could look at changing the limit "on the fly" look for HAL pins called "ini.***". You could pass different values to those prior to a probe move.


www.linuxcnc.org/docs/2.7/html/remap/rem...i_file_configuration

enable #<_ini[section]name> read only variables: 4

if set, the interpreter will fetch read-only values from the ini file through this special variable syntax.
enable #<_hal[Hal item]> read only variables: 8

if set, the interpreter will fetch read-only values from HAL file through this special variable syntax.


here it's said they are readonly .. I know how to read the ini.0.maxacceleration but how to write to it?

I doubt this is going to happen in sw .. will have to do it in hw :(

Please Log in or Create an account to join the conversation.

More
02 Jun 2016 20:53 - 02 Jun 2016 20:53 #75362 by andypugh

www.linuxcnc.org/docs/2.7/html/remap/rem...i_file_configuration
enable #<_ini[section]name> read only variables:


That's a different thing.

That is reading values from the INI file into G-code.

I was talking about the HAL pins such as ini.0.maxacceleration which you can manipulate in HAL.

For a first-cut. In the HAL file
net Z-accel  motion.analog-out-00 => ini.2.maxacceleration
Then in the G-code you can change the value with an M68 code.
linuxcnc.org/docs/2.7/html/gcode/m-code.html#mcode:m68
Last edit: 02 Jun 2016 20:53 by andypugh.
The following user(s) said Thank You: arhi

Please Log in or Create an account to join the conversation.

More
03 Jun 2016 01:25 #75369 by arhi
great I understood those are the same ... read already about m66 and m68 but I don't get the "E 0 to 3" is this the ## from motion.analog-out-## ?

will try immediately :D (it's 3:30am so will be running dry or my wife will throw me out but enough to see if it passes the syntax test :D )

Please Log in or Create an account to join the conversation.

More
03 Jun 2016 01:52 - 03 Jun 2016 01:53 #75371 by dgarrett
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
if the chosen gui supports it or in independent applications that
access hal pins after starting LinuxCNC.

$ man milltask
...
These pins cannot be linked or set in a halfile specified
by [HAL]HALFILE. They can be altered by independent halcmd
programs or by GUIs that support [HAL]POSTGUI_HALFILE. The
inifile is not auto‐ matically updated with these values
but can be updated using the calibration program
(emccalib.tcl) when using a [HAL]POSTGUI_HALFILE.

Last edit: 03 Jun 2016 01:53 by dgarrett.
The following user(s) said Thank You: arhi

Please Log in or Create an account to join the conversation.

More
03 Jun 2016 02:21 - 03 Jun 2016 02:28 #75374 by arhi

For a first-cut. In the HAL file
net Z-accel  motion.analog-out-00 => ini.2.maxacceleration


not working :(

not a single ini.*.* is recognised, linuxcnc fails to start (not a pin...)

for e.g. this works
net lalala motion.analog-in-00 <= axis.0.backlash-vel

so I'm sure syntax is ok

but this is "not a pin"
net lalala motion.analog-in-00 <= ini.0.backlash

(or any other ini.*.* tried 5+ different ones)

@dgarrett, what you wrote explains why this don't work but I'm not sure I understand the "They can be altered by independent halcmd
programs or by GUIs that support [HAL]POSTGUI_HALFILE" ?! are you saying that I can create a M204 script that will change the ini.0.max_acceleration value using halcmd? I do not want to change the ini file, I just want to set new acceleration values for axis for "from M204 till another M204..) .. now I never made a Mxxx on the linuxcnc but iirc it's just a shell script that you can use to do whatever you want right? so halcmd blah blah blah ? any chance you can share a cmd that will change ini.0.max_acceleration value? :D

EDIT: looks like I can just halcmd net ... after linuxcnc started, now these pins are available ... any way to tell linuxcnc to exec a "Script" after loading?
Last edit: 03 Jun 2016 02:28 by arhi.

Please Log in or Create an account to join the conversation.

More
03 Jun 2016 02:44 - 03 Jun 2016 02:48 #75376 by dgarrett

any way to tell linuxcnc to exec a "Script" after loading?

linuxcnc.org/docs/2.7/html/config/ini-co...applications_section

But note that ini hal pins are not evaluated while a program is running.
Last edit: 03 Jun 2016 02:48 by dgarrett.
The following user(s) said Thank You: arhi

Please Log in or Create an account to join the conversation.

More
03 Jun 2016 03:05 #75379 by arhi
custom_postgui.hal seems to be proper place to put these net's

Please Log in or Create an account to join the conversation.

Time to create page: 0.108 seconds
Powered by Kunena Forum