I am using Tortoise switches that are controlled with DS64s.
Over this past weekend I had a new Digitrax DS64 that apparently decided to become a plastic paperweight. Without any changes being made to the system and without any warning the #3 output refused to respond to commands when attempting to activate the switch attached to it.
My troubleshooting found there was constant voltage on the #3 output (11.93 Volts). The problem being that ‘activating’ the switch did not appear to reverse the polarity of the output which would cause the Tortoise to reverse and ‘throw’ the switch. A few minutes after #3 went south, the #1 output decided to join in and refused to function as well (same problem/symptoms).
I “switched” the Tortoise motors from the DS64 outputs #1 & #3 with the Tortoise motors from the DS64 outputs #2 & 4 to be sure there wasn’t an issue or problem with the Tortoise motors themselves. The problem Tortoise motors, #1 & #3, are now working fine but #2 & #4 are not working. This proved the problem was not with the Tortoise.
As my layout is still in progress, I had a DS64 that was planned for future use that had not yet been installed. I removed the ‘bad’ DS64 and replaced it with the ‘new’ one and all is well, for the present time.
Has anyone here experienced this type of problem with a DS64? If so, is there a fix other than a trip back to the creator?
I’ve had 8 DS64s for about 4 years and had one go bad less than a year in. It had no output, couldn’t program it etc… Digitrax replaced it promptly. In your case, are you sure that the outputs just didn’t lose their switch addresses ? Did you try reprogramming the address associated with the 4 outputs to see if that fixes the issue ? If the DS64 looses the addresses, then no
Speaking of DS64 problems, I have a total of 6. I have 3 of them that have a problem when first powered on they all get thrown to the open position. When I called Digitrax about this they said it was a known issue and that the engineer who wrote the program did this, and he is gone. They have no fix to it.
I would try to re-program them a couple of more times. My NCE switch 8’s lose their address when I get shorts in the system. I picked up an accessory booster and it seemed to do the trick.
I have four DS64’s installed so far, and now that you mention it, some of the turnouts attached to them do seem to move when I power up the layout.
I’ve never considered it to be an issue, though. It’s simply a minor curiosity, so minor in fact that I’ve never even bothered to see if it’s only certain outputs, or certain DS64’s, or whatever.
But if it really bugs you, try closing OpSw 6. That’ll disable Output Auto Power Up, so when you power up the layout, the turnouts won’t move until they receive a switch command.
Are you powering with track power or 12V ? If track power, I’d suggest trying 12V to see if that makes a difference. It shouldn’t but it is worth a try.
On my DS64s in the yard setup, I setup a cascaded route for each track and a clear all cascaded route. While I am not having this issue, it is real easy for me to either hit the panel button or execute the cascaded route address to quickly set the yard to the right configuration.
Did you set it, or did you try to set it? What’s that Yoda quote, “Do or do not… there is no try!” [;)]
Also, does your NCE throttle remember the last switch command it sent to that address, or the last switch command sent to that address, period?
The reason I’m asking is that because of the conversation in this thread I checked the four DS64’s in my yard throat this evening. One of the four exhibited this behavior on all four of it’s outputs, so I closed OpSw 6 and that “fixed” it. It stopped moving at power-up, but if I then sent a command to any of the four addresses, that address would respond accordingly.
That makes me think that either you didn’t actually close OpSw 6, or something (maybe another throttle, or a macro?) is sending a switch command, or you have some noise on your track bus that the DS64 is interpreting as switch commands (I’m assuming you’re using track power for your DS64’s.)
But again, it’s easy enough to work around even if OpSw 6 doesn’t work for you. For example, I have DS64 routes like Jeff mentioned he has (except some of mine don’t need to be cascaded) set up to line the turnouts to a given track in the yard. I also run a JMRI script at layout initialization to set the entire layout to a predetermined state. Your mini-panel will allow a similar type of solution.
In my case I leave OpSw6 thrown because I have panel indicator LEDs in-line with the Tortoise motor controls and I want to see the indicators on power up. However, I am running a Digitrax Super Chief system and while it will remember the last switch address and command, it doesn’t send them on power up. I also run all local 12V power to avoid possible power glitches due to a district losing power, intermittient shorts due to wheel arcing etc… Also, do make sure each DS64 ha a separate Board ID programmed.
I sent the DS64 back to Digitrax. While I was at it I returned the PS14 that died shortly after buying it (the cost of shipping the PS14 back by itself wasn’t economically practical).
Digitrax sent replacements for both items. I haven’t put either item back ‘on-line’ yet so for the time being, I’ll assume the problem has been taken care of.
The replacement PS14 box label now reads “Made in China” rather than “Made in the U.S.A.” While I have a strong aversion to “made in China”, at least they have updated their packaging.