Posts made by Luk14

@droftarts Thank you! Now everything works fine...

@phaedrux My firmware version is 3.2.2 . M98 do not report any errors.

When turn on the fan manually i can measure a different voltage:
off:0,32V
on:0,55V

So at least something is happen, but I would expect 24V.

When i remap the fan to the fan0 output i get 24V there.

Hi,

i want to use the heater1 output on my Duet Wifi as a fan output for my watercooling system. Unforunatly i am not able to measure any voltage on the connectors.

My config:

; 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.362 C386.0 D3.93 S1.00 V24.0            ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0                                            ; map heated bed to heater 0
M143 H0 S160                                       ; set temperature limit for heater 0 to 160C
M308 S1 P"e0temp" Y"thermistor" T4606017 B5848 C5.548428e-8 R4700 H0 L0      ; 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 S400                                       ; set temperature limit for heater 1 to 400C
M950 H2 C"nil"                                     ; disable heater 2 and free up the associated pin

; Fans
M950 F0 C"fan1" Q500                               ; create fan 0 on pin e1heat and set its frequency
M106 P0 S0 H-1 C"Bauteilkühlung"                   ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"e1heat" Q500                             ; create fan 1 on pin fan1 and set its frequency
M106 P1 S255 H0 T45                                ; set fan 1 value. Thermostatic control is turned on
M950 F2 C"fan2" Q500                               ; create LED on pin fan1 and set its frequency
M106 P2 S0 H-1 C"LED"                              ; set LED value. Thermostatic control is turned off

For testing the fan is linked to the bed. The printer isn t finish yet...

I hope you can find my mistake.

Ok it seams like there is no firmware solution. I will use a relay instead. But there should be a simple firmware solution, because these Meanwell PSUs are quite popular.

I got a replacement two days ago. With the new board everything works like i expected.

One more question. My 24V PSU can be turned on and off by a external signal. I wired it up and it works, but unfortunately the PSU is not a ATX one and turns off if it gets the 5V signal from the Duet. Is there a setting in the firmware where i can invert the ATX_ON pin?

Any further ideas?

@dc42

Nr.1 and when i apply 5V and VIN simultaneously.

@T3P3Tony said in Short-to-ground reported by driver(s) 0 1 2 3 4:

orking fine using the internal 5V regulator then we need to work out why the external 5V supply is causing the issue. Please can you measure the voltage level between 5V and Ground on (e.g.) the PanelDue header using a multimeter to confirm that when the external 5V PSU is attached the Duet has 5V on its 5V rail (not just on the power supply input).

PSU: 5,00V
pin1/2: 4,65V

I increased the voltage to (5,44V/5,05V) but the error message still occours.

* push *

When i switch from the 24V to the 5V supply quickly (just change the jumper position while it is running) i don t get any error message.

Edit:

If i turn on the 24V PSU first and after some seconds the 5V PSU everything will work fine.

@T3P3Tony

Yes, without the 5V PSU the board works just fine and I am sure that i use the right jumper configuration(s).

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2 running on Duet WiFi 1.02 or later
Board ID: 08DLM-996RU-N85S4-7JKDG-3SD6P-KVARN
Used output buffers: 3 of 24 (11 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 73212 of which 40 recycled
Never used RAM 15368, free system stack 191 words
Tasks: NETWORK(ready,160) HEAT(blocked,323) MAIN(running,452) IDLE(ready,19)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:01:11 ago, cause: power up
Last software reset at 2021-02-08 20:59, reason: User, GCodes spinning, available RAM 15368, slot 1
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 25.5, current 30.0, max 30.2
Supply voltage: min 23.9, current 24.1, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 0, ok, SG min/max not available
Driver 1: position 0, ok, SG min/max not available
Driver 2: position 0, ok, SG min/max not available
Driver 3: position 0, ok, SG min/max not available
Driver 4: position 0, ok, 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-02-20 19:12:18
Cache data hit count 85795599
Slowest loop: 4.85ms; fastest: 0.20ms
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 4.0ms, 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.55ms; 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.25
  WiFi MAC address 50:02:91:e5:3f:91
  WiFi Vcc 3.39, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 23832
  WiFi IP address 19.3.95.62
  WiFi signal strength -66dBm, mode 802.11n, reconnections 0, sleep mode modem
  Clock register 00002002
  Socket states: 0 0 0 0 0 0 0 0

@dc42
I leave it unconnected.

I have just connected the board, no fans, motors, sensors etc.

I connect the 5V PSU directly to the board. I checked the wiring twice. I also tried to use a USB PSU. Same result...

I used this guide:
https://duet3d.dozuki.com/Wiki/Power_Wiring#:~:text=The Duet operates on two power circuits: a,or not an external power supply is attached).

*** push ***

@dc42 said in Short-to-ground reported by driver(s) 0 1 2 3 4:

applied briefly but disappears again when the MCU starts communicating with the drivers. Is the blue LED that indicates VIN power lit continuously?

Yes the LED lit continuously. The 24V PSU is a MeanWell RSP-500-24. The 5V on is a MeanWell RS-15-5. When I use the internal switching regulator the error message disappears. Is the 15W PSU too weak to power the board?

Hello,

today I successfully setup the WIFI connection on my new DuetWifi and connected it to my 5V power supply. This worked very well, but after I connected my 24V power supply the web interface showed me the following error:

Error: short-to-ground reported by driver(s) 0 1 2 3 4
Error: over temperature shutdown reported by driver(s) 0 1 2 3 4

I did not connect any motor.

Is this normal or do I have a broken board?

[spoiler]
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2 running on Duet WiFi 1.02 or later
Board ID: 08DLM-996RU-N85S4-7JKDG-3SD6P-KVARN
Used output buffers: 3 of 24 (23 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 73212 of which 40 recycled
Never used RAM 15368, free system stack 189 words
Tasks: NETWORK(ready,176) HEAT(blocked,323) MAIN(running,470) IDLE(ready,19)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:08:03 ago, cause: power up
Last software reset at 2007-04-09 15:53, reason: HardFault, Platform spinning, available RAM 106588, slot 1
Software reset code 0x4060 HFSR 0x40000000 CFSR 0x00080000 ICSR 0x00000803 BFAR 0xe000ed38 SP 0x2001ff90 Task none Freestk 228 bad marker
Stack: 00000001 00000000 00000002 10807bf7 00000000 00456309 004483bc 41000000 dfeb33a4 159310b9 c9913a17 37fdbf95 00476ff0 00457b71 00000004 00474c1a 00474c26 00474c4e 00000000 00449361 200000a8 00000000 00000000 00000000 00000000 00456309 00000000
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 29.1, current 29.5, max 29.9
Supply voltage: min 24.0, current 24.1, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 0, temperature-shutdown! short-to-ground, standstill, SG min/max not available
Driver 1: position 0, temperature-shutdown! short-to-ground, standstill, SG min/max not available
Driver 2: position 0, temperature-shutdown! short-to-ground, standstill, SG min/max not available
Driver 3: position 0, temperature-shutdown! short-to-ground, standstill, SG min/max not available
Driver 4: position 0, temperature-shutdown! short-to-ground, 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-02-08 17:14:31
Cache data hit count 655813056
Slowest loop: 6.25ms; fastest: 0.23ms
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.8ms, 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: 202.09ms; fastest: 0.10ms
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 1
WiFi firmware version 1.25
WiFi MAC address 50:02:91:e5:3f:91
WiFi Vcc 3.39, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 27064
WiFi IP address 19.3.95.62
WiFi signal strength -61dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
[/spoiler]