Advanced Search

Actually I think linuxcnc has a problem where files are accessed on disk for the entire time the gcode is running. I have recently copied new ngc files onto the machine while the interpreter is running and things break.

I do understand that this is my fault, but it should probably get locking/tempfile/something safety check to make sure the interpreter doesn't do anything dangerous as a result of replacing an ngc file on disk while it is running.

I'll take a peek at firmware updates, but the machine is very stable with the in-tree nic driver, idle=poll, and a dedicated cpu for lcnc. All warnings have silenced and I can even record video from two cameras concurrently while lcnc is running with no latency issues.

There _is_ a way to test for signals with just one pin
in hal but I have forgotten how this is done...

PCW wrote:

Looks like the error is a signal name mismatch:

pncconf uses net machine-is-on   but the XHC file uses net machine.is-on  

Twice i searched for typos and missed this... i need thicker glasses, or more sleep

UGH!!!
You are 100% correct. I did not spot that variance (glasses???). OK! I can confirm hal works as expected after the edit. I am now going to go through the other errors I saw initially - I bet they are the same mismatches.
Thanks!

Looks like the error is a signal name mismatch:

pncconf uses net machine-is-on   but the XHC file uses net machine.is-on  

I agree with you - it didn't make sense to me either based on my [admittedly limited] knowledge. I will do some more testing around this and document what I find.

Is it possible to see a log of what hal commands are actually executed in order on start? That might illuminate the issue.

That doesn't make any sense.

 It makes no difference when or from where a net command is
executed as long as the connected pins are present. 
(at least in any version of LinuxCNC I've used)


 

Sounds like maybe the  the issue is the common ground
between encoders (because you are sharing the encoder
output from the new drive with the drive and the 7I77)

Have you tried a common mode choke on the new drives
encoder connection to the 7I77?

I agree they *should* be identicial... weird thing is it didn't work out that way. It simply refused to work unless I put it all in the latter xhc_whb04b_6.hal file. Could be a version bug, who knows.

having

net machine.is-on halui.machine.is-on
in GantryMill.hal

and

net machine.is-on whb.halui.machine.is-on
in xhc_whb04b_6.hal

would be identical

Looks like you figured out that setp isn't to be used on a line where you are connecting a signal, that is net.

Edit: nevermind, I se what you were drying to do, just use net on that line, and put a signal name in front. You don't setp a value of one pin to another, you net them together with a signal so the input pin takes the value of the output pin.

setp is for pins/parameters that you don't need to connect to anything and just want to set a static value to.

Hmmm... My ini shows this:

[HAL]
HALUI = halui
HALFILE = GantryMill.hal
HALFILE = custom.hal
HALFILE = toolchanger.hal
HALFILE = xhc_whb04b_6.hal
POSTGUI_HALFILE = gmoccapy_postgui.hal
POSTGUI_HALFILE = custom_postgui.hal
SHUTDOWN = shutdown.hal

In the end, because i used pncconf to generate the GantryMill.hal file I put this in my xhc_whb04b_6.hal file:

unlinkp halui.machine.is-on
net machine.is-on whb.halui.machine.is-on halui.machine.is-on

That seems to work. Jog dial works. Need to tweak the button functions, but I'll sort that out. Cheers!

Sounds like the whb hal (postgiu.hal?) file is not linked-in

(I usually test this kind of issue by inserting a deliberate error in the file
to make sure its being used)

I have several different programs that I want to connect each to an input pin so that when that pin is activated, the corresponding GCODE file will be executed.
Is such a thing possible?