Elk M1 Problem

Mike P

Active Member
Hi,

Any help here would be great. I left for work this morning and noticed my pond lights were on(output). while at work I checked my Ekeypad on my iPhone and it had the output off. go home lights still on. checked the panel and the relay was energized and I could not get it off. I tried to reboot the panel, no luck. Everything at this point except for the pond light is working fine. I went to RP and reset the XEP. After that, all seemed ok, except for the pond light. Then I noticed the time and date were all 0's. I went back to RP and tried to sync the time and date with my pc. It did not work, and I started getting error messages back. I did a send all and got system returned invalid info. back.

Has anybody had this happen before? Any suggestions?

Alarm portion of system is working except for sirens. Tested, all signals went out.

I would hate to have to buy a new panel just to send this one out for repair if that is the case.

Any help would be great.

Thanks,

Mike ;)
 
I saw some similar behavior when I first installed my M1XOVR and M1RB; no matter what I did, some outputs weren't responding the way they were supposed to. I did reset the board (power cycle) and haven't had an issue since; never really knew what was going on.
 
I think EL is pretty good at quick turnaround for a repair of a main board. Call them tomorrow and ask or call the dealer you purchased from. Elk may find it cheaper for you to replace then repair but it can go either way.

Bottom line is it cant hurt to ask them.
 
You might consider using the PC motherboard troubleshooting method where all unnecessary devices are removed in order to restore system back to “infantile state.†It’s possible that an add-on card or current drawing sensor has partial short circuit. After rebooting, check the input voltages, zone voltages, rs-485 errors, etc… If you are using M1XEP, you may have to revert back to serial RS-232 operation. If you can get, the date/time operating correctly and walk test works, then you can add one new item back to your system and retest until you find one that is induce problem.

I used this technique to track down a badly terminated RJ-45 cable that was causing sporatic RS-485 bus errors.
 
Back
Top