Duet 3 Mainboard 6HC - initial production run.


  • administrators

    @nitrofreak we are designing a series of CAN connected expansion boards (and tool boards :D)

    https://duet3d.dozuki.com/Wiki/Duet_3_Expansion_Hardware_Overview

    Thats just the first one that we have in test.

    To use external drivers we will be making another expansion board dedicated to that. If in the future there is demand we might also make a mainboard designed specifically for external drivers.

    Stepper drivers definitely have their place, as do servos, the long term goal for the Duet 3 family is to support a wide range of motor options from steppers, servos, BLDCs etc. Clearly it will take time to develop the expansion modules!



  • Damn, cool board! Also you solved all the limitations of duet2 which I came across, very nice work, congrats!



  • @T3P3Tony
    CanOpen support would be great as that is what the industrial servo and stepper drives normally support
    See https://www.can-cia.org/canopen/ for more info



  • @t3p3tony
    I also see mention on the about wiki page that the ethernet port may possibly support EtherCAT in the future, is that EtherCAT slave or master function. Master support would be totally amazing to have as you could integrate EtherCAT servo/stepper drives (depending on what protocol is used, CanOpen over EtherCAT is the most common). Slave support would also be very interesting as it would allow for a low cost EtherCAT multichannel stepper drive with I/O which could easily be used with Linuxcnc.


  • administrators

    CanOpen and EtherCat are both possibilities for the future.

    CanOpen has far too little bandwidth to use for 3D printing, so we are not using it for communication between the main board and the expansion board. Instead we are using the faster Can-FD hardware specification and a protocol loosely based on UAVCan. But the main board supports a second CAN bus that could be used to control slower devices using CanOpen.

    We hope to provide EtherCat master support sometime in the future. EtherCat slave devices require a royalty payment, but master devices do not.



  • Damn. I just bought groceries. I guess I'll have to wait until next month to order. 😞



  • @dc42 Is the DSF tied to Rpi implementations or can we use any SBC that has an SPI bus interface? For instance, I have a half dozen quad core Wandboards with SPI interfaces.

    Oh and maybe this is a question for @chrishamm but what made you guys go with C# and .NET for the DSF?



  • Is the DSF tied to Rpi implementations or can we use any SBC that has an SPI bus interface?

    Its no longer tied to wiringpi library for SPI at least. I suspect official support will be limited, initially at least, but you'll have a fighting chance at least



  • @bearer said in Duet 3 Mainboard 6HC - initial production run.:

    Is the DSF tied to Rpi implementations or can we use any SBC that has an SPI bus interface?

    Its no longer tied to wiringpi library for SPI at least. I suspect official support will be limited, initially at least, but you'll have a fighting chance at least

    Not having official support doesn't worry me 🙂



  • @T3P3Tony

    Purchased, im happy to be an early adopter to support the amazing work you guys do.

    looking forward to getting this thing in my hands.

    Regards


  • administrators

    @gtj0 said in Duet 3 Mainboard 6HC - initial production run.:

    @dc42 Is the DSF tied to Rpi implementations or can we use any SBC that has an SPI bus interface? For instance, I have a half dozen quad core Wandboards with SPI interfaces.

    Oh and maybe this is a question for @chrishamm but what made you guys go with C# and .NET for the DSF?

    It's not tied to RPi, but if you use a different SBC then you will need to port Duet Software Framework to it, and that SBC has better have a good SPI and GPIO driver unless you can write them yourself.

    If the SD card socket is fitted to the Duet 3 then it will be possible to run it in standalone mode (i.e. without the RPi or other SBC) by using the Ethernet interface; but if you do that, you will miss out on a lot of features.

    Using C# and .NET was chrishamm's choice. But in my experience, it is way more productive than programming in C++, when you have the computing power to absorb the additional overhead. Having memory management makes coding much simpler, and the run-time checking of pointers, array bounds etc. speed up fault detection hugely. A few days ago I spent three hours tracking down a null pointer dereference in RRF3 on Duet 3. That would have been pinpointed instantly had I been able to use .NET instead of C++.



  • @dc42

    The Freescale iMX6 platform is well supported in Linux. I wrote some of the device tree and driver stuff for it. 🙂

    Not criticizing the choice of C#, just curious. I haven't done any C# development in about 10 years so I'll have to see what .NET dev tools are like for Linux these days. Hopefully there's an Eclipse plugin. 🙂



  • Hi Guys

    Brain is wandering here. With this new equipment and its expansion capabilities.

    Do you think one Duet-3 with expansion boards could be configured to control for example three identical printers, X3 Y axis drivers, X3 Y axis drivers X3 Z axis drivers and X3 extruder drivers all running at the same time (properly calibrated of course) im thinking print farm applications where numerous printers of the exact same make, model etc are all printing the same g-code at the same time.

    Thoughts.



  • @calvinx IMHO it should be possible to augment IDEX printers to have three extruders.


  • administrators

    @calvinx yes. Map the drivers to the axis and off you go. However if one printer fails you either need to pause all 3 or wait to the end of the tandem print to sort it.



  • @t3p3tony

    Understood.

    My next question is just looking for a little clarification on wiring between the Duet-3 and a Rasberry Pi3B+

    The Engineer in me likes to be well prepared sorry..

    The Wiring Diagram for the Duet-3 shows the pinouts for the SBC 26 pin connector as shown in my render below, my question is, are the pins i have question marked not used ? as they are not mentioned in the wiring diagram.

    alt text


  • administrators

    That's correct, those pins are not connected on the Duet.



  • @dc42

    David Thank you for the faster than light response.

    this will allow me to make up a cable etc.


  • administrators

    We intend to supply a 26 to 40 pin cable with the Duet 3 main board, however if you wish to connect to other pins of the RPi then you will need to use a splitter board or a custom cable.



  • @dc42 David this is very exciting news, I am looking forward to the possibilities for the future.
    I am curious in the what way canopen was not fast enough as it is commonly used in multi axis coordinated motion control applications in Industrial automation.

    If you do bring canopen support into the firmware are you thinking of only supporting the newer canopen fd standard or will you be supporting the original canopen standard. I hope the original standard is supported as there tends to be a fair amount of used hardware on ebay that supports plain canopen


Log in to reply