John,
Interesting—thanks for the info. Can you share a bit more about your setup?
-
How many bus devices are connected?
-
Do you have a DBHR installed?
-
What firmware and bootware versions are currently on the AEKP?
I personally assisted in some extensive testing of this issue and was able to reproduce it consistently once I had the right setup. I’m curious to see how yours compares.
Also, can you provide more detail on how it’s failing? In a proper update, the update should reach 100%, indicating the file was fully transferred. On the 7-segment display of the control, you should see an “F” followed by a “P,” then it will count up from 1 to 9. When it displays “A,” the update is complete. This sequence happens for all bus device updates.
In the issue we previously investigated, the process would reach “F” and then revert to cycling “ENO” or other data. Essentially, the system was erasing the firmware in the bus device but failing to install the new one. This behavior was traced back to an incompatibility between older bus device bootware and firmware version 0.5.62. Version 0.5.64 was released to address and accommodate the older bootware.
Full disclosure: there is a known bug in the app when updating bus device firmware. It’s at the top of the priority list for the app team, once they finish their current work on the touchscreen interface. There are two issues to be aware of:
-
If the transfer percentage (1–100%) stops progressing, you’ll need to disconnect and reconnect the app. This typically results from a bad packet being returned, causing the connection to fail—more common on busy networks.
-
After any bus device firmware update attempt (successful or not), the app must be closed and reopened. Updating the device causes the app to lose its connection to the control due to the changes in the tables related to the devices.
Both issues are well documented and currently ranked as high priority. In addition, the web team is actively developing remote, cloud-based updating that won’t require the app. They’re working on the interface and infrastructure now.
Let me know what you find, and we’ll take a closer look based on your feedback.
Thanks,
Mike