You didn’t mention whether the motor moved during the failed portion of the test? I’ll assume it did…
Let’s start with the easier/cheaper things - unplug/replug both ends of the motor cable for that right motor and run a series of tests.
The test runs the motors one at a time at full speed and watches the encoder pulses from that motor to see that they are present and in the proper relationship to each other. A slightly skewed plug can make one of the encoder signals slightly noisy and cause an intermittent failure for the test.
If that didn’t fix it, suspect that particular cable or motor - swap the left and right plugs at the motor control board to differentiate between a board/gpio problem and a motor/cable one. Then swap the motor ends to test the cables.
If the problem is the cable, it might be a damaged wire (orange, green, white, yellow for the encoder), something that you might be able to fix. If the problem is the encoder, you can take the cap off the end of the motor and take a look. The encoder on the stock motors is magnetic, so metal filings could cause trouble. The solder connections might be harder to check and repair, but saving $ is a thing.
Not sure I understand the difference; I’m talking about the process where you set a tooth vertical and then extend the chains from their first link. First wipe the ERPROM, then Actions/SetChainLengthAutomatic.
I replaced my original USB cable today, did with motor test and the motor failed.
I checked all connections again. I did notice my left motor connection was a little loose,but still plugged in good. I used a zip tie to make sure it would hold in place.
Motor test passed.
I loaded a gcode file and pressed play. Then I got the message “sled not keeping up”.
I checked all connections again.
I cleared the gcode files, loaded another file, then I noticed that for some reason my file was not cutting into the materiel,but rather cutting above plane. I scrapped that file and loaded an older file that had worked in the past, and this worked. Part was cut out. So I blamed my gcode file from fusion360.
I loaded a second file, new today. It made it through all the pocket and bore cuts, but when it got to the profile cut it failed again.
I did a motor test and got yet another failure.
Will attach video of motor failing
Currently running version 1.2 in firmware and ground control.
Attempted to upload a video of the motor making electronic beeps etc, but the file is to large to upload here?
I am had bought a new motor cable awhile back when I cut through the z axis cable, but never used it…I had the other cable fixed by an electrical guy and its fine since…
Installed the new motor cable motors passed initial motor test, but failed when I tried to move the sled to a location.
i cleared the log file and loaded a quick gcode file for testing.
I will attach the files for review (please note, that i am still learning fusion 360 and i haven’t learned what to turn off, so there are a few lines that are ingnored)