Professionals in the world of Controller Area Network (CAN, or CAN bus) embedded electronics development and design are most probably familiar with Vector and their CAPL programming, but oddly enough, are not familiar with Kvaser’s t Script. Why? Well perhaps its due to Kvaser’s t Script functionality is relatively new, or maybe because it’s not properly leveraged. Let’s scratch the surface shall, we?
Vector set off to create a system that allows for more direct control of and access to CAN nodes, or ECUs. This resulted in CAPL, a C -based programming language that is based on event handling. Although it may be referred to a scripted language, which means it is compiled at runtime, CAPL is compiled just before runtime.
CAPL has proven itself as a powerful resource for an overwhelming number of organizations which develop, produce, and test embedded systems.
Kvaser’s t Script functionality is relatively new to the game. Similar to CAPL, it is designed to handle events, as that’s the nature of embedded systems. It is C -based (probably no surprise here), and is not a scripted language; it is compiled.
I have developed a wealth of t Script experience and products, some of which I offer here. I can say that this system is a force to be reckoned with; a sleeping giant, if you will. The potential is motivating.
The similarities and parallels these two systems share are not well known. Recently, I tested the portability of CAPL code to t Script, and it is surprisingly portable. The syntax is different, but there’s much potential here that I believe no one has caught on to.
I’D LIKE YOUR FEEDBACK!
Are you interested in porting your Vector CAPL code to Kvaser’s t Script? Please contact me with your thoughts. If there is interest in this strategy, maybe I will offer a utility to port your CAPL to t Script!