Hardware or software issues?
-
Hello All-
Purchased a Duet 3 Mini 5+ Wifi with a RatRig VCore 3 a few years back and I'm just now getting around to setting it up. Sigh.
Was in a bad car accident awhile back and it kind of slowed me down, you might say. : (-My Duet 3 Mini 5 has the expansion board installed
-It is also connected via the supplied ribbon cable to a RaspPi 3B+ as an SBC
-The Pi has it's own factory supplied power supply and is plugged in.
-There is NO SD card in the Duet (as I understand the directions stated to do)
-My newly flashed image is on the SD card located only in the slot on the Pi
-HDMI external monitor is connected to the Pi
-Diag lights look good on both the Duet & the Pi
-I can connect with YAT, but cannot execute any network commands, (error message says I cannot)
-The Pi card used as the SBC has Ethernet, HDMI, keyboard,etc...all correctly connected.
-M115 diag command does not show anything strange (that I can surmise) except the following?Supply voltage: min 0.0, current 0.8, max 0.8, under voltage events: 0, over voltage events: 0, power good: no
Some of the issues I'm running into-
-Ethernet on the Pi is NOT getting an IP address even though link lights are ON and flashing? I wanted to disable the wireless interface and use the Ethernet on the Pi, but cannot seem to get there from here...
-I can SEE the Duet logo on boot for a brief moment, then the whole screen blanks out, vid signal appears to be there, but just a black screen.
-Cannot run ANY network related commands in terminal mode- this appears to be by design.
-Cannot update the firmware on the Duet until I can resolved these other issues.Some of the reasons I'm trying to use the SBC setup as opposed to standalone are the Ethernet hookup vs wireless, ability to run addons, etc.
It's kinda frustrating to break out new in package hardware (albeit old) and run into issues I'm not familiar with. I DID try and search the forums here, but haven't found a similar issue to compare against- yet.
Other info from M115 Diag:
RepRapFirmware for Duet 3 Mini 5+ version 3.2.2 running on Duet 3 Mini5plus WiFi (SBC mode)Any help or insight is GREATLY appreciated as I'm stuck finishing my printer until I get these issues resolved.
Yes, I'm a NOOB here, it is what it is.
Thanks! -
I would suggest starting without the Pi in the mix at all, and get the mini5 up and running in standalone mode first. Once that's all working you can tackle adding in the Pi.
Getting the firmware updated on the mini5 is pretty straight forward, and getting connected to it over the network should be as well.
Start here: https://docs.duet3d.com/en/How_to_guides/Getting_connected/Getting_connected_to_your_Duet
-
Thanks for the reply- kind of the direction I was leaning to as well. Only reason I didn't was because I don't have wireless access where I'm at, everything on this LAN is hardwired.
If the Duet3 MIni5+ needs wireless access as an update path, that presents me with a problem, LOL.
Was hoping that someone had seen this combo of issues before and it was just a step I missed somewhere.I will see how far I can get connected with the Duet in standalone, but confidence is NOT high.
Really don't want to drag this all to a coffee shop with WiFi somewhere, that might be a bit awkward. ; )
-
If the mini5 is the wifi model, you can actually have it startup it's own access point which you can then connect to. You'd have to configure that over USB terminal connection.
Updating the firmware can be done with a USB connection to a computer. It presents itself as an external storage drive that you copy the firmware file onto.
-
-
@Phaedrux
Thanks again, good info! Not sure how I missed that, but will keep you all posted. -
@Electriceye just a heads hp rhat depending on when you bought the kit, there may be 4028 part cooling fans in the kit drawing mire current than the duet 3 mini board can provide. Best solution for that is to power it from an external 12V source.
I'm currently not at home and limited to mobile or Idtprovide you with a sketch.
-
@Electriceye the voltage readings in that M122 diagnostic response indicate that the Duet is getting 5V power (perhaps from USB) but not VIN power. That shouldn't stop the connection to the Pi working, but will prevent any attached heaters, fans and stepper drivers from working.
-
Hello All-
Many thanks for the observations and tips- duly noted!
As promised, here's where I'm at so far:Was able to update the Duet firmware & PanelDue 7i fairly easily, once connections were made.
According to the Electronics Diag button in DWC, my software is mis-matched? Oops!FYI- I'm still updating the data on the Duet, Pi is already updated. Havce not mounted to the printer yet, hence no mains inputs.
-HDMI screen output works great on the PI by itself, but blank screen issue remains in Duet SBC mode
-PanelDue 7i is not attached yet, but will probably end up using it once I find my cables, Doh!
-PanelDue was the easiest to update, really a bit of good news there.12/11/2024, 3:13:34 PM: Incompatible software versions: The installed software versions do not match. Please operate your setup only at equal versions to avoid potential incompatibilities and unexpected errors.
12/11/2024, 3:13:59 PM: M122: === Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.5.4 (2024-11-24 10:44:24) running on Duet 3 Mini5plus WiFi (SBC mode)
Board ID: W64JZ-X296U-D65J0-40KM8-1213Z-7VWNL
Used output buffers: 1 of 40 (17 max)
=== RTOS ===
Static ram: 103496
Dynamic ram: 106720 of which 0 recycled
Never used RAM 31532, free system stack 156 words
Tasks: SBC(2,ready,1.1%,869) HEAT(3,nWait 6,0.0%,369) Move(4,nWait 6,0.0%,355) CanReceiv(6,nWait 1,0.0%,939) CanSender(5,nWait 7,0.0%,336) CanClock(7,delaying,0.0%,334) TMC(4,nWait 6,0.0%,121) MAIN(2,running,97.7%,804) IDLE(0,ready,0.4%,29) AIN(4,delaying,0.8%,264), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:04:03 ago, cause: Vdd brownout
Last software reset time unknown, reason: HardFault bfarValid precise, Gcodes spinning, available RAM 52428, slot 0
Software reset code 0x0063 HFSR 0x40000000 CFSR 0x00008200 ICSR 0x00000803 BFAR 0x00000040 SP 0x2000a758 Task MAIN Freestk 745 ok
Stack: 00000000 00000571 0000056d 00000000 2001b3e0 000664e9 000781ca 61070000 00000000 0007dbd1 00000000 00000000 20000008 ffffffff 2001c8dc 20009b54 2001c6d8 2000a7d8 20000008 200095b4 2000a864 0007dca3 00000001 2000a7d8 20000008 2001fcb8 20000008
Error status: 0x00
MCU revision 3, ADC conversions started 182999, completed 182999, timed out 0, errs 0
MCU temperature: min 21.6, current 23.0, max 23.0
Supply voltage: min 0.7, current 0.7, max 0.8, under voltage events: 0, over voltage events: 0, power good: no
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 1: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 2: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 3: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 4: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 5: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Driver 6: ok, SG min n/a, read errors 0, write errors 0, ifcnt 0, reads 0, writes 0, timeouts 0, DMA errors 0, CC errors 0
Date/time: 2024-12-11 22:20:09
Cache data hit count 585343988
Slowest loop: 3.38ms; fastest: 0.10ms
=== Storage ===
Free file entries: 20
SD card 0 not detected, interface speed: 0.0MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
=== DDARing 0 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== DDARing 1 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Movement locks held by null, null
HTTP* is doing "M122" 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
File2 is idle in state(s) 0
Queue2 is idle in state(s) 0
Q0 segments left 0, axes/extruders owned 0x0000000
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== CAN ===
Messages queued 1220, received 0, lost 0, errs 1147208, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 26 (min 26), ts 1220/0/0
Tx timeouts 0,0,1219,0,0,0 last cancelled message type 30 dest 127
=== SBC interface ===
Transfer state: 5, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 7962/7962
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x0cd20
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server version 3.5.4 (2024-11-25 17:29:06, 32-bit)
HTTP+Executed:Executing M122
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 27.64, max time between full transfers: 1196.2ms, max pin wait times: 74.9ms/16.7ms
Codes per second: 0.10
Maximum length of RX/TX data transfers: 4360/220 -
@Electriceye said in Hardware or software issues?:
The installed software versions do not match. Please operate your setup only at equal versions to avoid potential incompatibilities and unexpected errors.
12/11/2024, 3:13:59 PM: M122: === Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.5.4 (2024-11-24 10:44:24) running on Duet 3 Mini5plus WiFi (SBC mode)This reminds me... exactly what software is "mismatched"? Is it really the DWC, or perhaps the RRF Version?
My installed software versions are as follows:Product ShortName Version
Duet 3 Mini 5+ Mini5plus 3.5.4
Duet Software Framework DSF 3.5.4
Duet Web Control DWC 3.5.3FIRMWARE_NAME: RepRapFirmware for Duet 3 Mini 5+ FIRMWARE_VERSION: 3.5.4 ELECTRONICS: Duet 3 Mini5plus WiFi FIRMWARE_DATE: 2024-11-24 10:44:24
FYI- Also no luck on the HDMI output still showing a 'blank/black screen. There is def some kind of video signal there...just nothing to see. (yes, it works in Pi mode- as it should)
Off I go, hunting for my elusive/missing cables...
-
@Electriceye the mismatched software is DWC. It's only one minor version behind RepRapFirmware so not critical. But it's odd that it didn't update. @chrishamm any suggestions?
-
@Electriceye try clearing your browser cache
