Through all the product launches we have been involved in over the years, one thing has become very clear: The step between "finished design" and "finished product" is often longer than one had hoped for.
We strive to make both software and hardware as reusable and modular as possible, deriving customer designs from our internal references as often as we can. This saves huge amounts of time in the design phase, but sticking to proven designs also minimizes the risk of unnecessary short rounds and software regressions down the road.
This is our internal SDK that grew organically from components we felt were worth reusing and refining for future projects.
Perhaps the most prominent component is eub_net_fsm, the LTE connectivity state machine that distills years of experience and obscure learning into an easy-to-use API - think of it as a map of the minefield that is cellular IoT.
Homemade might taste best when it comes to cabbage pudding, but when it comes to communication protocols, it's one of the most expensive mistakes you can make. For something that seems so simple on the surface, there is an incredible amount to think about.
Even "headless" devices need to be commissioned, configured and even debugged from time to time and then an HMI (Human Machine Interface) can be invaluable. But:
If HIL is easy to integrate, it has the potential to provide an incredible amount of robustness for very little effort - that's why we decided on a HIL investment that now includes:
