Lionel is no stranger to the world of smart device applications. The iCab and LCS APPs gave users smart device control of Legacy and TMCC products using the LCS Wi-Fi module and a Legacy Base2. The LionChief APP has given direct Bluetooth control to users, allowing basic controls of everything from a LionChief locomotive up to a Bluetooth-equipped Legacy locomotive. We thought, why not combine them?
This APP offers two modes that can operate concurrently. The Bluetooth tab will feel familiar to the LionChief APP, with all-new features being included. The Command Base tab connects to the new Base3 and gives full control of all Lionel command types and products. Full control of your railroad empire is now in the palm of your hand.
We have just released a MAJOR update to the Cab3 app! This release re-introduces VSR (Voice Streaming and Recording) for VSR capable engines on the Bluetooth side of the app, and shifts the user interface on the Base3 side of the app to more closely resemble a Cab2 (hardware remote) experience.
IMPORTANT:Please make sure that you have updated your Base3 Firmware to at least v1.35. Running Cab3 v2.0 with older firmware may result in odd behavior and certain functions not performing as intended!
Cab3 Version 2.0 for iOS, Android
Please explore this site for more information on Cab3 Version 2.0!
Improved stability of app when updating firmware on a Base3. This was more of an issue on Android devices, but could have affected iOS devices as well.
When canceling a device refresh, all devices found so far will be shown.
HORN label will dynamically change to WHISTLE when controlling a steam engine.
Changes for Android:
When canceling a device refresh, all devices found so far will be shown.
HORN label will dynamically change to WHISTLE when controlling a steam engine.
Fixed potential crash on startup when running on Android 10 or earlier.
Improved stability when switching quickly between tabs
Fixed issue where some engines might not have their images displayed properly
Fixed issue where double-tap to return to previous engine may not have been working properly.
NOTE: Just like on a Cab2 remote, in order for an engine to be considered a “previous engine” you must have “started it up”. Just selecting an engine without startup will NOT cause that engine to be considered the “previous engine”
Future features (and features from Cab3 Version 1 that are not available yet):