When it comes to long-time system monitoring or testing, a typical approach is to generate long-term logs containing CANopen traffic data covering multiple hours or sometimes even days. However, the often unsolved question is: how do I efficiently examine a log file with possibly 100s of thousands of CANopen messages? A typical approach is to load the log file into a spread sheet program and do manual searches, color highlighting and sometimes run custom scripts or macros to help locating issues.
ESAcademy’s Logxaminer helps with the post analysis of such recordings. It creates statistics and event lists on a configurable level of detail. This drastically shortens the time to get “real results” out of a CANopen log recording made. Statistics are not only produced globally, there are dedicated statistic views for each node present on the network during the recording.
Per node statistics include:
- Minimum/maximum heartbeat time
- Minimum/maximum SDO response time
- Number of bootups
- Number of emergencies transmitted
- PDO message rate
The Logxaminer not only produces statistics, it also generates an event listing with all important system events. The event listing filters information from the log including:
- Node ID assignment (by LSS)
- Bootups (expected/unexpected)
- SDO Aborts
- Unexpected messages
- Errors in LSS sequences
- Errors in SDO sequences
If a network is not stable, then the system event listing highlights potential clues as to what goes wrong where.