Duet 3 Paneldue not working

Visionary

Should be as I haven't changed config and it was in my old config.

Visionary

I just noticed that with power from main PSU the Duet (both mainboard and paneldue) won't work properly:

Wrong number of axis/heaters on paneldue
Paneldue responds but doesn't allow to do anything
When main power is on, connecting through ethernet doesn't seem to work

But with just USB power the printer seems work as normal (however I can't test anything without main power).

M122 gave this:

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.2.2 running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 
Used output buffers: 1 of 40 (13 max)
=== RTOS ===
Static ram: 149788
Dynamic ram: 93588 of which 52 recycled
Never used RAM 115404, free system stack 186 words
Tasks: NETWORK(ready,210) ETHERNET(blocked,119) HEAT(blocked,300) CanReceiv(blocked,927) CanSender(blocked,371) CanClock(blocked,358) TMC(blocked,65) MAIN(running,1144) IDLE(ready,19)
Owned mutexes:
=== Platform ===
Last reset 00:00:30 ago, cause: power up
Last software reset details not available
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
MCU temperature: min 31.0, current 41.7, max 41.7
Supply voltage: min 0.3, current 0.3, max 0.9, under voltage events: 0, over voltage events: 0, power good: no
12V rail voltage: min 0.1, current 0.2, max 0.3, under voltage events: 0
Driver 0: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
Driver 1: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
Driver 2: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
Driver 3: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
Driver 4: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
Driver 5: position 0, ok, reads 0, writes 0 timeouts 0, SG min/max 0/0
Date/time: 2021-04-12 17:59:23
Slowest loop: 7.05ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 2.6ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, maxWait 169ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 1, completed moves 1, 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 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 1 is on, I-accum = 0.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.
=== Network ===
Slowest loop: 6.40ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- Ethernet -
State: active
Error counts: 0 0 1 0 0
Socket states: 5 2 2 2 2 0 0 0
=== CAN ===
Messages queued 122, send timeouts 274, received 0, lost 0, longest wait 0ms for reply type 0, free buffers 48

jay_s_uk

@visionary sounds like you may have blown the 3.3v or 5v regulator. Can you confirm what lights are on when powered from the PSU? Also have a feel and see if anything gets hot

Visionary

@jay_s_uk

All LEDs are on continuously. Diagnostic LED is on too although its very dim.

dc42

@visionary said in Duet 3 Paneldue not working:

Diagnostic LED is on too although its very dim.

On a Duet 3, that normally means that the board isn't running any firmware.

Visionary

@dc42
When I used USB the board and panel work normally: I can even connect to it then through DWC, so it clearly has firmware on it. The diagnose LED (continuously on) is very dim with 24V main power when compared USB (blinking) powered brightness.

dc42

@visionary, are you powering anything else from the Duet's 5V supply other than the PanelDue? For example, a Raspberry Pi or an LED strip. I am wondering whether there is insufficient 5V power from the internal 5V regulator.

Visionary

@dc42

Only thing connected to 5V (in IO_x connectors) is paneldue i7. I have two inductive sensors NBB0,8-4M25-E2 and NJ2-12GM40-E as endstops on X- and U-axes, but those get their power from external 24V PSU. Other than that I have nothing unusual connected to mainboard. I tested with cheap multimeter 5V (and ground) output from IO-3 and got 4,88V.

BTW where is 5V regulator located on the board?

Visionary

The found out that one of the inductive sensors was the problem. Without it being connected paneldue showed correct information.

I'm not sure what is the exact cause. Too much current through GND-pin or input? Can I connect sensor GND to 24V PSU GND? Or would increasing/decreasing resistor value work?

My current wiring (Inductive sensor NBB0,8-4M25-E2-Y106003):

Visionary

I put voltage divider (10k and 4.7k resistors) between sensor and input on Duet and it seemed to fix the problem.