Greetings, a friend picked up a Taz 6. He knows nothing about 3d printers, so, he asked me if it works.
Now, I have so many questions. When sending to home, it misses the Z setter button (opposite side of the bed in X) and just keeps going. I shut the power off, reboot, and manually rise the nozzle. The nozzle is .4 in a Hexagon hotend (not a selection within Cura LE setup … maybe microswiss?). The travel limit switches in X & Z appear to be working. Y+ max appears to be very close to the bed edge. Seems like the bed position doesn’t align with frame in X & Y. I knew nothing about Lulzbot up to 3 days ago. I have a K1C & A1 combo (please don’t hold it against me. lol.
I’m thinking of marking the bed’s center, move X & Y to machine 140mm. then, unbolt the entire Y axis assembly & move the align the bed center mark to the nozzle. Ugh. Please suggest another solution.
A used printer with a non-standard nozzle size means we need more information about the printer. A picture (or two) of the tool head and the version of the firmware to start. The firmware version is displayed on the LCD screen when the printer is first powered up.
Have you successfully connected the printer USB to a host? Tell us about that host. Once we can establish a connection, we can send gcode commands to the printer and receive responses. This will make troubleshooting easier.
Thanks for the quick reply! Taz 6 running v 1.1.9.28. Marlin v 1.1.9. USB connection not made. I have original sd card. At least, the card has many files, including RAMBo, but yave not managed to load it into win 10 pc.
To better understand how to align components, is there a way to establish or change machine home position? (G53 command to me). No code creating at the printer control, so, I could write such code to a file.gcode on the sdcard & manually execute the file (or this not work)?
I agree with getting the pc connected to the printer. How & where & name of printer that window’s displays could be daunting.
I have seen the cura LE axis jog control when I loaded the sdcard, picked a *.gcode file to open & tried to send it to the printer. My thought process is a product of running/programming cnc milling machines for 30+ years. That includes the dangers of control knob movements. Stay close to the power off switch (Estop). Lol.
First pic is nozzle location at XY limit switches.
Second pic is nozzle missing z height button during sent home command.
I think that is the original Single Extruder but a picture with the whole extruder in frame would help confirm that.
1.1.9.28 is an old version of firmware. 1.1.9.34 was the last Marlin version 1 released by LulzBot. If you download and install a current version of CuraLE, it will have Marlin version 2 firmware. You could download an older version (from the link below). I would suggest the latest 3.6 version.
I would suggest that you connect the printer to your Windows 10 computer. It should show up as a COM port. Install one or both of the following:
With those in place, we can connect to the printer with a console that will let us send gcode commands and see the responses.
CuraLE will want to update the firmware but we can hold off on that for the moment.
Yes, that is the original Single Extruder V2.1. Remember the E-steps value, 830, as you will need it later since it is “hidden” when the tool head is installed 
. The stock nozzle was a 0.5mm but we can make adjustments for the 0.4mm nozzle that is installed.
Thanks. Installing 3.6.40 worked. I have manual control and verified the above pic of misalignment in X, crashing in Z when instructing home position. I changed the printhead value in printer manager.
For reference, use https://marlinfw.org/meta/gcode/ for details on the gcode commands available in Marlin.
Please execute the following commands from the CuraLE console. Capture the output and upload it here. Please use the </> on the toolbar so that the markdown editor doesn’t try to format the responses.
- M92
- M851
- M206
- M503
- M115
- G28 X Y
- M114
- M119
The first three commands will capture the current values of E-steps, Z-offset, and any home offsets. The next two commands will capture the current settings and firmware info. The G28 X Y will home X and Y and the last two commands will show the current position and the state of the endstops.
My TAZ 6 is connected to a Raspberry Pi 3B running OctoPrint.
after the G28 X Y I get:
Send: G28 X Y
[...]
Recv: X:-18.10 Y:308.50 Z:16.00 E:0.00 Count X:-1810 Y:30350 Z:25600
Recv: ok P13 B3
[...]
Send: M119
[...]
Recv: Reporting endstop status
Recv: x_min: open
Recv: y_min: open
Recv: y_max: open
Recv: z_min: open
Recv: z_max: open
Recv: z_probe: open
Recv: filament: open
Recv: ok P15 B3
[...]
Send: G28 Z
[...]
Recv: X:-20.10 Y:259.50 Z:16.00 E:0.00 Count X:-2010 Y:25250 Z:0
Recv: ok P13 B3
[...]
Send: M119
Recv: Reporting endstop status
Recv: x_min: TRIGGERED
Recv: y_min: open
Recv: y_max: open
Recv: z_min: open
Recv: z_max: open
Recv: z_probe: open
Recv: filament: open
Recv: ok P13 B3
Note that the response contains the M114 position.
If you want to wait until we look at the results then stop here.
I believe the next step will be execute M502 which will reset the firmware to factory defaults and then try the list again. We will need to restore the Z-offset and E-steps with, for example, M851 Z-1.27 and M92 E830 followed by an M500 to save those changes.
Thanks for your help!
My TAZ 6 is connected to a Raspberry Pi 3B running OctoPrint. How did you do this? I have no network on the sidekick 747 just usb. I have 2 Pi 4b and run various linux.
I run these commands from the Cura monitor console…
[09:45:27] M92
<<< [09:45:27] M92 X100.00 Y100.00 Z200.00 E439.00
<<< [09:45:27] ok P15 B7
[09:46:11] M851
<<< [09:46:11] M851 X-1.00 Y50.00 Z-1.36 ; (mm)
<<< [09:46:11] ok P15 B7
[09:46:54] M206
<<< [09:46:54] M206 X0.00 Y0.00 Z0.00
<<< [09:46:54] ok P15 B7
[09:47:14] M503
<<< [09:47:14] echo:; Linear Units:
<<< [09:47:14] echo: G21 ; (mm)
<<< [09:47:14] echo:; Temperature Units:
<<< [09:47:14] echo: M149 C ; Units in Celsius
<<< [09:47:14] echo:; Filament settings (Disabled):
<<< [09:47:14] echo: M200 S0 D2.85
<<< [09:47:14] echo:; Steps per unit:
<<< [09:47:14] echo: M92 X100.00 Y100.00 Z200.00 E439.00
<<< [09:47:14] echo:; Max feedrates (units/s):
<<< [09:47:14] echo: M203 X500.00 Y500.00 Z300.00 E40.00
<<< [09:47:14] echo:; Max Acceleration (units/s2):
<<< [09:47:14] echo: M201 X4750.00 Y4750.00 Z100.00 E9000.00
<<< [09:47:14] echo:; Acceleration (units/s2) (P R T):
<<< [09:47:14] echo: M204 P300.00 R3000.00 T300.00
<<< [09:47:14] echo:; Advanced (B<min_segment_time_us> S<min_feedrate> T<min_travel_feedrate> X<max_jerk> Y<max_jerk> Z<max_jerk> E<max_jerk>):
<<< [09:47:14] echo: M205 B20000.00 S0.00 T0.00 X10.00 Y10.00 Z0.40 E10.00
<<< [09:47:14] echo:; Home offset:
<<< [09:47:14] echo: M206 X0.00 Y0.00 Z0.00
<<< [09:47:14] echo:; Auto Bed Leveling:
<<< [09:47:14] echo: M420 S0 ; Leveling OFF
<<< [09:47:14] echo: G29 W I0 J0 Z0.84500
<<< [09:47:14] echo: G29 W I1 J0 Z0.15000
<<< [09:47:14] echo: G29 W I2 J0 Z-0.28500
<<< [09:47:14] echo: G29 W I3 J0 Z-0.66500
<<< [09:47:14] echo: G29 W I0 J1 Z0.74000
<<< [09:47:14] echo: G29 W I1 J1 Z0.20000
<<< [09:47:14] echo: G29 W I2 J1 Z-0.13000
<<< [09:47:14] echo: G29 W I3 J1 Z-0.38000
<<< [09:47:14] echo: G29 W I0 J2 Z0.52500
<<< [09:47:14] echo: G29 W I1 J2 Z0.15000
<<< [09:47:14] echo: G29 W I2 J2 Z-0.08000
<<< [09:47:14] echo: G29 W I3 J2 Z-0.15500
<<< [09:47:14] echo: G29 W I0 J3 Z0.25000
<<< [09:47:14] echo: G29 W I1 J3 Z0.09000
<<< [09:47:14] echo: G29 W I2 J3 Z0.03500
<<< [09:47:14] echo: G29 W I3 J3 Z0.22000
<<< [09:47:14] echo:; Servo Angles:
<<< [09:47:14] echo:echo: M281 P0 L10 U90
<<< [09:47:14] echo:; Material heatup parameters:
<<< [09:47:14] echo: M145 S0 H180.00 B60.00 F8
<<< [09:47:14] echo: M145 S1 H220.00 B110.00 F0
<<< [09:47:14] echo: M145 S2 H200.00 B60.00 F0
<<< [09:47:14] echo: M145 S3 H145.00 B0.00 F0
<<< [09:47:14] echo:; Bed PID:
<<< [09:47:14] echo: M304 P22.77 I0.58 D487.70
<<< [09:47:14] echo:; Controller Fan:
<<< [09:47:14] echo: M710 S255 I120 A1 D60 ; (100% 47%)
<<< [09:47:14] echo:; Retract (S F Z):
<<< [09:47:14] echo: M207 S3.00 W13.00 F2700.00 Z0.00
<<< [09:47:14] echo:; Recover (S F):
<<< [09:47:14] echo: M208 S0.00 W0.00 F480.00
<<< [09:47:14] echo:; Auto-Retract (S):
<<< [09:47:14] echo: M209 S0
<<< [09:47:14] echo:; Z-Probe Offset:
<<< [09:47:14] echo: M851 X-1.00 Y50.00 Z-1.36 ; (mm)
<<< [09:47:14] echo:; Stepper driver current:
<<< [09:47:14] echo: M906 X975 Y975 Z975
<<< [09:47:14] echo: M906 T0 E850
<<< [09:47:14] echo:; StallGuard threshold:
<<< [09:47:14] echo: M914 X3 Y3
<<< [09:47:14] echo:; Driver stepping mode:
<<< [09:47:14] echo:; Hotend Idle Timeout:
<<< [09:47:14] M86 B0 E0 S600 T150
<<< [09:47:14] echo:; Linear Advance:
<<< [09:47:14] echo: M900 K0.03
<<< [09:47:14] echo:; Filament load/unload:
<<< [09:47:14] echo: M603 L40.00 U50.00 ; (mm)
<<< [09:47:14] echo:; Filament runout sensor:
<<< [09:47:14] echo: M412 S1 ; Sensor ON
<<< [09:47:14] echo:; Model predictive control:
<<< [09:47:14] echo: M306 E0 P100.00 C36.29 R0.1143 A0.0936 F0.1744 H0.0056
<<< [09:47:14] ok P15 B7
[09:49:06] M115
<<< [09:49:06] FIRMWARE_NAME:Marlin FIRMWARE_VERSION:2.1.3.0.46 EXTRUDER_TYPE:Galaxy Series PROBE_TYPE:BLTouchBED_TYPE: STANDARD (Apr 25 2025 14:04:45) SOURCE_CODE_URL:github.com/MarlinFirmware/Marlin PROTOCOL_VERSION:1.0 MACHINE_TYPE:SideKick 747 KINEMATICS:Cartesian EXTRUDER_COUNT:1 UUID:5b3d61d6-80f8-41ed-bd8a-9c765f8d523d
<<< [09:49:06] Cap:SERIAL_XON_XOFF:0
<<< [09:49:06] Cap:BINARY_FILE_TRANSFER:0
<<< [09:49:06] Cap:EEPROM:1
<<< [09:49:06] Cap:VOLUMETRIC:1
<<< [09:49:06] Cap:AUTOREPORT_POS:0
<<< [09:49:06] Cap:AUTOREPORT_TEMP:1
<<< [09:49:06] Cap:PROGRESS:0
<<< [09:49:06] Cap:PRINT_JOB:1
<<< [09:49:06] Cap:AUTOLEVEL:1
<<< [09:49:06] Cap:RUNOUT:1
<<< [09:49:06] Cap:Z_PROBE:1
<<< [09:49:06] Cap:LEVELING_DATA:1
<<< [09:49:06] Cap:BUILD_PERCENT:1
<<< [09:49:06] Cap:SOFTWARE_POWER:0
<<< [09:49:06] Cap:TOGGLE_LIGHTS:0
<<< [09:49:06] Cap:CASE_LIGHT_BRIGHTNESS:0
<<< [09:49:06] Cap:EMERGENCY_PARSER:1
<<< [09:49:06] Cap:HOST_ACTION_COMMANDS:1
<<< [09:49:06] Cap:PROMPT_SUPPORT:1
<<< [09:49:06] Cap:SDCARD:1
<<< [09:49:06] Cap:MULTI_VOLUME:0
<<< [09:49:06] Cap:REPEAT:0
<<< [09:49:06] Cap:SD_WRITE:1
<<< [09:49:06] Cap:AUTOREPORT_SD_STATUS:1
<<< [09:49:06] Cap:LONG_FILENAME:1
<<< [09:49:06] Cap:LFN_WRITE:0
<<< [09:49:06] Cap:CUSTOM_FIRMWARE_UPLOAD:0
<<< [09:49:06] Cap:EXTENDED_M20:1
<<< [09:49:06] Cap:THERMAL_PROTECTION:1
<<< [09:49:06] Cap:MOTION_MODES:0
<<< [09:49:06] Cap:ARCS:1
<<< [09:49:06] Cap:BABYSTEPPING:1
<<< [09:49:06] Cap:EP_BABYSTEP:0
<<< [09:49:06] Cap:CHAMBER_TEMPERATURE:0
<<< [09:49:06] Cap:COOLER_TEMPERATURE:0
<<< [09:49:06] Cap:MEATPACK:0
<<< [09:49:06] Cap:CONFIG_EXPORT:0
<<< [09:49:06] ok P15 B7
[09:50:27] G28 XY. TABLE Went to the bak all the way, then made much grinding souns.
<<< [09:50:29] echo:busy: processing
<<< [09:50:31] echo:busy: processing
<<< [09:50:33] echo:busy: processing
<<< [09:50:35] echo:busy: processing
<<< [09:50:37] echo:busy: processing
<<< [09:50:39] echo:busy: processing
<<< [09:50:40] X:3.50 Y:-18.00 Z:15.00 E:0.00 Count X:350 Y:-1800 Z:3000
[09:57:13] M114
<<< [09:57:13] X:3.50 Y:-18.00 Z:15.00 E:0.00 Count X:350 Y:-1800 Z:3000
<<< [09:57:13] ok P15 B7
<<< [09:57:50] Reporting endstop status
<<< [09:57:50] X Min: open
<<< [09:57:50] Y Min: open
<<< [09:57:50] Z Min: TRIGGERED
<<< [09:57:50] filament: TRIGGERED
<<< [09:57:53] ok T:18.88 /0.00 B:19.78 /0.00 @:0 B@:0 My TAZ 6 is connected to a Raspberry Pi 3B running OctoPrint. How did you do this? I have no network on the sidekick 747 just usb. I have 2 Pi 4b and run various linux.
I run these commands from the Cura monitor console…
[09:45:27] M92
<<< [09:45:27] M92 X100.00 Y100.00 Z200.00 E439.00
<<< [09:45:27] ok P15 B7
[09:46:11] M851
<<< [09:46:11] M851 X-1.00 Y50.00 Z-1.36 ; (mm)
<<< [09:46:11] ok P15 B7
[09:46:54] M206
<<< [09:46:54] M206 X0.00 Y0.00 Z0.00
<<< [09:46:54] ok P15 B7
[09:47:14] M503
<<< [09:47:14] echo:; Linear Units:
<<< [09:47:14] echo: G21 ; (mm)
<<< [09:47:14] echo:; Temperature Units:
<<< [09:47:14] echo: M149 C ; Units in Celsius
<<< [09:47:14] echo:; Filament settings (Disabled):
<<< [09:47:14] echo: M200 S0 D2.85
<<< [09:47:14] echo:; Steps per unit:
<<< [09:47:14] echo: M92 X100.00 Y100.00 Z200.00 E439.00
<<< [09:47:14] echo:; Max feedrates (units/s):
<<< [09:47:14] echo: M203 X500.00 Y500.00 Z300.00 E40.00
<<< [09:47:14] echo:; Max Acceleration (units/s2):
<<< [09:47:14] echo: M201 X4750.00 Y4750.00 Z100.00 E9000.00
<<< [09:47:14] echo:; Acceleration (units/s2) (P R T):
<<< [09:47:14] echo: M204 P300.00 R3000.00 T300.00
<<< [09:47:14] echo:; Advanced (B<min_segment_time_us> S<min_feedrate> T<min_travel_feedrate> X<max_jerk> Y<max_jerk> Z<max_jerk> E<max_jerk>):
<<< [09:47:14] echo: M205 B20000.00 S0.00 T0.00 X10.00 Y10.00 Z0.40 E10.00
<<< [09:47:14] echo:; Home offset:
<<< [09:47:14] echo: M206 X0.00 Y0.00 Z0.00
<<< [09:47:14] echo:; Auto Bed Leveling:
<<< [09:47:14] echo: M420 S0 ; Leveling OFF
<<< [09:47:14] echo: G29 W I0 J0 Z0.84500
<<< [09:47:14] echo: G29 W I1 J0 Z0.15000
<<< [09:47:14] echo: G29 W I2 J0 Z-0.28500
<<< [09:47:14] echo: G29 W I3 J0 Z-0.66500
<<< [09:47:14] echo: G29 W I0 J1 Z0.74000
<<< [09:47:14] echo: G29 W I1 J1 Z0.20000
<<< [09:47:14] echo: G29 W I2 J1 Z-0.13000
<<< [09:47:14] echo: G29 W I3 J1 Z-0.38000
<<< [09:47:14] echo: G29 W I0 J2 Z0.52500
<<< [09:47:14] echo: G29 W I1 J2 Z0.15000
<<< [09:47:14] echo: G29 W I2 J2 Z-0.08000
<<< [09:47:14] echo: G29 W I3 J2 Z-0.15500
<<< [09:47:14] echo: G29 W I0 J3 Z0.25000
<<< [09:47:14] echo: G29 W I1 J3 Z0.09000
<<< [09:47:14] echo: G29 W I2 J3 Z0.03500
<<< [09:47:14] echo: G29 W I3 J3 Z0.22000
<<< [09:47:14] echo:; Servo Angles:
<<< [09:47:14] echo:echo: M281 P0 L10 U90
<<< [09:47:14] echo:; Material heatup parameters:
<<< [09:47:14] echo: M145 S0 H180.00 B60.00 F8
<<< [09:47:14] echo: M145 S1 H220.00 B110.00 F0
<<< [09:47:14] echo: M145 S2 H200.00 B60.00 F0
<<< [09:47:14] echo: M145 S3 H145.00 B0.00 F0
<<< [09:47:14] echo:; Bed PID:
<<< [09:47:14] echo: M304 P22.77 I0.58 D487.70
<<< [09:47:14] echo:; Controller Fan:
<<< [09:47:14] echo: M710 S255 I120 A1 D60 ; (100% 47%)
<<< [09:47:14] echo:; Retract (S F Z):
<<< [09:47:14] echo: M207 S3.00 W13.00 F2700.00 Z0.00
<<< [09:47:14] echo:; Recover (S F):
<<< [09:47:14] echo: M208 S0.00 W0.00 F480.00
<<< [09:47:14] echo:; Auto-Retract (S):
<<< [09:47:14] echo: M209 S0
<<< [09:47:14] echo:; Z-Probe Offset:
<<< [09:47:14] echo: M851 X-1.00 Y50.00 Z-1.36 ; (mm)
<<< [09:47:14] echo:; Stepper driver current:
<<< [09:47:14] echo: M906 X975 Y975 Z975
<<< [09:47:14] echo: M906 T0 E850
<<< [09:47:14] echo:; StallGuard threshold:
<<< [09:47:14] echo: M914 X3 Y3
<<< [09:47:14] echo:; Driver stepping mode:
<<< [09:47:14] echo:; Hotend Idle Timeout:
<<< [09:47:14] M86 B0 E0 S600 T150
<<< [09:47:14] echo:; Linear Advance:
<<< [09:47:14] echo: M900 K0.03
<<< [09:47:14] echo:; Filament load/unload:
<<< [09:47:14] echo: M603 L40.00 U50.00 ; (mm)
<<< [09:47:14] echo:; Filament runout sensor:
<<< [09:47:14] echo: M412 S1 ; Sensor ON
<<< [09:47:14] echo:; Model predictive control:
<<< [09:47:14] echo: M306 E0 P100.00 C36.29 R0.1143 A0.0936 F0.1744 H0.0056
<<< [09:47:14] ok P15 B7
[09:49:06] M115
<<< [09:49:06] FIRMWARE_NAME:Marlin FIRMWARE_VERSION:2.1.3.0.46 EXTRUDER_TYPE:Galaxy Series PROBE_TYPE:BLTouchBED_TYPE: STANDARD (Apr 25 2025 14:04:45) SOURCE_CODE_URL:github.com/MarlinFirmware/Marlin PROTOCOL_VERSION:1.0 MACHINE_TYPE:SideKick 747 KINEMATICS:Cartesian EXTRUDER_COUNT:1 UUID:5b3d61d6-80f8-41ed-bd8a-9c765f8d523d
<<< [09:49:06] Cap:SERIAL_XON_XOFF:0
<<< [09:49:06] Cap:BINARY_FILE_TRANSFER:0
<<< [09:49:06] Cap:EEPROM:1
<<< [09:49:06] Cap:VOLUMETRIC:1
<<< [09:49:06] Cap:AUTOREPORT_POS:0
<<< [09:49:06] Cap:AUTOREPORT_TEMP:1
<<< [09:49:06] Cap:PROGRESS:0
<<< [09:49:06] Cap:PRINT_JOB:1
<<< [09:49:06] Cap:AUTOLEVEL:1
<<< [09:49:06] Cap:RUNOUT:1
<<< [09:49:06] Cap:Z_PROBE:1
<<< [09:49:06] Cap:LEVELING_DATA:1
<<< [09:49:06] Cap:BUILD_PERCENT:1
<<< [09:49:06] Cap:SOFTWARE_POWER:0
<<< [09:49:06] Cap:TOGGLE_LIGHTS:0
<<< [09:49:06] Cap:CASE_LIGHT_BRIGHTNESS:0
<<< [09:49:06] Cap:EMERGENCY_PARSER:1
<<< [09:49:06] Cap:HOST_ACTION_COMMANDS:1
<<< [09:49:06] Cap:PROMPT_SUPPORT:1
<<< [09:49:06] Cap:SDCARD:1
<<< [09:49:06] Cap:MULTI_VOLUME:0
<<< [09:49:06] Cap:REPEAT:0
<<< [09:49:06] Cap:SD_WRITE:1
<<< [09:49:06] Cap:AUTOREPORT_SD_STATUS:1
<<< [09:49:06] Cap:LONG_FILENAME:1
<<< [09:49:06] Cap:LFN_WRITE:0
<<< [09:49:06] Cap:CUSTOM_FIRMWARE_UPLOAD:0
<<< [09:49:06] Cap:EXTENDED_M20:1
<<< [09:49:06] Cap:THERMAL_PROTECTION:1
<<< [09:49:06] Cap:MOTION_MODES:0
<<< [09:49:06] Cap:ARCS:1
<<< [09:49:06] Cap:BABYSTEPPING:1
<<< [09:49:06] Cap:EP_BABYSTEP:0
<<< [09:49:06] Cap:CHAMBER_TEMPERATURE:0
<<< [09:49:06] Cap:COOLER_TEMPERATURE:0
<<< [09:49:06] Cap:MEATPACK:0
<<< [09:49:06] Cap:CONFIG_EXPORT:0
<<< [09:49:06] ok P15 B7
[09:50:27] G28 XY. TABLE Went to the bak all the way, then made much grinding souns.
<<< [09:50:29] echo:busy: processing
<<< [09:50:31] echo:busy: processing
<<< [09:50:33] echo:busy: processing
<<< [09:50:35] echo:busy: processing
<<< [09:50:37] echo:busy: processing
<<< [09:50:39] echo:busy: processing
<<< [09:50:40] X:3.50 Y:-18.00 Z:15.00 E:0.00 Count X:350 Y:-1800 Z:3000
[09:57:13] M114
<<< [09:57:13] X:3.50 Y:-18.00 Z:15.00 E:0.00 Count X:350 Y:-1800 Z:3000
<<< [09:57:13] ok P15 B7
<<< [09:57:50] Reporting endstop status
<<< [09:57:50] X Min: open
<<< [09:57:50] Y Min: open
<<< [09:57:50] Z Min: TRIGGERED
<<< [09:57:50] filament: TRIGGERED
<<< [09:57:53] ok T:18.88 /0.00 B:19.78 /0.00 @:0 B@:0
/ gave me nothing on the console, maybe I didn’t understand correctly?
The Pi running “octoprint” I would be very invested to know how to do this with my sidekick 747. Is there a right up? I found this: UltiMaker Cura 5.8.1: Quick howto for Sidekick 747 with and OctoPrint/OctoLapse
The Lulzbot instruction that came with the machine pointed to Cura Lulzbot edition -4.13.17 -Exp-V1. that’s what I’m running on Mac mini m4- Sequa 15.5, and MacBook Intel Older os, but still runs same version of Ultimaker. The Gcode coming from Fusion 360 with Lulz SK 747 2.84 runs the printer very well, nice print, but no control for Gcode only rudimentary info from Monitor console. I can type in MCode Fusion will let me run multiple setups, so maybe a pause to insert nuts or change filament to something else?
I"m more familiar with HAAS inc panels or LinuxCNC for my gantry system… and a Lot more on the screen
@TheThresh, You have hijacked a topic about a LulzBot TAZ 6 to talk / ask about a Sidekick 747 and / or OctoPrint.
Please open a new topic either on this forum or at https://community.octoprint.org/. Myself (and others) will be happy to answer your questions.
As a courtesy to the author of this topic. Please move (or delete) your responses here to the new topic.
Right, I apologize , will do.
Thanks. Here are the responses from the console. Pics for the long responses. Code near the top of pic. M115 pic includes remainder code.
M92 >> OK P15 B4
M851>> echoProbe Z offset -1.2
OK P15 B4
M205 >> X:-19.00 Y:-258.00 Z:8.00 E:0.00
COUNT X:-1910 Y:-25929 Z:12800
G28 XY>> Pics of movement. New XY position in lower pic.
I haven’t commanded the M502 yet. Will wait for your reply. I’m working days thru friday, so my replies will be delayed until evenings. Thanks again. Soon applying " honey, i’m home … forever". Her reply likely, “where’s my print”! Lol.
You are on very outdated firmware.
Update to the latest 2.x firmware through CuraLE, then select the correct toolhead from the toolhead menu that will be available on the printer. Once you’re running the latest firmware, with the correct toolhead (Single Extruder 0.5) attempt the homing sequence again.
@Wrathernaut’s suggestion is what I was going to recommend as the final step once we understand why the hardware isn’t playing nice with the G28 Z location.
If you want to skip to that version of the firmware, I’m OK with that.
CuraLE 3.6.40 does not have the TAZ 6 Universal firmware version (it has 1.1.9.24 or 2.0.0.144).
You will need to install the latest version of CuraLE (4.13.16) to get the latest firmware (2.0.9.0.13).
Note that you can install both versions of CuraLE if you want.
Question on M994.
Did the machine come with an sdcard with info such as ESTEP settings?
I believe I have the original sdcasd files or, maybe, previous owner did a M993.
Just a guess at this point.
Firmware upgrade requires resetting (correct) esteps. Have I provided those to you? Is it wirhin the pic’s info?
Again, this isn’t my machine. The owner’s request was to see if I could get it running. Please consider my shoes as totally new to Lulzbot, 20 hours into this and may have zero need for the info gained.
Happy to leave a site thread on the topic, but, with the hijacking, it’s now likely to fall into too long didn’t read for other’s searches.
Thanks again.
The E-steps value is printed on the back of the toolhead. You posted a picture of it. You can also see it in the output of the M92 command and again, you posted a picture of it.
The other value you need to save is the Z-offset which can be seen from the output of the M851 command. You posted a picture of that one as well.’
I don’t believe any of the LulzBot builds of Marlin support the M994 (or M993).