Just received the set. Both of the Legacy PA AA set engines are powered and both have bluetooth.
I set unique engine ID for front engine, ran over sensor track and updated engine info in CAB2 yesterday. Then added trailing engine ID, etc to CAB2. Then lashed the two locos together via CAB2 into a unique train ID. Used the CAB2 settings to have the trailing engine running backwards in the lashup. Then used CAB2 to operate the lashed up engines around my oval track layout. All operated as expected.
Today I disconnected the Legacy command base from power, set my transformer to 18v track voltage, then turned on my universal remote, pressed one of the three engine selection buttons, and got the expected engine horn/blinking headlight on the leading engine. However, when I advanced the universal remote throttle, the engines were motionless. Then I noticed the trailing engine drive wheels turning with no engine movement. I turned off the universal remote and track power. The engines were driving against each other.
I then decoupled the forward engine and placed it on the same oval track several feet away still oriented relative to the trailing engine as if they were lashed up for dual engine operation back-to-back. Then I powered up the track, turned on the universal remote, pressed one of the three engine selection buttons, and again got the expected engine horn/blinking headlight on the leading engine. But this time, the forward engine did move forward ... and the trailing engine moved backward since they were not coupled to each other. So, clearly, each engine is responding to bluetooth. However, each engine travels forward when commanded via universal remote. In Legacy control, CAB2 enabled me to reverse the orientation of the trailing engine for lash up operation so when I command forward engine travel, the leading engine does travel forward while the trailing engine travels in backward direction relative to its orientation.
So, I thought perhaps I could get 'em synched using the Bluetooth LionChief App on my smart device. I fired up my smart device, turned on wifi, turned on bluetooth, then powered up the track to 18v, tapped the engine selection icon on my smart device LionChief App display, and the lead engine was acquired and its engine number board number was displayed on the app screen along with basic engine nomenclature. The trailing engine number was not displayed nor was it acquired as a unique engine on the app display. I checked horn/dialog/etc and all responded in the lead engine via the app. I then advanced the app throttle lever and the lead engine moved forward and the trailing engine moved backward just like when I used the universal remote.
This is the first lashed-together set of engines I have tried to use bluetooth with so it's a new experience to me. Again, works correctly in CAB2 legacy control. But no joy in bluetooth control.
So, here are my questions:
a. How do I get the two engines to move together in lashup configuration in the same direction via universal remote?
b. How do I get the two engines to move together in lashup configuration in the same direction via LionChief app?
c. How do I get the trailing engine to display its engine number board number on the LionChief app? Perhaps its a 'dumb' engine that does not display??
Tom
