BASE3 Roster Doesn't Match Engines In Database

Mine all show up as Legacy too.  I'm not overly concerned as they are correct using the App.

@MartyE posted:

Mine all show up as Legacy too.  I'm not overly concerned as they are correct using the App.

Since I prefer the remotes, I'd like them to be correct here.   For Legacy, I used the LSU to maintain all the stuff, much easier to type names, etc. using a full keyboard than on a remote.

Looks like a bug in the roster display code.  As you discovered, the Base3 needed a reboot before the roster would display.

Conversely, Lionchief RF engines will display correctly as "RF" in the Base 3 roster, but show up as "TMCC" in the engine data tab. Clearly there are bugs in the Base3 System Utility, but apart from occasional nuisance crashes, I manage to ignore them. More importantly, the database that I transferred from my BASE2 to BASE3 was not corrupted so my CAB1-L and CAB2 remotes both function correctly without any glitches. Fortunately, the BASE3 hardware appears solid from most accounts.

The CAB3 app is an entirely different topic that requires polite restraint on my part. Let's just say it is good that you have kept your remotes. Most people I know have quietly set the CAB3 app aside, at least for the time being. Lionel, for their part, appears to have done the same because there haven't been any updates in months. Let's hope for the best, which is a necessary investment to finish and then maintain the software so the BASE3/CAB3 product works as promised.

@GregR posted:

Conversely, Lionchief RF engines will display correctly as "RF" in the Base 3 roster, but show up as "TMCC" in the engine data tab. Clearly there are bugs in the Base3 System Utility, but apart from occasional nuisance crashes, I manage to ignore them. More importantly, the database that I transferred from my BASE2 to BASE3 was not corrupted so my CAB1-L and CAB2 remotes both function correctly without any glitches. Fortunately, the BASE3 hardware appears solid from most accounts.

The CAB3 app is an entirely different topic that requires polite restraint on my part. Let's just say it is good that you have kept your remotes. Most people I know have quietly set the CAB3 app aside, at least for the time being. Lionel, for their part, appears to have done the same because there haven't been any updates in months. Let's hope for the best, which is a necessary investment to finish and then maintain the software so the BASE3/CAB3 product works as promised.

Yep, I've had the BSU crash a couple of times, mostly when I click on a button that's probably in error, and the error isn't caught but rather crashes the utility.  However, it starts right back up, so it's only a minor issue for me.

I originally had an issue where most of the fields in the engine entry screen were green and not editable, not sure what I did to get rid of that issue, but now they work.

I had previously run at another layout with the CAB1L and CAB2 using the BASE3 and I didn't see any difference between that and using the Legacy base.

I was told by another user that if you get too many remotes connecting to the BASE3, it may lock up and require a power cycle to get going again.  I intend to try that on my workbench before I put it into service to make sure that doesn't happen here.  If I can connect four or five CAB1L and CAB2 remotes and toss in the CAB3 for fun, I'll figure that isn't something that should affect me.  I don't think it's often I'll have more than four remotes accessing the layout at the same time.