I just recently got my Elk M1 panel all wired up and now I'm to the point of getting the wireless sensors installed and communicating with the panel.
I have the Elk M1XRFEG connected and wired up and I have a few different style sensors (NX-455 and Ion plunger-g) laying around that I have for testing to make sure everything is working fine.
My problem is with the ION Plunger-G sensors. They enrolled fine and shows the state change when the plunger is actuated, but on initial power up of the M1,they will sometimes show 'OK' even though the zone is 'Violated'. If I cycle the plunger it then shows the zone is violated and works fine from that point on. At first I thought maybe the sensor was sticking but I don't believe that is the case because it works perfectly after doing the initial cycle.
To make it even a little more confusing, sometimes after powering up the panel, the zone will report as 'Force Armed'. After cycling the plunger one time it works as expected showing the zone as violated. This behavior seems normal to me, and I would expect it to do this everytime rather than sometimes showing the zone is secure on power-up when it isn't.
Any ideas?
I have the Elk M1XRFEG connected and wired up and I have a few different style sensors (NX-455 and Ion plunger-g) laying around that I have for testing to make sure everything is working fine.
My problem is with the ION Plunger-G sensors. They enrolled fine and shows the state change when the plunger is actuated, but on initial power up of the M1,they will sometimes show 'OK' even though the zone is 'Violated'. If I cycle the plunger it then shows the zone is violated and works fine from that point on. At first I thought maybe the sensor was sticking but I don't believe that is the case because it works perfectly after doing the initial cycle.
To make it even a little more confusing, sometimes after powering up the panel, the zone will report as 'Force Armed'. After cycling the plunger one time it works as expected showing the zone as violated. This behavior seems normal to me, and I would expect it to do this everytime rather than sometimes showing the zone is secure on power-up when it isn't.
Any ideas?