Profinity V2 IS NOW IN EARLY ADOPTER RELEASE
Profinity V2 is available now in Early Adopter Release. To support this release we are making the documentation public. To get access to the Profinity V2 installers, please log a support request at the Prohelion Support Portal requesting access to the Early Adopter release.
DBC
The DBC functionality in Profinity provides tools for working with CAN bus database files. These files define the structure of CAN messages, including signals, message IDs, and data formats. This section gives you a high-level understanding of what the DBC functionality can do.
Use the DBC viewer in Profinity to get the Component, Message and Signal names that you want to track
Key Features
This section lists the core capabilities of the DBC functionality. These features represent the main functionality you'll use when working with DBC files in your applications.
- Load and parse DBC files
- Access message definitions
- Access signal definitions
- Convert between raw CAN data and physical values
- Support for different DBC file formats
Usage
This section provides detailed examples of how to use the DBC functionality in your applications. Each example is shown in C#, Python, and JavaScript to accommodate different development environments.
Basic Operations
Basic operations cover the fundamental tasks you'll perform with DBC files, including loading and accessing message definitions.
GetDbcSignal Method
The GetDbcSignal
method retrieves a signal definition from the loaded DBC file using the component name, message name, and signal name.
Syntax
Parameters
component
: The name of the component that sends/receives the messagemessage
: The name of the CAN message containing the signalsignal
: The name of the signal to retrieve
Return Value
Returns a DbcSignal
object containing the signal definition, or null
if the signal is not found.
Value Property
The most important property of the returned DbcSignal
object is the Value
property, which returns the current physical value of the signal.
Important Notes
- The component, message, and signal names are case-sensitive
- Returns null if any of the parameters don't match definitions in the DBC file
- The
Value
property automatically converts the raw CAN data to the physical value using the signal's factor and offset