The DCC4PC hardware is a combined block occupancy detector and RailComm reader built into one. each board allows for up to 16 blocks to be detected with RailComm feedback on each.
To get the full potential of RailCom this must be used with a system that generates a RailComm cutout in the track signal, along with decoders that support RailComm feedback
Hardware Support: DCC4PC
JMRI connects to the DCC4PC using its own OmniBus protocol rather the TAMs emulated mode.
Sensors are automatically generated for the first six boards (boards addressed 0 -5) during the initialisation of the connection.
Additional sensors for boards above address 5 can be added using the sensor table, only the first sensor on the board needs to be entered, as the remainder on that board will automatically be populated when it is discovered.
The system name of a sensor is made up in the format of DPS1:01, where "DP" is the system name for Dcc4Pc, "S" means sensor, "1" is the board address, and "01" is the port on that board.
Reporters are automatically created when sensors are added as the two are tide together, there is no requirement to manually create these.
JMRI DCC4PC Tools
- DCC4PC Command Monitor
- Send DCC4PC Command
- DCC4PC Info
- DCC4PC Reader Boards
This lists all the processed commands sent and received to/from the interface, this excludes commands sent between JMRI and the interface in the date retrieval process.
Allow commands to be sent to the computer interface or a detection board, also referred to as a child board. Commands written in hex, should be prefixed with 0x, followed by the commands with no spaces, eg 0x0b020a
Retrieves the information for the Computer Interface Device.
Displays the current information of all the detection boards that have been configured. It is also possible to change the address of a board, please note that when doing this it will generate a new set Sensors and Reporters with the new address, it will not remove the old sensors or move any other details across.