Using the CAN Database

What is the CAN Database?

The CAN database is a structured library of predefined messages—typically based on SAE J1939-71 PGNs—available within controls platforms such as IQAN® Design by Parker Hannifin. These messages allow rapid configuration for sending or receiving standardized data, like engine speed, sensor values, or faults, across a machine’s CAN bus. IQAN Design’s built-in database covers many common needs, with the flexibility to add custom or third-party database files as needed.

How Does It Work?

• Each application in IQAN Design comes with a J1939 database; OEMs can import additional files for specialized components (e.g., sensors, third-party displays).
• Filter the database by description or keyword (e.g., ‘speed’), then specify if the message should be received (IN) or broadcast (OUT).
• Imported messages must be linked to appropriate modules. Adjust properties like transmission rate, priority, and address per device and application needs.
• You can export a configured set of messages as a database file to other projects, teammates, or even customers, greatly speeding up system commissioning and ensuring consistency.

Best Practices

• Assign each frame to the correct device. Simply importing a message does not guarantee proper routing or function.
• Review in/out default parameters and adjust these for your application, referencing device documentation.
• Timeout and error checking are not enabled by default. You need to review each message’s error response and set values that match system safety needs.
• Treat database messages as templates to customize. Fine-tune scaling, priorities, and error responses is necessary for each new program.
• Assist with Team Collaboration. Export and import database files to reduce manual re-entry, minimize human error, and streamline multi-developer or multi-system integration.

Expert Tips and Cautions

• Keyword Filters: Quickly search by keywords to find relevant messages.
• Manual Cleanup: Added channels can be incrementally updated, but removing channels requires manual action within the configuration tool.
• Ongoing Maintenance: The database feature has been consistent but should be reviewed with each significant device or software update.

By using the CAN database to its full extent—and customizing beyond “out of the box” defaults—OEMs reduce engineering time, enhance machine reliability, and enable streamlined team and customer collaboration for both current and future equipment programs. Contact us to learn more or sign up for one of our in person IQAN training sessions.