Recent content by hagak

Ok so I am getting close to just giving up on this, currently the only issue I can see is it takes a few minutes for the zones in the input expander to be "seen" and I get those log messages.  But other then that things function.   I did put the input expander out on its own branch as describe...

So for the first step I could just move the Input Expander from the DBH to be in parallel with the DBH and add a termination jumper to the Zone Expander correct?  This should not be hard to do they are not far from each other.

Just before I read you message I moved it to Address 11 and since I only have wireless in Group 4 I should be fine.   However it does not appear to help anything.  I have received 3 1367 logs since I restarted the panel 10 minutes ago.

Using 5.3.10 firmware. I did measure the voltages AT the expansion boards I have not done a manual calculation however with the system board reading 0.4A that seems to be well within the limits.   I did start reading more of the Elk Wireless expansion and noticed some intersting...

Replaced the RJ45 jacks and made sure the terminal blocks connections were secure.   Still have the issue.  I even rearranged the connections on the M1-DBH to see if the problem board would change (if it is not the Input Expander having a problem but another device ahead of it).  No changes.  ...

Also checked the System Diag. Data Bus errors: Retry T1A1: 00000 Retry T2A2: 00009 Retry T2A3: 00009   These do not appear to be changing.   It reports System Voltage at 13.8V and Current at 0.4A.

Question?  does the Input Exp 3 on the log indicate that it was the cause of the restart or is what restarted?  Since I do not notice anything like keypads flickering or anything is it just the input expander board that is restarting? 

Thanks Ral, will work on terminating the RJ45s.  I also checked the voltage at the boards and it is at 13.85V so that is good and measures the same at each of them.   More info if useful. While the boards are in a Input Ex and Output Ex are in a separate enclosure from the M1 it is right next to...

So in reviewing everything over, I reviewed the wiring instructions again for the M1-DBH and noticed they tell you to use 568A which stood out cause I always wire 568B.  So I double checked and sure enough all of my CAT5 going into the M1-DBH is wired for 568B.  The effect of this is the A line...

I have an input expander connected to an M1-DBH that is causing a lot of log issues with System Restart.  Note that the zones on the expander appear to function correctly but I get these in the logs all the time: 1367 = SYSTEM START UP Input Exp 3 this happens about every 3-5 minutes.     I have...

Ok so I think I have it solved.  And the solution is COSMOD2W.   Anyone with 2-wire smokes on an ELK coming to this thread, just get the COSMOD2W.   Additional benefit is now I get the maintenance signal from my i3 to the panel.   1st test using the F button to trigger the fire and it worked...

Ok so tried the SLOW response at 800ms and that does allow me to silence the alarm but it seems to be latched still and will re-alarm.  Note if I trigger the Alarm from an F-key I do not have this issue.  Also if I take teh RRS-MOD out I do not have any issue resetting the smokes.   Think I am...

<p>Thanks for the reponse.</p> <p>&nbsp;</p> <p>Yep I have JP1 set to 2wire, and the zone is set to FIRE ALARM with Type 2wire. &nbsp;Just last night I found that thread and was reading through it. &nbsp;I may try the Slow Loop Response however if that is the case I like your suggestion of the...

So I was going to post on this thread since it is similar but also very old http://cocoontech.com/forums/topic/3204-outputs/ .   My issue is when i have the RRS-Mod installed and triggered via the Following Rule WHENEVER ANY FIRE ALARM TURNS ON THEN TURN OUT 3 ON   And turn it off with this rule...

That is what I thought.  Guess I can setup a relay across my current water sensor zone for the water alert and add a dedicated zone for burglar so that I can identify it was tripped from a 3rd party sensor.