|
|
![]() |
![]() |
The O Gauge Railroading On-Line Forum
Lionel TMCC and LEGACY
Legacy Scrolling/Train Data Problem-ISSUE RESOLVED|
Go
![]() |
New
![]() |
Find
![]() |
Notify
![]() |
Tools
![]() |
Reply
![]() |
|
My upgraded Legacy was returned super fast with V1.2 loaded and life is good again. I commend Lionel for doing a super job. One of my problems with Legacy was not corrected with V1.2. The problem is with the “Trains” function in Legacy. I operate 8 of my engines only in pairs and have built permanent lash-ups in the “TRAINS” menu on the CAB2. The lash-ups are as follows:
TR3 - 2 Atlas EOB engines in 32 speed step mode operated as TMCC1 engines. TR4 - 2 Lionel Odyssey engines operated as TMCC1 engines. TR30-2 Legacy engines TR40-2 Legacy engines When I build these lash ups everything works great, I can scroll to select a TR # and all the info is there. After about an hour of operating the scroll function quits. I have to manually select each TR # to operate that lash up. When the scroll function quits the single digit TR #s (3&4) disappear. All data about the lash up is gone and when I try to rebuild it the red light (no comms with base) on the CAB2 comes on and the CAB2 locks up. Sometimes the CAB2 will reset itself and other times I have to do a power down to unlock it. The 2 digit TR#s are OK but I have to punch in the numbers (no scroll) to operate them. I reloaded V1.2 but it didn’t help. I have rebuilt these lash ups using all single digit TR#s (2, 3, 4 & 5) and everything seems stable. It appears this only happens when I combine single digit TR#s with double digit TR#s. I am not sure if this is a Legacy issue or isolated to my system only. Anyone else experiencing anything similar? This message has been edited. Last edited by: jim london, |
|||
|
|
|
All Legacy remotes do NOT have that problem. Call Lionel Monday or maybe jon will see this thread and post what to do...
Hey I have a Railroad to Run... Operating the NYC, CSX, PRR, and NYNH & H RR Daily ! Where Trains run Often Located in Billville USA. |
|||
|
I run 4 Legacy engines simultaneously with one TR and two handhelds and I have not experienced any Legacy handheld anomalies.
|
||||
|
Billman/winrose, Thanks for the response. I think the CAB2 indications are a symptom and the problem is with the base as that is where the Train data resides. I've narrowed it down even further to two Train #s. I can use any combination of 2 digit and 1 digit Train #s as long as I don't use TR3 and TR30 together. I can build TR30 and as soon as I build TR3(or vice versa) the trouble begins. I tried this many times this morning and it failed everytime using those 2 numbers. I have many other combinations that work so I just won't use those numbers. The system performs GREAT since the upgrade and I am really enjoying Legacy.
Thanks again for the response, Jim London |
||||
|
Jim,
I would like to interact with you on this issue. Please don't clear your database, and let's try to find out why this is happening. Please email me (in my profile) and we can arrange to connect. Thank you, jon |
||||
|
With help from Jon via e-mail this issue was easily resolved. It seems my data base was corrupt (loose bit somewhere) causing the problem. Jon recommended clearing the data base and reloading the engine data and lash ups which solved the problem. Many thanks to Jon for his help with this.
Jim London |
||||
|
| Previous Topic | Next Topic | powered by eve community |
| Please Wait. Your request is being processed... |
|
The O Gauge Railroading On-Line Forum
Lionel TMCC and LEGACY
Legacy Scrolling/Train Data Problem-ISSUE RESOLVED
