Advanced Search

Do you need the Realtek card?

Physically remove all unneeded hardware.

Try disabling all power-saving features you can.

./remove_all

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 ) )

True.

Also, make sure the function keys don't invoke some system function.

Pressing [R] should run program, but does nothing for me.

The only shortcuts that work for me are:

[Home] -> Home current axis.
[End] -> Touch-off current axis.
[Up Arrow], [Down Arrow] -> Jog and select Y-axis.

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.

Did ya set the governor to performance?

Try to remove unnecessary hardware.

blacklist kernel modules of unneeded devices.

Mask and disable unneeded services.

Ensure you have plenty of RAM; disk I/O should be avoided as much as possible.

Caching and buffering will reduce disk I/O and latency, but requires ample free RAM.

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?

tommylight wrote:

Do you get latency warnings when you run LinuxCNC?

Yes, at start

tommylight wrote:

Are you still using the same PC discussed here on several topics?

Yes i change NVIDIA with ATI and is better, but error of junction with "Community test youtube video" still occurs.

tommylight wrote:

Why do you keep doing the same things and expect different results? Stressing the system beyond it's limits will always fail.
Change the graphic card, get a used one for AMD, or get a used PC.

www.youtube.com/shorts/mWCeSrF2TUM
Whith stress test and 100 GLXGEARS the work go at end with machine not responsive! But one youtube video give me junction error.

tommylight wrote:

You had good latency at one point in time, so what happened?

Yes is good youtube video junction error still occurs.

#################################################
P.S. the forum have some problem e need fix.
EExamble Edit a quote quote all message and Code.
#################################################

Try deleting [spindle0]

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

A link to that PC would be great. I'd love to see those buttons.

cakeslob wrote:

thanks vp, that will save us a lot of work. we need to archive this shit for the repo or something

darkpheonix - that is good to hear

spyder - this is my WIP remora spindle template (no encoder edition). murphy is also using it. some might be duplicate to what you have now

#########################################################################################
# Remora Spindle hal remora_spindle.hal
#
# this hal file includes the following
# - connecting Remora outputs to LinuxCNC motion spindle.0 enable/direction
# - connecting spindle signals to LinuxCNC motion spindle.0 pins
# - converting the LinuxCNC motion spindle.0.speed-out-abs to signal with scale
# - connecting converted LinuxCNC motion spindle.0.speed-out-abs to Remora PWM
#
#########################################################################################

# conenct LinuxCNC motion spindle.0 on/enable to remora output 01
net spindle-on <= spindle.0.on => remora.output.01
# conenct LinuxCNC motion spindle.0 direction to remora output 02
net spindle-cw <= spindle.0.forward => remora.output.02

# connect spindle signals to LinuxCNC motion spindle.0
net spindle-cmd-rpm <= spindle.0.speed-out
net spindle-cmd-rps <= spindle.0.speed-out-rps
net spindle-cmd-rps-abs <= spindle.0.speed-out-rps-abs
net spindle-at-speed => spindle.0.at-speed

### Connect and configure spindle PWM/0-10v signal ###
###########################################################
# Spindle PWM 0-100 control
# converting the LinuxCNC spindle speed output
# into a useable output signal for our remora pwm component
# - for pwm the math is 100/ [MAX SPINDLE RPM] = gain
# 100/(5000rpm) = .02 , the gain is 0.02
###########################################################

# load a linuxCNC scale module,
loadrt scale names=scale_to_rpm.0,scale-rpm
addf scale-rpm servo-thread
# configure spindle rpm to pwm
# pwm 100 / max rpm = gain number
#setp scale-rpm.gain 0.02 # 100/ rpm (5000) = .02
setp scale-rpm.gain [SPINDLE_0]RPM_GAIN # 100/ rpm (5000) = .02
# connect the LinuxCNC motion spindle.0 speed-out-abs to the pwm scale
net spindle-speed-scale spindle.0.speed-out-abs => scale-rpm.in
# connect pwm scale output to remora spindle pwm SP.0
net spindle-speed-abs scale-rpm.out => remora.SP.0


# Manual toolchange

loadusr -W hal_manualtoolchange
net tool-change iocontrol.0.tool-change => hal_manualtoolchange.change
net tool-changed iocontrol.0.tool-changed <= hal_manualtoolchange.changed
net tool-number iocontrol.0.tool-prep-number => hal_manualtoolchange.number
net tool-prepare-loopback iocontrol.0.tool-prepare => iocontrol.0.tool-prepared

 

I tried this spindle config and I get the following error - ./remora-ec500.hal:79: Ini variable '[SPINDLE_0]RPM_GAIN' not found. Would you or anyone else know what might be wrong and how to fix it?

Beware of CaPs lOcK.

My AXIS window does not actually obey all the shortcuts listed in the "Quick Reference" pane.

It's weird.