Error: Undefined feed rate all of a sudden

[Mike Loebl]

All of a sudden when I was testing some different print speeds in Slic3r and adjusting M203, the print started throwing an exception "Error: Undefined feed rate"  whenever a G1 call is made.  This on a Azteeg X5 GT I've been running for about a year (currently on the June 14 firmware).  What has me really confused is I can reproduce it with just sending the following immediately after homing:

G1 Z10; move bed down 10mm

This command (and the the other's in my Gcode before I print) haven't changed in months, so I thought potentially I could have made a mistake when I updated M203:

M203 X100.0 Y100.0 Z30.0 E50.0

default_feed_rate and default_seek_rate are also set to the default of 4000 in the config.

I reverted the config file to it's default state with M502, didn't make a difference.  Here's the values:

; DO NOT EDIT THIS FILE

;Steps per unit:

M92 X100.45886 Y100.08242 Z408.23578 

;Acceleration mm/sec^2:

M204 S2000.00000 

;X- Junction Deviation, Z- Z junction deviation, S - Minimum Planner speed mm/sec:

M205 X0.05000 Z-1.00000 S0.00000

;Max cartesian feedrates in mm/sec:

M203 X100.00000 Y100.00000 Z30.00000 S-1.00000

;Max actuator feedrates in mm/sec:

M203.1 X500.00000 Y500.00000 Z42.66667 

;Digipot Motor currents:

M907 X1.00000 Y1.00000 Z1.20000 A1.00000 B1.00000 

;E Steps per mm:

M92 E465.1537 P57988

;E Filament diameter:

M200 D0.0000 P57988

;E retract length, feedrate:

M207 S3.0000 F2700.0000 Z0.0000 Q6000.0000 P57988

;E retract recover length, feedrate:

M208 S0.0000 F480.0000 P57988

;E acceleration mm/sec²:

M204 E500.0000 P57988

;E max feed rate mm/sec:

M203 E50.0000 P57988

;PID settings:

M301 S0 P48.4141 I1.9231 D304.7061 X255.0000 Y255

;Max temperature setting:

M143 S0 P300.0000

;PID settings:

M301 S1 P184.8786 I7.8090 D1094.2502 X255.0000 Y255

;Max temperature setting:

M143 S1 P300.0000

;Home offset (mm):

M206 X0.00 Y0.00 Z0.00 

;Probe feedrates Slow/fast(K)/Return (mm/sec) max_z (mm) height (mm) dwell (s):

M670 S5.00 K100.00 R0.00 Z325.00 H10.00 D0.00

;Probe points:

M557 P0 X160.00000 Y300.00000

M557 P1 X10.00000 Y40.00000

M557 P2 X300.00000 Y40.00000

;Probe offsets:

M565 X0.00000 Y0.00000 Z0.00000

Obviously I changed something by accident when updated M203, but not sure what.  Any help is appreciated as not seeing it.  

Thanks you,

-Mike

[Mike Loebl]

I think narrowed it down to potentially a bug in the firmware if a halt is cleared. If I power the board off completely, the G1 commands work fine. Likewise if I open up an older print before I updated some of the settings in Slic3r, it also works fine. However if I send it a newer gcode (guessing with something missing for the feed rate), I get the halt, after clearing the halt, the problem doesn't go away until the board is power cycled. Made my troubleshooting a nightmare, but now makes more sense. Now to see what Slic3r messed up...

--
You received this message because you are subscribed to a topic in the Google Groups "Smoothieware Support" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/smoothieware-support/CqpKdjaCNbs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to smoothieware-sup...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mark Rehorst]

I recently had the same problem.  Slic3r put G1 F0 commands in the gcode for some reason.

[wolfmanjm]

This is no bug. Fxxx is sticky and somewhere your gcode is setting F0, and ince that happens it will halt unless you specify a good feedrate.... G1 F100 for instance will fix it.

if it is a G0 then G0 F100 wil also fix it. The slicer needs to send good feedrates this is just the rule.

To unsubscribe from this group and all its topics, send an email to smoothieware-support+unsub...@googlegroups.com.

[Mike Loebl]

Ahhh ok that makes a lot more sense, thank you!  It's messing up the default feed rate, so any subsequent gcode, even if not wiping it out, *isn't* setting any value therefore it still won't work.  The fact I would pass in what I thought was  "Good" gcode was irrelevant at that point, and was misdirecting me to look in the wrong place during troubleshooting.  That actually helps a lot as I can see WTF is wrong with that gcode it's spitting out.  I noticed in the latest pull of Slic3r the default feedrate box was cycling enabled/disabled, betting that's a big part of it.   Thank you very much for the reply!

To unsubscribe from this group and all its topics, send an email to smoothieware-sup...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to a topic in the Google Groups "Smoothieware Support" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/smoothieware-support/CqpKdjaCNbs/unsubscribe.

To unsubscribe from this group and all its topics, send an email to smoothieware-sup...@googlegroups.com.

[Mike Loebl]

That was definitely it, pulled up the gcode and mostly certainly was setting to F0.... thank you for the help!