CAN Node Emulator

1. CAN Node Emulator CAN Node Emulator Using the Vector CAN-Tech CANalyzer Raj Atwal

2. Outline • HARP-B Hardware Architecture • Purpose • CANalyzer • Host Emulation • HARP Micro • LABView GUI • LO Microcontroller Emulation • Benefits

3. HARP-B Hardware Architecture

4. Purpose • We need to Test Efficiently & Effectively. • We need to Limit User Intervention while testing. • We need to Monitor CAN Bus Traffic. • We need to Test Continuously. • How have we achieved this?

5. CANalyzer • Troubleshooting Tool for CAN bus systems. • Assists in Observing, Analyzing, and Simulating Data Traffic. • Works… • With the raw data bytes within the CAN Message. • At the Application Level, with the actual physical values(ie scaled values). • And above all, integrates easily with existing hardware architectures...

6. HARP-B with CANalyzer CANalyzer

7. CANalyzer Features • Displays data segments of specific CAN messages. • Transmits predefined CAN messages. • Replays recorded CAN messages. • Evaluates and Acquires statistics on bus loading and bus disturbances. • Allows use of Symbolic names for CAN Messages and Signals. • Expansion of functionality via user programming. • Allows Tracing - a real-time listing of bus data traffic...

8. CANalyzer Features HOST • CAN “Sniffer” • Sits on the CAN Bus. • Picks up ALL CAN Messages. • Useful for Observing and Analyzing. • Nice way of keeping track or monitoring data traffic. • Helps in testing. CAN Bus HARP Micro LO Micro Controller OR LABView GUI CANalyzer

9. Program Development • The CAN Access Programming Language - CAPL, is used. • CAPL is application oriented, and very similar to the C Programming Language. • Program blocks can be inserted at any point in the data flow diagram. • CAPL is based on a “Special Event Procedure” concept. • This concept is a simpler version of Interrupts and Interrupt Service Routines. • Use of CAPL results in numerous potential applications...

10. Applications • Data Traffic Simulation. • CAN Node Emulation. • HOST Emulation. • HARP Micro. • LABView GUI. • LO Microcontroller Emulation. • Test CAN Bus Communications between CAN Nodes. • Perform “Event Specific” actions. • Link Between two buses.

11. System Overview LO Microcontroller CANalyzer CAN Bus HOST HARP Micro LABView GUI OR

12. HOST Emulation • Pretend to be the Host. • HARP Micro. • LABView GUI. • Simulate CAN Messages. • Transmit CAN Messages continuously with random data values. • Observation of LO Microcontroller behavior. • Analyze results, especially any discrepancies. • Specifically, we can… • Change Bias Voltages. • Change the YIG Frequency. • Turn Asynch Alarm, Idle, and Debug Modes on and off. • Respond to user requests entered via the keyboard.

13. LO Microcontroller Emulation • We can add CAPL program blocks that make CANalyzer behave exactly like the LO Microcontroller (or any other CAN Node). • When the LO Microcontroller (or any other CAN Node) is absent, testing with the HARP Micro can continue. • CANalyzer responds to RTR’s and all other CAN Messages from the HARP Micro. • This is a key feature, especially when we won’t have the LO Microcontroller.

14. Emulation Topology HOST MICRO OR LABView GUI LO Controller Emulation CANalyzer CAN Bus LO Microcontroller CANalyzer HOST Emulation

15. Procedure for CAN Node Emulation • All participating nodes must be connected to the CAN Bus. • All CAN Messages must be set up in the CANalyzer CAN Data Base. • All CAN Message Signals must be declared within the CAN dB. • Scale the Signals appropriately. • That’s it!

16. Benefits • In the ABSENCE of actual hardware devices, we can use CANalyzer to emulate those devices. • CAN Node Emulation allows • Reduction in delay time for testing. • Helpful in testing other CAN Nodes. • Testing can continue in the absence of any CAN Node. • Thorough and Efficient testing. • System response to a variety of CAN Messages. • Continuous overnight test runs. • Verification.

17. Questions? • Now its Demo Time...