Lost Step Counter

I believe that when I tried to use your code I was so much not understanding what I was doing, I may have introduced mistakes.
For instance, I didn't know the correct syntax for python. I referred to what I knew from "C", where "spaces" are not important.
And as was understanding a bit more , I made few experiences, and finally wanted to know what I was doing in my linuxcnc program...
Thank you again

Hi all, I'm using AndyPugh's code from the first page of this thread unmodified except replacing "axis" with "joint".



I'm loading 4 counts of miss_step, it loads as a module and all four counts have created the pins:

etc for joints 0 through 3.

This works and I can see them in Halshow. But as soon as I add the following lines to my HAL, LinuxCNC won't launch.

The error I get on launch is:

Any ideas? Hoping to get this working to troubleshoot some issues I've been having. Thanks for any help!

(INI/HAl attached)

The hal links are in your "post GUI" ?

Ok, looks like that part is resolved. Move AndyPugh's:

lines to being in the postgui HAL file.

The error is now that the pin "joint.0.motor-pos-cmd" is already connected to the signal 'x-pos-cmd' which is part of my main HAL setup. Is there a way to do this using the "x-pos-cmd" signal, my understanding being that once the signal is set up, we can use it many times?

If I change it to this:

then the error I get is that x-pos-cmd isn't a pin.

Thanks, gents. Much appreciated. I got this going, I just view them with Halmeter, and it's helped me diagnose some step timing issues.

my version of miss_step script:
And the connections in my custom_postgui.hal file:

So, I have spent a lot of time trying to get the original code to work using gmoccapy. I have it working but with unexpected results.

When I home the machine, I get the message box which shows the value in X. Perfect.

I thought, great, now I can load some gcode, run it and see which axis is having problems.

When I move the gantry to set up the 0,0,0 points, the machine takes off on it's own. A miss_step message box
pops up with some random number.

I can't even stop the jog unless I hit the e stop.

I thought, maybe this is a compatibility issue with gmoccapy. Maybe not.

Here is my code:

miss_step file:

#!/usr/bin/python
import hal, time
import sys
from Tkinter import *
import tkMessageBox

root = Tk()
root.withdraw()
h = hal.component("miss_step")

count = 1
for opt in sys.argv[1:]:
(dummy, count) = opt.split("=")
if dummy != "count":
count = 1

pins = []
for i in range(int(count)):
p1 = "axis.%i.pos-cmd" %i
p2 = "axis.%i.motor-pos-cmd" %i
d = 0
t = [p1, p2, d]
pins.append(t)
h.newpin(p1, hal.HAL_FLOAT, hal.HAL_IN)
h.newpin(p2, hal.HAL_FLOAT, hal.HAL_IN)

h.ready()
try:
flag = False
while 1:
time.sleep (1)
for t in pins:
if h[t[0]]-h[t[1]] != t[2]:
flag = True
t[2] = h[t[0]]-h[t[1]]
if flag == True:
flag = False
message = ""
for t in pins:
message = message + t[0] + " = %f\n"%t[2]
ret = tkMessageBox._show("Homing Position Differs",
message,
tkMessageBox.QUESTION, tkMessageBox.OK)
root.update()
except KeyboardInterrupt:
raise SystemExit

---

Here is my custom_postgui.hal code:

# -- AndyPugh zero checker connections
#net check0 miss_step.axis.0.pos-cmd axis.x.pos-cmd
#net Xpos miss_step.axis.0.motor-pos-cmd

---

Here is the custom.hal code:

#loadusr -W /home/jeff/Desktop/Mauer-Mill/miss_step count=3

---

I not only cannot get this code to work without taking over the machine during jogs, but wonder if
there is a way to monitor the two Y joints? I don't have any idea how to do that. It is there that I
am having problems. X and Z are fine. I can't keep the two Y's on my gantry machine to stay in sync.

Thanks much

I made a reply in the other thread, mentioning you may need to look at joints rather axes (plural of axis)