Duet2 Ethernet not responding after reboot/reset

clegg78

I've changed it to static IP to see if anything is different, and no it is not.

dc42

Are you providing VIN power, or just USB power?

If you send M122 from USB when it won't connect, what does the Network section of the diagnostic report show?

If you don't set a static IP address, does M552 report an assigned IP address, or not?

clegg78

M122 reports:
M122<CR>
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet Ethernet 1.02 or later + DueX5
Board ID: 08DGM-9T6BU-FG3SN-6JKF2-3S46Q-1UY7D
Used output buffers: 1 of 20 (2 max)
=== RTOS ===
Static ram: 25524
Dynamic ram: 98440 of which 0 recycled
Exception stack ram used: 272
Never used ram: 6836
Tasks: NETWORK(ready,1612) HEAT(blocked,1324) MAIN(running,3868) IDLE(ready,200)
Owned mutexes:
=== Platform ===
Last reset 00:00:32 ago, cause: power up
Last software reset at 2019-02-23 17:48, reason: User, spinning module GCodes, available RAM 6736 bytes (slot 3)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 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 16.9, current 19.1, max 19.2
Supply voltage: min 0.4, current 0.4, max 0.7, under voltage events: 0, over voltage events: 0, power good: no
Driver 0: ok, SG min/max not available
Driver 1: ok, SG min/max not available
Driver 2: ok, SG min/max not available
Driver 3: ok, SG min/max not available
Driver 4: ok, SG min/max not available
Driver 5: ok, SG min/max not available
Driver 6: ok, SG min/max not available
Driver 7: ok, SG min/max not available
Driver 8: ok, SG min/max not available
Driver 9: ok, SG min/max not available
Date/time: 1970-01-01 00:00:00
Cache data hit count 66505232
Slowest loop: 0.99ms; fastest: 0.06ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
=== 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: 1 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 ready with "M122" 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: 0.39ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 0 of 8
Interface state 5, link 100Mbps full duplex
ok

and M552 Returns:
M552
Network is enabled, configured IP address: 192.168.50.45, actual IP address: 192.168.50.45
ok

But the Green LED is just locked steady with no movement, and I cant access the device. If I power it off for an extended period of 2-5 minutes it will come back and work when I power it up.

dc42

@dc42 said in Duet2 Ethernet not responding after reboot/reset:

If you don't set a static IP address, does M552 report an assigned IP address, or not?

dc42

@dc42 said in Duet2 Ethernet not responding after reboot/reset:

Are you providing VIN power, or just USB power?

Your M122 report indicates you are only supplying USB power. That may not be sufficient.

and:

If you don't set a static IP address, does M552 report an assigned IP address, or not?

clegg78

It does it on 12V VIN as well... but I can connect it to the PSU ,and run the M122 again... I've primarily only used it on VIN supply. Just for this I had to disconnect it to get it over to my PC.

clegg78

@dc42 if I dont set an assigned IP: If it is working, it will report an IP via DHCP, if its not, it wont. It lists no IP or 0.0.0.0

dc42

@clegg78 said in Duet2 Ethernet not responding after reboot/reset:

@dc42 if I dont set an assigned IP: If it is working, it will report an IP via DHCP, if its not, it wont. It lists no IP or 0.0.0.0

I suspect a temperature-related fault on the Ethernet board, so I suggest you ask your supplier to swap the Duet for another.

clegg78

Thanks, I've submitted an RMA with the place I bought it.

I also dont think its temperature related, I can power up the board, and wait 15 seconds ( or how ever long it takes for it to fully boot) , hit the reset button, and the ethernet board is dead then until it powers down for a minute or two

clegg78

Just to follow up, I received my replacement Duet2Ethernet and it works perfect. The last one had issues updating the firmware from the web interface, and the lock up issue with the ethernet in general. The new one is working perfectly as expected.

Thanks for the troubleshooting assistance.

dc42

Thanks for confirming this. I'm sorry that you received a faulty Duet.