@Tracker John posted:I just finished a "game" session on my "Time Waster" switching layout. 5 switches and 9 sensor tracks in a 75" module. The end goal of building this layout is using LCS to provide automated shunting of cars from the starting positions to end positions with the classic Time Saver layout's restrictions on siding lengths. A dice roll is a good way to order the cars on the main line with another roll to determine destinations. There are practical problems to automation.
LCS signals the passing of locomotive or the (rare) sensor car. The presence of, and number, of cars coupled to the front and rear of the loco is unknown so the controlling software has to maintain the state of trains on the layout. Lionel needs to provide additional sensor car and train detection options. How about a kit to retrofit cabeese or other cars in our rosters to add input to sensor tracks? I'm sure Ryan can comment on how simple this can be if the LCRU receiver and logic in the sensor car is replaced with a simpler configuration mechanism.
The 1 to 98 address space of TMCC1 and TMCC protocols can quickly fill up with engine sensor IDs, but TMCC 0xFE and TMCC2 0XF8, 0xF9, and 0xFB commands can be extended to support a multitude of sensors (what was planned for the 0xFA address space?).
How about a "Train on Track" detection using insulated rails that feeds into a STM2 clone that transmits a "train entered" or "train exited" for a number of attached detection tracks and can be queried by software to learn the state of the detection track. (An insulated rail detection track that feeds a DC polarity signal (occupied | empty) to the STM2 is very feasible - I leave that board design to the H/W gurus).
With a shunting layout, command latency is an issue - the sidings are not long enough to allow slack in stopping the switching engine before cars are pushed off the end. In particular, Lionel's LCS App's suppressing control input for 3 seconds while it displays sensor track information is a big design miss. Wrecks await. I'm hoping that a Base3-related update to the App will fix this. The latency issue is a problem with all automation software as our track plans are compressed representation of a prototype and leave little slack for managing train speeds. Better detection of train position is essential.
Don't get me started on recalcitrant coupler opening and closing. Grrrr.
Automation with existing LCS products is going to be a challenge. Lionel has opportunities here.
First of all, that is a really cool thought, to use the classic timesaver layout as an LCS based automation platform/demo.
Maybe we actually start a side thread on that too, The LCS Timesavers Layout. I want to build one already. Plus, it can be a fun way to make a standardized layout for my game system too. I can implement waiting passengers or freight on that fixed size and pre-determined layout. It can serve as an automatic scoreboard for your progress on the timesavers puzzle. The Doodlebug (for both cargo and passengers) I just picked up would probably be pretty good for this. Along with 1 M7 car, and maybe a NW2 switcher and or 0-6-0 Docksider (best bargain pint size fun by the way).
As for replacing the sensor car, you know I already have most of that covered, right? A postage stamp sized board is all it takes. And I actually just had the idea now. Since my replacement sensor car transmitter board doesn't have the legacy signal receiver. I could just program it using a PDI cable connection and the CAB2!! Add a little PDI port on the board, plug it into LCS with a spare PDI cable to program it and replace it back on the track when done.
I will have to do some digging on those extended commands to see if they can help.
I could certainly look into adding support for the STM2 data for a challenge mode version of the game I'd say. Certainly would be good to generate automatic and random movement orders based on actual rolling stock locations. A custom module wouldn't be too bad. I could call it the LCS BDM Block Detection Module. For using the STM2 I could also create a board that converts isolated rail grounds to positive and negative DC, Probably can pull it off with a negative voltage switching transistor, a current limiting resistor and a pull-up resistor.
The base 3 App is great. The basically it's all cab2 functionality in an app derived from the LionCheif app. Though as of right now, I don't think it does much to replace the LCS App yet. No map view as of the last time I saw it at the Springfield Train Show.
