Thanks for the reply! Some of these are not completely clear to me.
@dc42 said in Duet with embedded "SBC":
Here are some reasons
Does anyone make a processor with A-cores, M-cores, and CAN_FD?
Not sure if CAN_FD is present in mentioned combo but I thought there are specialized IC's for CAN_FD?
It's most unlikely that we could compete with the cost of a Raspberry Pi + existing Duet. We don't have the advantages of scale that Raspberry Pi does.
Not sure how RPi can compete with pricing here since you would not have additional RPi cost but only the cost of Duet? Duet would likely have to be a bit more expensive due to using more expensive processor, though the currently one is definitely not cheap.
We would have to maintain our own Linux build.
I still have old Duet 2 without SBC so my understanding might be a bit off here but aren't you already maintaining your own linux build? Additionally base yocto and/or buildroot images are often provided by manufacturers.
We would have to provide technical support for all the functions that the SBC provides.
That's a tough one although considering how much issues you had with SBC communication maybe it would not be so bad. Just a thought.
Some users prefer to use a different SBC, such as Jetson Nano.
Definitely a downside although linux to linux communication is not so hard so people could easily add more computers if they wish to do so.
We would need to manufacture separate Duets for those who don't want the SBC functionality.
Maybe its misunderstanding here but I would not think that separate duet boards are necessary because duet would in that case effectively be SBC and maybe a stripped down version of linux could be made for those who absolutely would not want any applications.