Advanced Search

Yes, I would test at say a 100 Hz update rate.

I was just checking the 0.1 Hz update rate, as you said
it did not work, but it seems OK.

So if you can change the update rate from 0 to some positive number
while running and it keeps working, that indicates that at least one
divide by zero issue has been fixed.

The bad data error you have may be unrelated but the divide by zero fix
seems to have solved the very similar error finnengineering had with the stepgens


 

Yes works but it is practically unusable with 10sec intervals
also the problem of random data to encoder input it is unknown if resolves
completely or just happens in these long intervals and it is difficult to detect..
With update-hz set to 0.05 does not work.

i do not post it but i compiled my benchmark to windows also with nearly same results, so the pico is the bottleneck here.

i dont think all functions are able to handled with one pico, i have more time now for testing because the first PCB-s are only shipped on mar.23 and the components is in the coming week.

actually not using PIO now, the UDP data transfer runs on core0 and all io handling runs on the second core, i use the W5100s-evb-pico for the project with the wiznet library (using arduino ide) (for PIO testing i make a frequency generator (later stepgen) and send velocity from 1 of linuxcnc joint to it, it makes 2Mhz signal but dont have a fancy scope to find its jittering. Shock settled on my face, and a small smile appeared at the corner of my mouth when I saw the signal on the scope.

Looks promising. Many LinuxCNC hardware interfaces run at 1kHz, and that works fine for most purposes.
Are you using the PIOs to handle the communications? Maybe there are gains to be made there?

Does the Pi-Pico handle UDP natively?

With the new processor, latency seems better. But the test started without internet (I had a problem with the internet).

 

But it seems the main problem is the communication with the mesa card. Please see the attached picture.
I get this as soon as I start LinuxCNC. Why are ping times good, but in LinuxCNC it is so slow?

 

A quick way to verify that you have fixed the divide by 0 issue
is to set the update rate to 0 in say halshow, and the set it back to say 1
If communication continues at 1 Hz, then the issue has been fixed.

(I say this because at least in a RIP installation the
mesa_modbus.c.tmpl file used is not the one in the
LinuxCNC sources)

Delving into this in more detail, the AtoD conversion doesn't look very stable.
My digital voltmeter reads on a nominal mid position of XY feed pot a steady, non varying 1.666v
the 7i73 analog0 numbers flicker, not regularly, like on a timer, but with a fast random up and down.. With a slow-mo video
I actually get readings 1.565882,1.578824, 1.591756 the differences are exactly one bit. (3.3volts, 255 bits, ie 0.012941 volts per bit)
When the servos are on, then this flicker is actually audible.
Can you suggest anything that I can do to improve this please?
Thanks

i make another test this time with raspberry pi4 (4gb)
 

I have some Sunix PCI-E cards that work properly.
forum.linuxcnc.org/18-computer/54368-pci...ut-of-the-box#313942

To normal people, those numbers seem very far fetched as there is no pricing info for anything like that.
As Americans say: if you have to ask for the price, you can not afford it.
And when you do ask, be sitting with a glass of cold water in hand and 911 on speed dial.
Only when you have invoices in hand for such stuff, you start believing (coupled with the headache it induces)
See if you can find pricing for commercial license 5 axis CAM and report back here, if you can!

We (mods and admins) get e-mail notifications for every post, always, so from 50 to over 100 daily.

I think that you should enable HPC (High Performance Computing) to prevent it from lowering the cpu frequency. Possibly also core performance boost. And to see if the kernel parameter works: cat /sys/devices/system/cpu/smt/active

my only contact is the sales lady