Skip to main content

I hope many people are as happy to see the new IRV2 sensor track controllers.  If you add it up Lionel just reduced the cost of a sensor point to $40.  That is less than 1/2 the sensor track cost.  I have two suggestions that would really amp up the usefulness of this new module. 

First Suggestion: Make it work with curved track.

1V1A2679

The sensor module is fairly small, about 0.5 by 4 inches from the looks of the picture.  All of the active parts seem to be in the center 1/4 inch.

1V1A2678

size of module in an O-27 track

1V1A2672

by trimming off the corners on one side and taking a bite out of the middle on the other...

1V1A2673

...one could make a universal module that would work not only on straights...

1V1A2674

... but a variety of curves as well.  Here it is on an O-27 section

1V1A2675

Here on an Atlas 0-36

 

1V1A2676

and here on an Atlas O-72

blobid0

I have several Sensor Tracks mounted under curved sections with a tie cut out and they work fine.  I suppose that with the higher placement of the module with this proposed setup that the sensor might have to be placed on the inside portion of the curve as that is where the IR module on the engine would move as it goes around the curve.

Second Suggestion:  Be able to store and activate multiple programs for multiple engines in both directions.  This really only requires a minor change to the software and a little more memory. 

Software change: Today when you put the sensor module in program mode It takes whatever is the next engine to cross the track, starts a program for it, and erases any program that is currently there.  If instead you just start a new program for that engine or replace only the program for that same engine then you could have several.  There would have to be some limit and if you tried to put too many in, the track would need to flash an error code when it was full.  To delete one of the existing programs to make room for others simply run the existing engine over the track and then immediately press program again to take it out of program mode before any commands are stored for that engine.

I love my sensor tracks now but since I always run trains in the same direction it is frustrating that I can never use half the programs I might have, due to never running the engine over in the reverse direction.

Attachments

Images (10)
  • 1V1A2671
  • blobid0
  • 1V1A2672
  • 1V1A2673
  • 1V1A2674
  • 1V1A2675
  • 1V1A2676
  • 1V1A2677
  • 1V1A2678
  • 1V1A2679
Original Post

Replies sorted oldest to newest

superwarp1 posted:

It's a ask and you shale receive.  I'm glad Lionel came up with these.  No need to chop up a sensor track.   I'm also interested in the CSM2 for all my DZ-2500 switches.

 

I hope to get with Dave before York and see if we can get some more information on these to share at the Legacy Users Group meeting.  I agree a little long over due but worth the wait.  Hopefully these can be accessed via the High Rail App or eTrain like the current sensor tracks.

 

I hope to get with Dave before York and see if we can get some more information on these to share at the Legacy Users Group meeting.  I agree a little long over due but worth the wait.  Hopefully these can be accessed via the High Rail App or eTrain like the current sensor tracks.

MartyE... the plan is to have High Rail support the new hardware. High Rail's SensorTrack recording feature is pretty nice. :-)

 

MartyE posted:

I hope to get with Dave before York and see if we can get some more information on these to share at the Legacy Users Group meeting.  I agree a little long over due but worth the wait.  Hopefully these can be accessed via the High Rail App or eTrain like the current sensor tracks.

Hopefully, they can also be accessed via the CAB-2 and the iPad app.


 

 

superwarp1 posted:

It's a ask and you shale receive.  I'm glad Lionel came up with these.  No need to chop up a sensor track.   I'm also interested in the CSM2 for all my DZ-2500 switches.

Capture

I've been waiting for this. It's the way Lionel needed to go with the SensorTrack concept to make it more feasible to integrate into a layout. Kudos to Jon Z. and Dave and whoever else worked on this.

When I saw these I started thinking about how many I'd need so that my trains would do grade crossings on their own.  And the price point is low enough I might actually get them just for that.

And I just had another thought, if they work like I think I remember the sensor track working (I only played with mine once when I got the VL BB.), you could use them to enforce yard limits, or keep locomotives from running off the end of spurs.  Put one near the end of the spur and when the locomotive goes over, it stops.  At the entrance of a yard it can drop the locomotive speed to a crawl.

I may end up picking at least one of these up to use on my layout. At least for one of my four planned grade crossings. I would love to see Lionel make and Android App for their LCS, I know they opened it up so that partners could write the apps that interface with the LCS system. 

I would also like an Android App that does a least the basic functions.

I notice in the catalog description that the IRV2 comes with two cables to connect the sensors to the blue module (controller), and additional sensors also come with a cable.

I assume the cables are PDI cables, would that be right? If so, would Dave Olson mind chiming in and letting us know how long the included cables will be.

Cheers!

Keith

trnluvr posted:

Dave,I watched the show yesterday and you stated the cable length on these would 2 to 3 feet long,this is from the sensor to the module? If that's the case you really will not be able to spread these out very far on a layout. Could you explain this a little more,please.

Doug

Well if you have a double main line and wanted these for a crossing grade, the wire length should cover all 4 tracks 2 in each direction.

Yes, the maximum length from the sensor sled to the LCS blue box is 3 feet. We found this in testing. When the cables are longer, the data signal becomes unreliable and the info is lost I.E. the sensor track won't work. This is why we're choosing to only include 2 sensors with the module instead of 4. The add-on sensor is available for instances like Marty described above where you can use more than 2 in a relatively small area.

Dave Olson posted:

Yes, the maximum length from the sensor sled to the LCS blue box is 3 feet. We found this in testing. When the cables are longer, the data signal becomes unreliable and the info is lost I.E. the sensor track won't work. This is why we're choosing to only include 2 sensors with the module instead of 4. The add-on sensor is available for instances like Marty described above where you can use more than 2 in a relatively small area.

Now that we know that the sensors will need to be within 3 feet of the blue box...

  • Will there be any limit to how far the blue box can be from the next blue box in the LCS bus?
  • With the sensors operating through the blue box, will we be able to program the sensors directly from the CAB-2 or the iPad app?

Cheers!

Keith

Keith L posted:
  •  be any limit to how far the blue box can be from the next blue box in the LCS bus? No
  • With the sensors operating through the blue box, will we be able to program the sensors directly from the CAB-2 or the iPad app? Same operation as current sensor track.

 

Severn posted:

One imagines a repeater is possible... to address the length issue. I'll mention this to the engineers working on it.

MartyE posted:

It would be interesting if any other "satellite" items based on the sensor platform could be made to plug into the box. Such as?

 

Dave Olson posted:

MartyE posted:

It would be interesting if any other "satellite" items based on the sensor platform could be made to plug into the box. Such as?

 

IDK yet but I'm thinking.  LOL!  Seems like there is potential to utilize the platform beyond what the engine sensor can do.  Let me ponder this.  Could a different detection type device be utilized?  Like an RF ID?

Could a device that includes multiple user recordings be added so that a larger and longer selection of recordings be accessed?  Sort of a LCS storage device?

Last edited by MartyE
@Keith L posted:

I notice in the catalog description that the IRV2 comes with two cables to connect the sensors to the blue module (controller), and additional sensors also come with a cable.

I assume the cables are PDI cables, would that be right? If so, would Dave Olson mind chiming in and letting us know how long the included cables will be.

Cheers!

Keith

Sadly, the "IRV2 -> Sensor sled" cable is NOT the standard 4 pin cable.  Its a 5 pin and only available from Lionel in one length, 3 ft. 

@Dave Olson posted:

Yes, the maximum length from the sensor sled to the LCS blue box is 3 feet. We found this in testing. When the cables are longer, the data signal becomes unreliable and the info is lost I.E. the sensor track won't work. This is why we're choosing to only include 2 sensors with the module instead of 4. The add-on sensor is available for instances like Marty described above where you can use more than 2 in a relatively small area.

Dave, I just saw your statement about length limitations.  I actually have spliced some long runs together on 2 of the 4 sleds coming off my IRV2 with no problem.  The lengths were probably 10ft or so.  No problems to report.  Is this a function of the 12VDC/1A power supply?  Curious as to the root problem. 

Add Reply

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