automatically generated "status" leads to system hang

Troubleshooting talk for software

automatically generated "status" leads to system hang

Postby jledwards666 » 2015-Jan-Mon-16-Jan

I just did the upgrade to take an original Printrbot Simple (with circuit board Rev-D) to modern levels with kits for belts instead of strings, metal bed, and metal extruder. As required, I did the reflash of the firmware which, at least initially, seemed to go well. However, it soon became apparent that there is a problem with some sort of self-generating "status report". Regardless of what I do, about a minute after connecting, the printrbot generates a status which is nearly identical to what you get when you send a "m501" command (all "echos"), this followed by several actual commands which I suspect result in the hang:
N1 M110 *2
N1 M110 *2
N2 M115 *4
N3 M111 S6 *68
N4 T0 *30
N5 M20 *52
N6 M80 *61

I don't know what these do nor why they're being generated but they seem to be trouble. Thoughts?

ps: here's the complete "report" that gets generated after about a minute following successful connection, with the mystery commands separated out with a blank line for easy identification.

Code: Select all
10:14:20.095 : start
10:14:20.095 : echo:Marlin 1.0.0
10:14:20.095 : echo: Last Updated: Jun  5 2014 09:34:35 | Author: (lwalkera, Printrbot firmware)
10:14:20.095 : Compiled: Jun  5 2014
10:14:20.095 : echo: Free Memory: 3787  PlannerBufferBytes: 1232
10:14:20.095 : echo:Hardcoded Default Settings Loaded
10:14:20.095 : echo:Steps per unit:
10:14:20.118 : echo:  M92 X80.00 Y80.00 Z2020.00 E96.00
10:14:20.118 : echo:Maximum feedrates (mm/s):
10:14:20.118 : echo:  M203 X100.00 Y100.00 Z2.00 E14.00
10:14:20.118 : echo:Maximum Acceleration (mm/s2):
10:14:20.118 : echo:  M201 X2000 Y2000 Z30 E10000
10:14:20.119 : echo:Acceleration: S=acceleration, T=retract acceleration
10:14:20.119 : echo:  M204 S3000.00 T3000.00
10:14:20.119 : 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)
10:14:20.119 : echo:  M205 S0.00 T0.00 B20000 X20.00 Z0.40 E5.00
10:14:20.119 : echo:Home offset (mm):
10:14:20.119 : echo:  M206 X0.00 Y0.00 Z0.00
10:14:20.119 : echo:PID settings:
10:14:20.119 : echo:   M301 P22.20 I1.08 D114.00
10:14:20.119 : echo:Min position (mm):
10:14:20.119 : echo:  M210 X0.00 Y0.00 Z0.00
10:14:20.119 : echo:Max position (mm):
10:14:20.119 : echo:  M211 X152.40 Y152.40 Z152.40
10:14:20.119 : echo:Bed probe offset (mm):
10:14:20.119 : echo:  M212 X10.00 Y10.00 Z-4.00

10:14:20.586 : N1 M110 *2
10:14:20.586 : N1 M110 *2
10:14:20.586 : N2 M115 *4
10:14:20.590 : N3 M111 S6 *68
10:14:20.593 : N4 T0 *30
10:14:20.593 : N5 M20 *52
10:14:20.593 : N6 M80 *61
  • 0

jledwards666
Waiting to connect to printer...
 
Posts: 2
Joined: 2015-Jan-Mon-15-Jan
Reputation: 0

automatically generated "status" leads to system hang

Sponsor

Sponsor
 

Re: automatically generated "status" leads to system hang

Postby jledwards666 » 2015-Jan-Mon-17-Jan

I learned a bit more about the commands being generated at the end. Most seem harmless but the last one, M80, corresponds to "ATX Power On" and I guess is problematic. My real question, however, is what is generating these commands and why. Is it something within Repetier itself or are they being fed back from the reflashed Printrbot (Rev-D card) itself (unlikely)?
  • 0

jledwards666
Waiting to connect to printer...
 
Posts: 2
Joined: 2015-Jan-Mon-15-Jan
Reputation: 0


Return to Troubleshooting talk

Who is online

Users browsing this forum: No registered users and 1 guest

cron