Advanced Search

Ideally you should get no dropped packets at all.

I does sound like a network latency issue.

One thing to do to test is to run say:

sudo chrt 99 ping -i .001 -c 60000 -q 10.10.10.10

(will run for ~1 minute)
and see what the stats are

If there are no more network latency optimizations to do

You can increase the servo thread period (say to 2 ms)

Its also possible to make dropped packets not trigger following errors
(or cause path deviations) by specific hal file modifications
 

The parameters that store the location of the G30 are persistent. Even after rebooting the PC the G30 location will be the same. You only need to do G30.1 once.

Could I get a picture of the edge find button? If you use print screen button on your keyboard it will allow you to copy the screen to the clipboard or save a picture of your screen to your hard drive.

What behavior do you want M6 to do?

Tool change at G30 will allow you to manually change tools away from the part.

1. Add "TOOL_CHANGE_AT_G30=1" to the [EMCIO] portion of your INI file.
2. Power on your machine & home all axis.
3. Jog to the position you want to do manual tool changes at.
4. Type G30.1 into MDI and run it. This will save the current machine position as the location to go to when a tool change is called.
5. Test the machine. It should now rapid to this location when you call M6

linuxcnc.org/docs/2.6/html/gcode/gcode.html#sec:G30-G30_1

Thanks for chiming in. I'm hopeful that this is not the solution I'm after. My goal is to convert these signals within LinuxCNC using something like the BLDC HAL component or something of that nature then spitting out the results via some of my available outputs on my Mesa cards. Surely Hopefully it can be done in HAL and not need an external converter board. These PICO boards would hurt the wallet too much as well, 600USD for 4 that's 850CAD and that's about half of my net worth

#machineShopOnAShoestring

I would recommend your 7i76e option you mentioned in your first post.

Wheezy is far too old to expect stuff to still work. its well past end of life
Whilst the linuxcnc guys have done an amazing job keeping RTAI working for all these years its also past end of life.
Without the Linuxcnc devs, RTAI would not exist today.
Preempt_RT has won the real time wars.
If the default Linuxcnc ISO works reliably for you, it will work with a 7i76e

But like any modern OS, things are more complicated today and there are a number of optimisations I cover here
docs.google.com/document/d/1jeV_4VKzVmOI...diY/edit?usp=sharing
 

there is no comparison. Linuxcnc's QTplasmac, a Mesa 7i96 and a THCAD2 will give you a high end system for almost nothing. Its feature set is very extensive. The difference is that the THC is managed internally by Linuxcnc, not an external THC so the system knows much more about what I'd going on and has much more ability to provide consistent results.
This is quite an old video but it shows what you can do

And the cut recovery features

nothing comes close!

spammer booted

Spammer booted

Problem is that $1 contains a float which bash can't handle, so try:

I believe these lines were the problem:

net tool-prepare-request <= iocontrol.0.tool-prepare
net tool-prepare-confirmed => iocontrol.0.tool-prepared

Not sure if those came from PNCconf, but I commented them out and it seems to have resolved the issue.

Mach 3 is at a point where it is hard to run unless you have a really old version of windows. i used it for years until i hit issues in windows 10. so i would make the switch which i did do
when it comes to plasma and THC Linux with Mesa has probably the cheapest THC solutions out there but I'm in the US so duties and taxes could factor into it to some degree.

Hello PCW,
I checked the hm2_7i76e.0.packet-error-total and got 57 errors about 45 minutes. Is this too much?

I don't understand these packet losses - (my PC is a lenovo ThinkCentre M92p Mini-PC, Intel Core i5-3470T 2.90 GHz 8GB Ram, in the latency Test I get readings as shown in the photos, first at start, Servo 4000, Base 5608, after 30 minutes surfing, coding in Vcode, doing sth else: servo 82040, Base 24542, I set servo thread in the INI file to 1.600.000.
Kernel release 6.1.0-29-rt-amd64, Kernel Version #1 SMP PREEMPT_RT Debian 6.1.123-1 (2025-01-02)
What do you think?

I did the most Latency tips in this thread: forum.linuxcnc.org/38-general-linuxcnc-q...ead-and-irq-affinity - I disabled hyperthreading, power saving, virtualisation, TPM, turbo mode, ACPI, APM, Audio,, kernel isolate core 0 for interrupts - quiet irqaffinity=0 isolcpus=0. I bought a new network controller with RTL_8125 chip,  optimize my network connection with sudo ethtool -C eno1 rx-usecs 0 at any system start. Kernel release 6.1.0-29-rt-amd64, Kernel Version #1 SMP PREEMPT_RT Debian 6.1.123-1 (2025-01-02)

Anyways, I dont have servo motors with encoders wired to the MEsa 7i76e, so I cannot calibrate in live mode. I just set the FF2 to 0.0003 as you said. Same results as yesterday, not often but sometimes i get that motor-0-position errors.
Maybe my PC is too slow for a Linux system? Any suggestions?
Thank you so much for your support!
Hanno
(For some reason, I cannot put photos <1MB in this thread...)

Hi all. I need help with my custom M code I've started to write. I ran into a problem right at the beginning with an "if" statement. My M code should be M105 P100 and it seems the "P" value isn't transfered into the M code. 
​​​The M code always outputs "else" condition so "operand" isn't 100 as expected. 

I also wrote a similar M code with "case" and there the P value is recognised by bash. 

What did I do wrong here?

With a specific bios setting Linuxcnc does open and axis moving smooth, but at start up i get "unexpected realtime delay on task 1.

Sorry for the douple post. Didn't even realize it happened.

As for the problem, I don't think it is an issue with the LinuxCNC images. You are right that it is likely a general problem that would show on a non-LinuxCNC image. I figured I would ask here because you guys seem very knowledgable about not only LinuxCNC, but Linux in general.

That said, I have searched about this problem in general RPi forums and internet searches. I did a lot of that before posting here. There are reports of others having this problem but all of the solutions I have found on this say to go into raspi-config to change things, but the LinuxCNC images don't have raspi-config and menu-config doesn't have the same options. Basically what everything I have found is getting at is forcing the resolution for the login screen to a resolution that works with the monitor.

To be more clear as to what is happening, when the Pi starts to boot the monitor wakes up and pops up a little info window showing what resolution it is being driven at. This little window is a display thing, not a linux thing. Anyway, I can't remember what resolution it starts at with the verbose text, which appears fine, but when it gets to the login screen the little window pops up and shows the driving resolution has changed to 1366x768 @ 60Hz, which gives the skewed image in my previous post. At this point I can type username "cnc", tab to password "cnc" and it takes you to the desktop. Initially the desktop is skewed like the above picture, but you can make stuff out. If I navigate to display settings and set them for 1400x1050 @ 60 Hz the image is normal and everything is fine. If the machine goes to sleep or reboots, once it goes through the login screen again, the resolution is reset to 1366x768. If I can force the login screen rsolution to be 1400x1050 I think all will be good, but I don't know how to do that.