› M1 Support Forum › Elk issue after power failure
- This topic has 3 replies, 2 voices, and was last updated March 31, 2023 at 12:01 pm by Robert Du Gaue.
March 27, 2023 at 1:24 am #6788BEn Davis
Hi all. A couple days ago after a random power outage, my elk m1 powered back up, but can no longer communicate with it. This includes the wall keypads, which are showing a communication error message. On the M1 panel itself I am not seeing any error messages. Meaning the status light is blinking once per second and the ethernet port looks like it’s operating properly. I tried cutting power and plugging everything back in but that did not solve the problem. If anyone has ever experienced this and has any troubleshooting steps, that would be much appreciated.March 28, 2023 at 4:33 pm #6790Robert Du Gaue
Is your M1XEP set for DHCP or Static? Try to use the M1XEP defaults, I’ve had it factory default itself sometimes with power issues and static loosing it’s config so have to switch to DHCP or use the default static IP. For default static, you’ll need to setup you PC/Laptops IP to the network the M1XEP is on. IP address is 192.168.0.251, so set your PC/Laptop to 192.168.0.5 and try with that. There’s also a jumper on the M1XEP that you can use to default that if it’s in an unknown state.
From the manual:
“Note the IP address in the third column. This is the address used to connect/communicate with the M1XEP. Remember, if a DHCP server is on the network and the M1XEP is still set for DHCP (factory default), this number will most likely be a “dynamic” address. However, in the absence or failure of a DHCP server, the M1XEP will default to its last static IP address, which is set from the factory to 192.168.0.251. To force the DHCP/IP address settings to known values, please refer to the troubleshooting section of this manual on page 25″March 29, 2023 at 2:17 pm #6791BEn Davis
Thank you! This got me pointed in the right direction. The IP address had indeed changed. Oddly it changed to a vlan that doesn’t exist. 192.168.3.68. As far as I know, the unit has never had that IP address or existed on that vlan. I fixed it by temporarily creating that vlan at which point I was able to access it and change the IP address back.March 31, 2023 at 12:01 pm #6792Robert Du Gaue
Great! It likely did have that IP sometime during its lifetime. I’ve had it reset to an old IP also that I used to use. I’ll usually change the jumpers to DHCP, get it back to something known, then reconfigure static. Last time it happened though I ended up giving it a fixed IP through the router’s MAC address table and left it on DHCP. That was a couple of years ago and I’ve never had it happen again. 🙂
- You must be logged in to reply to this topic.