dbaker48 I thought about that, but confused myself thinking about DCS. Which the battery is the first thing to check, only in the engine. The engine not remembering it's identity. That's why I suggested deleting and readding the engine. dn't think the remote would discriminate between which command to process.
I thought about that, but confused myself thinking about DCS. Which the battery is the first thing to check, only in the engine. The engine not remembering it's identity. That's why I suggested deleting and readding the engine. dn't think the remote would discriminate between which command to process.
Not in the engine, DCSman. In his remote. Those DCS folks speak another language.
God bless TCA 05-58541 Benefactor Member of the NRA, Member of the American Legion, Retired Boss Hog of Roseyville , KC&D Qualified
Chief it might be rubbing off on me as my wife is and I have been married to her for 30 1/2 years but it was just one of the batteries really that was causing it.
Life's hard, even harder if your stupid John Wayne
http://rtssite.shutterfly.com/
Don
rtraincollector Well problem is now solved. It was caused by a low battery it was reading 0.07 so it was dead so the controller wasn't getting enough power to power the inferred light in the red button for speed
Well problem is now solved. It was caused by a low battery it was reading 0.07 so it was dead so the controller wasn't getting enough power to power the inferred light in the red button for speed
Are you blonde? Couldn't resist. Best part was you figured it out. Next time someone presents that problem, we'll all ask, "Have you checked the batteries in your controller." Was great talking to you.
RT,
That is some problem! Based upon everything you said, I guess just go back to the basics.
- Check wiring from Base to track, Loose?
- Try deleting and re-adding engine.
Posting question on other forum?
Well discovered one more thing as I try and figure this out on both bases no matter which controller I use there not receiving the signal to move all other signals it receives so now the question is why? What could be blocking it. and for just that. and how both bases and controllers at the same time
I did but thanks for coming up with an idea. this is one weird problem
When you test the two remotes sequentially, pull the batteries out of the one not being tested.
Did one more check runs in conventional fine so I'm lost for some reason all engines not receiving command to move other than in boost for the legacy and the atlas engine.
Every thing was running great for past year haven't run in about a week all was fine then today horn works, couplers work, crew talk work, tower com works boost works, brakes work work even direction works but can't get it to move with turning dial. Changed batteries same thing,, changed controllers same thing, changed bases same thing, tried both engines on the layout same thing I have no idea no wiring or any changes have been changed. Tried an engine I put ERR in everything but movement no boost or any type) tried an original tmcc (1995 vintage) direction and couplers only
Our community is FREE to join. To participate you must either login or register for an account.
Get the Classic Toy Trains newsletter delivered to your inbox twice a month