Sensor Tracks hitting the Streets.

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.

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

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.

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. 

Sensor installation in atlas track. just need to do a little more clean up.

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!

I think at some point in the future you might see a sensor equipped boxcar or the like, but I don't see retrofits for locomotives any time soon.  That would be a massive undertaking to cover even a majority of all the different models that exist.

Having some sort of simple programming option for the boxcar would be cool, then it really could be re-tasked for many different consists.

Why? 

I'm with Nicole, why?

The sensor boxcar would know it was "associated" with the engine in question.  When it was sensed, it would talk through the sensor track to the command base, the command base sends out the command for the engine to do the functions, just as it always does.

Well 2 way in such it reads the info and then transmits an action to the Legacy base via the PID cable, which then transmits it as a signal to an engine.

Marty,

I should have been more clear.  2 way communication from the sensor track device when looking at the module design.

Jim

Gotcha. Nothing that I know of but of course Jon would have the definitive answer.  

I "believe" that the IR transmitter on the locomotive is only one-way, it sends the data out.  It receives any data to act on the information through the normal Legacy track signal.

Like Marty says, Jon Z. is the guy to answer this question with 100% accuracy.

For Jon &/or Rudy, is there a chance that in a new version of Legacy that changes could be made to software so activation of the program and record buttons on the sensor track could be activated from the cab2.

Using action codes and starting recordings means you must actually push  the program and record buttons on the sensor track. Another option is to extend those buttons through a modification of the sensor track. If a software change or upgrade to the software is possible, I would think that would be the way to go.

reading this over and re-reading the catalog I was giving Lionel too much credit. The track sensor is merely a remote-track CAB 2 controller so it  is wired to and not wireless to the command unit that then re-sends a signal to the engine, as if I was pressing the CAB 2 buttons. So each sensor track needs to be wired to the command unit. 

Oh good more wires to run! I think I'll pass until the wireless track sensor comes out.

Well folks I've been playing with this for over a week.  I've had a playback of a recording I did running for the last few evenings.  I have to say I am impressed with the accuracy.  While I don't have grades and my track is a simple oval of 8x18, I have been triggering events, stops, and accessories via the playback with a great deal of accuracy based on the position of the train on the layout.  I even have an TMCC engine on a siding blow it's horn while the Legacy engine passes.

Love the fuel gauges too!  I can usually get the water to drop with about 4 laps and heavy train brake.  Coal usually after 8.  It is interesting seeing how different setting with load and speed effect the fuel and water consumption.  This will be cool on the Big Boy!

Hmmm, how about extending the LEDs also, since if the SensorTrack was in a tunnel or not in a position to be seen clearly?

Hmmm, nope I missed it!

Good Catch Marty!

Not sure if you saw my other post regarding this thread about members sharing what types of programming functions they are incorporating along with a script so that other laymen might be able to do it right!

Thanks,

Dennis

Marty,

Not all of us know the proper whistle signals for crossings, bell and or whistle when departing from a stop or arriving at a station, the speeds that are correct when departing the station as an example for some of the items.

I will try an do an example:

Train is approaching a crossing, the two long, one short and one long whistle blasts, how much before the crossing will depend on what speed the train is going but you get the idea.

Basically, the steps when you are doing the recordings as a written script, so that anyone just getting started would be able to do it correctly.

I know that we all should know this, and could probably do research on these but figured if we could get samples of the different scripts (sequences) that the members use when programming the CAB2 or the Sensor Track, etc, it might make things easier.

I know some things, but have been winging it on others which would allow others to either think I was doing it correctly and giving them an incorrect experience or opening myself up to someone not being nice and saying he doesn't know what he is doing to others.

Thanks,

Dennis