Train Telematics/Diagnostics with 4 x CAN Gateway

What problem did you solve?

Our project required us to monitor signals generated from various sources on the machine, such as engine speed, manifold temperature and pressure. Additional signals were generated by CAN-native sensors and existing CAN-based control units. One of the main challenges of the project was merging these different signal types into a single data stream, while maintaining galvanic isolation between the buses.

How did you solve it?

The CANmod.router's four independent and galvanically isolated CAN ports allowed the four CAN streams to be passively monitored and seamlessly merged into a single bus. Connecting the router to a CANedge3 4G LTE logger enabled it to be conveniently connected and powered without the need for additional wiring. Conflicting messages could be handled either via filtration or by leveraging the 'mux-mode' of the CANmod.router. Further, each CAN bus was analysed to deploy CAN filters/prescalers for optimizing the data stream.

What benefit has this led to?

The CANmod.router provided us with an immediate solution to our technical challenge, saving us valuable time in developing the core functionality. Its ease of use, online guidelines and configuration tool eliminated the steep learning curve usually associated with a new tool. The solution was almost plug & play, requiring only basic configuration and minimal adjustment. The logged MF4 files are easily accessible from our S3 bucket via CANcloud for analysis using asammdf.

Why did you choose the CANmod?

We chose the CANmod.router based on our previous positive experience with CANedge modules. Its compact size, ease of use and immediate compatibility with CANedge loggers make it the most logical choice for this application.

   — Alberto Bellato, owner