Posts made by taegge

More progress! I'm still missing a few components, but the board is mostly populated. The 5v and 12v/24v regulators are performing well. I got brave and plugged a CM5 in this morning -- green light and no smoke! I haven't come across any major design issues yet (knock on wood).
I've stumbled a few places where my old lead-free solder past didn't flow as well as needed, but have been able to diagnose and rework those issues. The mini-hdmi connector is a huge pain with its hidden row of contacts. I probably won't bother populating this on any other boards I make as it's pretty redundant with the two DSI/CSI and single full sized hdmi connectors.

I've fired off my order to for the pcb and components!
I've also cleaned up the design files good enough to publish if anyone is curious or wants to critique:
https://github.com/taegge/duet_pi

progress pics! (front and back view) It's coming together. I've got everything routed and the design rules checker is happy. I'm going to take a couple more days to mull over some choices, maybe clean things up a little more and send this off to get fabbed! I'm sure there's one killer feature that I'm forgetting to add. Hopefully I think of it before then

You might notice that I gave up on the idea to sandwich the CM5 in-between the boards. It seemed like an elegant idea in my head, but in practice the layout/routing wasn't making sense to me. The CM5 will probably be happier in open air with a passive heatsink anyways.

I'm a big fan of the Duet3 / SBC setup, but the physical interface to a raspberry pi has always bothered me (Different mount points, separate 5v power supply). I intend to develop a daughterboard(?) with the same footprint as the 6HC that will interface a Raspberry PI CM5, and include lots of raspberry pi IO, and some quality of life features for cleaner 6HC/SBC installs.

Features:

• most of the same IO as the CM5 IO board (ethernet, USB A, USB C, HDMI, DSI/CSI, microSD, m.2, fan connector)
• footprint and mounting holes identical to 6HC
• 26pin IO connector is in-line with 6HC such that an enterprising person could make a direct board-to-board connection (or more likely just use a very short ribbon cable)
• 40mm cooling fan for CM5, also cooling back side of 6HC (standard 4 pin connector)
• Accept 12v - 48v Vin similar to 6HC
• Some extra fused distribution of Vin
• 5v @ 5A switching power supply for raspberry pi
• 24v @ TBD A switching power supply (possibly 12/24v selectable?) for powering 1LC toolboards on systems with greater than 24v
  *On the bubble: pcb or chip wifi antenna (I'll likely be sandwiching the CM5 between the two boards, considering adding a separate WIFI antenna for fun, but may just opt for an external antenna. )

I have a preliminary schematic and board layout, but was curious if others had ideas to consider before I order a prototype PCB. If I'm successful I'll of course share the design with the community, but I don't have any plans to produce any significant quantities.

@deckingman That is a good observation. For some reason I was thinking that limitation was resolved in 3.1.0/3.1.1.

That still doesn't quite explain why I couldn't get the G30 S-1 command to return a valid height when the z-probe was connected to the expansion board, but it's good news that more change is coming in 3.2. Maybe that will resolve my issue.

@deckingman Thanks for the suggestion. My primary configuration is a bltouch (type 9 ) connected to the toolboard, which as you mention should be supported. For my sanity, I tried the bltouch (type 9) and a mechanical switch (type 5 and type 8 ) from the main board; there was no change in behavior.

This is leading me to think that the probe is working just fine and that there is some limitation with regards to having the z-axis being driven by an expansion board. I'm slowly working through the firmware source to see if I can find a smoking gun.

(I'm happy to report that with the 3x z-steppers being driven from the main board, bed leveling is performing beautifully! For anyone on the fence, I highly recommend this quality-of-life improvement)

Thank you for the reply. Yes, I was trying to calibrate my trigger height when I encountered this issue. Starting with the nozzle accurately homed (manually), then raised above the print surface, G30 S-1 would a echo an invalid negative value. Also, the z-coordinate would be adjusted "out of home" which is contrary to the expected behavior that you quoted.

M558 K0 P9 C"^20.io0.in" H5 F100 T8000                          
G31 K0 X0 Y-45 Z2.7 P500

I should mention that the invalid value is consistent based on the z-probe setup. For the above, G30 S-1 would echo exactly -2.30mm regardless of when the probe was triggered. Also, my previously homed z-coordinate was adjusted to be -2.30. A subsequent G1 Z0 command would move the Z to [actual trigger height]+2.3mm.

Moving the 3x z-axis steppers back to the duet mainboard is the only thing that seems to resolve the issue. This is OK, but I'd really like to run the Z-axis from the expansion board for wire routing reasons.

(I should mention that I'm running Duet3 with an SBC. Firmware version 3.1.1 on the main board. 3.1.0 for the 3HC and 1LC boards)

I'm excited to be commissioning a ~CoreXYU + 3x Z-axis for bed leveling. I was hoping to run the 3x Z-axis steppers from the 3HC expansion board, but can't quite get things to work right. G30 functions as expected--the probe lowers to the print bed, triggers the z-probe, stops, sets zero and raises .

However, when I probe the bed with G30 S-1, the probe will again stop the movement, but the z coordinate gets adjusted to some negative value (dive height - zprobe height?), and this negative value is what is returned as the z-probe trigger height.
(Obviously, G30 S-1 is not supposed to adjust the z coordinate. The real deal-breaker is that this same strange behavior occurs during bed probing for leveling / mesh compensation which causes the probe to raise higher and higher each progressive step until it raises outside of the dive height)

I was testing primarily with a BL touch, but the same behavior occurs with a generic switch acting as a probe. Also, the same behavior occurs regardless of whether the z-probe is connected to the main duet3 board, expansion board or tool board.

The Fix: G30 S-1 functions as expected and returns a valid probe height when I moved the 3x z-axis steppers to the main Duet3 board.
This is leading me to think that bed-probing with the Z-axis being driven from any board other than the main board is not supported? Or is there some other bonehead configuration issue that I might have missed?