Please enable JavaScript to view this site.

winIDEA Help

Version: 9.21.239

Navigation: FNet communication network > How-to guides

Scroll Prev Top Next More

CAN message injection

In this topic:

Requirements

Hardware modification

Message injection

Injection on message reception

 

 

Introduction

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.

 

 

Requirements

iC5700 BlueBox

CAN/LIN Add-on module

winIDEA 9.17.93 or newer

Knowledge of FNet communication

Knowledge of CAN/LIN qualifiers, triggers and actions

 

 

Hardware modification

CAN message injection is physically disabled by default.

CANinjectionJ1CANinjectionJ2

 

 

To enable injection remove the cover on your AOM CAN/LIN device and place jumpers on J1 for CAN1 and J5  for CAN2.

Click to enlarge

 

 

Message injection

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.

 

number1

Configure FNet Operation / CAN1 page.

CANinjection-allow

 

number2

Configure the Action 0.

1. Check option Record injected messages.

2. Select TC4 from the Action drop-down.

3. Enter ID and Data.

CANLIN_Action_IDandDATA

 

number3

Start the Analyzer Session.

 

Number4

Inject trigger via Hardware / Inject FNet Trigger / TC4.

CANLIN_StartTheAnalyzerSession

 

Result of the recording

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.

Click to enlarge

 

 

Injection on message reception

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.

 

number1

Open FNet Operation / CAN1 page.

 

number2

Configure the Trigger 0.

1. Check option Record all messages.

2. Select TC4 from the Action drop-down.

3. Enter ID and Mask.

CANLIN_ConfigureTrigger0

 

number3

Configure the Action 0.

1. Check option Record injected messages.

2. Select TC4 from the Trigger drop-down.

3. Enter ID and Data.

CANLIN_ConfigureAction0

 

Result of the recording

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).

Click to enlarge

 

 

Copyright © 2024 TASKING Germany GmbH