Avisos
Vaciar todo

M500 Command screwed up settings  

  RSS
sdub
 sdub
(@sdub)
Active Member
M500 Command screwed up settings

So I'm trying to calibrate my extruder... I calculated that my steps/mm setting should be increased from the default 161.30 to 174.19 to get accurate filament metering.

I entered the commands:

M92 X100.0 Y100.0 Z400.0 E174.19
M500

Both returned "ok"

After rebooting my printer, I issued another M503 command, and got

Send: M503
Recv: echo:Steps per unit:
Recv: echo: M92 X100.00 Y100.00 Z400.00 E0.0
Recv: echo:Maximum feedrates (mm/s):
Recv: echo: M203 X500.00 Y500.00 Z12.00 E0.00
Recv: echo:Maximum Acceleration (mm/s2):
Recv: echo: M201 X9000 Y9000 Z500 E10000
Recv: echo:Acceleration: S=acceleration, T=retract acceleration
Recv: echo: M204 S800.00 T1500.00
Recv: echo:Advanced variables: S=Min feedrate (mm/s), T=Min travel feedrate (mm/s), B=minimum segment time (ms), X=maximum XY jerk (mm/s), Z=maximum Z jerk (mm/s), E=maximum E jerk (mm/s)
Recv: echo: M205 S0.00 T0.00 B20000 X10.00 Y10.00 Z0.20 E0.00
Recv: echo:Home offset (mm):
Recv: echo: M206 X0.00 Y0.00 Z0.00
Recv: echo:PID settings:
Recv: echo: M301 P40.93 I4.88 D86.08
Recv: echo:Retract: S=Length (mm) F:Speed (mm/m) Z: ZLift (mm)
Recv: echo: M207 S3.00 F2700.00 Z0.00
Recv: echo:Recover: S=Extra length (mm) F:Speed (mm/m)
Recv: echo: M208 S0.00 F480.00
Recv: echo:Auto-Retract: S=0 to disable, 1 to interpret extrude-only moves as retracts or recoveries
Recv: echo: M209 S0
Recv: echo:Filament settings: Disabled
Recv: ok

Odd... zero steps/mm. Indeed when I tried to print, nothing extruded. I issued the M92 command again, and it is printing slow as molasses. A 0.100 benchy took more than 6 hours to print.

Unfortunately I didn't record the original values, so I'm not sure what other settings might have gotten screwed up that might be causing the super slow printing.

Respondido : 02/05/2017 4:51 am
sdub
 sdub
(@sdub)
Active Member
Topic starter answered:
Re: M500 Command screwed up settings

After a little more Googling, it appears the follwing commands needed to be fixed. Any guess how that could happen? Did I fat finger something?


M92 X100.00 Y100.00 Z400.00 E174.19
M203 X500.00 Y500.00 Z12.00 E120.00
M204 S1500.00 T1500.00
M205 S0.00 T0.00 B20000 X10.00 Y10.00 Z0.20 E2.50

After setting these 4 lines in the terminal, I issued an M500, M501, M503 and everything echoed back correctly. After another reboot of both the MK2 and the Octopi (for good measure), I again issued an M503 and got the following:

Send: M503
Recv: echo:Steps per unit:
Recv: echo: M92 X100.00 Y100.00 Z400.00 E174.19
Recv: echo:Maximum feedrates (mm/s):
Recv: echo: M203 X500.00 Y500.00 Z12.00 E120.00
Recv: echo:Maximum Acceleration (mm/s2):
Recv: echo: M201 X9000 Y9000 Z500 E10000
Recv: echo:Acceleration: S=acceleration, T=retract acceleration
Recv: echo: M204 S1500.00 T1500.00
Recv: echo:Advanced variables: S=Min feedrate (mm/s), T=Min travel feedrate (mm/s), B=minimum segment time (ms), X=maximum XY jerk (mm/s), Z=maximum Z jerk (mm/s), E=maximum E jerk (mm/s)
Recv: echo: M205 S0.00 T0.00 B20000 X10.00 Y10.00 Z0.20 E2.50
Recv: echo:Home offset (mm):
Recv: echo: M206 X0.00 Y0.00 Z0.00
Recv: echo:PID settings:
Recv: echo: M301 P40.93 I4.88 D86.08
Recv: echo:Retract: S=Length (mm) F:Speed (mm/m) Z: ZLift (mm)
Recv: echo: M207 S3.00 F2700.00 Z0.00
Recv: echo:Recover: S=Extra length (mm) F:Speed (mm/m)
Recv: echo: M208 S0.00 F480.00
Recv: echo:Auto-Retract: S=0 to disable, 1 to interpret extrude-only moves as retracts or recoveries
Recv: echo: M209 S0
Recv: echo:Filament settings: Disabled
Recv: ok

Seems to be miraculously fixed. I'll leave this here for others to search against, but I'm still baffled.

Respondido : 02/05/2017 5:07 am
JeffJordan
(@jeffjordan)
Miembro Moderator
Re: M500 Command screwed up settings

...
I entered the commands:

M92 X100.0 Y100.0 Z400.0 E174.19
M500

Both returned "ok"

yeah, that's the problem.
the second one should return a "Settings Stored" message.
had this behaviour sometimes at the 3.0.10 (release) as well.
just reconnect (which will cause a reset of the printer) and run the commands again.

dem inscheniör is' nix zu schwör...

Respondido : 02/05/2017 5:50 pm
Compartir: