Trouble Replacing M1XEP

[Joel Blackthorne]

I have an M1 Gold installed in 2012 and still going strong until last week.  I noticed the M1EXP was not long retrieving an IP over DHCP.  After a trying everything, I ordered a new M1XEP on Amazon.  I notice that the new board was assembled in Taiwan vs the older board which was assembled in China.  When connected, the new M1XEP:

• grabs an IP over DHCP without an issue
• can be pinged over the ip
• M1XEP Debug shows traffic:
  • 17:56:56 Open_Socks: 01 = 06
    17:56:56 TCP Secure connection accepted
    17:56:56 TCP Secure Received client hello
    17:56:56 TCP Secure Begin SSL negotiation
    17:57:04 TCP Secure SSL negotiation succeeded
    17:57:04 TCP Secure No challenge
    17:57:04 TCP Secure RP connected
    17:57:04 TCP socket dropped
    17:57:04 Close_Socks: 00 = 253
    17:57:05 TCP SendUnkPkt 16XK05571772106251100064
    17:57:15 TCP Query ElkServer, Count = 10

Thinking perhaps this is a firmware issue, I downloaded the 2.0.51 uddpate and it shows the M1XEP is already the latest firmware.  Thus, as a test, I connected a serial cable to the M1 itself and updated the firmware from 5.2.10 to 5.2.30.  Still, the M1XEP will not connect.

Any suggestions on what I might try next?

Thank you!

[Brad Weeks]

Make sure you are running ElkRP2 version 2.0.41:

• Click Setup, Options, Network Adapters
• Under the Network Adapters in the dropdown you should see the IP Address of your PC on the Local Area Network
• Select , Click OK and close the Network Adapters screen
• The M1XEP and your PC should be on the same network for example the M1XEP at 192.168.1.100 and the PC at 192.168.1.120
• On the Account Detail Screen under the System URL/IP this will be the IP of the M1XEP
• Port 2601
• The Options to Connect Non-Secure should Not be checked
• Try the connection again

[Joel Blackthorne]

Thanks for the feedback.  The issue was “operator error”.  I was so focused on firmware and bootloader versions that I forgot to clear the user name and passwords from my M1XEP profile, which is why the connection attempts were failing.  Once I cleared the user names and passwords, the SSL connection worked fine.  Elk hardware is awesome!

[Author]

Posts