My SM2 250 just updated its firmware to v1.10.1 so I told it to calibrate.
It promptly dug itself into my bed before I could get it to stop!
Did this release get tested before it was sent out? Im’m afraid to calibrate again!
Yeah. Somethings not right. My A350 calibrated fine but on the very first print it was a disaster. It parked itself for warming up in the front left corner and then when it went time to print it repeatedly crashed the head into the the corner of the bed. More accurately, it kept crashing the bed leveling sensor into the corner of the bed. 
It would not stop until I powered off. Then things got weird…
I powered the machine back on and did a home. The head went down instead of up and would have crashed into the bed again if I didn’t power off. Also, the right Z axis stepper motor was maybe off as it kept jerking when the Z axis was in motion.
I went back to FW 1.9 and did another calibration. Things seemed ok. Unfortunately, the print failed a few minutes in. The head was digging into the workpiece. I checked the bed leveling sensor before the print and it was maybe 0.1mm off from before the crash. Maybe it was moved more than I thought. I’ll do some more testing. I might also generate the gcode from PrusaSlicer instead of Luban.
Double check that your x y z cables are properly plugged into the right ports.
This sounds like what’s happened when people have had them wrong.
-S
Yup … I somehow managed to get the Y and Z cables in the wrong place. Wish the big white lettering was on the other side Of the plug so it was easier to see.
I upgraded the firmware on my A150 and now the bed doesn’t heat up. How do I revert back a firmware version so I can print again? Very frustrating.
As I understand it, you should be able to load earlier firmware onto the USB stick and open the file from the controller.
2 Likes
Wrong cables were not my problem. The head homed fine and moving the table and gantry manually with the controller worked as expected. Everything worked fine until I got a few layers into the print, then it just crashed the head into the build plate.
Oddly, looking at the Luban generated gcode file, I had a negative min_z. When I regenerated the file, the min_z was 0. This was using the default "normal mode for PLA. See below for what I’m talking about:
file that had the head crash:
;max_x(mm): 32
;max_y(mm): 27.25
;max_z(mm): 20
;min_x(mm): -32
;min_y(mm): -27.25
;min_z(mm): -20
rebuild gcode without touching anything:
;max_x(mm): 32
;max_y(mm): 27.25
;max_z(mm): 40
;min_x(mm): -32
;min_y(mm): -27.25
;min_z(mm): 0
How did you rebuild the G-Code and which version of Luban did you use to do it? Were the versions the same? Did you set anything on the SM, update calibration, home location, etc?