Track Plan!

At least 20 versions later, and countless sub-versions, I think I am homing in on a track plan.  Below is what it looks like as of now.  Some industrial areas are still pending detailed design.  But basic arrangement is there.  Some key features:

  • Think of it as an expanded version of previous.  Not a lot of “new” stuff going on – well except a new yard; just ballooning out the tight area… into an area twice as big!  All in, layout is right around 750 sq ft, including old and new space.
  • Staging yard went from dead end to run through.  This will be very nice when restaging the layout for ops.  About 30’ long on each track should easily allow 2 trains per track.  Total of 9 tracks.  Plan is for 8 to be used for ops, and one to be kept open for continuous run.  Elevation is at 35" at the lowest end and 37" at the other.
  • Main deck is at 47”, same as Valley Gate.  Valley Gate becomes an industrial yard, handling “shorts” for Warm Springs, etc.  The new yard will handle interchange with SP, ATSF, RI, and of course, GNW through trains.  Transfers will move local traffic between the new (as yet unnamed) yard and Valley Gate.
  • Large refinery will be along one wall.  Note that individual products will be identified on the loading tracks.  Might even add a pet-coke track.  It’ll be a very busy operation.  Ignore the circles adjacent to it - I had some ideas and forgot to delete them.
  • Mainline will go down to staging via a 3 turn helix.  A separate path UP from the helix will lead to a future industrial area.
  • Where the old dispatcher’s office area was will be another industrial area with street running.  Sneaking off to the back of that area into the new space will be a small staging yard for a RML/PR&C connection, if we can gain trackage rights.
  • Connection from the old layout to Warm Springs will be similar to previous, except now running along the entire perimeter of the new room.  Onava was moved in its entirety.  It will also have the connection to Black Water Falls and Cerro Vista along it.  With the added space, I can include a 2-track staging yard for the ATSF coming from, well, Santa Fe, NM.  The Santa Fe branch of the Santa Fe now has a connection – at least in my world!  Most of this trackage will be at 60"
  • On the other end, since Mesa City is no more, the upper level is accessed from what was the track leading up to Black Water Falls.  Will have some adjusting to do there, but it should work.  The old track to the wye at Mesa City will now go to a new industrial area where the dispatchers desk was.  This is likely to be a cement plant.    I will put in some kind of a wye there again, simply because we need a way to turn engines.

Will let you know when the GNW starts running trains again….lot's of work ahead.... looks like it’ll be a while…

Happy rails,

Detlef





Comments

Post a Comment

Popular posts from this blog

Configuring Push-buttons for Turnout Control in LCC (with BONUS section on Adapting JMRI for Feedback)

Image
So ALL the efforts, costs, brain damage and such to get LCC integrated into the layout is paying off in this one new step.  Let me explain. With LCC, each node is essentially its very own stand-alone microprocessor, capable of processing commands INDEPENDENTLY of a central PC or other server.  It just is connected to at the CAN bus, either looking for commands to respond (consumer) to or to issue them (producer).  SO... this addresses one of the goals of integrating LCC into my layout.  Sometimes I like to come down into the layout room and just run trains.  I don't have others with me, and for me, its a great way to unwind.  When I do that, I don't want to have to futz with turning on a PC and getting it going.  Ya, I know, some say it is not that big of a deal.  But if I am only going to be there for 5 or 15 minutes, seems like a hassle to mess with that.  I just want to through the power switch on, have the layout come to life, and run some trains.  Other times, I enjoy ho
Read more

Let’s Configure a Node – The Beauty of LCC (With a bonus section on connecting LCC to PanelPro)

Image
Recall one of the drivers for trying out LCC was to avoid writing detailed code.   Yes, I ~can~ write code.   But it is not my interest or hobby.   As such, anything that can help me translate what is in my head to implementation on a chip somewhere with as little brain damage as possible is quite welcome in my book.   Additionally I did not want the brains of the layout to live in a PC.   There are days when I just want to come down to the basement, flip on the power switch, and run trains.   And… if I am going to go through the trouble of having signals, I want them to come up and operating properly immediately.   Yea, I know I can set up a PC to boot up, execute the right programs and get running on its own.   Sorta.   It’s just one more piece of equipment and step I just don’t care to deal with.        Anyway…. So a big part of my hesitation of leaping into LCC was the angst associated with programming one of these nodes.   I do not have any model rail friends nearb
Read more

LCC and Wiring Continues

Image
Slower than desired, but better to do it right now than try to fiddle it in later.... In my last staging yard, I never did install feeders.  Instead I just counted on the continuity of the turnouts to carry power to each of the 16 staging tracks.  Bad idea.  ~Most~ stayed powered up over the 10 or so years it operated.  ~Some~ randomly dropped out... necessitating fishing and soldering wires onto tracks with 7" spacing between decks.  Not uber-fun at all. SO... with GNW Phase 3, I promised myself ALL track would have feeders every 6' (one feeder per 2 sticks of flex), plus additional feeders in any other complex areas such as yard throats.  This would also allow me to have every other stick of flex not have to be soldered at the track jointers, allowing for expansion and contraction of the benchwork.  BUT... this comes at a cost.  Instead of 16 single ended tracks, I elected to have a 9-track staging yard, each track capable of holding 3 trains.  (WHY I ever went to 9 tr
Read more