M84 error after upgrade to 3.3

fcwilt

@mringersoll said in M84 error after upgrade to 3.3:

Also why is the Z axis staying up so high the nozzle is about 6mm from the bed. and during probing i does not go down much at all before it goes back up the probe is triggering way early not even close to the bed when I home the printer the probe works as expected don't get it.

We would need to see your homing files first.

Have you made any changes to your config file? If so post it again.

Frederick

Phaedrux

If you change that line to M84 E0 that should solve that error, though I'm not sure it's related to your homing problem. For that we would need to see your homing files and start gcode as well.

mringersoll

@phaedrux Ok here are the homing files but my problem is the nozzle stays like 3mm above bed when it prints.

; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Mon Dec 06 2021 04:14:12 GMT-0600 (Central Standard Time)
G91 ; relative positioning
G1 H2 Z5 F9000 ; lift Z relative to current position
G1 H1 X-243 Y-241 F2400 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 H2 X5 Y5 F9000 ; go back a few mm
G1 H1 X-243 Y-241 F600 ; move slowly to X and Y axis endstops once more (second pass)
G90 ; absolute positioning
G1 X59 Y27 F9000 ; go to first bed probe point and home Z
G30 ; home Z by probing the bed

; Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 Z5 F150 ; lift Z relative to current position
;G90 ; absolute positioning

; homex.g
; called to home the X axis
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Mon Dec 06 2021 04:14:12 GMT-0600 (Central Standard Time)
G91 ; relative positioning
G1 H2 Z5 F9000 ; lift Z relative to current position
G1 H1 X-240 F2400 ; move quickly to X axis endstop and stop there (first pass)
G1 H2 X5 F9000 ; go back a few mm
G1 H1 X-240 F600 ; move slowly to X axis endstop once more (second pass)
G1 H2 Z-5 F9000 ; lower Z again
G90 ; absolute positioning

; homey.g
; called to home the Y axis
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Mon Dec 06 2021 04:14:12 GMT-0600 (Central Standard Time)
G91 ; relative positioning
G1 H2 Z5 F9000 ; lift Z relative to current position
G1 H1 Y-240 F2400 ; move quickly to Y axis endstop and stop there (first pass)
G1 H2 Y5 F9000 ; go back a few mm
G1 H1 Y-240 F600 ; move slowly to Y axis endstop once more (second pass)
G1 H2 Z-5 F9000 ; lower Z again
G90 ; absolute positioning

; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Mon Dec 06 2021 04:14:12 GMT-0600 (Central Standard Time)
G91 ; relative positioning
G1 H2 Z5 F9000 ; lift Z relative to current position
G90 ; absolute positioning
G1 X59 Y25 F9000 ; go to first probe point
G30 ; home Z by probing the bed

; Uncomment the following lines to lift Z after probing
;G91 ; relative positioning
;G1 Z5 F150 ; lift Z relative to current position
;G90 ; absolute positioning

Phaedrux

@mringersoll said in M84 error after upgrade to 3.3:

; Z-Probe
M558 P5 C"^!zprobe.in" H5 F240 T9000 ; set Z probe type to switch and the dive height + speeds
G31 P1000 X-47 Y-11 Z1.90 ; set Z probe trigger value, offset and trigger height
M557 X12:193 Y16:214 S25 ; define mesh grid

What type of Z probe do you have?

Have you calibrated the z trigger height recently?
https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe

What do you have in your slicer start gcode? I don't see anything wrong with your homing files.

mringersoll

@phaedrux Hello Again
I am using an EZabl for my probe and calibration about 2 days ago. I am using an Ender 3 Cura or simplfy3d slicer i tried to copy and paste to get my cura Start G code but does not work.

Mike

mringersoll

@phaedrux Hello
Here is the start gcode from my slicer

;M75 ; Start Print Timer and Engage Fil Sensor if USB Printing
G92 E0 ; Reset Extruder distance to 0
G1 E-2 ; Retracts filament to prevent blobs during probing
M84 E ; Disable E Motor for probe accuracy on direct drive systems
G28 ; home all axes
G28 Z ; home Z to get more accurate Z position
G29; EZABL mesh generation
G4 S10; wait for heaters to recover

M117 Purge extruder
G92 E0 ; reset extruder
G1 Z1.0 F3000 ; move z up little
G1 X0.16 Y26 Z0.3 F5000.0 ; move to start-line position
G1 X0.16 Y110.0 Z0.3 F750.0 E15 ; draw 1st line
G1 X0.6 Y110.0 Z0.3 F3000.0 ; move to side a little
G1 X0.4 Y13 Z0.3 F730.0 E12 ; draw 2nd line
G92 E0 ; reset extruder
G1 Z1.0 F3000 ; move z up little

M117 Printing.....

fcwilt

@mringersoll said in M84 error after upgrade to 3.3:

@phaedrux Hello
Here is the start gcode from my slicer

;M75 ; Start Print Timer and Engage Fil Sensor if USB Printing
G92 E0 ; Reset Extruder distance to 0
G1 E-2 ; Retracts filament to prevent blobs during probing
M84 E ; Disable E Motor for probe accuracy on direct drive systems
G28 ; home all axes
G28 Z ; home Z to get more accurate Z position
G29; EZABL mesh generation
G4 S10; wait for heaters to recover

M117 Purge extruder
G92 E0 ; reset extruder
G1 Z1.0 F3000 ; move z up little
G1 X0.16 Y26 Z0.3 F5000.0 ; move to start-line position
G1 X0.16 Y110.0 Z0.3 F750.0 E15 ; draw 1st line
G1 X0.6 Y110.0 Z0.3 F3000.0 ; move to side a little
G1 X0.4 Y13 Z0.3 F730.0 E12 ; draw 2nd line
G92 E0 ; reset extruder
G1 Z1.0 F3000 ; move z up little

M117 Printing.....

Where did that code come from?

Frederick

mringersoll

@fcwilt Hello That is the Start gcode from my Slicer like i was asked for.
Also as i said before there is something triggering my Z probe way off the print bed i mean the probe is nowhere near the bed when it triggers. When i run G28 the probe works as expected goes close to bed, anything after the probe might get 4mm from bed so something is messing with the Z Probe.

Mike

fcwilt

@mringersoll said in M84 error after upgrade to 3.3:

Hello That is the Start gcode from my Slicer like i was asked for.

Mike

You mentioned Cura and Simplify3D as the slicers you use. Is that correct?

Which slicer was the code you post from?

Was this code you entered in the user code location in the slicer or was it completely generated by the slicer?

Thanks.

Frederick

mringersoll

@fcwilt Hello
slicer generated with the addition for mesh bed probing

mringersoll

@fcwilt oh sorry Cura 4.12.1

mringersoll

@fcwilt Hello
well not sure how to fix it but when i turn on the printer in the console menu of my Paneldue there are two lines back to back that say bad model perimeter it is at the beginning seems to be after the network stuff than wifi starts so how do i start all over with this firmware and such.

fcwilt

@mringersoll said in M84 error after upgrade to 3.3:

two lines back to back that say bad model perimeter it is at the beginning seems to be after the network stuff than wifi starts so how do i start all over with this firmware and such.

I would suspect your M307 commands in the heater section.

The first is M307 H0 B1 S1.5. The S parameter is limited to 0 to 1.

The second is M307 H1 B0 S0.00. While the S parameter is within range it doesn't make sense.

Try setting them both to 1.0 and check again.

Frederick

Phaedrux

@mringersoll said in M84 error after upgrade to 3.3:

I am using an EZabl for my probe and calibration about 2 days ago.

I'd suggest going through the calibration again. See if the trigger height is what it should be. I don't see anything in the gcode that would cause it to trigger so high. so it may be an issue with the probe. Recalibrating would let you test it's trigger height.

mringersoll

@fcwilt Hello
well if this is not in the 1.3,1.5 Range i get a heater error that says heater not heating at a fast enough rate.
The first is M307 H0 B1 S1.5. how do i solve that problem.

Mike

mringersoll

@phaedrux hello i have recalibrated many times still same problem

Mike

fcwilt

@mringersoll said in M84 error after upgrade to 3.3:

@fcwilt Hello
well if this is not in the 1.3,1.5 Range i get a heater error that says heater not heating at a fast enough rate.
The first is M307 H0 B1 S1.5. how do i solve that problem.

Mike

I was just trying to determine if those two error messages were coming from these two commands.

The M307 values shown indicate the heater tuning had not been done so the message about not heating fast enough may go away once tuning is complete.

Frederick

mringersoll

@fcwilt Hello so how is the heater tuning done never done it before please explain.

fcwilt

@mringersoll said in M84 error after upgrade to 3.3:

@fcwilt Hello so how is the heater tuning done never done it before please explain.

In the docs for M303 there is a link to heater tuning in greater detail:

M303 - Run Heater Tuning

Frederick