public:cbuspublic:start
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
public:cbuspublic:start [2020/01/22 15:30] – [Identifiers] grovenor | public:cbuspublic:start [2020/01/22 15:56] – [Introduction] grovenor | ||
---|---|---|---|
Line 4: | Line 4: | ||
[[: | [[: | ||
==== Introduction ==== | ==== Introduction ==== | ||
- | CBUS is a Layout Control System running on the [[wp> | + | CBUS is a Layout Control System running on the [[wp> |
- | cbus.php and cbus2.php | + | * **[[https:// |
+ | * **[[https:// | ||
+ | A complete description of CBUS including the full specification and implementation notes is contained in the ' | ||
+ | | ||
- | {{ http:// | + | ===== CBUS Documentation ===== |
+ | This is the public view of CBUS and does not include MERG Technical Bulletins (TBs) or links to any other MERG Copyright material which is available only to members. | ||
+ | |||
+ | [[developerguide|CBUS Developers' | ||
+ | This Guide is intended for those with technical knowledge wishing to develop additional hardware, software and firmware for use with CBUS. It also provides all the technical background and information to enable a better understanding of how CBUS works, along with the rationale for our choices and methods. | ||
+ | |||
+ | [[jmriacccmd|Commanding Accessory Decoders using CANCMD & JMRI]] | ||
- | ===== Message Formats ===== | ||
- | | ||
- | Where the opcode informs the receiving node what to do, using the data as necessary. | ||
- | There are many opcodes, including: | ||
- | - On-Events and Off-Events | ||
- | - Train control, including programming | ||
- | - Node configuration | ||
- | Long Event format is: { opcode, [node-id(2).event# | ||
- | Where the concatenation [node-id.event# | ||
- | Short Event format is: { opcode, node-id(2), device#(2) }, | ||
- | Where node-id and device# are independent. The device# is considered a ' | ||
- | More than one node can send this event, e.g. throttles, and it will have the same effect. | ||
- | By convention, device#s 1-9999 denote ' | ||
- | and device# 10000 the `Start-of-Day' | ||
- | | ||
- | The reason for this partition is that CABs can send short events up to 9999 and it would not be | ||
- | advisable for these to clash with sensor events by mistake. | ||
| | ||
===== Tools: ===== | ===== Tools: ===== | ||
Line 37: | Line 30: | ||
* **SSI** (Solid State Interlocker) from [[http:// | * **SSI** (Solid State Interlocker) from [[http:// | ||
- | ===== Implementation Notes ===== | ||
- | |||
- | * CBUS operates over CAN at 125kbps. | ||
- | * CAN is bidirectional and has built-in error correction and message re-send. | ||
- | * CBUS CAN frames have an 11-bit header and an 8-byte data-part. | ||
- | * The data-part carries the CBUS message. | ||
- | * The header must be unique, and this is ensured by including the 1 byte CAN-ID assigned to the sending node. | ||
- | * The CAN-ID is retained by the node, moving it to a new layout may cause a CAN-ID conflict. | ||
- | * In SLiM mode, the node-id is set by switches, and the CAN-ID is set equal to the low-byte of the node-id. | ||
- | * In FLiM mode, if the node does not have a CAN-ID, one is automatically obtained by self-enumeration: | ||
- | * NB: New modules //must// be introduced to the bus one at a time. | ||
- | * The CAN-ID may be re-assigned: | ||
- | * CBUS uses 29-bit header CAN messages for bootloading. | ||
- | * A complete description of CBUS including the full specification and implementation notes is contained in the ' | ||
- | | ||