Legacy System Control Software

Why not do the computer link wirelessly?  Then you can use the Legacy System Utility without changing anything, just change it's configuration to connect through the network?

That’s what I do. Wireless.

gunrunnerjohn posted:

Why not do the computer link wirelessly?  Then you can use the Legacy System Utility without changing anything, just change it's configuration to connect through the network?

First off than you for the reply. Great suggestion, but you make a fatal assumption. The computer that I use is not a laptop, but it is a desktop that still has both serial and parallel port connections, no wireless, and I do not want to add wireless. The computer is connected to my network via a ethernet connection. 

Ed

You mean to tell me there's no wireless connections to your network?  It doesn't have to be on your computer, just connected anywhere on the network.

gunrunnerjohn posted:

You mean to tell me there's no wireless connections to your network?  It doesn't have to be on your computer, just connected anywhere on the network.

I am now confused.  The computer that this software is running on has no wireless connection or wireless adapter. So exactly how will it connect to the Legacy base. My train room is a out building on my property. It has internet connect via a access point that is setup in bridge mode (this access point is connected to a switch)  and talks to another access point that is also in bridge mode, that access point is connected to my network. The computers in the workshop/train room are all hardwired ethernet connections, as there is no wireless connection available. From page 10 of the manual:

To use the Legacy System Utility wirelessly, your computer must be connected to the WiFi network created by (or "joined to") the LCS WiFi module. Refer to the LCS WiFi Owner's Manual for details on installation of the LCS WiFi. Refer to your computer's operating system manual for information about connecting to wireless networks.

That is why I am confused by your reply

Ed

Do you connect to a network that has WiFi?  This computer has a direct Ethernet connection to my network switch (and router), but I can talk directly to my WiFi unit as well as the other wireless devices on my network. 

If you have no wireless connectivity on the network locally, that's easy to fix.  Simply connect an Access Point to your local switch that is serving the Ethernet connections and provide yourself with WiFi in your out building.

gunrunnerjohn posted:

Do you connect to a network that has WiFi?  This computer has a direct Ethernet connection to my network switch (and router), but I can talk directly to my WiFi unit as well as the other wireless devices on my network. 

If you have no wireless connectivity on the network locally, that's easy to fix.  Simply connect an Access Point to your local switch that is serving the Ethernet connections and provide yourself with WiFi in your out building.

When the access points (at least the ones that I have) are set up in bridge mode they no longer act as a normal access point and broadcast a ssid they strictly talk to each other at the mac address level.  Again according to the manual the computer running the Utility software can only connect wired (serial) or wifi, since the computer has no wifi adapter it is a serial connection. "To use the Legacy System Utility wirelessly, your computer must be connected to the WiFi network created by (or "joined to") the LCS WiFi module. Refer to the LCS WiFi Owner's Manual for details on installation of the LCS WiFi. Refer to your computer's operating system manual for information about connecting to wireless networks". I don't use LCS for its WIFI feature, only for the sensor modules, serial adapters, etc. If I did use the LCS WIFI adapter it can join a network only via a WIFI connection (again no access point as such is in use), as they do not provide a ethernet port, as I wish they would have done. John, you kinda missed the point of this original post. I don't want to add a lot more hardware, I would like to see the Utility software work connected via serial connection, connected to a LCS serial adapter, which currently is a unsupported function.

You're right, if in your case you don't add more hardware, you're probably out of luck.  I'm not holding my breath for Lionel to address this issue, but you can always hope.  Since most folks probably have WiFi available, I suspect that was the target market that Lionel programmed for.

ehkempf posted:

Will the Legacy System Control Software ever see a update? The one I would like to see most it the ability for it to be used chained off the LCS serial port. To use it now I have to connect and disconnect the LCS system from my computer's serial port in order to use one or the other. I find that using the Legacy System Control Software is the easiest way yo make change to the engines that in the command base. The other change I would like to see is the ability to make engine numbers numeric and alpha, not just numeric. A good example is I just set up the Santa Fe f3 set and noticed that the lead engine was assigned 22L, I would like to make the other three engines in this train 22A, 22B and 22C, but alpha are not allowed even though the system automatically assigned 22L to the lead engine that went over the sensor track.

Ed

Can't you use the Y cable to connect both the computer and the LCS Power to the base? This is included with the #990 set.

There are gender changers if that's the issue.

There won't be any Alpha characters added due to the coding of the Legacy system. 00-99 is it.

Moonman posted:

ehkempf posted:

Will the Legacy System Control Software ever see a update? The one I would like to see most it the ability for it to be used chained off the LCS serial port. To use it now I have to connect and disconnect the LCS system from my computer's serial port in order to use one or the other. I find that using the Legacy System Control Software is the easiest way yo make change to the engines that in the command base. The other change I would like to see is the ability to make engine numbers numeric and alpha, not just numeric. A good example is I just set up the Santa Fe f3 set and noticed that the lead engine was assigned 22L, I would like to make the other three engines in this train 22A, 22B and 22C, but alpha are not allowed even though the system automatically assigned 22L to the lead engine that went over the sensor track.

Ed

Can't you use the Y cable to connect both the computer and the LCS Power to the base? This is included with the #990 set.

There are gender changers if that's the issue.

There won't be any Alpha characters added due to the coding of the Legacy system. 00-99 is it.

I was not talking about the id no. Which is 1-98, but rather the road number. In the case I used the LCS system assigned 22L to my SF F3, but that is something that cannot be done on the cab2 in the info screens, nor the utility software. Only one end of the Y cable is for serial comm, so it can be connected to the comm port on a computer, or the LCS cable, the other end of the Y cable is for connection to a TMCC command base, not another comm port, to the best of my knowledge.

ehkempf posted:

Moonman posted:

ehkempf posted:

Will the Legacy System Control Software ever see a update? The one I would like to see most it the ability for it to be used chained off the LCS serial port. To use it now I have to connect and disconnect the LCS system from my computer's serial port in order to use one or the other. I find that using the Legacy System Control Software is the easiest way yo make change to the engines that in the command base. The other change I would like to see is the ability to make engine numbers numeric and alpha, not just numeric. A good example is I just set up the Santa Fe f3 set and noticed that the lead engine was assigned 22L, I would like to make the other three engines in this train 22A, 22B and 22C, but alpha are not allowed even though the system automatically assigned 22L to the lead engine that went over the sensor track.

Ed

Can't you use the Y cable to connect both the computer and the LCS Power to the base? This is included with the #990 set.

There are gender changers if that's the issue.

There won't be any Alpha characters added due to the coding of the Legacy system. 00-99 is it.

I was not talking about the id no. Which is 1-98, but rather the road number. In the case I used the LCS system assigned 22L to my SF F3, but that is something that cannot be done on the cab2 in the info screens, nor the utility software. Only one end of the Y cable is for serial comm, so it can be connected to the comm port on a computer, or the LCS cable, the other end of the Y cable is for connection to a TMCC command base, not another comm port, to the best of my knowledge.

The Y cable is just a DB9. I haven't had mine out in while. I connect it to the base and to a usb to DB9 adapter in my laptop for LSU updates and such. 

So, you just connect the LCS power cable to the other Y rather than a TMCC base or TPC. 

Now I understand about the prefill of the engine ID by the LCS. I just run straight legacy, so I can't help you on that. email one of the Lionel guys.

Forum member martyE stays up on that with the Lionel folks. email him.

ehkempf posted:

Moonman posted:

ehkempf posted:

Will the Legacy System Control Software ever see a update? The one I would like to see most it the ability for it to be used chained off the LCS serial port. To use it now I have to connect and disconnect the LCS system from my computer's serial port in order to use one or the other. I find that using the Legacy System Control Software is the easiest way yo make change to the engines that in the command base. The other change I would like to see is the ability to make engine numbers numeric and alpha, not just numeric. A good example is I just set up the Santa Fe f3 set and noticed that the lead engine was assigned 22L, I would like to make the other three engines in this train 22A, 22B and 22C, but alpha are not allowed even though the system automatically assigned 22L to the lead engine that went over the sensor track.

Ed

Can't you use the Y cable to connect both the computer and the LCS Power to the base? This is included with the #990 set.

There are gender changers if that's the issue.

There won't be any Alpha characters added due to the coding of the Legacy system. 00-99 is it.

I was not talking about the id no. Which is 1-98, but rather the road number. In the case I used the LCS system assigned 22L to my SF F3, but that is something that cannot be done on the cab2 in the info screens, nor the utility software. Only one end of the Y cable is for serial comm, so it can be connected to the comm port on a computer, or the LCS cable, the other end of the Y cable is for connection to a TMCC command base, not another comm port, to the best of my knowledge.

I was able to program the road number for one of my Legacy engines with a alpha character using the Legacy system utility. Perhaps you're not on the latest firmware version (base 1.6 / cab2 1.61) or system utility which is 2.0 I believe.

But you can connect to the computer and the rest of the LCS system at the same time.  Per this diagram from the LCS website.

Buy a SER2 and that gives you another DB9 connector to go to the computer with.  See that they show that in the lower left corner of the diagram.

EDIT: Sigh.  Lionel really should put things together better.  The SER2 website does have a note that the SER2 does not work for the Legacy Utility Software.  Not sure why the WiFi would work and the SER2 doesn't.  They should totally fix that as the SER2 was how I was planning on connecting my computer to my LCS system to use the Lionel software as my base and such would be buried and not accessible to swap the connector between the base and the LCS system with.  And unless they have updated the WiFi module since it came out, it won't work with my home network as last I knew you couldn't manually inter in the network SSID or password which I would need as I have a hidden network with MAC address filtering.

Davety posted:

ehkempf posted:

Moonman posted:

ehkempf posted:

Will the Legacy System Control Software ever see a update? The one I would like to see most it the ability for it to be used chained off the LCS serial port. To use it now I have to connect and disconnect the LCS system from my computer's serial port in order to use one or the other. I find that using the Legacy System Control Software is the easiest way yo make change to the engines that in the command base. The other change I would like to see is the ability to make engine numbers numeric and alpha, not just numeric. A good example is I just set up the Santa Fe f3 set and noticed that the lead engine was assigned 22L, I would like to make the other three engines in this train 22A, 22B and 22C, but alpha are not allowed even though the system automatically assigned 22L to the lead engine that went over the sensor track.

Ed

Can't you use the Y cable to connect both the computer and the LCS Power to the base? This is included with the #990 set.

There are gender changers if that's the issue.

There won't be any Alpha characters added due to the coding of the Legacy system. 00-99 is it.

I was not talking about the id no. Which is 1-98, but rather the road number. In the case I used the LCS system assigned 22L to my SF F3, but that is something that cannot be done on the cab2 in the info screens, nor the utility software. Only one end of the Y cable is for serial comm, so it can be connected to the comm port on a computer, or the LCS cable, the other end of the Y cable is for connection to a TMCC command base, not another comm port, to the best of my knowledge.

I was able to program the road number for one of my Legacy engines with a alpha character using the Legacy system utility. Perhaps you're not on the latest firmware version (base 1.6 / cab2 1.61) or system utility which is 2.0 I believe.

I am running all the current software as you show above. When I tried putting the road number is as 22A, it would not take a alpha only numeric. How did you set it to work.

sinclair posted:

But you can connect to the computer and the rest of the LCS system at the same time.  Per this diagram from the LCS website.

Buy a SER2 and that gives you another DB9 connector to go to the computer with.  See that they show that in the lower left corner of the diagram.

 

EDIT: Sigh.  Lionel really should put things together better.  The SER2 website does have a note that the SER2 does not work for the Legacy Utility Software.  Not sure why the WiFi would work and the SER2 doesn't.  They should totally fix that as the SER2 was how I was planning on connecting my computer to my LCS system to use the Lionel software as my base and such would be buried and not accessible to swap the connector between the base and the LCS system with.  And unless they have updated the WiFi module since it came out, it won't work with my home network as last I knew you couldn't manually inter in the network SSID or password which I would need as I have a hidden network with MAC address filtering.

One WiFi trick I use when connecting a device with little options to control some of the settings for hidden networks. I temporarily make the hidden network visible, Connect my device and save the settings. Once it's working make the network hidden again, it should retain the settings and still connect.

ehkempf posted:

Davety posted:

ehkempf posted:

Moonman posted:

ehkempf posted:

Will the Legacy System Control Software ever see a update? The one I would like to see most it the ability for it to be used chained off the LCS serial port. To use it now I have to connect and disconnect the LCS system from my computer's serial port in order to use one or the other. I find that using the Legacy System Control Software is the easiest way yo make change to the engines that in the command base. The other change I would like to see is the ability to make engine numbers numeric and alpha, not just numeric. A good example is I just set up the Santa Fe f3 set and noticed that the lead engine was assigned 22L, I would like to make the other three engines in this train 22A, 22B and 22C, but alpha are not allowed even though the system automatically assigned 22L to the lead engine that went over the sensor track.

Ed

Can't you use the Y cable to connect both the computer and the LCS Power to the base? This is included with the #990 set.

There are gender changers if that's the issue.

There won't be any Alpha characters added due to the coding of the Legacy system. 00-99 is it.

I was not talking about the id no. Which is 1-98, but rather the road number. In the case I used the LCS system assigned 22L to my SF F3, but that is something that cannot be done on the cab2 in the info screens, nor the utility software. Only one end of the Y cable is for serial comm, so it can be connected to the comm port on a computer, or the LCS cable, the other end of the Y cable is for connection to a TMCC command base, not another comm port, to the best of my knowledge.

I was able to program the road number for one of my Legacy engines with a alpha character using the Legacy system utility. Perhaps you're not on the latest firmware version (base 1.6 / cab2 1.61) or system utility which is 2.0 I believe.

I am running all the current software as you show above. When I tried putting the road number is as 22A, it would not take a alpha only numeric. How did you set it to work.

I'll have to check once I get home this evening.

Davety posted:

ehkempf posted:

Davety posted:

ehkempf posted:

Moonman posted:

ehkempf posted:

Will the Legacy System Control Software ever see a update? The one I would like to see most it the ability for it to be used chained off the LCS serial port. To use it now I have to connect and disconnect the LCS system from my computer's serial port in order to use one or the other. I find that using the Legacy System Control Software is the easiest way yo make change to the engines that in the command base. The other change I would like to see is the ability to make engine numbers numeric and alpha, not just numeric. A good example is I just set up the Santa Fe f3 set and noticed that the lead engine was assigned 22L, I would like to make the other three engines in this train 22A, 22B and 22C, but alpha are not allowed even though the system automatically assigned 22L to the lead engine that went over the sensor track.

Ed

Can't you use the Y cable to connect both the computer and the LCS Power to the base? This is included with the #990 set.

There are gender changers if that's the issue.

There won't be any Alpha characters added due to the coding of the Legacy system. 00-99 is it.

I was not talking about the id no. Which is 1-98, but rather the road number. In the case I used the LCS system assigned 22L to my SF F3, but that is something that cannot be done on the cab2 in the info screens, nor the utility software. Only one end of the Y cable is for serial comm, so it can be connected to the comm port on a computer, or the LCS cable, the other end of the Y cable is for connection to a TMCC command base, not another comm port, to the best of my knowledge.

I was able to program the road number for one of my Legacy engines with a alpha character using the Legacy system utility. Perhaps you're not on the latest firmware version (base 1.6 / cab2 1.61) or system utility which is 2.0 I believe.

I am running all the current software as you show above. When I tried putting the road number is as 22A, it would not take a alpha only numeric. How did you set it to work.

I'll have to check once I get home this evening.

Just to be sure I tried using the Legacy system Utility program again. The field I am talking about is Engine Road#. It will only take numeric entries, no alphas. When you hit a alpha character noting happens and no entry is made.

ehkempf posted:

Davety posted:

ehkempf posted:

Davety posted:

ehkempf posted:

Moonman posted:

ehkempf posted:

Will the Legacy System Control Software ever see a update? The one I would like to see most it the ability for it to be used chained off the LCS serial port. To use it now I have to connect and disconnect the LCS system from my computer's serial port in order to use one or the other. I find that using the Legacy System Control Software is the easiest way yo make change to the engines that in the command base. The other change I would like to see is the ability to make engine numbers numeric and alpha, not just numeric. A good example is I just set up the Santa Fe f3 set and noticed that the lead engine was assigned 22L, I would like to make the other three engines in this train 22A, 22B and 22C, but alpha are not allowed even though the system automatically assigned 22L to the lead engine that went over the sensor track.

Ed

Can't you use the Y cable to connect both the computer and the LCS Power to the base? This is included with the #990 set.

There are gender changers if that's the issue.

There won't be any Alpha characters added due to the coding of the Legacy system. 00-99 is it.

I was not talking about the id no. Which is 1-98, but rather the road number. In the case I used the LCS system assigned 22L to my SF F3, but that is something that cannot be done on the cab2 in the info screens, nor the utility software. Only one end of the Y cable is for serial comm, so it can be connected to the comm port on a computer, or the LCS cable, the other end of the Y cable is for connection to a TMCC command base, not another comm port, to the best of my knowledge.

I was able to program the road number for one of my Legacy engines with a alpha character using the Legacy system utility. Perhaps you're not on the latest firmware version (base 1.6 / cab2 1.61) or system utility which is 2.0 I believe.

I am running all the current software as you show above. When I tried putting the road number is as 22A, it would not take a alpha only numeric. How did you set it to work.

I'll have to check once I get home this evening.

Just to be sure I tried using the Legacy system Utility program again. The field I am talking about is Engine Road#. It will only take numeric entries, no alphas. When you hit a alpha character noting happens and no entry is made.

You're correct. I just tried mine with the same results. I was thinking of the engine name and there are no number when using the cab2, however I was able to enter numbers there inside the system utility. So I got that backwards. 

Davety posted:

ehkempf posted:

Davety posted:

ehkempf posted:

Davety posted:

ehkempf posted:

Moonman posted:

ehkempf posted:

Will the Legacy System Control Software ever see a update? The one I would like to see most it the ability for it to be used chained off the LCS serial port. To use it now I have to connect and disconnect the LCS system from my computer's serial port in order to use one or the other. I find that using the Legacy System Control Software is the easiest way yo make change to the engines that in the command base. The other change I would like to see is the ability to make engine numbers numeric and alpha, not just numeric. A good example is I just set up the Santa Fe f3 set and noticed that the lead engine was assigned 22L, I would like to make the other three engines in this train 22A, 22B and 22C, but alpha are not allowed even though the system automatically assigned 22L to the lead engine that went over the sensor track.

Ed

Can't you use the Y cable to connect both the computer and the LCS Power to the base? This is included with the #990 set.

There are gender changers if that's the issue.

There won't be any Alpha characters added due to the coding of the Legacy system. 00-99 is it.

I was not talking about the id no. Which is 1-98, but rather the road number. In the case I used the LCS system assigned 22L to my SF F3, but that is something that cannot be done on the cab2 in the info screens, nor the utility software. Only one end of the Y cable is for serial comm, so it can be connected to the comm port on a computer, or the LCS cable, the other end of the Y cable is for connection to a TMCC command base, not another comm port, to the best of my knowledge.

I was able to program the road number for one of my Legacy engines with a alpha character using the Legacy system utility. Perhaps you're not on the latest firmware version (base 1.6 / cab2 1.61) or system utility which is 2.0 I believe.

I am running all the current software as you show above. When I tried putting the road number is as 22A, it would not take a alpha only numeric. How did you set it to work.

I'll have to check once I get home this evening.

Just to be sure I tried using the Legacy system Utility program again. The field I am talking about is Engine Road#. It will only take numeric entries, no alphas. When you hit a alpha character noting happens and no entry is made.

You're correct. I just tried mine with the same results. I was thinking of the engine name and there are no number when using the cab2, however I was able to enter numbers there inside the system utility. So I got that backwards. 

That is not correct.  You CAN add alpha and numeric characters using the Cab2 when entering engine NAME.  When in naming mode, use the red dial to scroll and select letters.  For numbers just select from keypad.   So you don’t need the utility.  

SandJam posted:

Davety posted:

ehkempf posted:

Davety posted:

ehkempf posted:

Davety posted:

ehkempf posted:

Moonman posted:

ehkempf posted:

Will the Legacy System Control Software ever see a update? The one I would like to see most it the ability for it to be used chained off the LCS serial port. To use it now I have to connect and disconnect the LCS system from my computer's serial port in order to use one or the other. I find that using the Legacy System Control Software is the easiest way yo make change to the engines that in the command base. The other change I would like to see is the ability to make engine numbers numeric and alpha, not just numeric. A good example is I just set up the Santa Fe f3 set and noticed that the lead engine was assigned 22L, I would like to make the other three engines in this train 22A, 22B and 22C, but alpha are not allowed even though the system automatically assigned 22L to the lead engine that went over the sensor track.

Ed

Can't you use the Y cable to connect both the computer and the LCS Power to the base? This is included with the #990 set.

There are gender changers if that's the issue.

There won't be any Alpha characters added due to the coding of the Legacy system. 00-99 is it.

I was not talking about the id no. Which is 1-98, but rather the road number. In the case I used the LCS system assigned 22L to my SF F3, but that is something that cannot be done on the cab2 in the info screens, nor the utility software. Only one end of the Y cable is for serial comm, so it can be connected to the comm port on a computer, or the LCS cable, the other end of the Y cable is for connection to a TMCC command base, not another comm port, to the best of my knowledge.

I was able to program the road number for one of my Legacy engines with a alpha character using the Legacy system utility. Perhaps you're not on the latest firmware version (base 1.6 / cab2 1.61) or system utility which is 2.0 I believe.

I am running all the current software as you show above. When I tried putting the road number is as 22A, it would not take a alpha only numeric. How did you set it to work.

I'll have to check once I get home this evening.

Just to be sure I tried using the Legacy system Utility program again. The field I am talking about is Engine Road#. It will only take numeric entries, no alphas. When you hit a alpha character noting happens and no entry is made.

You're correct. I just tried mine with the same results. I was thinking of the engine name and there are no number when using the cab2, however I was able to enter numbers there inside the system utility. So I got that backwards. 

That is not correct.  You CAN add alpha and numeric characters using the Cab2 when entering engine NAME.  When in naming mode, use the red dial to scroll and select letters.  For numbers just select from keypad.   So you don’t need the utility.  

Thanks, I did not know that.

Guys you missed the point of this post. I was asking about the Engine Road#, not the Engine Name, which I know can be used with alpha-numeric. What brought on this post was my new set of SF F3's. The lead engine is 22L, and that engine was assigned to the cab2 when it went over a sensor track. I want to assign engine numbers 22A, 22B and 22C to the other engines, but cannot, as the Utility will not allow alphas in the Engine Road# field.

ehkempf posted:

Guys you missed the point of this post. I was asking about the Engine Road#, not the Engine Name, which I know can be used with alpha-numeric. What brought on this post was my new set of SF F3's. The lead engine is 22L, and that engine was assigned to the cab2 when it went over a sensor track. I want to assign engine numbers 22A, 22B and 22C to the other engines, but cannot, as the Utility will not allow alphas in the Engine Road# field.

Since it can't be done in the cab2 or the utility this would be a question for Lionel. For some reason they chose to not allow that ability.

Davety posted:

ehkempf posted:

Guys you missed the point of this post. I was asking about the Engine Road#, not the Engine Name, which I know can be used with alpha-numeric. What brought on this post was my new set of SF F3's. The lead engine is 22L, and that engine was assigned to the cab2 when it went over a sensor track. I want to assign engine numbers 22A, 22B and 22C to the other engines, but cannot, as the Utility will not allow alphas in the Engine Road# field.

Since it can't be done in the cab2 or the utility this would be a question for Lionel. For some reason they chose to not allow that ability.

Also why the limit to only a 4 digit road number.  I have equipment with 6, and can't add it to the remote correctly.

Lionel probably started with a somewhat simplistic coding, with corresponding hardware (register space) and can't add more digits, etc. I think it mostly is what it is.