Duex5 Fan Settings?
-
the p0 output broke yesterday on my duet wifi. I have set the output from p0 to duex Fan3 in the Reprap Config, but it doesn't work. Did I do something wrong ?
; Fans
M950 F0 C“duex.fan3“ Q500
M106 P0 S0 H-1 -
Post your full config.g
Also M122 and M98 P"config.g" can be enlightening.What do you mean by p0?
-
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.01(RTOS) running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DGM-956GU-DJ3S0-7JKFJ-3SD6M-1TFHG
Used output buffers: 3 of 20 (6 max)
=== RTOS ===
Static ram: 28476
Dynamic ram: 96284 of which 36 recycled
Exception stack ram used: 320
Never used ram: 5956
Tasks: NETWORK(ready,400) HEAT(blocked,1248) MAIN(running,3508)
Owned mutexes:
=== Platform ===
Last reset 00:02:44 ago, cause: power up
Last software reset at 2021-01-16 00:39, reason: User, spinning module GCodes, available RAM 5956 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 31.1, current 36.1, max 36.4
Supply voltage: min 24.1, current 24.2, max 24.3, under voltage events: 0, over voltage events: 0
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Driver 5: standstill, SG min/max not available
Driver 6: standstill, SG min/max not available
Driver 7: standstill, SG min/max not available
Driver 8: standstill, SG min/max not available
Driver 9: standstill, SG min/max not available
Expansion motor(s) stall indication: no
Date/time: 2021-01-16 11:27:28
Slowest loop: 14.09ms; fastest: 0.07ms
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 240, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
=== GCodes ===
Segments left: 0
Stack records: 2 allocated, 0 in use
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
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 15.54ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8- WiFi -
Network state is running
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.25
WiFi MAC address 8c:aa:b5:d5:7e:45
WiFi Vcc 3.35, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 25360
WiFi IP address 192.168.0.67
WiFi signal strength -72dBm, reconnections 0, sleep mode unknown
Socket states: 0 0 0 0 0 0 0 0
=== Expansion ===
DueX I2C errors 0
- WiFi -
-
M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 276C.
Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 558C.
Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 276C.
Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 558C.
Error: Bad command: /M141 H3
Error: Bad command: /M305 P2 R4700 T100000 B3950
Warning: M950 command is not supported
Warning: M950 command is not supported
Warning: M950 command is not supported -
i mean fan 0 for the parts cooling. on the duet it is broken and wanted to use it on the duex5
-
M950 is a version 3 command
you are running version 2 of the firmware
-
yesterday i uploaded the firmware 3.xx and installed it with m997 but vision remains in the setting by 2.01
-
@joe92 said in Duex5 Fan Settings?:
but vision remains in the setting by 2.01
You first have to do the update to 3.0 then further
-
I update the board and try again
-
from 3.0 I get this message "error: in-application programming binary" duet2cambinedlAP.bin "Not found"
-
@joe92
Take the full release zip file "Duet2and3Firmware-3.0.zip" and try it again.... -
Just to ensure you have a clean install with all the files, and you still have access to DWC. Upload these 3 zip files, one at a time. Don't extract them. Reboot after each.
https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.0/Duet2and3Firmware-3.0.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.2/Duet2and3Firmware-3.2.zip
-
ok everything works so far but my inductive sensor (PL-08N) doesn't
-
; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.1 on Fri Jan 15 2021 23:22:23 GMT+0100 (Mitteleuropäische Normalzeit); General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M555 P2 ; Set firmware compatibility to look like Marlin
M550 P"Voron V2" ; 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; G29 Mesh
M557 X55:295 Y30:270 S30 ; S30 for high density, S40 for testing; Drives
M569 P0 S1 ; X Motor goes backwards
M569 P1 S1 ; Y Motor goes backwards
M569 P3 S1 ; Extruder Motor 0 goes forwards (BMG)
M569 P5 S1 ; Z1 goes backwards
M569 P6 S0 ; Z2 goes forwards
M569 P7 S1 ; Z3 goes forwards
M569 P8 S0 ; Z4 goes backwardsM92 X80 Y80 Z400 ; Steps per mm
M92 E415 ; Steps per mm (BMG) (1.8deg)
M350 E16 I1 ; Configure microstepping with interpolation
M350 X16 Y16 Z16 I1 ; Configure microstepping with interpolation
M203 X18000 Y18000 E9000 Z4000 ; Set maximum speeds (mm/min) for 2.1 only (300mm/s max)
M201 X3000 Y3000 E6000 Z500 ; Set accelerations (mm/s^2)
M566 X900 Y900 E1200 Z150 ; Set maximum instantaneous speed changes (mm/min)
M98 P"/macros/print_scripts/xy_current_high.g" ; Set XY Motor Currents
M98 P"/macros/print_scripts/e_current_high.g" ; Set Extruder Motor Currents
M98 P"/macros/print_scripts/z_current_high.g" ; Set Z Motor Currents (must come after extruder, because on the extruder headers)
M84 S0 ; Set idle timeout, never time out; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X350 Y350 Z300 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; Inductive Leveling Sensor
M98 P"/macros/probe_scripts/activate_z_probe.g" ; activate the Z probe
M98 P"/macros/probe_scripts/activate_z_switch.g" ; activate the Z switch; Z-Axis Stepper Leveling Configuration
M584 X0 Y1 Z5:6:7:8 ; 4 motors; duex 5, 6, 7, 8
M671 X403:403:-56:-56 Y356:-66:-66:356 S20 ; belts in all 4 corners; 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 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 B3950 ; 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 S280 ; set temperature limit for heater 1 to 280C; Fans
M950 F0 C"duex.fan3" Q500 ; create fan 0 on pin duex.fan3 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
M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency
M106 P2 S1 H1 T45 ; set fan 2 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
M575 P1 S1 B57600 ; enable support for PanelDue; Enable config-override.g
;M501; Allow Movement of Axis that have not been homed
M564 H0 -
0:/macros/Probe_Scripts/activate_z_probe.g
M558 P5 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to switch and the dive height + speeds
G31 P25 X0 Y-23.50 Z6.500 ; set Z probe trigger value, offset and trigger height0:/macros/Probe_Scripts/activate_z_switch.g
M558 P5 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to switch and the dive height + speeds
G31 P1000 X0 Y0 Z1.53 ; Setup Offsets for Z Switch -
I tried the pin assignment but no difference. It doesn't matter whether the cables from the sensor are connected to the board, this error appears "Error: Z probe already triggered at start of probing move". the sensor is permanently set to 1000 in the web control. I don't know what to do next
-
To invert the switch signal you add a ! to the pin name.
Ex: C"^!zprobe.in"
-
the inverting worked but I get this message "G32
Error: Z probe was not triggered during probing move "; bed.g
; called to perform automatic bed compensation via G32
; setup for quad belt gantryM561 ; Clear any existing bed transform
G28 ; homeM98 P"/macros/probe_scripts/activate_z_probe.g" ;activate inductive z-probe
M401 ; Deploy probe - Deployprobe.g
; Probe bed at these 4 points:
G30 P0 X65 Y40 Z-9999
G30 P1 X65 Y260 Z-9999
G30 P2 X285 Y260 Z-9999
G30 P3 X285 Y40 Z-9999 S4M402 ; Retract Probe - Retractprobe.g
M561 ; Clear any existing bed transform
G28 Z ; Home Z AxisM98 P"/macros/probe_scripts/activate_z_probe.g" ;activate inductive z-probe
-
the z-probe works in single commands, but not in the g32 / g29
-
the pin assignment of the probe was a little different after the update. everything works now will update the board regularly from now on XD . many thanks