Train ID recognition is not required with a computer-controlled layout: with simple ON/OFF detectors, the PC follows the trains as it controls them, and always knows where they are. But there is one case where I find Train ID (and the new Railcom technology) useful: if you put a new locomotive on the tracks, you need to tell TC which locomotive it is.
Thanks to Railcom, the locomotive can be automatically recognized by TC. For people with a Loconet bus, the Uhlenbrock MARCo module offers a cheap – even if unperfect – solution. Here is a guick guide with Train Controller (Gold, V8).
This will allow you to deposit a new locomotive on one track section, and have TC automatically know which new locomotive is on the layout. You won’t need to tell TC which train it is.
This is a “gadget functionality”, but the Uhlenbrock MARCo only costs about €35 if you already have TC and Loconet.
For this price, it can’t be perfect: this solution has 2 caveats:
The block I will use to “put” new locomotives on the layout.It will also be a regular dead-end siding in normal traffic.
What you need:
I strongly advise reading my full overview of the MARCo module. In a nutshell: it detects train IDs using the Railcom technology on the tracks, and it can push the information using standard Digitrax transponding messages over the Loconet. That’s a good news, because Train Controller knows how to interpret train ID messages in the Loconet language.
We don’t want the MARCo to act as a fancy automation brain, we just want it to send the train IDs over Loconet for our PC to read them. Again, refer to my initial MARCo post to understand its configuration. For the purpose of this guide, here is a summary of my LNCVs (Loconet-CVs):
LNCV #00 (Address of your choice for section 1, in my case: 125) LNCV #02 =1 LNCV #15 =99
[important]TrainController V8 considers train detection and train identification as two separate things. Train DETECTION is your regular ON/OFF detector. Train IDENTIFICATION is the ability for a module to send the train number to TC. [/important]
Train Identification needs to be activated in Train Controller, and so as 2 levels:
In the options of your DCC system, make sure the Train Identification option is checked. In my case, this is a Locobuffer USB:
There are many Train ID technologies, so Train Controller needs a bit more information. You need to activate train identification for each single locomotive you have:
As per the limitations of the MARCo quoted earlier, I will need to split my block in 2 sections: one watched by the MARCo – where I will put my trains – and another watched by a standard ON/OFF Loconet detector – for the block to still be usable as a stop track in normal traffic.
How to setup a block with a MARCo for auto train ID (for new locomotives on the track)AND for regular traffic.
Train identification works for an entire block (not a single detection section), so it doesn’t matter if your section contains several detectors. So go back to the block options, and go to the Train Identification menu. As you now, the MARCo is simulating a transponder from Digitrax (it sends train numbers over the Loconet via the Digitrax protocol). So obviously MARCo is not available in the list, you can select “RX8 transponder zone”. You will need to compute which address your Uhlenbrock MARCo corresponds to in “Digitrax module” numbering. In my case, this is address 8 with input 7.
If all goes well, Train Controller will automatically detect which locomotive it is, sparing you the task of selecting the locomotive manually.
If the train isn’t detected, double check your calculation of the reporting address. It is easy to make mistakes. Also, check the blue LEDs of the MARCo when your train goes over the track section: if the train is Railcom compatible, and Railcom is activated, they should blink.
If you are having further trouble, shut down Train Controller and use the excellent Loconet-Checker software. If you don’t see the MARCo talking to the Loconet at all, then you have a problem with the module configuration, not Train Controller.
Also note the MARCo has 2 track sections, you can use the second section for a similar purpose somewhere else on your layout.
Yes: Train Identification is mostly superfluous with a good PC software such as Train Controller. But still, I like the added functionality of not having to declare new locomotives on the tracks myself.
Let’s be clear: the Uhlenbrock MARCo is not a perfect solution but a cheap one if you already have TC and a Loconet. If you want to spend more money (about 100€ instead of 35€), you may want to look at the Tams Elektronik RCD-2 detector, along with their RC-Link PC interface. Not only is it supported by TC, but you won’t be facing the 2 limitations of the MARCo: the direction of the locomotive AND non Railcom vehicles should be detected (if you connect the RCD-2 to an external on/off detector). Thanks Jean on the French forum Tout sur TrainController for the precious info !
Copyright notice: screenshots in this post are from Train Controller Gold V8 from Freiwald Software, which you can try in demo mode. No copyright infringement is intended.
Merci pour le feedback! En effet garder les boites ou pas a toujours é ...
Bonjour Je suis N'iste et de ce côté là on a plus de facilité pour ran ...
Thank you! I have checked the information regarding the converter - no ...
Hi! Well the Ecoes does support Railcom indirectly through its lan: it ...
Could you please be so kind to advise, does ECoS itself support Railco ...
Digital model railroading: 2016 news roundup
Uhlenbrock vs. ESU: 1990 vs. 2014?
The mother of German high speed – Part 1
Kato N Flying Hamburger (DCC sound, light & Next18)
Fleischmann V100: full DCC overhaul with DH05C decoder
Never miss a model railroading update, subscribe to the LocGeek newsletter.
1 email per month top, unsubscribe anytime!