With the Beijer CAN Library (BCL), your software environment can extract vehicle information from CAN data. The BCL actually translates CAN data into useful and insightful data for your product. The BCL is the heart of our technology, which is used in all our products such as the Beijer CAN Interface (BCI), Beijer CAN Controller (BCC) and the Beijer CAN Module (BCM). But this Beijer CAN Library can also be integrated directly into your product, creating a complete software solution!
Car manufacturers each use their own CAN protocols and there are even differences per type, model and engine variant. Making and keeping your product CAN-compatible therefore requires a lot of effort, while you mainly want to concentrate on what you are really good at. CAN solutions are our specialty. For decades we have been researching new cars and translating all those different ‘CAN languages’ into one readable format. The BCL is precompiled for your specific platform and is linked to your software environment. Your software environment will retrieve CAN data from vehicles via the Library.
All this offers:
• A total solution for your product.
• The certainty that your equipment can handle all desired CAN data in all vehicles.
• Time saving, because the entire process of examining cars, analyzing/processing CAN data and keeping it up-to-date is taken off your hands.
• Cost effective because an integrated solution has no unnecessary hardware.
• Beijer CAN firmware maintained by highly advanced algorithms that enable processing of the latest CAN technology.
• Easy installation, supported by vehicle-specific INCAR instructions in six languages.
• A professional CAN solution based on proven technology that has been used in our CAN products (BCI) for over 15 years.
Phase 1: Beijer analyzes CAN data and collects interpretation knowledge from all car makes and types.
Phase 2: all raw data is subjected to Beijer technology. An ingenious process that translates and enriches the raw data.
Phase 3: your product with our BCL is fed with valuable In-vehicle data.
Phase 4: your customer receives all vehicle information he has requested via your application.
The choice to integrate our component is not a light one. After all, you are not buying a separate interface that connects a system to a car. For that reason, we would also like to invite you for a non-binding conversation with our people who can inform you about all the ins and outs involved in such an integration process. We then work towards a joint process in which we define the list of parameters (dataset) and vehicles for your application and make agreements about this that are in line with your service(s).
