I would go for a BSM2 in a minute. I have two huge loops of track with 5 blocks in each loop.
I would be in for a bsm2 as well.
To be honest I would have thought the new asc2 would have included on off feed back already.
To be honest I would have thought the new asc2 would have included on off feed back already.
I am in the planning/acquisition stage. But looking over at the options as of right now, sensor track is the only way. 10 sensor track will easily eat the budget 
but if I can use one STM2, then it's one device for 16 blocks.
but if I can use one STM2, then it's one device for 16 blocks.
The SensorTrack and STM2 are really two very different products with quite different purposes. Block detection is not a currently envisioned feature of the STM2.
Envisioning it might be a positive.
With the two way communication of the LCS components I was hoping that Lionel would have built feedback into their new products. Then we wouldn't need the extra wiring, like we will for the command switches. I could use an asc3 already I guess.
Block detection could be very useful depending on how it is implemented in the app. I might be very interested. Please update the Lionel LCS app, that's the one I am willing to pay for.
Dan
It used to be "The devil is in the details" now it's "The devil is in the software".
I'm wondering what the circuit is for sensing switch position inside LCS STM2. Do you know?
Thanks
It requires the connection of the yellow wire which shows the switch position as thru when it's +5 vdc and out when it's -5 vdc. But what do you mean by "circuit"? Something more than just that it puts out a different data word depending on whether it sees +5 or -5?
CJACK,
Thanks for the reply. I am asking about the way that the STM2 determines electrically the state of the switch in the case of an all AC track and accessory powered system, including O27 switches.
Where is the +5 VDC or - 5 VDC that you mention?
Every FasTrack switch has a power supply inside to convert AC to DC and circuitry to develop 5 vdc and -5 vdc. The yellow wire lights the green or red LEDs in the manual remote controller. So they are using that signal to send data to the LCS.
Thanks for that information regarding FasTrack. But I still would like how the switch state is detected in the case of, for example, an O27 switch such as 5122 or 1122(E).
Barry835 posted:Thanks for that information regarding FasTrack. But I still would like how the switch state is detected in the case of, for example, an O27 switch such as 5122 or 1122(E).
Here's the manual, it has a description of how to connect each of the kinds of switches. Suffice it to say that connected as required, the STM2 is programmed to recognize the voltage levels in different switches and interpret thru from out. In every case, I think the combination of voltages or lack of a voltage which lights the green or red lamps, or LEDs, in the manual remote controllers is how the STM2 determines position.
CJACK,
Thanks for the info. It is appreciated.
If we want to build a detector from scratch for automatically detecting the state of an O27 switch track, and use only connections to the ground terminal and one of the other three terminals, how would we do it, in a way that would be robust and a simple as possible? This is the question.
Thanks again.
Well, I don't know what the details are for any switch except the FT ones. But, in looking at the connections in the STM2 manual, all the other switches connect their common terminal to the "sense return" on the STM2. And they connect one of the throw terminals to the input for the switch on the STM2. By throw, I mean the THRU or OUT terminal that you use to change the switch direction with the remote manual controller. So I would just do that with same thing the 022 switch...not knowing if it looks like the tubular remote switch or not. But I don't see how it could hurt the STM2. And as they say for one of the examples, Try the other terminal if it displays the wrong direction of the track.
Barry835 posted:CJACK,
Thanks for the info. It is appreciated.
If we want to build a detector from scratch for automatically detecting the state of an O27 switch track, and use only connections to the ground terminal and one of the other three terminals, how would we do it, in a way that would be robust and a simple as possible? This is the question.
Thanks again.
I just reread this post and realize I missed the part about building a detector from scratch. Do you mean not using the STM2 and instead building your own detector to interface to the LCS? That's entirely possible, but not so advisable since all the work has already been done for only about $90. I can however see the interest in how it was done...study the coding of the processor in the STM2, etc. But I don't have any specific knowledge as to building one. There are some forum folks however who would, and if you could create a passion in one of them to undertake the subject, the project might be realizable even though the time invested would far surpass the value of purchasing one.
One thing though is someone mentioned a block detector. That might be a welcome addition to the LCS family for some. Similar technology.
My thinking is to probably not go with Lionel LCS mostly because of what I am aware of with respect the software available to support it, and the entry costs. I have no Legacy or TMCC. My thinking is to use CTI hardware and software which runs under Windows. It seems to able able to do a nice job with switching track power to blocks, switching switch tracks and with occupancy detection in an all AC system, based on what I have read. Cost is reasonable, and one can start small at low initial cost. I like the features of the CTI software: software control panel, real-time layout schematic, and programming features. I can see that the programming will take some effort, but it looks like fun at this point. That is why I am interested in the switch state detection. I have not yet ordered anything from CTI, but am close to doing so.
To me, Lionel LCS would be more attractive if the software to support it would have more of the features that are attractive to me, and if the software would run on a hardware platform I already have. I use Windows and an android smartphone.
Barry835 posted:To me, Lionel LCS would be more attractive if the software to support it would have more of the features that are attractive to me, and if the software would run on a hardware platform I already have. I use Windows and an android smartphone.
Check out eTrain Command Console (L), a new Windows-based software program that works with Lionel's LCS hardware. It also works with Android phones. For links to the program and a little more info, see here: http://www.lionel.com/lcs/LCSPartner/index.html
Barry835 posted:My thinking is to probably not go with Lionel LCS mostly because of what I am aware of with respect the software available to support it, and the entry costs. I have no Legacy or TMCC. My thinking is to use CTI hardware and software which runs under Windows. It seems to able able to do a nice job with switching track power to blocks, switching switch tracks and with occupancy detection in an all AC system, based on what I have read. Cost is reasonable, and one can start small at low initial cost. I like the features of the CTI software: software control panel, real-time layout schematic, and programming features. I can see that the programming will take some effort, but it looks like fun at this point. That is why I am interested in the switch state detection. I have not yet ordered anything from CTI, but am close to doing so.
To me, Lionel LCS would be more attractive if the software to support it would have more of the features that are attractive to me, and if the software would run on a hardware platform I already have. I use Windows and an android smartphone.
Thanks for the explanation. You might have started your original question with a little of this background information. Good luck on the alternate approach and keep us informed on how you proceed.
