(Provided by Lao Guan, a maintenance expert from Qinghai Firefighting – welcome to register and exchange as a member)
(3) 5010 Series Fire Alarm Controllers
1.1 Alarm feedback information repeatedly printed during sound and light broadcast
Fault phenomenon: When the 5010 main unit’s sound and light broadcast is activated, the main unit will repeatedly print the alarm feedback information.
Solution: This situation is caused by enabling sound and light feedback; it can be resolved by turning it off.
1.2 5010 main unit reports type fault after registering alarm
Fault phenomenon: After the 5010 main unit registers the sound and light in the loop as an alarm, it reports a type fault, with version display board 1.2.08 and loop board 0.6.02.
Solution: Upgrading to the latest version will resolve the issue.
1.3 5010 display board shows white screen or flickering
Fault phenomenon: The 5010 main unit’s display screen shows a white screen or abnormal flickering, with normal power voltage output. Disconnecting all external lines and re-plugging the LCD screen cable does not resolve the issue.
Solution: Repair the display board.
(4) 5009 Series Fire Alarm Controllers
1.1 5009 cannot transmit data using serial cable
Fault phenomenon: The 5009 cannot transmit data using the serial cable, displaying “Serial communication failure”.
Solution: Before transmitting data using the serial cable, set the “Serial Debugging Tool” to 1 in the “System Unit Configuration” menu.
1.2 JBF5009 fire alarm controller cannot query incoming linkage logic
Fault phenomenon: The linkage logic written through the Fire Alarm Debugging Assistant APP is transmitted to the JBF5009 fire alarm controller normally, but it cannot be queried in the JBF5009 controller menu.
Solution: It was found that the “~” in the linkage logic written on the phone was a Chinese symbol; changing it to an English symbol before transmission resolved the query issue.
1.3 JBF5009 cannot register D16 combustible gas detector
Fault phenomenon: The JBF5009 fire alarm main unit cannot register the D16 switch-type combustible gas detector, and the D16 detector’s code reading is normal, but no values are displayed in the controller browsing.
Solution: It was found that the JBF5009 controller’s factory default loop protocol is “Enhanced Protocol”; changing the loop protocol to “Standard Protocol” allowed normal registration of the detector.
1.4 JBF5009 controller cannot switch between Chinese and English interfaces
Fault phenomenon: The JBF5009 controller cannot switch between Chinese and English interfaces; selecting “English” and pressing the confirm button has no effect.
Solution: It was found that the control version was 3.0, which was too low to enable the Chinese-English switching function. Upgrading to version 4.2 restored the switching functionality.
1.5 JBF5009 controller cannot register load components, reports unregistered fault
Fault phenomenon: The JBF5009 controller cannot register load devices, reporting an unregistered fault.
Solution: Check if the device coding exceeds the controller’s load capacity.
(5) 51S01 Series Fire Alarm Controllers
1.1 CRT cannot receive reset information from 51S01 main unit
Fault phenomenon: The 51S01 controller connected to the CRT cannot receive reset information from the 51S01 main unit.
Solution: Set the 51S01 controller to centralized mode.
1.2 51S01 controller cannot connect properly with CAD version CRT
Fault phenomenon: The 51S01 controller connects to the CAD version CRT, but disconnects after a reset.
Solution: The CAD1.4.3 version CRT (which is rarely used now) uses an adaptive protocol. If the command is sent using the national standard protocol and there is no response, it will send the 11S protocol’s 3f command. The 51S01 will recognize this command as a debugging tool, leading to communication failure. This has been fixed in the new version.
1.3 51S01 fails to read Chinese comments
Fault phenomenon: The 51S01 fails to read Chinese comments.
Solution: During debugging, the 51S01 needs to be set with the correct machine number. If set to machine number 0, it will not be able to read Chinese comments properly.
1.4 51S02 startup light stays on
Fault phenomenon: The 51S02 is in normal operating status, but the startup light stays on, and resetting or powering off does not change this.
Solution: Check the 51S02 operating mode and change it back to normal mode (in the 51S01 controller, this light indicates the startup indicator; in the 51S02, it is the debugging light. When the 51S01 is not configured with a multi-line bus, the system defaults this main unit as 51S02, so in debugging mode, the debugging light will be on. Exiting debugging mode will resolve this).
1.5 51S01 controller has abnormal communication with 5023 CRT
Fault phenomenon: The 5023 CRT communicates normally with the 51S01 controller when first powered on, receiving fire alarm information, but after the 51S01 controller resets, the CRT shows abnormalities and cannot communicate properly.
Solution: After investigation, it was found that the 51S01 controller’s time was set to the year 2058. Resetting the time to the correct value resolved the issue.
1.6 51S01 controller prompts file not found when upgrading using USB drive
Fault phenomenon: The 51S01 controller prompts that the file cannot be found when upgrading using a USB drive.
Solution: Create a folder named sys—51S01 on the USB drive, insert the USB drive, and select the corresponding file for the upgrade.
1.7 JBF51S01 triggers linkage in automatic prohibition state
Fault phenomenon: When the JBF51S01 is set to automatic prohibition state, it still triggers linkage.
Solution: Because the 51S01 system configuration includes one gas extinguishing zone, the controller defaults the first loop as a gas extinguishing loop, which is not controlled by the automatic prohibition of the alarm loop (only controlled by the automatic state of the gas extinguishing panel), hence the main unit can still trigger linkage even when in automatic prohibition state.
Welcome to join the Blue Flame Watchtower membership community
Finding the right direction makes effort meaningful
