@Sean's Train Depot posted:The hardware is super solid from what I can tell as I have been using it with my Cab2 remote and everything works perfectly like it did with my Base2 (Legacy Base).
So, for people just looking to replace an old/dead Legacy Base this is a perfect replacement.
The software defects that cause issues, do NOT happen when using the Remotes.
Ditto
Lionel is gathering information related to the issues with the Cab3 app. To my knowledge and in my own experience the Cab3 base works fine and I have not experienced problems with the hardware. Fortunately I have the Cab2 to use while Lionel sorts through the Cab3 app issues.
One feature that was helpful for me was the ability of the base3 to upgrade my Cab2’s from Version 1.2 to current version 1.74
When you do the upgrade the Base3 needs to be connected to the internet (not Access Point)?
@Jeff2035 posted:This may have been answered but we are already on page 7, so I may have missed it.
I can connect my Cab2 to the Base 3.
I can connect my iPhone to the Base 3 using the Access Point.
My router does not have WPS.
I have not been able to successfully connect using the instructions "JOIN to NETWORK Mode (no WPS)".
Does this work for anyone?
Jeff:
I was having the same issue. I could not connect the Base 3 to my home network. My problem was my iPhone was connected to my home network's 5GHz network. My internet service and Wi-Fi is from Xfinity. Xfinity Wi-fi has a 2.4 GHz network and a 5GHz network. The Base 3 is 2.4GHz. I had to log in to my Xfinity router and split the two networks, the 2.4GHz network and the 5GHz network. Once I split them I could see the 2.4GHz channel as an available network and I connected my iPhone to it. Once my iPhone was connected to the 2.4GHz channel I was then able to connect the Base 3 to my home network with my iPhone. I found this solution after hours of searching on the internet.
Neal Jeter
You only need the access point. Swipe up on the base3 app and tap the Cab2 v1.74 memory module and it will take you through the steps to use the memory module that comes with the base3 to do the upgrade.
Hooah!
Jim, that was easy.
My Cab2 is now upgraded to 1.74.
Thank you.
@Lionlman posted:Jeff:
I was having the same issue. I could not connect the Base 3 to my home network. My problem was my iPhone was connected to my home network's 5GHz network. My internet service and Wi-Fi is from Xfinity. Xfinity Wi-fi has a 2.4 GHz network and a 5GHz network. The Base 3 is 2.4GHz. I had to log in to my Xfinity router and split the two networks, the 2.4GHz network and the 5GHz network. Once I split them I could see the 2.4GHz channel as an available network and I connected my iPhone to it. Once my iPhone was connected to the 2.4GHz channel I was then able to connect the Base 3 to my home network with my iPhone. I found this solution after hours of searching on the internet.
Neal Jeter
Just posting Wi-Fi connection experience:
I could not get the base3 to connect to my wifi either. WPS did not work for me either. I tried connecting according to the documentation and the app would seemingly connect, but the orange Lionel light would never light up.
I had to set a static ip address in my Wi-Fi router and then manually set that ip address in the Wi-Fi connection settings in the cab3 app. This finally worked and worked consistently. Hope this helps some folks.
@rplst8 posted:@Lionlman posted:Jeff:
I was having the same issue. I could not connect the Base 3 to my home network. My problem was my iPhone was connected to my home network's 5GHz network. My internet service and Wi-Fi is from Xfinity. Xfinity Wi-fi has a 2.4 GHz network and a 5GHz network. The Base 3 is 2.4GHz. I had to log in to my Xfinity router and split the two networks, the 2.4GHz network and the 5GHz network. Once I split them I could see the 2.4GHz channel as an available network and I connected my iPhone to it. Once my iPhone was connected to the 2.4GHz channel I was then able to connect the Base 3 to my home network with my iPhone. I found this solution after hours of searching on the internet.
Neal Jeter
I'm not sure what you're try to tell me here... Are you thinking that an Xfinitiy router is not allowing communication between the two bands because that's not what's happening here.
Xfinity uses a combined SSID for both the 2.4 & 5 GHz networks. In the unsplit mode many (if not all) 2.4 GHz only devices like Doorbell cams and the BASE3 are unable to join the network as Jeff indicated. When you split the networks The BASE3 can join the newly created 2.4 network. Once this is done, you can leave your Xfinity WiFi router in split or unsplit mode and the BASE3 will still be able to connect to the router all the while Jeff's iPhone can be connected to either band and communicate to the BASE3. This is well documented on the xfinity forums.
I've helped quite a number of my friends with Xfinity routers in this very situation and when we're done their 5GHz connected laptop can still print on their 2.4GHz connected printer just fine. Xfinity is not creating separate LANs for the 2.4, 5, or Wired networks.
This is not a result of bug or error in the xfinity router but rather the way they intend the device to function. (backwards in my opinion)
@nightwolf00 posted:Just posting Wi-Fi connection experience:
I could not get the base3 to connect to my wifi either. WPS did not work for me either. I tried connecting according to the documentation and the app would seemingly connect, but the orange Lionel light would never light up.
I had to set a static ip address in my Wi-Fi router and then manually set that ip address in the Wi-Fi connection settings in the cab3 app. This finally worked and worked consistently. Hope this helps some folks.
My experience with the BASE3 is that the "L" will not illuminate orange until a CAB3 app makes connection to the device. The one at the club connects to the WiFi network but the "L" doesn't illuminate orange when that happens.
@H1000 posted:My experience with the BASE3 is that the "L" will not illuminate orange until a CAB3 app makes connection to the device. The one at the club connects to the WiFi network but "L" doesn't illuminate orange when that happens.
In my case, the cab3 app showed a green wifi icon (indicating a connection), but in reality wasn’t connected (orange L did not light up). I could not get a connection until I tried what I described in my previous post.
@nightwolf00 posted:In my case, the cab3 app showed a green wifi icon (indicating a connection), but in reality wasn’t connected (orange L did not light up). I could not get a connection until I tried what I described in my previous post.
Something similar was mentioned by some else where the CAB3 app mistook another device on his network for the BASE3. He had to do what you did as well to tell the CAB3 exactly where to look for the BASE3.
@H1000 posted:Something similar was mentioned by some else where the CAB3 app mistook another device on his network for the BASE3. He had to do what you did as well to tell the CAB3 exactly where to look for the BASE3.
Ah, I guess I missed that one when I was reviewing all of the posts. Hopefully Lionel improves this aspect in future updates as well as improving Powermaster control. Took me a while to figure that aspect out.
@nightwolf00 posted:Ah, I guess I missed that one when I was reviewing all of the posts. Hopefully Lionel improves this aspect in future updates as well as improving Powermaster control. Took me a while to figure that aspect out.
I think that was me. I still had the LCS WiFi module and the CAB3 App showed connected but the IP address was the LCS module instead of Base3. Once it was removed all connected fine.
I installed the Base3 and all my engines (25) from the early TMCC (Hudson Yellow Belly) to my latest the SF 2-10-10-2 and Strasburg 89. All my Vision line engines run as they should using the Cab3 App including the GG-1 (6-82751). Some quirkiness when using the Cabe3 App, but for the most part, I'm happy and waiting for the next upgrade. Some quick observations:
Now for the really odd specific happenings:
1: I power my tracks with a ZW-L in command mode. 4 tracks TR 1-4. I can use the Cab2 and Cab 1L to power up the tracks, NOT the Cab3 App. I have no idea why that's happening or how to do it. Whenever I hit the TR button it wants to build a train. Maybe the soft keys will be addressed at the next upgrade of the App.
I highly recommend keeping a Cab2 or Cab 1-L handy to take control.
2: I have the original Acela (6-18357). Even the doors work!!! I love it. It's in the Cab3 Base database and works as advertised with the Cab2 and Cab1L. I also used the iCab and the Acela responded as it should. The Cab3 App "she's a not so good." Sometimes it will start up…sometimes not. No icons are displayed at all, ever...
YIKES! As I was composing this message, I decided to walk through the issues one more time. I powered up the layout, Base3 is broadcasting. My Cab2 and Cab1-L connect. I powered up the tracks via the Cab2. With the Cab3 App, I could not address the Acela. I tried another engine that never caused an issue...nothing. The Cab2 and 1-L operated the engines as they should. Then I discovered the Cab3 App lost access to my entire engine roster! I also tried my iPad...the train database is there, but it's hit and miss whether I can start the Acela, or another reliable engine on a different track. Once again, Cab2 and 1-L work. I cycled the Base3 but the Cab3 App did not access my engine roster.
I deleted the Cab3 App from my iPhone and reinstalled it. The Roster returned.
3. I powered up the Acela on Track 1 and the DT&I 353 on Track 2. Once I started up the Acela and the DT&I the Acela stepped on the DT&I. The DT&I would not respond to commands, but the Acela did. It would shut down, but not the DT&I. I could restore control over the DT&I only after powering down Track 1, the track the Acela was on.
Although it presents challenges, I'm glad I added the Base3 and the Cab3 App. Keeps me involved!
MaryE, I still have my LCS WiFi module installed and I don't think it's causing these issues...???
@H1000 posted:I'm not sure what you're try to tell me here... Are you thinking that an Xfinitiy router is not allowing communication between the two bands because that's not what's happening here.
Xfinity uses a combined SSID for both the 2.4 & 5 GHz networks. In the unsplit mode many (if not all) 2.4 GHz only devices like Doorbell cams and the BASE3 are unable to join the network as Jeff indicated. When you split the networks The BASE3 can join the newly created 2.4 network. Once this is done, you can leave your Xfinity WiFi router in split or unsplit mode and the BASE3 will still be able to connect to the router all the while Jeff's iPhone can be connected to either band and communicate to the BASE3. This is well documented on the xfinity forums.
I've helped quite a number of my friends with Xfinity routers in this very situation and when we're done their 5GHz connected laptop can still print on their 2.4GHz connected printer just fine. Xfinity is not creating separate LANs for the 2.4, 5, or Wired networks.
This is not a result of bug or error in the xfinity router but rather the way they intend the device to function. (backwards in my opinion)
You're right, I misread his post.
It's interesting the Base3 can't join the network in combined SSID mode though. Some routers have a "Wi-Fi compatibility" mode that helps with older 2.4Ghz devices. I wonder if something is afoot there. Like the base link rate or something.
P.S. When routers do have network isolation enabled, certain things like printing may still work across bands because the devices are using a higher layer protocol like DLNA/UPnP or Apple Bonjour. Network isolation usually just keeps the Layer 2 separate.
I just pulled up the old iCab app it seems like you need to run the base in AP mode for it to connect, but when it does you’re on your way. It’s a much better interface than cab3 and very intuitive if you used any of the older remotes. I can also turn on my track power. If anyone figures how to make it connect to the base in “network” instead of “AP” please share!
@Kneissl posted:I just pulled up the old iCab app it seems like you need to run the base in AP mode for it to connect, but when it does you’re on your way. It’s a much better interface than cab3 and very intuitive if you used any of the older remotes. I can also turn on my track power. If anyone figures how to make it connect to the base in “network” instead of “AP” please share!
My iCab connected over network. Took about a minute but it did connect.
Even has the roster and any change I make on iCAB and vice versa shows up on CAB3 App.
I just discovered another issue with the cab3/ base3: The aux3 button to activate the funny cow sound does not work on my Lionel stock car set 2026850. Perhaps I am not doing something right.
Has anyone else had issues with the aux3 button on other items?
Having other odd signaling issues with CAB1/TMCC loco's. They dont wan to do things correctly or at all.
So for giggles, tried iCAB app and it works. So I guess I need to run multiple apps?
@MartyE posted:My iCab connected over network. Took about a minute but it did connect.
Even has the roster and any change I make on iCAB and vice versa shows up on CAB3 App.
Thanks! I gave up too early, it failed a couple times but once it found the base it seems to be quick now. iCab might be old but feels a lot more solid than the Cab3. I’m happier with this rig, no runaways, no constant crashing, works like you expect.
iCAB it is then. Just controlled all my TMCC/CAB1 stuff with it.
@Kneissl posted:Thanks! I gave up too early, it failed a couple times but once it found the base it seems to be quick now. iCab might be old but feels a lot more solid than the Cab3. I’m happier with this rig, no runaways, no constant crashing, works like you expect.
While iCab was good it lacks a lot of Legacy feature such as Train Brake, variable momentum, AUX3 plus more. I'm am sure that the CAB3 app will get the issues solved.
Cab3 app seems to also suffer from issues pairing with BTLE locos as well. The base pairs, loco acknowledges pairing, but you cannot control them, nor does it add them to the roster.
@ToledoEd posted:I installed the Base3 and all my engines (25) from the early TMCC (Hudson Yellow Belly) to my latest the SF 2-10-10-2 and Strasburg 89. All my Vision line engines run as they should using the Cab3 App including the GG-1 (6-82751). Some quirkiness when using the Cabe3 App, but for the most part, I'm happy and waiting for the next upgrade. Some quick observations:
- Direction icon sometimes works as it should. Mostly it doesn’t switch colors at direction change. This happened with most of my engines.
- When you change directions the engine may or may not stop. Sometimes, after sopping the engine will creep until you give it some throttle then throttle down to stop it.
- Not all icons activate features as they should
- Database update/engine add to Base3 database commands seem odd to me. When you add an engine your asked do you want to update the database Yes/No. My instinct was yes…wrong answer. It’s NO. Not sure if I don’t understand or there is something quirky about the software. Once I figured out I needed to say “NO”…problem solved.
Now for the really odd specific happenings:
1: I power my tracks with a ZW-L in command mode. 4 tracks TR 1-4. I can use the Cab2 and Cab 1L to power up the tracks, NOT the Cab3 App. I have no idea why that's happening or how to do it. Whenever I hit the TR button it wants to build a train. Maybe the soft keys will be addressed at the next upgrade of the App.
I highly recommend keeping a Cab2 or Cab 1-L handy to take control.
2: I have the original Acela (6-18357). Even the doors work!!! I love it. It's in the Cab3 Base database and works as advertised with the Cab2 and Cab1L. I also used the iCab and the Acela responded as it should. The Cab3 App "she's a not so good." Sometimes it will start up…sometimes not. No icons are displayed at all, ever...
YIKES! As I was composing this message, I decided to walk through the issues one more time. I powered up the layout, Base3 is broadcasting. My Cab2 and Cab1-L connect. I powered up the tracks via the Cab2. With the Cab3 App, I could not address the Acela. I tried another engine that never caused an issue...nothing. The Cab2 and 1-L operated the engines as they should. Then I discovered the Cab3 App lost access to my entire engine roster! I also tried my iPad...the train database is there, but it's hit and miss whether I can start the Acela, or another reliable engine on a different track. Once again, Cab2 and 1-L work. I cycled the Base3 but the Cab3 App did not access my engine roster.
I deleted the Cab3 App from my iPhone and reinstalled it. The Roster returned.
3. I powered up the Acela on Track 1 and the DT&I 353 on Track 2. Once I started up the Acela and the DT&I the Acela stepped on the DT&I. The DT&I would not respond to commands, but the Acela did. It would shut down, but not the DT&I. I could restore control over the DT&I only after powering down Track 1, the track the Acela was on.
Although it presents challenges, I'm glad I added the Base3 and the Cab3 App. Keeps me involved!
MaryE, I still have my LCS WiFi module installed and I don't think it's causing these issues...???
Excellent report Ed!!. Thanks for taking the time to do so. I'm sure it will be appreciated by many members.. 
@Stone Rhino posted:Cab3 app seems to also suffer from issues pairing with BTLE locos as well. The base pairs, loco acknowledges pairing, but you cannot control them, nor does it add them to the roster.
We added a Bluetooth LC engine without issue. We then commanded the engine to move forward around speed step 5, hit the direction button on the CAB2, scrolled the wheel to one speed step and the engine took off in reverse at speed step 6! The BASE3 stopped the engine with the direction command but didn't reset the speed to zero. So the next movement in reverse picked back up at speed step 5 plus the additional speedstep commanded.
@nightwolf00 posted:I just discovered another issue with the cab3/ base3: The aux3 button to activate the funny cow sound does not work on my Lionel stock car set 2026850. Perhaps I am not doing something right.
Has anyone else had issues with the aux3 button on other items?
I used the Aux 3 on engines that used that feature (Strasburg 90 Ghost whistle sequence) and it works fine.
I don't have that car, but check to verify it is programmed correctly in the base 3?
@Stone Rhino posted:Cab3 app seems to also suffer from issues pairing with BTLE locos as well. The base pairs, loco acknowledges pairing, but you cannot control them, nor does it add them to the roster.
I tried multiple engines with BT on both the BT side and Base3 side of the app and had no issues.
What side of app were you using? If it was Base3 side, did you use one of the reserved addresses for BT?
@Quarter Gauger 48 posted:Excellent report Ed!!. Thanks for taking the time to do so. I'm sure it will be appreciated by many members..
I'll have to test my Acela and see if I have same result, but just curious since a lot of people are keeping the 990 system stuff hooked up, you do disconnect the power to your Legacy base when trying to use the base3 correct? Just eliminating the obvious stuff.
One enhancement I'd like to see in the app is when you type in an Engine #, that you can just hit the Startup button and then it automatically moves to the Engine screen. I like the Startup button because it, starts up the sounds and lighting in sequence (Background sounds, Spin up sound, Headlight, Marker Lights, Cab Light, Smoke Unit). Right now, you enter an engine and tap Enter and then it moves to the Engine screen. You then can tap the R to startup background sounds, but it does not do the other stuff until you blow the whistle or do something else. Not as prototypical.
So, in the app for me, after I do the Enter and it moves to the Eng screen, I just tap engine again to do my preferred Startup button sequence.
@Sean's Train Depot posted:I'll have to test my Acela and see if I have same result, but just curious since a lot of people are keeping the 990 system stuff hooked up, you do disconnect the power to your Legacy base when trying to use the base3 correct? Just eliminating the obvious stuff.
Sean, first, thanks for posting excellent videos about implementing and using the Base3 and Cab3 App. Yes, I have disconnected the Base2. Found that out the hard way!😁. Reading the info on the Lionel site is important.
@Sean's Train Depot posted:I used the Aux 3 on engines that used that feature (Strasburg 90 Ghost whistle sequence) and it works fine.
I don't have that car, but check to verify it is programmed correctly in the base 3?
Thanks for the reply. I think it is programmed correctly. The quilling cow and the loading/unloading sounds work. I have it setup as freight sounds in the engine roster. Perhaps there is something I am missing?
@Quarter Gauger 48 posted:Excellent report Ed!!. Thanks for taking the time to do so. I'm sure it will be appreciated by many members..
Thanks, Ted. Once I’m comfortable with the Base3 and Cab3 App I intend to give Zack the Base2. He can’t wait!
@Sean's Train Depot posted:I tried multiple engines with BT on both the BT side and Base3 side of the app and had no issues.
What side of app were you using? If it was Base3 side, did you use one of the reserved addresses for BT?
Good morning Sean.
Yes. I used the pairing via base on channel #10. The loco stops making its "nobody controlling me" chirp which tells me its communicating. It just never shows up in roster (actually nothing does). The Cab3 app can directly control the loco via bluetooth.
So, just an FYI, I am running AP mode and never connected it to a PC. Is this where the mistake was made?
@Sean's Train Depot posted:I'll have to test my Acela and see if I have same result, but just curious since a lot of people are keeping the 990 system stuff hooked up, you do disconnect the power to your Legacy base when trying to use the base3 correct? Just eliminating the obvious stuff.
It would make sense to do this as you are trying to have two devices broadcast the control signal. For example, the TMCC/CAB1 base and Legacy CAB2 base. You cannot have the CAB1 base U-Post connected the same time the Legacy CAB2 base is connected; Hence the need for the serial cable to use the CAB1 and CAB2 to talk to trains at the same time.
@H1000 posted:We added a Bluetooth LC engine without issue. We then commanded the engine to move forward around speed step 5, hit the direction button on the CAB2, scrolled the wheel to one speed step and the engine took off in reverse at speed step 6! The BASE3 stopped the engine with the direction command but didn't reset the speed to zero. So the next movement in reverse picked back up at speed step 5 plus the additional speedstep commanded.
Unfortunately I do not have any CAB2 gear. The lack of availability and reasonable cost have kept it out of my reach.
@Stone Rhino posted:Good morning Sean.
Yes. I used the pairing via base on channel #10. The loco stops making its "nobody controlling me" chirp which tells me its communicating. It just never shows up in roster (actually nothing does). The Cab3 app can directly control the loco via bluetooth.
So, just an FYI, I am running AP mode and never connected it to a PC. Is this where the mistake was made?
No, AP mode is fine, that is just how your handheld device communicates with the Base3. The BT signal will come from the BT radio in the Base3 to the engine.
What engine is it?
So far, all my Lionchief BT engines showed up on the Base3 side correctly when programmed in that reserved range.
@Sean's Train Depot posted:No, AP mode is fine, that is just how your handheld device communicates with the Base3. The BT signal will come from the BT radio in the Base3 to the engine.
What engine is it?
So far, all my Lionchief BT engines showed up on the Base3 side correctly when programmed in that reserved range.
This set:
http://www.lionel.com/products...onchief-set-2023100/
Again, I can pair it, but nothing I add or select actually shows in the roster. There is one loco in the roster and that is a TMCC Amtrak HHP-8 #664. I cannot even select the BT paired loco in the app.
I'm flushing the Cab3 app out of the phone and will try again since its limited to just the Cab3 app.
@Stone Rhino posted:This set:
http://www.lionel.com/products...onchief-set-2023100/
Again, I can pair it, but nothing I add or select actually shows in the roster. There is one loco in the roster and that is a TMCC Amtrak HHP-8 #664. I cannot even select the BT paired loco in the app.
I'm flushing the Cab3 app out of the phone and will try again since its limited to just the Cab3 app.
It seems I have overlooked a page on the manual about the process of pairing the loco to the base. I swear I went over this already.
Access to this requires an OGR Forum Supporting Membership
