If you are using the Legacy cable, just for a serial cable I guess, with the cable plugged into the Legacy base, you must use the connector marked "serial comm" plugged into the computer serial input.
The other connector that is marked "command base" is not used except for the Powermaster Bridge or the TMCC command base.
If you are using the Legacy cable, just for a serial cable I guess, with the cable plugged into the Legacy base, you must use the connector marked "serial comm" plugged into the computer serial input.
The other connector that is marked "command base" is not used except for the Powermaster Bridge.
Or TMCC Command Base, that I use.
If you use a serial cable or USB to serial why do you need the Lionel Y connector?
Ken M
The Lionel Y connector cable is for having a serial to go to the computer and a connection to go to the Powermaster Bridge. That's the only use for it. The end that goes to the Powermaster Bridge is a totally different set of pin connections than the normal serial pin out.
cjack, the "Y" supplied with the Legacy system is more commonly used to hook a TMCC Base to the Legacy Base, hence the label "Command Base" on the male 9-pin connector. The connections at the 9-pin "Command Base" connector are still pins 2, 3 and 5. Those pins just feed into different pins at the male Legacy Base - pins 4, 1 and 5.
Perhaps you are referring to a different "Y" cable?
I think this point has already been made clear, but I'll say it anyway: If you are using a USB-serial adapter and ONLY connecting a computer to LEGACY base, there's no need to use the 'Y' cable supplied with the LEGACY system.
rudy
If you use a serial cable or USB to serial why do you need the Lionel Y connector?
Ken M
The Lionel Y connector cable is for having a serial to go to the computer and a connection to go to the Powermaster Bridge. That's the only use for it. The end that goes to the Powermaster Bridge is a totally different set of pin connections than the normal serial pin out.
cjack, the "Y" supplied with the Legacy system is more commonly used to hook a TMCC Base to the Legacy Base, hence the label "Command Base" on the male 9-pin connector. The connections at the 9-pin "Command Base" connector are still pins 2, 3 and 5. Those pins just feed into different pins at the male Legacy Base - pins 4, 1 and 5.
Perhaps you are referring to a different "Y" cable?
No, same one. I was confused that the only use for it was the Powermaster Bridge being connected to the "Command Base" end of the Y. I see now that it allows use of the Cab 1 if plugged into a TMCC base too.
But still, to connect to the computer, you have to use the Serial Comm end of the Y cable and not use the Command Base Y cable end?
What I was thinking is that the Command Base output is pin 2, that is, serial data comes out of the command base into pin 2 of the cable to send data into pin 4 of the Legacy base. So pin 2 of that cable end is an input...not an output which would be needed to go to a serial input of the computer. And that the only end of the Y cable that should be connected to the computer serial port is the one labled "Serial Comm".
I think this point has already been made clear, but I'll say it anyway: If you are using a USB-serial adapter and ONLY connecting a computer to LEGACY base, there's no need to use the 'Y' cable supplied with the LEGACY system.
rudy
Well I was thinking that Johnsgg1 was using the serial port on his computer and using the Legacy Y cable just as a cable. I was trying to say to be sure to use the "Serial Comm" end of it to connect to his serial input on the computer. I think that is true.
Thank you Rudy, I think your answer is very straight forward & what I thought.
KenM
Here is a question. Just ran my new DMIR Mikado. Engine ran great!
When I went to load the engine with the module, my Cab2 would not recognize the module. Checked several other modules and it was just this one. Could it be blank? If it is blank.. could I use the utility to create the module just as if it was a "black module" ?
Kind of wondered what Marty thought about this.
If it's not a black module, it is not writable, so the answer is no. 
I think the Utility is win only.
But I guess if you run Parallels or Bootcamp?
You can run the LEGACY System Utility on a Mac, BUT! You must have installed Windows on your Mac and either use Parallels, or in my case, VMWare Fusion. So it is true that LSU is "Windows only." But if you're running Windows on your Mac, it is possible to run LSU.
Rudy
Lionel, LLC
If it's not a black module, it is not writable, so the answer is no.
John the data must get written to the module originally somehow.
These are most likely OTP or mask parts, not re-writable modules. Re-writable modules are more expensive, and they don't use them unless there's a reason. 
These are most likely OTP or mask parts, not re-writable modules. Re-writable modules are more expensive, and they don't use them unless there's a reason.
I'm well aware that the black module is re-writable. The point of my post was just to have some conversation about a blank "orange" module and how the engine modules are originated.
These are most likely OTP or mask parts, not re-writable modules. Re-writable modules are more expensive, and they don't use them unless there's a reason.
I'm well aware that the black module is re-writable. The point of my post was just to have some conversation about a blank "orange" module and how the engine modules are originated.
Sorry, but I thought that's exactly what I posted. I'll be quiet now, since you didn't like my answer.
What I'm getting is that MichRR714 is wondering if the orange module IS blank (somehow mis-sent) if it could be written to (for the first and only time written to) by the base. Not likely, but a reasonable thought if you've never dealt with roms, eeroms, etc.
These are most likely OTP or mask parts, not re-writable modules. Re-writable modules are more expensive, and they don't use them unless there's a reason.
I'm well aware that the black module is re-writable. The point of my post was just to have some conversation about a blank "orange" module and how the engine modules are originated.
Sorry, but I thought that's exactly what I posted. I'll be quiet now, since you didn't like my answer.
Your conversation is welcome.. your attitude however is unnecessary.
What I'm getting is that MichRR714 is wondering if the orange module IS blank (somehow mis-sent) if it could be written to (for the first and only time written to) by the base. Not likely, but a reasonable thought if you've never dealt with roms, eeroms, etc.
Thanks Chuck. You sure got my drift.
Your conversation is welcome.. your attitude however is unnecessary.
OK, let's reset. Sorry that came across the wrong way. I actually thought I answered the question, but I think you changed the nature of what you were asking a bit after the fact. I'm not really trying to give you attitude, I thought I was trying to answer your question.
To recap:
You asked if the Legacy orange module was writable and I said no.
Next you made the statement about the data getting to the module, and I mentioned One Time Programmable and Masked parts.
Then it seems the conversation went south.
To recap, it's my belief that the parts they use in the colored modules would be either masked or a OTP part. I'm 100% certain you can't rewrite them with your Legacy controller, I just tried it to make sure.
I suppose if the parts were OTP parts and the module was really blank that it's possible it might write. However, typically OTP parts and normal FLASH parts have different control signals and write voltages, so it's not likely.
Here is a question. Just ran my new DMIR Mikado. Engine ran great!
When I went to load the engine with the module, my Cab2 would not recognize the module. Checked several other modules and it was just this one. Could it be blank? If it is blank.. could I use the utility to create the module just as if it was a "black module" ?
Kind of wondered what Marty thought about this.
Here in my original post I stated that I felt my module could be blank. Thus never written to. I don't think I ever changed the nature of my question.
I'm going to try to write to my suspected blank module today and will post what I find.
I'm be amazed if you can write to it, but I've been amazed before. 
I'm be amazed if you can write to it, but I've been amazed before.
John, no dice on the write. It acted like no module was present. All is not lost though, I learned something and I fixed the Mars light on my S3 with a couple more clicks
Yep, several people have apparently fixed their mars light with the utility. I fixed the fact that I couldn't program any engine for #2, there was garbage in the fields and apparently the Legacy CAB2 didn't know how to erase it.
Too bad about the module, but it would have been a fluke to be able to program it I suspect. I'm temped to pry one of the 1.2 modules apart to see what chip they use, it's not like I'll ever be going back to that version again!
I'm be amazed if you can write to it, but I've been amazed before.
John, no dice on the write. It acted like no module was present. All is not lost though, I learned something and I fixed the Mars light on my S3 with a couple more clicks
How does the the Mars light function now?
This gave me a reason to get a computer for the train room. Always wanted one there so I bought a new opened box INSPIRON mini Dell laptop for $200 on ebay. Bought the Serial / USB adapter, a $6.00 seial Y cable (The one that comes with legacy is not a Y cable), and a 30ft USB cable. Downloaded the software and set up the utility no problem. So now I have a fully functional PC on my train worktable permanently connected to the legacy base. I also hooked up my P-touch label maker (didn't realize how much more you could do using the PC program to create the labels), and the internet so I can look-up and order parts without leaving the workbench.
I have to say I like having the utility but I am a little disappointed. I was hoping for more functionality. You can edit engine data but nothing else. OK - so adding Rule-17 to my CC2 was pretty cool. But why not have a tab to edit accessory info? Also, I was really hoping for a way to save the recordings off of the CAB-2. My layout is very complex and very automated. For example, I run 2 trains on one track that perform an automatic exchange via a siding after 3 laps. The exchange is automatic using relay boards but I use the Cab-2 recording to control the action of each engine. It takes a long time to get it just right and everytime I change the engine combo I have to redo the recording. It would be nice to be able to create a library of recordings.
When are the black modules coming out? I can't find anyone taking orders and version 1.4 does not seem to be available to download
Maybe someone could inquire about the potential to expand the functionality of the utility at the morning sion at York.
I have no doubt that the functionality will increase over the next year and beyond. Small beginnings...
We are really the beta testers for this utility, it hasn't been "advertised" so others outside of the OGR forum know about it. I expect much more is coming. Including editing "Lash ups". As soon as the black modules are available we will probably see ver 1.4 released.
Patience,
Dan
How does the the Mars light function now?
Great. With the ability to edit the engine, I added the functionality to turn the Mars light off and on. I removed Rule 17 lighting, however since it was active when the engine was last used that feature will still be operational.
Received my cables to hook up my LSU to computer. I used USB cable 15 meters long or approx 49 feet. works good. I am unable to figue out how to edit trains, am I missing something.
Thank You
Ken
For anyone who's interested, I leave my Legacy Base connected to the layout and have a home-made 30' ribbon cable, connected to a 6' serial<--> USB Cable, that then connects to the PC in the workroom. I then use the PC to load black modules in the Base for updating the Base and the Cab-2.
The ribbon cable has been in place for the past 8 years so that I never have to remove my 3 TIUs from the layout to update their software. Now, the same cable also works for Legacy updates.
I then use the PC to load black modules in the Base for updating the Base and the Cab-2.
Barry, How did you obtain your black modules?
I then use the PC to load black modules in the Base for updating the Base and the Cab-2.
Barry, How did you obtain your black modules?
A few got them for testing purposes, they will soon be commercially available, until 1.4 is released online there is really nothing to do with them anyway
A few got them for testing purposes, they will soon be commercially available, until 1.4 is released online there is really nothing to do with them anyway
Is Barry writing a book on Legacy now??
Barry, How did you obtain your black modules?
I'd tell you but then I'd have to kill you...
Is Barry writing a book on Legacy now??
I'v been assured that if I did, no one here would read it, because it's unnecessary.
I wonder if the new ZW-L will come with a 1.4 module?
It should since 1.4 is required to use it
I'd tell you but then I'd have to kill you...
Get in line behind my wife.
FYI - I found leaving the USB connected to the computer (without the utility running) does interfere with the devices wired via the command base cable. My accessories run on auto pilot through an ARC. With the cable in, some commands in the sequence get dropped. Leaving the USB plug out of the computer is an easy fix. I'm not sure why technically this happens but I think it may have to do with the serial converter. It would not have be apparant to me if I didn't have automated sequences.
Access to this requires an OGR Forum Supporting Membership
