Advanced Search

I think it was the wording "reset". To actually reset a 7I95T
you need to cycle the power (or issue a reset command but
LinuxCNC never does this)

If this is a real time error, it may be that the servo thread period
needs to be increased to say 2 ms as 1 ms is marginal on a RPI4.

Hi everyone,
I recently ran a benchmark test on my LinuxCNC setup to measure the data request speed, and I thought I’d share the results with you all. I’d love to hear your thoughts or any suggestions for further optimization!
The setup was connected as follows: [Linux 4.19.0-27-rt-amd (core i5) PC (3 byte send 5 byte receive)] -> [switch (TL-SG1005D)] -> [W5100S-Pico]. This was a non-realtime throughput measurement, and the result I got was a stable 2500 requests/second, which I think is pretty solid. I’m curious about your experiences—has anyone else done similar benchmarks, and what do you think of this performance?

Thanks in advance for your input!

 

If you ever set the update rate to 0, you can never change it again or the driver will hang (this is a known bug)

Hi shellcrash,
I'm trying to get an X6 1090T working with a biostar A880GZ motherboard (which I think is just one generation newer). I'm so far unable to get as low a jitter as you got, and I was wondering if you remembered any bios, kernel, etc settings that enabled you to get such low jitter numbers.


I've only gotten below 40us jitter so far: forum.linuxcnc.org/38-general-linuxcnc-q...it-of-jitter?start=0

Hallo,

ich habe mich entschlossen meine Systeme mal auf neuen Stand zu bringen. Ich habe dazu LinuxCNC 2.9.4 parallel installiert und möchte nun die Konfiguration erstellen. Die alte Konfiguration von der Version 2.8.4 (mit gmoccapy und einigen Macros und WHB04B-4andrad ) funktioniert so natürlich nicht. Was kann ich von der alten Konfiguration weiter verwenden, was muss ich anpassen und was muss neu erstellt werden? 

Danke für eure Hilfe.

Norbert


 

Hi Grotius,

this is awsome, good work.
Regarding the ringbuffer, did you already try a code with lots of tiny segments? In your example there is propably plenty of time between the g code lines to calculate the next clothoid. With lots of smaller sections we could test if it works in general.
If the calculation takes 25ms then running a g code with F6000 with sections shorter than 2.5mm might already be the limit.
Would be an interesting test what happens with a modern g code with lots of tiny moves.

Best regards,
Fabian