0
edits
Changes
From IGEP - ISEE Wiki
m
Created page with '=== IGEPv2 EXPANSION === <section begin=IGEPv2 EXPANSION>> The IGEPv2 EXPANSION provides a CAN interface using MCP2515.<br> Several tools are provided by socketCAN to use this …'
=== IGEPv2 EXPANSION ===
<section begin=IGEPv2 EXPANSION>>
The IGEPv2 EXPANSION provides a CAN interface using MCP2515.<br>
Several tools are provided by socketCAN to use this controller:
*candump: dump traffic on a CAN network.
*cansend: simple command line tool to send CAN-frames via CAN_RAW sockets.
*cangen: CAN frames generator for testing purpose.
*canplayer: send CAN frames from a file to a CAN interface.
In order to test the CAN interface you can connect IGEP0022 to a CAN device or network or to another IGEP0022 board.<br>
In the last case, you have to connect the two boards like this:<br>
Board 1 Board 2
.--- ---
| 1 |-X X-| 1 |
| 2 |----------------| 2 |
| 3 |----------------| 3 |
| 4 |----------------| 4 |
.--- ---
If this is your first time accessing CAN bus, check J702 jumper is not connected before follow this tutorial. If you don't have this jumper, don't worry because its function is only for testing.
Now you can set up the interface (on all boards when using multiple IGEP0022 <span lang="en" id="result_box" class="short_text"><span title="Click for alternate translations" class="hps">connected to a CAN network simultaneously)</span></span>:<br>
/sbin/ip link set can0 up type can bitrate 125000
If you want to receive CAN data, use:
candump can0
If you want to send CAN data, use:
cansend can0 123#AABBCCDD
cansend can0 123#R
cansend can0 1F334455#1122334455667788
cansend can0 1F334455#R
On the receiver side, you must see the following messages:
can0 123 [4] AA BB CC DD
can0 123 [0] remote request
can0 1F334455 [8] 11 22 33 44 55 66 77 88
can0 1F334455 [0] remote request
Switch roles and try it again
<section end=IGEPv2 EXPANSION>>
[[Category:CAN bus]]
<section begin=IGEPv2 EXPANSION>>
The IGEPv2 EXPANSION provides a CAN interface using MCP2515.<br>
Several tools are provided by socketCAN to use this controller:
*candump: dump traffic on a CAN network.
*cansend: simple command line tool to send CAN-frames via CAN_RAW sockets.
*cangen: CAN frames generator for testing purpose.
*canplayer: send CAN frames from a file to a CAN interface.
In order to test the CAN interface you can connect IGEP0022 to a CAN device or network or to another IGEP0022 board.<br>
In the last case, you have to connect the two boards like this:<br>
Board 1 Board 2
.--- ---
| 1 |-X X-| 1 |
| 2 |----------------| 2 |
| 3 |----------------| 3 |
| 4 |----------------| 4 |
.--- ---
If this is your first time accessing CAN bus, check J702 jumper is not connected before follow this tutorial. If you don't have this jumper, don't worry because its function is only for testing.
Now you can set up the interface (on all boards when using multiple IGEP0022 <span lang="en" id="result_box" class="short_text"><span title="Click for alternate translations" class="hps">connected to a CAN network simultaneously)</span></span>:<br>
/sbin/ip link set can0 up type can bitrate 125000
If you want to receive CAN data, use:
candump can0
If you want to send CAN data, use:
cansend can0 123#AABBCCDD
cansend can0 123#R
cansend can0 1F334455#1122334455667788
cansend can0 1F334455#R
On the receiver side, you must see the following messages:
can0 123 [4] AA BB CC DD
can0 123 [0] remote request
can0 1F334455 [8] 11 22 33 44 55 66 77 88
can0 1F334455 [0] remote request
Switch roles and try it again
<section end=IGEPv2 EXPANSION>>
[[Category:CAN bus]]
