http://www.lionel.com/lcs/LCSproducts/STM2/index.html
I was hoping lionel would make a product like this and the wiring looks very simple!
|
http://www.lionel.com/lcs/LCSproducts/STM2/index.html
I was hoping lionel would make a product like this and the wiring looks very simple!
Replies sorted oldest to newest
This is a nice addition. I wonder if this is going to be shown at the York LUG meeting this week.
That is a nice addition. Although it's clearly for Fastrack switches, it appears it uses the +/- indicator output of the switch, so other switches could be adapted to feedback as well. I wonder if Alex figured on this for his non-contact points position indicator?
Now that the "cat" is out of the bag, we will be showing this at the LUG meeting as well. It works wonderfully.
It will be for many different switch types I am told. As of now I have it set to be triggered from a standard FT switch.
JonZ and Rudy have been very helpful in getting us all the LCS components together to show as much as we can. I believe I can say we will have all of them on hand for the LUG meeting. Only the SER2 will not be active as I really didn't have anything to connect it to.
It looks like you will need an ASC2 to use with other than Fastrack command switches.
Actually, with this module providing the feedback, I can't see why you can't use the SC2 as well. The feedback is independent of how the switch gets changed, the whole basis of having this feedback module.
That is correct, the STM2 is meant to complement, not replace the functionality of a command control switching device. In other words, it doesn't throw the switch, it tells you (or more accurately, tells your Lionel LCS App) that a switch has been thrown.
I'm not sure if "need" is the best word. If you want your LCS App to know when a switch is activated by a traditional lever-switch or by the non-derailing feature of a switch, then the STM2 is for you.
We bought into the whole LCS concept Rudy, so now we "need" the STM2!
I need it...
I need it...
Can't find iCab...guess it's not out yet.
Will the STM2 expand beyond 16 switch positions like the SC-2s by programming addresses?
Oh...I see PGM button on the picture, so that answers my question I think.
Will the STM2 expand beyond 16 switch positions like the SC-2s by programming addresses?
Oh...I see PGM button on the picture, so that answers my question I think.
Yes, you program its base address and if you use more than one, just make sure their addresses do not overlap.
I wonder if Alex's sensors could be tied to the STM2 to provide the actual switch position. And how would an incomplete throw be monitored?
Dan
Will the STM2 expand beyond 16 switch positions like the SC-2s by programming addresses?
Oh...I see PGM button on the picture, so that answers my question I think.
Yes, you program its base address and if you use more than one, just make sure their addresses do not overlap.
I have 8 non-TMCC Fastrack remote switches. I have pre-ordered 2 ASC2's to control them with the LCS app. I will use up 8 TMCC ID's for the 2 ASC2's. If I get an STM2, does it use additional TMCC ID's? If it does, do all 16 TMCC ID's have to be used or can it be programmed to use fewer (in my case 8) ID's?
If the STM2 uses its own TMCC ID's, then 8 switches will use up at least 16 TMCC ID's.
Between engines, lash-ups, switches, command control rolling stock (dining cars, ethanol tankers, etc), and command control accessories (culvert loader and unloader, etc.), the limit of 99 TMCC ID's is becoming a serious constraint.
The switch ID and the STM2 ID must match, that is how the linkage is set between the switch and the monitoring. Also the STM2 monitoring inputs are all consecutive. Thus if the STM2 is set to SW 1, it also monitors 2 thru 16.
There is no need to set the STM2 to monitor less than 16, if the input is not connected then no commands are generated or sent to the iPad. For example if you only connect one switch to monitor on the STM2, then the balance of the IDs are not "used up". Actually, the STM2 does not "use" any switch ID at all. The SW ID setting is only important for formatting the monitoring response.
Between engines, lash-ups, switches, command control rolling stock (dining cars, ethanol tankers, etc), and command control accessories (culvert loader and unloader, etc.), the limit of 99 TMCC ID's is becoming a serious constraint.
Vince, switches have their own set of 99 ID's, as do accessories. Neither of these affect the 99 ID's for locomotives.
I wonder if Alex's sensors could be tied to the STM2 to provide the actual switch position. And how would an incomplete throw be monitored?
Dan
On Fastrack switches, and incomplete throw shows a variable voltage of less than 2 volts typically. And the manual controller goes dark. My wild guess for Fastrack switches is that the STM2 looks for plus or minus voltage with a threshold maybe of less than a volt, so it would report whichever position it was last in, but not a definitive incomplete.
It's not clear if the STM2 knows what to do with an incomplete throw. I don't know how it would indicate that status.
Between engines, lash-ups, switches, command control rolling stock (dining cars, ethanol tankers, etc), and command control accessories (culvert loader and unloader, etc.), the limit of 99 TMCC ID's is becoming a serious constraint.
Vince, switches have their own set of 99 ID's, as do accessories. Neither of these affect the 99 ID's for locomotives.
Boy do I feel like an idiot. I always set aside a range of ID's for the switches and never used those ID's for engines.
Thank you GRJ.
At least it's nice to know I'm not the only one that occasionally tosses out a really stupid statement and then feels like an idiot.
I'm sure it's happened to all of us at times, it's just your turn in the barrel.
Between engines, lash-ups, switches, command control rolling stock (dining cars, ethanol tankers, etc), and command control accessories (culvert loader and unloader, etc.), the limit of 99 TMCC ID's is becoming a serious constraint.
Vince, switches have their own set of 99 ID's, as do accessories. Neither of these affect the 99 ID's for locomotives.
Boy do I feel like an idiot. I always set aside a range of ID's for the switches and never used those ID's for engines.
Thank you GRJ.
I don't find the question dumb. Whenever I do something like the "range of ID's" thing my wife says "you are thinking too much...again".
There are no dumb questions Chuck, just dumb answers.
I think he was just thinking that he only had a total of 99 ID's for engines, switches, and accessories. No big deal, just brain fade, we all have it from time to time.
This may be silly, but why not just look at the color of the lights on the switches?? red for 'out', green for 'thru'. Why bother with the extra wiring and expense?? Unless you can't see the light(s)
This may be silly, but why not just look at the color of the lights on the switches?? red for 'out', green for 'thru'. Why bother with the extra wiring and expense?? Unless you can't see the light(s)
The system allows the layout display on the tablet (drawn by the LCS app) to be updated in real time, so that the display accurately reflects the physical status of the switches on the layout regardless of whether they have been thrown manually or wirelessly via the app. The layout display on the app would become frustrating to use if its display gets out of sync with what is actually happening on the layout.
It looks as though if you really wanted to get hi tech and use I-phones, droids, etc..., to run your trains, it's going to cost use in the neighborhood of $300 EXTRA over any Legacy equipment you have. Now if we're running trains, why not just use what normally runs trains, example: in this case a Legacy hand held. If you are in the room running trains, why use your phone?? I don't get this one! You can't be tied so much to your phone that you rely on it to run all things in your life. I think it's time for therapy here.
Obviously, you are not a candidate for the new LCS stuff. Also, your estimate of $300 is pretty light, you also need a bunch of sensor tracks.
The problem with 'new age' electronics is that if one part of the system breaks down and you want to replace it, a 'new' improved version comes along and your system is obsolete, they don't make 'em anymore. I don't mind new, but phone apps to control trains, an expense not necessary.
Note: my TCP 300 bit the dust, not remade by L, so now it's the new Powermaster for replacement, which actually looks like the old Powermaster in a different color. (and it still can't handle the power of a TPC, but it's wireless).
My issue is that I would have to essentially rewire, or actually add wires, to every switch which would require tearing them all up to add this. That is something that is almost a no-go for me.
My issue is that I would have to essentially rewire, or actually add wires, to every switch which would require tearing them all up to add this. That is something that is almost a no-go for me.
If you have the controllers connected to your switches, then you could intercept the yellow wire there. If you just use SC-2s, 3 conductor wire, and didn't bring the yellow wire out...I see your problem.
My issue is that I would have to essentially rewire, or actually add wires, to every switch which would require tearing them all up to add this. That is something that is almost a no-go for me.
If you have the controllers connected to your switches, then you could intercept the yellow wire there. If you just use SC-2s, 3 conductor wire, and didn't bring the yellow wire out...I see your problem.
I was thinking about that. A lot more tedious because of the way I have set up my layout but way more practical to do. I may end up doing that.
It looks as though if you really wanted to get hi tech and use I-phones, droids, etc..., to run your trains, it's going to cost use in the neighborhood of $300 EXTRA over any Legacy equipment you have. Now if we're running trains, why not just use what normally runs trains, example: in this case a Legacy hand held. If you are in the room running trains, why use your phone?? I don't get this one! You can't be tied so much to your phone that you rely on it to run all things in your life. I think it's time for therapy here.
Super O man, LCS was designed to be an easy to implement control panel.
Your point is well taken, however I want to point out that a hardwired control panel is not free to implement. When comparing the energy to build, wire, and implement a wired control panel, the LCS system comes in easier and probably cheaper. And it can be reconfigured easy.
The folks who want to augment their control panel, or simply have put off making a control panel the LCS approach is advantageous - minimal space, same or less cost, ease of use, ease of reconfiguration, sound effect augmentation, and just plain cool
If you are using ASC2s, is the read back built in or do you need the STM2 also?
I have the iPad app working with my switches. It's great, you can hand it to a visitor and they can set them without knowing the switch number, I also have a hard time remembering them quickly. If you have a small layout you don't need it. The larger the layout the more it enhances operation. Also, not all of my switches are easily seen. Some are on the other side of the layout or behind a mountain where you wouldn't walk around to. My layout is probably a medium sized layout. Two 130' and two 80' loops, 6 crossovers, 13 other switches, plus a yard and roundhouse areas I haven't built yet which will have another 10 plus switches. There is also a mountain switchback and town loop for another 4 switches. Can't wait to get it all done.
Dan
If you are using ASC2s, is the read back built in or do you need the STM2 also?
I have the iPad app working with my switches. It's great, you can hand it to a visitor and they can set them without knowing the switch number, I also have a hard time remembering them quickly. If you have a small layout you don't need it. The larger the layout the more it enhances operation. Also, not all of my switches are easily seen. Some are on the other side of the layout or behind a mountain where you wouldn't walk around to. My layout is probably a medium sized layout. Two 130' and two 80' loops, 6 crossovers, 13 other switches, plus a yard and roundhouse areas I haven't built yet which will have another 10 plus switches. There is also a mountain switchback and town loop for another 4 switches. Can't wait to get it all done.
Dan
It senses +5 or -5 as to showing Green or Red...so...and it shows that on the iPad for the switch address to which the sense wire is connected.
Seems like to do a block, the software would have to distinguish between a switch and an isolated length of track. I would guess that a Block Status Module 2 (BSM2) would be what is needed responding to a track voltage by a wire, and a way to isolate track sections in the software and shown on the iPad. That would be cool...and probably thought of by the developer . Why not? It's just code, right?
I assume Block Status Module 2 (BSM2) is not a real thing, correct?
I assume Block Status Module 2 (BSM2) is not a real thing, correct?
Correct. Seems like an obvious one though to monitor the presence of the track voltage...and not unlike what is already written for the switches.
It's an interesting suggestion. How many of you have your track split into isolated blocks that correspond to the way you'd want to visualize block status on your tablet?
Access to this requires an OGR Forum Supporting Membership