Physical feed override parallel port

Hello Todd

So your information was essential and both were partially successful, LinuxCNC opened normally but the feed is locked at zero, the machine does not move in MDI or Automatic.  I opened the HAL Configuration (attached) the “halui.feed-override.count-enable” the scale is working correctly.  I noticed that “halui.feed-override.scale” and “halui.feed-override.value” always remains at zero this happens in both options in romi308(foincr) and romi308(mux16).

Hi Andy

Yes I tested, for example my case is connected to inputs 10,11,12 and 13 of parallel port 1 (0).

net fo-incr-a   <= parport.0.pin-10-in-not  <= classicladder.0.in-20
net fo-incr-b   <= parport.0.pin-10-in-not  <= classicladder.0.in-21
net fo-incr-c   <= parport.0.pin-10-in-not  <= classicladder.0.in-22
net fo-incr-d   <= parport.0.pin-10-in-not  <= classicladder.0.in-23

As much as I did this test I thought it would not use the classicladder signal.
 

Interesting that I tested two options (foincr: “loadrt mux16 names=foincr”, “addf foincr servo-thread”) and (mux16: “loadrt mux16 count=1”, “addf mux16.0 servo-thread”) both opened normally no presented errors.  Only the feed bar in the Gmoccapy GUI is stuck at zero in both.  Is there any other information in the ini, pref.Hal, postgui.hal, or another file I need to include something?

i would try to work through each part of the problem to see where the error is.

use halmeter or halshow to look at:

fo-incr-a -> does it change state when you move your selector?

if yes then:
mux16.1.out-s -> does it change when you move the selector?

if yes then:
halui.feed-override.counts -> does it change as you move the selector?

That's a good start anyways.

So friends I'm quite lost, I reached a point I couldn't evolve my problem anymore….  I made three videos if anyone can identify something I can't.  One is the Falcon lathe I put three external keys (feed, rapid and spindle) they are working perfectly, the other two videos is the same Romi machine plus one with hal foincr and another mux16….


drive.google.com/file/d/1Lp88-cDHsK8svB_...Ey/view?usp=drivesdk

drive.google.com/file/d/1s8wISVcA-EnsIdh...PJ/view?usp=drivesdk

drive.google.com/file/d/11ejh6s2K0pSrUkU...09/view?usp=drivesdk

I think the problem might lie somewhere with the hal pin "halui.feed-override.scale". In your videos the working config the scale is set to 0.01. But in the videos of the problem configs hal show is showing that this value is set to 0, even though your hal file has a line that says "setp halui.feed-override.scale .01". My suspicion is that you may have another hal file in your config that either has another "setp halui.feed-override.scale" or has that pin netted to something and is resetting that pin's value back to zero.

For a long time and fatigue, but with your help I thank you, because today I solved it.  The cause of all this was the handle WHB04, causing conflict…