Skip to main content

Is anyone having issues upgrading from 1.26 to 1.28 firmware version on the Base 3.

Following the instructions, the base three will not stay connected in AP mode, while also in upgrade mode.   It states that I am trying to connect to a non-base 3 accessory. 

Makes no sense. 

Original Post

Replies sorted oldest to newest

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...

Base3 Firmware Version Table

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
Last edited by MartyE

Add Reply

Post

OGR Publishing, Inc., 1310 Eastside Centre Ct, Ste 6, Mountain Home, AR 72653
800-980-OGRR (6477)
www.ogaugerr.com

×
×
×
×
Link copied to your clipboard.
×
×