Alarm Engine Support Forum Odd “Medical” alarm Reply To: Odd “Medical” alarm

#8207
Michael Burrell

    Keith,

    I appreciate the detailed response.

    Medical Alarm Display Issue: Control Version 0.5.73 is causing the mismatch where the Burg Alarm on the App/Control is displaying as a Medical Alarm on the keypad. In version 0.2.37 of the keypad firmware and in version 0.4.82 of the control, we updated the alarm priority display list. Since you have an older version of control firmware with a newer version of keypad firmware, they are out of sync. Without getting too deep into the weeds here, the control has a priority list that informs the keypad what to display on the “top line” of the keypad. The keypad screen is divided into two display lines. The top line can show messages like BURG ALARM, FIRE ALARM, or FIRE TROUBLE. These top-line messages are fixed and not editable by the installer. The bottom line is the variable line that shows zone names, etc. The display of these top-line messages is based on a “Priority Byte” sent to the keypads during an event. Essentially, the Control is sending the priority number which it thinks is for a BURG ALARM, but the Keypad has an updated priority number list that shows that as a MEDICAL ALARM. So, it displays that. In this case, your keypad has the updated list, but the control has older firmware and the out of date list. For a keypad with 0.2.37 or higher firmware to display properly, you will need to update the control to 0.4.82 or higher. I suggest 0.5.22 as there are many improvements.

    Panel Firmware Update: You have to use Local Discovery to connect to the panel if you want to update firmware. Clicking on the Local Discovery button will present you with a local discovery panel list. This is how you connect locally. If you use the “cloud list” that shown on the page with the “Start Local Discovery” button, it will create a remote connection via the cloud and block firmware updating. We currently do not allow firmware to be updated when connected via the cloud list. The local discovery function works differently than M1; you can use this when you are on the same network as the control to connect for configuration. Certain settings in the control are not allowed while remote, such as updating firmware and disabling the cloud connection (0.5.22).

    Here is a link to the firmware notes: https://www.elkproducts.com/alarm-engine-support/ae-update-info/

    There are major improvements from 0.4.82 control firmware and up. Please look over the release notes linked above. Also, please update the keypad as well. There are many user improvements in keypad firmware 0.2.40 based on field feedback.

    We addressed several issues related to zone behavior by doing a full rework of the zone attributes in 0.4.82 control firmware. I recommend updating to 0.5.22 and test to see if it resolves the issue with the interior follower.

    I apologize for the need to update firmware, I realize this is burdon to do this, but it is our only means of addressing these issues when they are reported. We are working towards remote updating of firmware to remove the requirement for being onsite with the control.

    Thanks,
    Mike

     

     

     

    Scroll to Top