Motors Moving Extreeeemly Slow (about 1step/sec)

[mfc]

I have a Leapfrog Creatr dual. The other day all motors suddenly stopped moving during a print, although there was no error message and the print completed.

I discovered a fried diode on the bottom of the electronics board in the power path that feeds all the stepper motor drivers. I replaced the diode and the motors now respond normally to manual jog control.

But the printed won't work normally using S3D (athough it does work using Repetier!).

At first I thought the printer simply locked up when I start a print, but then noticed that the motors actually move and the print progresses VERRRRY slowly, almost imperceptibly. Seems like the stepper motors move at about 1 step per second!

Again, it does work normally using Repetier!

Anyone have a suggestion of what the issue is?

-Matt

(PS: I have reflashed the board a few times, and re-installed S3D twice.
I also replaced the MEGA2560 chip with no change in behavior.)

[JoeJ]

Go to help --> reset all settings in S3D just to make sure you are using the stock settings. Restart the program and select Leapfrog Creatr Dual

[mfc]

Hi - 1 should have mentioned that I did "reset all" a couple times.

I even reinstalled S3D, reinstalled the firmware, and replaced the mega2560 chip.

[mfc]

Update:

I discovered a workaround, but it doesn't explain why this suddenly started happening.

If I delete the line near the start of the S3D gcode "M201 X1000 Y1000 Z500" everything seems to work.

Strangely, if I delete just the next line "M202 X1000 Y1000 Z500" things seemed to work BUT there is no X motor activity. I have to disconnect/connect to get the motor back.

Anyone have an explanation or suggestion?

[JoeJ]

Those are just editing EEPROM settings. Maybe you have corrupt eeprom values?

I think there is a gcode command to restore the default eeprom values (http://reprap.org/wiki/G-code#M502:_rev ... ttings..22, looks like it might be M502 then M501)

[3drebel]

How did you resolve this issue?

-3drebel

[JoeJ]

Leapfrog has released a new firmware that breaks many of the common Marlin G and M-codes including those used to set acceleration values. No idea how they messed that up since it is already supported by default with Marlin (the firmware which theirs is based on), but they did.

So if you are one of the unfortunate people who has a printer with this new buggy firmware, you can't use the M201, M202, or M204 commands. Simplify3D has these in the beginning of their starting script since it worked fine with previous firmware versions. Just remove those 3 commands from the beginning of your starting script and it will work with the new firmware.

[PimR]

Hey,

please try attached firmware. It's beta version of the coming release.

Make sure you enter the correct offset for your printer in Configuration.h, often found on a sticker on the bottom of the printer.

To double check, issue a M502 and a M500 commando in terminal to reset the settings to factory settings.

Both M201 and M202(not used in the firmware) should and can be removed from the startup script in Simplify3D.

Kind regards,
Pim R.
Lpfrg