CAN rxMotionDelay and adv

[ctilley79]

Can (pun) someone explain the CAN debugging parameters? Especially the motion delay and adv. Do you see any problems here? This is on a tool board V1.1 running 3.4b7.

[dc42]

@ctilley79 I don't see a problem here. 'rxMotionDelay' is the delay between the time at which the CAN interface time stamped a movement message that was received and the time at which it was about to be put in the queue for processing. 'adv' is the minimum and maximum time in advance of a motion command being due to start that the movement message was put in the queue for processing. Both are in units of 750kHz clocks. These are the accumulated values since you last ran M122 for that board, or since power up if you haven't run M122 for that board since power up.

[ctilley79]

@dc42 gotcha, I wanted to make sure because I’m using about 3 feet of ribbon cable for the CAN signal. I was concerned that since it’s not twisted pair, it may cause problems. Seemed to print well. No lost packets over an 8 hour print.