Skip to main content

Just received the SC2 and decided to test all functions using Legacy and TMCC.  The Cab2 communicates with the SC2 when throwing switches.  However, when building a route, the Cab2 will not send a signal to the SC2 when hitting the set button (no red light).  I decided to use my Cab 1 to build a route and it worked. I can "fire" a route with the Cab2 (and Cab1) but not build a route with the Cab2. 

 

Any idea what the problem may be?

 

Thanks

Original Post

Replies sorted oldest to newest

This behavior is as expected.  The CAB-2 does not build routes as a CAB-1 did.  The CAB-2 stores a list of switches in a route in the Legacy base; and fires that  route by sending (switch) commands directly to each switch.

 

However Cab-2 does send a route fire command in addition to the individual switch commands, so if a route exists (by using a Cab1) it will still fire.

 

The difference as Jon and Dale are saying is the TMCC has the routes stored in the SC2 and Legacy has the routes stored in the command base itself as a list of INDIVIDUAL SWITCH commands and to maintain compatibility it sends the appropriate route command out first. The caveat is the Legacy remote can execute both TMCC routes and Legacy routes but the cab1 can only execute TMCC routes.

Ron

 

So Cab 2 will store routes in the Legacy base.  Therefore when building a route with the Cab2, the SC2 will not receive the rte data and hence no red led signal.   I should then be able to call up the route number, hit the "fire" key and the applicable switches should fire.  Is this correct: Build a route with the Cab2, route data stored in the base and then "fire" the routes?

Will try this again.

 

Really appreciate all your comments and help

Thanks

Post
×
×
×
×
Link copied to your clipboard.
×
×