c++ grab in position signal

yes ... now I try to force it to 1 and in hal meter and in hal configuration it exist and go to 1 value

.... mmm ... the previous version of mycomponent.comp are named MYcomponent.comp .... yesterday during my first test I see that calling hal parameter into gcode is supported only for lowercase, than i renamed MYcomponent pin and hal pin in hal file, in component and in all custom Mcode to lowercase "mycomponent". Than I cancel Mycomponent from usr/bin folder and I compiled again "mycomponent" and I install it (using sudo comp --install & sudo comp --compile ..... there are some other operation for complete the change from "MYcomponent" to "mycomponent"??

I call gcode like a subroutine using halui.mdi .... I'm on ubuntu 10.04 and linuxcnc 2.5.4 ...I do not know what else to add

andypugh wrote:

k-1 wrote:

there are some other operation for complete the change from "MYcomponent" to "mycomponent"??

The filename and the component name declaration in the .comp file have to match exactly or you get hard-to-spot errors.

Indeed, you need to stop using capitalisation, dashes or underscores in names also.

All of those can lead to unexpected errors, the python interpreter in comp will for instance try to subtract one half of a name from the other half if you use a dash

regards

normally in all my code I don't use strange caracters ..... only use number for reply some var.... in this case I have use MYcomponent... sob ... but yesterday I change all reference to this component to "mycomponent" ..... anyway have this error ..... how I can solve it? ... change name, and all other reference, of my component (example in charlie.comp , charlie.signal, etc etc) can solve this issue? ..... there are other operation to do?

yes during normal operations mycomponent.kstop work OK .... BuT I never read and see the doc that you have mentioned .... very thanks .... I don't understand the right mode to declare this feature...

FEATURES: 8
or
FEATURES: enable #<_hal[my component.stop]> ??

do not worry ..... I should do more study the doc.

in ordet to solve my ysterday question, today have re-rename mi comp in e.comp ..... all custom Mcodes and other pins or signal become now e.xxxxx .... in mi file.ini I've add FEATURES=12 .... and I read this post andypug-goodworck .... but I still have the yesterday problem with the parameter # < _ hal [ e.sftop [> ... if you launch a command mdi so .... I get ######

but in hal meter I see it to change value from 0 to 1 and vice versa .......

ps. to avoid any problem I deleted every other INI files related to other tests done on the pc apart from that I work on.

.... I get ###### with FEATURES=12 and 28 too