Subscriber & Member Login

Login, or register today to interact in our online community, comment on articles, receive our newsletter, manage your account online and more!

Problem programing DS64 routes

285 views
2 replies
1 rating 2 rating 3 rating 4 rating 5 rating
PED
  • Member since
    April, 2016
  • 362 posts
Problem programing DS64 routes
Posted by PED on Tuesday, May 15, 2018 12:10 PM

I am having a problem programing a route into a DS64 that is triggered by a pushbutton. As far as I can tell, all is wired correctly but the DS64 does set the route when I push the correct pushbutton. Here is my situation:

- I wired a pushbutton to a specific route in the DS64. 

- I used JRMI to load the route into the correct route slot in the DS64 tied to the pushbutton. I am using a  virtual address as my top address. Last switch address is repeated per instructions

- I can now use my throttle and run the route OK

With that setup, here is what is happening:

- I have OpSw 11 = c. This is per manual as well as Digitrax tech info. With this as the only OpSw change, the pushbutton causes the turnout associated with that DS64 input to toggle between thrown/open but will not run the route

- Here is where it gets strange. The manual says to leave OpSw 15 in its factory setting (thrown) because that feature has not been implemented yet. Meanwhile, the Digitrax tech info (KB393) says to set OpSw 15 = c, otherwise it will prevent the local trigger from directly triggering the outputs. I tried to change OpSw 15 in JMRI and it will not make that change. I then made the change with my throttle directly to the DS64 and that would change OpSw 15 to c. However, when I do that, nothing happens when I trigget my pushbutton. ( I can still run the route from my throttle).

I can play around with the setting but I always get the same result with whatever combination I set.

At first I thought perhaps I needed to update the firmware in my DS64 but after searching Digitrax, there is no download for a DS64 update.

I am now stuck. Any ideas what is the problem?

Paul

Washita and Santa Fe Railroad
Circa 1970's in south central Oklahoma

PED
  • Member since
    April, 2016
  • 362 posts
Posted by PED on Tuesday, May 15, 2018 12:38 PM

Update - as I messed around with it some more, I discovered that if I got rid of the virtual address as a top address and used a switch in the route sequence as top address, the pushbuttons works correctly. However, the problem with that no address in any route can include the top address I would be using. If any route uses that top address anywhere in its route, it would create confusion in the route structure. Not sure what would happen but that is a no no.

Don't know why using a virtual address would cause a problem but its not supposed to. Digitrax recommends use of virtual address in this situaltion and their examples use that approach. 

Unless someone knowns how to fix this, I will press on without virtual addresses and figure out something to avoid address conflicts.

Paul

Washita and Santa Fe Railroad
Circa 1970's in south central Oklahoma

PED
  • Member since
    April, 2016
  • 362 posts
Posted by PED on Tuesday, May 15, 2018 3:01 PM

False alarm. After setting up a different DS64 with pushbuttons, everything worked OK on it. Went back to original DS64 and discovered that I had cross wired two switches to the wrong terminals. Fixed that and all is good.

Love the pushbutton routes. Makes routing with yards and complex switch situations much easier without trying to remember all the turnout positions.

Paul

Washita and Santa Fe Railroad
Circa 1970's in south central Oklahoma

Subscriber & Member Login

Login, or register today to interact in our online community, comment on articles, receive our newsletter, manage your account online and more!

Users Online

Search the Community

ADVERTISEMENT
ADVERTISEMENT
ADVERTISEMENT
Model Railroader Newsletter See all
Sign up for our FREE e-newsletter and get model railroad news in your inbox!