DUET 3 - connectivity issues
-
@CJ-BRAVO If you're able to (PanelDue) you could make a M122 and check whether voltage is ok or if you see other errors. Maybe there are also LED indicators on the board which signal an error (but I don't know them).
-
M122 works
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.01-RC12 running on Duet 3 MB6HC v0.6 or 1.0
Board ID: 08DJM-956L2-G43S4-6J9DA-3SD6R-1V5AF
Used output buffers: 1 of 40 (13 max)
=== RTOS ===
Static ram: 154588
Dynamic ram: 161144 of which 20 recycled
Exception stack ram used: 308
Never used ram: 77156
Tasks: ETHERNET(blocked,472) NETWORK(ready,276) HEAT(blocked,1412) CanReceiv(suspended,3824) CanSender(suspended,1484) CanClock(blocked,1432) TMC(blocked,208) MAIN(running,4676) IDLE(ready,80)<Owned mutexes:
=== Platform ===
Last reset 00:05:42 ago, cause: reset button
Last software reset time unknown, reason: Terminate called, spinning module GCodes, available RAM 77064 bytes (slot 3)
Software reset code 0x4183 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x04432000 BFAR 0x00000000 SP 0x20417478 Task MAIN
Stack: 0000002b 0046afa7 00000000 2044d198 204177e0 0046b30f 00000000 0046ac95 204174c8 00450373 20417518
Error status: 0
MCU temperature: min 37.6, current 38.7, max 38.8
Supply v[Warning: Maximal number of bytes per line exceeded! Check the EOL (end-of-line) settings or increase the limit in the advanced terminal settings.]Voltage is 30.
I see this warning:
Warning: Maximal number of bytes per line exceeded! Check the EOL (end-of-line) settings or increase the limit in the advanced terminal settings
-
ok sorry my bad. heres the full M122:
m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.01-RC12 running on Duet 3 MB6HC v0.6 or 1.0
Board ID: 08DJM-956L2-G43S4-6J9DA-3SD6R-1V5AF
Used output buffers: 1 of 40 (13 max)
=== RTOS ===
Static ram: 154588
Dynamic ram: 161224 of which 20 recycled
Exception stack ram used: 308
Never used ram: 77076
Tasks: ETHERNET(blocked,444) NETWORK(ready,276) HEAT(suspended,1412) CanReceiv(suspended,3428) CanSe
nder(suspended,1484) CanClock(blocked,1432) TMC(blocked,208) MAIN(running,4532) IDLE(ready,80)
Owned mutexes:
=== Platform ===
Last reset 00:12:36 ago, cause: reset button
Last software reset time unknown, reason: Terminate called, spinning module GCodes, available RAM 77
064 bytes (slot 3)
Software reset code 0x4183 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x04432000 BFAR 0x00000000 SP 0x2041
7478 Task MAIN
Stack: 0000002b 0046afa7 00000000 2044d198 204177e0 0046b30f 00000000 0046ac95 204174c8 00450373 204
17518
Error status: 0
MCU temperature: min 38.6, current 38.6, max 38.6
Supply voltage: min 30.0, current 30.0, max 30.0, under voltage events: 0, over voltage events: 0, p
ower good: yes
12V rail voltage: min 12.1, current 12.1, max 12.1, under voltage events: 0
Driver 0: standstill, reads 59616, writes 0 timeouts 0, SG min/max not available
Driver 1: standstill, reads 59615, writes 0 timeouts 0, SG min/max not available
Driver 2: standstill, reads 59616, writes 0 timeouts 0, SG min/max not available
Driver 3: standstill, reads 59616, writes 0 timeouts 0, SG min/max not available
Driver 4: standstill, reads 59616, writes 0 timeouts 0, SG min/max not available
Driver 5: standstill, reads 59616, writes 0 timeouts 0, SG min/max not available
Date/time: 2020-06-09 13:29:47
Slowest loop: 0.87ms; fastest: 0.14ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 375, MinFreeDm: 375, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== Heat ===
Bed heaters = -1 -1 -1 -1 -1 -1 -1 -1 -1 -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
SBC is idle in state(s) 0
Daemon* is idle in state(s) 0 0, running macro
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 13.02ms; fastest: 0.03ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8- Ethernet -
State: active
Error counts: 0 0 0 0 0
Socket states: 2 2 2 2 2 0 0 0
=== CAN ===
Messages sent 0, longest wait 0ms for type 0
=== Linux interface ===
State: 0, failed transfers: 0
Last transfer: 756039ms ago
RX/TX seq numbers: 0/1
SPI underruns 0, overruns 0
Number of disconnects: 0
Buffer RX/TX: 0/0-0
ok
- Ethernet -
-
I tried updating RRF to 3.1 (which the true latest...).
Because I can't connect to the duet 3 IP, I copied the firmware to the SD card then used M997 S0 with the terminal.
but I get an error that it can't be found..
I tried copying it to the SYS and other folders... no success
-
@CJ-BRAVO Have you tried a different SD card?
-
@CJ-BRAVO there was a bug with 30V, but it was fixed a few versions older than you use (https://forum.duet3d.com/topic/12157/duet-3-attempt-to-move-motors-when-vin-is-not-in-range-30v/7) I don't think it's the reason.
I see no errors in your M122.How do you access Ethernet and USB (Windows, Linux, Mac?) and is it possible that the connection broke to to an (security?) update. If Duet 3 Ethernet is connected to your internet router, something like MAC address control could block the Duet. It would be visible in the router log file as access denied.
-
ok I did M21 to restart the sd card.. i have connection and managed to update the firmware.
-
@CJ-BRAVO if you didn't power off the board when removing and putting the sd card back you will always need
M21otherwise it sounds like gremlins in the system somewhere. -
@bearer
I think it is gremlins and I think they had a late supper.
I got it to work I think. changed the SD card.
could it be just the cards' fault? is there procedure of formatting the card?
-
@CJ-BRAVO said in DUET 3 - connectivity issues:
is there procedure of formatting the card?
best option is using the sd formatter tool, and not using a quick format (takes a while, but will remap all bad sectors)
https://www.sdcard.org/downloads/formatter/
(gremlins should stick to being in films... sigh)
-
ok will give it a shot
thanks
