I need to open a formal support ticket as I have a batch of Here4 Blues that are not behaving correctly, and this seems to be unrelated to the recent service bulletin.
Sometimes when they are powercycled, they get stuck in SOFTWARE_UPDATE or MAINTENANCE mode, when I definitely have not manually triggered such things. The LEDs blink blue in this case.
When I use Mission Planner to view the status of the device during reboots, it says “booting with fallback bootloader”. Setting FLASH_BOOTLOADER to 1 doesn’t result in a change to this message.
Using “Update beta firmware” reverts the firmware to 1.14, which seems to make that message go away, instead saying “Booting with main bootloader”. Updating back to 1.15 is a roll of the dice for whether or not this status reverts.
Regardless, I can’t seem to find a combination of ardupilot gps parameters and here4 parameters that will allow some units to change their constellations (some report low satellite count until I get into ucenter and start mucking with the guts), or enter rtk when I have a local ntrip caster, or stay in 3D Fix in spite of the selection to use SBAS corrections.
I am dealing with several units that exhibit these characteristics, as well as a few for which it seems that the compass has finally failed. I could use some next steps to correct these issues.
