Hello.
I recently changed the toolhead on my lulzbot mini to an aerostruder v1. I updated the firmware when prompted in Cura LE, but now the printer crashes on the x and y axis’s before it starts a print. This happens after it successfully homes and auto levels. Sometimes it will only run into itself for a second before starting a print, but most of the time it will keep trying to move until it sends a kill signal. Does anyone know what could be causing this? I’ve tried using different computers with different operating systems, but it does not seem to have helped. I have attached a video of the printers behavior.
Thanks
Was this GCODE written for the previous firmware? If so it’s almost certainly an incompatible startup sequence.
If this is new GCODE written with the same version of Cura that upgraded the firmware, please provide the startup section that has been output:
It looks like everything through probe sequence is fine, so it’ll be around this section from my startup GCODE here:
M425 Z ; use measured Z backlash for compensation
M425 Z F0 ; turn off measured Z backlash compensation. (if activated in the quality settings, this command will automatically be ignored)
M204 S500 ; restore standard acceleration
G1 X0 Y0 Z15 F5000 ; move up off last probe point
That last one, the equivalent of my G1 X0 Y0 Z15 F5000 looks like the command that is screwing you up.
Here is the startup GCODE generated by cura. I don’t think it was generated for the previous firmware since it was generated by a fresh install of cura that was also used to upgrade the firmware.
;This G-Code has been generated specifically for the LulzBot Mini with Aerostruder V1
M73 P0 ; clear GLCD progress bar
M75 ; Start GLCD Timer
G26 ; clear potential 'probe fail' condition
M107 ; disable fans
M420 S0 ; disable leveling matrix
G90 ; absolute positioning
M82 ; set extruder to absolute mode
G92 E0 ; set extruder position to 0
M140 S{material_bed_temperature_layer_0} ; start bed heating up
G28 ; home all axes
G0 X0 Y187 Z156 F200 ; move away from endstops
M109 R{material_soften_temperature} ; soften filament before retraction
G1 E-15 F75 ; retract filament
M109 R{material_wipe_temperature} ; wait for extruder to reach wiping temp
G1 X45 Y173 F11520 ; move above wiper pad
G1 Z0 F1200 ; push nozzle into wiper
G1 X42 Y173 Z-.5 F4000 ; wiping
G1 X52 Y171 Z-.5 F4000 ; wiping
G1 X42 Y173 Z0 F4000 ; wiping
G1 X52 Y171 F4000 ; wiping
G1 X42 Y173 F4000 ; wiping
G1 X52 Y171 F4000 ; wiping
G1 X42 Y173 F4000 ; wiping
G1 X52 Y171 F4000 ; wiping
G1 X57 Y173 F4000 ; wiping
G1 X77 Y171 F4000 ; wiping
G1 X57 Y173 F4000 ; wiping
G1 X77 Y171 F4000 ; wiping
G1 X57 Y173 F4000 ; wiping
G1 X87 Y171 F4000 ; wiping
G1 X77 Y173 F4000 ; wiping
G1 X97 Y171 F4000 ; wiping
G1 X77 Y173 F4000 ; wiping
G1 X97 Y171 F4000 ; wiping
G1 X77 Y173 F4000 ; wiping
G1 X97 Y171 F4000 ; wiping
G1 X107 Y173 F4000 ; wiping
G1 X97 Y171 F4000 ; wiping
G1 X107 Y173 F4000 ; wiping
G1 X97 Y171 F4000 ; wiping
G1 X107 Y173 F4000 ; wiping
G1 X112 Y171 Z-0.5 F1000 ; wiping
G1 Z10 ; raise extruder
G28 X0 Y0 ; home X and Y
G0 X0 Y187 F200 ; move away from endstops
M109 R{material_probe_temperature} ; wait for extruder to reach probe temp
M204 S300 ; set probing acceleration
G29 ; start auto-leveling sequence
M420 S1 ; enable leveling matrix
M204 S2000 ; restore standard acceleration
G28 X0 Y0 ; re-home to account for build variance of earlier mini builds
G0 X0 Y187 F200 ; move away from endstops
G0 Y152 F4000 ; move in front of wiper pad
G4 S1 ; pause
M400 ; wait for moves to finish
M117 Heating... ; progress indicator message on LCD
M109 R{material_print_temperature_layer_0} ; wait for extruder to reach printing temp
M190 R{material_bed_temperature_layer_0} ; wait for bed to reach printing temp
G1 Z2 E0 F75 ; prime tiny bit of filament into the nozzle
M117 Mini Printing... ; progress indicator message on LCD
Can you manually heat it up and issue the g29 command?
Yep, it causes all 3 axis’s to crash when I issue the G29 command.
If the G29 screws up, it’s something in firmware for sure. Do you remember the version you had before this update?
Looking in the code, there is Z_PROBE_END_SCRIPT, which looks like where the error would be.
I do not remember which firmware I had before the update. Ill try flashing some of the older versions to see if that fixes it.
The 2.0.9 code I was looking at didn’t look like it had anything following the G29, but I’m not great at coding Marlin, so it’s entirely possible I just can’t find it.
Be sure you’re reflashing the EEPROM as well, to get it as clean as possible.
I have downgraded to the Aerostruder 1.1.9.28 firmware on the lulzbot website. I cant seem to find any other version except for the 1.1.9.34 that cura provides. Still, issuing the g29 command results in the same behavior with cura saying that the nozzle wipe has failed.
There’s the “stable” firmwares here, which I believe were the ones included with hardware:
It can usually be found in C:\Program Files (x86)\cura-lulzbot 3.6\resources\firmware - just look for the 2.0.0.144.hex for your Mini.
Index of /Software/Marlin/2.0.0.144 (lulzbot.com)
If you don’t have a screen, it looks like you’ll want:
Marlin_Mini_Aerostruder_2.0.0.144_aded3b617.hex (lulzbot.com)
With the screen:
https://download.lulzbot.com/Software/Marlin/2.0.0.144/Marlin_Mini_Aerostruder_2.0.0.144_aded3b617.hex
There’s also firmware here, the development versions which may have bugs, but usually keep pace with the versions of Cura released on the website
Index of /software/Marlin/2.0.0.174 (lulzbot.com)
Yep, looks like the 2.0.0.144 firmware has fixed the problem.
Thanks so much!
No problem, glad to be of help.