Advanced Search

Found the solution by motivating tommylight to take a detailed look at it , spent him some hours of his night life Jokes away he is a master.
Thank you Tommy

Oh good, someone else replied about the RPI, i was going to go postal!
For 35$ it is magnificent, even 50$ is OK mostly, not a single cent more.
For 100-120$ i can get old Lenovo X1 Yoga, full PC with touchscreen, battery, and much more powerful than RPI.
Also:
PC: download ISO, install ISO, reboot, copy config, run machine!
RPI: download IMG, no not that one the other one for V5 with 4GB not with 8GB or 2GB, write image, boot.... for a while, nothing works, fix wifi, fix power options, fix servo period, use raspiconfig, edit config.txt, fix whatever Unknown mentioned, reboot 20 times, find another power supply, find a cooler to glue to it, find a faster SD card, it crashed ... boot loop, start over. Oh hell no, never again.

As always, great starting points. I'm waiting for my EL2502, although the EL2521 seems to work just fine. Thanks, Corbett and Rodw.

The way I understand it, when I command a rapid move, the Mesacard wants to give it the full 10V, leading to a really rapid move on the motor, way to fast for what linuxcnc anticipated, and that will cause some issues.

 
That's not actually what happens. With velocity mode servos, tuning LinuxCNCs PID FF1 term is what mainly
determines the output voltage correspondence to requested velocity. If FF1 is tuned properly, the analog
output voltage will generate very close to the correct velocity in the drives. Any small per cycle or
cumulative errors are corrected by the P term position feedback.

One way to get a good initial value for FF1 is to set the analog scaling so it is equal to machine units per second
at 10V. In this case FF1==1.000