Note that packet-error can be useful to prevent bogus velocity corrections
in the case of lost/dropped packets:
# position command and feedback
net emcmot.00.pos-cmd joint.0.motor-pos-cmd => pid.0.command mux2.0.in1
net stepgen0fb hm2_[HOSTMOT2](BOARD).0.stepgen.00.position-fb mux2.0.in0
net motor.00.pos-fb <= mux2.0.out joint.0.motor-pos-fb pid.0.feedback
net motor.00.command pid.0.output hm2_[HOSTMOT2](BOARD).0.stepgen.00.velocity-cmd
net ioerror hm2_[HOSTMOT2](BOARD).0.packet-error mux2.0.sel
This hal section uses the packet error pin to select the commanded position
rather that the [stale] feedback position for loop feedback in the event of packet
loss
Ok so next steps? There are still to many variables to figure out if its kernel or linuxcnc its self.
Has anyone got 2.9 running a mesa Ethernet card 7i95 or 96 etc stably?
I looked at building 2.8 for deb-11 to see if its in CNC or the OS but i looks like this is not really possible.
I looked at getting the 4.19 series kernel in deb-11 and that is not easy either, would have to be a source config and build.
