BiDiB Configuration

Content → Command Stations → BiDiB

• Configuration | Setup examples | USB Mapping

The BiDiB system works with Unique-IDs and local addressing (Path).
The local addressing can change after every startup of the system.
At startup Rocrail creates a mapping between local address and Unique-ID.

Menu: Rocview → Programming → BiDiB

All BiDiB hardware modules have an identify button. If this button has been pushed the this dialog will pop up.
After closing this dialog with the OK button the decimal UID number will be copied to the clip board to make it possible to paste this value into the Bus field(s).

The left value is the hexadecimal and the middle value the decimal representation of the Vendor ID.

The left value is the hexadecimal and the middle value the decimal representation of the Product ID.

Classification of the node.

User defined string for identifying this node.
This name can be used as alternative to the bus value. (UID-Name)
MSG_STRING_GET: STRING_ID = 1: Username, read/write

Program the modified Username string.

In Rocrail the decimal Unique-ID, must be set in the Bus field of the sensor or accessory interface tab.
This UniqueID(Bus) is long and the one to choose is not always an easy job.
The left value is the hexadecimal and the right value the decimal representation of the UniqueID(Bus) number.
The decimal representation is used as bus value for objects. (The decimal representation can and may be a negative number.)

The printed board serial number should read V 0D P 67002900 in this example.

In the tree view every node is prefixed with its class mnemonic(s) between brackets.
Note: A node can provide more then one class.

If an image is found with a file name formatted as "bidib-vid-pid.png" it will be shown on the index page.
For example: "bidib-13-103.png"
The image file size must be less then 50k in PNG format.

The Reporting option requires a file name which must be specified by dialog. The file format is CSV and can be read and manipulated by most spreadsheet programs.
All listed modules are port by port reported. The RocrailID will be also reported if an object is linked to the uid:port:type.

Opens the WEB site of the selected node. (In the default WEB Browser.)

Sends an Identify message to the selected node which will accomplish flashing the LED on the module.

Check if the selected node is still alive. A pong response will be listed in the controller pane. (Monitor trace level.)

Get the last error from the selected node. An error report will be listed in the server pane. (Exception trace level.)

With Drag&Drop the Unique-ID can easily be set on all objects which have an interface Tab:

Rocrail provide a basic implementation for reading and writing features.

Reads all features of the selected node.
This action is required to enable some other tabs in this dialog.

Writes the selected feature with its new value; Check the documentation for writable features.

Use this GBMBoost-Master option with care and use a high interval time like 20. (20 x 100ms = 2 seconds)
Set this value to zero to disable this feature.

The port type to be configured; Check the documentation.
Only some port types have configuration parameters:

BiDiB Ports are zero offset based.

Read the actual configuration settings of the selected port and type.

Write the actual configuration values to the selected port and type.

Use ON/OFF to see if the configured port is behaving as wanted.

After releasing the thumb of one of the sliders the values are send to the module.

The port properties can only be set for port type output and if the selected module supports port configuration like OneControl.

• Timer: Used for I/O type pulse.

• http://www.bidib.org/protokoll/bidib_fw_update.html
• http://www.opendcc.de/elektronik/lightcontrol1/lightcontrol.html
• CoolTerm