EyezOn Forum

Posted: **Fri Sep 08, 2017 10:58 am**

There was a cellular network problem yesterday that cause my system to generate some trouble codes, including FTC. Looking at my logs from the envisalink, it looks like the initial verbose trouble status (849) was sent, but an update wasn't sent when the system went into FTC state, or when the FTC cleared. The FTC Trouble (814) / Restore (815) TPI codes were sent by the envisalink.

Any idea why there wasn't a verbose trouble status updates around the period from 15:15-49?

Code: Select all

Sep 07 15:11:24 - DEBUG - core/envisalink.py:handle_line@158: RX < 510 - Keypad Led State - Partition 1
Sep 07 15:11:24 - DEBUG - core/envisalink.py:handle_line@158: RX < 840 - Partition Home Trouble LED ON
Sep 07 15:11:24 - DEBUG - core/envisalink.py:handle_line@158: RX < 840 - Partition 2 Trouble LED ON
Sep 07 15:11:24 - DEBUG - core/envisalink.py:handle_line@158: RX < 840 - Partition 3 Trouble LED ON
Sep 07 15:11:24 - DEBUG - core/envisalink.py:handle_line@158: RX < 840 - Partition 4 Trouble LED ON
Sep 07 15:11:28 - DEBUG - core/envisalink.py:handle_line@158: RX < 511 - Keypad Led Flash State - Partition 1
Sep 07 15:11:29 - DEBUG - core/envisalink.py:handle_line@158: RX < 849 - Verbose Trouble Status 01
Sep 07 15:11:29 - DEBUG - core/envisalink.py:handle_line@158: RX < 510 - Keypad Led State - Partition 1
Sep 07 15:11:29 - DEBUG - core/envisalink.py:handle_line@158: RX < 511 - Keypad Led Flash State - Partition 1
Sep 07 15:11:29 - DEBUG - core/envisalink.py:handle_line@158: RX < 510 - Keypad Led State - Partition 1
Sep 07 15:11:29 - DEBUG - core/envisalink.py:handle_line@158: RX < 652 - Partition Home Armed Mode Away
Sep 07 15:12:32 - DEBUG - core/envisalink.py:handle_line@158: RX < 550 - Time/Date Broadcast 09/07/17 15:12
Sep 07 15:15:40 - DEBUG - core/envisalink.py:handle_line@158: RX < 511 - Keypad Led Flash State - Partition 1
Sep 07 15:15:40 - DEBUG - core/envisalink.py:handle_line@158: RX < 849 - Verbose Trouble Status 01
Sep 07 15:15:40 - DEBUG - core/envisalink.py:handle_line@158: RX < 510 - Keypad Led State - Partition 1
Sep 07 15:15:40 - DEBUG - core/envisalink.py:handle_line@158: RX < 511 - Keypad Led Flash State - Partition 1
Sep 07 15:15:40 - DEBUG - core/envisalink.py:handle_line@158: RX < 510 - Keypad Led State - Partition 1
Sep 07 15:15:40 - DEBUG - core/envisalink.py:handle_line@158: RX < 652 - Partition Home Armed Mode Away
Sep 07 15:16:32 - DEBUG - core/envisalink.py:handle_line@158: RX < 550 - Time/Date Broadcast 09/07/17 15:16
Sep 07 15:16:49 - DEBUG - core/envisalink.py:handle_line@158: RX < 814 - FTC Trouble
Sep 07 15:19:13 - DEBUG - core/envisalink.py:handle_line@158: RX < 815 - FTC Trouble Restore
Sep 07 15:19:13 - DEBUG - core/envisalink.py:handle_line@158: RX < 510 - Keypad Led State - Partition 1
Sep 07 15:19:13 - DEBUG - core/envisalink.py:handle_line@158: RX < 841 - Partition Home Trouble LED OFF
Sep 07 15:19:13 - DEBUG - core/envisalink.py:handle_line@158: RX < 841 - Partition 2 Trouble LED OFF
Sep 07 15:19:13 - DEBUG - core/envisalink.py:handle_line@158: RX < 841 - Partition 3 Trouble LED OFF
Sep 07 15:19:13 - DEBUG - core/envisalink.py:handle_line@158: RX < 841 - Partition 4 Trouble LED OFF

System Details: DSC 1832 4.6, EVL-4 1.0.102

Note: the initial trouble was due to a "T-Link Network Fault", which is visible in the eyez-on portal logs, but can't be seen from the Envisalink TPI. The sequence of events as seen from the portal's event log is:

Code: Select all

2017-09-07 15:19:13 - Phone Number 1 FTC Restore
2017-09-07 15:17:38 - T-Link Network Restore
2017-09-07 15:16:48 - Phone Number 1 FTC
2017-09-07 15:11:23 - T-Link Network Fault

Posted: **Wed Oct 18, 2017 12:04 pm**

Didn't see any response to this. Could someone let me know if I'm not understanding things correctly or whether this is/was a bug?

I think 849 Verbose trouble status (849) should have been sent/updated via the TPI with bit 3 - Failure to Communicate set, when the panel decided it had FTC trouble.

Sure, It's a minor point since updated firmware sends both 814 and 815 - FTC Trouble / FTC Restore. (FTC restore 815 was added TPI 1.08 according to the doc, but don't recall which firmware version had the update) But I think for completeness/correctness, unless I'm misunderstanding something, the verbose trouble status bits should have been updated as well.

Thanks.

EyezOn Forum

DSC missed verbose trouble status update for FTC?

DSC missed verbose trouble status update for FTC?

Re: DSC missed verbose trouble status update for FTC?