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.
.JPG)
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.
DeleteHello currently i have the same problem. Error on central panel "repeater is configured but not present. And in the repeater panel in only shows "CCP". may i know how you upgrade the firmware? and is there any specific format or capacity of usb needed to be connected to the panel because i tried to to back up the program but not saving on my USB drive.
DeleteHi. For the issue where the central panel displays “repeater is configured but not present” and the repeater panel only shows “CCP,” it could be due to communication loss, incorrect configuration, or firmware issues.
DeleteTroubleshooting Steps:
1. Error on Central Panel: “Repeater is configured but not present.”
This error indicates that the central panel expects a repeater panel to be connected, but it’s not detecting one. Possible causes and solutions include:
• Configuration Mismatch: Ensure that the system’s configuration accurately reflects the connected devices.
• Connection Issues: Verify that all cables between the central panel and the repeater are securely connected and free from damage.
• Power Supply: Confirm that the repeater panel is receiving adequate power.
• Address Settings: Check that the repeater’s address settings are correctly configured and do not conflict with other devices.
2. Repeater Panel Displaying Only “CCP”
The “CCP” message on the repeater panel suggests it might be in a default or limited mode, possibly due to firmware issues or configuration problems. To troubleshoot:
• Firmware Status: Ensure that the repeater’s firmware is up-to-date.
• Configuration Alignment: Verify that the repeater’s configuration matches that of the central panel.
• Communication Integrity: Check the communication link between the repeater and the central panel for any disruptions.
3. Firmware Upgrade and USB Requirements
Upgrading the firmware of your Salwico Fire Alarm System typically involves using a USB memory stick. Here are some general guidelines:
• USB Format: Use a USB stick formatted to FAT32, as this is commonly supported.
• Capacity: While specific capacity requirements aren’t specified, using a USB stick with a capacity between 4GB and 16GB is generally advisable.
• Firmware Files: Ensure that the correct firmware files are loaded onto the USB stick.
• Upgrade Procedure: Insert the USB stick into the panel’s USB port and follow the manufacturer’s instructions for initiating the firmware upgrade.
For detailed instructions tailored to your specific system model, please refer to the manufacturer’s documentation or contact Consilium’s technical support.
4. Backing Up the Program to USB
If you’re experiencing issues backing up the program to your USB drive:
• USB Compatibility: Ensure the USB drive is formatted to FAT32 and is recognized by the system.
• Available Space: Verify that the USB drive has sufficient free space for the backup file.
• System Logs: Check the system logs for any error messages related to the backup process, which might provide further insights.
If these steps don’t resolve the issue, it’s recommended to consult the system’s user manual or contact Consilium’s technical support for specialized assistance.
Good day! Everyone
ReplyDeleteI have some issues
consillium fire detection system get 139 loop analogue 2 loopA short circuit how to troubleshoot. And after some time reseted how to find out.
Kindly advise
Good day! A "Loop A short circuit" error in a Consilium fire detection system (or similar systems) can result from a variety of issues. Here’s a step-by-step guide to troubleshooting and identifying the root cause:
Delete1. Understand the Problem
Short circuit detection: This means there’s an electrical short in the loop wiring or one of the devices connected to Loop A.
Intermittent fault: If the system resets itself after some time, the issue might be intermittent, possibly caused by loose connections, moisture, or a failing device.
2. Inspect the Wiring
Check physical connections: Inspect all connectors, terminals, and junction boxes along Loop A for loose, corroded, or damaged wires.
Look for external damage: Ensure no cables are pinched, cut, or exposed to moisture.
Measure loop resistance: Use a multimeter to check the loop’s resistance. A significantly low resistance indicates a short.
3. Isolate the Fault
Disconnect segments of the loop: Divide the loop into smaller sections by disconnecting it at various points. This can help pinpoint where the short circuit is occurring.
Reconnect gradually: Start reconnecting one segment at a time while monitoring the system for errors.
Use EOL resistors: Ensure End-of-Line (EOL) resistors are correctly installed where needed.
4. Inspect Devices on the Loop
Test individual devices: Disconnect and test each detector, sounder, or manual call point for faults. Replace any faulty devices.
Clean devices: Dust, debris, or moisture inside detectors can cause temporary faults.
5. Environmental Factors
Check for moisture or water ingress: Look for signs of condensation or water in devices or cables.
Interference: Electromagnetic interference from nearby equipment can sometimes mimic faults.
6. Log and Monitor the System
Check system logs: If your Consilium system provides logs, review them for recurring fault patterns or timestamps.
Monitor conditions: After resetting, keep an eye on environmental or operational changes that might correlate with the issue.
Fire alarm system Salwico Consilium
ReplyDeleteHello everyone,
Please I need some help with my fire alarm, I have an fault alarm ‘’CENTRAL 30 LMX 12 XFIRE SIGNAL FAULT(225)’’ as on the picture attached and the main control panel is not displaying anything.
Please I need some help.
Thanks
The fault message “CENTRAL 30 LMX 12 XFIRE SIGNAL FAULT(225)” on a Salwico Consilium fire alarm system typically indicates an issue with communication between the central control panel and one or more devices or modules in the system. The fact that your main control panel is not displaying anything suggests a deeper issue, such as power loss or a fault in the control panel itself. Here’s a step-by-step troubleshooting guide:
Delete1. Check the Power Supply
• Ensure that the control panel has power. Check the main power supply and any backup batteries.
• Verify that there are no blown fuses or tripped circuit breakers.
2. Inspect the Control Panel
• If the control panel display is blank, it may need a reset or replacement.
• Check for any physical damage, loose connections, or burnt components.
3. Check the Loop Devices
• A signal fault often means there is an issue with a device connected to the loop. Inspect the loop for:
• Loose wiring
• Damaged or disconnected devices
• Incorrect device addressing
• If you know which device corresponds to the fault code (225), inspect it specifically.
4. Reset the System
• Try performing a system reset from the control panel. If the reset button or function is unresponsive, power cycle the entire system by disconnecting and reconnecting the main power and battery backup.
5. Consult the Manual
• Refer to the Salwico Consilium system manual for specific troubleshooting steps related to the fault code. If you don’t have the manual, you can often find it online by searching for the model number or in our closed channel https://t.me/+4ixrulIo_cFhMTEy.
The control panel is on but the display is blank system fault indication light is on and the fault indication light on annalogue addresable loop module MX is bliking all the time.
DeleteThe situation you’ve described suggests a serious communication issue within the system. The control panel being on but having a blank display, along with the system fault indication and the blinking fault light on the MX module, typically points to a few potential causes:
DeletePossible Causes
1. Control Panel Fault:
• The blank display might indicate an internal fault in the control panel’s processor or display module. This could affect the system’s ability to communicate with the loop module.
2. Loop Module Communication Fault:
• The blinking fault light on the MX loop module suggests it cannot communicate properly with the control panel or devices on the loop.
• This could be due to:
• Damaged wiring in the loop.
• A failed loop driver card/module.
• Improper termination or grounding issues.
3. Configuration Issue:
• If a configuration file is corrupted or missing, the control panel may fail to properly manage the devices and display information.
4. Power Supply Issue:
• While the control panel is powered, there might be insufficient voltage or unstable power affecting the system’s performance.
5. Faulty Device on the Loop:
• A defective device (e.g., detector, module) on the loop could cause communication errors and disrupt the system.
Troubleshooting Steps
1. Power Cycle the System:
• Switch off the main power supply and disconnect the battery backup. Wait a few minutes, then reconnect the power. Monitor for changes in the control panel display or fault indicators.
2. Inspect Loop Wiring:
• Check for damaged or disconnected wiring in the loop.
• Verify proper grounding and loop terminations.
3. Test the Loop Module (MX):
• Check the connections on the MX loop module for loose wires or faulty connectors.
• Replace the module with a spare if available to rule out hardware failure.
4. Check the Loop Devices:
• If possible, isolate sections of the loop to identify if a specific device is causing the issue.
• Inspect devices for visible damage or incorrect addressing.
5. Verify Power Supply:
• Measure the voltage at the control panel and the MX loop module to ensure they are receiving the correct and stable power supply.
6. Inspect the Control Panel Hardware:
• Check internal connections within the control panel for loose cables or damaged components.
• If the display module is faulty, it may need replacement.
Fire alarm system Salwico Consilium HELLO, Where is the internal battery located in the fire alarm syste.
ReplyDeleteThe internal battery for a Salwico Consilium fire alarm system is typically located inside the main control panel or the power supply unit of the system. Here’s how you can check:
Delete1. Locate the Main Control Panel
Open the main panel by unlocking it (a key may be required). Inside, you should see various components, including circuit boards, wiring, and a section designated for power.
2. Look for the Battery Compartment
The internal batteries are usually housed in a separate compartment or located near the bottom of the panel. They are commonly sealed lead-acid (SLA) batteries.
3. Check Battery Specifications
The system manual or a label near the battery compartment should specify the required battery type and capacity (e.g., 12V 7Ah or similar).
If you do not see such a battery in your panel, then most likely an external General Service battery is used.
Hello, could you send me the manual where is the alarm codes please?
ReplyDeleteHi, here is the link to the instructions https://www.dropbox.com/scl/fi/ivsk9t61x8nguxpd874bi/Fire-Detection-System-Salwico.rar?rlkey=1fazy5y2s5sungct8jjq370mt&dl=0.
DeleteIf you need more instructions on Salwico Consilium, I recommend our closed channel https://t.me/+4ixrulIo_cFhMTEy
Good day. I have reed your advice, and tried to troubleshoot a problem on our vessel without success. We have from time to time more then 40 active alarms on the loop No2. Pos cable break, negative cable break, SCI not answering. We have disconnected power supply and measured resistance for shorts and breaks, all readings were good. We checked each sensor on the loop all connections were ok. Tried to isolate small sections, fault moved to diferent SCI. We dont have spares onboard, to check if sci is a problem. Is it possible that one faulty SCI triggers other SCI's on the loop, since we have different sci triggered after every test?Thanks in advance.
ReplyDeleteYes, a faulty Short Circuit Isolator (SCI) can cause issues across the loop. If an SCI is malfunctioning, it may not isolate faults correctly, leading to erratic fault indications such as cable breaks or other SCIs not responding. Since the fault moves after each test, it suggests that either:
Delete1. A single faulty SCI is intermittently affecting communication, causing other SCIs to misreport faults.
2. A wiring issue (e.g., intermittent loose connection, corrosion, or high resistance) is affecting multiple SCIs in different locations, causing different fault readings depending on loop conditions.
3. Loop load issues where voltage drops or instability might be causing multiple SCIs to misbehave.
Without spare SCIs, you could try:
• Swapping SCIs from another loop (if available and identical) to see if the issue follows a specific SCI.
• Checking loop voltage at various points to see if there’s a significant drop.
• Inspecting loop connections again, focusing on terminals where SCIs are installed.
• Using an oscilloscope or multimeter to check for fluctuations or noise in the loop wiring.
If you can isolate the fault to a single SCI, replacing it is the best solution.
Hi thanks for prompt reply. So far what we noticed during tests: Since it is a closed loop, we tried to disconnect cables from one side of SCI (side that is being cut off ), we get Voltage on the output 34V, when we connect cables back SCI cut off, voltage drops to 2V. That happens on several different SCI, even though we connect only one sensor. I do suspect for a noise in the system, but it's hard to pinpoint from were is coming from since, the SCI are cutting off across the whole vessel.
ReplyDeleteThat voltage behavior suggests a possible grounding issue, excessive loop current draw, or interference affecting the SCIs across the vessel. A few things to check:
Delete1. Loop Ground Fault – Measure resistance between loop conductors and vessel ground. A low reading (below 1MΩ) could indicate an unintended ground connection causing SCI instability.
2. Excessive Current Draw – If a faulty device is drawing too much current, the loop voltage may drop, causing SCIs to isolate sections. Try disconnecting non-essential devices one by one and monitoring voltage.
3. EMI/Noise Interference – Since SCIs are triggering across the vessel, consider sources of electrical noise like VFDs, large motors, or generators. If possible, check if faults occur more frequently when specific equipment is running.
4. Loop Power Supply – Verify that the power supply feeding Loop No. 2 is stable and not fluctuating under load. Check output voltage and ripple using a multimeter or oscilloscope.
5. Cabling Issues – Even though continuity tests were good, try checking for intermittent faults by slightly bending or stressing cables at different points, especially around penetrations and terminations.
If you have another loop running without issues, you could compare voltage, current draw, and ground isolation readings to see if there’s a key difference.
I would like to thank you for your excellent guidance. By removing SCI's from the loop we managed to find one of the SCI that was giving us the faults throughout the system. Best regards
DeleteThx for your feedback regarding the solution to this problem.
DeleteGood time of the day,we faced problem with repeater panel on the bridge,that it’s not giving audible alarms from buzzer and bell when alarms appears,but on main control station all alarms signalising with audible alarms,please advise,is it possible that bell/buzzer to be malfunction?
ReplyDeleteYes, it’s possible that the buzzer or bell in the repeater panel is malfunctioning. However, before replacing it, you should check the following:
Delete1. Configuration & Settings:
• Ensure that the repeater panel is configured to provide audible alarms. Some systems allow enabling/disabling audible signals in the settings.
• Check if the buzzer/bell has been muted or disabled accidentally.
2. Hardware Issues:
• Inspect the buzzer and bell for physical damage or loose wiring.
• Measure the voltage supplied to the buzzer when an alarm occurs. If no voltage is present, there could be an issue with the repeater panel’s control board.
3. Communication & Power Issues:
• If the repeater panel is connected via data bus, ensure there are no communication faults between the main panel and the repeater.
• Check power supply connections to the repeater panel. A low-voltage issue might prevent the buzzer from working.
4. Firmware/Software Issues:
• If other functions of the repeater panel are working normally, but the buzzer is not, a firmware issue might be causing this. Restart the panel and, if possible, check for any available updates.
Next Steps:
1. Try activating the buzzer manually if the system allows for testing.
2. If the buzzer/bell still does not sound, try swapping it with a known working unit.
3. If replacing the buzzer does not fix the issue, the problem could be within the repeater panel’s control circuit, requiring further diagnostics or manufacturer support.
Hello All, we are having issue in consilium fire detection system, there is no alarm in the system whereas in loop 7 one smoke sensor is not giving alarm while testing ie 7.1 but after this 7.2 smoke sensor and 7.3 manual call point is working. We have changed smoke sensor with base plate, changed manual call point. Still we cant receive any alarm for 7.1 smoke sensor.kindly help to resolve this issue TIA.
ReplyDeleteIn addition to above, if we change 7.1 smoke sensor with 7.2 then the one which is not working in 7.1 is working in 7.2.
ReplyDeleteSince the 7.1 smoke sensor works when placed in 7.2, the issue is likely with the address configuration, wiring, or loop communication rather than the sensor itself. Here’s a step-by-step troubleshooting approach:
Delete1. Verify Addressing
• Ensure that the 7.1 smoke sensor has the correct address set in the system.
• Compare its address with the working sensors (7.2 and 7.3).
• If possible, try manually assigning 7.1 a new address and check if it appears correctly in the panel.
2. Check Loop Communication & Integrity
• Swap the wiring positions of 7.1 and 7.2. If 7.1 still does not work in its original location, there might be a wiring fault.
• Inspect loop continuity using a multimeter to check for loose or broken cables at 7.1’s location.
• Look for ground faults or short circuits around the 7.1 sensor wiring.
3. Inspect Loop Device Configuration in the Panel
• Verify in the fire panel configuration that 7.1 is correctly assigned and not disabled or misconfigured.
• Run a loop device scan from the panel to check if 7.1 is detected properly.
• If your system has a service tool or software for loop mapping, check if 7.1 is recognized correctly.
4. Investigate Power Issues
• Measure voltage at 7.1’s base plate when powered. Compare this with 7.2 and 7.3.
• If voltage is lower at 7.1’s base, there may be a poor connection or an issue in the loop power distribution.
5. Check for Software or Firmware Issues
• If other steps fail, consider rebooting the system or checking if a firmware update is needed for the fire alarm panel.
Next Steps
• If wiring and addressing are fine but the problem persists, try adding another known working sensor to 7.1’s position.
• If even a working sensor fails at 7.1, then it’s almost certainly a wiring or panel recognition issue.
Hello Den, I would like to thank you for your elaborate guidance. As loop 6 and 7 are identical, we swapped 6.1 with 7.1. Both the smoke sensor tested found satisfactory.
DeleteThank you for feedback.
DeleteGood day, Vessel is facing an issue with false fire alarm from paint store, it is coming simultaneously, It is an isd type smoke detector. I tried to disable the detector, even after disabling, still false alarm is coming, so changed with new detector, still problem exist. Kindly help me to sort out this issue
ReplyDeleteGood day,
DeleteSince you’ve already replaced the ISD smoke detector and the false alarms persist even when the detector is disabled, the issue could be related to one of the following:
Possible Causes & Troubleshooting Steps
1. Contaminated Environment (Dust, Fumes, or Humidity)
• Paint stores often have fumes, solvent vapors, or high humidity, which can cause false alarms.
• Ensure proper ventilation and check for any recent painting or chemical work in the store.
2. Loop or Communication Issues
• Since disabling the detector didn’t stop the alarm, the loop might be experiencing faults or ghost alarms.
• Check for ground faults or loop voltage fluctuations using a multimeter.
• Inspect the loop cabling for any damage or loose connections.
3. Faulty Input from Another Device
• Verify if any manual call points or other devices are linked to the same zone and causing activation.
• Check the event logs in the central panel to see if the alarm originates from the correct address.
4. SCI (Short Circuit Isolator) Issue
• Since you’ve had SCI-related issues before, a faulty SCI might be triggering false alarms.
• Try bypassing the nearby SCI (if possible) or check if SCI activation logs are present in the system.
Next Steps:
1. Try isolating the loop segment where the paint store detector is connected. If the false alarm stops, the issue is in that part of the loop.
2. Check for ground faults using a megger to measure insulation resistance.
3. If possible, swap the detector’s address to a different one and see if the alarm follows the address.
4. Check the panel event logs for any repeated pre-alarm conditions or communication errors.
Hi! Advanced thank you for I am asking some inputs/advice from you.
ReplyDeleteCurrently we are now facing some issues,
- The fire control panel on the bridge was stuck in CCP bios screen and fire doors are all closed (24vdc supplied magnet coil) so we go the main panel for checking
1st scenario observations
1.1) One "Loop M X module" (Loop No.2) is completely off (means no light on PS and COM as well as no lights in alarm and fault)
1.2) All other (1,3,4,5,6) Loop MX modules has both steady lights, Green light for (PS) but Yellow light for (COM)
1.3) Buscon M10 has no lights for TX RX
1.4) I/O 700H does not have (PS) light and only yellow light in (COM) 1 -4 no lights only with green light is 5-8
1.5) we have 3 units of M8 Relay and (PS) light is off and only steady Yellow light for (COM)
so we decided on changing using a spare "Loop M X module" we used as a guide for dip switch the old module, after putting the new one we disconnect and connect the (1-10) connectors from "Charger M" to reset and it, then few seconds later the fault light for Loop Module MX No's. 1,3,4,5 and 6 starts blinking but still steady Yellow light (COM) and steady Green Light (PS), but the new one fault and alarm light has no any light except for Steady Green light (PS) and Steady Yellow (COM).
Hi. I will think about your problem. First try to do basic troubleshooting for such problem.
DeleteIt looks like a major communication or power distribution issue is affecting multiple modules. Here are a few things to check:
1. Power Supply Issues:
• Since multiple modules lack PS (Power Supply) lights, verify the output voltage from the Charger M and ensure it supplies a stable 24VDC.
• Check the fuse protections for Charger M and other power distribution modules.
2. Bus Communication Failure:
• The Buscon M10 has no TX/RX lights, indicating no data exchange. This could be due to:
• A failure in Buscon M10 itself.
• A short or open circuit in the bus wiring.
• A fault in a connected module disrupting communication.
3. Loop M X Module Behavior:
• The newly installed Loop MX Module (Loop 2) only has steady PS and COM lights but no fault or alarm indications.
• The remaining loops show steady COM yellow lights, which might mean a bus communication issue.
Suggested Steps:
1. Power Check:
• Measure the actual voltage at each module’s power terminals.
• If power is absent at multiple modules, trace back to the Charger M or any intermediary power distribution points.
2. Bus Check:
• Disconnect Buscon M10 and inspect its connections.
• If possible, replace Buscon M10 with a spare or try resetting it by temporarily disconnecting its power.
3. Loop Isolation Test:
• Try disconnecting all loops from the system.
• Reconnect them one by one and observe if a particular loop is causing the issue.
4. BIOS Stuck at CCP:
• If the CCP panel is stuck in BIOS, it may indicate:
• A corrupt firmware or hardware failure.
• Loss of communication with essential system components.
Do you have access to any log messages or error codes from the main panel or a way to check the system logs?
Hi, as of now we do not have access on main panel.. only clicking sounds and lights from keys. The repeater panels only has this fault 185 - No Poll from Master ( from manual - the module has not received any communication from the backbone master in the last 30s)
DeleteFault 185 (“No Poll from Master”) means the backbone master is not communicating with the system. Given that the main panel is unresponsive (only clicking sounds and key lights), the issue likely originates from the central processing unit (CCP) or backbone communication bus.
DeleteNext Steps:
1. Check CCP Panel Power Supply:
• Since the CCP is stuck in BIOS, it may not be fully booting. Try power cycling the CCP by shutting it down (if possible) or disconnecting its power source for a few minutes before reconnecting.
• If the CCP has a separate power supply unit (PSU), check if it’s delivering the correct voltage.
2. Inspect Backbone Communication:
• The backbone bus connects all system modules. Since multiple modules have no TX/RX activity, the backbone communication might be down.
• Check for any disconnected or damaged communication cables.
• If possible, locate the backbone master module and see if it has power and active TX/RX signals.
3. Try Resetting the System:
• If power and connections are intact, try resetting the Buscon M10 by disconnecting it and reconnecting after a few minutes.
• Check if there’s a reset procedure for the CCP in your manual.
Since the fire doors are affected, restoring backbone communication is urgent. Do you have any spare Buscon M10, backbone cables, or access to the main CPU of the system?
We changed out a "dirty" smoke detector but the problem remains - still at 96% ... what is the system actually looking at here? resistance? what's the next step? changing out the base? what else would cause this fault?
ReplyDeleteWhen system reports a high contamination percentage (e.g., 96% dirty), it means the detector is measuring excessive optical chamber contamination, not electrical resistance. The system monitors the degradation of the optical sensor’s clarity, typically caused by dust, soot, or other particulates accumulating inside.
DeleteWhy is the contamination level still at 96% after replacing the detector?
The system might still be reading the old contamination value from the loop. Possible reasons include:
1. Configuration / Memory Issue
• Some Salwico panels do not automatically reset contamination levels when a detector is replaced.
• Try performing a manual reset from the panel or a device re-poll to update the status.
2. Detector Base Issue
• A faulty or corroded detector base could be causing false readings.
• Check the base connections and consider replacing it.
3. Wiring Issue
• If the loop has voltage fluctuations or grounding issues, it might interfere with readings.
• Inspect for loose connections, damaged cables, or noise interference.
4. Software Filter Delay
• Some systems have a contamination averaging function that does not immediately clear the value.
• Wait 5–10 minutes and check again.
5. Multiple Detectors in the Same Address / Loop Issue
• If two detectors are mistakenly assigned the same address, the panel might still be reading an old contamination value from a different device.
Next Steps:
1. Try resetting the contamination level from the panel (if your model allows it).
2. Re-check loop voltage and base connections to rule out installation issues.
3. If contamination persists, replace the detector base.
4. If still unresolved, verify system addressing and try a full loop re-poll.
Let me know what you’ve tried, and we can troubleshoot further!
Hello Den good day I am facing an issue with (151)fault:central 1 board ZB 61 configured not present input card.
ReplyDeletecan you please advice,maybe you have solutions
what can possibly be done to rectify it .Thanks
Greetings! The (151) Fault: Central 1 Board ZB 61 Configured Not Present Input Card means that the fire alarm system expects to detect an input card (ZB 61) in the central panel, but it is either missing, faulty, or not communicating properly. Here are some steps you can take to troubleshoot and resolve the issue:
Delete1. Check Physical Connection
• Open the fire alarm control panel and verify that the ZB 61 input card is installed in its designated slot.
• Ensure the card is securely seated in the backplane connector. Try reseating it by removing and reinserting the card.
• Inspect for any loose or damaged wiring connected to the card.
2. Power Cycle the System
• Restart the fire alarm panel by powering it off completely and turning it back on after a few minutes.
• Check if the fault clears after rebooting.
3. Inspect LEDs and Indicators on ZB 61
• If the ZB 61 has LED indicators, check for any abnormal blinking or no lights at all.
• No lights may indicate that the card is not receiving power or has failed.
4. Check Configuration and Software Settings
• Log into the system configuration and confirm that the ZB 61 card is correctly assigned and enabled in the system setup.
• If the card was replaced recently, ensure that the system configuration was updated to reflect the new card.
5. Test the Backplane and Slots
• If possible, swap the suspected faulty ZB 61 card with a working one from another slot.
• If the issue follows the card, then the ZB 61 is likely faulty and needs replacement.
• If the issue remains in the same slot, the backplane or main CPU board may have a fault.
6. Check for System Firmware Issues
• If the panel was recently updated or modified, there might be compatibility issues with the firmware.
• Ensure that the firmware version is correct and up to date.
7. Replace the ZB 61 Card (If Necessary)
• If all troubleshooting steps fail and the card is confirmed faulty, replace it with a new one and update the system configuration accordingly.
8. Contact Consilium Support
• If the problem persists despite these steps, it may require specialized diagnostics. Contact Consilium technical support for further assistance.
Good day. I have find your advice and tried to troubleshooting an issue on our vessel unsuccessful. Having LOOP ANALOGUE 1 CABLE BREAK NEGATIVE, FAULT (142); LOOP ANALOGUE 1 CABLE BREAK POSITIVE, FAULT(141); ZONE 1 SCI 18 NO ANSWER, FAULT(128).
ReplyDeleteAs per following instructions:
Disconnected power supply and measured resistance for cable breaks with +/-, all readings were satisfactory.
Isolated sections/zones with bypass/jumper on the SCI (All faults active only on the loop 1 with 44 sensor); From the number of 2 to number of 18 have (A/-) cable breaks and from number of 19 to number of 44 have (-/B) cable break). Number 18 is SCI and after swapping from bridge SCI are both good conditions with communication. And after continuously make same test with deactivated/disconnected SCI from number of 18 haven’t any lost of sensors being after SCI and still appears of several sensors on those zones. After disconnected SCI from different locations( SCI 36) which is follow next from SCI 18 and after that I get done order with success resetting failure ZONE 1 SCI 18 NO ANSWER, FAULT(128).
If we exclude all the reasons that have been checked, namely have:
Polarity satisfactory. Have 35VDC.
Resistance with bypass/jumper between SCI and MCP methods are satisfactory. Have 0MOhm.
Next step to checking zone which includes sensors from 19 to 35.
What could you advise in this case? I'll be grateful for your response.
Good day. I see you’ve done thorough troubleshooting, and it’s good that you’ve ruled out polarity, voltage, and basic wiring issues. Based on your findings, here are a few things to consider next:
Delete1. Check for Intermittent Connections or Hidden Damage
Since you have ruled out resistance issues with bypass/jumper testing, there might still be a hidden problem, such as:
• Loose terminal connections in junction boxes or within sensor bases. Try tightening and rechecking.
• Micro-breaks in cables that only cause issues under load (wiggle test cables while monitoring faults).
• Corrosion or moisture ingress inside cable glands or connectors.
2. Test SCI Isolation Again
Since SCI 18 originally showed “No Answer” but resetting SCI 36 resolved the issue, try these steps:
• Bypass SCI 36 again and see if it affects the faults on 19-35.
• If the faults persist, try bypassing SCI 35, then SCI 34, etc., working backward.
• If isolating different SCIs clears faults, one of them might be failing under load.
3. Check Communication Integrity
• Use an oscilloscope (if available) to check signal quality on the loop.
• If SCI 18 and the sensors behind it still report properly after bypassing, but faults still exist elsewhere, there may be excessive noise or interference affecting communication.
4. Test Sensors in the Affected Section (19-35) Individually
• If possible, disconnect sensors one by one to see if any specific device is causing instability.
• Swap sensors from a working area to a faulty area and see if the problem follows.
5. Potential Issue with Loop Driver or MX Module
If the loop is large (44 sensors) and the issue remains random, there might be a loop power issue or intermittent fault in the Loop MX module.
• Check if other loops have similar issues.
• If you have a spare Loop MX module, swapping could help diagnose.
Since you’ve managed to reset Fault 128 (SCI 18 No Answer), focusing on sensors 19-35 is a good next step. Let me know what you find after further isolation testing.
Please be informed I have on the Loop 1 only 4 SCI’s with number of SCI 2, SCI 9, SCI 18, SCI 36.
DeleteI got your message and I will be in touch soon with details for.
Thanks for the clarification. Since you have only four SCIs on Loop 1, here’s how you can refine your troubleshooting:
Delete1. Verify SCI Functionality Again
• You mentioned that bypassing SCI 36 helped reset the “SCI 18 No Answer” fault. This suggests that SCI 36 might be affecting communication downstream.
• Try bypassing SCI 9 and see if that impacts faults on sensors 2-18.
• If possible, swap SCI 9 or SCI 36 with a known good SCI from another loop (if available) to check for changes.
2. Check Loop 1 Sensor Groups Again
Since faults are divided into two sections:
• Sensors 2-18: A/- cable break (Fault 142)
• Sensors 19-44: -/B cable break (Fault 141)
Try these steps:
• Disconnect sensors from 19-35 one by one while monitoring the faults.
• If the cable break fault disappears when a specific sensor is removed, it may indicate a faulty sensor or base.
3. Measure Voltage at Different Points
• Measure the loop voltage at the terminals of SCI 9, SCI 18, and SCI 36 while faults are active.
• Compare with the normal 35VDC reading—if voltage drops significantly at any point, that might indicate an issue with wiring or SCI function.
4. Inspect Loop for Ground Faults or Interference
• If all physical connections seem fine, check for grounding issues.
• Disconnect the loop from the panel and measure insulation resistance between loop conductors and the ship’s structure.
• If resistance is low, you might have a ground fault contributing to the instability.