ecos-en
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| ecos-en [2020/04/12 14:12] – [ESU ECoS and Märklin CS1(R)] smitt48 | ecos-en [2024/04/18 02:08] (current) – [Manually add a locomotive to Rocrail] rainerk | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| \\ | \\ | ||
| - | | {{http:// | + | |< >| |
| + | | | ||
| | ESU ECoS 2 (50200 & 50210) | | ESU ECoS 2 (50200 & 50210) | ||
| Line 17: | Line 18: | ||
| Configuration CS1: \\ | Configuration CS1: \\ | ||
| | | ||
| + | {{ : | ||
| + | \\ | ||
| As for the configuration of the CS1: | As for the configuration of the CS1: | ||
| * IP-Address: 192.168.1.117 | * IP-Address: 192.168.1.117 | ||
| Line 44: | Line 47: | ||
| ====Synchronise==== | ====Synchronise==== | ||
| Synchronise the loco definitions with the ECoS.\\ | Synchronise the loco definitions with the ECoS.\\ | ||
| - | This option is also needed to __**[[: | + | This option is also needed to __**[[: |
| - | > See also the __**[[http:// | + | > 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===== | =====ECoS Throttle===== | ||
| Line 92: | Line 100: | ||
| ====Test the connection==== | ====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 this all function you have all setting | + | 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 |
| {{ecos_power.png}} | {{ecos_power.png}} | ||
| Line 98: | Line 106: | ||
| \\ | \\ | ||
| =====Locomotives===== | =====Locomotives===== | ||
| - | | Starting with revision 12579 a loco will be created, if needed. | | + | In the ECoS-> |
| - | | Starting with revision 2.1 - 327 the functions of the loco will be created, if needed. | | + | |
| - | In Rocrail-> | + | |
| ====New Locomotive added to the ECoS, during the Rocrail session==== | ====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. | 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. (Version 12637). \\ \\ | + | 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==== | ====Manually add a locomotive to Rocrail==== | ||
| Select Tables/ | 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__. \\ In this example the " | + | :!: The link between ECoS and Rocrail is __NOT__ |
| + | > **Note:** The locomotive has to __exist__ in the ECoS. | ||
| + | In this example the " | ||
| {{ecos_loc1.png? | {{ecos_loc1.png? | ||
| Line 116: | Line 124: | ||
| > **Note:** The address is not important as the link is done by the ID, however, the address __must not be 0 (zero)__. | > **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 **'ServerDefined'**. For Motorola decoders the protocol may be set to ' | + | > **Note:** The protocol should remain to **'Default'**. For Motorola decoders the protocol may be set to ' |
| Line 128: | Line 136: | ||
| \\ | \\ | ||
| =====Switches===== | =====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 **[[: | + | 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? | + | {{ecos_turnout1.png? |
| \\ | \\ | ||
ecos-en.1586693521.txt.gz · Last modified: 2020/04/12 14:12 by smitt48