On the topic of the purpose of the SER2 - am I correct in assuming the SER2 will also be necessary if I want to interconnect the Legacy command base with a DCS TIU using the TIU/TMCC-Legacy connector cable?
Got my sensor track installed, works great. I used transition tracks on each end for tuber o gauge. Rudy is there a way to activate the program button from the cab2? I want to install other sensor tracks, but they will be out of reach as I can't walk around my layout?
Got my sensor track installed, works great. I used transition tracks on each end for tuber o gauge. Rudy is there a way to activate the program button from the cab2? I want to install other sensor tracks, but they will be out of reach as I can't walk around my layout?
Sorry Jim, there's no CAB button equivalent for pressing the Program button on SensorTrack. We decided against it, because of the risk of unintended *CAB* button presses changing SensorTrack settings while the operator was doing something unrelated on their layout.
Perhaps a little jack on the track in the future so you could remote the program button. 
Perhaps a little jack on the track in the future so you could remote the program button.
Oh, that's a good idea! I wouldn't be surprised if an enterprising person such as yourself attempted just such a modification. 
I'm probably up to something like that. 
You don't have to run them far, just where you can reach them from the side of the layout. Hopefully, you won't be programming the track all the time.
Do you need the DB9 cable to make the sensor cable work & how long is the cable?
Ken M
Do you need the DB9 cable to make the sensor cable work & how long is the cable?
Ken M
Yes, Ken. Each LCS installation requires one 6-81499 LCS DB-9 Cable with Power Supply. This includes a 10 foot cable. One end goes to your command base, the other end to the first LCS component in your system. The photo below shows one of the blue LCS modules connected (such as LCS WiFi) but it could be a single SensorTrack instead.
When you add a second and subsequent LCS device to your installation, you’ll need additional LCS PDI cables. Each piece of LCS hardware is cabled to the next in a daisy-chain fashion, using these cables, which are available in 1’, 3’, 10’ and 20’ lengths.
For more info: http://www.lionel.com/lcs/LCSp...CScabling/index.html
I sure like the idea of a jack on the sensor track to add a program button in a remote location. I will get another sensor track and see if I can add some wires and a button.
Rudy, you will sell more tracks if the program button could be controlled from the cab2 or add the jack as suggested above.
So how about a simple cable coupler to allow joining two LCS PDI cables? That way I wouldn't have nine feet of a twenty foot cable lying around my layout, when I only need eleven feet from one module to the next.
Sounds like a business opportunity, modify sensor tracks for remote operation.
Sounds like a business opportunity, modify sensor tracks for remote operation.
It looks as though it would be pretty simple to disconnect the small board that holds the buttons and LEDs, and make an extension cable so that this board could be connected some distance from the sensor track.
I'd probably just mount a tiny 1.5mm 2-pin jack on the side of the module and run a cord to a push-button.
Played with my sensor track a bit today.
Its nice how it loads the engine information in on its own, but I'm a little surprised that when you program the ACC # of the track sensor it doesn't update the Legacy remote to say Sensor track! Seems like it would of made sense to do so. LCS components should identify themselves!
UP Genset didn't come up with a name of the engine but did set it as a Legacy Diesel. SP Shark, and SP Berk worked as expected.
Jim
Jim,
The ACC number is used only by the iPad to ID multiple sensor tracks. The Cab-2 does not need this info, and it is possible to reuse the ACC ID that Sensor Track uses if you don't want to reprogram the Sensor Track presets.
Jim
Another bit of info, some of the earlier locos did not transmit the name unless stopped. I think if you stop the Genset over the sensor track it will update the name. LMK if that happens, I don't have a Genset to try it here.
You'd have to be pretty exact to stop it right at the sensor I would expect. When I get a sensor track, I'll try my NS Genset over it.
Unless Lionel both plans to add sensor kits for both existing non-Lionel equipped engines and Lionel non-equipped engines(for minimal control, of course) and additional sensor track kits for non-Lionel track this will go the way of the original wireless Lionel engines in the 50s. Great idea but no compatibility with existing engines and track . . . so very short life.
Thus, if Lionel is betting that we will all shelve our non-equipped engines and re-track our non-sensor trackage they are in a few words "fooling themselves". Because most of us will simply ignore them!
Unless Lionel both plans to add sensor kits for both existing non-Lionel equipped engines and Lionel non-equipped engines(for minimal control, of course) and additional sensor track kits for non-Lionel track this will go the way of the original wireless Lionel engines in the 50s. Great idea but no compatibility with existing engines and track . . . so very short life.
Thus, if Lionel is betting that we will all shelve our non-equipped engines and re-track our non-sensor trackage they are in a few words "fooling themselves". Because most of us will simply ignore them!
Access to this requires an OGR Forum Supporting Membership
