M1XEP IP address changed and ELKRP not communicating after power failure

› M1 Support Forum › M1XEP IP address changed and ELKRP not communicating after power failure

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #11847
    Doron Golan

      I have the ELK M1 Gold Alarm Panel and the ELKRP software for access and programing. I had a power failure that lasted 6 hrs and found out that the M1XEP the local IP address changed from the DHCP that was reserved. The new IP address was 192.168.3.64 which is not part of my network IP. The following are the troubleshooting steps I took which did not resolve the communication access issue of the ELKRP.

      ELK M1XEP troubleshooting summary
      <table>
      <tbody>
      <tr>
      <td>Item</td>
      <td>My action / finding</td>
      <td>Result</td>
      </tr>
      <tr>
      <td>Original problem</td>
      <td>A ~6-hour power failure occurred</td>
      <td>After power returned, the M1XEP was no longer using its reserved address</td>
      </tr>
      <tr>
      <td>Normal gateway</td>
      <td>Confirmed router/LAN address</td>
      <td>192.168.68.1</td>
      </tr>
      <tr>
      <td>Reserved M1XEP IP</td>
      <td>Confirmed DHCP reservation</td>
      <td>192.168.68.67</td>
      </tr>
      <tr>
      <td>Unexpected M1XEP IP</td>
      <td>M1XEP came back after outage at</td>
      <td>192.168.3.64</td>
      </tr>
      <tr>
      <td>JP2 recovery</td>
      <td>Performed the ELK JP2 procedure</td>
      <td>Successful</td>
      </tr>
      <tr>
      <td>M1XEP IP afterward</td>
      <td>Checked M1XEP address</td>
      <td>Returned to 192.168.68.67</td>
      </tr>
      <tr>
      <td>DHCP reservation</td>
      <td>Verified</td>
      <td>192.168.68.67 remains reserved</td>
      </tr>
      <tr>
      <td>ELKRP connection</td>
      <td>Attempted account access</td>
      <td>Connection still fails</td>
      </tr>
      <tr>
      <td>First ELKRP message</td>
      <td>During connection</td>
      <td>“Connecting, verifying system identity”</td>
      </tr>
      <tr>
      <td>Next message</td>
      <td>During connection</td>
      <td>“System returned invalid information”</td>
      </tr>
      <tr>
      <td>Final message</td>
      <td>Connection terminates</td>
      <td>“System did not respond. Connection may have been terminated.”</td>
      </tr>
      <tr>
      <td>ELKRP version</td>
      <td>Checked installed version</td>
      <td>2.0.34</td>
      </tr>
      <tr>
      <td>M1G Control module</td>
      <td>Checked</td>
      <td>5.0.32.0</td>
      </tr>
      <tr>
      <td>M1 Control module</td>
      <td>Checked</td>
      <td>5.0.32.0</td>
      </tr>
      <tr>
      <td>ELKComm</td>
      <td>Checked</td>
      <td>2.0.2.2</td>
      </tr>
      <tr>
      <td>ConvertDB</td>
      <td>Checked</td>
      <td>1.4.10.0</td>
      </tr>
      <tr>
      <td>ELKSafe</td>
      <td>Checked</td>
      <td>1.1.10.0</td>
      </tr>
      <tr>
      <td>ErrorDlg</td>
      <td>Checked</td>
      <td>1.2.12.0</td>
      </tr>
      <tr>
      <td>Trace function</td>
      <td>Looked for it in M1XEP Setup</td>
      <td>Not available in your ELKRP installation</td>
      </tr>
      <tr>
      <td>M1XEP green LED</td>
      <td>Inspected</td>
      <td>Flashing</td>
      </tr>
      <tr>
      <td>M1XEP orange LED</td>
      <td>Inspected</td>
      <td>Solid</td>
      </tr>
      <tr>
      <td>Serial cable</td>
      <td>Reseated the serial connection</td>
      <td>No change</td>
      </tr>
      <tr>
      <td>M1 Serial Port 0</td>
      <td>Checked keypad Global G34</td>
      <td>115,200 baud, correct</td>
      </tr>
      </tbody>
      </table>

      #11850
      Brad Weeks

        Power down the M1XEP, install a jumper onto JP2 of the M1XEP and follow the instructions on page 18 of the M1XEP Installation Manual to Force the M1XEP back into DHCP Mode. Once the Green LED is blinking one blink per second rem0ve the JP2 jumper, allow the M1XEP to reboot and try to “Find” it again using the ElkRP software

        #11852
        Doron Golan

          As a follow up to my previous post which I tried to enter as a table with the steps I took and the outcomes. I am posting the same info in a more readable format see below:

          1) I have an ELK M1 Gold panel with an M1XEP Ethernet interface and use ELKRP for programming and access.

          2) I had a power failure lasting approximately 6 hours. Before the outage, the M1XEP was operating normally on my network.

          3) My router/gateway address is 192.168.68.1, and I have a DHCP reservation for the M1XEP at 192.168.68.67.

          4) After power was restored, I discovered that the M1XEP had changed its IP address to 192.168.3.64, which is not on my 192.168.68.x network.

          5) I performed the JP2 procedure according to ELK’s instructions to restore the M1XEP network configuration.

          6) The JP2 procedure was successful. The M1XEP returned to 192.168.68.67, which is the IP address reserved for it in my router.

          7) ELKRP can now locate the M1XEP at 192.168.68.67, but I still cannot connect to the M1 Gold through ELKRP.

          8) When I attempt to connect using ELKRP, I first see “Connecting, verifying system identity.”

          9) ELKRP then reports “System returned invalid information.”

          10) This is followed by “System did not respond. Connection may have been terminated.”

          11) My ELKRP version is 2.0.34. The installed modules/components shown are: M1G Control 5.0.32.0, M1 Control 5.0.32.0, ELKComm 2.0.2.2, ConvertDB 1.4.10.0, ELKSafe 1.1.10.0, and ErrorDlg 1.2.12.0.

          12) I checked the M1XEP LEDs. The green LED is flashing and the orange LED is solid.

          13) I reseated the serial cable between the M1XEP and the M1 Gold panel. This made no difference to the ELKRP connection problem.

          14) I checked the M1 Gold programming at Global G34. Serial Port 0 is correctly set to 115,200 baud.

          15) At this point, the original IP-address problem appears to have been corrected because the M1XEP is again reachable at its reserved 192.168.68.67 address. However, ELKRP still cannot complete the connection to the M1 Gold and continues to report “System returned invalid information” followed by “System did not respond. Connection may have been terminated.”

          *Current question: What should I check next to determine whether the problem is with the M1XEP, its serial communication with the M1 Gold, or another ELKRP/M1XEP configuration issue?

           

          #11855
          Brad Weeks

            Update your ElkRP2 to version 2.0.41, on the Account Detail Screen make sure the System URL/IP is correct, Port 2601 and the “Connect Non-Secure” is not checked

            #11861
            Doron Golan

              Hi Brad,

              Thanks for the reply. When I try to find out any new updates with ELKRP I get the message that ” ELKRP encountered an error while attempting to download the first available Update, Please verify your internet connection is working and you can access the website at http://www.elkproducts.com. The error returned was: The request was aborted: could not create SSL/TLS secure channel.” My question is what the steps to do the update of the M1XEP to version 2.0.41. I am using windows 10.

              #11862
              Brad Weeks

                Try logging into the website and under Support, M1 Owners, Downloads and Updates you should be able to download ElkRP2 version 2.0.41. From the M1XEP Setup click Trace, click Select ALL, click Show Setup at which point information should populate in the Trace window scroll down to Application Version — what is the APP version in the M1XEP?

                #11866
                Doron Golan

                  Hi Brad,

                  My M1XEP setup does not have Trace to click on, It only show: Reboot, Send, Receive, Find, Close. So, I don’t know what version is my current M1XEP. I have downloaded the ElkRP-Full-install-2.0.41.zip.

                  #11867
                  Brad Weeks

                    You will need to unzip and run the .exe

                  Viewing 8 posts - 1 through 8 (of 8 total)
                  • You must be logged in to reply to this topic.
                  Scroll to Top