Greg Amer
The Industrial Lead
Mac, Tks for the insight. I think you are correct, I will make life a little simpler and not worry about reporting. If I ever get the "reporting bug" then I can always go back and hook up the red wire.
If you are already using WinLok, it is not that far to add signals later. I am using JMRI and NOT providing electrical feedback. I am relying on the tortoise to move the points when the command is sent. If it doesn't, something is wrong and needs to be repaired. Now, one of the things that I have to do when the program is first started is to get the turnouts synchronized with the panel view. I do this by sending a command to all the turnout to put them into a known state (set for the mainline routes). I use a routing command in JMRI for this. I also use LED's in series with the tortoise motor wires on my control panels.
I use three SE8C's and one DS64 for controlling my turnouts. The SE8C also has 8 inputs available, and I do use these for tortoise position feedback when any tortoise is not commanded through LocoNet.
I don't think it is worth running the extra wires if the tortoise is already computer controlled..
Elmer.
The above is my opinion, from an active and experienced Model Railroader in N scale and HO since 1961.
(Modeling Freelance, Eastern US, HO scale, in 1962, with NCE DCC for locomotive control and a stand alone LocoNet for block detection and signals.) http://waynes-trains.com/ at home, and N scale at the Club.
It's pretty much a requirement for non-Loconet systems, or if you have the ability to toggle the turnout via fascia buttons so no Loconet message is generated. And then only if you want to have a virtual panel in JMRI or something, or use signals and have qualifiers based on turnout position. If the only way to toggle the turnout is via DCC and you do use Loconet, the positions will be already reported - just theoretically not as accurately as if you hooked up feedback.
--Randy
Modeling the Reading Railroad in the 1950's
Visit my web site at www.readingeastpenn.com for construction updates, DCC Info, and more.
Randy tks for the reply. I use tortise with LED's hooked into the motor windings to show me T/O position. With my small pike I can pretty much see all the T/o's and will be able to tell if they are switching or not. It's not 100% bullet proof but good enough I think. I was just wondering if there was some sort of magical component to having a reporting signal.
Well, with no switch contact and Loconet, you know a command was sent to the turnout.
With the switch contact connected for feedback, you know the command was sent and the Tortoise actually moved.
With a microswitch on the throwbar connected for feedback, you know command was sent and at least the throwbar moved (linkage not broken), hopfully the points are still attached to the throwbar and they moved as well.
It all depends on how failsafe you want to make things. Real railroads have lives at stake, but unless you have a turnout right near the edge of the Giant Chasm, there's not too much danger in a model railroad derailment because of a misaligned turnout. If you aren't otherwise using the contacts and the inputs on the DS54, go for it.
Well I have my benchwork up and am about to install my first Tortise on this layout. I have six DS-54's and will use them for facia push button T/O control. One switch on the tortise will be for frog polarity but I have the second switch available on the tortise and was wondering what the advantages of using it for standard reporting to loconet were if any? I don't do any kind of signaling, no detection of any kind. I do run my layout with winlock would there be an advantage to having the reporting for that? I guess the real question for me is "what does reporting do for you?, what do you gain?" Is it worth hooking up the red wire?
Tks for any help or insight.