ColorCNC Colorlight 5A-75E/5A-75B as FPGA controller board

Hello Peter
As I wrote earlier, I just have the motor connected. And jerks on the screen coincide with jerks on the engine.
I've tried different GUIs: gmoccapy, axis, qtvcp axis. Everywhere the behavior is the same.
Moreover, if I use the Fabio driver and firmware, everything moves smoothly, without jerks, with any GUI, qtdragon also tested.

Also with the Fabio driver, the CPU usage is much less.
On a 32-bit system, this is noticeably even stronger.

Update: After 11 runs of the 3D_Chips program on a 32 bit system, the driver went into the same uncontrolled movement as in the 64-bit version.

Hi, about packet loss behavior, you can try to raise the value of Lcnc.00.tx-max-retries, this Is the Number of missing packets that Will trigger the board self disabling. Default value Is 5, you could set it to some value higher than timeout, for example 100.

Update: Due to complaints on speed and stability, I've made some changes in the stepgen algorithm (aims at solving both uncommanded / wrong movement and jerky motion). Also added now timing on all components to find out which function causes a high CPU usage. Tomorrow I'll be able to test it on my FPGA whether it works and will share the timing results. Feel free to test it earlier.

muvideo wrote:

Hi, about packet loss behavior, you can try to raise the value of Lcnc.00.tx-max-retries, this Is the Number of missing packets that Will trigger the board self disabling. Default value Is 5, you could set it to some value higher than timeout, for example 100.

Ok, i change it to 100000.
Result the same
I try to remove cable from board for 0.1-0.2 sec
100000 retries for 10 sec, i'm right?

100000 should last about 100s before reset, but I've never timed this, I was more interested in the number of consecutive Lost packets. In this scenario the watchdog will bite for sure way before the 100s, depending in how it is configured.
I've noticed that if I disconnect briefly the cable, the connection Is fully restored only after several seconds, and I dont know why.
Maybe in the next iteration I should introduce better error messages so that the reset reason will be more clear.
My machine Is now fully cabled, I'll soon be able to test the sw on actual hardware.

Video