Using Bluetooth device independently of Cab2 Base

No problem here.  I just fired up a Legacy, a TMCC, and a LC+ 2.0 locomotive at the same time.  I was running the LC+ 2.0 from the Orange LC Universal remote and the Legacy and TMCC locomotives using the CAB2.

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

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.

Hm.  I wonder if this feature could be added by a firmware version update (or with the BASE-3 when it is released)?

@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.