JMRI: ESU ECoS Support

JMRI can connect to an ESU ECoS command station via an Internet connection.

To configure the connection:

Turnout, Sensor and a basic throttle and power support is available for a JMRI-connected ECoS unit.


Only basic support for throttles via the Ecos is supported. When an entry from the roster, or a DCC address is directly entered into the address field, JMRI will check the existing list of ECoS locos for a match on the first DCC address it comes across. If there is no match, the throttle will create an entry in the Ecos which will be listed as "Created By JMRI" with a default of 128 speed steps.
From version 2.9.4 when you close down JMRI, you will be prompted to either delete or keep the entries in the ECoS.
Consisting is NOT supported


ECoS-connected senors on the s88 bus have names like "US100:01", where "U" is the system name for esU ecos, "S" means sensor, "100" is the s88 board address registered in the Ecos, and "01" is the port on that board.


ECoS-connected turnouts have names like "UT123", where "U" is the system name for esU ecos, "T" means turnout, and "123" is the address.

Ecos Initialisation

When JMRI first starts up, it reads the turnout, sensor and loco information from the ECoS, which might take a couple seconds. Turnouts and Sensors are automatically added into the JMRI tablesk, this is necessary so that a link can be made between the sensors and turnouts configured in the ecos and the accessory address that JMRI uses.
While gathering the loco information from the ecos, JMRI will check to see if there is already a roster entry assoicated with the loco. If the check fails, the system will ask if you wish to add import the Loco to the roster.

Ecos Loco Database

The Ecos Loco Database allows you to view all the locos that are configured on the Ecos, Assign them to a JMRI roster entry to the loco or import it in to the JMRI roster.

Importing Locos from the Ecos

When importing the loco to JMRI, it currently only creates a skeleton record, that contains the loco Name along with the decoder type if selected and the loco address. This process does not currently import any CV values stored on the Ecos into JMRI.

Exporting Locos into the Ecos

When a new roster entry is created in JMRI, you will be asked if you wish to add the roster entry in to the Ecos Database. The ecos entry will use the roster id as the loco name, set the speed steps 128, and set the loco address. The number of speeds change be changed in the Ecos Preferences Menu.


This is currently not supported by the Ecos.

Additional information on the ECoS can be found on the ESU web site.

Support for ECoS was first available in
JMRI 2.3.3.
Support for the ECoS throttle was first available in
JMRI 2.7.4.
Support for the ECoS s88 Feedback Sensors was first available in
JMRI 2.7.9.
Support for the ECoS RailCom Feedback was first available in
JMRI 2.99.7.