Greetings! In this article, we'll look at some of the problems with the Salwico Consilium fire system on a 10+ year old vessel and how to troubleshoot these issues.
In the official instructions for this system, you can find a lot of information about the problems that occur during the operation of the Salwico fire alarm. But today we will consider only some of them.
General Troubleshooting Steps for Salwico Consilium Fire Alarm System (briefly)
Any fire system on a ship is powered by two sources (main switchboard and emergency switchboard, usually 220V), and additional batteries (usually two 12V each, connected in series).
Attention! If you have an old Salwico Consilium fire system on your vessel, avoid turning it off completely, as this may cause it to fail to boot later.
The first problem that happened with this system was error No. 158 BATTERY CABLE / FUSE FAULT.
At the same time, the "CHARGERM 90 charger" is present in the name of the error. This alarm came out once a day, and could disappear for a week. What is the reason of this problem will be written below.
According to the instructions, this could be a problem with the cable or fuse from the charger to the batteries. There is no fuse in this circuit, the cable contacts were retightened, and later the cable was completely replaced with a new one to eliminate the issue of cable and bad contacts.
The above actions did not help, the error continued to come out from time to time. Next question was about the condition of the internal batteries. The time to replace them was just right, so the option of bad batteries also took place. But the corresponding BATTERY FAULT alarm for batteries did not come out, i.e. this indicates that the capacity and voltage of the batteries are normal, sufficient for operation.
.JPG "Control panel (inside view)")
The next step was to replace the charger with a new one. Since the ship was built, a new CHARGERM charger has been included with the spare parts of this system.
The system was previously de-energized and the same address for the new charger was specified using DIP switches as on the old unit.
As a result, after replacing the charger and starting the system, the BATTERY FAULT alarm came out. The explanation for this most likely is that the batteries really should be replaced and they do not want to work with a new charger. Therefore, the old charger was installed back until new batteries received.
So what's the problem? Let's return to the fact that this error is not permanent, it came out once a day in the period from 12 to 16 p.m., or it could not come out at all. It should also be said that during this period of time the ship worked near the equator and the temperature in the superstructure increased significantly. And since the system is located on the ship's bridge and at the peak of solar activity it heated up significantly, the air temperature in the room varied from + 30 to + 40 ℃ (the air conditioner in the superstructure could not cope, and the separate air conditioner did not work on the bridge).
Such overheating may already be unacceptable for relatively not new electronic equipment, as well as for old batteries (about 4 years old). This charger can operate within -5 to +55℃. But since the equipment is already old, then the temperature limits change and most often downwards.
It turns out there was an overheating of this unit and batteries. It was also noted that after leaving the high temperature zone, the work of the fire system improved and the error stopped coming out.
The optimal temperature limit when charging batteries is from -5 to + 40℃. Unfortunately, alarm No. 229 OVERHEATED did not come out to confirm this version. But this is due to the fact that the thermistor on the charger is set to a higher temperature, and the electronic components of the board and the batteries themselves can no longer withstand even a lower temperature. Also, as a rule, when charging old batteries, much more heat is generated than when new ones are charged.
As a result, a fan was temporarily installed inside the control panel, which provided additional cooling for the charger and batteries. Installing a new battery and charger later will fix this problem completely.
This problem is very common on old vessels. Over time, the temperature limits of the operation of electrical equipment decrease and the electronics begin to overheat. Therefore, you can often find additional fans in different systems on such ships. The solution to the problem is to replace these units and install additional cooling.
The next problem that may appear on old systems is cable break messages. In our case, error No. 142 CABLE BREAK NEGATIVE. In this case, the first loop and the minus line are indicated.
.JPG "LOOP ANALOGUE 1 CABLE BREAK NEGATIVE, FAULT (142)")
This error indicates that a cable break has appeared in the first loop (negative conductor).
Go to Service Menu - Loops - Loop 1 - Press “2” and see that the entire negative line of the loop is not responding.
Thus, all 57 units in the loop (sensors, insulators and manual activation buttons) lose the negative line. It happens for a short time and disappears almost immediately. At first, the source of the problem was difficult to find, but over time, the error began to hang longer and the problem worsened.
The instruction suggests a way to find the place of the break. SCI units are short circuit isolators for detecting a short circuit in a section of a circuit or in a sensor. This loop also involves heat and smoke sensors, and manual buttons to activate the alarm.
The instructions are to disconnect the cable from the LOOP MX No. 1. I recommend that you first de-energize the circuit.
Next, install temporary jumpers on the short circuit insulators so that you can check the entire circuit. In fact, you just need to transfer the chip inside these insulators to neighboring bypass contacts. The same must be done in manual activation buttons if short-circuit protected contacts are used and possibly in sensors, also if short-circuit protection is used. In our case, short circuit protection is not used in them.
.JPG "SCI (contacts on jumper)")
It can be seen from the diagram above (Fig. 2) that in order to start checking the circuit, it is necessary to install jumpers on insulators and timers (in our case, there are no timers in this loop).
It can be seen from the diagram (Fig. 3) that the first loop consists of 7 zones and each zone (except the first one) starts with a short circuit insulator. Therefore, you need to install jumpers on 6 insulators. After de-energizing the circuit, installing jumpers and disconnecting the chip from the unit of the first loop, we check the circuit from plus to plus and from minus to minus (using tester).
To de-energize the circuit, it is necessary to turn off two 220V circuit breakers (on the main switchboard and the emergency switchboard), and also remove power from the batteries!
When the cable was checked from plus to plus, the tester showed 0 Ohm, when checking from minus to minus, the tester showed 150 - 200 kOhm. According to the instructions, the circuit resistance should be no more than 185 Ohms. In our case, it really turned out to be a break in the negative conductor somewhere on the first loop.
Then I recommend not to use this method, but to try to cut off each zone by jumping plus and minus starting from the first zone. We put a jumper at the output of the LOOP MX 1 unit (for example, 11 - 12) (see Fig. 2) and measure the resistance at the input of the insulator of the second zone (see Fig. 3). If the resistance is 0 Ohms, then go ahead. We put a jumper at the output of the insulator of the second zone and measure the resistance at the input of the insulator of the third zone, etc.
Thus we check each zone. You can split the entire loop in half or start from the last zone and move in the other direction, but here it’s convenient for anyone. The main thing is to understand the principle of cutting off zones.
After checking all zones, we got to the problem area. It turned out that the break is in zone No. 6. Here you also need to search, just cut off each sensor, insulator and button.
As a result, two manual buttons for activating the fire system turned out to be problematic. They are located on the left and right sides on the main deck, just near the exits from the superstructure to the deck.
As a result of severe contamination and oxidation of the contacts, the system eventually began to see a break. Two buttons were found in the stock of the fire system, but already used. They were supplied instead of the old ones, DIP switches were pre-set, as on the old ones.
One button gave an error No. 144 LOOP UNIT TYPE CHANGED. Those, the system decided that a unit of a different type than the original was installed.
The instruction from the maker did not help and the cause of the error is not clear. Therefore, I had to clean the contacts of the old button.
.JPG "Setting the working button (comparison of DIP switches)")
After a thorough cleaning of the contacts, the button was safely returned to work. The second button was also cleaned and put to spare. At the same time, a new checking of the negative line showed 0 Ohm, what was required to be achieved.
Also, during the checking of all zones, bad connections were found on the terminals and chips.
%201.JPG "Short circuit insulator (problem contact, rests on 2 wires)")
%202.JPG "Short circuit insulator (problem contact, rests on 2 wires)")
%203.JPG "Short circuit insulator")
.JPG "Terminal on the bridge (problematic contact, 3 cores remained in operation)")
Such problematic connections can lead to a broken line over time, so all bad contacts have been updated.
What else has been done? Before starting to search for a troubleshooting problem, an attempt was made to replace the LOOP MX No. 1 on LOOP MX No. 4, which is not used in the system, and the line is bypassed with jumpers. This was done in order to eliminate the problem with the unit, which could occur due to the same overheating described above with the CHARGERM unit.
But this action did not bring a positive result. By the way, after the launch, the system took a long time to load and at first did not see the sensors of the first loop, but eventually it loaded completely.
What other problems can happen with the Salwico Consilium fire system? During long-term operation, individual sensors may also fail, due to breakage or contamination. Sensors that are located in the engine room are especially heavily contaminated.
The system provides monitoring of sensor pollution and it can generate the corresponding error No. 130 DIRTY SENSOR. You can see in advance the degree of contamination of the sensors using the menu.
In this case, the sensor must either be cleaned or replaced if cleaning does not help. Because Since the system uses addresses for each unit and sensor, then when replacing sensors, it is necessary to assign the corresponding address to them. To do this, you need to use a special device.
Manuals! If you need instructions, configuration files or software for the Salwico Consilium fire alarm, I recommend our closed telegram channel Marine Engineering Manuals.
If you have experience with this system or you need troubleshooting, then write in the comments to this article. I will gladly take part in troubleshooting, I will help as much as I can!
General Troubleshooting Steps for Salwico Consilium Fire Alarm System (briefly)
To troubleshoot a Salwico Consilium fire alarm system, follow these general steps:
Initial Checks:
Power Supply:
- Ensure the system is properly powered.
- Check for any blown fuses or tripped circuit breakers.
- Verify that the backup batteries are functioning and properly connected.
Visual Inspection:
- Inspect the control panel for any visible signs of damage or loose connections.
- Ensure that all modules and cards are seated correctly.
- Check the wiring for any signs of wear, corrosion, or disconnection.
Control Panel Diagnostics:
System Status:
- Check the control panel's display for any error codes or messages.
- Refer to the system's manual to interpret these codes.
Alarm and Fault Indicators:
- Identify which zones or devices are indicating an alarm or fault.
- Reset the system and see if the issue persists.
Device-Specific Checks:
Detectors (Smoke, Heat, etc.):
- Clean the detectors to ensure no dust or debris is causing false alarms.
- Check for any physical obstructions around the detectors.
Manual Call Points:
- Test each manual call point to ensure they are functioning correctly.
- Inspect for any signs of tampering or damage.
Sounders and Beacons:
- Ensure that all sounders and beacons are working correctly.
- Verify that the correct signals are being transmitted and received.
Communication and Software:
Wiring and Networking:
- Check all communication wiring for continuity and proper connections.
- Ensure that any networking equipment is operational and correctly configured.
Software Configuration:
- Verify that the software configuration matches the physical layout of the system.
- Update the software if there are any available updates or patches.
Common Issues and Solutions:
False Alarms:
- Clean detectors and ensure they are correctly placed.
- Check for environmental factors like dust, steam, or aerosols.
Intermittent Faults:
- Inspect all connections for stability.
- Check for any sources of electromagnetic interference.
System Failures:
- Ensure the firmware is up-to-date.
- Perform a full system reset if necessary.
Documentation and Support:
Manuals and Documentation:
- Refer to the user manual and technical documentation specific to your Salwico Consilium model.
- Keep a log of all tests and inspections performed.
Technical Support:
- Contact Salwico Consilium technical support if the issue persists.
- Provide detailed information about the issue, steps taken, and any error codes or messages.
Preventive Maintenance:
- Schedule regular maintenance checks.
- Keep the system clean and free from dust and debris.
- Regularly test all components to ensure they are functioning correctly.
For specific troubleshooting steps, always refer to the user manual provided with your Salwico Consilium fire alarm system.
What is the "Alarm delay off" led actually for? It the menu there are two timers 1 and 2 for "mute" and "reset". There is no description in the manual.
ReplyDelete
DeleteThe "Alarm delay off" LED on the Salwico Consillium alarm system typically indicates a delay feature for alarms, allowing for a brief period before alarms are silenced or reset. This can be useful to prevent nuisance alarms during temporary conditions, giving operators time to assess the situation.
The timers in the menu, labeled "mute" and "reset," likely control the duration of how long the alarms can be muted or how long before the system resets after an alarm condition is cleared.
Good day. We had an engine room fire and recently, we cannot reset the system even when fire was extingueshed. Thus we switch off power supply for ac and DC. When we retore the power and tested. General alarm did not activate even after 2 minutes have lapse. What could be the problem of the system?
ReplyDeleteGood day. After an engine room fire and a full system shutdown, if the general alarm fails to activate after restoring power, here are some possible issues to check:
Delete1. Faulty Alarm Control Panel: The control panel may have been damaged during the fire, and it might not be sending the necessary signals to trigger the alarm. Inspect the control panel for any signs of damage or burn marks.
2. Damaged Wiring: Heat from the fire could have damaged or melted some wiring, which may be preventing the alarm signal from reaching its components. Check all related wiring and connections for continuity and integrity.
3. Power Supply Issue: The power supply to the general alarm system might not be restored correctly, or there may be issues with the main power source. Verify that all power supplies are stable and functioning.
4. Faulty General Alarm Unit: The general alarm unit itself may have been affected, especially if it was exposed to high temperatures or smoke. Test the general alarm unit to ensure it’s operational.
5. Control Circuit Faults: Some control circuits may need resetting or could have residual faults from the fire. Try resetting all connected circuits as per the system manual.
Good Day .I have an issue with 2 sensors one heat type and the other smoke and heat type on the same loop.Comes in alarm after a short circuit on another sensor install in a cold room.I replaced the sensor in cold room but with no results.
ReplyDeleteIn MENU on LOOP Unit List these two sensors have signed -/- instead of A/B. It looks like perhaps system lost those addresses.I read the manual on how to install new unit in the loop but is not clear . What is the exact procedure.Many thanks.
Good day! It sounds like the two sensors might have lost their addresses or configuration due to the short circuit. Here’s a general procedure that should help you re-address or reinitialize the sensors on the Consilium Salwico loop.
DeleteSteps to Reinstall Sensors on a Consilium Salwico Loop:
1. Check Loop Integrity: Before proceeding with sensor reconfiguration, ensure the loop wiring is intact and that there are no additional shorts or open circuits on the loop.
2. Access the Control Panel:
• Go to the main control panel and navigate to the MENU.
• Enter LOOP MENU or LOOP UNIT LIST where you can view the sensors on the loop.
3. Remove the Faulty Units (Optional):
• If the system still shows the sensors with the -/- addresses, you may need to “delete” or remove these entries from the loop unit list. This allows the system to re-scan and reinitialize these addresses without interference. (If you don’t have this option, then try reload the system).
4. Install/Replace Sensors:
• For each sensor, follow the manufacturer’s guidelines for physical installation (making sure they’re properly connected to the loop).
• If the sensors are already installed, proceed to the next step for addressing.
5. Reinitialize the Loop:
• Within the LOOP MENU, there should be an option like Loop Initialization or Unit Auto Addressing. Select this option to re-scan the loop. (If you don’t have this option, then reload the system).
• This process should automatically detect and assign addresses (A/B) to the sensors.
• If the sensors do not appear after the scan (reload), check their connections and try the re-scan again.
6. Verify Sensor Status:
• After reinitialization, navigate back to LOOP UNIT LIST and confirm the two sensors have their addresses (A/B) displayed instead of -/-.
• If the issue persists, double-check all wiring connections and ensure each sensor is compatible with the loop settings.
7. Test Sensors:
• To confirm proper operation, you may want to perform a sensor test if the system allows it, ensuring they trigger alarms as expected.
If it’s doesn’t help, try re-address the sensors as per manual.
Good day, I am facing an issue with 80 faults. * Loop analogue 2 loop b short circuit fault (140), * Loop analogue 2 loop a short circuit (139), rest of all is NO ANSWER fault(128) . Please give me guidance.
ReplyDeleteGood day. Here’s a structured troubleshooting approach you can take:
Delete1. Short Circuit Faults (Loop A and B)
• Cause: Short circuit faults, such as 140 and 139, usually indicate an issue with the wiring or a connected device on the loop.
• Steps to Check:
• Inspect the wiring for Loop A and Loop B on Loop Analogue 2, looking for any signs of damage, exposed wires, or loose connections.
• Ensure there are no foreign objects or water ingress causing short circuits in the junction boxes or devices.
• If possible, disconnect the loop wiring and use a multimeter to test for continuity or shorts in each loop independently.
• If you identify a damaged section of the cable or a faulty device, repair or replace it and reset the system.
2. No Answer Faults (Fault Code 128)
• Cause: “No Answer” faults usually suggest that the control panel cannot communicate with the devices on the loop.
• Steps to Check:
• Check the devices connected to the loop with the No Answer faults. These might be faulty or disconnected devices.
• Inspect loop termination points (if applicable) and make sure each device is properly connected and seated.
• Ensure that the loop is not overloaded with devices. If the power supply is insufficient, it can cause communication issues.
• If your system uses isolators, check that they are functioning properly and are not blocking communication to sections of the loop.
3. Power Supply and Loop Load Check
• Confirm that the power supply is stable and meets the requirements of the system. If the power supply is fluctuating, it could result in multiple faults across the loop.
• Check that each loop is within its maximum device capacity, as an overloaded loop could lead to faults.
4. Loop Module Reset
• Perform a reset of the loop module (or loop card) to see if the faults clear temporarily. Disconnect and connect again.
5. Isolation Testing
• If you’re still encountering issues, try isolating segments of the loop and testing smaller sections individually. This can help identify if a particular segment or device is causing the fault.
6. Contact Support
• If the above steps do not resolve the issue, it may be beneficial to contact Consilium technical support. They may be able to offer additional insights specific to your system model.
By systematically checking each of these areas, you should be able to identify and correct the issues causing the faults.
Good Day..!!
ReplyDeleteI am facing this error on Fire Detection System - loop analogue 11 cable breK negative, fault (142)
There are total 95 units on loop 11...how will i understand that the cable break is for which particular unit..??
I madr the scan by going in the service option but it show "ok" for all the units.
The error message “loop analogue 11 cable break negative, fault (142)” in a Salwico Consilium fire detection system indicates a potential disruption in the loop wiring, commonly caused by a break or loose connection in the negative line. With 95 units on the loop, pinpointing the exact fault can be challenging.
DeleteHere are steps to troubleshoot the issue effectively:
1. Check the Control Panel:
• The system’s control panel should display the faulty loop. In your case, it’s loop 11. Use the panel to confirm that all devices in the loop are addressed correctly.
2. Service Mode Scanning:
• Although your scan showed “OK” for all units, this might indicate an intermittent fault. Run the scan multiple times and ensure the loop addresses match the installed devices.
3. Divide and Conquer:
• Isolate sections of the loop by disconnecting smaller segments at terminal junction boxes. Check if the error persists. This can help identify the segment where the break or loose connection exists.
4. Inspect Wiring and Connections:
• Physically inspect the cable connections for corrosion, wear, or disconnection at device terminals or junction boxes. Pay close attention to areas exposed to high vibration, moisture, or heat.
5. Test for Continuity:
• Use a multimeter to test the continuity of the negative line throughout the loop. A lack of continuity in any section indicates the cable break location.
6. Replacement or Repair:
• Once identified, repair or replace the faulty section of the cable. Ensure all connections are secure and protected from environmental damage.
Hello, I received fault (159) zone 11 cable break/shorted
ReplyDeleteCan you please advice, maybe you have some solutions.
Hi, the fault message “159 Zone 11 cable break/shorted” in a Salwico Consilium fire alarm system typically indicates a wiring issue in Zone 11. Here are steps you can take:
Delete1. Inspect Wiring: Check Zone 11’s cables for physical damage, loose connections, or improper terminations.
2. Measure Resistance: Use a multimeter to test for continuity or short circuits in the wiring.
3. Examine Devices: Ensure all connected devices in the zone are operational and not causing faults.
4. Review System Settings: Verify configuration and termination resistors in line with the manual.
Also, if have smoke on this zone, will it still work and give fire alarm?
DeleteIf Zone 11 has a cable break or short circuit, the fire alarm system’s functionality in that zone is compromised. Smoke detection and alarm triggering may not work unless the fault is resolved. Modern systems often prioritize addressing such faults to restore zone functionality. It’s crucial to troubleshoot and repair the issue to ensure safety.
DeleteSo can it also be an option of checking fault? For example if i have a break in the middle of zone, if i try to test sensors after break point they will not work or when this fault appeared all zone out of order?
ReplyDeleteIf there is a cable break in the middle of the zone, sensors beyond the break will not work since the signal cannot reach them. The zone could also register as completely out of order if the fault disrupts the circuit. Whether the entire zone or just a portion becomes non-functional depends on the specific system design and wiring configuration.
DeleteGood day, today i try what i think yesterday and one sensor not passed testing, when i changed him with new one, fault disappeared. Now system working properly. So it’s also can be like checking option. Thank you for your advise.
DeleteGood day, thanks for your experience.
DeleteHello, I currently have a problem with my system while carrying out battery test. The fault alarm states : CENTRAL 30 REPEATER 40 NO ANSWER, FAULT (128)
ReplyDeletewhat can possibly be done to rectify it. Thanks
The error “CENTRAL 30 REPEATER 40 NO ANSWER, FAULT (128)” in the Salwico Consilium fire alarm system generally indicates a communication issue between the central fire alarm control panel and a connected repeater panel. Here’s how you can troubleshoot and rectify it:
Delete1. Check the Communication Link
• Cable Connections: Ensure all physical connections between the central panel (30) and the repeater (40) are secure and intact.
• Wiring Continuity: Test the wiring between the two panels for continuity. Look for loose, broken, or damaged cables.
• Termination Resistors: Verify that the termination resistors at the ends of the communication line are properly installed if required by the system.
2. Inspect the Repeater Panel
• Power Supply: Confirm that the repeater panel is powered on and its power supply is stable.
• Fault Indicators: Check for any fault or error messages directly on the repeater panel. Address those first if present.
• Battery Check: If the repeater has backup batteries, ensure they are in good condition and properly connected.
3. Battery Test Impact
• Battery Voltage: Low or failing batteries during a test may cause the central panel to lose communication with peripherals. Verify the central panel’s batteries are adequately charged and functioning.
• Load Test: Perform a load test on the batteries to ensure they can handle the required current.
4. Restart Components
• Restart both the central panel and the repeater panel to reset the communication link. Sometimes a simple reboot resolves transient communication issues.
5. Inspect the System Logs
• Access the system’s event log to gather more detailed information about the fault’s timing and potential triggers.
Thanks for the update. problem rectified. The repeater firmware was corrupted and needed an upgrade.
DeleteThank you for writing what the problem was.
Delete