Skip to main content

6 replies

DCS Wifi Error: "Selected Switch is Inactive"

jdstucksjdstucksOGR Forum Member SUPPORTING MEMBER

I was thrilled to receive the DCS Wifi unit for my layout this Christmas. I purchased the app, updated my remote and TIU at the train store, and plugged everything in. I even backed up the remote to save my engines, accessories, and switches. I imported everything successfully to the app and can run the trains no problem. The switch and accessory names all made it over to the DCS app. However, when I go to active one of my switches or accessories I receive the following error message "Selected Switch is Inactive". 

Does anyone know why this is happening and how it can be fixed? I've already done an app re-set and imported the backup files a second time but nothing changes. The traditional DCS remote still throws the switches successfully. 

Thanks in advance. 

- Jason

Original Post

Replies sorted oldest to newest

jdstucksjdstucksOGR Forum Member SUPPORTING MEMBER

Barry - Thanks for reaching out. I was able to solve the issue which I'll explain. But first, to answer your questions:

  • Is the problem with one switch or all switches? All switches/Accessories
  • Is DCS App free, Standard or Premium version? Premium
  • Which platform, iOS or Android? iOS
  • One TIU or multiple TIUs? 1 TIU
  • Normal or Super TIU mode? Normal
  • How many AIUs connected to which TIUs? 2 AIUs
  • What version of DCS, WIU firmware and DCS App? v3.0.2

I fixed the issue by manually selecting each switch/accessory in the app and editing the switch/accessory path. I basically just reconfirmed which TIU, AIU, and AIU port each switch/accessory should be associated with. It took a mere 5 minutes to complete this for all 16 programmed switches and 3 accessories. Everything has run flawlessly since doing this. 

- Jason 

Barry BroskowitzBarry BroskowitzOGR Forum Member MEMORIALIZED MEMBER

Jason,

I'm  not surprised. There are bugs in the import from remote process, a number of which I've reported previously. However, on iOS the issue that you had wasn't one of those that I found.

Regardless, it's possible that if the remote that you cloned had sustained issues prior to being cloned, that could have been the cause of the problem. I did see some anomalies in that regard during beta testing. My fix was similar to what you did, i.e., replacing the corrupt data from the clone file.

Last edited by Barry Broskowitz

Add Reply

Views: 359
Post
The DCS Forum is sponsored by

Membership Required

We're sorry. You must be signed in to continue. Sign In or Register
×
Are you sure you want to remove from your Block List?
×
Loading...
×
When you block a person, they can no longer invite you to a private message or post to your profile wall. Replies and comments they make will be collapsed/hidden by default. Finally, you'll never receive email notifications about content they create or likes they designate for your content.
Note: if you proceed, you will no longer be following .
×
Link copied to your clipboard.
×

Access to this requires an OGR Forum Supporting Membership

OGR Forum Supporting Membership

Help support this forum with an OGR Forum Supporting Membership.
You will be able to watch the videos in the INSTRUCTIONAL VIDEO FORUM!
A one-year OGR Forum Supporting Membership is only $12 per year, so sign up now!


    OR     


Access the ALL the OGR VIDEO FORUMS AND  over 300 back issues of OGR
with a DIGITAL SUBSCRIPTION!



$12.00 per 12 Months (plus tax if applicable)
×