@jumpedwithbothfeet

WINNER WINNER!

Fried Chicken dinner!

You sir..are correct!
The clue I should have guessed was that the LED on the SSR was not illuminating...LEDs are polarity sensitive!

The image I was going by (duet3_mini5+_v0.5-v1.02_d1.5_wiring.png) was upside down as viewed on the screen, as opposed to the direction I have it mounted. GREAT CATCH!

Board now heats up (quickly I might add) and the LED on the SSR is aglow!

jumpedwithbothfeet wins the internets today!

Thanks to ALL who had tips, suggestions and input. You people ROCK!

Those Delta printers always amaze me... so crazy complex looking, to say the least.

I'm getting ready to wire in my ADXL345 to my Duet 3 Mini5+ as well and wondered how that flat ribbon cable is working out for you? Everything I have read suggests using STP Ethernet CAT 6 or above to help prevent interference and subsequent data loss.

I'm trying to keep the overall mass down on the gantry on my Core XY RatRig as the wiring loom there is already full of wires and the more mass you add to that toolhead, the more you have to compensate for.

Have you had any interference issues or data drop? I'm going to cut and weigh the corresponding lengths or ribbon cable vs Ethernet and see which one is lighter & more flexible.

Also- My ADXL has the pinouts already labeled, but I cannot find the Duet side pinouts- I believe it is like 6 wires or such.
I finally found the pin outs on the docs site. I was searching for ADXL which returned zero results. Doh.
https://docs.duet3d.com/en/User_manual/Connecting_hardware/Sensors_Accelerometer

Congrats on your Delta printer- very impressive machine you have there!

@keyz182
Yes, this topic IS old...er but alas- I need to clarify something as I'm nearing the 'power on smoke test' ; ) for my RatRig VCore 3 with Duet 3 Mini 5+ and really do not wish to see the 'magic smoke'

In the thread above, there is a reference link to:
Check the table here - LINK REMOVED as I need at least 2 reputation to post links...sigh

When I try that link- it is el broko, non-functional, kaput!

So... I looked around and according to this resource-
duet3d dot kom/en/How_to_guides/Wiring_your_Duet_3

The Duet has an on-board 5V regulator which is powered by the VIN input (12-24V).
Unless you plan to provide an external 5V source, you should at this time check that there is no jumper on Int 5V Disable or 5V Select.
Optionally, external 5V power can be supplied to:

'5V IN' pin on EXT_5V connector. In this case, add a jumper to the 5V Select jumper between '5V_EXT_IN' and '5V_COM' pins, and add a jumper to Int 5V Disable.
In some cases you may want to power the Duet from the 5V output of an SBC connected to the SBC header. Note that the total power of the Duet and peripherals must be factored into the SBC power budget, and should not exceed 1A. Powering the SBC from the duet is not supported. In this case, add a jumper to the 5V Select jumper between '5V_SBC' and '5V_COM' pins, and add a jumper to Int 5V Disable.

Right...so here's the issue-

• My Power supply: Meanwell LRS-350-24 seems adequate enough for this build (New, voltages all look good)
• My Duet 3 MIni 5+ is running in SBC mode with an attached Pi3B+ with its own factory power supply (5.25v 2400 mA)
• The Pi Factory power supply plugs directly into the Micro USB port on the Pi3B+
• The Pi3B+ is connected directly to the Duet 3 Mini 5+ via the supplied 26 pin ribbon cable
• The supplied 26 pin ribbon cable has 5 volts feeding the Duet 3 Mini 5+
• My Panel Due 7 is connected to the Duet Board via IO_0 connector (I'm sure this draws some power)

The documentation here suggests:
duet3ddot kom/en/How_to_guides/Wiring_your_Duet_3
We recommend powering the SBC using its own PSU, to ensure stable voltage and sufficient supply of current to both Duet and SBC.

I know I can power the Panel Due 7 from the 4 wire connector I already wired up, but can also power it via the 10 pin serial cable, (albeit limited to 400mm length)

With these stated power requirements I've already listed, it seems there woukld be a 5v conflict waiting to happen if I don't choose my jumper setting correctly...which is what led me to this thread.

I'm sure I'll wait to add in some LED lighting,etc as well. Is my Duet 3 Mini 5 + going to be able to handle all this?

Sorry if this question is considered too obvious, I'm apparently missing my marbles today. Oh yeah- prob yesterday too.

@dc42

I see another thread that recently touched on this, but I'm still wondering what the most optimal power setup is going to be given my cfg of PanelDue7 connected to the Duet3 Mini 5+ and externally powered SBC.

great post here: duet3d dot kom/topic/35950/external-5v-supply-for-sbc-raspberry-pi-4-and-duet-3-mini-5
explains this a bit better, but there has to be a tradeoff somewhere. I want the Pi to be stable with it's own power supply, but also know the Duet3 Mini5+ is going to be needing adequate power for the PanelDue7,etc...
I'm also aware that the 26 pin ribbon cable has limits with that tiny gauge wire and do not wish to push things too far.

After I get past this last power cfg issue, I can power it all up and start to finally commission this printer!

@mikeabuilder

Hmm.
An idea for sure, but if I recall correctly Duet with an attached SBC does not allow network commands?
That's the problem I ran into a few weeks back, anyways.

According to AI the reason being:
If you're getting a "network command not allowed" error on your Duet SBC (Single Board Computer), it usually means you're trying to send a network-related G-code command while the Duet is not currently configured to operate in "SBC mode," where it directly handles network communication with a connected computer; check that your Duet is properly set up to work with an SBC and that the SD card is empty as the Duet needs to be running in SBC mode to execute network commands.

And I agree...the likelihood of getting your LAN Mgr. to allocate a fixed IP address in a EDU environment is slim at best.
Even fire-walled and sandboxed to infinity, the temptation for those college kiddos to setup servers using fixed IP's is too great to overlook.

@dc42

I have been on this planet for 62 years... and technology has come a long, long way. Working in a scientific research and engineering background with 1200 employees, 3D printing really helped pave the way for prototyping, short run production and proof of concept every day.

Now I have my own company and rely on 3D printing (among others) to brings my ideas in the world, including one I was able to prototype and create in my kitchen, now an actual consumer item and the best in it's class. I have 2 patents on that one (and counting). Check out Sealgenie if you want to know more.

Being an inventor means you are always trying to make it better, faster, lighter smarter...using technology to your advantage. I have created 3D printed parts for family, friends and others just because I could- often times it was special parts that were no longer available or so esoteric parts simply were not made available to the public.

Pushing the envelope with 3D printing has been a great inspiration to ALL makers, and my latest is a novel graphene/carbon fiber filament (and SLA resin) that actually IS hundreds of times stronger, unlike the fake stuff they try to peddle to the consumer market now. I have world-wide patents pending on that, among others already)

So...when you ask- What can you do with a 3-D Printer?
My answer is..what CAN'T YOU DO?

Hello All-

Recently unboxed my Open Builds C-Beam CNC machine kit and after looking it over...is there any advantage of replacing the stock Black Box Motion Control system with a Duet board? I have a Duet 2 new in box and might be downgrading my Duet 3 Mini 5+ since it has a couple of blown drivers. I should only need 3 driver circuits for the C-Beam anyways, so this way it can still be of limited use on a smaller scale project like the C-Beam.

Also- Looking at the Worker Bee CNC as well, looks promising. Thoughts?

• Cheers!

@oliof

Thanks for the reply- I'm hoping for the best, but preparing for the worst.

Going to pull the board off the printer today and look at it real close with my digital Microscope and also continuity test all the Z Stepper motors wire runs.

The weird thing is, the rear Z motor seemed to be working when I moved to a spare driver (Out 6) on the mini expansion board. That tells me that both the stepper motor AND wiring to that motor are intact and functional.

I also have a Duet 2 I could test with, but not really as it only supports 5 drivers and I need a minimum of 6 for this Rat Rig V-Core 3 printer, as you are well aware.

This may be a good time to print up the V-Core 3.1 upgrade printed parts, since my RatRig is down and I still have my trusty little Flash Forge Creator Pro to print on. It's horribly slow...but it still prints really nice prints.

@Tinchus

I know you mentioned that your display is the Waveshare 7" model connected via HDMI, I had a similar issue with the Duet 7" PanelDue and version. 3.5.4...it simply would not work via HDMI with the Duet Pi 32 bit image. It worked just fine under the Rasp Pi native image. I ended up having to connect it via a10 pin ribbon cable and worked great. So much for HDMI...

I know It's not a solution for you, but just wanted to let you know you were not the only one.
From what I can tell, HDMI trys to use specific display modes, and not automagically, either.

You Tube video covers the basics- Make sure you test the HDMI output outside of Duet Pi first, this proves that your display still works, just not with the current Duet Pi image.
[Fix Black screen on boot | No video output | Raspberry Pi Guide](https://www.youtube.com/watch?v=Sbwedsfov

From what I can tell, the HDMI output is in a display mode that the Duet Pi Image doesn't like...

• Cheers!

@dc42

I remembered that this board had the ability to drive 6 motors, so I re-mapped my rear Z to my open 6th driver circuit on the extension board. It works there, but my front stepper is out of phase:

Warning: Driver 0.2 warning: phase B may be disconnected

So...that's not good, looks like 2 drivers may be toast. What a way to start a build.

Here's my M122 results:

1/18/2025, 3:25:46 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 (27 max)
=== RTOS ===
Static ram: 103496
Dynamic ram: 107784 of which 12 recycled
Never used RAM 30456, free system stack 198 words
Tasks: SBC(2,ready,1.4%,839) HEAT(3,nWait 6,0.0%,323) 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,1.5%,110) MAIN(2,running,95.6%,762) IDLE(0,ready,0.6%,29) AIN(4,delaying,0.8%,264), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:05:21 ago, cause: power up
Last software reset at 2025-01-18 22:14, reason: User, Gcodes spinning, available RAM 30480, slot 2
Software reset code 0x6003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU revision 3, ADC conversions started 241089, completed 241087, timed out 0, errs 0
MCU temperature: min 25.3, current 31.2, max 31.4
Supply voltage: min 24.0, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
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: standstill, SG min 0, read errors 0, write errors 0, ifcnt 12, reads 29174, writes 12, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 29176, writes 10, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 12, reads 29174, writes 12, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 12, reads 29174, writes 12, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 12, reads 29174, writes 12, timeouts 0, DMA errors 0, CC errors 0
Driver 5: standstill, SG min 0, read errors 0, write errors 0, ifcnt 12, reads 29174, writes 12, timeouts 0, DMA errors 0, CC errors 0
Driver 6: standstill, SG min 0, read errors 0, write errors 0, ifcnt 12, reads 29174, writes 12, timeouts 0, DMA errors 0, CC errors 0
Date/time: 2025-01-18 22:27:00
Cache data hit count 719104473
Slowest loop: 3.98ms; fastest: 0.09ms
=== 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 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.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 0x0000803
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== CAN ===
Messages queued 2763, received 0, lost 0, errs 1517266, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 26 (min 26), ts 1607/0/0
Tx timeouts 0,0,1606,0,0,1155 last cancelled message type 30 dest 127
=== SBC interface ===
Transfer state: 5, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 12382/12382
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: 29.53, max time between full transfers: 88.3ms, max pin wait times: 79.3ms/22.8ms
Codes per second: 0.15
Maximum length of RX/TX data transfers: 4359/864

@dc42

Uh oh...that doesn't sound good. At all.

So....If a driver is blown, how repairable is that? If it's just a MOSFET or cap I can probably desolder and repair that.

If a logic circuit is toast, that means a chip and with the age of this board(even though it's only been out of the original package for a month) what are the chances of warranty? Hmm...

Any schematics or board level information I can use to test against? My FLUKE meter awaits...

Thanks for the information...albeit concerning.

• Cheers!

Hello @juliann @fcwilt @Nurgelrot @oliof

Hate to resurrect this thread, but was hoping you had seen this before:

Have started to commission my RatRig V-Core 3 (404x400) and have also run into some unusual issues:

SuperSlicer was adding in all kinds of Klipper based commands in the print GCode...so I reluctantly went back to Simplify3D 5.12 just to get something to slice and do test prints with.

First prints were dismal...nozzle was way too close to the bed, so I re-ran true bed leveling, mesh calibration, cleared all prior mesh data and proceeded to do some basic test prints.

After baby stepping a bit whilst printing I could def see an improvement in surface finish of the layers; not so dull looking and a bit shinier, which to me means close to proper height.

Halfway through I got a ton of driver overheating alarms...so I shut down and printed up a new backer plate for the Duet3 Mini 5+ which is now mounted with an increased backplate space of 20mmvs the 5 that were there originally.

Today I fire it all up and do my normal home axes, but the back Z stepper motor has gone all wonky....it is trying to lower itself while the front 2 are raising? Hit emergency stop and repeat...same thing. Ugh.

What could cause my steppers to go out of phase like this by itself? I checked my config.g for the steppers section and that has not changed.

I think this RatRig V-Core 3 has promise...if I can just get rid of the quirks that seem to come with it.
Any help from you Core X-Y Gurus is ALWAYS appreciated!

@dc42

I just ran into the same thing... 2 of my drivers were complaining about over heating...yikes!
This is on a Duet 3 Mini 5 with 6 active stepper motors.

So, I'm off to print a backing plate with taller stand-offs and a mount for a blower fan. My stepper motors are all fairly cool, but the amperage draw makes sense. My FLIR ONE camera came in handy yet, again! ; )

• Cheers!

@T3P3Tony

That's why I was puzzled by the code output...I DID select RepRap Firmware in the output section of SuperSlicer.
Look's like it has it's mind made up on Klipper. Going to un-install and start over...something's not right there.

Thanks again to all!

• Cheers!

@Phaedrux said in Failed to get file info. Illegal parameter letter '_':

_

EDIT - I DID find one END_PRINT near the end, replaced it with an M0 (doh)
But there are a metric boatload ton of _ characters in that code...are they not supposed to be there?
EXAMPLES:

START_PRINT EXTRUDER_TEMP=240 BED_TEMP=90
SET_PRESSURE_ADVANCE ADVANCE=0.05
SET_VELOCITY_LIMIT SQUARE_CORNER_VELOCITY=5
;WIPE_START
;WIPE_END

...and so on and so forth...

Ugh. 1 of 4494 instances found

Thanks @Phaedrux , A hunting I will go!

Hopefully it's near the start of the code and not buried in the middle somewhere...

• Cheers!