Graham,

I will focus my reply on this part of your dilemma, (The linking to have a sensor trigger the route is an extension of the base function - and not worth getting into until the route is correctly defined to your satisfaction).

At this point I take the term
-> "get a couple of points to connect" to mean you saw them appear in the route builder strip on the right as you were configuring/editing a route
-> "unable to retrieve ...." may refer to the (short sighted) design of the CS2s memory function panels which have a limitation, in that you will only be able to "see" the Route Builder Strip again if you return to configuration/edit mode for the route being considered

The user manual does contain the essential steps you need, however they have inserted a number of distracting "options" and notes that are not needed to get things going.

You indicate that you have navigated as far as the route Edit screen before
-> Memory Tab (to access the memory panels)
-> Service Button (to enter configuration mode - note the screen background goes blue)
-> Select "A1" (or another route ID of your choice)

At this point ..
-> the RouteID icon will acquire a blue border to identify which route is being configured
-> (image below) Advance details will be displayed at the bottom of the screen (Like Route name and the s88 sensor definition stuff)
-> (image below) the "Route Builder Strip" will appear on the right.


The concept is to add accessories(identifying their desired aspect) to the "Route Builder Strip".
(Once the route is built, either the "save" or "save_and_exit" buttons must be selected, following this it is also desirable to "shutdown" the CS2 correctly - don't just turn off the power switch)

To add accessories to the "route builder strip" one must change to either the Keyboard tab or the layout tab( assuming accessories have been added there) In doing so you will notice the Memory Tab remains BLUE indicating you are still in configuration/edit mode. From the keyboard panel you can select the accessory items and will observe them appear in the "Route Builder Strip". When you have built the route be sure to save it.

Edited by user 16 May 2013 10:26:52(UTC)  | Reason: Not specified

Hi Graham, your phrasing is giving me cause to wonder if there is a misunderstanding about what is the route. Apologies if I am being a bit basic.

The "A line" (not the "A1 line") is just a reference on the screen and contains 8 routes (by default named A1,A2...A8 - although those names can be changed). The line itself is NOT a route containing up to 8 objects (turnout/signal/function). There is no link/chaining between routes (on the same line or else where) unless you specifically create it!

While it is valid to have only one item (Turnout/Signal/Function) within each route, as you suggest you have done with the "6 consecutive" buttons, it is more common (dare I say expected) that all the items you want to daisy chain are WITHIN the route (e.g. you could put the 6 points of a fiddle yard in one route so that pressing one button will cause 6 devices to fire in sequence to the desired state)

Please confirm that you are intending to set up 6 routes with 1 switch/point in each and are not wanting a single route containing 6 switches/points


Absolutely not - Personally I recommend steering clear of this option until it is enhanced to be practical. FYI refer to Review of Memory Conditioning Feature



Again, as above, each button represents a route the ICON has the following meaning
-> This is an empty undefined route container , i.e. contains no turnout/signal/function objects
-> This route contains objects but at least one is not in the desired state
-> This route contains objects and ALL of them are in the desired state
-> This route contains objects and has been activated and is in the process of setting all object to the desired state. This is transient and will last only long enough for the CS2 to send commands to each of the objects in the route - on completion the yellow dot will change to green.

For example if a route contained only one item (Signal #3) with a desired state of GO(Green) and the signal was in that state, then the icon would have a green dot. As it would after you pressed the button to activate the route and set it to that state. Now if , say on the keyboard, you changed the state of Signal #3 to Stop(Red) the route would be compromised and the icon for the route would have a split "S"


Note: A point worth making that relates to your observation is that once a route has gone green and set the objects to the desired state - pressing it again will do NOTHING- i.e. if you manually change a turnout to the "wrong" state. The Route has no knowledge of this and thinks that everything is where it should be and does NOT fire again. Only when "it thinks" the Route is split will it react to an activation.

Warning: And as a sanity check, be aware that there are still bugs in the Route edit function (@3.0.1) I have found these "appear" after a number of edit where you are building up a route but get something wrong (e.g. red instead of green) and do a number of re-edits on the same item. If you suspect this I can only suggest noting down the route objects, delete them all back an empty route (and save that) then build the route again with as few re-edits as possible.