@dc42 it's printing at the minute, so I don't want to go poking around the wiring. I will take a good look at the wiring later, and if I find an obvious issue, I won't reply to this thread! The fact it is not expected behaviour at least points me in a good enough direction to continue debugging.
Thanks for the assist.
A further point of clarification:
OUT3 is connected to a 12v water pump, but only the PWM & Tach signals are connected. +12 is direct from an external PSU.
OUT4 is connected to the 24v FAN (all 4 wires).
Neither device shows a Tach signal when VIN is selected. Both show a tach signal when 12v is selected.
@dc42 yes. the fan is on OUT4. the jumper is set to VIN.
@JabawokJayUK specifically: 9GA0624P6G001
Hello all, Is it expected behaviour to lose the tacho signal on a 4-wire fan if you switch from the onboard 12v to VIN? on OUT3/4 on the DUET 3 Mini 5? I am using 24v 4 wire fans for a circulation system and if I use the 12v, I get a tacho signal, but if I switch to VIN, I lose the tacho signal.
Many thanks
@sebkritikel I'm sure thats what happened to me initially, which led me down the rabbit hole. Appreciated.
I had a little play this morning and the original "positive" offset works, although I was 3mm out. After tweaking the offset I can get the tool heads to react as expected:
T0
G1 X254 Y250 Z1
T1
G1 X254 Y250 Z1
Should I have to replicate this offset in my cura config or is the duet offset going to handle this automatically? I'm thinking specifcally of these X/Y offset setting in the Nozzle settings tabs:
I have 2 fixed tools on a single axis, E0 and E1. Assuming that E0 is the HRP as per the documentation, my E1 is exactly +13.4mm away on the X Axis.
If I set the tool E1 to have an offset of X13.4 it ends up 13.4mm offset in the wrong direction, if I set it it -13.4, it ends up 13.4mm out in the correct direction. like it added 13.4 to 13.4 in the firmware?
Its almost as if the offset wants to be X0 but then I have no idea how it knows where E1 is?
; Tool 0 (Extruder 0)
M563 P0 S"Extruder0" D0 H1 ; 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
; Tool 1 (Extruder 1)
M563 P1 S"Extruder1" D1 H2 ; define tool 1
G10 P1 X-13.4 Y0 Z0 ; set tool 1 axis offsets
G10 P1 R0 S0 ; set initial tool 1 active and standby temperatures to 0C
Here in the image you can see the previous positive offset marks in the glue stick to the left and the same offset set as a negative in blue. Black is E0.
Firmware is 3.4.5
@jay_s_uk yeah tried that. i'm a dumbass, i had the 2nd tool mapped to the first tool extruder in the config. hence why i was scratching my head 
Ok, so I'm stumped here
E0 is able to be extruded just fine with with buttons on the PanelDue or the web gui, but not E1? if I set E1 active, it still extrudes E0.
What basic thing am I missing here?
Cheers
@Phaedrux I have previously tried all of those options. Dedicated 2.4ghz SSID, and multiple tails / multiple antennas (2-10 dBi) both directly connected or with extensions to locate the antenna in better air. Its not a physical issue.
Its either a bad board or a firmware issue, and the solution to both is to move to wired. I didn't want it to be connected over wifi initially, as I intended to use it in SBC mode, so it wasn't an issue, and I had this wifi version spare. Still, now I intend not to use the SBC so replacing it with a wired version is the logical option.
@Phaedrux Unfortunately, this does not fix it. Today, I booted the machine after being off all night. It came up and connected to the SSID, acquired its IP without issue and I successfully connected to the web GUI. Within 30s it dropped the wifi and was unable to connect again with the panelDue showing it no longer had a connection to the wifi:
I ran M552 S0/1 as requested from the Panel Due and that leaves it in the following state:
ERROR: WiFi module reported Unexpected WiFi state 'idle' while trying to connect
As you can see from the image below, the ariel is in plenty of space and the closest access point is <1m away offering coverage for a/c/b/g/n/ specifications.
@jay_s_uk M122 Output:
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.5 (2022-11-30 19:41:16) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: 7MHB6-B296U-D65J0-40KM0-3103Z-H23WT
Used output buffers: 3 of 40 (21 max)
=== RTOS ===
Static ram: 103652
Dynamic ram: 111168 of which 0 recycled
Never used RAM 26892, free system stack 194 words
Tasks: NETWORK(notifyWait,11.6%,215) HEAT(notifyWait,0.0%,342) Move(notifyWait,0.0%,363) CanReceiv(notifyWait,0.0%,797) CanSender(notifyWait,0.0%,336) CanClock(delaying,0.0%,348) TMC(notifyWait,1.2%,115) MAIN(running,86.1%,425) IDLE(ready,0.3%,30) AIN(delaying,0.8%,263), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:01:39 ago, cause: power up
Last software reset at 2023-03-24 09:38, reason: User, GCodes spinning, available RAM 26892, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU revision 3, ADC conversions started 99432, completed 99432, timed out 0, errs 0
Step timer max interval 1470
MCU temperature: min 18.9, current 23.7, max 23.9
Supply voltage: min 24.0, current 24.1, max 24.1, 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
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, read errors 0, write errors 0, ifcnt 9, reads 8994, writes 9, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 9, reads 8993, writes 9, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 9, reads 8993, writes 9, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 9, reads 8993, writes 9, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 9, reads 8993, writes 9, timeouts 0, DMA errors 0, CC errors 0
Driver 5: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 8992, writes 10, timeouts 0, DMA errors 0, CC errors 0
Driver 6: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 8992, writes 10, timeouts 0, DMA errors 0, CC errors 0
Date/time: 2023-03-24 12:03:27
Cache data hit count 189075977
Slowest loop: 11.45ms; fastest: 0.13ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 0.7ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters 3 -1 -1 -1, ordering errs 0
=== 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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== CAN ===
Messages queued 901, received 1989, lost 0, boc 0
Longest wait 3ms for reply type 6053, peak Tx sync delay 6, free buffers 18 (min 17), ts 497/496/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 12.65ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
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.27
WiFi MAC address f0:08:d1:03:7f:b0
WiFi Vcc 3.40, reset reason Power up
WiFi flash size 2097152, free heap 25208
WiFi IP address 192.168.100.165
WiFi signal strength -42dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
@jay_s_uk said in DUET 3 mini 5 wifi unstable:
what do you class as the latest firmware?
3.4.5 Stable.
I have found a problem where the wireless module will not reconnect to the wireless network, after a restart or power off / on cycle. The console throws a continuous loop of:
Error: WiFi module reported: network scan failed
I have tried reinstalling the firmware multiple times and am on the latest firmware. This is an error report rather than a request for help as I have bought the wired version to replace it with.
@T3P3Tony Still wont let me edit it, but its not an issue for this thread. Thanks for the upvotes though!
@JabawokJayUK Ive fixed the obvious H4 H0 issue in that btw but the site wont let me edit it as it gets flagged by Akismet as spam
@jay_s_uk Thanks, I had completely forgotten about the CAN limitation. Ive swapped some connectors around and got the rpm back for the waterpump, but still having some wierdness with the fan control. Revised config:
; ###############################################
; ##### Heater Preferences #####
; ###############################################
; Bed Heater
M308 S0 P"temp2" Y"thermistor" T100000 B3950 A"Bed" ; configure sensor 0 as thermistor on pin temp0 for the bed
M950 H0 C"out0" T0 Q11 ; create bed heater output on out0 and map it to sensor 0, lower switching frequency to 11Hz
M307 H0 R0.599 K0.348:0.000 D2.09 E1.35 S1.00 B0 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S130 ; set temperature limit for heater 0 to 130C
; Extruder 0
M308 S1 P"temp0" Y"pt1000" A"Extruder0" ; configure sensor 1 as PT1000 on pin temp1
M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1
M307 H1 R2.568 K0.267:0.000 D8.50 E1.35 S1.00 B0 V24.0 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S500 ; set the maximum temperature in C for heater
; Extruder 1
M308 S2 P"temp1" Y"pt1000" A"Extruder1" ; configure sensor 1 as PT1000 on pin temp1
M950 H2 C"out2" T2 ; create nozzle heater output on out2 and map it to sensor 2
M307 H2 R2.541 K0.273:0.000 D8.59 E1.35 S1.00 B0 V24.0 ; disable bang-bang mode for heater and set PWM limit
M143 H2 S500 ; set the maximum temperature in C for heater
; Water Pump Control
M950 F5 C"!out3+out3.tach" ; configure out3 as a 4 wire fan controller with PWM & Tach for the Pump
M106 P5 H1:2 T40 C"WaterPump" ; Turn on pump and link to E0/1 heaters to go full power over 40c
; Chamber Heater
M308 S3 P"121.temp0" Y"pt1000" A"Chamber" ; define cab temp as a PT1000 on the 1LC
M950 H3 C"121.out0" T3 ; create chamber heater output on out0 on the 1LC and map it to sensor 3
M307 H3 B0 S1.00 ; disable bang-bang mode for the chamber heater and set PWM limit
M141 H3 ; map chamber to heater 3
M143 H3 S100 ; set temperature limit for heater 3 to 100C
; Chamber Fan
M950 F4 C"!out4+out4.tach" Q250 ; configure out4 as a 4 wire fan controller with PWM & Tach
M106 P4 H4 H0 T60 S255 C"ChamberFan" ; Link Fan to Bed and enable over 60c
; Radiator Fans Control
M308 S6 P"121.temp1" Y"thermistor" T10000 B4725 C7.06e-8 A"Water" ; configure temp1 on the 1LC as thermistor for the water cooling
M950 F6 C"!121.out1+out1.tach" ; create Radiator fan output on out4 and map it to sensor 6
M106 P6 H6 T20:40 C"RadFans" ; Link RadFans to Water Temp and Thermostaically control
Weirdly, the Fan that should be labelled "ChamberFan" in the GUI, is now labelled Fan0?
Hey smart fellows, I have a heater/fan config and am having some issues that I would like advice on if possible.
I have a bed heater, 2 extruder heaters, a water pump (fan), a chamber heater and a chamber circulation fan all connected across multiple outs on a Duet 3 Mini and a Toolboard LC1. While everything works in the config below, I would like to revise it and have had weird results when I try!
; ###############################################
; ##### Heater Preferences #####
; ###############################################
; Bed Heater
M308 S0 P"temp2" Y"thermistor" T100000 B3950 A"Bed" ; configure sensor 0 as thermistor on pin temp0 for the bed
M950 H0 C"out0" T0 Q11 ; create bed heater output on out0 and map it to sensor 0, lower switching frequency to 11Hz
M307 H0 R0.599 K0.348:0.000 D2.09 E1.35 S1.00 B0 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S130 ; set temperature limit for heater 0 to 130C
; Extruder 0
M308 S1 P"temp0" Y"pt1000" A"Extruder0" ; configure sensor 1 as PT1000 on pin temp1
M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1
M307 H1 R2.568 K0.267:0.000 D8.50 E1.35 S1.00 B0 V24.0 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S500 ; set the maximum temperature in C for heater
; Extruder 1
M308 S2 P"temp1" Y"pt1000" A"Extruder1" ; configure sensor 1 as PT1000 on pin temp1
M950 H2 C"out2" T2 ; create nozzle heater output on out2 and map it to sensor 2
M307 H2 R2.541 K0.273:0.000 D8.59 E1.35 S1.00 B0 V24.0 ; disable bang-bang mode for heater and set PWM limit
M143 H2 S500 ; set the maximum temperature in C for heater
; Chamber Heater
M308 S3 P"121.temp0" Y"pt1000" A"Chamber" ; define cab temp as a PT1000 on the 1LC
M950 H3 C"121.out0" T3 ; create chamber heater output on out0 on the 1LC and map it to sensor 3
M307 H3 B0 S1.00 ; disable bang-bang mode for the chamber heater and set PWM limit
M141 H3 ; map chamber to heater 3
M143 H3 S100 ; set temperature limit for heater 3 to 100C
; Chamber Fan
M950 F4 C"!121.out1+out1.tach" ; create chamber fan output on out1 on the 1LC and map it to sensor 3
M106 P4 H3 T30 C"ChamberFan" ; Link Fan to Heater and enable over 20c
; Water Pump Control
M950 F5 C"!out3+out3.tach" ; configure out3 as a 4 wire fan controller with PWM & Tach for the Pump
M106 P5 H1:2 T40 C"WaterPump" ; Turn on pump and link to E0/1 heaters to go full power over 40c
; Radiator Fans Control
M308 S6 P"121.temp1" Y"thermistor" T10000 B4725 C7.06e-8 A"Water" ; configure temp1 on the 1LC as thermistor for the water cooling
M950 F6 C"!out4+out4.tach" ; configure out4 as a 4 wire fan controller with PWM & Tach
M106 P6 H6 T20:40 C"RadFans" ; Link RadFans to Water Temp and Thermostaically control
The above config is delivering the following functions:
The basics of what I "would like" to achieve is that the chamber circulation fan (F4) is enabled when the bed (H0) gets over 50C rather than the chamber thermister. However if I change my config to reflect the H0 heater in the M106 command for the Chamber Fan, it just comes on and stays on at any temperature as if its conflicting with another command.
Also, for some reason, in this config, I am not getting the feedback from my Waterpump speed. but If I remove aspects of the config or switch from 12v to VIN on the Out3/4 connectors, it suddenly jumps into life, as if the sensor channel on the board is being shared with another out and the two signals cancel each other out?
Any thoughts based on what you see?
Many thanks
Jay