Hi, LinuxCNC needs to know what the max frequency of the stepgen is capable of so it can limit the frequency command. Also, the traj max velocity should be lower than the joint max velocity so that the joint can catch up the following error.
Hey is it possible to use FlexIO instead on the step and dir pins?
I was doing some reading online saying FlexIO is more stable then edma? Just wondering if the pins are the correct ones to use FlexIO? I cant find too much documentation on it
working on a configuration inside a virtual machine, but for some reason with the card the f-error literally just climbs and climbs no matter what I do. my network card latency is 1ms +- 0.2ms and thread jitter is about the same as my other computer maybe a little worse, what i'm trying to do is figure out how all this effects the controlling of the card. I seem to have a stable f-error at 20mm/m haha weird, I am wondering if its the jitter or network card latency that is causing the f-error on my real machine and of course my virtual as well. Its a interesting test, ideas?
Could you tell me why nve has this error, let's say I have no cable connected, I turn on the board and then connect the cable, the connection is confirmed but when I give the command to the axis, I have a joint error, but when I disconnect the board now with the cable connected and turned it on again, the error no longer occurred, that is, the error only occurred when I turned on the board before connecting the cable.
Could you tell me why nve has this error, let's say I have no cable connected, I turn on the board and then connect the cable, the connection is confirmed but when I give the command to the axis, I have a joint error, but when I disconnect the board now with the cable connected and turned it on again, the error no longer occurred, that is, the error only occurred when I turned on the board before connecting the cable.
So on my Hyper-V debian with RT Kernel and LinuxCNC I figured out if I change the latency to 2,000,000 instead and 500hz on the ec500 f-error stops raising like crazy and becomes very stable, this is using a usb realtek ethernet card too which has a latency of about .8ms to 1.2ms and 1.95ms occasionally. So next week i'm going to test this on my Dell Wyse 5060 setup and see if this cures my impossible to further tune f-error problem. I think it might as the dell wyse for some reason gets bad jitter and latency. The Hyper-V machine was able to get down to 0.03 f-error at 2000 scale P 10, and 1600mm/m movement, so I count that as progress in trying to find my problem.
