Keypad Update

[JOHN WADE]

Michael,  On two different systems I was able to update the controllers, but when attempting to go from kp2.49 to 2.50,  on one system the update repeatedly failed.  On the other system it locked up two keypads.  I was able to get one to reinstall the 2.49.  The other said keypad update busy fir =an indefinite period despite multiple power cycles and attempts to revert to 2.49.  Ultimately replaced that keypad and did not try to update the replacement.  Please advise.

[Michael Burrell]

John,

We began receiving reports late yesterday and this morning about similar issues occurring when updating the Keypad from E27 0.5.62. It appears this may also affect the XIN update. The issue is not consistent, as we did not encounter it during our internal testing. That said, based on feedback from the field, we were able to briefly recreate the problem this morning and believe we now have a fix. We are currently testing it and expect to release it shortly.

It’s important to note that updating the AEKP or XIN is not critical. The update related to them only includes changes to the underlying code and does not affect functionality. You will not see any difference in operation between firmware versions.

This issue with the bus devices updating relates to how the control firmware communicates with certain bus devices under certain configurations. We hope to have the fix available very soon.

Apologies for the issue and thank you for your patience.

Mike

 

 

[JOHN WADE]

Michael,  I was able to successfully update the input expander on the one system I have attempted that on so far.

[Michael Burrell]

Thanks John.

We should be releasing a new E27 CB version today to address the Keypad update issue.

[Michael Burrell]

Update: We have resolved the issue. E27 CB 0.5.64 will be published Monday morning once testing completes over the weekend.

[JOHN WADE]

Controller update works. No joy on keypads.

[Michael Burrell]

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:

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

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

 

 

[JOHN WADE]

Mike, I will be at another location this afternoon, so I will be able to see if this is a global problem, perhaps…  I will gather the information you requested then.

[JOHN WADE]

E27 Controller  hardware 1.4 firmware 5.64  bootloader 2.24

Has input expander, 2 keypads, digital dialer, 2-way wireless, input expander and zwave

Keypads  hardware 1.1  firmware 2.49  bootloader 1.2

Digital dialer (also won’t update) hardware 1.2  firmware 2.12  bootloader 1.2

 

When attempting keypad update, update either times out between 7 and 57% or goes to 100% says update complete and hangs.

Nothing changes on the keypads during or after attempted update.

When attempting digital dialer update,  error code 11030, failed to start update, incompatible.

 

Hope this leads to a solution.

 

[Michael Burrell]

John,

I appreciate the information. I am out of the office today and tomorrow, but I provided engineering this information and they were able to briefly recreate the issue and are working to discover what the cause is.

Mike

[Michael Burrell]

John,

We’ve identified and resolved the issue you experienced with the bus updating process. I’ve taken E27 CB 0.5.64 down from the site while we test the new firmware. We’ll release it as soon as testing is complete, and we’re prioritizing it to get it released.

The issue turned out to be inconsistent and required a specific configuration to reproduce, which allowed it to slip past our testing procedures. The information you provided was instrumental in helping us uncover it, I greatly appreciate your help.

Mike

[Author]

Posts