Advanced Search

I need to set the jog increment to a specific value and bind it to a key, let's say 'e'.  I'm using the Axis GUI so the key binding is done like this in .axisrc, which works:

root_window.bind( "<e>", set_jog_inc_precise )

The contents of the function set_jog_inc_precise is the issue.  I've tried the following

vars.jog.increment.set( "0.001" )

linuxcnc.command().jog( linuxcnc.JOG_INCREMENT, True, 0, 10, 0.001 )

j = root_window.nametowidget( ".pane.top.jogspeed.jogincrement")
j.set( "0.001" )

root_window.tk.eval( "set jogincrement 0.001" )
commands.set_jog_increments()

Only the second (linuxcnc.command()...) had an effect.  It actually jogged the axis, when I was watching the DRO.  So when I press "e" it would jog X 0.001 in the positive direction but when I used the arrow, it jogged X based on the drop-down menu in the Manual Control tab.

The backstory is that I have a pendant that isn't supported and have managed to map it from /dev/hidraw<n> to a virtual keyboard.  Most of the buttons work but the relative adjustment of the jog increment (i, I) is not the best because the dial on the pendant is labeled and it's easy to get out of sync. 

I've spent a few hours trying to get this working, reviewed the documentation for the python linuxcnc module, and even asked a few chatbots.  What am I doing wrong?

UPDATE:
After i stopped the servo from spinning on it´s own I went on to setup the limits and the X-Axis ran away like carzy, you´d give 0,05V on to the servo drive and it would react with max speed. I was confused since everything worked fine with 0,02V.
From the other axis i knew it should behave diffrent and should have a slow smooth motion with 0,5V

I´ve swapped the drives with each other, same
I´ve swapped the driver with a new one, same
I´ve checked the wiring, everything on the correct terminal.
I´ve checked the Tacho signal: 0V - THATS IT. The servodrive trys to keep up with the command, but since the Servo isn´t moving it gives even more power until it goes into fault or the axis crashes.

So i was sure the servo is cooked. I was already checking the sister machine for a spare Servo, already loosening the screws and was kinda like:
"oh let´s first remove the broken one".

As i pulled the cables i noticed the cable to the Tacho was ripped out INSIDE the screw thingy where the cable enters the housing. I repaired the wiring and voilá, servo works as expected.

So long story short, the previous owner already had the ripped wire and tried to fix it with tuning the drive, just like i did. The real problem was the severed cable to the tacho.

I've just heard back from the team at Leadshine.

It looks like the EL7 drives have a 0.0625ms delay on the encoder outputs.

Know people have had an issue with the 5ms delay on the DMM drives. Anyone think this might be an issue?

I've just enquired regarding any delay from analog velocity signal to drive reaction, which I assume would effect tuning as well.

Thanks,

J

Hey,
I'm currently working on configuring different setups using various Mesa boards (7i96S and 7i95T).
For creating the configurations, I’ve been using either the pncconf Wizard or Mesact. Unfortunately, neither tool seems to produce fully working configurations for my particular setup.That’s why I’m now trying to better understand which HAL functions are actually necessary.
Specifically, I’d like to learn what the different pins mean and how they should be connected in a way that makes sense.Could you point me toward some resources or documentation that would help me learn these basics?

Thanks a lot for your time!

Thank you very much - zz912.
Your last change is now working.
Regards, Hermann