M1 Dealer Site  
Search

Any term All terms

Main Menu
Home
FAQs
Bulletin Board (Forums)
Site Search
Downloads **
Email Elk Tech Support
M1 Training Videos
RP Training Videos
XEP Training Videos
XSP Training Videos
Webinar Training Videos
Go to Main Elk Website

View Topic
Forums :: M1 & M1EZ8 Controls :: M1XEP doesn't connect after latest update

| Reply Reply |
M1XEP doesn't connect after latest update
Posted by dzazzo on 02/03/2010 09:16 PM

Greetings - Installed the latest firmware on the M1XEP, updated the bootloader first as per the directions, then updated the firmware, and now none of the ElkRP (1.6 or 2.0) will connect to it. Please advise. DZ

Re: M1XEP doesn't connect after latest update
Posted by bradweeks on 02/04/2010 10:31 AM

After a Firmware Update you will need to wait the full 8-minutes for the M1XEP to reboot before trying to connect. After waiting 8-minutes are you able to "Find" the M1XEP on your LAN? If so from the RP Account Details Screen change the Port from 2601 to 2101 and try to connect. Once connected click the M1XEP Setup and click "Send" to make sure all your settings are sendt back to the M1XEP.

Re: M1XEP doesn't connect after latest update
Posted by inline on 02/05/2010 06:38 AM

Hi, pretty common issue, I experienced it to. Can you ping the m1xep? I had to powercycle it and then noticed email sending was not working, so I did a send all and reboot. All was working after that. See this thread for more: http://www.cocoontech.com/forums/index.php?showtopic=15607

Edited by inline on 02/05/2010 06:39 AM

Re: M1XEP doesn't connect after latest update
Posted by GTJill on 02/10/2010 02:10 PM

I did the M1XEP bootware (1.2.0) & firmware (1.3.10) upgrades, waited 10 minutes, but I can no longer connect. A power cycle didn't help either. I can "Find" the XEP and it shows the correct IP address and port (2601), but I cannot connect. It will not connect using the unsecure port (2101) either, but I believe that I had that disabled prior to the upgrade. When I try to connect via web browser ("Virtual Keypad"), I get the "Please wait..." screen from the XEP, followed by a "Failed to Connect" pop-up that says "Unable to connect. Another device may already be connected." I've connected to the control via the phone line and also by removing the XEP and hooking up via serial. Everything looks fine. Tried re-enrolling and verifying that panel says "XEP=Yes". Control is running latest (5.1.24) firmware. Any ideas?

Re: M1XEP doesn't connect after latest update
Posted by jcurtiss on 02/10/2010 04:15 PM

I had the same problem. I found even though the ELKRP software returned the correct IP address assigned from my DHCP server the M1XEP actually went to it's default IP address of 192.168.0.251. The software must store this address within the PC. I confirmed this by direct connecting to the M1XEP and manually configuring my laptop to an IP address of 192.168.0.100 and I was able to successfully connect. To resolve mine I powered down the M1XEP and reset my router while the M1XEP remained off line. When I restored power to the M1XEP it obtained a new IP address from the router and I connected with this IP address.

Re: M1XEP doesn't connect after latest update
Posted by bradweeks on 02/10/2010 06:38 PM

If the M1XEP is set to DHCP Mode and is not assigned an IP Address by the router the M1XEP will default to 192.168.0.251. After an update the M1XEP will need approximately 8 minutes to reboot but once the reboot is complete you should be able to Find, highlight the IP Address, click Use Selected and then try your connection. If not please try the following:
Power down the M1XEP and back up while connected to the LAN
Wait for the M1XEP to reboot indicated by the Green LED flickering with data traffic on the LAN then Find , Use Selected and Connect
If not able to connect refer to page 25 of the M1XEP Installation Manual under "Forcing the DHCP/IP Address Setting to Known Values" and use the JP2 jumper to set the M1XEP into DHCP Mode.
When the Green LED is blinking 1 blink per second remove the JP2 jumper and let the M1XEP Reboot.
Once the Reboot is complete "Find" the M1XEP, highlight the IP Address and click Use Selected, click the TCP/IP Setting Tab and click Copy.
Next click Connection icon and Network

Re: M1XEP doesn't connect after latest update
Posted by mohansen on 03/03/2010 11:41 PM

I have tried all of the above and I still cannot connect to the M1XEP. I get "Failed to Connect to Server". I have tried DHCP, 2101, 2601, power off, etc. I waited probably 10-15 minutes after the firmware update before I tried connecting. I will try connecting via serial but not sure what I will be able to do unless the upgrade did not complete properly.

Re: M1XEP doesn't connect after latest update
Posted by mohansen on 03/03/2010 11:53 PM

I was able to successfully connect via serial and everything looked normal. I was not able to see the M1XEP which made sense. I did a save and then moved the serial cable back to the M1XEP and was able to connect. It then disconnected me after I did a Send All. I was able to reconnect and changed my IP from DHCP back to static. Still not clear on why connecting via serial worked but wanted to share my experience with others.

Re: M1XEP doesn't connect after latest update
Posted by billakers on 03/07/2010 09:25 PM

This hit me as well. After waiting for 30 minutes, I was still unable to reconnect. Power cycling did nothing to fix the problem. I was able to ping the IP address, but I could not connect. I scanned the port with NMAP, and the XEP wasn't even listening on port 2601:

$ sudo nmap -sS 192.168.0.251
Starting Nmap 5.21 ( http://nmap.org ) at 2010-03-07 08:51 EST
Nmap scan report for 192.168.0.251
Host is up (0.026s latency).
Not shown: 997 closed ports
PORT STATE SERVICE
21/tcp open ftp
26/tcp open rsftp
80/tcp open http
MAC Address: 00:40:9D:3D:7D:17 (Digiboard)


I tried power cycling the XEP several times, with no luck. Finally, even though the XEP was already statically using 192.168.0.251/24, I "reset" the IP address using the jumper on the board.

After this reset, the XEP started listening on 2601 again:

$ sudo nmap -sS 192.168.0.251
Starting Nmap 5.21 ( http://nmap.org ) at 2010-03-07 10:11 EST
Nmap scan report for 192.168.0.251
Host is up (0.026s latency).
Not shown: 996 closed ports
PORT STATE SERVICE
21/tcp open ftp
26/tcp open rsftp
80/tcp open http
2601/tcp open zebra
MAC Address: 00:40:9D:3D:7D:17 (Digiboard)

So I guess that "resetting" the IP address with the jumper does more than just change it back to the last static address. It was somehow able to get the service listening on 2601 again.

Edited by billakers on 03/07/2010 09:26 PM

Re: M1XEP doesn't connect after latest update
Posted by GTJill on 03/09/2010 02:15 PM

I was also able to get it back using the procedure to change the IP to DHCP and back to static (Thanks Brad!). Doesn't make sense, since the IP was correct and ping-able, but it did fix the problem. Quite odd.

Re: M1XEP doesn't connect after latest update
Posted by podryna on 05/27/2010 12:55 AM

I've also experienced the same problem with a new install. IP was static before update. It's found after update, but can't connect. Ping is OK. Attempts to connect via browser gives message about not connecting because some other device may already be connected. Power cycling and reboot everything (including the computer) do not help.

Thanks to Brad, the force back to DHCP does the trick. However, the instructions are incomplete. For those that don't have page 25 of the user manual (which I usually would have lost except that this is a new machine), here it is:
1. Power down the M1XEP. Place a shorting jumper across the two pins of JP2 (ed. this is to the top left of the ENet connector... hopefully you can find a jumper). Power the M1XEP back up.
2. After a few seconds, the green LED on the RJ45 connector will blink five times. About 30 seconds later, the green LED will blink and repeat in a 'coded' fashion, indicating either DHCP or STATIC modes. If set for DHCP mode, there will be 1 quick blink. If set for STATIC mode there will be 2 quick blinks. When the B1XEP is forced to STATIC mode its address will become 192.168.0.251.
3. If the blink indicates the wrong mode, power the unit down and back up to force it to the opposite setting.
4. When the green LED indicates that the M1XEP is at the desired setting, remove the shorting jumper from JP2 and the allow the M1XEP to continue booting up. This may take another minute.

Note that you HAVE TO REMOVE THE JUMPER to allow the unit to complete its boot up procedure. Make sure the green light is in the right blink sequence for your desired mode.

I don't have the patience to see if those who do the upgrade in DHCP mode have this problem. Maybe the company engineers can do some testing? Or maybe just fix the software?

Happy updating. -Peter

Edited by podryna on 05/27/2010 12:57 AM

Re: M1XEP doesn't connect after latest update
Posted by dougr222 on 06/02/2010 04:14 PM

Thank you - this helped. Jumper booting the M1XEP into DHCP, "finding" it with ElkRP2 which allowed connecting to the control, and then setting the M1XEP's static address back to what I want.

Re: M1XEP doesn't connect after latest update
Posted by simonw71 on 06/07/2010 01:52 AM

Greetings - I have been having the same "can't connect, another device may already be connected" errors during the setup of my port forwarding. I can connect to the virtual keypad inside my local LAN, but when I connect from the outside with ports 80 and 2601 forwarded to the M1XEP, I get asked for a password, get a blue background image, and then nothing for ages until the timeout message. If I go back to connecting inside my LAN, all is fine again. Can anybody explain that or help me figure out how to test the possibilities? Thanks very much! Simon

Re: M1XEP doesn't connect after latest update
Posted by bradweeks on 06/07/2010 07:52 AM

Did you also port forward Port 26?

Re: M1XEP doesn't connect after latest update
Posted by simonw71 on 06/08/2010 01:54 AM

Brad - yes, port 26 also forwarded with 80 and 2601. I also ran an NMAP scan. It says ports 21, 26, 80 and 2601 are open - but not 2101 which is odd because it should be open according to the M1XEP setup. But my ISY-99 can't see the Elk on port 2101 so I do believe this. Should I run the M1XEP jumper 2 reset and reboot sequence as described in the posts of this topic? I already tried selecting reboot from ElkRP and it doesn't seem to help. Simon

Edited by simonw71 on 06/08/2010 02:11 AM

Re: M1XEP doesn't connect after latest update
Posted by AnthonyCalia on 12/06/2010 02:32 AM

This is why I always check the forums first. Most of the time, whatever problem I'm seeing, someone has suffered before me! I, after upgrading the M1XEP firmware had exactly the same problem. After reading the previous posts, and running a port scan on my fixed IP address, I was convinced that the problem was in port 2601 not being open. I did one last power cycle of the M1XEP, but this time waited about ten minutes before attempting to connect, and for reasons unknown, everything now works. Bottom line, I'm not sure what was not working, and it seemed to heal itself with time. I guess it would be nice to have a definitive answer, but this will have to do for now. Anthony

| Reply Reply |