Here is a detailed response from the ELKRP Guru:
The latest firmware version for the M1XEP is 1.2.12. It wouldn’t hurt to upgrade to it. If the problem still persists, do the following:
1) Open the account in ElkRP
2) Click on Account Details
3) Press Ctrl-F5 to open a diagnostic window (You may have to resize it to see it better)
4) Connect to the M1 via network.
5) If you see a receive line that looks like this: RCV: 08RP0200 . . .
a. Check the cable connecting the XEP to the M1 – make sure it is snug and works.
b. Reboot the XEP (power cycle it) and wait 2 minutes for it to reboot. Try it now.
c. Use Keypad programming to check Globals G34 – make sure it is 115200 baud. If not,
i. Set it to 115200 baud.
d. If it is, change it to some other value, save it, then change it back to 115200.
e. Try that. If still no joy, default Globals Programming using G45 (refer to the manual).
f. Default the entire control.
6) If you see: RCV: 08RP0100 . . .
a. Make sure another copy of ElkRP is not connected to the control already.
b. Reboot the XEP.
7) If you see neither of the above,
a. Reboot the XEP.
b. Reboot the control and XEP together.
c. Try the additional steps below.
d. Contact your distributor for technical support.
Additional steps:
Hopefully, you’ve enabled the non-secure port (2101) on the XEP. If not, this won’t work…
1) Open HyperTerminal (HT) and create a TCP/IP (Winsock) connection to the XEP’s IP address, port 2101.
2) Press a few keys on the M1KP or trip a zone to see ASCII data in HT’s window.
3) If all you see is 08RP0200 . . . then try the steps under #5 above.
4) If you see valid ASCII data resulting from the key presses and zone changes, the XEP is working fine.
5) If problems persist, isolate them to the XEP/cable/M1 by doing the following –
6) Disconnect the serial cable from the XEP and plug it into a serial port on your PC. (note: if you use a USB<->RS232 converter, first make sure it works)
7) Use HT to make a serial connection using the COM port the cable is attached to, 115200 baud, 8 data, 1 stop, no parity, no handshaking.
8) If you see valid ASCII data, the M1 and cable are OK – problem may be in the XEP.
9) If you see no data or corrupt data, check the baud rate in the M1 (G34) and the PC. If still no joy, try another known good cable. If still no joy,the M1’s RS232 driver may be damaged.
