CAB-2 update to 1.6 goes OK--Base update gives blinking yellow light

I suggest trying the update again.  You may have a bad download or black module write, perhaps download the code again and cook the black module again?

I redownloaded the v 1.6 software and remade the black module.  Same result.

It seems odd to me that the yellow light on the Base is blinking, yet the CAB-2 CTC screen says that the Base is running 1.6.  If there were an error, wouldn't the CTC screen say that the Base was still running the previous version I had installed (1.54)?

Also, I notice that now, when I power up the CAB-2, the first screen that appears is the last one I used before powering down the CAB-2.  With the previous versions of the software, the first screen that appeared was the CTC screen.  Is this a change with 1.6?

Keith

I had the same exact problem. I had to send it beck to Lionel. They fixed it and shipped it back to me for free.  Great service.

Do you mean you were getting the 6-blink error code after updating your Base to 1.6?  What did Lionel say was the issue?

Keith

It was a six blink error and the base would not upgrade.  I cant remember what the issue was, but I purchased my 990 back in  August 2014 with the first batch after the long delay in production.  

I didn't experience the same issue, but I did have an error with updating my Legacy base to 1.6 just yesterday.  I've recently added LCS WiFi to the mix and updated to the LSU V2 which now supports connecting to the Legacy base via WiFi as well as serial.  (See my separate post on that experience.)  

I purchased the Legacy 990 set in January of 2015.  It was on V1.52 and the update to V1.6 was the first I'd tried having only just gotten a pair of black modules.  I made a 1.6 Cab2 module and a separate 1.6 base module.  LSU reported no problems creating either.  The Cab2 update went just fine.  But the base update resulted in a 4-blink error.  Repeating the update twice still resulted in the 4-blinker.  I then remade the base module in LSU and again received no error from LSU.  This time the base updated fine with no blink errors.  

I would download the update again and remake the black module.  I'd repeat that a number of times.  Although if you get the same result after a few tries then I suspect you have the same issue as MikeN.

Thank you for the suggestions.  I've redone the update of the Base multiple times, including redownloading the update and remaking the black module, and I keep getting the same 6-blink error code.

A few additional notes that may help to hone in on the problem:

Every time I run the Base update--that is, AFTER the first time I tried to update the Base (see below*)--the CAB-2  reports that the Base is running v. 1.6.

I seem to be able to access the changes from 1.54 to 1.6 on the CAB-2.  Would I be able to do this if the Base were not also updated?

Can someone who has 1.6 tell me if when you power up the CAB-2, the screen that appears is not the CTC screen, but the last screen you were using before powering down?

*The very first time I tried to update the Base to 1.6, the CAB-2 was in the Base, which was on a shelf under my layout, and, because it was dark (!), I inadvertently put the Base module into the port in the CAB-2, which was an inch above the port in the Base.  Of course, the update didn't run that time.  Is it possible that that first unsuccessful attempt to update the Base without the module in the Base port activated the 6-blink error code and that, since then, the updates have been successful, but that, for some reason, the error code will not go off?

Keith

Mine failed the update as well, don't remember number of blinks (thinking 3, but could have been 6?), but they were red. Lionel tech at LHS tried it also and it failed. His was the third black module tried (I tried two). LHS's 990 upgraded just fine with his module. I talked to Lionel a couple of times on the problem, tried everything they suggested. It had to go back to them for repair. It was still under warranty. I have upgraded it twice I think since then with no problems, so they got it fixed. I believe the service ticket said they had to reset something inside, from their note on the repair ticket it wasn't clear to me what they reset?

"Can someone who has 1.6 tell me if when you power up the CAB-2, the screen that appears is not the CTC screen, but the last screen you were using before powering down?"

Yes I am running 1.6 it does as you describe.

Nick

Gentlemen,

   Nick is correct when Lionel fixed my 990 Base they upgraded it to 1.6 the latest Rev and it operates as Nick indicates.  Last screen used before powered down.

PCRR/Dave

I plan to contact Lionel customer service next week, but I've continued to try to troubleshoot the 6-blink error code.  Even though I'm getting the error code on the Base, it seems (as I mentioned above) that the Base did update with 1.6.

I've just discovered that if I power down the Wi-Fi module, the 6-blink error code on the Base turns off!  Even if I haven't connected to the Wi-Fi module with my iPad, the mere fact of the Wi-Fi module being powered up is associated with getting the 6-blink error code.  I also have a BPC2 in my system, but whether it is powered up or down has no effect on the 6-blink error code.  As far as I can tell so far, the Legacy system and the Wi-Fi are otherwise operating normally and I seem to be able to access the 1.6 changes.

Does anyone have any idea why the Wi-Fi module being powered up--even if not connected to the iPad--would cause the error code on the Base?

Keith

Keith Levine posted:

I plan to contact Lionel customer service next week, but I've continued to try to troubleshoot the 6-blink error code.  Even though I'm getting the error code on the Base, it seems (as I mentioned above) that the Base did update with 1.6.

I've just discovered that if I power down the Wi-Fi module, the 6-blink error code on the Base turns off!  Even if I haven't connected to the Wi-Fi module with my iPad, the mere fact of the Wi-Fi module being powered up is associated with getting the 6-blink error code.  I also have a BPC2 in my system, but whether it is powered up or down has no effect on the 6-blink error code.  As far as I can tell so far, the Legacy system and the Wi-Fi are otherwise operating normally and I seem to be able to access the 1.6 changes.

Does anyone have any idea why the Wi-Fi module being powered up--even if not connected to the iPad--would cause the error code on the Base?

Keith

That is normal operation. It's still communicating with the base even though the iPad isn't. The yellow light will blink when the WiFi is hooked up. You're most likely fine.  The information you just provide was the missing piece of the puzzle. 

I agree with Marty. To confirm that all is actually working correctly, I suggest you try the 1.60 base update one more time, but with the DB9 LCS cable disconnected from your command base. If the update finishes normally without any blinking error codes, then all is well and there's no need to contact customer service.

When any LCS component is connected to the command base, it sends a ping (a "heartbeat" sort of command) about once a second. So the light on your command base will always be blinking slowly when that cable and an LCS device are connected. Perhaps these ping commands are making it look like the base is giving you an error code, when in fact, it's just the LCS system heartbeat.

Thank you, Marty, for figuring out what I was seeing after the 1.6 Base update; thank you, Rudy, for suggesting how I could confirm it; and thank you everybody else for helping as well.

Per Rudy, I ran the Base update again with the DB9 LCS cable disconnected, and, voila, NO blinking yellow light on the Base after the update.  Marty's diagnosis confirmed!

What I'm wondering, for the future, is what is the difference between the once-a-second blinking yellow light that indicates communication between an LCS device and the Base, and the blinking yellow light that's an error code signifying a "Verify fail after program" error after a Base update attempt?

The yellow light I see on the Base, which I now know is indicating LCS device - Base communication, seems to be blinking once a second, with a slight pause after every 6 blinks.  How is this different from the 6-blink error code?  Or do both situations make use of the same blinking yellow light pattern?

Keith

Keith

i suspect when Legacy was released many years ago, LCS was not on the radar. So I imagine the thought of the error code and the heartbeat were not on anyone's list. Anyways trying to get the module in with the db9 connected is quite a feat. LOL. Glad you got it figured out!

I'll inquire as to the on/off timing of error code blinks vs. the normal LCS heartbeat and include that info in the read me.txt file next we release a Legacy system software update. I've also mentioned this to our customer service folks so they can ask the question next time an LCS user reports a 6-blink error. Thanks for your help!