Skip to main content

I would like some feedback on how the sensor track works with multiple engines.

 

Below is a very simplified schematic of my layout, with 4 sensor tracks installed in the locations with the gray dot.  Speed Zone 1 is where my yard and terminals are located, Speed Zone 2 is an urban area, and Speed Zone 3 is open country.  I would like to run an IR equipped Legacy engine around the loop with the engine speed changing each time it goes over a sensor track depending on which speed zone it is entering.  I’m pretty sure this is not a problem with one engine.

 

My question is if I am running two IR equipped engines on the same track (and same direction for you jokers), can the sensor track/LCS be programed to change the speed of both engines so they will stay the same distance apart?  Or will I need two sensor tracks at each location?

 

Thanks. Ron

 

 

Sensor track placement

Attachments

Images (1)
  • Sensor track placement
Original Post

Replies sorted oldest to newest

I'm not sure there is more to add but what I understand a sensor track can trigger a playback for any sensor equipped engine that passes over it or just the engine that made the recording. 

 

So I would surmise that if a sensor track set to playback on any sensor engine that passes over could set the speed of any engine going over it. The only cravat is to make sure momentum and speed entering into the sensor track is the same on both engines. 

 

With the multiple sensor tracks around the layout you should be able to speed up and slow down engines. 

 

Of course since it's not out yet this is based on what we saw at the LUG meeting. 

Marty,

 

Thanks for your thoughts on this.  I concur with you.

 

It doesn't make sense that Lionel would limit the sensor track to one engine at a time, and I can see your point on the engines having to be going the same speed entering into the track.

 

Now I need to see how to make a good transition between my RCS/Gargraves track and the FastTrack piece.

 

Ron

They definitely are not limited unless the recording is made that way. From what I remember from the info sent with the demo track for the Lug meeting there were 3 record modes. 

 

1) A recording made on 1 engine would trigger the playback of that recording for any sensor equipped engine crossing the sensor track. The recording would contain any input from the Cab 2 including accessories and TMCC engine commands. 

 

2) A recording made by an engine would only trigger from the engine that made the recording. The recording could contain all of the above. 

 

3) A recording made by an engine will only trigger with that engine and The recording would only record preselected accessories and such. 

 

So if that's the case #1 should work for you. We only had one to play with so I am looking forward to trying multiple sensor tracks. 

Cappilot, I like the scenario you describe. Marty is correct, a custom recording can playback on all passing compatible locomotives. Also, based on the the simplified layout you've shown above, you could do your scenario with fewer than 4 SensorTracks. I'm working on some demo videos for SensorTrack this week and I'll try and record an example for you.

 

cheers,

rudy

Chris, by default a recording made will apply to all passing engines. You don't need to specify any TMCC IDs. Just set up to record, roll (for example) engine 17 over the track and perform your scenario and end the recording. Then, when engine 17 rolls over the track again, the scenario is repeated. Now roll engine 37 over (again, just an example ID). Engine 37 will perform all the same actions as engine 17 did. So will engine 54 and any other compatible locomotive.

 

To your second question, no. You can do the reverse, though, so that *only* engine 17 causes the scenario to play, but engines 37 and 54 (again using the above example) pass over the track and the scenario is not triggered.

Last edited by Railsounds

How much longer before we can get the components to use on other brands of track?  FasTrack is nice stuff and I have a lot I use on the carpeted floor, but I'd want features like this on a layout which will be with Atlas track.  I like the sound of the solid rail better and have always like the look of Atlas on cork with no ballast.  Comes from my N scale days I suppose.  But FasTrack is hands down the best for the floor.  After a number of years my kids, their friends or cousins, have yet to ruin any of the stuff I leave on the floor.  It gets stepped on, stood on, HotWheels get driven on it, we even vacuum right over it when we do the floor, and have no issues with the track.  But for a permanent layout I like something different.

Originally Posted by RailfanRon:

This is going to be a cool add on to any layout. What bums me out is I would like to see the software for a pc. I don't have an IPad but I do have a win 8 tablet and a few laptops and a desktop or two.

Ron

Ron, as you can see in the video, many of the SensorTrack features do not require an iPad or any other computing device. But to your interest in a Windows PC software prograthat works with SensorTrack: We have made all the protocol information from SensorTrack and the rest of the LCS system available to our LCS Partner developers. If there's a strong enough demand, I'm sure you'll see some computer-based products that interface with SensorTrack in the future. But for now, I think the product has plenty to offer on its own, with or without an iPad.

Originally Posted by cbojanower:

An official no fastrack solution is not in the near future , but with some tools and a bit of work you could do something with he fastrack sensor

But I had thought I read that Lionel was going to develop a setup to use outside of FasTrack.  I'm not looking for an exact Atlas drop in fit, but I'd rather not have to take apart a FasTrack one to do it.

I believe the last York Legacy User's group that it was mentioned that they're discussing it, and it should eventually happen.  However, I believe you can be assured that until they get the LCS system laying flat with Fastrack that they're not going to be rushing into other track types. Note that I don't speak for Lionel, just repeating what I understand from the last I heard on the topic.

 

If you want it now, I think you need to carve up some Fastrack SensorTracks.

 

Originally Posted by Railsounds:

Thanks, Marty. I've been working on some video examples to help explain SensorTrack. We just posted Part 1, you can find it at this link. I am working on a follow-up that will demonstrate the recording features that we've been discussing in this thread. More to come!

 

Cheers,

Rudy

Rudy,

 

Not all of come from a railroad background and well are just getting our feet wet!

 

I was wondering if Lionel or the users could post different scripts that could detail how the tracks recording features can be implemented for realistic usage?

 

Thank you in advance for your consideration.

Add Reply

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