Base 3 Firmware 1.28 upgrade issues

I did it via my PC and the Base 3 Sytem utility.  Connected the PC  network to the Base3 in AP mode with the base Switch set to AP and booted with the Gear/upgrade switch pressed in.  Blinking light on the Base3  Did the update, took another couple of minutes for the base to reboot.   Then I reconnected the computer to the Base3 AP network. To check everything.

If you have been running the Base3 on your home network/router.   You need to go the the Base3 System Utility 'Configure" menu at the top to get it to find the IP address while in AP mode.  Search option worked for me.  192.168.1.111 I think.  Then you need to configure it back later in the Base 3 System Utility once you go back to the home network.  Search worked for me then also.

There seems to be an issue upgrading from the mobile device.  I had the same issue.  Hopefully @Dave Olson can look into this.  I too did the upgrade from the PC using the Base3 System Utility.

For what it's worth here is what 1.28 addresses...

Release Notes:

• Bluetooth sub-system
  • When monitoring “SET” command, do not clear B3 database entry if no BLE loco paired on this address
  • Convert Legacy “SET” command to TMCC1 SET command so decoder will process all pairing requests
• RF sub-system
  • When monitoring “SET” command, do not clear B3 database entry if no RF loco paired on this address
  • Convert Legacy “SET” command to TMCC1 SET command so decoder will process all pairing requests
• Modify PDI port controls
  • Create API command processing and logic to reallocate PDI port board ID assignment ranges and enables
  • Major changes to restructure the port allocation relative to PING/board IDs
  • skip sending echoes between PDI ports keeping traffic lower in the PDI port processing
  • skip sending internal PDI command requests out over the PDI ports
  • Blink PDI power LED if the port does not have board ID allocation for modules connected
• Fix record locking on 4-Digit info requests
  • Fix ID2/ID4 lookup sequencers to reset state machine if a record is locked, otherwise subsequent lookups may fail
• Fix potential for buffer overflow; fix missing fields
  • when reading module data length, limit size of data transfer to buffer size
  • initialize the PMID and BTMAC fields properly on restore from module
• Skip Serial EnQueue when queue is disable
  • to improve system throughput, do not add processing for queues that are not active, stopping queue overflows

Ok, thank you all for the suggestions.  Mr. Hubbard, I followed your directions and had no issues with the update using the computer.  My base 3 is now at version 1.28.

I will keep this in mind for future updates.

Best

Billb

Is this old news and corrected with recent app update?

Just updated my base 3 from 1.22 to 1.28 last night through the app. Kinda late getting around to messing with the base 3, have had it since release and only sampled it with the cab2 initially.

After updating base 3, went back to cab2, app was a little confusing as I'd not read the online manual, and I see I'll need to smartphones to use this thing for awhile. One to read the manual on while running app on the other.

@Rod M. posted:

Is this old news and corrected with recent app update?

Yep.  A new version App came out last week.  You missed that drama.

One thing I like to advise people to do is turn on Base3 but not the trains.  Poke around the app and get a feel for the controls.  The APP and Base3 don't know the trains aren't powered and running for the most part with few exceptions.  It's a good way to just poke around.  Once you get the lay of the land and read over the Power and Control site power the trains.  Start of slow with one train and play.  The Cab2 and Cab1L work seamlessly with Base3 so when you're not wanting to learn and just want to run trains I would suggest grabbing those until you are comfortable with the App.