I thought so too, just wanted to get it from the Horse's Mouth. 
This was kept in the read me in case anyone needed to upgrade their software up to version 1.60. Just to be clear the 1.61 does not erase the roster. Upgrading from 1.2 erased the roster as the database was reconfigured. Since 1.3 no database changes have required the roster to be erased.
Mopac01, The reefer is on a different ID than the locomotive, so this is not applicable to the issue as it does not know the engine ID of the TMCC locomotive and cannot change the settings.
Lionel Dean posted:Mopac01, The reefer is on a different ID than the locomotive, so this is not applicable to the issue as it does not know the engine ID of the TMCC locomotive and cannot change the settings.
Dean,
But it does know the engine ID of the TMCC locomotive if you create a TRAIN as indicated for best operation in the sound reefer's manual. In establishing the TRAIN you've telling it the engine ID of (in my case) the TMCC engine and the ID of the additional unit in the consist which in this case is the ID of the sound reefer. And once I do this, accessing the sound reefer with the CAB2 via the TrainLink button immediately changes my TMCC Challenger's type and sound settings to Legacy ones which renders the TMCC Challenger uncontrollable since the Cab2 has suddenly started sending Legacy commands to it. Even the Cab2 button icons are changed. If I address the engine by it's ID and go into Info and change it back to a TMCC engine and Railsounds it works fine with the Cab2 UNTIL I address the sound reefer via TrainLink at which point the TMCC Challenger I've linked with the sound reefer via a TRAIN gets it's Cab2 settings changed again and becomes inoperable. (CORRECTION - Not inoperable just unaccessible. If it's going around the track the engine continues to do so - I just can't send it any more commands. Or more precisely I CAN send it commands it's just that what the Cab2 is sending is now Legacy commands and since it's a TMCC engine it doesn't understand those commands which means I've "lost control" of the engine.)
Could the instructions be incorrect in telling you to use the Cab2 "TrainLink" for commands to access the reefer when it is in a train pulled/pushed by a TMCC locomotive since that locomotive will not respond to the "TL" commands when you toggle? At least it seems the "TL" you are doing is not returning to TMCC mode. Interested as a friend is getting one of these as a gift from his wife. No manual on the website?
Mopac01,
Glad to help, would you please give us the SKU of the "sound reefer" car that has the IR transmitter you are pairing with the TMCC Challenger.
Thanks,
SantaFeFan posted:Mopac01,
Glad to help, would you please give us the SKU of the "sound reefer" car that has the IR transmitter you are pairing with the TMCC Challenger.
Thanks,
The sound reefer doesn't have an IR transmitter. It's simply causing a similar type of issue in terms of a Legacy device interacting with a TMCC device and changing the Cab2 settings of the Legacy device (correction - changes the settings of the TMCC device).
The sound reefer is the one sound reefer in the 3 pack PFE boxcar set that just shipped at the end of September, specifically Lionel 6-83545. The manual (attached) on page 9 indicates "For best operation, your VISION Reefer car should be assigned to a Train. Be sure it has a different engine ID from any active locomotives on your layout." I've followed the instructions to build the train with a TMCC Lionmaster Challenger (that has always operated without issue with my Cab2) and the PFE sound reefer. Building the Train as specified on page 9 of the instructions works just fine and I get confirmation sounds from both the Challenger and the sound reefer. But, similar to the sensor track issue in this thread (which I also started BTW) what can only be a programming issue in the Cab2 causes the TMCC engine's database settings to get changed when the sound reefer is accessed via the Cab2. There is simply no other explanation that a programming bug causing this.
Attachments
Files (1)
mopac01 posted:SantaFeFan posted:Mopac01,
Glad to help, would you please give us the SKU of the "sound reefer" car that has the IR transmitter you are pairing with the TMCC Challenger.
Thanks,
The sound reefer doesn't have an IR transmitter. It's simply causing a similar type of issue in terms of a Legacy device interacting with a TMCC device and changing the Cab2 settings of the Legacy device.
The sound reefer is the one sound reefer in the 3 pack PFE boxcar set that just shipped at the end of September, specifically Lionel 6-83545. The manual (attached) on page 9 indicates "For best operation, your VISION Reefer car should be assigned to a Train. Be sure it has a different engine ID from any active locomotives on your layout." I've followed the instructions to build the train with a TMCC Lionmaster Challenger (that has always operated without issue with my Cab2) and the PFE sound reefer. Building the Train as specified on page 9 of the instructions works just fine and I get confirmation sounds from both the Challenger and the sound reefer. But, similar to the sensor track issue in this thread (which I also started BTW) what can only be a programming issue in the Cab2 causes the TMCC engine's database settings to get changed when the sound reefer is accessed via the Cab2. There is simply no other explanation that a programming bug causing this.
Thanks, we agree the reefer does not have an IR transmitter; and sensor track is not germane to this discussion. OK, now to the concern you are asking about.
Please confirm the reefer and TMCC Challenger are on different TMCC IDs, and what ID they are set to. Please also let us know the TR ID you are building. Please also indicate the version of the Cab-2 and Base software you are using.
Thanks,
SantaFeFan posted:mopac01 posted:SantaFeFan posted:Mopac01,
Glad to help, would you please give us the SKU of the "sound reefer" car that has the IR transmitter you are pairing with the TMCC Challenger.
Thanks,
The sound reefer doesn't have an IR transmitter. It's simply causing a similar type of issue in terms of a Legacy device interacting with a TMCC device and changing the Cab2 settings of the Legacy device.
The sound reefer is the one sound reefer in the 3 pack PFE boxcar set that just shipped at the end of September, specifically Lionel 6-83545. The manual (attached) on page 9 indicates "For best operation, your VISION Reefer car should be assigned to a Train. Be sure it has a different engine ID from any active locomotives on your layout." I've followed the instructions to build the train with a TMCC Lionmaster Challenger (that has always operated without issue with my Cab2) and the PFE sound reefer. Building the Train as specified on page 9 of the instructions works just fine and I get confirmation sounds from both the Challenger and the sound reefer. But, similar to the sensor track issue in this thread (which I also started BTW) what can only be a programming issue in the Cab2 causes the TMCC engine's database settings to get changed when the sound reefer is accessed via the Cab2. There is simply no other explanation that a programming bug causing this.
Thanks, we agree the reefer does not have an IR transmitter; and sensor track is not germane to this discussion. OK, now to the concern you are asking about.
Please confirm the reefer and TMCC Challenger are on different TMCC IDs, and what ID they are set to. Please also let us know the TR ID you are building. Please also indicate the version of the Cab-2 and Base software you are using.
Thanks,
The TMCC Lionmaster Challenger is Engine ID 83 (generally I use the last 2 digits of the number of the rolling stock/engine). I'm not at home at the moment and don't remember the Engine ID of the reefer, except I'm pretty sure it's whatever the last 2 digits is of that reefer's number. I know for sure it's NOT the same (83) as the Challenger's ID. The TR ID I was building was 9 if I remember correctly. (I erased it when it became clear - to me anyway - there was a software bug here.) I believe I'd tried a two digit TR ID initially (11?) but didn't get a response from the Challenger (horn/whistle blast), but then figured the Challenger as a TMCC engine might not be able to respond to something higher than a single digit TR ID. So I moved to 9. And when I built the TR with ID 9 I DID get a horn/whistle confirmation from the TMCC Challenger and some sort of sound confirmation from the reefer as well. My Cab2 and base are both at 1.60. The update to 1.61 on my Cab2 will have to wait until I'm at home.
I just took sensor track and sensor cars off my want list. That takes care of that. Now an appointment with the eye doctor to get the eyes uncrossed.
We have tried to create your failure, with the same setup and ID setting you indicated, and with V1.60 on the Cab-2/Base. We do not have any problem as you describe your setup. Perhaps you should clear the engine record on ID #83 and the engine record for the Vision Reefer(ID??). Try adding them back into a new Train (9 or less as this is a TMCC loco) and let us know your results.
Thanks.
SantaFeFan posted:We have tried to create your failure, with the same setup and ID setting you indicated, and with V1.60 on the Cab-2/Base. We do not have any problem as you describe your setup. Perhaps you should clear the engine record on ID #83 and the engine record for the Vision Reefer(ID??). Try adding them back into a new Train (9 or less as this is a TMCC loco) and let us know your results.
Thanks.
Just so we're all on the same page, what steps to completely clear the engine record on ID 83? I've never gotten rid of any engines or cars with engine IDs (like the Crane/Boom cars) before and want to make sure it is completely "gone."
Bring up # 83 under ENG, ACC, or whatever you are trying to use, press info and scroll with the big red knob to "clr". Press the button under that.
BTW, if you have something stored at a certain item/address and your sensor track won't record a new engine as it rolls over, you may have to clear that item/address. Then it will record. Ask me how I know that...
SantaFeFan posted:We have tried to create your failure, with the same setup and ID setting you indicated, and with V1.60 on the Cab-2/Base. We do not have any problem as you describe your setup. Perhaps you should clear the engine record on ID #83 and the engine record for the Vision Reefer(ID??). Try adding them back into a new Train (9 or less as this is a TMCC loco) and let us know your results.
Thanks.
One other thing that just came to mind, although I haven't specifically called attention to it above. Engine 83 is the TMCC Lionmaster Challenger AND I HAVE A SENSOR CAR (the REA one) set for 83 as well, plus the sound reefer. I'm wondering if the bug with the TMCC engine and sensor car was manifesting itself when ANYTHING legacy was getting accessed - sensor track OR sound reefer?? Hmmmm I will update the Cab2 to 1.61 then retry creating the train with Engine 83 and the sound reefer with the sensor car still in the consist as well. If that still exhibits the TMCC engine settings getting changed to Legacy then I'll try completely deleting Engine 83, the sound reefer and the sensor car and starting over.
mopac01 posted:SantaFeFan posted:We have tried to create your failure, with the same setup and ID setting you indicated, and with V1.60 on the Cab-2/Base. We do not have any problem as you describe your setup. Perhaps you should clear the engine record on ID #83 and the engine record for the Vision Reefer(ID??). Try adding them back into a new Train (9 or less as this is a TMCC loco) and let us know your results.
Thanks.
One other thing that just came to mind, although I haven't specifically called attention to it above. Engine 83 is the TMCC Lionmaster Challenger AND I HAVE A SENSOR CAR (the REA one) set for 83 as well, plus the sound reefer. I'm wondering if the bug with the TMCC engine and sensor car was manifesting itself when ANYTHING legacy was getting accessed - sensor track OR sound reefer?? Hmmmm I will update the Cab2 to 1.61 then retry creating the train with Engine 83 and the sound reefer with the sensor car still in the consist as well. If that still exhibits the TMCC engine settings getting changed to Legacy then I'll try completely deleting Engine 83, the sound reefer and the sensor car and starting over.
Thanks for that important piece of information! The issue you are experiencing has absolutely nothing to do with your vision Reefer car. The problem is your IR Sensor Car, and version 1.61 of the Cab-2 code will solve your issues.
V1.61? Missed that. I see it on the Lionel site but a few posts ago I only saw 1.60 mentioned. Interesting and thanks for the heads up!
MartyE,
It was announced a few hours earlier in this thread by Lionel Dean, if you want to read the post and haven't yet seen it.
And holy cow he did. Thanks! Didn't go back far enough.
Welcome to the forum Dean...you may regret signing up. LOL!
MartyE posted:And holy cow he did. Thanks! Didn't go back far enough.
Welcome to the forum Dean...you may regret signing up. LOL!
Dean may regret signing up, but WE certainly won't regret Dean signing up! Welcome Dean. I for one am thrilled you're here.
SantaFeFan posted:mopac01 posted:SantaFeFan posted:We have tried to create your failure, with the same setup and ID setting you indicated, and with V1.60 on the Cab-2/Base. We do not have any problem as you describe your setup. Perhaps you should clear the engine record on ID #83 and the engine record for the Vision Reefer(ID??). Try adding them back into a new Train (9 or less as this is a TMCC loco) and let us know your results.
Thanks.
One other thing that just came to mind, although I haven't specifically called attention to it above. Engine 83 is the TMCC Lionmaster Challenger AND I HAVE A SENSOR CAR (the REA one) set for 83 as well, plus the sound reefer. I'm wondering if the bug with the TMCC engine and sensor car was manifesting itself when ANYTHING legacy was getting accessed - sensor track OR sound reefer?? Hmmmm I will update the Cab2 to 1.61 then retry creating the train with Engine 83 and the sound reefer with the sensor car still in the consist as well. If that still exhibits the TMCC engine settings getting changed to Legacy then I'll try completely deleting Engine 83, the sound reefer and the sensor car and starting over.
Thanks for that important piece of information! The issue you are experiencing has absolutely nothing to do with your vision Reefer car. The problem is your IR Sensor Car, and version 1.61 of the Cab-2 code will solve your issues.
I've upgraded the Cab2 to 1.61 (which thanks to the LCS WiFi module is a LOT slicker and easier than before). And everything seems to be working great! It was still odd that, as another poster earlier in the thread experienced, the TMCC Challenger didn't seem to have a problem with the sensor track on it's own (although his other TMCC engines did). As long as I didn't make a Train involving the TMCC Challenger and the Vision sound reefer the sensor car set to the same ENG ID as the TMCC Challenger didn't seem to impact the TMCC Challenger. I had made a Type 2 recording on the sensor track and on it blew the Challenger's whistle and activated a signalman car. That recording "played" whenever the sensor car behind the Challenger crossed the sensor track without impacting the Challenger's Cab2 settings. But add in the TRain with the Vision sound reefer and using TrainLink to access the sound reefer DID change the Challenger's Cab2 settings to Legacy. However, since upgrading the Cab2 to 1.61 everything seems to work as one would expect and as described in the manual.
After applying 1.61 I followed the instructions on the sensor car to use TxIR (to ensure the locking mentioned in the 1.61 readme file took place). I then created Train 9 with the TMCC Challenger and the Vision PFE sound reefer. Now accessing the sound reefer via TrainLink has no effect on the TMCC/Railsounds settings on the Challenger. I then made a Type 2 sensor track recording while addressing the Challenger as ENG 83, again blowing the Challenger whistle and activating a signalman car in the consist. Interestingly enough if I stop the Challenger then readdress it as TR 9 and take it (with the sensor car trailing) across the sensor track the recording doesn't play. But stop TR 9 and readdress it as ENG 83 and go across the sensor track (same direction in each example) and the recording plays. I didn't expect this behavior since it's the same physical engine and trailing sensor car in both cases but it's actually quite cool that it makes such a granular distinction.
I really appreciate the help on this. It's really cool to be able to use a 16 year old TMCC engine with a brand new sensor car and sound reefer and pull it all together with the Cab2 and LCS.
Lionel Dean posted:Hello everyone.
Engineering has come up with a fix for the issue with SensorCar and TMCC locomotives. I have placed the software upgrade on our website www.lionel.com in SUPPORT https://www.lionelsupport.com/service-documents/
The download is # 71-4295-505 Legacy Cab-2 Software Version 1.61.
This fix addresses the issue with Cab2 and SensorCar when used with a TMCC locomotive. Please note that after installing the update your Cab2 will show version 1.61. There is no base update necessary. Cab2 version 1.61 will work with Legacy Base version 1.60
For more detailed information please see the read me file in the download.
Thank you, Dean
I have had a really busy work week so far so when I saw this thread had some updates you can imagine I was very excited to read this and try the new Cab software. I downloaded it and updated my Cab module over the WiFi and then updated my layout Cab2. I then tried out programming the sensor cars with the 2 TMCC locomotives, one Lionel and one Atlas, and I must say everything worked perfect! I am just so tickled and want to say thank you to Dean and everyone else at Lionel for looking at this and creating a fix. It is just really nice to know I am not completely crazy and to see the great support out there for the Legacy line.
Thank you again!
