"For the team’s engineers it is important to be able to write, test and debug the enormous amount of new low-level code, and IAR Embedded Workbench provides an excellent working environment for this."
Forze is a hydrogen racing team, consisting of about 70 students of the Technical University of Delft. Committed to hydrogen since 2007, the team develops hydrogen racing cars. Forze combines the spectacle of racing with innovative and durable technology.
Forze has been using IAR Embedded Workbench in combination with Arm microcontrollers for about five years now.
Sanne Nielsen, Acquisitie Manager at Forze, comments:
For the team’s engineers it is important to be able to write, test and debug the enormous amount of new low-level code, and IAR Embedded Workbench provides an excellent working environment for this.
Building a hydrogen race car comes with major challenges. The use of fuel cell technology in cars is quite new, which means there aren’t as many components available.
Sanne Nielsen again:
The parts we use are from companies operating in a scala of different industries that use different standards and protocols. Many components we use have also been placed in a car. To combine a wide variety of different parts into one electronic system, we are in need of a powerful and intuitive coding environment.
Using IAR Embedded Workbench we are able to write software that allows all components in the system to communicate with each other. It is also possible to keep an overview of all the code, making it easier to alter or add code segments. With the software we wrote, we are able to optimally combine everything in the system to get the most out of it.
Jaan Marten Buis, Forze new Chief Software, comments:
For myself, I am a programmer with moderate experience. Still, I did not have to spend a lot of time figuring out how the programming interface worked as IAR Embedded Workbench has numerous functions which I find quite helpful and that I use on a daily basis.
In particular, I like the possibility to trace variables, find where they are defined, declared and what type they are. Furthermore, I find the JTAG debugging tool very helpful and easy to use. The placement of breakpoints and running the code is fast and convenient in use.
Finally, I especially like how clean and intuitive the development environment is. It offers a lot of functionality, while the main screen is not crowded with too many buttons.
Jan Marten Buis comments:
It is fast and easy to use which saves time when you want to debug code, and this is very important for us as our car have a lot of code. It also allows for quick on-the-go adjustments in the code when a part is not working as expected. Thanks to this feature, the team can test multiple things during one test by making small changes to the software and put it on the car.
Jaan Marten Buis names the debugging environment as his favorite feature of IAR Embedded Workbench:
The debugging environment helps when new code does not do what it should do. Simply running the code and adding breakpoints and checking variable values can help a lot. Also, the navigation buttons while in debugging mode are quite intuitive and allow for many debugging cycles in a short amount of time.