I wanted to run a quick prototype to make sure I understand how it works before going on the actual layout.
Train detection
The English manual is easily found on the Internet and the wiring is pretty straight forward: one of the tracks is isolated and gets its feed from the ECoSDetector instead of directly from the ECoS Command Station. The ECoSDetector gets a direct feed from the ECoS Command Station.
It is very important to follow 0 is black and is direct to the track, whereas B is read and goes through the ECoSDetector.
Now, it is easy to link the ECoSDetector to the track diagram on the ECoS Command Station by using the icon circled in red below:
When everything is wired up and correctly configured, here is what happens:
The track in red shows that this section is occupied!
Train identification
This is all great, but we actually don't know which engine is on that occupied section. Enters RailCom. Decoders equipped with the RailCom protocol can communicate back to the digital station.
I need to insert a RailCom box on the track diagram on the ECoS Command Station by using the icon circled in red below:
So, same as above, but now with RailCom:
We actually see the name of the engine on the track diagram. Unfortunately, ECoSDetector 50094 has only 4 RailCom inputs out of the 16 inputs. However, ESU offers the ECoSDetector RC 50098 that provides only RailCom inputs, but one module has only 4 inputs: http://www.esu.eu/en/products/digital-control/ecosdetector/ecosdetector-rc/