Elk M1 Firmware Update Scrambles Zones

[KapnKrunch]

I just updated my Elk M1 to the latest firmware (5.2.10) and immediately after, I noticed some violated zones. I then immediately down-graded to the prior firmware version, and the problem remained.

Turns out that somewhere during the process of the update, the zone definitions got scrambled, which resulted in incorrect parameters in some zones.

I had to re-enter the correct information for the last 5 zones, and all was well.

Very strange, and something to look at if you upgrade your M1 firmware.

 

[Del91574]

Can't say I've experienced the same on all the M1's I've put in over the years, all the way back to the platform start when there was the M1 and M1G as separate panels.

Usually, a best practice for any panel, no matter who the manufacturer is to have a copy of the panel before you make any changes and a copy after you make the changes. Some of the larger pieces of hardware actually fare better if you "overlay" a blank template into the panel, then put the modified panel program in. YMMV.

 

[ddennerline]

The Elk documentation indicates best practice is to “send all” from ElkRP after an upgrade. Also, during reboot some zones will show as violated. I just upgraded today to 5.2.10 and a few zones did show violated/restored status (no big deal). I was pretty happy that upgrade didn’t fail; thus requiring a laptop and rs-232 cable (this has happened to me before).