Loconet occupancy detectors from Uhlenbrock (left) & Train Modules (right)
Here is my experience with 2 different Loconet detectors.
The first one is the 63320 from Uhlenbrock, which is a “classic”. The second occupancy detector is from a rather unknown Hungarian manufacturer, Train Modules. They are distributed by Conrad in Germany, and I had already tested their accessory decoder.
I may try Digitrax products one day, but they are not distributed through the channels I know, here on the old continent.
I switched from S88 to Loconet for train detection a while ago. Although I still use my old S88 detectors thanks to the Uhlenbrock S88 to Loconet adapter (reviewed here), I now prefer to buy native Loconet detectors.
Both modules have 2 Loconet in/out ports. Both detect the power consumption of locomotives or cars with lighting. The comparison stops here.
Here are the main differences, some of which will be discussed later:
Very straightforward in both cases. Connect the Loconet cable to your Loconet network. Connect the left side pin to the common DCC track power. Then attach your 4 or 8 track sections to the remaining pins. Both modules have holes so they can be screwed under your layout directly. It is to be noted than the Train Modules is twice as small as the Uhlenbrock one. On the other hand, it only controls half the number of track sections…
Loconet detector from Train Modules
The Train Modules detector is delivered with a 4 page manual (in German and English, when purchased in Germany). Programming is simple and efficient:
Uhlenbrock 63320 Loconet
As always, Uhlenbrock decided to complicate things. This is however justified here, since the module has many more functions than the Train modules one.
You can program it two ways:
It gets more complicated with LNCVs if you want to use the advanced functionality of the module.
First, you may want to set the module address to something else than 1 (LNCV #0). This helps programming this decoder independently from others. Then, you can set a number of things:
Options 1 and 2 are great to avoid “polluting” your Loconet with busy/free messages. A train with poor power contacts may indeed be reported as absent for a few milliseconds. These settings can even be set for each track section individually, which is rather powerful.
The third point is part of the “decentralized” automation promoted by Uhlenbrock. I had already mentioned this in my post about their MARCo detector). Since their Intellibox is rather “dumb”, they invite the users to automate their layout at the local level, in each little brick such as this detector. This detector can indeed control switches, or signals, based on the status of the controlled track sections. Up to 2 accessories can be controlled, per section. This is rather powerful. However, my humble opinion still stands: this is the wrong way to go. If you want to automate your layout in a powerful manner, and in a way that can be changed easily, you need a centralized brain. This brain can be a more intelligent command station (e.g. the ESU ECOS II than can handle shuttles), or a computer software.
I did those tests using the free Loconet Checker software, and Rocrail.
Train Modules 65321 under my layout
The Train Modules test was easy: it worked immediately. There seems to be some kind of – limited – anti-flicker control. I have the impression the on/off messages sent over the Loconet are slightly delayed in the case of poor track condition. I can’t be 100% sure though, this would require more tests. In any case, the module works as expected, great.
Uhlenbrock 63320 under my layout
Uhlenbrock managed to ruin the fun once again. I started testing, and no matter what I did, no occupancy message was sent over the Loconet.
So I used another functionality of this module, the “report address”. By calling this address, for example as if it were a switch, the module is forced to send the status of all track sections over the Loconet. I did this, and surprise: the reported status were actually correct (1 track was occupied, the other 7 free). The screenshot below is the result of calling the report address (1017 – 1 = 1016), which correctly shows than section 431 is occupied.
Correct messages from the 63320 when called with the “report address”.
Thanks to two posts in German (here and here), I found a possible solution. It seems polarity of the DCC track power is important for this module. So I did change the polarity on my ECOS II, and did as instructed: programmed the module once again. It still doesn’t work. My module seems to know if the tracks are occupied or not, but keeps the information for itself unless interrogated by force with the “report address”.
So, I am quite surprised with the result of this small experience.
I am 100% satisfied with the Train Module device. It’s simple, it’s small, it works. It’s kind of a pity that the price is rather high for only 4 track sections. Despite the list price of €49.90, Conrad Germany is currently discounting them for €35 “while stocks last”. Is this an end of life product? Is conrad stopping the distribution of Train Modules products? I don’t know.
As for Uhlenbrock, the module still doesn’t work. I have called for help on some forums (and will update this post if anything changes). My assumption is the module needs the ground of the Loconet network and the DCC track to be paired together. This is the case for people using an Intellibox (Loconet and DCC track are grounded internally). This is not the case for me and my standalone Loconet. I may end up discarding this module and using something else. I may found the solution and then think “why didn’t I try that earlier?”. In the meantime, I can’t get this module to work, at all.
Last thought of the day: I really should look away form Uhlenbrock. Some of their products are great, but all of them are designed with users of their Intellibox command stations in mind… They also have a website that looks like it was designed 8 years ago, that they didn’t even bother to translate. Here I’ve said it: they’ve put me in a bad mood 😉
Update from 02-jul-2013: Despite the efficient troubleshooting help on the German forum 1zu160, I couldn’t get the Uhlenbrock module to work. That doesn’t mean it’s a bad product. Probably, it requires a common ground between Loconet and DCC track power, which is not the case in my DIY Loconet installation. I have ordered 2 extra Train Modules devices to replace the 63320.
I always try to be fair and square when giving grades, see the details about the evaluation criteria here !
Reminder: I am a hobbyist and these articles only represent my personal views. I am not receiving any compensation, in any form, from the brands or stores mentioned here. The product names, marketing names, and brands mentioned here are the property of their respective owners.
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 ...
The Monaco TER: too rare to be a model train
Kato N Flying Hamburger (DCC sound, light & Next18)
Arnold locomotive with smoke generator
Digital Protocols in a nutshell (introducing Cheat Sheets)
Mehano Vossloh G2000: Next18 conversion
Never miss a model railroading update, subscribe to the LocGeek newsletter.
1 email per month top, unsubscribe anytime!
Cookies are used to give you the best experience on the site. Cookies are files stored in your browser and are used by most websites to help personalise your web experience.
By continuing to use our website without changing the settings on the disclaimer page, you are accepting cookies as described on the same page.