Duet 2 Ethernet IP address keeps flashing on display.
-
Hi all,
I have a Duet 2 WiFi that I converted to use a hardwired connection. When I power up the board, the IP address keeps flashing on the screen - I'm using a static IP and the message was flashing on the screen even when no ethernet cable is connected to the board. The board was working fine until 30 minutes before I made this post. I was Autotuning the heated bed and nozzle via the Web interface. After the Bed autotuning parameters were uploaded, I started the nozzle autotune and that's when the connection went on the fritz. I have attached my config.g file as well the the M122 log from my Duet in this post.
The board is running firmware 3.2.2
Any help would be much appreciated.
Here's a link to a video that shows what's happening with the board: https://photos.app.goo.gl/RL3ky76qKWW3fdH36
-
Does it still do that when powered by VIN?
-
Yes. In fact, I tried to time the issue and it happens like clockwork 2 minutes and 30 seconds after powering up. Here's a screenshot of the console as it starts fritzing out
Is the issue with the config.json file?
-
Try creating a fresh SD card with a basic config.
-
I just did that thinking it may be an issue. Wiped the SD card, reloaded a basic config after setting it up and in 3 minutes, same error.
Also noticed that if I issue an M552 S0, wait a few seconds and then issue an M552 S1 P0.0.0.0, the lights on the ethernet port don't turn back on.
-
Considering this is an ethernet conversion I am wondering if there's an issue either with the module or the installation.
-
I've tested the pin connections for shorts or accidental solder blobs and I haven't found any issues. I was also careful to not let the board soak up too much heat when de-soldering the Wi-Fi Module. I think the only other option is that the ethernet module itself is faulty, which would be a bummer since the Wi Fi in my basement sucks and that's where this printer is going to be.
I've ordered a new Duet 2 Ethernet board, so I'll wait to see how that turns out. In the meantime, I'm going to wipe the main board's firmware and re-flash it using BOSSA, then rebuild RRF 3.2.2 and see what that does.
-
btw, here are the firmware settings I've configured"
![53e5fba2-4785-4931-b506-ee0179872d68-image.png]
(/assets/uploads/files/1614450403946-53e5fba2-4785-4931-b506-ee0179872d68-image.png)
-
Perhaps @dc42 has other ideas. My money is on the module. Let us know what you find.
-
@Phaedrux Will do. Thanks! Also, the Z-Bot printer looks badass. I'm programming this board for what will eventually become a Hypercube CoreXY. For now it's an upgrade for my CR-10S to which I've added linear rails and converting to a 24V system.
-
Thanks. It's served me well.
-
Try removing the Ethernet cable while it is in this loop, then send M122 from YAT and post the result.
-
And of course it's not happening anymore... I formatted the SD card instead of just deleting the folders and then reloaded RRF3.2.2. After plugging in through USB, the network issue hasn't popped up yet. Though I haven't put the config_override.g file in the sys folder yet. Let me try that and start up the board again.
-
Lol... it happened just as I submitted my previous post.... Here's the M122 log from YAT (scroll through the network address messages for a bit)
-
Your Ethernet state is: Interface state establishingLink, link down
Mine (Duet2/Ethernet) is: Interface state active, link 100Mbps full duplexDo you see the connection-state (not traffic) light blinking on the Ethernet connector.
Do you have a different Ethernet cable you can try?
-
I tried multiple cables, as that was the first thing I thought of as well. The yellow light is solid on the port when this happened and the green (traffic) light is flickering
-
I do have an 8 port switch between my router and the board, so maybe I'll have to see what's going on there?
-
I changed to a third cable and this time, the board went into the loop and then restarted. Here's the M122 after restart:
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet Ethernet 1.02 or later
Board ID: 08DGM-917DA-G4MS8-6JKD2-3S06R-T9TRB
Used output buffers: 1 of 24 (2 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 68848 of which 40 recycled
Never used RAM 19732, free system stack 195 words
Tasks: NETWORK(ready,548) HEAT(blocked,337) MAIN(running,471) IDLE(ready,20)
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:00:14 ago, cause: software
Last software reset at 2021-02-27 15:42, reason: StuckInSpinLoop, GCodes spinning, available RAM 19732, slot 0
Software reset code 0x0083 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0040080f BFAR 0xe000ed38 SP 0x20001fac Task NETW Freestk 467 ok
Stack: 004073fb 004072c2 01010000 f8000000 40a556ff 418dfce4 b7154800 3331bb4c 40000000 3f317200 b5ddea0e 388aade3 bb360493 3bcb9c8b 00000000 418554cd 38533333 7f7fffff 00000000 60000010 000000f0 000000f0 0040705b 000021c8 000021c8 400e0e00 0040716f
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 17.3, current 18.0, max 18.2
Supply voltage: min 1.7, current 1.7, max 1.8, under voltage events: 0, over voltage events: 0, power good: no
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: 1970-01-01 00:00:00
Cache data hit count 19863370
Slowest loop: 2.37ms; fastest: 0.13ms
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 0.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 ready with "M122" 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: 1.03ms; fastest: 0.01ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 0 of 8
Interface state establishingLink, link down
ok -
And it's not connecting to the network anymore. When this happened last time, I had to keep the board turned off for about 10 minutes and then try again and it connected to the network.
-
Do you have any "Cold spray"?
Maybe it's your Ethernet interface chip getting too hot?
