LCS app

Don,

I think that the main benefit is indeed the graphical representation of the layout (or just a portion of it). I'm guessing that we'll soon see command equipped uncoupler and operating sections of track, much like the command switches that will allow "plug and play" yards and sidings. Activating these items via the iPad during switching moves would be much easier than the Legacy remote.

I'm also guessing that we will eventually see a more expanded role from the sensor tracks when combined with action recordings.

You can have command controlled coupling sections right now, just connect them through something like the SC-2 or ASC.

i.e when the GS2 hits the infrared sensor for the 2nd time then execute a prerecorded command sequence.

They were demoing something like this at the open house.  I'm not sure that the sequence isn't set up in the CAB-2 and the sensor just provides the "trip wire" to fire off the sequence.

The program allows you to build a portable control panel that you can take with you as you move around the layout or one that you don't have to actually physically build and wire if you don't move around the layout.

We plan on covering "This and a whole lot more" at the Legacy Users Group Breakfast.

The sensor track is directional dependent.  Meaning the action will be different when the train goes left to right than right to left.  This was explained last spring so there is some great potential there.

I am working at getting perhaps a small demo for the Legacy Breakfast that folks can see close up and first hand. 

I do believe the commands are part of the track that are sent to the base for "transmit" to the engine.

Actually train control was never a primary goal of the LCS app, it's intended to be an electronic control panel. It does have some basic TMCC functions, but it was never intended to replace the CAB2 the way the MTH app is trying to mimic the DCS controller. It is intended primarily for engine management and track control and does allow you to do a few things around the layout from it, but you will still want/need a CAB2 to get the most out of your engines.

We'll I hope everyone can see the potential of incorporating this type of functionality. What we need is the ability to create multiple legacy recordings and a way to trigger them automatically.  You can do this with an ARC, but it is limited to TMCC commands. The engine dependent infrared sensor and the ability to make 20 or 30 recordings would take us to a whole new level of train control. Even just an ARC that supports Legacy commands would go a long way.

Please bring this up at the breakfast. Unfortunately, I will be away and won't be able to make it to York in October.

The one question I hope is answered is whether the sensor track can be used without the LCS application and iPad.  I'd like to use it with the Legacy system, but I sense that it's only going to be useful with the LCS.

I sense I'd like more details.

I sense a gunrunner sighting Friday morning at York. 

That's a very good question- and what about the LCS SWC2 and LCS ACC2. Will they work via the wifi, legacy signal or base cable?  Will they be addressable through the CAB2? Just what exactly is an LCS SER2?  Seems to me they are trying to add another layer with LCS but it doesn't seem to be adding much in the way of functionality.  It would be nice if someone could provide a roadmap for where they are going with this. At this point I just view it as a novelty item that doesn't add much to the layout. Rather than the iPad app a Legacy controller with a better screen that could do the same would of been a better way to go in my mind. 

Wish I could make the York breakfast.

I'm planning on it, I'll have to eat breakfast somewhere.

Marty,

"This and a whole lot more"

My words, exactly!  

Barry you need to register that as a trademark

Previous posts from Lionel have stated that the LCS App is only a part of the LCS system. The power supply unit connects to the Legacy base, and drives the new devices via the LCS bus. This indicates that devices added to the bus will be controllable from the CAB-2, and may also be controllable from the LCS app if you have a Wi-Fi module on the bus.

Chris,

Barry you need to register that as a trademark

Somehow, I don't think that would work. Regardless, I don't mind lending the words to Marty. Maybe I'll charge him a beer at Friday's.  

Well, I'd like hard facts, I'd hate to spend a bunch of money and find out the indications were wrong.   I think that will be a worthwhile question at the LUG Breakfast.  Sounds like Marty already has it on his plate anyway.

I think we'll get the answers you are looking for. 

Beer for Barry...this and a whole lot more at Thursday at Fridays!

Marty,

Beer for Barry...this and a whole lot more at Thursday at Fridays!

LOL!

Chuck and are having a pretty detailed conversation about the recording features of SensorTrack in this thread:

https://ogrforum.com/t...50#21984675479246850

Also, SensorTrack (and the other LCS modules) do not *require* LCS App/LCS WiFi. There are features and functions unique to the LCS App/LCS WiFi. But you can build an LCS system without it.

I'm going to paraphrase Nichole's recent post and summarize thusly: Devices added to the LCS bus will be controllable from the CAB-1L and CAB-2, and are also controllable from the LCS app if you have an LCS Wi-Fi module on the bus.