M84 error after upgrade to 3.3
-
Hello everything worked fine when i was at ver 3.22 than went to ver 3.3 and now things are messed up
get a M84 error tells me the line in the Gcode and all but how do i look at the error. also now the nozzle does not go down close to print bed stays about 10 mm up.Thank You
Mike
-
Can you provide us with more information?
Can you share your full config.g and the results of sending M122 and M98 P"config.g" ?
Where do you see the M84 error?
For your nozzle problem if may help to share your homing files, bed.g, start gcode, etc. -
@phaedrux
Ok been a while went back to 3.2.2 and all is fine, anyway how do i post the info you are requesting and i will reinstall 3.3 and post the info sound good right after the print that is going is done.Mike
-
@mringersoll said in M84 error after upgrade to 3.3:
how do i post the info you are requesting
Copy and paste.
-
@phaedrux Ok here we go The Error comes after i start print either during the Bed Probing or right after.
12/9/2021, 3:44:02 PM M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later
Board ID: 08DGM-9T6BU-FG3S8-6J9DD-3S86R-KBKHF
Used output buffers: 6 of 24 (16 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 75072 of which 0 recycled
Never used RAM 15468, free system stack 174 words
Tasks: NETWORK(ready,12.0%,246) HEAT(delaying,0.0%,330) Move(notifyWait,0.1%,364) MAIN(running,86.4%,461) IDLE(ready,1.5%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:01:02 ago, cause: power up
Last software reset time unknown, reason: User, GCodes spinning, available RAM 15468, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 18.9, current 24.0, max 24.2
Supply voltage: min 24.3, current 24.4, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, standstill, SG min/max not available
Driver 1: position 0, standstill, SG min/max not available
Driver 2: position 0, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2021-12-09 15:44:01
Cache data hit count 2273262020
Slowest loop: 5.70ms; fastest: 0.17ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 7.2ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 16.18ms; fastest: 0.00ms
Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8- WiFi -
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.26
WiFi MAC address b4:e6:2d:60:31:eb
WiFi Vcc 3.28, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 24792
WiFi IP address 10.0.0.169
WiFi signal strength -64dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
Config.g
; Configuration file for Duet WiFi (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Mon Dec 06 2021 04:14:12 GMT-0600 (Central Standard Time); General preferences
M575 P1 S1 B57600 ; enable support for PanelDue
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"My Hacked Ender 3" ; set printer name; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet; Drives
M569 P0 S0 ; physical drive 0 goes backwards
M569 P1 S0 ; physical drive 1 goes backwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S0 ; physical drive 3 goes backwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E97.18 ; set steps per mm
M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
M906 X850 Y850 Z850 E900 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Axis Limits
M208 X-3 Y-3 Z0 S1 ; set axis minima
M208 X235 Y235 Z255 S0 ; set axis maxima; Endstops
M574 X1 S1 P"xstop" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin ystop
M574 Z1 S2 ; configure Z-probe endstop for low end on Z; 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; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B1 S1.50 ; enable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S150 ; set temperature limit for heater 0 to 150C
M308 S1 P"e0temp" Y"thermistor" T100000 B4138 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S0.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S280 ; set temperature limit for heater 1 to 280C; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T65 ; set fan 1 value. Thermostatic control is turned on; Tools
M563 P0 D0 H1 F0 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C; Custom settings are not defined
; Miscellaneous
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss12/9/2021, 3:47:32 PM M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Error: bad model parameters
Error: bad model parameters - WiFi -
-
@mringersoll said in M84 error after upgrade to 3.3:
The Error comes after i start print either during the Bed Probing or right after.
Yes, and what exactly is the error?
-
@phaedrux sorry here is the error also the print head is like 6mm off the bed when it starts printing but for some reason the display says it is at.30 for Z axis i am really confused with this please help 3.2.2 works fine so maybe just go back to 3.2.2 and stay there i guess.
12/10/2021, 3:04:49 PM Error: in GCode file line 20 column 6: M84: expected number after 'E'
same error just different lines and columns depends the file i choose for printing.Mike
-
@mringersoll said in M84 error after upgrade to 3.3:
12/10/2021, 3:04:49 PM Error: in GCode file line 20 column 6: M84: expected number after 'E'
same error just different lines and columns depends the file i choose for printing.Please post that line of code which is generating the error.
Frederick
Printers: A FT-5 with the 713 upgrade bits, a custom MarkForged style, a small Utilmaker style, a small CoreXY from kit and a E3D MS/TC setup. Various hotends. Using Duets (2 and 3) running 3.4.6
-
@fcwilt
so how do i get to that line of code to post it? -
@fcwilt
and what do i use to open it to get the lineThanks
-
@mringersoll said in M84 error after upgrade to 3.3:
and what do i use to open it to get the line
Thanks
It's a text file. You can open it in most any text editor - one with line numbers would be helpful.
Or you can also upload to the SYSTEM folder in the DWC and open it there.
Frederick
-
@fcwilt
M84 E ; disable for more accurate probing,is what is says.
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.Mike
-
@mringersoll said in M84 error after upgrade to 3.3:
M84 E ; disable for more accurate probing,is what is says.
Well there is why you are getting an error. Whatever is generating that line of code is not putting the number(s) after the E.
If you use to work possibly the older firmware didn't handle that error properly or perhaps in the absence of any number(s) it used a default.
Frederick
-
@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
-
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.
-
@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 -
@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 gridWhat 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_probeWhat do you have in your slicer start gcode? I don't see anything wrong with your homing files.
-
@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
-
@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.....
-
@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
