DEP — DEVlink Engineering PlatformUser Guide

Signal Mappings

Every component port in DEP can be tied to a canonical signal, and every canonical signal can be mapped to a bus endpoint such as a CAN frame bit range, a LIN signal, an ARINC 429 label or an EtherCAT PDO. Signal mappings are the single place where these links are defined, for automotive, aerospace and industrial systems alike. The same mappings are compiled into MIL and SIL execution.

Open System → Signal mappings, or Configure → Signal mapping in System Engineering.

Canonical Signal & Bus Mapping for the Multi ECU project: coverage counters, filters and the mapping matrix.
Canonical Signal & Bus Mapping for the Multi ECU project: coverage counters, filters and the mapping matrix.

Coverage counters

CounterMeaning
Port coverageShare of logical ports that have a mapping.
MappingsNumber of canonical mappings.
Unmapped portsPorts without a mapping. They are listed below the matrix, for example 25 unmapped logical ports. Ports connected directly on the canvas do not need a bus mapping.
Endpoint conflictsTwo mappings write to the same endpoint.
Broken referencesA mapping points to a port, network or database entry that no longer exists, for example after a DBC replacement.

Create a mapping

  1. Open the formSelect Create mapping.
  2. Choose the sourceLogical port: the component port, for example VCU / torqueRequest. Canonical DEP signal: the System-wide signal name.
  3. Choose the networkNetwork: Direct / internal, or a CAN, CAN FD, LIN, Ethernet, EtherCAT, ARINC 429 or ARINC 825 network of the System. Give the mapping a Mapping name.
  4. Describe the endpointFill in the fields of the protocol: Message / profile and Signal / parameter (from the database); Frame ID, Bit offset and Bit length (CAN/LIN); Label (octal) and SDI (ARINC 429); Encoding; Address / PDO / service (Ethernet, EtherCAT).
  5. Timing and transformPeriod (ms), and the linear transform Factor and Offset (physical = raw × factor + offset). Add Notes if useful.
  6. SaveSelect Save canonical mapping. All mappings are saved atomically with the System revision.

Work with the matrix

The matrix shows one row per mapping: Status, Component / port, Canonical signal, Network, Protocol endpoint, Period, Transform and Actions.

  • Search by component, signal, network or label.
  • Filter by protocol (DIRECT, CAN, CANFD, LIN, ETHERNET, ETHERCAT, ARINC429, ARINC825) and by status (Ready, Conflict, Broken).
  • Bulk edit: tick Select visible mappings or individual rows, then use Apply to selected (for example, change the period of many mappings at once) or Remove selected.
  • Export CSV and Import CSV: edit large projects in a spreadsheet. An import is applied atomically: either all rows are accepted, or none.

Resolve conflicts and broken mappings

  1. Filter Status = Conflict or Broken.
  2. For a conflict, decide which mapping owns the endpoint, then change or remove the other one.
  3. For a broken reference, re-select the port or the database signal. If you replaced a DBC, use the network's Controlled remapping (see Networks and Restbus).
  4. Run Check in System Engineering. Unresolved mapping problems are reported as DEP-MAP-CONFLICT.

Mappings describe the System configuration. DEP does not write to physical buses, whatever the mappings say.