cbus:socketcan-en
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
cbus:socketcan-en [2019/01/10 14:27] – rjversluis | cbus:socketcan-en [2024/04/12 07:42] (current) – [Pi01CAN Interface] rjversluis | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== SocketCAN ====== | ====== SocketCAN ====== | ||
[[: | [[: | ||
- | [[: | + | [[: |
[[: | [[: | ||
* [[: | * [[: | ||
+ | * [[: | ||
\\ | \\ | ||
// | // | ||
- | |||
- | {{: | ||
\\ | \\ | ||
=====Introduction===== | =====Introduction===== | ||
- | The RPI-CAN MCP251x Interface board needs a Raspberry Pi 2/3.\\ | + | The __**[[: |
- | SocketCAN is only available if the Rocrail server runs on the same Raspberry Pi with the RPi-MCP251x | + | SocketCAN is only available if the Rocrail server runs on the same Raspberry Pi with the PiCAN on it.\\ |
- | The communication with CBUS(CAN) is direct and binary; No bidirectional conversion needed between the MERG Gridconnect ASCII framing.\\ | + | The communication with RCAN((Supports also CBUS)) is direct and binary; No bidirectional conversion needed between the MERG Gridconnect ASCII framing.\\ |
The 12VDC power supply for the connected CANGC* units can be provided wit a __**[[: | The 12VDC power supply for the connected CANGC* units can be provided wit a __**[[: | ||
+ | |||
\\ | \\ | ||
Line 26: | Line 26: | ||
\\ | \\ | ||
- | ===== RPI-CAN MCP251x | + | ===== Pi01CAN |
- | * https:// | + | * **[[:rocnet:pi01can-en|PiCAN-01]]** |
- | + | ||
- | {{https:// | + | |
+ | [[: | ||
+ | //The I2C parts can be left out If the RocNet connection is not needed. (Just write a remark in case its ordered at GCA.)//\\ | ||
\\ | \\ | ||
=====Raspi Setup===== | =====Raspi Setup===== | ||
Line 72: | Line 72: | ||
</ | </ | ||
//If the Pi-CAN should be used with MBUS, the bitrate must be set to 250000.//\\ | //If the Pi-CAN should be used with MBUS, the bitrate must be set to 250000.//\\ | ||
+ | |||
+ | :!: **Note:** On newer PiOS versions add a file named / | ||
====Check==== | ====Check==== | ||
< | < | ||
- | pi@keltenbahn: | + | dmesg | egrep -i " |
[ 3.998382] CAN device driver interface | [ 3.998382] CAN device driver interface | ||
[ 4.051102] mcp251x spi0.0 can0: MCP2515 successfully initialized. | [ 4.051102] mcp251x spi0.0 can0: MCP2515 successfully initialized. | ||
Line 81: | Line 83: | ||
===== Rocrail Setup ===== | ===== Rocrail Setup ===== | ||
- | {{:cbus:cbus-socketcan-en.png}}\\ | + | {{:cbus:rcan-setup-en.png}}\\ |
* Select type SocketCAN | * Select type SocketCAN | ||
* Set Hostname(device name) to **can0** (If not set: can0 will be used.) | * Set Hostname(device name) to **can0** (If not set: can0 will be used.) | ||
Line 98: | Line 100: | ||
\\ | \\ | ||
- | =====Hardware===== | ||
- | * https:// | ||
- | * http:// | ||
- | * https:// | ||
- | \\ | ||
===== CANService ===== | ===== CANService ===== | ||
As alternative to running Rocrail on the Raspberry Pi, it is also possible to use the __**[[: | As alternative to running Rocrail on the Raspberry Pi, it is also possible to use the __**[[: | ||
It behaves like a GC1e.\\ | It behaves like a GC1e.\\ | ||
+ | |||
+ | \\ | ||
+ | ===== Alternative CAN Board ===== | ||
+ | This low-cost // | ||
+ | {{: | ||
+ | The Raspberry __[[# | ||
+ | < | ||
+ | oscillator=8000000 | ||
+ | </ | ||
+ | Check the board which frequency the crystal has printed on it:\\ | ||
+ | {{: | ||
+ | This example shows 8000 kHz -> 8000000 Hz\\ | ||
+ | For CAN speeds above 125kHz it is recommended to replace this crystal with a [[https:// | ||
+ | \\ | ||
+ | |< >| | ||
+ | | Wiring | ||
+ | ^ Shield ^ Rpi ^ Rpi Pin number(s) ^ Remark ^ | ||
+ | | VCC | 5V | 2, 4 | With 3V3 it will receive, but cannot send CAN packets. | | ||
+ | | GND | Masse (Ground) | 6, 9, 20, 25, 30, 34, 39 | | ||
+ | | CS | GPIO 8 (CE0) | 24 | | ||
+ | | SO | GPIO 9 (MISO) | 21 | | ||
+ | | SI | GPIO 10 (MOSI) | 19 | | ||
+ | | SCK | GPIO 11 (SCLK) | 23 | | ||
+ | | INT | GPIO 25 | 22 | | ||
+ | |||
+ | **Notes:** | ||
+ | * This board is __not isolated__. (ISO1050) | ||
+ | * A ground connection on the screw terminal is missing, and it is __strongly recommended to connect the ground__ of the CAN cable to the GND pin of this board to avoid static voltage which could destroy the electronics. | ||
+ | |||
+ | |||
cbus/socketcan-en.1547126837.txt.gz · Last modified: 2019/01/10 14:27 by rjversluis