M84 error after upgrade to 3.3
-
@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 recoverM117 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 littleM117 Printing.....
Where did that code come from?
Frederick
-
@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
-
@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
-
@fcwilt Hello
slicer generated with the addition for mesh bed probing -
@fcwilt oh sorry Cura 4.12.1
-
@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. -
@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
-
@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.
-
@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
-
@phaedrux hello i have recalibrated many times still same problem
Mike
-
@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
-
@fcwilt Hello so how is the heater tuning done never done it before please explain.
-
@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:
Frederick