Extruder tool configured but not displayed
-
I'm having a weird problem right now, I just went through the rep-rap configuration tool and configured my extruder (or so I thought). On DWC it displays my bed, but not my extruder tool.
I looked at my configuration.g file, and my tool seems to be listed there, but it's still not showing up on DWC. I also triple checked my wiring, and both the motor and thermister for my hotend seem to be plugged into the correct locations. I'm probably missing something obvious. I am very new to the Duet scene, any help is appreciated. ```
code_text; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.2.3 on Wed Jul 28 2021 23:43:42 GMT-0600 (Mountain Daylight Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Wilson 2" ; 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 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 E107.00 ; set steps per mm M566 X900.00 Y30.00 Z30.00 E120.00 ; set maximum instantaneous speed changes (mm/min) M203 X6000.00 Y6000.00 Z360.00 E1200.00 ; set maximum speeds (mm/min) M201 X3000.00 Y1000.00 Z3000.00 E3000.00 ; set accelerations (mm/s^2) M906 X1200 Y1200 Z1200 E1200 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 X200 Y300 Z180 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 S1 P"zstop" ; configure active-high endstop for low end on Z via pin zstop ; Z-Probe M558 P0 H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed M557 X15:215 Y15:195 S20 ; define mesh grid ; Heaters M308 S0 P"bedtemp" Y"thermistor" T100000 B3950 ; 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.00 ; enable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S60 ; set temperature limit for heater 0 to 60C M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.06e-8 ; 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 S245 ; set temperature limit for heater 1 to 245C ; Fans ; Tools M563 P0 S"Extruder" D0 H1 F-1 ; 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 -
What version of firmware and does your version of DWC match?
-
@phaedrux Just checked, I'm running 3.3.0 on both. Or at least I'm assuming, the M115 command comes back with 3.3 for the board , and the version of my DWC is 3.3.0 .
-
Can you send M122 and M98 P"config.g" in the Gcode console in DWC and post the results?
What happens if you send
T0in the console? -
@phaedrux Ok the results for M122 were:
7/29/2021, 2:26:17 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: 08DLM-996RU-N85S4-7JKD4-3SS6K-TA8RQ
Used output buffers: 3 of 24 (11 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 74504 of which 128 recycled
Never used RAM 15908, free system stack 184 words
Tasks: NETWORK(ready,11.0%,252) HEAT(delaying,0.0%,336) Move(notifyWait,0.1%,364) MAIN(running,84.2%,407) IDLE(ready,4.7%,29), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:00:19 ago, cause: power up
Last software reset at 2021-07-29 00:31, reason: User, GCodes spinning, available RAM 15908, 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
Step timer max interval 0
MCU temperature: min 31.0, current 34.5, max 34.6
Supply voltage: min 23.7, current 23.8, max 23.9, 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-07-29 14:26:16
Cache data hit count 744932926
Slowest loop: 5.35ms; fastest: 0.16ms
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.1ms, 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.57ms; 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.26
WiFi MAC address f4:cf:a2:66:ad:f9
WiFi Vcc 3.31, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 24200
WiFi IP address 192.168.1.16
WiFi signal strength -62dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
The results from M98 P"config.g" were:
7/29/2021, 2:30:01 PM M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Error: in file macro line 58 column 28: M563: expected number after 'F'
Error: Tool 0 not found
Error: Tool 0 not foundIf I send T0 in the console it just reads back:
7/29/2021, 2:32:14 PM T0 - WiFi -
-
@printer_wrangler said in Extruder tool configured but not displayed:
Error: in file macro line 58 column 28: M563: expected number after 'F'
Error: Tool 0 not found
Error: Tool 0 not foundWell I think this is the problem. I had wondered about using F-1 in your tool definition.
M563 P0 S"Extruder" D0 H1 F-1 ; define tool 0
Remove the F-1 or change it to the fan you actually want to use as the part cooling fan. You don't have any defined, so I guess you don't have a part cooling fan? If that's the case just remove F-1.
If that works and the config tool is the one that generated the F-1 then we'll have to look into that.
-
@phaedrux @phaedrux Well thank you so much, that worked. It looks like in the reprap configuration tool I had left a part cooling fan, and as you said I don't have one hooked up at the moment (I need to print a new mount and air duct first). In subsequent configurations I haven't had the problem, it now reads F0 instead of F-1 by default, so I think it was my fault all along. Are there any resources you recommend for learning more about the g code commands, particularly the diagnostic commands? It looks like knowledge in that area is going to be important moving forward with a duet controlled printer.
-
https://duet3d.dozuki.com/Wiki/Gcode Has details on every gcode used in RepRapFirmware. Bookmark it or always just have it open in a tab.
-
@phaedrux Ok will do, thanks again!
