Skip to main content

I have an all command layout.  I run nothing conventionally.  I have a Pennsylvania LionChief Plus 2.0 Berkshire that came as a set with passenger cars.  One of the cars is an announcement coach from wits trip dialogue.  I run the locomotive in TMCC mode with my Cab2 system.  The announcement coach will not announce.  If I run the locomotive with Bluetooth the announcement coach works perfectly.  The issue is I cannot get the locomotive and announcement coach to connect to Bluetooth unless I cut the power to my Cab2 base impeding the operation of my other lock-in my layout.  Is there a way I can have both Bluetooth and my Legacy Locomotives running at the same time?

Original Post

Replies sorted oldest to newest

It appears that the announcement feature can only be activated either with the Universal Remote or the BT app, so assigning the engine a TMCC address will not help.

This from the Lionel website:

ANNOUNCEMENT COACH FEATURES:

  • Additional train announcements activated with dialog button on Universal Remote or LionChief® App


You can run that engine using the BT app and get the announcement feature, but the OP seems to have an issue with running that engine with BT (to get the announcement) and any another command engine with the Cab2 at the same time but, as I understand it, you should be able to run both at the same time. I don't believe the command signal should interfere with the BT signal.

Obviously, he could also try running the Pennsy 2.0 engine with a Universal Remote and see if interference with the Cab2 still exists.

@Richie C. posted:

It appears that the announcement feature can only be activated either with the Universal Remote or the BT app, so assigning the engine a TMCC address will not help.

This from the Lionel website:

ANNOUNCEMENT COACH FEATURES:

  • Additional train announcements activated with dialog button on Universal Remote or LionChief® App


You can run that engine using the BT app and get the announcement feature, but the OP seems to have an issue with running that engine with BT (to get the announcement) and any another command engine with the Cab2 at the same time but, as I understand it, you should be able to run both at the same time. I don't believe the command signal should interfere with the BT signal.

Obviously, he could also try running the Pennsy 2.0 engine with a Universal Remote and see if interference with the Cab2 still exists.

Yes, I know.  The issue is I’ve assigned a TMCC code to the locomotive and it will not respond to a Bluetooth signal UNLESS I cut power to the Cab2 base.  

@RixTrack posted:

Have you ever run the LC+ 2.0 in TMCC?  Have you assigned it a TMCC address?

I run all my LC+2.0 locomotives with TMCC, I only occasionally test when a question comes up with BT.  I find the LC+2.0 to be rock-solid with TMCC, not so with BT.

@RixTrack posted:

Yes, I know.  The issue is I’ve assigned a TMCC code to the locomotive and it will not respond to a Bluetooth signal UNLESS I cut power to the Cab2 base.  

The fact that it has a TMCC address shouldn't affect it's ability to run with BT in any manner, and it certainly doesn't for my layout with the Legacy command base active and other TMCC/Legacy stuff running.

Last edited by gunrunnerjohn

Add Reply

Post

OGR Publishing, Inc., 1310 Eastside Centre Ct, Ste 6, Mountain Home, AR 72653
800-980-OGRR (6477)
www.ogaugerr.com

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