- Posts: 1111
- Thank you received: 0
#<_hal[custom.pin]> not defined
I use the value of out bit parameter from my custom comp in a if loop in my gcode ... the gcode is present as start code in myini.ini file ... Is possible to solve these warning (I need start with these program ... I've not choice) ... i just try to use my gcode as soubroutine ... but obviously is the same ...
In My header custom comp there is these line:
Regards
giorgio
Please Log in to join the conversation.
linuxcnc.org/docs/2.7/html/remap/remap.h...i_file_configuration
Be aware of the warnings here:
linuxcnc.org/docs/2.7/html/remap/remap.h...ap:referto-hal-items
Your ,comp sample seems to create two pins with the same name. That probably won't work.
Please Log in to join the conversation.
ini file ... open_file = ""
than when axis (or in my case nogui gui
and use these script on remote machine..
if you prefer can use as argv the complete name file or path complete name file (example /home/myfolder/myngc.ngc) ... so the last row become:
that's all folks ...
If there are a more secure and elegant method I hope that someone me indicates ....
Regards
giorgio
Please Log in to join the conversation.
You need to activate reading HAL pins from G-code:
linuxcnc.org/docs/2.7/html/remap/remap.h...i_file_configuration
Be aware of the warnings here:
linuxcnc.org/docs/2.7/html/remap/remap.h...ap:referto-hal-items
for version 2.6 is the same??
Regards
Giorgio
Please Log in to join the conversation.
You need to activate reading HAL pins from G-code:
linuxcnc.org/docs/2.7/html/remap/remap.h...i_file_configuration
Be aware of the warnings here:
linuxcnc.org/docs/2.7/html/remap/remap.h...ap:referto-hal-items
for version 2.6 is the same??
there is not my case .... I have only one but set as io .....Your ,comp sample seems to create two pins with the same name. That probably won't work.
Regards
Giorgio
Please Log in to join the conversation.
k-1 wrote: for version 2.6 is the same??
Yes.
linuxcnc.org/docs/2.6/html/remap/structu...d_sub_ini_features_a
Please Log in to join the conversation.
FEATURES = 28
So I think these is not the real problem .... i suspect that: custom pin is read after call of my custom comp. My custom ccomp is read from custom_hal.hal .... custom_hal.hal is read after myhal.hal..... so when gcode is parse.... my custom comp do not exist..... probabily if can loadrt mycustomcomp in myhal the problem disappear..... tomorrow i try these
Regarfs
Giorgio
Please Log in to join the conversation.
