Diag flashing
-
@Phaedrux m98 missing parameter ‘p’
-
@Phaedrux said in Diag flashing:
M98 P"config.g"
That's the full command.
M98 calls a macro defined by P"whatever macro name"
-
; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Sat Mar 06 2021 22:50:41 GMT-0700 (Mountain Standard Time); General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"SWX1 Duet" ; set printer name
M669 K1 ; select CoreXY mode; Network
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet; Drives
M569 P0 S1 ; physical drive 0 goes forwards
M569 P1 S1 ; physical drive 1 goes forwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S1 ; physical drive 3 goes forwards
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 E415.00 ; 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 X900 Y900 Z900 E900 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X300 Y300 Z400 S0 ; set axis maxima; Endstops
M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop
M574 Z1 S2 ; configure Z-probe endstop for low end on Z; Z-Probe
M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X0 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 X15:215 Y15:195 S20 ; 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 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
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 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S300 ; set temperature limit for heater 1 to 300C; 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 S0 H1 T45 ; set fan 1 value. Thermostatic control is turned on
M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency
M106 P2 S0 H1 T45 ; set fan 2 value. Thermostatic control is turned on; Tools
M563 P1 D0 H1 F0 ; define tool 1
G10 P1 X0 Y0 Z0 ; set tool 1 axis offsets
G10 P1 R0 S0 ; set initial tool 1 active and standby temperatures to 0C; Custom settings are not defined
-
@Phaedrux guess im not fallowing ,
-
@anthony1m said in Diag flashing:
M669 K1 ; select CoreXY mode
Is your machine CoreXY? Because you have it set as such. This will move both motors for an X or Y move.
Edit: please post your homing files, as @Phaedrux asked you to.
Ian
-
@anthony1m said in Diag flashing:
@Phaedrux guess im not fallowing ,
In the console tab send this command
M98 P"config.g"and copy and paste the response here. It might show some errors or messages. -
@Phaedrux said in Diag flashing:
M98 P"config.g"
3/10/2021, 7:27:21 PM M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled -
This post is deleted! -
@anthony1m That looks good. No errors anyway.
-
@anthony1m said in Diag flashing:
WiFi firmware version 1.23
It looks like the wifi server didn't get updated.
Try uploading the full release zip file again to the system tab in DWC. Just to make sure everything is correct.
https://github.com/Duet3D/RepRapFirmware/releases/download/3.2.2/Duet2and3Firmware-3.2.2.zip
-
Will need to see your homing files to say why it's moving the way it's moving during homing. Post homeall.g homex.g homey.g homez.g and bed.g if you've set that up yet.
-
@Phaedrux I'm close3/10/2021, 8:10:02 PM m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later
Board ID: 08DLM-996RU-N85S4-7JTD6-3SJ6R-KA9BR
Used output buffers: 3 of 24 (10 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 73268 of which 40 recycled
Never used RAM 15312, free system stack 189 words
Tasks: NETWORK(blocked,186) HEAT(blocked,308) MAIN(running,457) IDLE(ready,20)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:01:47 ago, cause: software
Last software reset at 2021-03-10 20:08, reason: User, GCodes spinning, available RAM 15068, slot 2
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
MCU temperature: min 31.3, current 32.0, max 32.4
Supply voltage: min 21.9, current 22.1, max 22.3, under voltage events: 0, over voltage events: 0, power good: yes
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-03-10 20:10:01
Cache data hit count 129951247
Slowest loop: 4.40ms; fastest: 0.21ms
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 3.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: 15.91ms; fastest: 0.00ms
Responder states: HTTP(0) 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.23
WiFi MAC address 48:3f:da:88:d4:72
WiFi Vcc 3.38, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 22120
WiFi IP address 192.168.0.197
WiFi signal strength -36dBm, mode none, reconnections 0, sleep mode modem
Clock register ffffffff
Socket states: 0 0 0 0 0 0 0 0
- WiFi -
-
@Phaedrux I think you can check this as solved . I will work on it and if I run into any issued Ill read the information and ask for help if I need it. You guys are awesome thank you.
-
@Phaedrux well this happened again except now the diag is on solid and windows disconnected right away. it was fine middle of a print it dropped connection and does nothing.
-
@Phaedrux any ideas Its on a new meanwell ps also , why this board keeps having diag issues it brand new.
-
https://duet3d.dozuki.com/Wiki/What_to_do_if_your_Duet_won't_respond
Can you run through this guide and see how far you can get?
-
@Phaedrux yes thank you I am working on that now.
-
"Error reading device descriptor" This is as far as I get, I can't get past that. That's the one I was working last night before I came back here. my mac or rpi 4 wont see it either usb not recognized with or with a sd card different ports and cables and restart of the machine.
-
@Phaedrux Had it dialed in was producing some great prints, Then just in the middle stopped and could not connect again.
-
When and where did you purchase the Duet?
What LEDs light up when connected to VIN or USB?
