I am having trouble getting the virtual keypad in ML to work with my M1G. I am running ML3 and the latest ML Elk plugin. I am using the M1 ethernet port to comunicate with ML. I have updated the M1G with all of the latest Firmware including the keypad and M1XEP. I do have the M1 variables updating on the MLServer and I can arm and disarm the system using the MLServeCmd.MLELKM1|Arm~1~2~1234. I have put the MLServeCMD.MLElkM1|KPinit~1 in the virtual keypad scene startup command. But I cannot get the MLServeCMD.MLElkM1|Key~x commands to work. Please help
Unless I'm reading the plugin log wrong it doesn't appear that the plugin ever sends a command to the M1. After entering 4 digits I'd expect to see an entry similar to:
TCP/IP Sending [0Da010012340003F]
but I never see and TCP/IP Sending messages in the log after entering digits.
I see the same issue with the KPExit command. When issued I see:
in the log but no command appears to be sent to the M1 and "Updating Virtual Keypads" continues to be logged. In contrast when issuing a KPInit command I see:
TCP/IP Sending [08kc010009]
Rcvd: 29 bytes [19KC01000000000000000000017]
Rcvd: Keypad KeyChange Data
End Event [4/1/2008 11:22:24 PM]
Two things. Did you notice to see if the associated ELKM1 server varaibles were being updated as you pressed the keys?
The virtual keypad is only programmed to respond to a few preset key sequences. If the panel is previously armed then pressing the four digits will send the disarm command. If you press the Bypass key you will get prompted for the zone to bypass.
What sequence of button pushes are you trying to emulate?
CinemarDave wrote:An update to the plugin will be posted that supports this sequence.
That's good news; I'll keep my eyes peeled for the update.
I know that a "disarm" command can be programmed with: MLServeCmd.MLELKM1|Arm~0~1~1234 but any disarming procedure that doesn't require a code to be entered manually could allow an intruder to simply disarm the system during the entry delay.