Advanced Search

This is the call that starts the touch probe routine with those settings.
Here is the actual probing program code.
github.com/LinuxCNC/linuxcnc/blob/2.9/li...f_subprogram.py#L179

First - I have NO idea what I did to fix it... but it is working now. I feel like I 'proved' the Infinite Monkey theorem ...(en.wikipedia.org/wiki/Infinite_monkey_theorem)

That said, when it WASN'T (or being pessimistic about the the future - when it DOESN'T) working, the target you refer to, was appearing but the DRO was not zeroing.

I'm going to do a text comparison of the now working INI and HAL files with the almost working INI and HAL. The almost working files allow me to start the router, move it around and homes without error... except it does not zero the DROs.

Arden

Guessing but it sounds like the component uses global C variables.
Check out 8.4 here linuxcnc.org/docs/html/hal/comp.html#_per_instance_data_storage if relevant.

Hello Gentlmen,

Excuse me, but once again I am facing weird behaviour of custom components file during its programming... 

I need 3 axis there fore I am using a 3pcs of components in the .hal file via count = 3..

I have many IOs stuff because component will communicate with profibus DP driver and it is basicly same as with ethercat but little bit different(other story) But long story short.. when I am homing there we have a custom homing subroutine and modes of driver are changing etc.. issue is comming - I have starting homing with single axis(over internal subroutine), any of them and mode of driver operation is changed over all components==all axis .. what exactly help me right now is have custom names of same component each but it is little bit tricky...

What the behaviour is this overflowing from one to other component in the single instance of lcnc?

Thanks En....