Is anybody using this? It sounds interesting, but maybe only for automated operations? Have any of the other manufacturer's embraced the idea?
I have the right to remain silent. By posting here I have given up that right and accept that anything I say can and will be used as evidence to critique me.
Not using it, not willing ot be limited to using just Digitrax decoders.
Railcomm is supported by more (has become an NMRA standard), but you need to use Railcomm compatible boosters, or install a cutout device on the output of each one, negating the use of inexpensive boosters as a cheap way of adding more power/power districts.
--Randy
Modeling the Reading Railroad in the 1950's
Visit my web site at www.readingeastpenn.com for construction updates, DCC Info, and more.
I am setup for transponding via BDL168. Not worth the hassle.
There is only one commercially available application that uses Transponding and that is Soundtraxx Surroundtraxx. But many if not most, are using the Surroundtraxx system without Transponding, so go figure.
There is no commercial application available that uses Railcom to my knowledge. Any other use of Transponding or Railcom requires you play with the likes of JMRI and scripting.
My Transponding setup is just too temperamental for any use and I have worked with Digitrax directly to try and sort out the issues without succes.
Only Digitrax decoders support Transponding. NO other decoder manufacturer picked up on it. I used SDN144 for transponding and that was nothing but problems. I had bettre luck with Transponding using the single function only Digitrax decoders (TL1). But gets expensive, as I was using Soundtrax Tsunami and Digitrax LT1 combo. I wanted to use the SDN144 to bring the cost down.
Your experience may be different.
I gave up on it.
Marc
There may be no commercial applications for Transponding or Railcomm, but JMRI reads both. Also, many systems that support Railcomm actually do Railcomm Plus which adds more - like self-identifying the loco as soon as you place it on the track, and map the F keys if the throttle design allows naming them something instead of just F1, F2, etc. Like the ESU CabControl with the Android-based throttle. Stick a supported loco on the track and the throttle will ID it and register it.