Safety and security – two critical factors in developing software for any application. And with the software-defined vehicle in the near horizon, anything and everything related to software is even more critical. That’s where ETAS’ ASCET-DEVELOPER enters the conversation. With key features including, modeling, validation, automatic code generation and toolchain integration, ASCET enables software engineers to build high-performance, easily maintained, safe and secure embedded software for vehicles. In fact, it’s been a proven solution for over 20 years, powering 450 million ECUs and in compliance with all industry safety standards.
But it’s easy for us to tout its benefits, so we asked Jesse Beeker from TWIG Power, to give some insight on their real-world application of ASCET-DEVELOPER.
For what type of project did you use ASCET-DEVELOPER?
We initially used it on a battery management system and were so happy with it, we plan to use it on a system control unit and motor drive unit soon.
What challenges did you face with the project?
There were a handful of challenges, specifically:
- Limited engineering resources
- Ongoing requirement changes
- Engineering discoveries (i.e., unexpected results) during development
- Target MCU (motor control unit) defined by what was available for purchase
- Third-party software integration
For resource limitation, we were able to use a mix of third-party, low-level drivers along with an entry-level software engineer and system architect to create a solution. ASCET required the software engineer to adhere to high quality standards and allowed the architect to easily review and modify factors when developing the solution.
For the target MCU, we were forced to use a less-desirable MCU that required a solution where a device migration had to be developed before code was written. By using ASCET, we can keep all our code intact and maintain validated algorithms when the transition to a long-term MCU solution occurs.
No. In fact, the majority of the work was performed by a college intern. And while the system architect had some ASCET training, they haven’t been an active user in a while. As with any complex build environment, success comes from being able to get to quickly get to a stable build process. With the Eclipse environment, the amount of training and previous experience is reduced because of the alignment with the benchmark in the MCU space.
Yes, and the reason is simple. We live in a litigious world that is dependent on software, and C-code will never be understood by a legal authority. Model-based code generation is the best defense to situations when software control is questioned. Thanks to ASCET, our products are safe and secure.