mbus:mbus-en
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
mbus:mbus-en [2019/02/14 13:13] – [Lawicel/SLCAN] rjversluis | mbus:mbus-en [2022/02/10 22:05] (current) – [Devices] rjversluis | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== MBUS ====== | + | ====== MBUS TrackBox====== |
[[: | [[: | ||
- | [[: | + | [[: |
- | * [[: | + | * **[[:mbus: |
- | \\ | + | * [[: |
\\ | \\ | ||
=====Introduction===== | =====Introduction===== | ||
Line 10: | Line 10: | ||
The Command Station, Märklin TrackBox(GleisBox), | The Command Station, Märklin TrackBox(GleisBox), | ||
- | ====Overview==== | ||
- | {{mbus: | ||
====Devices==== | ====Devices==== | ||
- | {{ : | + | {{ : |
- | * Raspberry Pi + Rocrail Server + __**[[: | + | * Raspberry Pi + Rocrail Server + __**[[: |
- | * or Banana Pi M1 + Rocrail Server + [[http://lnxpps.de/bpi/|BPi CAN]] | + | * Märklin TrackBox(GleisBox) |
- | * __**[[: | + | |
- | * Märklin TrackBox(GleisBox) | + | |
* Märklin Mobile Station [[https:// | * Märklin Mobile Station [[https:// | ||
- | | + | * [[http:// |
- | | + | * [[: |
\\ | \\ | ||
- | {{mbus: | + | =====Setup===== |
- | =====Type===== | + | {{:mbus:mbus-interface-en.png}}\\ |
+ | ====Type==== | ||
This defines over which interface Rocrail communicate with CAN.\\ | This defines over which interface Rocrail communicate with CAN.\\ | ||
- | ====USB GridConnect==== | + | ===USB GridConnect=== |
//"For small systems."// | //"For small systems."// | ||
The company [[https:// | The company [[https:// | ||
- | The USB connection | + | Fixed baud rate of 500000.\\ |
- | ====SocketCAN==== | + | * WIO-CAN |
+ | * Arduino RCAN | ||
+ | ===SocketCAN=== | ||
//" | //" | ||
SocketCAN can be used in combination of the following components: | SocketCAN can be used in combination of the following components: | ||
- | * Raspberry Pi 2 or 3, __**[[: | + | * Raspberry Pi 2, 3 or 4 |
* Rocrail Server with MBUS as controller (Assuming CAN0 as device.) | * Rocrail Server with MBUS as controller (Assuming CAN0 as device.) | ||
- | * __**[[: | + | * __**[[: |
The advantage of this type is the direct Rocrail Server connection with CAN; It can run without EtherNet and USB.\\ | The advantage of this type is the direct Rocrail Server connection with CAN; It can run without EtherNet and USB.\\ | ||
- | The WiFi on the **Raspberry Pi 3 b+** can be used for visualisation by Rocview, Rocweb and/or andRoc.\\ | + | The WiFi on the **Raspberry Pi 3/4 B+** can be used for visualisation by Rocview, Rocweb and/or andRoc.\\ |
- | ====CC-Schnitte==== | + | ===CC-Schnitte=== |
//"If you already have one."// | //"If you already have one."// | ||
__**[[: | __**[[: | ||
The communication does not use serial framing which could lead to wrong interpretations of data.\\ | The communication does not use serial framing which could lead to wrong interpretations of data.\\ | ||
+ | Fixed baud rate of 500000.\\ | ||
- | ====TCP==== | + | ===TCP=== |
- | //"Alternative | + | //"The Märklin way."// |
Default port 15731.\\ | Default port 15731.\\ | ||
- | Compatible with CS2/ | + | Compatible with: |
+ | * CS2/CS3. | ||
+ | * WIO-CAN | ||
- | ====UDP==== | + | ===UDP=== |
- | //"The Märklin way."// | + | //" |
Fixed read/write ports 15730/ | Fixed read/write ports 15730/ | ||
Compatible with CS2/CS3 communication.\\ | Compatible with CS2/CS3 communication.\\ | ||
The __**[[: | The __**[[: | ||
- | ====Dummy==== | + | ===Dummy=== |
//" | //" | ||
All CAN frames are echoed with the response bit set.\\ | All CAN frames are echoed with the response bit set.\\ | ||
- | ==== Lawicel | + | === LAWICEL |
- | The Lawicel/SLCAN protocol to use with common serial CAN interfaces like **[[http:// | + | The [[http:// |
+ | Fixed baud rate of 115200.\\ | ||
\\ | \\ | ||
- | =====Hostname===== | + | ====Hostname==== |
For UDP and TCP type.\\ | For UDP and TCP type.\\ | ||
The extra field on the right is to set the TCP port; 15731 is used if not set.\\ | The extra field on the right is to set the TCP port; 15731 is used if not set.\\ | ||
\\ | \\ | ||
- | =====Device===== | + | ====Device==== |
The serial device used with type **USB GridConnect** or **CC-Schnitte**.\\ | The serial device used with type **USB GridConnect** or **CC-Schnitte**.\\ | ||
\\ | \\ | ||
- | =====Protocol===== | + | ====Track Protocols==== |
The supported digital protocols by the TrackBox.\\ | The supported digital protocols by the TrackBox.\\ | ||
If all protocols are disabled in the settings, they will be all activated at startup. At least one protocol must be activated.\\ | If all protocols are disabled in the settings, they will be all activated at startup. At least one protocol must be activated.\\ | ||
- | =====Report state===== | + | \\ |
+ | =====Options===== | ||
+ | {{: | ||
+ | ===Report state=== | ||
Report the current, voltage and temperature of the **[[# | Report the current, voltage and temperature of the **[[# | ||
|< >| | |< >| | ||
Line 80: | Line 86: | ||
| Regular | Report every 5 seconds | For use in combination with the Power Manager | | | Regular | Report every 5 seconds | For use in combination with the Power Manager | | ||
- | \\ | + | ===Slot purge time=== |
- | =====Options===== | + | |
- | ====Slot purge time==== | + | |
If a locomotive is nonactive for this period of time, and the speed is zero, it will be removed from the refresh cycle to make place for other locomotives.\\ | If a locomotive is nonactive for this period of time, and the speed is zero, it will be removed from the refresh cycle to make place for other locomotives.\\ | ||
Purging is deactivated if this time is set to zero.\\ | Purging is deactivated if this time is set to zero.\\ | ||
Line 88: | Line 92: | ||
- | ====Acknowledge sensor events==== | + | ===Acknowledge sensor events=== |
Acknowledge the Block type inputs of the __**[[: | Acknowledge the Block type inputs of the __**[[: | ||
Only the ON will be acknowledged. If an acknowledgement was not received the GC2a will resend the event until the block input goes OFF.\\ | Only the ON will be acknowledged. If an acknowledgement was not received the GC2a will resend the event until the block input goes OFF.\\ | ||
The GC2a enables this option automatically after receiving the first acknowledge, | The GC2a enables this option automatically after receiving the first acknowledge, | ||
- | ====Master==== | + | ===Master=== |
+ | **Note:** MS2 Firmware 3.55 and higher does negotiate different, compared with previous versions. This none conform update will be not supported.\\ | ||
+ | **Note:** //Master mode will be disabled in case a CS2/CS3 is detected.// | ||
Puts the connected MS2 in slave mode and provide loco information.\\ | Puts the connected MS2 in slave mode and provide loco information.\\ | ||
After the MS2 is in slave mode, a loco can be selected from the Rocrail server with the following sequence:\\ | After the MS2 is in slave mode, a loco can be selected from the Rocrail server with the following sequence:\\ | ||
Line 102: | Line 108: | ||
| {{: | | {{: | ||
- | ====Read only==== | + | ===Read only=== |
Trace only the traffic on the CAN bus, and do not evaluate.\\ | Trace only the traffic on the CAN bus, and do not evaluate.\\ | ||
- | ====MSApp==== | + | ===MSApp=== |
{{ : | {{ : | ||
Support for the [[https:// | Support for the [[https:// | ||
Line 112: | Line 118: | ||
\\ | \\ | ||
- | =====Programming track===== | + | ====Programming track==== |
This output addressing can be used for activating a relay before programming.\\ | This output addressing can be used for activating a relay before programming.\\ | ||
The TrackBox does not provide a separate output for programming. To avoid programming all locomotives on the main track, it can be helpful to switch to the isolated programming track.\\ | The TrackBox does not provide a separate output for programming. To avoid programming all locomotives on the main track, it can be helpful to switch to the isolated programming track.\\ | ||
Line 121: | Line 127: | ||
All addressing schemes are supported. (FADA/ | All addressing schemes are supported. (FADA/ | ||
The bus value **must** be set to zero.\\ | The bus value **must** be set to zero.\\ | ||
- | ====GC2a==== | ||
- | * Bus = CAN-ID | ||
- | * Address = GC2a port number, 1...16 | ||
\\ | \\ | ||
- | =====GC2a Signal support===== | + | =====Tips===== |
- | This is for simple signals up to 4 LED and max. 5 aspects.\\ | + | * Note: In order to show changes |
- | Only the RED address will be used as offset for all LEDs.\\ | + | |
- | |< >| | + | |
- | ^ Parameter ^ Description ^ | + | |
- | | Control | Aspect numbers | | + | |
- | | Port type | LED | | + | |
- | | Bus | CAN-ID | + | |
- | | Addressing | FLAT from 1 to 16 - number of aspects | | + | |
- | + | ||
- | ====Aspect Values==== | + | |
- | See: __**[[:signal-props-en#value|Aspect Values]]**__ \\ | + | |
- | The number of controlled LEDs will be calculated from the aspect values.\\ | + | |
- | + | ||
- | ===Example=== | + | |
- | ===Aspect value examples=== | + | |
- | |< >| | + | |
- | ^ Value (dec) ^ LEDs ^ | + | |
- | | 0x01 (1) | LED 1 on | | + | |
- | | 0x02 (2) | LED 2 on | | + | |
- | | 0x04 (4) | LED 3 on | | + | |
- | | 0x08 (8) | LED 4 on | | + | |
- | | 0x11 (17) | LED 1 blinking | | + | |
- | | 0x55 (85) | LED 1 and 3 blinking | | + | |
- | | 0x03 (3) | LED 2 and LED 1 on | | + | |
- | | 0x13 (19) | LED 2 on and LED 1 blinking | | + | |
- | + | ||
- | + | ||
- | \\ | + | |
- | =====TrackBox===== | + | |
- | ====Channels==== | + | |
- | Table of known channels: | + | |
- | |< >| | + | |
- | ^ Channel ^ Measurement ^ Units ^ | + | |
- | | 1 | Current | mA | | + | |
- | | 3 | Voltage | hundredth of V | | + | |
- | | 4 | Temperature | C° | | + | |
- | Those three channels will be polled every 5 seconds, and in case of a **[[# | + | |
- | The Trackbox can be added to the __**[[: | + |
mbus/mbus-en.1550146410.txt.gz · Last modified: 2019/02/14 13:13 by rjversluis