Tool not showing on DWC
-
The extruder is plugged into E0 but it's not showing in DWC. I don't remember changing anything for this.
; Configuration file for Duet WiFi (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.2.3 on Fri Feb 26 2021 10:46:02 GMT-0500 (Eastern Standard Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"My Printer" ; 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 s1 is forward s0 backwards M569 P5 S1 M569 P6 S0 ; physical drive 1 goes forwards M569 P2 S1 ; physical drive 2 goes forwards M569 P3 S1 M569 P4 S1 ; physical drive 3 goes forwards M584 X0 Y5:6 Z2:4 ; set drive mapping M671 X-20:290 Y0:0 S5 ;leadscrews at left (connected to Z) and right (connected to E1) of X axis M208 X10:300 Y0:180 ;X carriage moves from -5 to 270, Y bed goes from 0 to 130 M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z400.00 E420.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 X600.00 Y600.00 Z50.00 E250.00 ; set accelerations (mm/s^2) M906 X800 Y800 Z800 E800 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 X310 Y310 Z180 S0 ; set axis maxima ; Endstops M574 X2 S1 P"!xstop" ; configure active-high endstop for high end on X via pin !xstop M574 Y2 S1 P"!ystop+!e0stop" ; configure active-high endstop for high end on Y via pin !ystop M574 Z2 S2 ; configure Z-probe endstop for high end on Z ; Z-Probe ; 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 M950 S0 C"duex.pwm5" G31 P500 X-31.5 Y7 Z1.28 ; set Z probe trigger value, offset and trigger height M557 X0:155 Y0:155 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 R0.135 C738.7 D1.34 S1.00 V23.5 ; enable 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 B4725 C7.060000e-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 R2.039 C177.8 D6.23 S1.00 V24.0 ; disable bang-bang mode for heater and set PWM limit M143 H1 S285 ; 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 T45 ; set fan 1 value. Thermostatic control is turned on ; Tools M563 P0 D0 H1 F0 S"Extruder" ; 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 M575 P1 S1 B57600 ;enable support for PanelDue T0 ; Select first tool
-
Hi,
I'm confused by your config.g file.
In your M569 commands you have drives 0, 2, 3, 4, 5 and 6.
The file says you are using a Duet WiFi.
The Duet WiFi doesn't have drive 6.
Are you actually using a Duet WiFi/Duex 5 combo?
That's the kind of information that is helpful for us to know.
In your M584 command you don't have an E setting so I don't think the tool has an extruder to reference thus the lack of display.
You can always check your config.g to see if the firmware reports anything wrong by executing, from the DWC console, M98 P"config.g".
Frederick
-
@fcwilt Thanks for the response, Frederick. I have a duex5 but failed to mention that, apologies. I added E0 to M584 and the tool is showing up correctly.
When I enter M98 P"config.g" into the DWC console I get 'Warning: Macro file config.g not found'. Correcting this sounds like it would be helpful for future issues.
-
@resh said in Tool not showing on DWC:
When I enter M98 P"config.g" into the DWC console I get 'Warning: Macro file config.g not found'. Correcting this sounds like it would be helpful for future issues.
I don't know why that would be. I'm using firmware 3.2.2 and that M98 command executes config.g as expected.
You sure you typed the filename correct?
Frederick
-
@fcwilt When I type M98 P"config.g" into the console box and hit send I get that message. I copy/pasted and got the same thing.
I spoke too soon about that tool working. When I go to retract the entire X axis moves. I put in this line and it moved left. G1 E-20 F300
I figured that should retract 20mm of filament at 300, instead the entire extruder moves left.
-
@resh said in Tool not showing on DWC:
@fcwilt When I type M98 P"config.g" into the console box and hit send I get that message. I copy/pasted and got the same thing.
Is your config.g file is in the System folder?
I spoke too soon about that tool working. When I go to retract the entire X axis moves. I put in this line and it moved left. G1 E-20 F300
I figured that should retract 20mm of filament at 300, instead the entire extruder moves left.
Post your current config.g file again and let me take a closer look.
Frederick
-
@fcwilt Changed E0 to E3, I got confused on the numbers but it's working now.
In the system tab my config folder is labeled "config.g.bak". There isn't anything with just config.g
-
@resh said in Tool not showing on DWC:
@fcwilt Changed E0 to E3, I got confused on the numbers but it's working now.
In the system tab my config folder is labeled "config.g.bak". There isn't anything with just config.g
Curious. I wonder how the board can boot without a config.g file.
Perhaps it is in another folder and the board finds it there, somehow.
Check your Macro folder.
Frederick
-
Curious. I wonder how the board can boot without a config.g file.
If no config.g file is found, then the RRF will use the config.g.bak
-
@siam said in Tool not showing on DWC:
Curious. I wonder how the board can boot without a config.g file.
If no config.g file is found, then the RRF will use the config.g.bak
I've been using Duets for several years and that fact escaped me.
Thanks very much.
Frederick
-
@siam Will this cause a problem somewhere down the line? I probably did something at some point and made that folder vanish.
-
@resh said in Tool not showing on DWC:
@siam Will this cause a problem somewhere down the line? I probably did something at some point and made that folder vanish.
Well you can do one of the following:
- rename config.g.bak to config.g
- create a new config.g and copy the contents of config.g.bak into it.
Frederick
-
After renaming config.g please send M98 P"config.g" again.
Also send M122 and report the results of that.