broken checksums on some Elk "AS" messages

[lmamakos]

I've noticed that occasionally I'm getting messages from the Elk M1 (via the M1-XEP Ethernet interface) with an incorrect checksum on some "AS" messages. Usually, I'll see correct messages like:
1EAS000000001111111100000000000E

but every so often, the broken version of this message with a bad checksum slips in as:

1EAS00000000111111110000000000A6

I believe the broken messages are triggered when I use Java applet in the Elk M1-XEP to arm/disarm the M1-Gold panel, vs. using one of the physical keypads. I can't easily verify this now since the system is a couple hundred miles from here, but looking at the logs of messages seems to confirm this conclusion. Does this ring a bell for anyone?

I'm running firmware version 4.5.8 on the M1G and version 1.2.14 firmware on the M1-XEP.

Louis Mamakos

 

[Lagerhead]

I believe the broken messages are triggered when I use Java applet in the Elk M1-XEP to arm/disarm the M1-Gold panel, vs. using one of the physical keypads.

Hmmmm.... Maybe this is related?

I lately noticed, but did not investigate or report, incorrect behavior of the applet in reporting zone status. At times, the "display" in the keypad applet has said "0 ZONES VIOLATED" (that's a zero there) when it should of course say "READY TO ARM". It has also reported the wrong number "[n] ZONES VIOLATED", which is easy to verify because all the zones are listed correctly with the STATUS button.

This XEP is hardware version 1.0, boot 1.1.4, and firmware 1.2.12.