“Embed allowed us to model the system and be confident about our design before committing to any hardware. The software guided us in the right
path to take and sped up development.”
With the verification level complete, the controller firmware was run with the hardware plant. Each subsystem was vigorously tested employing the established design-simulate-validate procedure. The testing was key to apply to the Safety Evidence Assurance Level (SEAL) standards of Lockheed Martin. Bi-directional hyperlinks to the requirements documents were placed in the Embed diagram with hyperlink-enabled label blocks. Compound block coloring was used to track validation progress. Embed data export with automatic source diagram and time stamp served as evidence of validation of implementation in meeting the SEAL requirements.
With Embed, the code for all the peripherals was created, handling interrupts and scheduling tasks automatically from the graphical diagram. The Engineers were able to iterate and optimize the code. AMETEK was very pleased with its MBD process and Embed's contribution to it. According to Godfrey, “One of the advantages of Embed is that you are not directly coding in C. You are employing a diagram and using the automatic code generator to create the code.” He explains that if the automatically generated code proved too long, for example, he could go back and easily optimize it for efficiency. “Embed allowed us to model the system and be confident about our design before committing to any hardware,” he added. “The software guided us in the right path to take and sped up development.” When it came to the verification and validation exercises, the software allowed code segments to be individually tested and the results logged.
What's Next?
Moving forward, AMETEK plans to use the model-based development process on other projects. For example, it will leverage its work in embedded processors on an armored fighting vehicle for Spain, an underbelly camera for a Turkish aircraft and a fan control for a Canadian vehicle.