CAN Orchestrator

CAN Message/Signal Editing (Phase 1):

  • Import/Export DBC files

  • Automatic conversion of scale unit to match selected device. For example, MoTeC forces pressure channels to read off of the CAN bus in kPa. If the message is transmitted in bar and has a scaling factor you have to change the factor to be factor * scaling. The software will automatically make this conversion when you target the DBC export to a MoTeC device. The initial plan is to provide this automatic conversion for MoTeC, ECU Master, AIM and Cosworth.

  • Best-in class editing (i.e,, dynamic configuration bit orientation in message viewer)

Network Capacity Design Analysis (Phase 2):

  • Specify devices and CAN ports (i.e., the C187 has four CAN ports)

  • Specify transmitted messages and signals

  • Analyze CAN Bus:

    • Estimated utilization

    • Device contribution

    • Impact of moving a device to a different CAN bus

    • Specify received messages allows analysis

    • Analysis of unutilized bits (transmitted but not decoded)

    • Analysis of empty bits (i

Traffic Viewer (Phase 3):

  • View CAN message traffic

  • Automatically identify messages not specified above

Configuration-Driven Message Editor (Phase 4):

  • Configuration-driven message editor