Content → Command Stations → BiDiB

• Configuration | Setup examples | USB Mapping | OpenDecoder
• Power Manger | BiDi Server Option | Loco Code
• BiDiB & Rocrail Wiki (DE)

BiDiB is a protocol which supports P&P with a high reliability communication level.
For more information:

• http://bidib.org/
  • License DE EN

Rocrail is a BiDiB licensee.

The addressing is linear: FADA
Only the Bus(ID) and the Address fields are used.

if sensor and input types at the same board exist the sensor range is 1 .. 128 and the input types are at 201 .. 328.

• BiDi Server Option
• Loco Code
• Create guest Loco on BiDi

• Easy Configuration
• Current sense occupancy detection.
• RailCom® detection; Rocrail Code.¹⁾
• RailCom® KM/H.
• Read/Write CV's on the main, POM, reported by RailCom® mobile decoders.
• CV Programming on the service track. (No hardware available yet.)
• Loco control; velocity, functions…
• BiDiB & DCC Accessory control.
• All port types and macros.
• DCC Watchdog support.
• External throttle support. (MultiMaus, LH90, LH100)
• Booster control.
• Booster diagnostics

IID for addressing this interface directly from without Rocrail.

Device name of the RS232 port.
Typically COMx for Windows; Check the device manager.

The FDTI is supported out of the box: use /dev/ttyUSBx for Linux based systems.
See also USB Mapping.

For Mac OS X the FDTI device driver must be installed: USB to Serial.
After install and connecting the GBMBoost Master a new serial device is found under "/dev/tty.*".
If the productID is not factory standard follow this setup: OpenDCC USB Setup

• http://www.opendcc.de/elektronik/usb/opendcc_usb.html
• Reset Product ID to factory settings: http://wiki.fichtelbahn.de/doku.php?id=interface_treiber

Host name or IP address.

TCP or UDP port.

Communication speed in Bits Per Second.
The current version of the GBMBoost supports 115200 only.

Hardware handshake CTS/RTS.
Disable handshake only if the hardware does not support it.

• Serial (USB)
• TCP (Ethernet)
• UDP (Ethernet)

To activate the secure ACK option of the BiDiB protocol.

The secure ACK interval in 10ms units. 20 is the default. (200ms)
If Rocrail did not send an ACK with in this time frame the event will be resend by the sensor unit.

If a manually operated accessory is reported, as error, Rocrail will try to reset it back to its last known state.

The Watchdog Feature will be automatically checked at startup.

This node overview list will be automatically generated during the connection setup between Rocrail and the BiDiB interface.

Read the Configuration page for more information on node configuration.

Overview

• CAT 5 Twisted pair cable. (AKA Ethernet patch cable)

To be able to detect multiple Railcom decoders in the same section the following option must be set:

• Send zero speed command at power on

The reported Location ID must mach with a Sensor-ID in Rocrail.
This sensor should have its address set to zero.
The reporting address is used for the sensor Code.
IRM only reports arrival and not depart, so for automatically reset use the Sensor Timer.

It is recommended not to add or remove BiDiB modules to/from the bus in automatic mode because this will cause a lot of communication traffic and leads to strong delayed events.
The track power will be shut off in case a module is reported as 'lost'.

Starting with firmware 2.1.4 the GBMBoost Master can be used as Programming Track.
Before programming on the PT the PT-Mode must be set, see the PT Button on the Programming Tab.

The GBM16T with Firmware 2.1.1 must be disconnected from the GBMBoost-Master or set into reset mode:

• OpdeDCC Signal Decoder & BiDiB (DE)

• FTDI Virtual COM Port Drivers

• Protocol
• GBMBoost als Zentrale einrichten (DE)
• BiDiB Wiki (DE)
• Fichtelbahn Shop

Here are decoders listed which are not conform the RailCom specs.

• LDG30/32 SW Version 2.1 → http://forum.opendcc.de/viewtopic.php?f=27&t=547