Rocrail is a BiDiB licensee.
The addressing is linear: FADA
Only the Bus(ID) and the Address fields are used.
| Addressing starts in Rocrail with one; Null is not used.
Port zero on the LC is in Rocrail address one.
|BiDiB Port||Rocrail Address||Rocrail Port|
if sensor and input types at the same board exist the sensor range is 1 .. 128 and the input types are at 201 .. 328.
|White||Current||Auto scaled; "mA max." is 100%|
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
Host name or IP address.
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.
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.
If this option is activated, it will be reported if a loco ID is no longer recognized by a RailCom detector.
The Watchdog Feature will be automatically checked at startup.
Read the Configuration page for more information on node configuration.
To be able to detect multiple Railcom decoders in the same section the following option must be set:
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:
The Wizard can be connected to TCP port 62875 to configure nodes.
The Communication must be disabled before port 62875 will be serviced.