Both motors not responding

My Maslow has done little else but a couple of cuts since purchased last December. I made some time to build the new frame in the past month and today tried to reconnect everything looking forward to finally doing some real cutting. Sadly the motors are not responding. I’ve read all I can find on the forum here. Reinstalled Arduino firmware, reset Ground control, checked that the power cable was in the right place, wiped EEPROM, tried to run Test Motors / Encoders. Both motors are silent. I’m running the latest firmware and Ground Control (1.18) . Everything worked pretty fine the last time, though that was months ago. Would not have expected the motors to pack up within that time frame, without being used. How may I verify if it’s a hardware issue or not?

This is what it looks like in Ground Control. Can anyone please tell if the error message holds any useful clues?

Hmmmmm I think based on that error message we can say it’s almost certainly a software issue. I think that the problem is likely caused by the big jump in version number with the update.

Since it looks like the issue is with the machine loading it’s position will you try to use the set chain lengths manual command and let us know what happens?

Thanks @bar, I tried it to no avail. Even when I reset GC settings to default, It still says old position data detected, please set $12, $1, $19 and $20 to load old position data

Hmmmm darn.

So I’ve been looking into it and the section of code which is giving you this error is:

        bit_true(sys.oldSettingsFlag, NEED_ENCODER_STEPS);
        bit_true(sys.oldSettingsFlag, NEED_DIST_PER_ROT);
        bit_true(sys.oldSettingsFlag, NEED_Z_ENCODER_STEPS);
        bit_true(sys.oldSettingsFlag, NEED_Z_DIST_PER_ROT);
        sys.state = STATE_OLD_SETTINGS;
        Serial.println(F("Old position data detected."));
        Serial.println(F("Please set $12, $13, $19, and $20 to load position."));

It looks to me like the jump in firmware versions is so big that we are ending up with some missing information that the machine needs. Ground Control should detect this automatically and send the missing information but that doesn’t seem to be what’s happening. Let me keep digging and come up with another recommendation to try.


Let’s try to do what it want’s us to do and update those values. I’ve grabbed a copy of those settings for my machine and made a fake gcode file which will set them on your machine. Open it just like any other gcode file and press the green play button, and it will update your machine with those settings. Give the arrow buttons a click to see if it will move after that. (43 Bytes)

1 Like

Oh wow, it works, the motors are now responding. Wish I understood what you just did fully, but I’m happy enough that the motors now respond. :man_dancing:


I wish I understood fully too :grin: Sorry about the trouble there I think it was just a matter of the big jump in the firmware version causing some hickups

No worries, there was something to learn there. Thanks again.

1 Like