Should I ditch SBC mode?
ctilley79 last edited by
One of the main things that drew me to the duet 3 was SBC mode. It's nice having an ultra fast web server to interact with the web interface therefore freeing the controller to do what it does best.
However, I'm seeing SBC firmware features always lag behind standalone mode. The latest example is accelerometer support. When will it be supported for SBC mode? I'm trying to understand the limitations you're facing in development that's causing SBC to be more difficult to implement. What challenges are you facing?
fcwilt last edited by
I got a MB6HC to mess with, tried it with an SBC, thought it had potential and promptly stopped using it.
I find "standalone" mode suits me just fine.
Your mileage may vary.
@ctilley79 The first DSF beta featuring accelerometer support will follow within the next two weeks. To get that working, we'll have to make deeper changes to the SPI protocol including the whole timing mechanism and we'll have to add new interfaces for RRF to write files on the SBC. Because accelerometers were added rather late in the v3.3 development and because there were other more urgent reasons for the v3.3 release, these changes could not make it into the final v3.3 release.
There is no reason why you could not record CSVs in standalone mode and use them in SBC mode at this time, though.
ctilley79 last edited by ctilley79
@chrishamm I take it theres not enough onboard storage on the mainboard to do everything (accelerometer data collection) on the controller, then send it back to the SBC so timing doesn't matter? You could use the controller's sd card as a working area then send back to the SBC through SPI?
jay_s_uk last edited by
@ctilley79 currently, an SBC connected duet doesn't have an SD card on board