CAN message injection
In this topic:
•Injection on message reception
BlueBox tools support CAN message injection into CAN network. This feature is especially useful for testing MCU response to particular correct or faulty CAN messages. The advantage of injecting CAN messages with CAN/LIN add-on module is a clear and efficient overview of correlation of network activity to MCU activity in one application.
•iC7max, iC5700
•CAN/LIN Add-on module
•winIDEA 9.17.93 or newer
•Knowledge of FNet communication
•Knowledge of CAN/LIN qualifiers, triggers and actions
CAN message injection is physically disabled by default.
To enable injection remove the cover on your AOM CAN/LIN device and place jumpers on J1 for CAN1 and J5 for CAN2.
Message injection can be configured via FNet Operation as shown below. Example below shows how to inject a standard-length CAN message with ID 0x123 and 32-bit all-zero data. A TC4 is set as an action trigger on when to inject this message.
Configure FNet Operation | CAN1 page. |
Configure the Action 0. |
1. Check option Record injected messages.
2. Select TC4 from the Action drop-down.
3. Enter ID and Data.
Start the Analyzer Session. |
Inject trigger via Hardware | Inject FNet Trigger | TC4. |
After manually triggering an injection, a trigger and the injected message will be shown on the Profiler Timeline as can be seen below, together with all of the messages that were already recorded on the bus.
As an example, you will be looking for the message with an ID 0x555, assigning detection of it to TC4 and triggering the output message with ID 0x123. A picture below shows a complete configuration for this kind of behavior.
Open FNet Operation | CAN1 page. |
Configure the Trigger 0. |
1. Check option Record all messages.
2. Select TC4 from the Action drop-down.
3. Enter ID and Mask.
Configure the Action 0. |
1. Check option Record injected messages.
2. Select TC4 from the Trigger drop-down.
3. Enter ID and Data.
As soon as a message with the correct ID will be detected a response message will be injected on the bus. A trigger will also be recorded to distinguish between injected and incoming messages (in case a message with the same ID is already present on the bus).