Hello All,
So I have an EST 3 system SDU version 3.74…multiple story building, multiple nodes. The issue that I am having is that when the building engineer disables a smoke detector (SIGA PS), central station receives a ground fault trouble however, the panel does not show a ground fault…only the disable. Prior to said disable, panel is normal…no ground faults present. Any insight to this…anyone come across this before.
If the central station is using contact ID, the EST might have the wrong code programmed into it. It’s not like other system where you program the dialer with the numbers for central and you’re done. You have to tell the MODCOM what codes to send. Pasting some rules for MODCOM events below:
{MODCOM RULES**********************}
{ CHANGE ‘ACCT’ & X’S TO MATCH PROGRAM AS NEEDED }
{ THIS IS TO SEND EVERY DEVICE. IF GENERAL, CHANGE LAST 3 DIGITS TO 001, 002, ETC. FOR ZONE #'S }
[MODCOM_LOCAL_ALARM]
LOCALALARM ‘Unprogrammed_Device_Data_Card_<N:101,102,201,202,301,302>’ : +SEND ‘ACCT’ MSG “111000<N:3>”, {CHANGE LABEL FOR SSDC}
-SEND ‘ACCT’ MSG “311000<N:3>”;
[MODCOM_FAIL_SAFE]
ALARM ‘Fail_Safe_Event_00_00’ : +SEND ‘ACCT’ MSG “114000000”,
-SEND ‘ACCT’ MSG “314000000”;
[MODCOM_TROUBLE]
CMSFIRSTTROUBLE : +SEND ‘ACCT’ MSG “130000000”,
-SEND ‘ACCT’ MSG “330000000”;
[MODCOM_SUPV]
FIRSTSUPERVISORY : +SEND ‘ACCT’ MSG “120000000”,
-SEND ‘ACCT’ MSG “320000000”;
[MODCOM_SMOKE]
ALARM ‘SMK_<N:X-XX,XX-XX>’ : +SEND ‘ACCT’ MSG “111100<N:3>”,
-SEND ‘ACCT’ MSG “311100<N:3>”;
[MODCOM_ELEV_SMOKE]
ALARM ‘SMK_ELEV_<N:X-XX,XX>_*’ : +SEND ‘ACCT’ MSG “111100<N:3>”,
-SEND ‘ACCT’ MSG “311100<N:3>”;
[MODCOM_HEAT]
ALARM ‘HEAT_<N:XX>’ : +SEND ‘ACCT’ MSG “111400<N:3>”,
-SEND ‘ACCT’ MSG “311400<N:3>”;
[MODCOM_PULL]
ALARM ‘PULL_<N:X-XX>’ : +SEND ‘ACCT’ MSG “111500<N:3>”,
-SEND ‘ACCT’ MSG “311500<N:3>”;
[MODCOM_FLOW]
ALARM ‘FLOW_<N:X-XX>*’ : +SEND ‘ACCT’ MSG “111400<N:3>”,
-SEND ‘ACCT’ MSG “311400<N:3>”;
[MODCOM_PUMP_RUN]
SUP ‘SUP_XXX’
: +SEND ‘ACCT’ MSG “120000001”,
-SEND ‘ACCT’ MSG “320000001”;
[MODCOM_PUMP_FAIL]
SUP ‘SUP_XXX’
: +SEND ‘ACCT’ MSG “120000002”,
-SEND ‘ACCT’ MSG “320000002”;
[MODCOM_LINE_1_TRBL]
LOCALTROUBLE ‘Telephone_Line_1_01_05’ : +SEND ‘ACCT’ MSG “135100001”,
-SEND ‘ACCT’ MSG “335100001”;
[MODCOM_LINE_2_TRBL]
LOCALTROUBLE ‘Telephone_Line_2_01_05’ : +SEND ‘ACCT’ MSG “135200002”,
-SEND ‘ACCT’ MSG “335200002”;
[MODCOM_BATT_TRBL]
LOCALTROUBLE ‘Batt_Trbl_01_03’ : +SEND ‘ACCT’ MSG “130200001”,
-SEND ‘ACCT’ MSG “330200001”;
[MODCOM_AC_FAIL]
ACFAIL ‘AC_Brownout_01_03’ : +SEND ‘ACCT’ MSG “130100001”,
-SEND ‘ACCT’ MSG “330100001”;
{********************************************************************************************************}
Excellent. Thank you for your insight…I will look into the MODCOM rules.
Here’s a list of contact ID codes:
http://library.ademconet.com/MWT/fs2/MX8000/Contact-ID-codes-with-explanation.PDF
Others have been spot on and it’s very likely someone missed a number in the rules on the output side for the code.
Couple of questions, though. 3.74 is rather old now. Do you have the ability to upgrade to the most current which is 5.1’ish (don’t have the laptop open right now but it’s around that)? How large is this system?
I ask those questions because with the release of the EST3X there is now an option to have all cms codes auto generated. EST will tell you it’s not designed to work on a standard EST3, but it will. With that said, it would be very important to check the warnings and cms report to make sure nothing is missing. I say that because using this setting once with a rather large system generated errors where it didn’t auto generate everything which forced me to go back to old school of writing the rules.
Its one of my biggest complaints with the while 3-MODCOM and there failed attempt at the Synergy line. It’s just over complicated and leaves so so much up for error to the programming technician.
Sorry to bump an old thread - I just joined the forums yesterday.