CAB3 Review - Bluetooth edition

I did the same thing when swiping up on that screen but once you know about it I was just a little more Careful.

One other issue I had when running my Alco S2  If the engine was traveling forward at a mis speed hitting reverse  The Engine stops and goes in reverse    The throttle says ) but the engine takes off at the speed I was going forward

Funny, when I tried the CAB3, I did exactly the same thing and the test engine took off like a rocket!  The bummer was, I was on the other screen then and I had to get back to slow it down.  It was on a wide curve and going up a grade, so it didn't depart the track so no harm done, but it did give me a jolt.

@Joe Fermani posted:

I downloaded the new Cab3 app to try out on my bluetooth locs.  Overall impression is good.  The app does have a few issues that I hope Lionel will correct in a future version.  I tested the app using my Legacy PRR S1.  I picked this loc because it will sometimes have issues being controlled using the LionChief app.  Due to the loc's large size and all the diecast metal, the LionChief app sometimes loose the signal from the engine.  The engine would then stop and I would have to re-link the engine to the app.  I wanted to see if Lionel was able to improve this with the new Cab3.

The search button found the loc right away.  I was able to link it up and address the engine without issues.  I then proceeded to do a test run around the layout to see how well it performed.  About half way around the layout, a message popped up on the app that it has lost signal and was attempting to reconnect.  It reconnected automatically and the engine never stopped.  This new retry feature when signal is lost is a great feature.  I was able to successfully control the engine via bluetooth without issue.  The Cab3 app had to re-connect several times while running but its retry feature worked well and the engine never stopped liked it did under the LionChief app.  Other Lionel Bluetooth engines I have do not have this problem.  The speed control seems to have a finer control over the engine speed as compared to the LionChief app.  I could really make the S1 creep just like I do when using my Cab2.

The slider control for the speed allows the user to slide the speed up and down.  Users can also just tap a spot on the speed control and it will automatically set the slide to where you touched.  The other controls on the main screen all work well - horn/bell/crewtalk/direction/voice commands.  All function as expected.

If you swipe up on the app, the next screen displays.  On this screen, users can turn the smoke on or off, set a speed limit, set the momentum, change the app theme.  This is where I encountered my first problem.  When you go to swipe up, if you are not careful where you swipe, you could swipe the speed control to max while trying to change screens.  I think it would be better to get rid of swiping and have a button to click to get to the next screen.  This could prevent accidental speed changes.  At least going back to the prior screen its a swipe down, at worst you set the engine speed to 0.   The theme options are a nice touch especially if you have kids using the app.  It adds an extra element of fun while controlling the trains.  What is missing on this screen is a volume control.  LionChief app allowed the user to set the volume on the bell and whistle.  Users could also select what bell/whistle they wanted.  You don't have that ability in the app.  Lionel should really add that feature back - at least the volume control.

The only other issue I found using the app is the phone timing out.  I have my phone set to low inactivity so the screen turns off under a minute.  This required me to keep tapping the app to keep the phone awake to control the trains.  Lionel should add an option to the app to keep the phone awake while the app is in use.  This would allow users to keep the phone active the entire time you are running trains.

Overall, I think Lionel did a nice job on the app.  The few issues i found are not show stoppers but it would greatly improve the function of the app.  Of all issues I found, the swipe up and down to get to the other screens and possibly messing up your speed setting is the most critical.  I can see kids swiping the wrong spot and sending a loc flying off the layout when they wanted to get to the smoke option.  Until Lionel fixes these issues, I still see the LionChief being used as I like the volume control and the whistle/bell selection options.

I look forward to seeing how the Cab3 works. @Dave Olson

The volume control is on the app, when you are on the home page just swipe right. It's improved, you pick bell and horn/whistle by pushing numbers 1 through 5 instead of using a slide control.

@GAN Railroad posted:

The volume control is on the app, when you are on the home page just swipe right. It's improved, you pick bell and horn/whistle by pushing numbers 1 through 5 instead of using a slide control.

Thanks for the tip!  I completely missed that.

Just tried it on my 1988 SD70 from 2023 with bluetooth.     

One time the horn stayed on and would not stop until I killed the app.   

Bell shows active, blue button, but is not ringing.   Selecting which bell to use plays the bell.  Cannot get the bell out of blue/active/unavailable mode.   

Hit the kill button, train stopped, but then started again with the slider at 0.   Hitting it a second time stopped the train. 

Crew talk showed blue/not available.   Had to restart app to get it working.

I am severely concerned that the app is in this state after years of promise and reported testing.

Will try to figure out how to turn in bugs and report it all.

@VHubbard posted:

Just tried it on my 1988 SD70 from 2023 with bluetooth.     

One time the horn stayed on and would not stop until I killed the app.   

Bell shows active, blue button, but is not ringing.   Selecting which bell to use plays the bell.  Cannot get the bell out of blue/active/unavailable mode.   

Hit the kill button, train stopped, but then started again with the slider at 0.   Hitting it a second time stopped the train.

Crew talk showed blue/not available.   Had to restart app to get it working.

I am severely concerned that the app is in this state after years of promise and reported testing.

Will try to figure out how to turn in bugs and report it all.

@Dave Olson did a video tutorial on the app and had mentioned that they only had a few brands of phones to test with. He assumed and expected that bugs will show up on different devices than used in development.

You can send an email to TalkToUs@lionel.com