Advanced Search

What does it do when you try adjust the speed? Is it a VFD you are using? What is the speed input to the vfd pwm or 0-10v analog. Have you the VFD wired correctly ?

I'm a n00b, straight from UGS, so I don't know if that will be an issue. I anticipate using the pendant during setup, so being on the "Manual Control" window might not be a problem.

What's a solution to the focus problem?

Yes PCW, is the same Realtek with dkms driver for fix latency.
Maybe I'm asking the wrong question: is it really necessary to do the test with YouTube?

When you get an error, what does:

halcmd show param *.tmax

(typed in a terminal)

show?



 

OK, I figured out a way to select from the GUI list of jog increments using a single keystroke.

There's more than meets the eye. You've got to pull in some GUI elements that are only apparent if you read through axis.py. It's not good enough to set the increment because the GUI will re-set it based on the dropdown.

import linuxcnc
import tkinter
import hal

def set_jog_inc_rc( event, index ):
global comp, jogincr_index_last

root_window.call( widgets.jogincr._w, "select", index )
jogincr = widgets.jogincr.get()
print( f"setting jog increment to {jogincr} inch " )
comp = float( jogincr.translate(str.maketrans("", "", string.ascii_letters)) ) # remove "in"


root_window.bind( "<e>", lambda event: set_jog_inc_rc( event, 5 ) )
root_window.bind( "<f>", lambda event: set_jog_inc_rc( event, 3 ) )
root_window.bind( "<g>", lambda event: set_jog_inc_rc( event, 1 ) )

Murphy wrote:

Try deleting [spindle0]

setp scale-rpm.gain .02
put that in instead
 

 

At least that gets me to the next error - ./remora-ec500.hal:127: Pin 'remora.output.02' was already linked to signal 'spindle-cw'

line 127 is - net mist    remora.output.02     => iocontrol.0.coolant-mist

Edit: I figured out that the pin for the spindle was wrong, it should of been .00 not .02. Now I have the spindle turning on. First time I have seen the spindle run sense the day the machine shipped. No speed control and I am unsure how to fix that, but at least I am making progress. At this rate I might even see the mill actually working before fall.

One thing to note is keyboard shortcuts only work when the Axis window has focus.

JT

PCW wrote:

Do you have a Ethernet connected motion device? 
If so, the latency test is relatively useless for determining the actual
LinuxCNC latency.
A simple ping test is much more informative:
sudo chrt 99 ping -i .001 -q -c 60000 [Device_IP]
(will run 1 minute and print out timing statistics)
Where device _IP is the IP address of your Ethernet motion control interface.

Yes PCW, is the same Realtek with dkms driver for fix latency.
Maybe I'm asking the wrong question: is it really necessary to do the test with YouTube?