@MartyE posted:Buy a SER2 and connect it to the PDI buss and connect the TMCC base to the serial port on the SER2. Done.
Thanks Marty. Curious why you can’t just get a DB9 serial to micro USB but if Ser2 works, thats good.
Pete
Dave 69 follow these instructions below to transfer the engines. It will take 1 / 2 minutes per engine.
For those having trouble moving their base2 engine roster to the base3, I was able to move our clubs roster of 80 ID addresses in about 90 minutes once I got the hang of it. That being said here is where the instructions are. Go to www.control.lionel.com, select the Base3 instructions, drop down to the section on the left that says Memory Modules, select that. Scroll down till you get to ‘Creating a MEM with the base2’. The instruction are about 4 paragraphs long, if you get to ‘updating firmware’ you went a little too far. Follow the instructions and it works. Yes, I’m sure the B3SU is easier, but it is not out yet. Have to work with what you have.
@Reading RR posted:Dave 69 follow these instructions below to transfer the engines. it will take 1 / / minutes per engine.
For those having trouble moving their base2 engine roster to the base3, I was able to move our clubs roster of 80 ID addresses in about 90 minutes once I got the hang of it. That being said here is where the instructions are. Go to www.control.lionel.com, select the Base3 instructions, drop down to the section on the left that says Memory Modules, select that. Scroll down till you get to ‘Creating a MEM with the base2’. The instruction are about 4 paragraphs long, if you get to ‘updating firmware’ you went a little too far. Follow the instructions and it works. Yes, I’m sure the B3SU is easier, but it is not out yet. Have to work with what you have.
Thank you. I guess you just have to remember what eng ID number is assigned to each locomotive to save it to that ID number in the base 3.
I successfully imported 1 engine, very awkward. I have the base 3 downstairs next to my router trying to connect it to the home network with no luck. It seems you probably need the CAB3 utility software to do this. Anyone sensing how clunky this thing is?
Question? How can I switch from the speed lever on the Base 3 app to the radial control?
@Alabama Joe posted:Question? How can I switch from the speed lever on the Base 3 app to the radial control?
Double tap the 3 digits above the speed lever. This is on the Lionel Power and Control site.
Dave 69
A lot of people are having trouble connecting to there networks. I run AP, no problems.
The app is absolutely a clunky nightmare. You press the wrong thing for instance and the app closes. Great when you're trying to control trains. With all kinds of potential disasters waiting to happen as you swipe to change engines and accidently might start something rolling you dont want to roll or uncouple a string of cars. So I have to ask myself, what am I getting out of this? The CAB2 remote is still the best thing to use. What did I pay $500 for, 4 digit addressing? Can't use 4 digits with a CAB2 remote. It is begging for a CAB3 remote, and I don't mean the 1L. I mean a remote like a CAB2, but better.
@Reading RR posted:Dave 69
A lot of people are having trouble connecting to there networks. I run AP, no problems.
I'm sorry, AP?
@Reading RR posted:Dave 69
A lot of people are having trouble connecting to there networks. I run AP, no problems.
Sean had a good suggestion to move your base right next to the router to initially set up the network connection. The base can then be moved back to the train table. OTOH, when on the network, there may be new issues not seen running just AP.
@MartyE posted:Double tap the 3 digits above the speed lever. This is on the Lionel Power and Control site.
Thank you Marty. I looked but I must have missed it. Thanks again.
@Dave 69 GTEL posted:I'm sorry, AP?
Access Point
@Apples55 posted:Dave;
This techno-peasant needs some clarification… won’t the current LCS PDI cable which is attached to the Sensor Track work with the Base 3??? Since the portion of my layout where the track is located is sceniced, replacing the cable will be problematic. Thanks.
As Gunrunner John indicated, the PDI cables in use for your current LCS layout will work fine. BUT, with Base 2, the first PDI terminated in a serial port which was used to connect your first LCS device to the base. With Base 3, the first cable needs to be PDI to PDI, so yes, that first cable will need to be replaced. Very nice that you have three PDI ports in Base 3 though, so you needn’t daisy-chain your entire LCS infrastructure together. That could get sloppy, and if an issue arose, it was a little tougher to troubleshoot than it will be now.
@Bruce Brown posted:Sean had a good suggestion to move your base right next to the router to initially set up the network connection. The base can then be moved back to the train table.
This is what I did. It took a second try and connected. Then brought it downstairs to the train room and works fine.
Gene
@gunrunnerjohn posted:I couldn't connect the LCS WiFi module using WPS when I first got it. I tried four different routers, and only one recognized the WPS, sadly it was a spare and not the router used for my home network that I needed to connect.
I have a feeling that some folks are going to have the same experience with the BASE3. I finally got the LCS WiFi connected here using the LcsWifiMonitorLE program. I suspect a similar capability will be needed by some to get the BASE3 connected to their WiFi.
WPS is always a bit “touchy” with any device you’re trying to connect to your LAN. It also assigns an IP address within the range of those available, but doesn’t let you specify the address. That results in the CAB 3 needing to search your entire domain for the Base 3 whenever the connection is lost (device shut down). That gets old quick! I’d highly recommend using the instructions “Join network without WPS” then either assigning a static IP address, or assign the IP address that you wish your DHCP server to lease to the Base 3 based on its MAC address. Since that IP will never change, reconnecting the Cab 3 app to the Base 3 is almost instantaneous, and the connection is much more reliable. It involves an additional step, since you first need to place the BASE 3 in AP mode, connect your mobile device to Base 3, then manually add in your SSID and password. Once those are in, the “Get” button will negotiate a connection and you can reconnect your mobile device back to your home’s SSID, where it will then find the Base 3. Still recommend assigning static IP address to the device though (or really any priority device such as printers on your home network). It saves a lot of aggravation down the road.
Now, the question becomes… What is everyone going to be doing with their LCS WiFi modules which will no longer be necessary to address your LCS system?!?
Don't throw your LCS WiFi away just yet. The command stream data echoed by the Base3 WiFi is filtered for performance reasons which breaks features on exisitng 3rd party software. As I noted in this thread, the LCS WiFi can coexist on the same subnet as the Base3 and allows 3rd party software to operate correctly.
Thanks for sharing that tidbit, as I wasn’t aware! It actually makes sense that the two could peacefully coexist since they have different IP addresses. You just need to differentiate which one you’re trying to reach.
@Pennsy Johnnie posted:WPS is always a bit “touchy” with any device you’re trying to connect to your LAN. It also assigns an IP address within the range of those available, but doesn’t let you specify the address. That results in the CAB 3 needing to search your entire domain for the Base 3 whenever the connection is lost (device shut down). That gets old quick! I’d highly recommend using the instructions “Join network without WPS” then either assigning a static IP address, or assign the IP address that you wish your DHCP server to lease to the Base 3 based on its MAC address. Since that IP will never change, reconnecting the Cab 3 app to the Base 3 is almost instantaneous, and the connection is much more reliable. It involves an additional step, since you first need to place the BASE 3 in AP mode, connect your mobile device to Base 3, then manually add in your SSID and password. Once those are in, the “Get” button will negotiate a connection and you can reconnect your mobile device back to your home’s SSID, where it will then find the Base 3. Still recommend assigning static IP address to the device though (or really any priority device such as printers on your home network). It saves a lot of aggravation down the road.
Now, the question becomes… What is everyone going to be doing with their LCS WiFi modules which will no longer be necessary to address your LCS system?!?
I agree with this. DHCP can always cause issues with any device. Static is always the best, but for some they don't know how to assign a static IP.
@Sean's Train Depot posted:I agree with this. DHCP can always cause issues with any device. Static is always the best, but for some they don't know how to assign a static IP.
I assign static addresses to all my NAS boxes, alarm system, and the networked printers. That greatly improves the ability for the flaky Windows SMB discovery for networked devices.
It looks good, and works with my TMCC, Legacy, and Lionchief+ (pretty cool to run the lionchief on a cab2). The good times end there... cab 3 app is super clunky and buggy and where's the desktop app!?. Overall very disappointing that the software is in such a sorry state after years of delay. I'm gonna ride it out, but a little part of me wishes I canceled the preorder, unless you have lionchief you're better off with LCS wifi.
I just sent this e-mail to Lionel:
"I have the Base 3. The app stinks. Not only is it buggy and crashes a lot but it's just a clunky, clumsy way to control trains, which are expensive moving objects. My CAB2 control is the preferred interface but not everyone has one or can afford one on the used market these days. The app is crap and Lionel should develop and offer a Base 3 compatible handheld control. And I'm not talking about the feature lacking CAB-1 like, CAB-1L . I'm talking about a full featured CAB-3 handheld, full control and displaying locomotive pictures, 4 digit addressing and everything. Do you know for instance that the HALT button must be held down for 2 seconds before it shuts down the layout in an emergency? That's a problem because it might obviously stop things too late. The purpose of that is also obviously so you don't accidently hit it, but that's the limitation of an app. Another thing the app will not control the track power output of my ZW-L transformer through the TR function. For that I must use my CAB-2 handheld. This base needs a full featured and different and better control solution."
So I'm advocating for Lionel to offer a good CAB-3 handheld, similar but even better than the CAB-2.
Hah, I assumed the halt button didn't work. Sure enough, if you hold a couple seconds it does!
Our assessment of the CAB3 app is similar, it's a hot mess right now. Some fundamental finger gesture controls need serious attention. We've already had a catastrophic locomotive collision at the club due to screen change swipe being misconstrued as commands sent to engines with panic stops (HALT) not being accessible in time.
I suspect if a physical CAB3 remote is ever produced, it will be based on the CAB3 app for the software and perhaps a custom controller for the physical hardware control.
One thing we all need to remember here is that as Lionel is getting the bug list put together, it will take a little bit of time for them to compile code, test, and release an update on the stores. Updates to the app may not be day-to-day as they fix these bugs but could be every few days or weekly. I know we all want this to be perfect from day one but perfection is going to take some time and patience.
The reason the halt button takes 2 seconds is that if you accidentally hit it the whole layout would come to a screeching halt. Not defending Lionel, but that would get old real fast, since it is easy to hit the wrong button on the app.. I'm sure Lionel will eventually get the app. better, my current preference is the CAB2. I cannot believe I am saying this but, this is the future like it on not, and as time goes on we will all have to adapt. Hopefully a new hardware remote is in the future someday.
@Dave 69 GTEL posted:I just sent this e-mail to Lionel:
"I have the Base 3. The app stinks. Not only is it buggy and crashes a lot but it's just a clunky, clumsy way to control trains, which are expensive moving objects. My CAB2 control is the preferred interface but not everyone has one or can afford one on the used market these days. The app is crap and Lionel should develop and offer a Base 3 compatible handheld control. And I'm not talking about the feature lacking CAB-1 like, CAB-1L . I'm talking about a full featured CAB-3 handheld, full control and displaying locomotive pictures, 4 digit addressing and everything. Do you know for instance that the HALT button must be held down for 2 seconds before it shuts down the layout in an emergency? That's a problem because it might obviously stop things too late. The purpose of that is also obviously so you don't accidently hit it, but that's the limitation of an app. Another thing the app will not control the track power output of my ZW-L transformer through the TR function. For that I must use my CAB-2 handheld. This base needs a full featured and different and better control solution."
So I'm advocating for Lionel to offer a good CAB-3 handheld, similar but even better than the CAB-2.
While I'm all for advocating for a new handheld, I think you did your message a disservice with the tone you took. Pretty demanding as well. While it certainly is fine to point out what you think the short comings are, a more diplomatic tone would have in my view a better approach.
I have written to Lionel in the past. I have posted to this forum, critical of their product when I felt I needed to, but each time I took the time and the effort not to be insulting, derogatory, or mean spirited in my post or email.
Posts like these are why Lionel rarely comes on the forum and participates short of Dave.
@Reading RR posted:The reason the halt button takes 2 seconds is that if you accidentally hit it the whole layout would come to a screeching halt. Not defending Lionel, but that would get old real fast, since it is easy to hit the wrong button on the app.. I'm sure Lionel will eventually get the app. better, my current preference is the CAB2. I cannot believe I am saying this but, this is the future like it on not, and as time goes on we will all have to adapt. Hopefully a new hardware remote is in the future someday.
Sure, making it instant would definitely be a nuisance. But what about making it instant + a confirmation dialog. Or maybe instant if you press a combination of the halt button and volume up or something.
@MartyE posted:While I'm all for advocating for a new handheld, I think you did your message a disservice with the tone you took. Pretty demanding as well. While it certainly is fine to point out what you think the short comings are, a more diplomatic tone would have in my view a better approach.
I have written to Lionel in the past. I have posted to this forum, critical of their product when I felt I needed to, but each time I took the time and the effort not to be insulting, derogatory, or mean spirited in my post or email.
Posts like these are why Lionel rarely comes on the forum and participates short of Dave.
Huge props to Dave for coming in here, on the other hand I think people are justifiably upset with the quality of software. Base3 is a decent pile of C-notes, and the cab3 app is not really useable without a real remote nearby to slam the halt button.
@Kneissl posted:Huge props to Dave for coming in here, on the other hand I think people are justifiably upset with the quality of software. Base3 is a decent pile of C-notes, and the cab3 app is not really useable without a real remote nearby to slam the halt button.
Perhaps it could go like this...
"Hey Dave could there be an option to make the Halt button instant, a 1 second delay, or 2 second delay? User selectable. Thanks."
Another reason to keep this civil, if we don't OGR will close this topic. Then a new one will have to start.
After our little mishap with the HALT Button. We did some quick onsite research and testing and then Training and PRACTICE with the members on using the HALT button. How it works, when & where (which screens) it is available on. We made each and every one of them PRACTICE using it in a non-emergency situation so that they get a feel for using it. This didn't take long and helped reestablish some of the comfort level with the app.
Safety is first and foremost and understanding how to use the HALT button should be one of the first things anyone should do.
The E-STOP button in the MTH App works the same way as the HALT button does, I don't think Lionel needs to make any changes there but people should try it out so they understand how it works.
@MartyE posted:While I'm all for advocating for a new handheld, I think you did your message a disservice with the tone you took. Pretty demanding as well. While it certainly is fine to point out what you think the short comings are, a more diplomatic tone would have in my view a better approach.
I have written to Lionel in the past. I have posted to this forum, critical of their product when I felt I needed to, but each time I took the time and the effort not to be insulting, derogatory, or mean spirited in my post or email.
Posts like these are why Lionel rarely comes on the forum and participates short of Dave.
I do demand better and have a right to. If Dave Olson does visit these forums, and it wouldn't surprise me if he had visited this one, then that is Lionel visiting the forum and at a very high level.
Knowledge is power for sure. I certainly am NOT discouraging folks from making known what they like and dislike as well as offering suggestions. I'm pretty sure Dave and the folks at Lionel are happy to listen if it makes their product better and more enjoyable but presentation definitely gives more credibility to your thoughts.
Just my opinion. Your milage most likely will vary.
I think constructive language is definitely the right way to go. However, there have been warnings since the beginning of the announcement of the discontinuation of the 990/CAB-2, that a physical remote is not only preferred, but that an "app" by itself would never yield the level of control required for controlling $2000 locomotives.
All of that advice was summarily dismissed. Lionel made its choice and is going to have to deal with the feedback or customers will speak with their dollars or lack thereof.
@rplst8 posted:All of that advice was summarily dismissed. Lionel made its choice and is going to have to deal with the feedback or customers will speak with their dollars or lack thereof.
Dave said on the Legacy User Group event that they haven’t ruled out a hardware remote but the focus was on Base3 and the App first and foremost.
I certainly wouldn’t write it off just yet.
@H1000 posted:Our assessment of the CAB3 app is similar, it's a hot mess right now. Some fundamental finger gesture controls need serious attention. We've already had a catastrophic locomotive collision at the club due to screen change swipe being misconstrued as commands sent to engines with panic stops (HALT) not being accessible in time.
The screen swipe was a MAJOR design mistake IMO! To change screens, just have a button with an arrow to "swipe" in that direction. The swipe is way too easy to turn into an errant command.
Truthfully, the whole problem with no tactile feedback of a smart screen device is a major reason why I don't like the idea of an app for controlling my trains.
@gunrunnerjohn posted:The screen swipe was a MAJOR design mistake IMO! To change screens, just have a button with an arrow to "swipe" in that direction. The swipe is way too easy to turn into an errant command.
Maybe they'll address that. I'm sure they are seeing the comments and suggestions. The great thing about an App is it can be modified and changed.
@gunrunnerjohn posted:The screen swipe was a MAJOR design mistake IMO! To change screens, just have a button with an arrow to "swipe" in that direction. The swipe is way too easy to turn into an errant command.
I'm not going to disagree there, John. MTH has both methods for changing screens and they did a much better job of mastering the swipe to change screens. I prefer the buttons to change the screens but still feel very comfortable with the swipe and scroll methods used on the DCS App.
The app users at the club I'm currently helping prefer to use the DCS App to run their Lionel engines via the BASE3 as it is familiar to them. The BASE3 now adds the ability to run RF & Bluetooth engines from the LC & LC+ generation that don't have TMCC with the DCS App which has been received well.
Simple question amidst the discussion: Can I use Cab3 app in a place that doesn't have Wifi?
@Conductor Earl posted:Simple question amidst the discussion: Can I use Cab3 app in a place that doesn't have Wifi?
As long as there is a Base3 you can use the App in Base3 mode. The Base3 will need to be in Access Point mode and the app will connect to it. You will need to make sure your phone is connected to the base's WiFi. The App will connect directly to Bluetooth equipped engines on the Bluetooth side with out a Base3.
@Conductor Earl posted:Simple question amidst the discussion: Can I use Cab3 app in a place that doesn't have Wifi?
Yes. You'll have to set the BASE3 to AP (Access Point) mode and then connect your Phone/Tablet directly to the BASE3 Wi-Fi network.
