both tristate_float & abs_s32 won't load ! (addf fails)

More
01 Dec 2016 03:26 - 01 Dec 2016 03:44 #83513 by gmouer
both tristate_float and abs_s32 components won't load properly
The loadrt line appears to function properly but the failure occurs with the addf line for the respective component.
I am running debian and 2.7.8, installed off the livecd and then updated.
The tristate_float was reported and fixed about a year ago I found on a search, The problem appears to have re-appeared

both of these fail on the addf line

loadrt tristate_float count=1
addf tristate_float.0 servo-thread

loadrt abs_s32 count=1
addf abs_s32.0 servo-thread

(Both components are used in the example hal file for the shuttlexptress included with the 2.7.7 livecd)
I would appreciate someone testing loading these components.

Thanks
George
Last edit: 01 Dec 2016 03:44 by gmouer.

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

More
01 Dec 2016 14:20 #83522 by PCW
In both cases, the function name uses a dash instead of a underscore
so:

loadrt tristate_float count=1
addf tristate-float.0 servo-thread

loadrt abs_s32 count=1
addf abs-s32.0 servo-thread

works
Dont ask me why these are named this way

If you have a question about a function name you can just loadrt the component and then:

halcmd show funct

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

More
01 Dec 2016 14:27 #83523 by gmouer
Thanks Pete !

Apparently the example hal file for the shuttlexpress, which is included with the livecd has the syntax of the addf for those components wrong also.

That example hal file for the shuttlexpress should be corrected.
(here is the code, same as included on the livecd. github.com/modmaker/machinekit/blob/mast...on/shuttlexpress.hal)

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

More
01 Dec 2016 14:45 #83524 by PCW
Yeah probably just a bad assumption when those examples were typed in
(and apparently not tested)

The man pages for the components are correct

and
linuxcnc.org/docs/html/hal/comp.html#_syntax
Explains the name munging

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

More
01 Dec 2016 16:39 #83529 by Todd Zuercher

Thanks Pete !

Apparently the example hal file for the shuttlexpress, which is included with the livecd has the syntax of the addf for those components wrong also.

That example hal file for the shuttlexpress should be corrected.
(here is the code, same as included on the livecd. github.com/modmaker/machinekit/blob/mast...on/shuttlexpress.hal)


It is right in the example you linked to

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

More
01 Dec 2016 16:46 - 01 Dec 2016 16:48 #83530 by gmouer

Thanks Pete !

Apparently the example hal file for the shuttlexpress, which is included with the livecd has the syntax of the addf for those components wrong also.

That example hal file for the shuttlexpress should be corrected.
(here is the code, same as included on the livecd. github.com/modmaker/machinekit/blob/mast...on/shuttlexpress.hal)


It is right in the example you linked to


Hi Todd,
I used that example code as a basis for writing hal code for my shuttle pro. The pro model is slightly different.
I also found some other problems with the shuttlexpress example hal file. The file references some halui.axis pins which no longer exist in the current lcnc release. That caused pin not found error messages.
in particular : halui.axis.jog-speed , halui.axis.x.plus, halui,axis.x.minus (same for Y and Z axis)
These pins are now relocated into the halui.jog section.

Had a novice like me plenty confused for a while, but I won the battle and my bridgeport has variable speed jog with the shuttle pro working nicely now.

George
Last edit: 01 Dec 2016 16:48 by gmouer.

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

More
02 Dec 2016 14:14 #83575 by andypugh

loadrt abs_s32 count=1
addf abs-s32.0 servo-thread

Dont ask me why these are named this way


The reason is that the component name has to match the file name, and "-" is invalid in a Linux file name.
However the standard for HAL pins is (meant to be) all "-" and no "_",

(I didn't say it was a _good_ reason)
The following user(s) said Thank You: gmouer

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

Time to create page: 0.084 seconds
Powered by Kunena Forum