“We don’t do insects, we don’t do missiles.” – Brett Aldrich (SMACC Architect)
From it’s inception, SMACC was written to support the programming of multi-component, complex robots.
If your project involves small, solar-powered insect robots, that simply navigate towards a light source, and as a developer you’re focused on how to run a state machine on an $1, EEPROM chip with 8kb of memory, then SMACC is probably not the right choice for you… (We recommend an if/else statements, in a while loop, in C99).
Or if you’re project is a hypersonic missile, and because you travel at MACH 7+ you need an update loop that runs at 50MHz, SMACC is also probably not the right choice for you… (We also recommend if/else statements, in a while loop, in C99).
But if you are trying to program a robot with a mobile base, a robotic arm, a gripper, two lidar sensors, a gps transceiver and an imu,
or you’re trying to build an autonomous submarine with an array of sensors and actuators…
or you’re trying to build a UAV that looks something like this…
And you want the ability to program complex autonomous behaviors with ROS right out of the box, in a systematic manner, with deterministic execution, that has the potential to be deployed on systems with real-time requirements….
then you’ve come to the right place.