Ralphmp
Registered
For some time I’ve been planning a rack railway. My original intention was a simple design which ran from a station at the height of the main railway to the upper terminus. Unfortunately, I can’t implement this for logistical reasons, so I need to have a design where the rack railway trains go part way in one direction and then complete the journey in the opposite direction - see below:
As my layout is all Massoth DCC, I planned to operate the rack railway with the Massoth Navi “automatic drive” function, using some Track Contacts, a single channel point decoder and a Feedback module. The logic is:
1. Train leaves A, heading for B in a forwards direction
2. Having cleared the points, Train passes over Track Contact TC1 which triggers:
4. Train then returns to B, passing over TC1 which, quite reasonably, repeats Step 2
5. Train then returns to C as in Step 3 and spends the rest of its days going backwards and forwards between B and C!!!
So after much doodling, cursing, etc. I think I’ve found a solution that will work and I’m looking for some of you experts out there to either say “yes” or “nope, back to the drawing board”.
The solution involves an additional track contact – TC3 – and a supplementary switch attached to the points motor that switches power between TC1 and TC3 depending on which direction the points are set.
The proposed process now goes like this:
1. Train leaves A heading for B in forwards direction; as points are set for A direction, TC1 is powered and TC3 is “dead”.
2. Train passes over TC1 which triggers the actions above and over TC3 which, being "dead", triggers nothing; also, when setting the points for C, power is cut to TC1 and restored to TC3
3. Train heads in reverse for C, passes over TC2 which does the actions above
4. Train heads back to B in a forwards direction, passing over TC1 which is now “dead” so triggers nothing, and then over TC3 which triggers:
As the action of setting the points to A in step 4 also cuts power to TC3 and restores it to TC1, when the train comes back up the cycle can be repeated.
Apologies for the length of the post – hopefully it’s clear what I’ve come up with. Any comments on whether this solution will work and/or ways it might be optimised would be appreciated.
Thanks in advance.
As my layout is all Massoth DCC, I planned to operate the rack railway with the Massoth Navi “automatic drive” function, using some Track Contacts, a single channel point decoder and a Feedback module. The logic is:
- Train leaves A heading for B
- Train stops after clearing points, points are set for C, train reverses direction and heads to C
- Trains stops at C, waits for a while, then heads back to B
- Trains stops after clearing points, points are set for A, train reverses direction and heads back to A
1. Train leaves A, heading for B in a forwards direction
2. Having cleared the points, Train passes over Track Contact TC1 which triggers:
- Points being set correctly for train to proceed to C
- A “proceed in reverse” command after a 10 second delay
4. Train then returns to B, passing over TC1 which, quite reasonably, repeats Step 2
5. Train then returns to C as in Step 3 and spends the rest of its days going backwards and forwards between B and C!!!
So after much doodling, cursing, etc. I think I’ve found a solution that will work and I’m looking for some of you experts out there to either say “yes” or “nope, back to the drawing board”.
The solution involves an additional track contact – TC3 – and a supplementary switch attached to the points motor that switches power between TC1 and TC3 depending on which direction the points are set.
The proposed process now goes like this:
1. Train leaves A heading for B in forwards direction; as points are set for A direction, TC1 is powered and TC3 is “dead”.
2. Train passes over TC1 which triggers the actions above and over TC3 which, being "dead", triggers nothing; also, when setting the points for C, power is cut to TC1 and restored to TC3
3. Train heads in reverse for C, passes over TC2 which does the actions above
4. Train heads back to B in a forwards direction, passing over TC1 which is now “dead” so triggers nothing, and then over TC3 which triggers:
- Points being set for train to return to A
- A “proceed in reverse” command after a 10 second delay
As the action of setting the points to A in step 4 also cuts power to TC3 and restores it to TC1, when the train comes back up the cycle can be repeated.
Apologies for the length of the post – hopefully it’s clear what I’ve come up with. Any comments on whether this solution will work and/or ways it might be optimised would be appreciated.
Thanks in advance.