4010 Problems and Fixes
4010 Problems and Fixes
SolutionBulletin
Fire
SB-990025
REVISION HISTORY:
Revision Revision Date Revised by Reason
A 11/09/1999 R. Silliker To provide an update on reported issues
B 02/28/2000 R. Silliker To Update the Latest Status
C 10/10/2000 D. Langlais To Update the Latest Status
D 03/23/2001 D. Langlais Updates to the following issues
• Intermittent Battery Charger Troubles
• Intermittent Excessively Dirty Trouble on SSD Devices
• Added Revision column
• Added Mandatory/Immediate Action Requirements
• “ANY” command used in equations
E 04/30/2001 D. Langlais Updates to the following issues
• Intermittent Excessively Dirty Trouble on SSD Devices
• Intermittent Battery Charger Troubles
• Erratic Operation and Resound of True-Alert Non-Addressable
(SmartSync) Horns
• True-Alert Non-Addressable (SmartSync) Horns Ping on Reset
• Cannot Reset Isolator Bases
• Cannot Reset Isolator Bases If Wired Class B
• Channel Fail Toggles Between Normal and Trouble
• IDNet Channel Fail instead of Wrong Type Trouble
• IDNet Channel Failure (Sometimes followed by an IDNet Class A
Trouble)
• Intermittent IDNet Channel Failure
• Erratic Operation of True-Alert Non-Addressable (SmartSync)
Horns when Programmed at Address 12
• (Canadian Operation) No Indication of First Stage / Second
Stage Alarm
• 2.02.01 Master (.bin) File for Selective Network Jobs where the
Network Card Toggles Missing Failed
• Cannot Passcode Protect the Function Menu
• No Answer Trouble on Random IDNet Addresses
• COMPARE Opcode in Custom Control does not work in 4010
programmer rev 2.03
• Unable to Acknowledge a 4010 supervisory point over the
network.
• Class A Trouble does not clear on System Reset (MZAM with
Point Types of either Trouble or Utility)
• (Canadian Operation) Operational Concerns when using
CANPUL Device-Type for 2-stage Pull Stations
• Cannot Prioritize Sounder Programming in Custom Control
• WalkTest Horn Operation is Erratic
• Acknowledge Output Opcode does not work
• CFIG Format Mismatch / Restoring to Factory Default
1 OF 22
FIRE
Tyco Safety Products
SolutionBulletin
Fire
REVISION HISTORY:
Revision Revision Date Revised by Reason
F 02/18/2002 D. Langlais Updates to the following issues (Updates have Bolded Text)
• FIXED: Network Ground Fault added under Hardware Issues
• FIXED: Intermittent Wrong Type Trouble on Multi-Sensor Device
• FIXED: Intermittent Excessively Dirty Trouble on SSD devices
• FIXED: All Cards Go Missing Failed and then Clear / as well as N2 Trouble
• ADDED: 4009A IDNet Class A Tbl followed by Fiber Option Card Trouble
• ADDED: Adding a 4010 to an existing network flags all nodes that they need to
be built
• RE-OPENED: IDNet Channel Failure (Sometimes followed by an IDNet Class
A Trouble)
• NOTE: IDNet Channel Failure Instead of Wrong Type Trouble – Corrected
documentation error in the rev E Solution Bulletin
• NOTE: Added info re: Charger Trouble reporting from 4009T
G 07/19/2002 D. Langlais Updates to the following issues (Updates have Bolded Text)
• FIXED: Adding a 4010 to existing Network flags all Nodes that they need to
be built.
• FIXED: Version Control Mismatch After Deleting and Adding Nodes
• FIXED: Next Gen Net Programmer shows No build is necessary
• FIXED: Suppression Programming Turns Off after adding SDACT
• FIXED: 4009A No Answer Trouble and Wrong Type Trouble reports to the
4010, but not to the 4120 Network
• FIXED: Degraded Style 7 Trouble on a Style 4 Network
• FIXED: User Defined Keys - Cannot Change Labels with the 4010 PC
Programmer
• FIXED: Intermittent 4009A Option Card Trouble
• ADDED: IDNet Point in Open Circuit Trouble Clears on System Reset
• ADDED: Error 78, Invalid Network Device
• ADDED: Operational Problems with TRELAY Point Type
• ADDED: Network Operational Problems
• RE-OPENED: All Cards Go Missing Failed and then Clear / as well as N2
Trouble
H 10/10/2002 D. Langlais Updates to the following issues (Updates have Bolded Text).
• FIXED: Ground Fault Condition after Replacing the 4010's LCD Display
• FIXED: Output Abnormal Trouble does not report after Suppression Release
Peripheral has turned ON
• FIXED: SMPL ON Qualifier does not work for SUPABRT Point Type
• FIXED: Operational Problem with SUPABRT Point Type
• FIXED: IDNet Point in Open Circuit Trouble Clears on System Reset
• STATUS UPDATE: The 4010 Programmer now installs to a different path
2 OF 22
FIRE
Tyco Safety Products
SolutionBulletin
Fire
REVISION HISTORY:
Revision Revision Date Revised by Reason
I 04/23/2003 D. Langlais Updates to the following issues (Updates have Bolded Text).
• FIXED: How to Correct Error 119 When Installing a 4010 Programmer Onto a
GCC
• FIXED: 4009A8 IDNet Point Is not displayed in the Suppression Release Point
Tab
• FIXED: How to Correct Invalid Device Type for this Opcode when programming
the FIRE STATE of an IPHOTO
• FIXED: Certain Device Types in 4010 must be placed in a List if the Disable /
Enable Opcode is used in CC
• FIXED: Invalid Device Type for this Opcode is displayed on 4010 PC
Programmer
• FIXED: After making changes to a 4010 Node, the Next Generation Network
Programmers build flags are incorrectly set
• FIXED: Error 78, Invalid Network Device
• FIXED: Unable to Select CANPUL Device Type in the Suppression Tab
• FIXED: Class A Trouble on an IDNet Monitor ZAM Clears on System Reset
Even if Zone is Still Open
• FIXED: IDNet IAM Point in Open Circuit Trouble Clears on System Reset /
Provided P16 is turned ON
• FIXED: 4010 Network Point Priorities coming from a 4100 node, are not being
updated properly at the 4010 node
• FIXED: How to Eliminate Phantom Network Alarms From 4010 Panels.
• ADDED: DE switch mode does not work correctly when 4010 points are being
disabled from a 4120 node
• ADDED: Alarm Silence / System Reset Inhibited After Timer Expired
• ADDED: Entire PRINT STATEMENT does not display on Remote LCD Annunciator
• ADDED: When Walktest Events are sent to a Printer, the Printout is Coded
• ADDED: How To Fix a 4010 Panel whose General Alarm Outputs Do not
Activate on Alarm or Manual Evacuation
• ADDED: Build Error On GCC With Multiloop Network "Loop Style Of Network
Card Does Not Match Other Nodes"
J 07/18/2003 D. Langlais Updates to the following issues (Updates have Bolded Text).
• FIXED: General Alarm Outputs Do not Activate on Alarm or Manual Evacuation
• FIXED: When Walktest Events are sent to a Printer, the Printout is Encrypted
• FIXED: Entire PRINT STATEMENT does not display on Remote LCD
Annunciator
• FIXED: User Defined Keys - Label gets corrupted when job is uploaded
• FIXED: Intermittent IDNet Channel Failure (sometimes followed by an IDNet
Class A Trouble)
• FIXED: All Cards Go Missing Failed and then Clear / as well as N2 Trouble
• FIXED: Unable to turn OFF 4010 Pseudo points from GCC utility buttons
• FIXED: After making changes to a 4010 Node, the Next Generation Network
Programmers build flags are incorrectly set
• FIXED: Alarm Silence / System Reset Inhibited After Timer Expired
3 OF 22
FIRE
Tyco Safety Products
SolutionBulletin
Fire
REVISION HISTORY:
Revision Revision Date Revised by Reason
K 01/20/2004 D. Langlais Updates to the following issues (Updates have Bolded Text).
• FIXED: How to Correct 4009 TrueAlert Class A Trougle Reporting on a
4120 Network
• FIXED: 4009 IDNet NAC Extender Panel report Battery Trouble to the 4010
• FIXED: SIGA device types, when used in conjunction with SQAlert and
Qalert point types can have a major impact with Trouble reporting for
4100 type Nodes
• FIXED: Build Error On GCC With Multiloop Network "Loop Style Of
Network Card Does Not Match Other Nodes"
• FIXED: Unable to make LSDUCT points external at 4100+, GCC and IMS-
• FIXED: Spell Check Issue
4 OF 22
FIRE
Tyco Safety Products
SolutionBulletin
Fire
PRODUCT:
4010
SUBJECT:
4010 panel problem reports and expected resolution dates.
CAUSE:
Multiple issues with the 4010 panels are either under investigation or resolutions are in the testing cycle. These issues fall into four categories:
Hardware, Firmware and Programmer and Unresolved Issues.
SOLUTION:
MANDATORY/IMMEDIATE ACTION REQUIREMENTS:
GENERAL NOTES:
Hardware:
742-267 – 4010 SFI/O Board (US) – Currently at Revision 565-737 M
742-268 – 4010 SFI/O Board (Canada) – Currently at Revision 565-738 M
742-346 - 4009 IDNet NAC System Board – Currently at Revision 565-771 P
565-903 – 4009 IDNet NAC CLB Fiber Option Card – Currently at Revision 565-903 E
Firmware:
742-147 - SFI/O Firmware Chip – Currently at Revision 3.02.01
741-106 – 4009A Firmware Chip – Currently at Revision 1.08
741-091 – 4010 RS232 Card Firmware Chip – Currently at Revision 1.02
741-101 – 4010 Network Card Firmware Chip – Currently at Revision 4.01
742-146 – 4010 PCCIII Firmware Chip – Currently at Revision 2.02
Programmer:
741-107 – 4010 PC Programmer – Currently at Version 3.03.02 - 4010-9890
553-807 – SDACT Programmer Software – Currently at Version 1.05.05
Master:
741-108 – 4010 Master (.bin) file – Currently at Version 3.03.03
741-121 – 4010 French Master (.bin) file 3.03
5 OF 22
FIRE
Tyco Safety Products
SolutionBulletin
Fire
Hardware Issues:
Issue Status Fix Comment Rev
Ground Fault Fixed Replace the The LCD assembly was changed by vendor to have metal (ground) inserts placed in the H
Condition after Metal Screws mounting holes. If the existing LCD is attached to the mounting plate with metal screws
Replacing the 4010's and Washers and washers, then the plastic screws (432-027) and washers (541-321) must be used.
LCD Display with Plastic. Kit The washers are mounted between the keyboard mounting plate (636-760) and the
743-180 Display.
6 OF 22
FIRE
Tyco Safety Products
SolutionBulletin
Fire
Firmware Issues:
Issue Status Fix Comment Rev
4009 IDNet NAC Fixed There is a defect in the 4009 IDNet NAC Extender U11 firmware chip 741-106 at K
Extender Panel (4009A revision 1.05 and greater
report Battery Firmware) 1.08
Trouble to the 4010 or later Fix: Upgrade the 741-106 4009A firmware chip to rev 1.08 or greater.
revision
Note: This trouble can be cleared by powering down the 4009A. It will also clear
on its own after 24 hours (4009A does not monitor the batteries until 24 hours
after an AC Power Fail)
All Cards Go Missing Fixed Defects were found in the SFI/O Firmware Chips code, that caused the SFI/O to reboot J
Failed and then (SFI/O itself. During the reboot, all the 4010 cards would go missing failed and then clear
Clear / as well as N2 Firmware) immediately, sometimes leaving an External N2 Trouble latched into the panel.
Trouble 2.05.05 or later
revision as well To fix this issue, ensure that the SFI/O firmware chip is at revision 2.05.05 or greater.
as Ferrite Beads Also, install ferrite beads (155-010) onto the IDNet Channels field wiring.
Fixed (SFI/O J
IDNet Channel Firmware) Software filtering was added to the SFI/O firmware chip at revision 3.02.01 to eliminate
Failure, 3.02.01 or later false reporting of Channel Failure
(sometimes followed revision
by an IDNet Class A Details:
Trouble) There have been some reports of the 4010’s IDNet Channel intermittently going
Channel Fail and then clearing on its own. In some cases, an IDNet Class A Trouble is
also annunciated (NOTE: the panel does not indicate any devices going no answer
trouble, which indicates that the channel is not failing or is only failing for a short
duration).
(SFI/O
Output Abnormal Fixed Firmware) 3.02 Replacing the Firmware Chip to 3.01 or later will fix this problem H
Trouble does not or later revision
report after
Suppression
Release Peripheral
has turned ON
Intermittent Wrong Fixed Replacing the Firmware Chip to 2.05.06 or later will fix this problem F
Type Trouble on (SFI/O
Multi-Sensor Device Firmware)
2.05.06 or later
revision
Intermittent Fixed Two deficiencies were found in the 4010’s SFI/O Firmware chips code, which caused
Excessively Dirty (SFI/O Intermitted Excessively Dirty Troubles to come in and clear on random devices. These F
Trouble on SSD Firmware) problems were fixed with the SFI/O firmware chip at rev. 2.05.02 and 2.05.06.
devices 2.05.06 or later
revision
RS232 Card Missing Fixed (RS232 Replacing the RS232 Card’s Firmware Chip will fix this problem. C
Failed Firmware)
1.01.02 or later
revision
Mandatory Upgrade 2.05 Provide improved system performance D
7 OF 22
FIRE
Tyco Safety Products
SolutionBulletin
Fire
Firmware Issues continued:
Issue Status Fix Comment Rev
4010 Panel reports Fixed 3.04 or later Version Control Mismatches Troubles have occurred on networks when re-initialized. D
Version Control revision Restarting the panel (sometimes multiple times) eliminates the symptom. If restarting
Mismatch on restart the panel clears the version control mismatch, a new 4010 network card chip (revision
of 4010 node 3.03.05 or greater) will fix this problem.
Cannot reset Isolator Fixed (SFI/O If a 4010 panel is configured with isolator bases, and the IDNet channel is wired Class E
Bases Firmware) A, you are typically able to reset the Isolator Bases (Output Abnormal Condition) after
2.05.05 or later the shorted condition is cleared. Intermittently, however, a system reset does not clear
revision the Output Abnormal Condition, and a warm start of the panel is required. This problem
is not repeatable.
Cannot reset Isolator Fixed (SFI/O If a 4010 panel is configured with isolator bases, and the IDNet channel is configured E
Bases if wired Class Firmware) Class B (Class A jumpers located at the panel), you are unable to reset the Isolator
B 2.05.05 or later Bases (Output Abnormal Condition never clears). The temporary fix is to warm start the
revision panel, or force a Class A Trouble on the IDNet Circuit.
Channel Failure Fixed (SFI/O If a system is configured with Isolator Bases, and one of the bases has a wiring fault on E
Trouble toggles Firmware) one of the terminals (the input is wired correctly but the output is miss wired / i.e.: plus
between Normal and 2.05.05 or later wire on minus termination and visa versa), the system will not boot up properly and go
Trouble revision in and out of Channel Failure Trouble.
IDNet Channel Fixed (SFI/O If a regular base is installed where an isolator base is programmed, “Channel Failure” is E
Failure Instead of Firmware) indicated on the front panel versus a “Wrong Type” trouble.
Wrong Type Trouble 2.05.05 or later
revision
IDNet Channel Fixed (SFI/O If HEAT is installed where a SMOKE is programmed, “Channel Failure” is indicated on the F
Failure Instead of Firmware) 2.05 front panel versus a “Wrong Type” trouble.
Wrong Type Trouble or later revision
Erratic Operation of Fixed (SFI/O If a 4009IDNet NAC panel is programmed using address 12 on the 4010 IDNet Card, G
True-Alert Non- Firmware) 3.01 the 4009A will not operate properly. Symptoms are: 1.) Long delays (5 to 10 minutes)
Addressable or later revision before NAC circuits activate; 2.) Erratic signal operation when horns do activate. Coding
(SmartSync) Horns will change at random or when signal silence/system reset is activated; 3.) Same delay
when Programmed to turn signals off when signal silence or system reset is pressed.
at Address 12
Intermittent Output Fixed (SFI/O Revision B of this Solution Bulletin stated that this problem was corrected with an SFI/O C
Abnormal Trouble on Firmware) Firmware revision of 2.03.01. Even though a definite cause to this problem was
2 wire SSD Sensors 2.03.02 or later identified and fixed at revision 2.03.01, it was later discovered not to be the only cause.
and Open Circuit revision Another cause to this problem was identified and fixed at revision 2.03.02 of the SFI/O
Trouble on Pull Firmware Chip.
Stations
Erratic Operation Fixed (SFI/O E
and Resound of Firmware) The symptoms were typically horns resounding after silence or reset, or unable to
True-Alert Non- 2.03.03 or later silence signals. This defect was found and fixed in the 4010’s SFI/O Firmware Chip at
Addressable revision revision 2.03.03 and the 4009IDNet NAC’s firmware chip at rev. 1.01.03.
(SmartSync) Horns
NOTE: There is also a potential that these same symptoms may be experienced
because there is less than 20 feet of wire between the panel and the first device. If this
is the case, adding a few more feet of wire will eliminate the problem
8 OF 22
FIRE
Tyco Safety Products
SolutionBulletin
Fire
Firmware Issues continued:
Issue Status Fix Comment Rev
True-Alert Non- Fixed (SFI/O E
Addressable Firmware) This problem was fixed on the 4010 system at revision 2.03.03 of the SFI/O firmware
(SmartSync) Horns 2.03.03 or later chip. This problem has also been fixed with the 4009A firmware chip at revision 1.03.
Ping on Reset revision
The first round of Fixed (SFI/O C
code is not complete Firmware) This problem was fixed on the 4010 system, but the defect is still present when using
on True-Alert Non- 2.03.03 or later 4009 IDNet Nac Panels Signal Circuits.
Addressable revision
(SmartSync) Horns
(Canadian Status See Comments When using the CANPUL device type in order to get 2 stage annunciation, the point G
Operation) No Update must be programmed as S2STAGE. The only indication that a device is in stage 1 or 2
Indication of First alarm is by viewing the alarm log or by viewing the printer (if installed). Per design, the
Stage / Second 4010s LCD display does not indicate Stage 1 or 2 conditions.
Stage Alarm
9 OF 22
FIRE
Tyco Safety Products
SolutionBulletin
Fire
Programmer Issues:
Issue Status Fix Comment Rev
Build Error On GCC Fixed (4010 Fixed in 3.01 4010 programmer where editing of the loop number is no longer K
With Multiloop Programmer) allowed.
Network "Loop 3.03 or later
Style Of Network version Temporary Fix: Change loop numbers on 4010 Network cards to 1.
Card Does Not
Match Other
Nodes"
After making Fixed (4010 This issue was corrected with the 4010 Programmer revision 3.03.01 J
changes to a 4010 Programmer)
Node, the Next 3.03.01 or later NOTE that if you make changes to a 4010 node on the network, ensure that the network
Generation Network version programmer says that a build is necessary. If it says no build is necessary, you will
Programmers build have to build by loading the job and building in the 4010 programmer.
flags are incorrectly
set
General Alarm Fixed (4010 This was fixed with Programmer revision 3.03.01, which now error checks for more than J
Outputs Do not Programmer) 255 points.
Activate on Alarm or 3.03.01 or later
Manual Evacuation version
DETAILS:
List 1 ( L1 ), General Alarm List has a limit of 255 points. If more than 255 points are
populated into the list, the panel will not perform its General Alarm functions, nor will it
reset the alarm. Also, anything programmed using L1 as the Input Qualifier, will not
function because the list never turns ON. List 1 gets populated with IDNet devices as
well as Pseudo Points that have Fire Alarm Priority One Point Types.
10 OF 22
FIRE
Tyco Safety Products
SolutionBulletin
Fire
Programmer Issues continued:
Issue Status Fix Comment Rev
How to Correct Error Fixed (4010 Fixed with programmer 3.03. I
119 When Installing Programmer)
a 4010 Programmer 3.03 or later DETAILS:
Onto a GCC version The following is the error that comes up during the installation...
Component MoveData had the following error:
Media Name: data
Component: Jet Database files
File Group: Registering Jetfiles
File c:\Windows\System\msrd2x35.dll
4009A8 IDNet Point Fixed (4010 The problem is not always consistent, but is easily duplicated when using the 3.01 and I
Is not displayed in Programmer) 3.02 4010 Panel programmers.
the Suppression 3.03 or later
Release Point Tab version If the 4009A8 IDNet Point does not display in the Suppression Release Point Tab in the
4010s Programmer, try to delete the point and then add it at a different address.
Depending on the specific application, the fix to this issue varies slightly. In some
cases, deleting all the 4009A points from the programmer may be necessary before
adding them back into the job.
How to Correct Fixed (4010 If a any Device Type is programmed as an IPHOTO, and this point needs to be added I
Invalid Device Type Programmer) to the Output of a Custom Control Equation programmed with Opcode of FIRE, the point
for this Opcode 3.03 or later must first be added to a List and this List must be used in the Custom Control Equation.
when programming version
the FIRE STATE of
an IPHOTO
Certain Device Fixed (4010 If a any Device Type is programmed as an QSPHOTO, QRPHOTO, QPHOTO, I
Types in 4010 must Programmer) QIPHOTO, OHEAT, KACPULL , and this point needs to be added to the Output of a
be placed in a List if 3.03 or later Custom Control Equation, for Disable/Enable the point must first be added to a List and
the Disable / Enable version this List must be used in the Custom Control Equation.
Opcode is used in
CC
Invalid Device Type Fixed (4010 A defect exists in the 4010 programmer prior to version 3.03, which does not allow a list I
for this Opcode is Programmer) of points to be programmed with any of the following Custom Control qualifiers…
displayed on 4010 3.03 or later
PC Programmer version Physical Normal, Physical Abnormal, Physical Open, Physical Short, Abnormal Detect,
Open Detect, Short Detect
Temporary Workaround:
Whenever using the above Qualifiers, drag the individual points into the equations
output instead of using a LIST.
Unable to Select Fixed Fixed with 4010 programmer revision 3.03 I
CANPUL Device (4010
Type in the Programmer)
Suppression Tab 3.03 or later
version
11 OF 22
FIRE
Tyco Safety Products
SolutionBulletin
Fire
Programmer Issues continued:
Issue Status Fix Comment Rev
Error 78, Invalid Fixed This issue occurs by deleting a point from an IDNET Card and the network tab is not I
Network Device (4010 visited. If different point types are later added to the same IDNET point, they are
Programmer) automatically added to the network card tab and create the error 78 crash.
3.02 or later
version The 4010 Programmer, starting at version 3.02, will prevent the network from having
this issue in the future. However, this does not repair damage that happened in an
earlier version. If the problem was created by an earlier version of the programmer, the
only way to fix it is to find the corrupt point and delete it from the 4010 panel. If the
corrupt point cannot be found, the 4010 may need to be removed from the network and
then added back into the network.
Note: The most likely points are ones that have been recently deleted or added.
Status Update
The 4010 Status FYI: The 4010 Programmer starting at rev 3.01 now installs to a different path. The H
Programmer now Update new path is C:\Program Files\Panel Programmer\Programmer
installs to a different
path
Version Control Fixed (4010 A version control issue existed on 9.02 and later networks when a node was deleted G
Mismatch After Programmer) and then replaced by a new node at the same address. This issue is fixed by using the
Deleting and Adding 3.01 or later 3.01 4010 Programmer and the 1.03 Next Generation Network Programmer (to be
Nodes version released early August).
Suppression Fixed (4010 When an SDACT is added to the programmer, the suppression program stops working. G
Programming Turns Programmer)
Off after adding 3.01 or later NOTE:
SDACT version Check the suppression system options from the front panel display and notice that the
option changes from ON to OFF after the SDACT card is added.
Network Fixed Network Temporary fix is to build the 4010 panels in the 4010 Programmer. Permanent fix is to C
Programmer Rev. Programmer use Version 2.05 or later of the Network Programmer, or 1.01 of the New Network
2.04 or earlier is not 2.05 or later Programmer.
compatible with 4010 version
Phase 2
Programmer
IDNet NAC Extender Fixed SDACT Temporary fix is to acknowledge all the troubles and continue to build. When importing C
Point Types and Programmer the file to the SDACT, acknowledge all troubles, then continue to import. Permanent fix
SQALERT pt types 1.05 or later is to use Version 1.05 or later of the SDACT Programmer.
are not recognized version
by 4010 SDACT.
SDACT programmer
does not recognize
TrueAlert Non-
Addressable point
types.
12 OF 22
FIRE
Tyco Safety Products
SolutionBulletin
Fire
Programmer Issues continued:
Issue Status Fix Comment Rev
The 4010 Phase Fixed (4010 Use Rev. 2.02 or later version of the 4010 Programmer and either Rev. 2.05 or later of C
2.01 and 2.01.02 Programmer) the Network Programmer or 1.01 of the New Network Programmer.
programmers do not 2.02 or later
properly remove version
nodes from existing
networks
4010 will not build if Fixed (4010 Use Rev. 2.02 or later version of the 4010 Programmer C
QSPHOTO points Programmer)
are made public on 2.02 or later
network card version
The 4010 Fixed (4010 Temporary fix is to use “save as” to save the job as a different file. The Permanent fix is C
Programmer does Programmer) to use version 2.02 or later of the 4010 Programmer.
not always save 2.02 or later
correctly. version
Changes made to Fixed (4010 It was discovered that if changes to the program were made, and the panel file name C
the Application Programmer) contained illegal characters, the programmer would not create a new build file and the
Program are not 2.03 or later changes would not be downloaded. This was happening when using the Save-As
showing up at the version feature. The programmer was not checking for illegal characters at this level. Version
panel. 2.03 of the 4010 Programmer added file-naming validation when using the Save-As
feature so that this mistake can no longer happen.
Adding an equation Fixed (4010 If an equation is accidentally added to the default custom control and the job is saved, C
to Default CC thus Programmer) the programmer is permanently corrupted and a new job must created. Version 2.02 of
corrupting the job 2.02 or later the 4010 Programmer eliminated the ability to add an equation to Default CC
version
If the panel is Fixed (4010 This problem was fixed at version 2.02 of the 4010 Programmer C
programmed with the Programmer)
point type of RIAM, 2.02 or later
and the device version
installed is an IAM,
the panel will crash
with code #10
Cannot use System Fixed (4010 This problem was fixed at version 2.02 of the 4010 Programmer C
Points (2-1-0 through Programmer)
2-9-0) with the 2.02 or later
On/Coding Qualifier revision
in Custom Control
Cannot Un-assign Fixed (4010 Revision B of this Solution Bulletin reported that this feature was eliminated from the C
the Key Switch on Programmer) Rev. 2.02 4010 Programmer. The feature was re-enabled with the Rev. 2.03 4010
Remote LCD 2.03 or later Programmer and any defects in its operation also fixed.
Annunciator version
PC Programmer Fixed (4010 This problem was fixed at Rev. 2.02 of the 4010 Programmer. C
locks you out of L9 Programmer)
through L12 after 2.02 or later
upgrade from 1 to 2 version
13 OF 22
FIRE
Tyco Safety Products
SolutionBulletin
Fire
Programmer Issues continued:
Issue Status Fix Comment Rev
Branch number Fixed (4010 This problem was fixed at Rev. 2.02 of the 4010 Programmer. C
changes in info Programmer)
Screen 2.02 or later
version
Temperature Fixed (4010 There is a bug in the 4010 Programmer (versions 2.01, 2.01.02, 2.02) that will not allow C
Programming not Programmer) custom control to be written for heat sensors. This problem was fixed with the release
working in Custom 2.03 or later of version 2.03 4010 Programmer.
Control versions
Unable to program Fixed (4010 A problem was found when using the enable Opcode in Custom Control. If the point C
using Enable Programmer) being enabled, was a Relay Iam, the point would not enable. This problem was fixed
2.03 or later with the release of 4010 Programmer at version 2.03.
version
ANY command in Fixed (4010 Custom Control equations using the ANY Command will change if a job is uploaded into D
Custom control Programmer) a programmer prior to rev 2.02. For example, if the Custom Control Equation is
Changes after 2.02 or later programmed with ANY 2, this equation will change after upload to ANY 512. If this
upload, causing version change is unnoticed, the ANY command will then change to ANY 0 after download. The
outputs to turn on equation will now be True on Panel Startup and Turn on equation output points.
after download
Cannot Passcode Fixed (4010 Prior to programmer rev 2.03.03, there is no way to passcode protect the menu items E
Protect the Function Programmer) located in the Function Menu. These items are Manual Evacuation, City Disconnect,
Menu 2.03.03 or later Control Point Bypass, Elevator Bypass, Door Holder Bypass, Lamp Test, and Display
version Time and Date. Changes were made to both the Programmer and the Master to
enhance the product with this feature.
(No Answer Fixed (4010 Under certain hardware configurations, IDNet devices appear not to communicate at E
Trouble) on Programmer) certain addresses. If the devices are moved to another address, communication is
Random IDNet 2.03.03 or later established. This issue is not repeatable. If this problem is experienced in the field, and
Addresses version the job is programmed with the a programmer at a minimum rev of 2.03.03, please save
the original job file and send it to Technical Support.
COMPARE Opcode Fixed (4010 This Opcode worked in the programmers prior to rev. 2.03, but was broken at rev 2.03. E
in Custom Control Programmer) The equation can be written using the front panel programmer, provided there is no
does not work in 2.03.03 or later Network or DACT card in the system. If a job is restored using the 2.03 programmer,
4010 programmer version and the job restored had used the Compare Opcode, the job will not build at 2.03
rev 2.03 because errors will be detected. This problem was corrected with the revision 2.03.03
Programmer
Class A Trouble Fixed (4010 If a Class A Monitor ZAM, when configured with TROUBLE or UTILITY as its point type, E
does not clear on Programmer) goes into Class A Trouble, the trouble will not clear on System Reset. A warm start is
System Reset 2.03.03 or later needed.
(MZAM with Point version
Types of either To fix this problem, populate the points into List 13 (Class A ZAM Reset List)
Trouble or Utility)
Changes were made to both the Programmer and the Master to fix this problem.
Acknowledge Output Fixed (4010 If a point is programmed to self acknowledge, the following will happen… E
Opcode does not Programmer)
work 2.03.03 or later The point will lock up in the unacknowledged state, not allowing the point to be
version acknowledged (the LED stays flashing, and the Piezo continues to sound).
If a point is a System Power Supply Points (2-1-0, 2-2-0, etc), the panel will crash with
an error code 11 / PC = B047 / Bank 0 / Task 04 upon activation of the point.
14 OF 22
FIRE
Tyco Safety Products
SolutionBulletin
Fire
Programmer Issues continued:
Issue Status Fix Comment Rev
System Reset Status Status Update The 4010 reset duration is self-adjusting based on the number of IDNET devices. If the G
Aborted, Alarms Update system has a large number of devices, approximately 200, the 4010's reset timer may
Present is displayed exceed the 30 seconds allowed by the 4120 reset window timer and cause the 4120
on the head end reset to abort.
annunciating node
when performing a Workaround: Lengthen the reset time of any 4120 panel that Annunciates 4010 panel
Network Reset alarms. The equation below needs to be added to each of these 4120 panels.
IN:
THE ON STATE OF
A34 TIMER "SYSTEM STARTUP PULSE TIMER"
OUT:
SET to value 40 (Seconds) the analogs:
A15 ANALOG "SYSTEM RESET WINDOW TIMER SETPOINT"
END:
15 OF 22
FIRE
Tyco Safety Products
SolutionBulletin
Fire
Master Issues:
Issue Status Fix Comment Rev
How to Correct 4009 Fixed (4010 Master Permanent Fix:| K
TrueAlert Class A .bin File) Upgrade the 4010 Executive .bin File to 3.03.03 or greater.
Trouble Reporting 3.03.03 or later
on a 4120 Network revision Temporary Workaround:
Do Not Program NACS Circuits and SLC Channels for Class A when the Circuits
are Passed across the Network.
Details:
If 4009T and 4009A have Class A Notification Circuits, and these circuits are
programmed with device types on a 4010 system connected to a 4120 Network.
The SIGA device types, can have a major impact with Trouble reporting for 4100
type Nodes. When the problem occurs, the Fire Alarm Panel Trouble count will
decrement to zero (0) and any new Troubles being reported can not be
Acknowledged. The only way to clear the problem is to Warm-Start all Nodes
that the points are made External.
NOTES:
1.) This problem is more likely to appear when there are prolonged periods of
intermittent open Ckt troubles being reported across the 4120 Network. When
Isolators are used, the fault Isolation process will cause this problem to occur.
2.) NAC and SLC Circuits that are configured for Class "A" but programmed for
SIGB will not affect Class "A" operation. An Open Circuit Trouble will still report
to the 4010 Panel
SIGA device types, Fixed (4010 Master Upgrade the 4010 Executive .bin File to 3.03.03 or greater. K
when used in .bin File)
conjunction with 3.03.03 or later Details of Issue: SIGA device types, when used in conjunction with SQAlert and
SQAlert and Qalert revision Qalert point types can have a major impact with Trouble reporting for 4100 type
point types can have Nodes. When the problem occurs, the Fire Alarm Panel Trouble count will
a major impact with decrement to zero (0) and any new Troubles being reported can not be
Trouble reporting Acknowledged. The only way to clear the problem is to Warm-Start all Nodes that
for 4100 type Nodes the points are made External.
NOTE:
Programming a 4009 TrueAlert Controller that is configured for Class “A” but
programmed for SIGB will not affect Class “A” operation. A Common Class A
Trouble will still report to the 4010 Panel
Alarm Silence / Fixed (4010 Master Fixed at version 3.03.01 of the Panel Executive .bin File. J
System Reset .bin File)
Inhibited After Inhibit 3.03.01 or later
Timer Expired revision
16 OF 22
FIRE
Tyco Safety Products
SolutionBulletin
Fire
Master Issues continued:
Issue Status Fix Comment Rev
Unable to turn OFF Fixed (4010 Master There is a defect in 4010 executive 3.03 and earlier which causes GCC graphic J
4010 Pseudo points .bin File) switches to only be able to activate 4010 pseudo points.
from GCC utility 3.03.01 or later
buttons revision Upgrade the 4010 software and executive revision to 3.03.01.
User Defined Keys - Fixed (4010 Master At rev 3.01, editing of User Defined Keys Labels was eliminated from the product. J
Label gets corrupted .bin File) 3.01 or
when job is uploaded later revision
Entire PRINT Fixed (4010 Master This issue was fixed with 4010 executive .BIN file at version 3.03.01. J
STATEMENT does not .bin File)
display on Remote LCD 3.03.01 or later DETAILS explaining issue:
Annunciator
revision
If a Print Statement is used in custom control, the entire print message does not display
on remote LCD Annunciators. For Example if the print message is "Fire On Second
Floor", the remote LCD annunciator may only display an F. The 4010s Front Panel LCD
Display does display the entire message.
Also, worth noting, is that if the input to the Print Statement in Custom Control is a point
in alarm (Fire Det M1-1), additional operational problems occur on the remote LCD
Annunciator. What happens is as follows...
The 4010s front panel LCD Display displays the Fire Alarm as well as the print
statement as designed, but the Remote LCD Annunciators display operates incorrectly.
Its Fire Alarm LED Blinks, indicating that an alarm was received, but the annunciators
display does nothing (Locks Up). For example, the Fire Alarm LED turns on, but the
FIRE Count does not change. If this is the first alarm, the display says FIRE=0 instead
of FIRE=1. The display will eventually correct itself, but this may take several minutes.
17 OF 22
FIRE
Tyco Safety Products
SolutionBulletin
Fire
Master Issues continued:
Issue Status Fix Comment Rev
When Walktest Fixed (4010 Master Fixed in Master .bin file at revision 3.03.01 J
Events are sent to a .bin File)
Printer, the Printout is 3.03.01 or later DETAILS:
Encrypted revision When the system is configured with a printer, and the system is configured to print
walktest events, and the system contains an Exec .bin file prior to rev 3.03.01, some
events are not easily understandable.
For Example, a smoke sensor at address 2 was brought into alarm on a system with the
following date and time (2:24 AM Sat 09 Mar 02). The following is what printed out...
(022403-6090302 @03-002-000 W1).
022403 - This translates to the current time of 2:24:03 AM (hours / minutes / seconds)
W1 = Fire Alarm
Class A Trouble on an Fixed (4010 Master This issue is fixed with the 4010 Executive at rev 3.03 and greater. I
IDNet Monitor ZAM .bin File) 3.03
Clears on System or later revision DETAILS:
Reset Even if Zone is This defect is in the 4010 Executive at revs 3.02.05 and 3.02.06
Still Open
If a Class A Trouble exists on an IDNet Monitor Zam and a system reset is performed,
the Class A Trouble disappears. If the zam detects a status change, the trouble will
reappear. If the panel is warm or cold started, the Class A Trouble will reappear.
NOTE: Even though the trouble disappears from the panel, the zam will still function on
both sides of the Class A break.
IDNet IAM Point in Fixed (4010 Master Upgrade the 4010s master executive to revision 3.02 or greater I
Open Circuit Trouble .bin File) 3.02
Clears on System or later revision DETAILS:
Reset / Provided P16 If a 4010 system has either the 2.02.07 or 3.01 master downloaded into it, and the
is turned ON system is configured with AHJ Reset activated (P16 AHJ City Reset Pseudo Point
turned on), IAM points in OPEN CIRCUIT trouble condition will change status to
NORMAL on system reset (even though the wires are still open)
(4010 Master
4010 Network Point Fixed .bin File) 4010 Executive version 3.02.05 and later fixes this issue. I
Priorities coming from 3.02.05 or later
a 4100 node, are not DETAILS:
version ALL priorities were broken in the 4010 when controlled from the 4100. The priorities
being updated
properly at the 4010 were being reversed in the Master. For example, if a 4100+ CC Equation states to
node HOLD ON a 4010 NAC Circuit at PRI = 6,9, the Priority at the 4010 does not update
correctly when the CC Equations Input goes True
18 OF 22
FIRE
Tyco Safety Products
SolutionBulletin
Fire
Master Issues continued:
Issue Status Fix Comment Rev
How to Eliminate Fixed (4010 Master This problem has been fixed in revision 3.03 Master I
Phantom Network .bin File) 3.03
Alarms From 4010 or later revision DETAILS:
Panels. The 4010 was sending out a bad network packet (2 packets put together an analog
sensor update and a digital pseudo). When this happens...
- The head end node may put this bad packet into its Alarm Log
- The head end node may activates Custom Control if this point is used in an equations
input
- The head end node may send out an alarm to the Central Station.
(4010 Master
SMPL ON Qualifier Fixed .bin File) 3.02 or 4010 Executive version 3.02 and later fixes this issue. H
does not work for later version
SUPABRT Point
Type
(4010 Master
Operational Problem Fixed .bin File) 3.02 or Intermittent Short on a SUPABRT Point sometimes reports as an Abnormal and creates H
with SUPABRT Point later version a Supervisory in the panel
Type
(4010 Master
IDNet Point in Open Fixed .bin File) 3.02 or DETAILS: H
Circuit Trouble later version If a 4010 system has either the 2.02.07 or 3.01 master downloaded into it, and the
Clears on System system is configured with AHJ Reset activated (P16 AHJ City Reset Pseudo Point
Reset turned on), IAM points in OPEN Circuit trouble condition will change status to NORMAL
on system reset (even though the wires are still open)
(4010 Master
4009A No Answer Fixed .bin File) 4010 Executive version 2.02.07 and later fixes this issue. G
Trouble and Wrong 2.02.07 or later
Type Trouble reports version
to the 4010, but not
to the 4120 Network
(4010 Master
Degraded Style 7 Fixed .bin File) If the annunciating node is a 4020 / 4100 / NDU style node, the following equation can G
Trouble on a Style 4 2.02.08 or later be written until the new Master .bin file is installed. In the ON state of A34, Hold P225
Network version off pri = 8,8
(4010 Master
Network Card Goes Fixed .bin File) If the 4010 Network Card intermittently fails during heavy panel traffic, the problem may E
Missing Failed and 2.02.01 or later be corrected with the Master (.bin) file at revision 2.02.01 or greater. This file corrected
then Clears version a defect, which could cause multiple duplicate EQB’s to be generated in the 4010 panel.
Alarm Pseudo Point Fixed (4010 Master A defect was found, which causes Alarm Pseudo Points to turn off when a system reset C
turns off on Reset .bin File) is performed even though there is a custom control equation telling it to turn ON at a
even though a 2.01.03 or later higher priority.
custom control version
equation is holding it
on at a higher priority
24 Point I/O Open Fixed (4010 Master 4010 24 Point I/O. Programmed and Wired for N/C Switches, Open Supervised. What C
Circuit Trouble does .bin File) happens is that an open condition on the I/O point will correctly annunciate a Trouble,
not clear 2.01.04 or later but upon restoral of the wiring fault, the trouble does not clear. This problem was fixed
revision with the release of 2.01.04 of the 4010 Master (.bin) file.
19 OF 22
FIRE
Tyco Safety Products
SolutionBulletin
Fire
Master Issues continued:
Issue Status Fix Comment Rev
Clock Slow Fixed (4010 Master The cause of the clock loosing time was determined, and a fix was implemented at C
.bin File) 2.02 or revision 2.02 of the 4010 Master (.bin) File.
later revision
Event Queue Fixed (4010 Master With rev 2.02 of the 4010 Master (.bin) File, the event queue has been increased from C
Overflow Trouble .bin File) 2.02 or 128 events to 255 events. This should buffer up enough events to prevent most event
when Panel Alarms later revision queue overflows. Event Queue Overflow Trouble typically occurs on systems that
activate all Smoke Sounders on alarm. The only fix if this problem is occurring, is to
stagger the activation of events.
NOTE: There are 2 tasks that service this queue. They are the LCD task and the
RS232 task. When an event gets put on the queue these tasks are responsible for
taking that event off of the queue when they are done with it. These tasks run at fairly
low priority so that they do not interfere with normal alarm and trouble processing.
Warm Start is required to clear an Event Queue Overflow Trouble.
Unable to Fixed (4010 Master If a 4010 supervisory condition is cleared during a Network Reset cycle, the supervisory C
Acknowledge a 4010 .bin File) clears off of the 4010 panel, but the head end annunciating nodes supervisory trouble
supervisory point 2.02.05 or later LED pulses, the piezo sounds, and the panel does not respond to the supervisory
over the network. revision acknowledge. The only way to clear this condition is to re-activate the supervisory
condition at the 4010 system, and then clear it once again.
Cannot Prioritize Fixed (4010 Master If a custom control equation turns on the sounders, and then the smoke enters the E
Sounder .bin File) alarm level in the sensor, and the then smoke falls below the alarm level in the sensor,
Programming in 2.02.05 or later the sounder will turn off following the single station programming (last event wins).
Custom Control revision
At rev 2.02.05 Master, SMPL has priority over single station operation when the devices
sounder is ON, but allows single station operation to work when the devices sounder is
OFF.
WalkTest Horn Fixed (4010 Master The 4010 does not ignore Supervisory Alarms that are on the system prior to entering E
Operation is Erratic .bin File) WalkTest. This results in multiple points trying to report at the same time. If the
2.02.05 or later Supervisory Alarms are restored to normal, the problem clears. Restore the points to
revision normal prior to entering WalkTest.
NOTE:
If restoring the Supervisory points to normal is not an option, Disabling the points should
clear the Supervisory Alarm conditions, but leave Disable Troubles on the system. At
this point enter WalkTest to see if problem clears.
User Defined Keys - Fixed (4010 Master Engineering changed the software at revision 3.01 so that there is no longer any ability G
Cannot Change .bin File) 3.01 to edit the User Defined Keys and LED labels. Master .bin files 2.02 and 2.02.XX
Labels with the 4010 or later revision allowed label changes using the front panel programmer.
PC Programmer
20 OF 22
FIRE
Tyco Safety Products
SolutionBulletin
Fire
Master Issues continued:
Issue Status Fix Comment Rev
CFIG Format Status See Comments • All revision 1 programmers are compatible with all revision 1 master (.bin) E
Mismatch / Restoring Update files
to Factory Default • All revision 2 programmers, prior to programmer rev 2.03.03, are compatible
with all revision 2 master (.bin) Files prior to 2.02.05
• A job using the revision 2.03.03 programmer MUST use a revision 2.02.05
master (.bin) file.
• All revision 3 programmers are compatible with all revision 3 master (.bin)
files
NOTE:
An FSB was created on Dec 28, 1998 (FSB 1105), which deals with CFIG
Format Mismatch.
Alarm Silence and Status See Comments If an equation is written in the 4010 using P26 as the input, it will only work the first time C
System Reset Update signal silence is pressed because P26 stays on until the panel is warm started.
Pseudo Points latch Therefore, if trying to use this pseudo point in custom control, an equation must be
ON written that says when P26 turns on, Hold Off P26 at a Pri=9,9.
IN:
…P26 (Signal Silence)
…DELAY 10 seconds “Delay for a constant the constant here is 10, select an analog
timer”
OUT:
…HOLD OFF P26 PRI=9,9
END:
If the delay is not used, P26 sometimes latches on even though the equation says to
turn off. This happens when pressing the silence key, and holding the key in for a
couple of seconds. Putting the delay into the equation reduces the probability of this
happening.
Unable to Download Status See Comments This has occurred when the SDACT switch is in the program position and the panel is C
to the SDACT Update powered down then re-powered. When this happens, the panel no longer recognizes
that the download switch is in the Program position. To fix, simply toggle the switch
from the program position, to the normal position and then back to the program position
with power applied.
21 OF 22
FIRE
Tyco Safety Products
SolutionBulletin
Fire
Unresolved Issues:
Issue Status Fix Comment Rev
(Canadian TBD TBD When the pull station's general alarm key switch is returned to the normal position, the C
Operation) Signals pull station resounds the alarm to the panel and the signal circuits are activated again.
Resound When the
General Alarm Key
Switch is Returned
to Normal
22 OF 22