M1EXP

pitbull

Member
Hi everybody,
 
I just changed my router and now I can connect to my M1EXP anymore. I also cant access my ISY99 but would like to solve the M1 first. Is their anything I need to do to gain access once again since I changed my router? Is this a port forwarding issue?
 
The M1xep has probably been dynamically assigned a new IP address by DHCP in the new router. If true you will need to log into the router, determine the IP address of the m1xep and then tell the Elk control the new address using the keypad or elkrp.
 
Mike.
 
Sorry but that I do not know because it is different for each router. Generally speaking you need to log into the router using your web browser and learn to navigate through it's menus. You should be able to learn what you need to know from the routers owner manual or maybe you can find someone with some experience to help you.
 
Mike.
 
1) Open ElkRP
2) Establish the Network connection with your system
3) From the Account Details page, select the M1XEP Setup button
4) From the M1XEP Setup window, select TCP/IP Settings
 
The page may look similar to this:
index.php

 
The key is the radio button that says, "Assigned an IP address via DHCP".
 
I'd highly recommend setting it up to a static address. I always select an address outside the DHCP range of your router, but that's not necessarily required.
 
As the secure port section reads, if you are accessing this outside of your LAN, then you do need to have the secure port setup (port forwarded) on your router as well.
 
drvnbysound said:
1) Open ElkRP
2) Establish the Network connection with your system
3) From the Account Details page, select the M1XEP Setup button
4) From the M1XEP Setup window, select TCP/IP Settings
 
The page may look similar to this:
index.php

 
The key is the radio button that says, "Assigned an IP address via DHCP".
 
I'd highly recommend setting it up to a static address. I always select an address outside the DHCP range of your router, but that's not necessarily required.
 
As the secure port section reads, if you are accessing this outside of your LAN, then you do need to have the secure port setup (port forwarded) on your router as well.
Can you establish a connection to the elk ethernet system without knowing the ip address of the elk adapter? Can RP find the adapter?
 
Mike.
 
There is a Find button on the M1XEP's introduction page.  
 
For the ISY if you go to this link you will be able to login.  http://www.universal-devices.com/99i/
 
Agree with drvn, it is a good idea to assign static ip's to both of these, make sure they are not in the DHCP range on your router.  If you go into your router, you should be able to assign a range to DHCP, you should be able to narrow that range and leave some room for static IP's for the Elk and ISY.
 
I did set up my M1EXP with a static IP address. Now I guess I need to figure out how to have the router programmed with this address. Very different than the one I previously had
 
The weird thing is that both the M1EXP and ISY wont connect anymore when I launch the icon I normally use.
 
Perhaps it would be easiest for you to use the jumper technique to put the M1XEP back into the DHCP mode.  Refer to the instructions.  Then your router should automatically assign an appropriate IP address and ELK RP2 should be able to find the M1XEP.  Once you are connected, you can set the automatically assigned IP address as the new static IP address.  This isn't the technically correct approach, but I get the impression that we would end up doing a week's worth of Q&A otherwise. :unsure:
 
Some brands of routers use different ranges of addresses for DHCP vs static than other brands.  Have you checked your new router to make sure the DHCP range doesn't conflict with the static IP addresses you've assigned?
 
The IP address the M1EXP was set with by the previous router does show to now be within the DHCP of my existing router.
 
jpmargis said:
Perhaps it would be easiest for you to use the jumper technique to put the M1XEP back into the DHCP mode.  Refer to the instructions.  Then your router should automatically assign an appropriate IP address and ELK RP2 should be able to find the M1XEP.  Once you are connected, you can set the automatically signed IP address as the new static IP address.  This isn't the technically correct approach, but I get the impression that we would end up doing a week's worth of Q&A otherwise. :unsure:
it works nice thanks. Should I now change it to something outside my routers DHCP?
 
pitbull said:
Should I now change it to something outside my routers DHCP?
 
That would be the best way to tell if the problem was caused by a conflict between the static address that it had originally and the DHCP range.  When you have a static address assigned that is within the DHCP range, it's possible that DHCP will assign that address to some other device on the network. It doesn't know that it is also assigned to the ELK.  Once you have two devices assigned to the same address, all sorts of strange things can happen.
 
so does that mean I simply change the address and then have the info sent to the M1EXP.  (don't need to connect with a hard wired right) Also when you say assign an address outside the DHCP range you mean the last set of number need to be below or above the range my router would normally assign an IP address right? Sorry still learning
 
The DHCP server in the router allows you to specify a starting and ending address for the addresses to by used by DHCP.
 
For example, on my router,DHCP is set up to start at 192.168.1.100 and end at 192.168.1.254.   That leaves 192.168.1.2 through 192.168.1.99 for static addresses.
 
You didn't say what fixed address you had the M1XEP assigned to originally, but let's say it was 192.168.1.4.   If you change the XEP configuration back to this, 
and then set the router's DHCP start address to something greater than that (and also greater than the ISY99, if that also has a fixed address), you should be ok.
 
In general, it's nice to set DHCP to leave a reasonably large block of addresses for static addresses and let DHCP manage the rest.   For most home networks, you probably won't have a reason to assign more than a handful of static addresses.   Setting DHCP to start at .100 gives you more room than you're likely to ever need, while leaving plenty of dynamic addresses as well, so you'll probably never have to change the configuration.
 
Back
Top