First let me say that this was my first experience with alarm systems and I did not understand things as well when I first installed it in April as I do now. I mention this because I may have misunderstood what I was looking at and reporting things incorrectly early on.
I began this thread with the problem where the system voiced an open zone in area1 when arming area2 and that threw me for a loop for a week. It ended up with elk telling me that the system behaves this way. They don't call it normal or abnormal but just say that it is what it is. So I wasted a week or so on that and now consider it to be normal.
Yes, originally I had the p212s in the garage and the TWA in the house powered from the M1. In addition to the area1/area2 chime problem the voice chime would also announce a zone violation at random. It was always a zone that was violated but it had been violated for some time like a window that was open all day. I could be sitting watching tv and suddenly it would just speak a zone name for no apparent reason. When I removed the p212s and garage components the M1 ran well with both the twa and the xrftw. When I attached the p212s and garage components the problem came back.
After some trial and error we learned that it worked well without the xrftw. and elk agreed to replace the wireless system. In post #66 I arrived at a stable system sans xrftw. It was while the xrftw was in the mail that I moved the p212s up to the house and removed the twa.
When the new xrftw arrived I installed it and the system ran well. I added the TWA and the random chimes returned. This is when we turned our attention away from the wireless and towards the possibility of an overload problem. I offloaded the twa to the p212s. After that the chimes were less frequent but I started getting control startup errors in the log and xep restores. This is when I started twisting wires together to carry the power to the garage and the xep restores disappeared and the controls startups were less.
Today I reinstalled the firmware again just for peace of mind and the randoms chimes became very frequent. I immediately cycled the power on the system and go figure - it is running perfectly since....except for one thing.
Now you guys are going to think that I'm making this crap up but something new is happening here. Today I erased the error log using elkrp2. That seemed to work and the log is clear in elkrp2 and the log is clear in M12TOGO but the log is a mess in ekeypad. Ekeypad error log shows a string of "flash memory error trouble" messages. And what's weird is that they are dated Sep 26....two days ago. I'm looking at this as an ekeypad app problem and ignoring it for the time being.
Mike.
I began this thread with the problem where the system voiced an open zone in area1 when arming area2 and that threw me for a loop for a week. It ended up with elk telling me that the system behaves this way. They don't call it normal or abnormal but just say that it is what it is. So I wasted a week or so on that and now consider it to be normal.
RAL said:Mike -
I went back and re-read this entire thread. Let me summarize what I came away with and then tell me if I've got it right.
1) In your original configuration, with the P212S in the garage, it seemed like there was a data bus problem of some sort, perhaps caused by the M1XRFTW wireless adapter. You found that after replacing the XRFTW, it worked ok without the TWA connected, but problems came back when you connected the TWA in addition to the XRFTW. And if you disconnected the XRFTW, it worked ok with the TWA connected.
Yes, originally I had the p212s in the garage and the TWA in the house powered from the M1. In addition to the area1/area2 chime problem the voice chime would also announce a zone violation at random. It was always a zone that was violated but it had been violated for some time like a window that was open all day. I could be sitting watching tv and suddenly it would just speak a zone name for no apparent reason. When I removed the p212s and garage components the M1 ran well with both the twa and the xrftw. When I attached the p212s and garage components the problem came back.
After some trial and error we learned that it worked well without the xrftw. and elk agreed to replace the wireless system. In post #66 I arrived at a stable system sans xrftw. It was while the xrftw was in the mail that I moved the p212s up to the house and removed the twa.
When the new xrftw arrived I installed it and the system ran well. I added the TWA and the random chimes returned. This is when we turned our attention away from the wireless and towards the possibility of an overload problem. I offloaded the twa to the p212s. After that the chimes were less frequent but I started getting control startup errors in the log and xep restores. This is when I started twisting wires together to carry the power to the garage and the xep restores disappeared and the controls startups were less.
Today I reinstalled the firmware again just for peace of mind and the randoms chimes became very frequent. I immediately cycled the power on the system and go figure - it is running perfectly since....except for one thing.
Now you guys are going to think that I'm making this crap up but something new is happening here. Today I erased the error log using elkrp2. That seemed to work and the log is clear in elkrp2 and the log is clear in M12TOGO but the log is a mess in ekeypad. Ekeypad error log shows a string of "flash memory error trouble" messages. And what's weird is that they are dated Sep 26....two days ago. I'm looking at this as an ekeypad app problem and ignoring it for the time being.
Yes while the xrftw was in the mail to elk I moved the p212s to the house thinking that I made a bad decision putting it outside in the first place and I initially used 1 twisted pair for power. It is when I noticed low voltage in the garage that I added the other pairs. I think that it was system restores that made me notice the low voltage.RAL said:2) Because of winter temperatures in the garage, you decide to move the P212S into the house and power the devices in the garage from there over the Cat5e cable, using 3 pairs to provide the power.
I have gone through the same thought process.RAL said:Assuming I have these facts right, here's what's bothering me.
Item 1 makes it seem like there is a power supply loading problem on the M1 itself. It appears that when you decrease the load by removing the TWA or the XRFTW, the problem goes away.
But item 2 makes it seem like there is a problem with the devices in the garage not getting adequate power. I guess it's possible that moving the P212S created a second problem. But I wonder....
Don't apologize, I'm open to all suggestions. DEL has also recommended a separate ps for the twa. On the one hand I would love to get to the bottom of this and on the other I am thinking about just moving the p212s to the garage, disconnecting the TWA and if it runs well I can call it a day. I don't really need the twa and I don;t think that it's worth running another power supply just for it alone.RAL said:Since moving the P212S back to the garage is easy for you to do, that seems like a good next step. But I suspect that you will see the earlier problems with the TWA and XRFTW return.
If that happens, I'm thinking it would make sense to try and provide a separate power source for the TWA and see if that fixes things. It would be nice to get some understanding of whether this really is all a power problem, and a separate power supply for the TWA might be a way to prove that.
I apologize for throwing another suggestion at you at this point. Just thinking about all the things you've seen and what it could mean.
Mike.