M1XEP FAIL TO COMMUNICATE Error

[Michael Doherty]

I have an Elk M1 system with an MX1XEP. Up until a few weeks ago, the system was working fine. Now, I keep receiving a “FAIL TO COMMUNICATE” error on the keypad, but I can’t figure out what is causing it. I use the eKeypad app to remotely access the system. I can access and control the system when on WiFi in my house, but cannot when on cellular. I keep getting a “time out” error message on the app. I am pretty sure the appropriate port (2601) on my router is forwarded properly. Any suggestions as to how to resolve the error are appreciated. Thanks.

[Brad Weeks]

Failed To Communicate would indicate the M1/M1XEP attempted to send a signal to your Central Monitoring Station but did not receive the Acknowledgement of the signal. This message will continue to display until the M1/M1XEP receives the Acknowledgement. Please check with your Central Monitoring Station to make sure the IP Address, Port number, Account number and if required the DNIS information is correct and matches the information in the M1XEP Setup under the Central Station tab. Under the M1XEP Setup and the TCP/IP Setting tab make sure your Primary DNS Server IP is correct — in some cases the Default Gateway IP will work as the Primary DNS Server. If your M1XEP isn’t running firmware 2.0.51 I would also update the M1XEP and retest with sending signals to Central Station and remote connection with eKeypad.

[Michael Doherty]

Brad,

I contacted my central monitoring station (Alarm Relay). All connection parameters were correct (and unchanged). They had me power down the alarm panel and reboot my modem/router. After doing so, the system still did not send a signal to the monitoring station. Also, there was now an “ETHERNET TROUBLE” message on the keypad in addition to the communication failure message. The Ethernet trouble message has appeared occasionally over the past couple of weeks. I can now no longer connect to the M1XEP via the RP Software.

Prior to powering down the panel, the RP Software would connect. When it did connect, though, I would receive a conflict message stating the database was modified and I would download the change to the system and reboot the M1XEP. I could then connect without a conflict. However, when I exited the RP Software and got back in, the conflict message would appear even though I had made no changes to the setup/database. I don’t know if that’s relevant.

Finally, the Alarm Relay tech said the problem was either the Ethernet cable or the M1XEP itself. I changed out the cable and still received the Ethernet trouble and communication failure messages, leaving only the M1XEP as the issue, in his opinion. What do you think? Thanks.

[Brad Weeks]

From keypad programming:

• Press the ELK key; screen should display 1-View/Control Automation Fncts
• Press the 9 key; screen should display 9-Installation Programming (0)
• Press the Right Arrow Key and enter the Keypad Installer PIN (Globals G42)
• Screen should display 01-Bus Module Enroll
• Press the Right Arrow key to perform the Enrollment
• Once complete press the ELK key until screen returns to 9-Installation programming
• Press the 8 key, screen should display 8-System Settings
• Press the Right Arrow key; screen should display 81-Set System Clock in 24 HR Format
• Type 6; screen should display 86-System Diagnostics
• Press the Right Arrow key; screen should display 1:DataBusErrors…
• Press the 5 Key — Does M1XEP = Enrolled  or M1XEP = NO?
• If M1XEP = NO then the M1 does not see the M1XEP which could be either the cable between the M1XEP and the M1 or a bad serial port on either the M1XEP or the M1
• Direct a Direct connection with ElkRP2  to the M1 using an USB to RS232 Serial Cable . If you are able to connect direct then the M1 Serial Port is Good

[Michael Doherty]

When I press the Right Arrow Key to perform the Enrollment, I first get a message saying “KP Addr. 2 ==> Lost Comm,” but it ultimately says Enrolled. In the last step, when I press and hold the 5 Key, it first says M1XEP=No, then switches to Enrolled, then back to No, and finally back to Enrolled. When I release the 5 Key, it says Enrolled. I’m not sure how to interpret the result. Is the M1 seeing the M1XEP? Thanks.

[Brad Weeks]

On the M1XEP circuit board locate the D6 LED (located between the power connection and the RS232 port) and watch the LED to see if it blink off and then back on which indicate the M1XEP is rebooting. If this is the case you will need to replace the M1XEP

[Michael Doherty]

The D6 LED on the M1XEP is lit and solid (NOT blinking). Thanks.

[Brad Weeks]

From the keypad Menu 8 screen when M1XEP = Enrolled watch the second line the 30Sec PING count and the number should increment by 1 every 30 seconds

[Michael Doherty]

The number on the 30Sec PING Count line is increasing by 1 every 30 seconds.

[Brad Weeks]

If M1XEP = Enrolled and the PING Count is incrementing the M1 and the M1XEP are communicating with each other. Under the M1XEP Setup and Central Station verify with your Central Monitoring Service the information including the IP Address for their Receiver (Surguard or OH2000 E) is correct, the Port is correct and the Account Number is correct.

[Michael Doherty]

All of the Central Station information was somehow erased. Monitoring service walked me through re-entering the information and and am now reconnected. The communication failure error is no longer on the keypad. Thanks again for your help.

[Author]

Posts