If you already have the 990 Legacy command and LCS setup is there anything that the CAB3 can add? Other than the app.
Original Post
Replies sorted oldest to newest
The Cab3 App can switch between Bluetooth and Base3 control modes for running engines within the same App. With the older Apps and 990 base, you would need to swap between the LionChief and iCab apps. The Cap3 App is available on both Android and iOS and can be used without a Base3 while the old Apps are available for iOS (Apple) devices only. .
The Cab3 (Bluetooth mode) can connect to 3 engines at a time while the LionChief App connects to a single Bluetooth engine at a time.
@Tracker John posted:The Cab3 App can switch between Bluetooth and Base3 control modes for running engines within the same App.
Interesting question. Can you switch between BT and Legacy control in the same running session? If you're running a couple of BT locomotives, can you turn on a Legacy engine track and jump over to BASE3 and run that one without interrupting the running of the BT engines?
@gunrunnerjohn posted:Interesting question. Can you switch between BT and Legacy control in the same running session? If you're running a couple of BT locomotives, can you turn on a Legacy engine track and jump over to BASE3 and run that one without interrupting the running of the BT engines?
It is my understanding that is the case. I'll let you know. Has anyone entered a Bluetooth engine into Base3 yet to use with the Cab2 or Cab3App in Base3 mode? When I had the unit for the Virtual Legacy Meeting this was an awesome time using a Cab2 to run my Star Trek starter set.
The Cab3 switches between Bluetooth and Base3 modes allowing (as I just tested) two Bluetooth and a TMCC engine to be controlled. I'm on my switching layout with short leads so latency matters else bad things happen. Swiping among the Bluetooth-connected engines was seamless. When I went to the Base3 tab, the Cab3 had to reconnect to the base and the engine selection always defaulted to the last Legacy engine run from the base. The TMCC engine ID needed re-selecting, added more delay and aggravation.
Update: Once I corrected some fat finger issues and got the Base3 roster corrected, the swap from Bluetooth into Base3 mode went much better. There is still the delay for the App3 to connect to the base, but the TMCC engine remained as the selected ID.
