| This is a simple dialog for doing simple configuration jobs.
For more sophisticated programming the BiDiB Wizard is recommended.
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.
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 GMB16T has also a button, but this is not implemented as an identify button because its not connected to the BiDiB bus.
Pushing this button will set the GBM16T in test mode and will post continuously occupancy messages.
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, or UID, must be set in the Bus field of the sensor or accessory interface tab.
This UID 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 UID 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.
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.
|The CSV file imported and exported as PDF with LibreOffice.|
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.)
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.
|A value of 1 will send every 80ms a message to the GBMBoost-Master.|
The port type to be configured; Check the documentation.
Only some port types have configuration parameters:
|Servo||Left adj.||Right adj.||Velocity||-|
|Light||brightness on||brightness off||dim on||dim off|
|Backlight||dim off||dim on||channel mapping||-|
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.
The Rocrail server only starts a firmware update if the target node has the feature for updating over BiDiB set.
The selected HEX file must be accessible by the server.
The first 50 lines of the selected file will be listed up.
Starts the update process.
The button will be disabled and the text of the button changes to "Wait…" until a program event arrives from the server.
The progress bar range is set to the number of lines in the hex file. The server reports progress every 10th line processed.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <?xml-stylesheet type="text/xsl" href="bidib_products_en.xsl"?> <bidib version="1.0" date="16-08-2013"> <productlist> <product vid="13" pid="101" cid="146" desc="GBM16TC Stand-Alone" url="http://www.opendcc.de/s88/gbm_bidi/gbm_bidi_en.html"> <description lang="de" text="GBM16TC Eigenständig" url="http://www.opendcc.de/s88/gbm_bidi/gbm_bidi_de.html"/> <description lang="nl" text="GBM16TC Zelfstandig" url="http://www.opendcc.de/s88/gbm_bidi/gbm_bidi_nl.html"/> </product> <productlist> </bidib>
|vid||Vendor ID (NMRA)||0…255|
|cidext||Class ID extension (reserved)||0|
|url||WEB Site URL of documentation. (EN)||*|
Description sub-nodes are optional and can be used to add a language dependent text and URL.