ecos-en
Differences
This shows you the differences between two versions of the page.
| Previous revision | |||
| — | ecos-en [2025/04/22 11:12] (current) – [Synchronise] stefanf | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ======ESU ECoS and Märklin CS1(R)====== | ||
| + | [[: | ||
| + | [[english|Content]] -> [[english# | ||
| + | |||
| + | \\ | ||
| + | |< >| | ||
| + | | {{https:// | ||
| + | | ESU ECoS 2 (50200 & 50210) | ||
| + | |||
| + | \\ | ||
| + | > **Note:** A factory reset of the ECoS might be necessary, if a previously working system "all at once" starts to slow down. | ||
| + | > See this __**[[https:// | ||
| + | |||
| + | \\ | ||
| + | > **Note:** It is possible to connect a CS1 (60212) to Rocrail. | ||
| + | > See this __**[[https:// | ||
| + | Configuration CS1: \\ | ||
| + | | ||
| + | {{ : | ||
| + | \\ | ||
| + | As for the configuration of the CS1: | ||
| + | * IP-Address: 192.168.1.117 | ||
| + | * Gateway: 192.168.1.1 | ||
| + | * Network: 255.255.255.0 | ||
| + | * DHCP Check Box is disabled | ||
| + | =====Setup===== | ||
| + | {{ecos1-en.png}}\\ | ||
| + | Check your setup to find out how the ECoS is configured in the your LAN.\\ | ||
| + | If you have problems connecting to Rocrail, try to connect the ECoS to your Web Browser using section 8.6 of the ECoS handbook (2011). \\ | ||
| + | The same IP address or hostname that was used connecting the ECoS to your Web Browser is the IP address or hostname you need to enter in Rocrail. | ||
| + | |||
| + | ====Hostname==== | ||
| + | {{ : | ||
| + | Set the IP address or DNS name to match your ECoS. (Device name in the ECoS settings.)\\ | ||
| + | As an example hostname ' | ||
| + | Click the triple dot button {{icons: | ||
| + | * **Note:** Modern WEB Browser do no longer support Java Applets. \\ Use a [[https:// | ||
| + | ====Port==== | ||
| + | The default port for the ECoS is 15471. | ||
| + | ====Version==== | ||
| + | ^ Version ^ Function ^ | ||
| + | | 0 | RailCom messages with offset +1. | | ||
| + | | 2 | RailCom messages with the same offset, 1601, as occupancy. | | ||
| + | |||
| + | * **Hint:** It is normal that occupancy detectors and Railcom data come through different channels. After discovering the Railcom channel, create a normal feedback (sensor) with this address and enter it in the corresponding block with the " | ||
| + | ====Synchronise==== | ||
| + | Synchronise the loco definitions with the ECoS.\\ | ||
| + | This option is also needed to __**[[: | ||
| + | > See also the __**[[https:// | ||
| + | |||
| + | **Note** After the initial download of locomotive information using the synchronize function, it is recommmended to turn synchronize off (it uses quite a few resources). For the addition of a few locomotives the **[[: | ||
| + | ====Discover==== | ||
| + | |< >| | ||
| + | | **Rocview -> Control -> Discover** | | ||
| + | The Discover command can be used to get the locos from the ECoS.\\ | ||
| + | Newly discovered locos during the session are automatically added to Rocrail.\\ | ||
| + | The Discover option is a " | ||
| + | |||
| + | =====ECoS Throttle===== | ||
| + | To synchronize the ECoS throttle with Rocrail the Server option __**[[: | ||
| + | |||
| + | \\ | ||
| + | =====Command Station Variations===== | ||
| + | ====ESU ECoS 1/2==== | ||
| + | //ECoS 1 (black & white screen) {model 50000- 4 Amp} with Railcom or ECoS 2 (color screen) {model 50200- 4 Amp or 50210- 6 Amp} with Railcom and RailcomPlus.// | ||
| + | //For the ECoS 1; Railcom and RailcomPlus is available in the power district of an ECoS Booster.// \\ | ||
| + | | ||
| + | |||
| + | ====Märklin CS1 Reloaded==== | ||
| + | //The Märklin CS1 (Reloaded) {model 60212} is technically the same as ECoS, except it does not support Railcom or RailcomPlus.// | ||
| + | //Railcom or RailcomPlus is available in the power district of an ECoS Booster.// \\ | ||
| + | [[http:// | ||
| + | |||
| + | ====Piko SmartBox==== | ||
| + | //The Piko SmartBox is technically the same as ECoS but only supports the DCC format.// \\ | ||
| + | //With the Smartbox you can use ESU Detectors, but the GUI is missing to configure them. Currently, you can not configure it through the network interface. You can try to program using an ECoS (or otherwise) and then attach them to a Smartbox, they should work. \\ | ||
| + | See ESU Forum (in German): http:// | ||
| + | {{: | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | \\ | ||
| + | |||
| + | =====Setup connection and Command Station===== | ||
| + | {{: | ||
| + | The ECoS must be connected to the LAN as described in section 20 of the manual. The best way is to provide ECoS with a static IP address; section 20.1.2 of the manual. | ||
| + | In this example it is set to 192.168.10.50. \\ | ||
| + | **Remark:** Sometimes the PC (Win XP, SP3) can't connect the CS1 (ping timeout) via network although the IP address and the wiring is correct. In that case you should start the PC //before// the CS1 boots.\\ | ||
| + | Check if Rocrail PC can make a connection with ECoS: open the Web interface of the ECoS with an Internet browser [[http:// | ||
| + | |||
| + | Now we can setup Rocrail. | ||
| + | Start the Rocrail server and the Rocrail GUI. | ||
| + | Choose File/ | ||
| + | Fill in the IP address (the one in this example) and the port number 15471 (this is a fixed value). | ||
| + | Remove the not used controllers, | ||
| + | |||
| + | {{ecos_controler.png}} | ||
| + | |||
| + | ====Test the connection==== | ||
| + | With the Power On command we can test the communication. Select Control / Power On. The first time nothing happens because Rocrail is in Power Off and ECoS in GO (Power ON). Select it again. The ECoS should swap now to STOP mode. Repeat it and the ECoS swaps to GO and Rocrail shows Power On. If the settings for communicating with ECoS is correctly set then you can now start adding locomotives. | ||
| + | |||
| + | {{ecos_power.png}} | ||
| + | |||
| + | \\ | ||
| + | =====Locomotives===== | ||
| + | In the ECoS-> | ||
| + | |||
| + | ====New Locomotive added to the ECoS, during the Rocrail session==== | ||
| + | As soon as a non-mfx locomotive is added to the ECoS, then this is immediately available for use in Rocrail. | ||
| + | When a new mfx locomotive is added to the ECoS, then a query against the Ecos Lok table is performed by the program. After this operation the new mfx locomotive is also immediately available for use in Rocrail. \\ \\ | ||
| + | |||
| + | ====Manually add a locomotive to Rocrail==== | ||
| + | Select Tables/ | ||
| + | :!: The link between ECoS and Rocrail is __NOT__ by address but by loco ID as has been set in the ECoS. __The ID must match exactly with the name for this loco in the ECoS__. \\ | ||
| + | > **Note:** The locomotive has to __exist__ in the ECoS. | ||
| + | In this example the " | ||
| + | |||
| + | {{ecos_loc1.png? | ||
| + | |||
| + | In the tab " | ||
| + | |||
| + | > **Note:** The address is not important as the link is done by the ID, however, the address __must not be 0 (zero)__. | ||
| + | |||
| + | > **Note:** The protocol should remain to **' | ||
| + | |||
| + | |||
| + | {{ecos_loc2.png? | ||
| + | |||
| + | ====Loco Test==== | ||
| + | The first loco can now be tested. In order to do so for instance a throttle is opened and the loco is started. | ||
| + | |||
| + | {{ecos_loc_start.png}} | ||
| + | |||
| + | \\ | ||
| + | =====Switches===== | ||
| + | For a first test a new switch is created by either using the track plan editor or from the menu Tables -> Switches. The connection between a switch and ECoS is carried out by the switch address. The ECoS is working with continuous addresses (see also **[[: | ||
| + | |||
| + | |||
| + | {{ecos_turnout1.png? | ||
| + | |||
| + | \\ | ||
| + | The following table can be used to determine the values to be entered into the address and port fields, respectively: | ||
| + | | ECoS Address | Rocrail Address | Rocrail Port | ECoS Address | Rocrail Address | Rocrail Port | | ||
| + | | 1 | 1 | 1 | 13 | 4 | 1 | | ||
| + | | 2 | 1 | 2 | 14 | 4 | 2 | | ||
| + | | 3 | 1 | 3 | 15 | 4 | 3 | | ||
| + | | 4 | 1 | 4 | 16 | 4 | 4 | | ||
| + | | 5 | 2 | 1 | 17 | 5 | 1 | | ||
| + | | 6 | 2 | 2 | 18 | 5 | 2 | | ||
| + | | 7 | 2 | 3 | 19 | 5 | 3 | | ||
| + | | 8 | 2 | 4 | 20 | 5 | 4 | | ||
| + | | 9 | 3 | 1 | 21 | 6 | 1 | | ||
| + | | 10 | 3 | 2 | 22 | 6 | 2 | | ||
| + | | 11 | 3 | 3 | 23 | 6 | 3 | | ||
| + | | 12 | 3 | 4 | 24 | 6 | 4 | | ||
| + | |||
| + | \\ | ||
| + | The values for other ECoS addresses can be calculated: | ||
| + | * Address = (ECoS-Address -1) / 4 + 1 | ||
| + | * Port = (ECoS-Address -1) mod 4 + 1 | ||
| + | |||
| + | > Tip: Google can calculate expressions like '' | ||
| + | |||
| + | The figure above shows how to enter these values for ECoS address 26 in the Rocrail dialogue: | ||
| + | |||
| + | |||
| + | \\ | ||
| + | =====Detector Extension Outputs===== | ||
| + | In the EcoS touch screen interface, you can define an accessory ( e.g. A two states light signal) with a DCC address. You then associate two outputs of the ECoS detector extension to this accessory to reflect its state (one for the red led, one for the green led). | ||
| + | Then in Rocview, you also define a signal of the same kind as the one defined in the ECoS, and with the same DCC address. | ||
| + | |||
| + | \\ | ||
| + | |||
| + | =====S88 configuration===== | ||
| + | Note: **The ground terminal of the first sensor module must be connected to the ground pole of the tracks.** \\ \\ | ||
| + | |||
| + | > **Note:** The ECoS differentiates between 8 and 16 port S88 modules. Currently Rocrail defaults to 16 ports, thus continuous addresses are not possible. | ||
| + | Add the S88 bus to your ECoS (screen shot from a ECoS II (version 4.0.2)), follow ECoS instructions -- Section 22: S88 Bus configuration. | ||
| + | You can see that two S88 modules have been added to the ECoS. | ||
| + | S88-1: sensor 1 through 16 and | ||
| + | S88-2: sensor 1 through 16. | ||
| + | |||
| + | You can see that 3 sensors (2, 3 and 4) of S88-1 show a status of occupied. | ||
| + | |||
| + | {{ECoS S88 screen.png}} | ||
| + | |||
| + | This is a picture of the Rocrail Sensor monitor. You can see that the same 3 sensors have a state = 1 (active). | ||
| + | |||
| + | {{Rocrail Sensor monitor.PNG}} | ||
| + | |||
| + | |||
| + | Here are the corresponding settings in Rocrail. The addressing in Rocrail differs from the addressing in ECoS. | ||
| + | For S88-1 the Rocrail addresses are 1 through 16, for S88-2 the addressing starts with 17 through 32, S88-3 would use address 33 - 48, etc.. | ||
| + | |||
| + | |||
| + | {{Rocrail Sensor screen.PNG}} | ||
| + | |||
| + | Note the address of 18 on the Rocrail Sensor Interface screen, for the 2nd sensor of S88-2. The " | ||
| + | |||
| + | {{Rocrail Sensor screen 2.PNG}} \\ | ||
| + | =====ECoS Detectors===== | ||
| + | When using ESU Detectors the addresses are prefixed with 16, The first sensor has address 1601 and the last one in the string has address 1616. Once the 100th sensor (MADA 7.4, PADA 100) has been reached then the Rocrail addresses start with 1700, etc..\\ | ||
| + | {{ECoS_Detector_addresses.jpg}} \\ | ||
| + | When installing a new sensor, the current status is not displayed but only updated after the status changes. To read the sensors __**[[: | ||
| + | |||
| + | ====RailCom Detectors==== | ||
| + | :!: ESU RailCom Detectors can trigger many messages per second and will have negative impact on communication which leads to delayed incoming sensor events.\\ | ||
| + | A work-around is to disable broadcasting addresses over RailCom channel 1 in all loco decoders. Also disabling RailComPlus is recommended.\\ | ||
| + | {{: | ||
| + | \\ | ||
| + | |||
| + | =====Shutdown===== | ||
| + | If needed Rocrail can send a shutdown command to the ECoS controller. | ||
| + | Check the " | ||
| + | |||
| + | {{ecos shutdown.PNG}} | ||
| + | |||
| + | \\ | ||
| + | =====Programming===== | ||
| + | ====Programming Track==== | ||
| + | ECoS Firmware: 4.1.0\\ | ||
| + | Rocrail revision: 10285\\ | ||
| + | Before using the programming track the rail power must be set to ON(GO).\\ | ||
| + | ====POM Loco Decoders==== | ||
| + | ECoS Firmware: 4.2.3\\ | ||
| + | Rocrail revision: 13974\\ | ||
| + | Before using POM the rail power must be set to ON(GO).\\ | ||
| + | ====POM Accessory Decoders==== | ||
| + | ECoS Firmware: 4.2.3\\ | ||
| + | Rocrail revision: 13998\\ | ||
| + | Before using POM the rail power must be set to ON(GO).\\ | ||
| + | |||
| + | |||
| + | |||
| + | \\ | ||
| + | |||
| + | =====Protocol===== | ||
| + | {{ecos: | ||
| + | {{ecos: | ||
| + | {{ecos: | ||
| + | [[esu-ecos-email|ECoS PC Protocol Lizenz]]\\ | ||
| + | |||
| + | ====Online help==== | ||
| + | <code bash> | ||
| + | telnet < | ||
| + | help()< | ||
| + | |||
| + | # Online help for the ECoSNet 0.5 implementation of your ECoS2 4.1.2 | ||
| + | # | ||
| + | # | ||
| + | # About help: | ||
| + | # | ||
| + | # This help. | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | # Basic ECoSNet protocol description. | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | # Short explanations of the available commands. | ||
| + | # | ||
| + | # List of implemented errors. | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | # As a general advice, if something seems ambiguous, just give it a try. | ||
| + | # Most things will be obvious afterward. | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | # See also there for the licence condition of this specification | ||
| + | # | ||
| + | # | ||
| + | # Implemented objectclasses: | ||
| + | # model | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | # loco | ||
| + | # | ||
| + | # | ||
| + | # route | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | # | ||
| + | |||
| + | </ | ||