EST3 Modcom Problem

[ThePeck]

First time posting but have used this forum a lot finding answers.

So anyway for my first question, I got an EST3 Panel that is having a problem transmitting to a Bosch 6600 receiver. The Fire Alarm and Troubles transmit fine and they are being received. But the Supervisory isn't showing in their log. The ModCom says it's sending, connecting and then finishes without an error.

I have the Fire Inspector saying it's a program issue and/or panel issue. Then I have the programmer saying it's the Bosch 660 Receivers issue. And I'm stuck in the middle trying to figure it out before they start fighting lol. I'm the NICET supervisor on-site (Overseas USACE project). Previously, months before, the receiver seemed to work. Although they hadn't programmed out account number yet and for some reason the receiver was getting gibberish. It was chalked up to that it hadn't been programmed yet. So after programming finally when the Inspector on site we tried it and everything but the Supervisory is coming in.

So anyone have any experience with this receiver or the seen a similar problem with the programming on the ModCom? Thanks!

[Leo]

I would bet you are using CID, It could just be the phone lines.
I have had problems with CID on some phone lines,
have you try using a different receiver
did you run a report to see what it is sending to the CS

have you used a Telguard Radio?
this would most likely find the problem for you.
I use the TG7 telguards.
what this will do for you is..
first it will bypass the phone lines.
you can quickly switch receivers and check the account number the panel is sending.
you can have the TG7 use the account number and receiver phone numbers in the panel or change it via your login account at Telguard.

[ThePeck]

Yep we sure are using CID.

Well the problem seems to be the code that is being sent because the receiver picks up and transmit the code and evidently everything goes well because our panel is receiving the acknowledgment that is was received and the panel doesn't try to re-send.

I'm not familiar with Telguard but I did go to the site and look it up. Unfortunately it'd probably not be an option. Since this is a US Navy project and the CMS is on base and we're using the base phone network.

The receiver in the CMS I don't really have access to. And any communication with the CMS is hard to get as far as helping us fix this situation. I can pretty much only contact the non-emergency line and ask them if they have received anything on their end.

You have any knowledge about this 6600 receiver? Could it be that it's not programmed right? Or is there even any programmable CID codes. They say they just input the account number and that's the extent of their programming.

Thanks again!

P.S. I have also attached the SDU file in case anyone wants to take a look at it and it would be appreciated. I also sent it to the EST local rep in Saudia Arabia and waiting to hear back. He's not much help though evidently. Before when we couldn't get the Trouble signal to transmit, his solution was just "not to transmit the trouble signal" and remove it from the program entirely. lol

[Leo]

find any panel/dialer and from outside the base and send CID to the 6600
from a dialer that in not being used or a customer
go to a customer that uses CID that you can change the CS info (account number receiver phone numbers) quickly.

because if it is the 6600 you will need to prove it

[ThePeck]

Sounds like a plan, I thought about that as well. I found out there's another EST3 on base and asked around where it's at. Tomorrow I'm going to try to take the programmer along with the Fire Chief and go test their supervisory and grab it's program.

[Old fire alarm guy]

Hi - I've been looking around on here too. Note that if there is a typo in the CID event (1st 3 digits) it won't send or the receiver will interpret the code incorrectly.

I used to do some EST programming years ago - here's a copy of some rules I used in the NYC area for CID events:

{**********************************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";


{********************************************************************************************************}