Advanced Search

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.

just draw it out and if it looks right you are on the right track. if the jog directions corresponds to spindle motion through the tables work envelop, you have it correct. where the home origin is is just the defining point of the machine reference from which all other settings are predicated on. so where ever your origin is the min/max travels are from that point to the opposite side of the cartesian coordinate system.

Mine mesa ethernet card has interrupts on cpu0 how can move it to cpu3 isolated for linuxcnc ?

You can temporarily check if this helps:

 

first

chmod +x pinirq.txt

then 

sudo ./pinirq.txt [ethernet_device_name_]

Where [ethernet_device_name] is the name of the Ethernet device connected to the 7I96S
(probably eth0, eno1 enp0s25 or similar)
 

the installation is pretty well locked down, the issues come from configuration setup. if you are starting from an existing gmoccapy config you will need to use the docs for machine configuration setup to guide your transition. always start with testing to see if the sim works as expected, if it does but you have issues with your machine config its a good indicator you missed some items.

the required PB config bits are NOT optional, do NOT skip the reading as there are things in the reading that are required to be done. its a short one pager so just be diligent.

if using gmoccapy and you have ots of custom hal files and such be sure you remove anything that may conflict with probe basic in hal. if you miss one you will get an error telling you the conflict.

thre can be only one post gui hal call in the ini. so if you have anything you need to keep from your existing post gui hal file, you will want to consolidate the items into the probe basic post gui hal file or read the linuxcnc docs on how to call any other post gui hal files from within the main PGHF.

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?