Tehachapi, BC

[Santa Fe Guy]

Rod, if you have block detection enabled, it's super simple to implement, but it's only worth it if it advances your ops concept. 

Since trying this last night, my mind has been racing with the possibilities it opens up: context-sensitive control panels, surround sound, dispatching tools.  I'm giddy.   

Hi Gary. Thanks, all my SFRSD is blocked with 4 BDL's and signalled using 4 SE8C's linked to two computer screens set up in the old AT&SF way. If you notice the post from Brendan he is my young computer guru and has done all the computer work for me. I'm sure he (we) will get it going before the next session, I just didn't know it existed. If interested see my blog, the address is below it might show you the stuff we have done.
Rod.

[John]

since you are experimenting .. I suggest you also look at CATS .. it runs on top of JMRI, and simplifies the coding for CTC operations .. it also does DTC, ABS, and APB-2/3 .. I've set the M&O up with it ..

http://cats4ctc.wikidot.com/

[GaryHinshaw]

It's definitely on the to-do list.  My initial foray into Layout Editor was so I could generate the virtual control panels.  Then I just kept exploring.  I need to keep working on the hardware too. 

[sp org div]

since you are experimenting .. I suggest you also look at CATS .. it runs on top of JMRI, and simplifies the coding for CTC operations .. it also does DTC, ABS, and APB-2/3 ...

Seconded, (nice layout Mr Parker).
...and also tracks train ID across the DS panel (with much additional fluff....).
Thanks Rodney!

Jeff

[Smike]

Sure, hopefully this is what you are looking for.  Here is a snippet from my Layout Editor panel (which can also serve as the dispatcher's panel):

Excellent, thank you for all of the info you provide!

[Santa Fe Guy]

since you are experimenting .. I suggest you also look at CATS .. it runs on top of JMRI, and simplifies the coding for CTC operations .. it also does DTC, ABS, and APB-2/3 .. I've set the M&O up with it ..
Nice panel John
Rod.

[GaryHinshaw]

Is that a +1 Rod?  Like I said, I will definitely be investigating...

[Santa Fe Guy]

Yep, screwed that reply up. LOL.
Rod.

[GaryHinshaw]

Time for another decidedly un-photogenic update.   We had another test session this weekend (officially session #5 on Feb 20) to try out the new command and control features.  Before describing the session I'll review a few of the projects that were completed in preparation for it.  Hosting a session is a great way to force progress!

The main task was to complete the installation of block detection and DCC turnout control on the main line.  That is done now, with the exception of the last two blocks at the south end of the line, which will require a tricky auxiliary bus wire to be installed.    Here is one component of the system:



(I told you the update was un-photogenic.)  On the right is a RR-CirKits Watchman boards, which detects 8 blocks; on the left is a Motorman board which drives 8 turnouts.  The board on the far left is a "fan-out" board that basically converts ribbon cable to separate wires - handy for remote installations.  There are now 4 of each type of board scattered around the layout.  The blank slot in the track above will eventually hold a Signalman board for driving signals.

Elsewhere you'll find this motley collection of gizmos:



Top left is the UR92 (Digitrax radio receiver); next is my WiFi router for serving WiThrottle and web pages; on the bottom is the adapter that connects Loconet to the serial bus used by the RR-Cirit boards.  On the right is an unruly collection of wall warts to power them all.  Will there ever be a standard form factor for wall warts?   

Here's one from the tasks-I-was-not-looking-forward-to file: installing Tortoises at the interlocking in the Vortex where the line converges from 3 tracks to 2 partway up the helix (for clearance reasons).  There is one turnout in the set that was in the middle track of the 3-track section and I foolishly did not plan ahead for attaching a linkage to its points.  With a session approaching, I could not leave this job undone, so the time had come!  Here is an ugly close-up of the ultimate solution:



I tunnelled a piece of brass tubing under the inner track (wrapped in heat shrink to forestall shorting the inner track) and ran a steel wire through it to the throw-bar.  It now works like a champ, but getting to this point was a bit of a misadventure.  Recall that there is minimal clearance underneath this turnout for a mechanism, and in any case I had not pre-drilled a hole through the roadbed to accommodate any linkage, and I had no way to drill one now given the roadbed above and below this level.      Further, the vertical helix support was blocking in-line access to drill out the tunnel under the inner track.   After trying some awkward drilling, it finally occurred to me that I could simply remove the support without having the helix collapse:



(It bothers me that it took me so long to realize that this was the obvious solution....)  Once the support was removed, it was very simple finish off the installation, which is now fully under DCC control:





Finally on to the session - without photos, alas.  Guests included Railwire members Mark Dance, Tim Horton, and Andrew Hutchinson, and two others, one of whom used to be a dispatcher for BNSF in the Vancouver area.  Most of the session was run with Engine Driver throttles on phones and tablets, and train control was very reliable.  The main reason for using smart throttles was to try out virtual signalling: I was broadcasting the main layout control panel to the web display in the throttle so operators could see signal aspects in the panel (since I don't have hardware signalling installed yet).  The panel they were looking at was the full layout panel from jmri's Layout Editor:



Operators can easily zoom and scroll around this display, but I think we agreed that this was too much information, specifically more than a real crew would have access to. I am now working on a scheme, similar to Bob Bucklew's, to push specific signal aspect panels to each throttle so the operators can just focus on the track ahead.  I have now piqued Steve Todd's interest (he's the Engine Driver maintainer) in coming up with a way to automatically push sub-panels out to specific throttles in a context-sensitive way, based on train location and direction.

What's next for the layout build?  Track-laying is now about 2/3 complete.  The sections circled in blue above are still unbuilt: the lower deck mainline, which comprises a bit under half of the full mainline run, and the Bakersfield yard.  For logistical reasons, the last section to be built will be the Caliente-Bealville segment since it will reside over Bakersfield and/or cross the entrance door.  So I will simultaneously work on Bakersfield and Edison, building towards an eventual Golden Spike somewhere in the Caliente area.

Also, there were two items standing in the way of starting scenery on the upper deck: 1) ballasting the main line, and 2) setting up block detection and turnout control.   Item 2) is now essentially complete on the upper deck and item 1) is complete over a large fraction of the upper deck, so there are really no more excuses to start installing final back-drops and putting landforms in place.   

Long update.  Thanks for looking

[Ed Kapuscinski]

Great stuff Gary (as per usual)!!

I've discovered a sudden interest in DCC components (bet you can't guess why...). I'm glad I'm going to be trying it out on a "simple" scale first.

So, in that vein, can you tell me about the watchman and switchman? They seem like a much more economical approach than a PSX-4, if they do circuit breaking.

[Scottl]

So much gizmo awesomeness 

Glad to hear Engine Driver on tablets went well.  It is probably the best interface I have used to run trains and it will be great for DPU or other complex consisting.

[bdennis]

Gary,
Looking great.
One quick question.. Why run all those wall warts around the place?
Why not just run a 12v 4A DC power bus around the layout and use that to power all the DCC devices.
I used this method on my old layout and had 20+ DCC devices around the layout with no issues.

Note: I use a separate power supply on my DCS100 command station as suggested by Digitrax.
Note: I have 16V 7A DC power supplies from old IBM Laptop docking stations that I use for the DC power bus and then I have a small circuit that has a 1A voltage regulator (with jumpers that adjust the output voltage) on it near groups of devices and that then drops the voltage to the required level. (some need 9v some need 12v etc)

Just a suggestion..

[GaryHinshaw]

So, in that vein, can you tell me about the watchman and switchman? They seem like a much more economical approach than a PSX-4, if they do circuit breaking.

Hi Ed.  The Watchman is for block detection and the Motorman is for turnout control, neither handles circuit breaking.   For that I am using "OnGuard" boards from Tony's, as seen, e.g. here.  These are a bit less expensive than the PSX, but they are plenty capable and you can get straight breakers (OG-CB) or auto reversers (OG-AR).  BTW, I love seeing you tearing it up in the basement again!

Note: I have 16V 7A DC power supplies from old IBM Laptop docking stations that I use for the DC power bus and then I have a small circuit that has a 1A voltage regulator (with jumpers that adjust the output voltage) on it near groups of devices and that then drops the voltage to the required level. (some need 9v some need 12v etc)

A DC bus like this is definitely on the list!  Just haven't had the time yet.  I'd be curious to know more about your step-down circuit because I too have a range of voltage requirements from 5-15 V and I'd prefer not to run separate busses for each.

[Ed Kapuscinski]

Hi Ed.  The Watchman is for block detection and the Motorman is for turnout control, neither handles circuit breaking.   For that I am using "OnGuard" boards from Tony's, as seen, e.g. here.  These are a bit less expensive than the PSX, but they are plenty capable and you can get straight breakers (OG-CB) or auto reversers (OG-AR).  BTW, I love seeing you tearing it up in the basement again!

Ahh, cool. Thanks for the info.

So, why did you choose the OGs instead of PSX's? I'm still learning about this aspect of DCC, so I'm curious.

And thanks. I am too! It's amazing what a boost to the budget and no more commuting will do for one's hobby.

[GaryHinshaw]

So, why did you choose the OGs instead of PSX's? I'm still learning about this aspect of DCC, so I'm curious.

And thanks. I am too! It's amazing what a boost to the budget and no more commuting will do for one's hobby.

Only because they are a bit cheaper and I didn't really need the adjustable features that the PSX have.  For example, you can set the in-rush current threshold in the PSX in the event that you have large-scale locos with on-board sound because their start-up current rush can trip a breaker, but I don't see that as a likely issue with N scale locos.   You certainly can't go wrong with a PSX though.

And yes, time and money are both key requirements when building a layout...