Unable to write modules

One way to see if your port works would be to reload 1.4 from the 1.4 Blue Base Module. At least you would know if the base acknowledges the port.  Hope this helps.

The only time I've gotten that error is with an incorrect module inserted.  If you stick a blue, orange, or white module in, you'll get that error.  If all things are working, a black module should never get that.

I have exactly the same problem with my Legacy system too.  I can load from the blue modules, but I cannot write to a black module.  I've tried with two different black modules. 

Like the OP, I can backup and reload via the cable to and from my computer. I get exactly the same error message when I try to write to a black module. It seems that my base is just unable to write, but is fine for reading.

If anyone has a solution, I too would really appreciate learning of it.

I'm guessing that Lionel is going to have to provide the solution.

......... and folks wonder why some would rather just purchased the module already programmed, or in my case I'll wait till 1.6 or 1.7 or something. 1.4 works well enough

Well, if you can't write modules, there's a good chance you can't read them either.

I put the blue 1.4 module, although I really have no way of knowing if it does anything, since 1.4 is already in there. I'm going to try and see if I can write modules in the club's base and then use them to update mine. Although, like you said John, if I cant write em, I probably cant read them either.

Mine can read OK.  I was able to reload the V1.4 blue modules OK. It just won't write.

I installed version 1.51 myself after downloading the file. This may sound silly but I would be a candidate to buy the modules ready to go from Lionel if they had them in a timely manner 

I completely understand people's apprehension about downloading and installing on their own. These are expensive items we have and buying programmed modules from Lionel would offer many some peace of mind that it will work. Just my thoughts. 

Writing them at the club is one way.  I did an update of a couple of bases for club members from 1.2 to 1.51 since they couldn't write with 1.2, so that's an option.

Nicole, did you try reading after you noticed it can't write?  I'm curious how that could happen.

For both of you, I'd take the modules somewhere to another Legacy system and see if they can be written.  It could, after all, be some defective modules.  Not likely, but it's nice to eliminate possibilities, that's Debugging 101.

At first I tried loading the black module even though I had received the error message. This failed of course, and left me with a corrupted base. So I re-loaded the blue module (With crossed fingers.) and that worked OK.  So I deduced that my base can read modules OK, but cannot write to them. My black modules came direct from Lionel, but a few months apart, so they are probably not from the same batch. I suspect that I've got a wonky base as it also has a faulty charger. 

I don't have the option to try my module in another base, as I know of no other Legacy users in this country. I'm also loathe to send my system back to Lionel for repair, as I don't want to be without it for an extended period of time. (By this I mean the two-way shipping time, not Lionel's repair time - which I understand is very fast.)  

Nicole, you have a good point in that you're in a totally different time-zone.   If you'd like, you can send me the modules, and I'll program 1.51 on them and send them back.

This is something to try. The modules do not

plug in very well and if there are any labels on

the sides , top or bottom, the module may

not plug in correctly. That rubber plug on the base that

covers the module connector makes it hard to plug in the

module so I removed it. The rubber plug will just pull

out from the base.

Try changing a setting for an engine that is all ready in the

base and see if you can save it to the base. This will indicate

that the computer can write to the base.

With a black module in place, select an engine that is in

the base and try saving just that engine to the module.

Saving all the base settings does not save to the module

but to a file in your computer so that is not a test of writting

to the module.

Lionel has said they will give no techinical support  for the

LSU so you are on your own except for the Forum.

so we have no LSU support from lionel correct?

so who actually made this online program for us to use and also whom do we download it from?

seems to me if your going to stop giving the free upgrade modules and then create a way for end users to upgrade themselves then you sure as heck need to support it.

just my opinion and it solves nothing except if indeed it's found once again to be a defective modules then were back to  QC yet you all keep feeding there coffers amazing simply amazing.

I speak my mind I'm not ranting just saying we deserve better and as a group united all current day manufactures will bow to customer service once again.

$oo

Lionel will still sell upgrade modules, so they're not "stopping" support for upgrades.  What they are doing is allowing you to do the upgrades for free once you have a black module, a pretty good deal IMO.

You shouldn't look a gift horse in the mouth.

You shouldn't look a gift horse in the mouth.

????  it's not for me I have plenty.

I think that Lionel has limited support for the LSU due to different configurations of compluters and cables. I am wondering if there is not a device conflict in the system causing the write error to the base. I would suggest looking there since the device conflict could be one where it can read but not write. The USB to Serial cables can be buggy and different manufacturers cables can act differently. I have been able to read and write to both of my bases wtih no problems.

I used the same laptop and the same cable set to write both the cab and base modules at the club without issue. Now that I have a different version, it is very easy to see that the port in my base at home will not read or write black modules. I tried the 1.4 blue module that came with the set when I bought it, and it is able to read that.

The black modules I wrote worked in updating the club's remote and base. I was also able to update my remote with the remote module that I made.

So now I'll be calling Lionel for an RA#, since obviously something is wrong within the base itself.

I have a bad base also. I decided to install the 1.51 upgrade today. I pulled out the black modules and wrote the files to them with no problems(using win 8 pro 64 bit by the way) but when I tried to update the base it wouldn't go into update mode. The yellow light never did flash and the base just seemed to go into regular mode. Thinking the module didn't write I went to the train room and updated the layout base with no problems. I guess it has a trip to Lionel in the future. Now to get around to making a couple of free modules.

Ron

Are all these bases with issues with the black modules from the new production, or are they older bases?  I'm curious to see if there's a pattern here.

My base is from last spring, and came with v1.4 installed.  I was wondering the same thing. Is it possible perhaps that the black modules don't work correctly with the latest bases? (Or the LSU software has a bug that doesn't like the newer bases. That's probably more likely, as I would be surprised if the hardware was changed much in that area. Also, mine seems to accept a reload from a blue v1.4 module OK.)  

John, thanks for your email. I'll be writing back to you shortly. Thanks again. 

I wonder if the other Legacy systems are also the newer production as well.  All the ones I've worked on have been older ones at least a couple years old.

My older base took the update from the black module but the newer one that came with 1.4 did not. I'll check to see if it will take the blue 1.4 module.

Ron

We may be seeing a pattern here, it seems that it "might" be some of the newer production has a problem.  Obviously, it's not all of them, because some folks here with new Legacy sets have written black modules.

FWIW, I looked at a new Legacy set that was in a local store for the owner, it also had a problem with black modules, forgot that data point.

My friend just got a legacy base with 1.4 ..I brought 1.51s over it took the update..I didnt try making them ...

The issue appears to be writing, not reading.

I have an older base and it took a update that was done on a blue module for me and the first one for the base did not work but got a 2nd one it it worked fine.  If you stick the module in and the side lights do not instantly start flashing it is not going to work.  that is what i found.

Mine had no trouble Writing the module and the write was good. It has trouble updating itself with the module. The module did update my other base so the file write is good. I think my problem lies in the button on the bottom. It doesn't seem to see that it is pressed on power up.

Ron

Update. It appears that the module did write the base to 1.51. So, I guess my problem is the amber light doesn't flash. I guess I just have a bad amber led in the base. I never thought to boot up and see if it took cause there was no flashing.

Ron

I did the write on a newer, came with 1.4 base, and the write worked fine. I also did a read to the base and 1.51 updated fine. Just wanted to check a new black module and the newer base to see if there was some wholesale issue with the newer bases. 

I bought mine in late July. It was  1.4 factory install. Neither reads or writes. Does not appear to even realize that there's a module in it (holding channel select and plugging it in merely initiates a standard start up sequence).

When the blue reprogram module is used, it works as it should. I dont know how the port pinout works, whether the black module uses a pin that the rest dont or whatnot and that pin has a bad joint, but it *should* work, and it doesnt work at all. There seems to be an internal disconnect between the port and the base memory.

I may have missed something here but the issue seems to point at the black modules. I have had no issue with the black modules I have. They are all from the very first when they became available.

I just reread the posts and it does look like Boilermaker1 has a bad 1.4 base...so more data please

I have some factory made black modules and some I created from blue modules.  All of them read and write in my command base without any issues.  That being the case, I can't imagine it's the black modules, it would seem that it's more likely the base.

FWIW, from reviewing the chip specifications for the EEPROM in the modules, there are no extra pins used, they just tie the write protect line off for black modules.  So, if it reads, it should write as well, it's the same pins, just different serial commands to the chips.

Got an RA from lionel this morning, I dont think I'll have time to ship it back until wednesday, so we'll see what happens.

Boilermaker1, if you have a moment to try one more thing, I'd appreciate knowing what your com speed is set to. You can find this under the LEGACY SYSTEM UTILITY Configure menu, Com Speed. If it's currently set to High, it is possible that choosing Low instead could help. 

thanks,

Rudy

Rudy,

I have been using the default "high speed", however I just tried using "low speed",  and it still does not work. It still says to check if there is a module in the base.

OK, thank you for checking. Please follow-through with your RA and send your base to service so we can get this sorted out.