Advanced Search

That's been very successful! Thanks! MY spindle is turning! Just in the wrong direction but that's no problem. I can wire it up so that its CW. The next days I will check how to configure the pendant for spindle control. But today, Iam very happy that the spindle is turning!
Thanks a lot, PCW!
Hanno

hey there

i have been trying to get your guide working 

getting a issue that stops me in my tracks

i just downloaded the latest 2.9.4 iso file.
and i am testing in a virtual machine VM

following your guide halfway through step 3

"then move the NativeCam folder in:
/usr/share/linuxcnc/gladevcp

sudo mv NativeCam /usr/share/linuxcnc/gladevcp

and this fails with the error  mv: cannot stat 'NativeCam' : No such file or directory

everything up to this stage seemed to work

would love any help you have cheers

I am in the process of getting our Mazak VTC16B Retrofit wrapped up. We ended up using dmitry's NYX hardware & IO interface. For config, we took one of the nyx MDS sample configs and adapted it to our I/O. We got everything to work in Axis, now we are trying to switch to GMOCCAPY. 

The issue we are having is that I keep getting an error when loading any sample version (or our own local version) of gmoccapy, I keep getting this error along the lines of "/usr/share/gmoccapy/gmoccapy.glade:5576:1 Duplicate object ID 'chk_use_kb_shortcuts' (previously on line 4179) (8)
 (gmoccapy:62)". I confirmed there is a duplicate block in gmoccapy.glade. I have searched the github issues but can't seem to find anything on if this is a known issue or not. Is this a known issue with Gmoccapy in 2.9.4, or does it appear like I have a corrupted install? Any help would be much appreciated. 

I've attached our machine hardware info, error report, & gmoccapy.glade file.

Thanks!

Hello LinuxCNC community,We are a group of engineering students working on our semester project – building a CNC plasma cutter using LinuxCNC as the control system.Since we are developing the machine from scratch and learning LinuxCNC at the same time, we would greatly appreciate the opportunity to discuss and receive guidance from experienced users. We are particularly interested in understanding potential challenges, key considerations, and best practices for setting up LinuxCNC for our machine.Brief Overview of Our Machine:

• CNC plasma cutter with X, Y, and Z axes
• Z-axis with a ball screw and linear guides
• Floating head with a proximity sensor as a probe input
• Plasma cutter with a voltage divider and THC (Torch Height Control)
• LinuxCNC control, likely using Mesa hardware
• Torch Height Control (THC) integration via Mesa THCAD-2
• Voltage divider (50:1) for plasma voltage feedback
• Probing system for automatic height sensing before cutting

We have already explored various existing solutions, but we would love to hear from those with practical experience in setting up and running a CNC plasma cutter with LinuxCNC.Some key topics we would like input on:

• Choosing the right hardware (drivers, Mesa cards, sensors)
• Configuring LinuxCNC (HAL, INI, probe input, THC integration)
• Common challenges and pitfalls when setting up a plasma cutter
• Best practices for calibration and fine-tuning

If anyone is willing to share their expertise or discuss this with us in more detail, we would greatly appreciate it. A virtual meeting would also be very valuable for us.Thank you in advance for your time and help.Best regards,
Ibrahim Al-N and the 4.semster students at Absalon Kalundborg (Denmark) 

Hello, I'm currently trying to create a handwheel with the Arduino. Now I'm having a problem with the HAL.

I added in my CNC.hal : 

loadusr arduino-connector
net zJog => axis.z.jog-counts <= arduino.counter.0
axis.z.jog-enable = 1
axis.z.jog-scale = 0.1

When I start my CNC I get the error "Pin 'arduino.counter.0' does not exist". When I try this commands in "Halshow" it works fine.

Can someone help me with this?

ok so when i set this all up it was foreign until it wasn't and know its foreign again. I look at the step conf wizard and input the info the best I remembered . I have 3:1 on rack n pinion stepping at 16 motors are 1.8 so input 200 this returns something like 9600 which is way off from what im actually running 2793 on step scale. ran some testing until i had it dialed in to 2778 step scale and now its back to hitting 36" and 72" give or take 1/16 or best a tape measurer can provide. Im guessing in the step conf wizard im entering bad info since the step scale is so far off from my real world example. still not sure why I would be hitting spot on for over a year and than all of a sudden need to make a minor step scale change.

Where can find a skeleton of qss file with all button strings ?

Did you install linuxcnc-ethercat? The error says it is missing lcec, linuxcnc-ethercat.

I never updated my 7i97T firmware, so I won't be of any help with the pinout. If you are worried about not seeing the 7i84 io on that, don't be worried. The 7i84 just shows up in halshow once plugged in.

net spindle.0.on => hm2_7i76e.0.7i76.0.0.spinena

should be

net spindle-enable => hm2_7i76e.0.7i76.0.0.spinena
 

not sure if that is in a linuxcnc update thing or not, i would ask in the general chat maybe. i can confirm in 2.9.3 here shift key does not change the jog speed. so i'm not certain where the disconnect occurred. from some quick research it appears gmoccapy used the shift key to double the default linear velocity setting, but i do not see in linuxcnc where this is a standard and I know i never wrote that functionality into probe basic. in probe basic the only control over the jog speed that is built into the ui is the jog slider.

Latency is basically unimportant with Mesa hardware _if_  you never get timeouts

Also the latency test does not test network latency which is more important for
Ethernet connected cards.

To check network latency:

sudo chrt 99 ping -i .001 -c 60000 -q 10.10.10.10
(will run for ~ 1 minute and print stats)

Assuming the Ethernet card is set for 10.10.10.10

Things that improve network latency:

isolcpus to last CPU, and pinning the Ethernet IRQ to the last CPU

disabling power management, disabling Intel AMT
 

Mon24 13:59: hm2/hm2_7i76e.0: Watchdog has bit! (set the .has-bit pin to False to resume)

Indicates relatively huge network latency (>5 ms if the watchdog setting is the default 5 ms)
That sounds like maybe a power management issue so you might try adding pcie_aspm=off
in your kernel command line.

What is the current kernel command line?
 (cat /proc/cmdline)



 

Is the above line from apt my clue?

The problem that is fixed by the DKMS driver has fairly specific symptoms.

can you run:

sudo chrt 99 ping -i .001 -c 60000 -q 10.10.10.10
 (will run for ~ 1 minute)

and post the stats here

(assuming 10.10.10.10 card address)

Lcvette wrote:

in probe basic? i don't recall ever having a feedoveride via shift. i do not see anything to that effect in the code. was this in a different ui?

It is not a cancellation, it is a speed increase. When you press the keys to move along the axes it moves at a speed of, for example, 360 and when you press the shift key + the movement key it moves at a much higher speed. I have always used that in probe basic and in any other Linuxcnc interface. but since update 2.9.4 it doesn't work for me.