Advanced Search

sorry, my bad, you should remove that -q in the command which makes your ping output quiet. try this:
sudo chrt 99 ping -i 0.001 10.10.10.10 -c 1800000 | grep -v time=0.

btw. are you still getting that error finishing read?

You could use an ngc remap to create a gcode for setting numbered parameters to the required offset values and another ngc remap to read the parameters and set one of the built in offset system. Arrange the parameters in blocks of 10, that way a 'p' word value can easily be used to reference which block to read/store the (x,y,z,..) offset values from/to.

Maybe you can write your own macro to load the offsets from a file

Use python to remap an unused Gcode to get the required offset values from a file and set one of the nine built in offset systems. Takes a bit more effort than the above solution.

I've wondered the same thing a few times. Wouldn't mind digging into code if no one has a solution.

thank you, that is very helpful.
By running "sudo lspci -v", I could confirm that the right driver is used (see attachment).

 

But when I try to run the modified ping command, the result is just the same as before. It doesnt filter out any packets over 1ms... again, see screenshot.
I guess the command has to be modified a bit...
 
Regards and thank you
Sebastian

I guess we had a power spike - I know we lost power because the computer had rebooted. But the message was about not being able to find a boot device. After MUCH futzing around - I THINK I may have had damaged my primary SATA port (weird). I could boot the system from a USB and view the drive contents, but I couldn't figure out how to rebuild the boot drive to boot it. I had made backups of the config files 'just in case' (I'm usually a much bigger risk taker and don't bother) and managed to pull them off the drive before I proceeded with a 'nuke and a repave'. When I couldn't get a new system laid down - I thought it WAS the hard drive then. I had an SSD kicking around that I put in and... same problem. That lead me to try a different SATA port and voila - new system installed. 

Within this new SSD based system I did the latency test (I was seeing a number like 71,000?) and then ran StepConf just to create the files. Once I had the files in place - I overwrote them with my backups and Bob's yer Uncle - my system was up and running. EXCEPT - when I try the fast move using the SHIFT key - all 3 axes move a random, short distance and then there is a sound like it's moving - but it's not. 

I tried to modify the MAX_ACCELERATION  in both the [AXOIS_X] and the [JOINT 0] sections of the .ini. But changing those resulted in a non-start on LinuxCNC. Even as I type this - I THINK the issue might be the stepper timing and not the acceleration. But I'm hoping that the brain trust on LinuxCNC here in the forums can point me in the right direction.

I've searching the online documentation and the 362 page Integrators manual - but there is really SO much underlying knowledge of the workings of Steppers, Servos and 'integration' terminology that just baffles me. I'm still plugging away!

Thanks in advance...

I tested your attached files (including install attached cia402, cia402_homecomp files, successfully) in current LinuxCNC.
with LC10E - EEPROM version V1.04

Power on is OK, Jog each axis is OK,
But X axis cannot stop when I pressed [Home All] button.

In Halshow window, cia402.0.opmode = 8 always.

What am I missing ?
Does anyone know any update for it ?

after installing the driver run this to check that it is the right one being used:
sudo lspci -v
under Realtek controller check Kernel driver in use, it should be r8168. (see attached screenshot)

to avoid problems i suggest to blacklist the r6169 driver completely in grub by adding: modprobe.blacklist=r8169

or, since your pc looks similar to mine you can add the whole my line to /etc/default/grub which through trial and error i found the most stable:

GRUB_CMDLINE_LINUX="irqaffinity=0-1 kthread_cpus=0-1 isolcpus=domain,managed_irq,2-3 rcu_nocb_poll pcie_aspm=off r8168.aspm=0 r8168.eee_enable=0 modprobe.blacklist=r8169,mei_txe"

don't worry it will not kill your pc  it just rebalance your cores to do different things. 

dont forget to run "sudo update-grub" to update grub configuration otherwise you won't see any changes after restart.

also check sudo dmesg for any errors during boot.

having 1.2ms ping once in a blue moon won't kill you. i suggest to add "grep -v time=0." to see how many actual pings you got over 1ms.

i normally run something like this:

sudo chrt 99 ping -i 0.001 -q 10.10.10.10 -c 1800000 | grep -v time=0. 

this will run ping for 30 minutes with 1ms pings and only show you the pings that took longer then 0.999 ms.

if you see only one or two 1.2 ms in 30 minutes it is not a problem, 8ms is super bad though. 

have fun!

I wonder how the were inserted? Thank You , I will try it tommorrow.

[TRAJ}Axis XAxis YDelete .ini from those lines.

 
This is the .ini that I modified while working on the Z Axis Homing . 

Bumped into this today:
- Linux is a tool you use to extract value from your hardware.
- Windows is a tool Microsoft uses to extract value from you
-
Original comment here

User name @neilbrideau8520

Go give the man some likes.

Were are the error files located ? var/ Error ? This ubuntu is very unfamiliar to me .

Thx Peter. Really appreciate your help. Last question …. Can you tell if my realtek nic is using the dkms driver or not? I attached the output of a script that you posted somewhere.Like I said in the first posting, I didn’t know that Linux headers might have been necessary when I installed dkms.  

Might be usable with a 2 ms servo thread.

I would check how LinuxCNC runs now

 

Alright. I applied that command in the grub configurator, rebooted and ran the pinIRQ script again.
ping times look much better (dropped from 8 to 1.2), but I am still too high... right?

first

sudo ./pinirq.txt enp1s0
Cores: 4
Old CPU Mask: f
Set device enp1s0 IRQ 121 CPU mask to 8

then

cnc@linuxcnc:~/gcodes$ sudo chrt 99 ping -i .001 -q 10.10.10.10
PING 10.10.10.10 (10.10.10.10) 56(84) bytes of data.
^C
--- 10.10.10.10 ping statistics ---
142832 packets transmitted, 142831 received, 0.000700123% packet loss, time 143400ms
rtt min/avg/max/mdev = 0.056/0.108/1.211/0.035 ms