Skip to main content

LCS and Z-Stuff DZ-2500 switch machines; if the switch machine is activated via non-derailing function it will not show the change on the LCS app.  There were some posts a while back that discussed a work around*, but I would like to know if Lionel is going to address this within their LCS products.  

Marty, I'll be there.  Thanks for putting this together again.

*Used another relay, but never read anything from anyone that said they got it to consistantly work.   

Last edited by CAPPilot

Thanks Marty. I am glad you are taking the effort to make this a better hobby.  I am sorry I cannot make it will be on the road traveling to York at that time.

1) This product is amazing why can't we have it for Lionel engines? The technology can be expanded to use only selected engines that are running on the layout to avoid multiple sounds. Talking about ground breaking sound effects!

 

 

bli_rollthun_kit_illustrationbli_rollthun_kitMRR020116_MPR_BLIRollThunder_MV0618

 

 

12)  Use a small receiver to activate selected couplers in Key freight or passenger cars. This would be a keeper for small shunt puzzles on my layout say the Inglenook siding puzzle of 8 cars. Of course the couplers would respond to the Legacy remote.

I believe LGB had developed this for their products?

 

maxresdefault

 

16) Is more of a Hot Box detector or axle detector with speaker and voice after cars are scanned.... its a random number generator for wheel faults, or for more realism,  a resistor can be located on the axel, and this one shows actually when it gets hot.

I am not sure who made these devices for HO layouts.

But maybe with the LCS sensor this could be activated and use feedback to the Legacy remote?

 

 

 

 

 

 

Attachments

Images (4)
  • bli_rollthun_kit_illustration
  • bli_rollthun_kit
  • MRR020116_MPR_BLIRollThunder_MV0618
  • maxresdefault

Hi Marty, Thanks for setting this up. 

I have had a issue ever since I got the LCS sensor track. It does not reliably trigger when crossed over by a IR equipped loco.

Jon Z,  sent me a lab tested sensor track that acts the same way. I even tried it on my LCCA/Lionel modular layout. The wiring on this layout is exactly to the modular specifications. And again it acts up.

There was talk from Jon Z that this was due to noise being picked up from the track. (This won't be solved by the little terminator that you can get for the unused PDI connector in the chain.)

Could you ask if any progress has been made on solving this? 

Also if anyone at the meeting has experienced the same issue?

There was talk of a shielded sensor track.

Many thanks

Nick Hannaford

Hi Marty,

to add to the remarks of Nick my two observations concerning the sensor track in operation:

- in more or less 95% cases  the direction arrow on the screen shows the wrong direction during the very first passing of an IR equipped engine; the following passings are indicated correctly

- after two or three days of non operating the layout, it can occur often that the sensor track looses the entered program and must be programmed again.

I have installed the Little terminator at the end of the chain.

Thanks and reagrds

Albrecht

Harvy posted:

Hi @MartyE,

I will not be attending.  Hopefully some year.  I do enjoy the videos though and appreciate your support of the LCS Partners. 

I would like to answer two of the questions from my point of view as it relates to my softwate.  I will not answer for Lionel.  I will only answer with your permission. 

If you send them to me I will make sure they are in the Q&A or you can add your answer when the summary is posted.  

MartyE posted:
Harvy posted:

Hi @MartyE,

I will not be attending.  Hopefully some year.  I do enjoy the videos though and appreciate your support of the LCS Partners. 

I would like to answer two of the questions from my point of view as it relates to my softwate.  I will not answer for Lionel.  I will only answer with your permission. 

If you send them to me I will make sure they are in the Q&A or you can add your answer when the summary is posted.  

I'll wait for the summary to be posted.

Thank you.

Hi Marty,

I will be there! Looking forward to my first TMCC/Legacy meeting .. been wanting to attend for a looong time ... chance to put the faces and names together and meet fellow Legacy afficianados.... 

Also my Legacy base and handheld need to be upgraded.. do I need to bring both of my Cab-2s or just one and the base??

thanks Marty... really looking forward to it!

 

RD posted:

Hi Marty,

I will be there! Looking forward to my first TMCC/Legacy meeting .. been wanting to attend for a looong time ... chance to put the faces and names together and meet fellow Legacy afficianados.... 

Also my Legacy base and handheld need to be upgraded.. do I need to bring both of my Cab-2s or just one and the base??

thanks Marty... really looking forward to it!

 

You can do it a couple of ways.  If you have black modules you can bring those and we will create a Base upgrade module and Cab2 upgrade module and test them on my system.  You can take those home and do your base and remotes at home.  If you prefer to bring your base and 2 remotes to York we can use my modules I carry with me to bring you up to Base V1.60 and Cab2 V1.61.

Last edited by MartyE
MartyE posted:
RD posted:

Hi Marty,

I will be there! Looking forward to my first TMCC/Legacy meeting .. been wanting to attend for a looong time ... chance to put the faces and names together and meet fellow Legacy afficianados.... 

Also my Legacy base and handheld need to be upgraded.. do I need to bring both of my Cab-2s or just one and the base??

thanks Marty... really looking forward to it!

 

You can do it a couple of ways.  If you have black modules you can bring those and we will create a Base upgrade module and Cab2 upgrade module and test them on my system.  You can take those home and do your base and remotes at home.  If you prefer to bring your base and 2 remotes to York we can use my modules I carry with me to bring you up to Base V6.0 and Cab2 V6.1.

I always thought Lionel's recommendation was the base and the remote should have the same version of the firmware.  Why is there a new version for the Cab-2 and not the base?

The last update was for the CAB2 only to fix an issue with the sensor boxcar. The base version and it's software didn't change. That is why the base is 1.6 and the Cab 2 is now 1.61.

From the 1.61 Upgrade Read Me file...

Lionel LEGACY V1.61 System Upgrade

Thank you for downloading the Lionel LEGACY V1.61 upgrade. The upgrade includes the following files:

filename description
-----------------------------------
ReadMe_LEGACYv161.txt this file
CAB2-v161.cab2 the CAB internal software upgrade code (LEGACY System Utility required to load)

No Legacy Base code change is required for this upgrade. Use Legacy Base code version 1.60 with legacy CAB code 1.61.

The change made from the previous version CAB code (v1.6) is as follows:
--------------------------------------------------------------------------

* Fixes an issue with CAB2 and SensorCar when used with a TMCC engine. This fix allows owners of older TMCC locomotives to use SensorCar and SensorTrack to create their own custom recordings, one in each direction of travel.

Problem: With this combination of products and CAB2 version 1.60, "Control Type" settings were switched back to Legacy (LEG) each time SensorCar rolled over SensorTrack. This caused operational problems for the TMCC locomotive because CAB2 was sending commands the older-style locomotive could not understand.

Fix: Version 1.61 of the CAB2 software "locks" the legacy Base record when the "TxIR" button is pressed during SensorCar setup. The "lock" means that SensorCar will NOT change the engine name, control type, etc., when it rolls over a SensorTrack. Be sure to verify (or if not, change) the engine ID in question to CAB1 or TMCC control type after pressing TxIR.

To remove this lock, CLEAR the engine ID in question via CAB2 and SensorCar will again be free to modify that engine ID record.

This update doesn't change the way you program or use your SensorCar. The existing owner's manuals are still correct; no new manuals will be released for this version.

 

Last edited by MartyE
MartyE posted:

I also edited my post to correctly identify the versions as Base 1.6 and Cab2 V1.61.  Sorry if there was any confusion.

Marty,this is going to sound stupid but how so you see if that's the version you have? (It doesn't seem to come up on the screen when you power it up.)

"There are no stupid questions, just stupid people."- Mr. Garrison, South Park Elementary School.

MartyE posted:

The last update was for the CAB2 only to fix an issue with the sensor boxcar. The base version and it's software didn't change. That is why the base is 1.6 and the Cab 2 is now 1.61.

From the 1.61 Upgrade Read Me file...

Lionel LEGACY V1.61 System Upgrade

Thank you for downloading the Lionel LEGACY V1.61 upgrade. The upgrade includes the following files:

filename description
-----------------------------------
ReadMe_LEGACYv161.txt this file
CAB2-v161.cab2 the CAB internal software upgrade code (LEGACY System Utility required to load)

No Legacy Base code change is required for this upgrade. Use Legacy Base code version 1.60 with legacy CAB code 1.61.

The change made from the previous version CAB code (v1.6) is as follows:
--------------------------------------------------------------------------

* Fixes an issue with CAB2 and SensorCar when used with a TMCC engine. This fix allows owners of older TMCC locomotives to use SensorCar and SensorTrack to create their own custom recordings, one in each direction of travel.

Problem: With this combination of products and CAB2 version 1.60, "Control Type" settings were switched back to Legacy (LEG) each time SensorCar rolled over SensorTrack. This caused operational problems for the TMCC locomotive because CAB2 was sending commands the older-style locomotive could not understand.

Fix: Version 1.61 of the CAB2 software "locks" the legacy Base record when the "TxIR" button is pressed during SensorCar setup. The "lock" means that SensorCar will NOT change the engine name, control type, etc., when it rolls over a SensorTrack. Be sure to verify (or if not, change) the engine ID in question to CAB1 or TMCC control type after pressing TxIR.

To remove this lock, CLEAR the engine ID in question via CAB2 and SensorCar will again be free to modify that engine ID record.

This update doesn't change the way you program or use your SensorCar. The existing owner's manuals are still correct; no new manuals will be released for this version.

 

Ah, got it.

Thank you.

MIKATT1 posted:
MartyE posted:

I also edited my post to correctly identify the versions as Base 1.6 and Cab2 V1.61.  Sorry if there was any confusion.

Marty,this is going to sound stupid but how so you see if that's the version you have? (It doesn't seem to come up on the screen when you power it up.)

"There are no stupid questions, just stupid people."- Mr. Garrison, South Park Elementary School.

Once the cab2 and base are powered, push the CTC button on the cab2 and it will tell you what versions the base and the hand held are at. 

Last edited by MartyE

I won't be going to York, but I will be looking forward to your video and report from the meeting as usual. Also would like to thank you for doing all of this for those of us that can't attend. I really look forward to these (and all the other reports) twice a year just like you all that get to attend the York meets! Maybe someday I'll make it in person.

Well the meeting is pretty well set.  We have a lot of questions to cover, we'll review the Bluetooth App as it pertains to operating the new Legacy engines equipped with BLE, and Dave Olson will speak about a few of the new things Lionel has coming out as well as the BLE Legacy path.  Dean will also be there to answer CS questions as well as any other relevant questions.

As always we will have some flyers for the LCS Partners including eTrain and High Rail both we have shown at previous meetings.

I will post the agenda early next week and will have limited copies at the meeting. 

I will have all the needed parts to make modules or upgrade bases.  I hope to keep the end of the meeting right at 8:45 so everyone can get to the halls.

I will also have a question to the group that could be a very cool thing for us.

(Edited for clarity)

Last edited by MartyE

I posted the questions in pdf form that were submitted to Lionel.  Again we'll be recording the meeting and if all goes well should be available sometime the following week for viewing.  We had a lot of questions so I suspect that will be the majority of the meeting along with Dave Olson's small presentation and Q&A.  No big surprises but with the Legacy BLE we should be able to get some information from Dave on how this will change the way we operate our trains!

MartyE posted:

I posted the questions in pdf form that were submitted to Lionel.  Again we'll be recording the meeting and if all goes well should be available sometime the following week for viewing.  We had a lot of questions so I suspect that will be the majority of the meeting along with Dave Olson's small presentation and Q&A.  No big surprises but with the Legacy BLE we should be able to get some information from Dave on how this will change the way we operate our trains!

Hoping we finally get the auto whistle/horn Depart - Back-up - Crossing signal sequences like MTH has!

Add Reply

Post
×
×
×
×
Link copied to your clipboard.
×
×