Greetings! Another article in the "blog" section, here I want to share with you some thoughts about the service that periodically has to be ordered for ships for the purpose of repair or maintenance of various ship systems.
Let me remind you that in the articles in the "blog" category I do not write some super useful information. It can be just some thoughts, reasoning or interesting stories from the sea life of an electrician. Although even in these articles someone will find something useful for themselves.
It so happened that the ship's Autoprime Autronica fire alarm completely failed. Of course, for the ETO and the entire crew this is a real headache. For the electrician, this is an endlessly long and laborious process of troubleshooting, for the management - endless correspondence with the office and superintendents, for the rest of the crew - additional watches. In general, everyone is tense, and especially the electrician.
Background of the breakdown
The Autoprime Autronica marine fire alarm is a rather capricious Norwegian alarm system. Among the disadvantages of this system, I would like to note the fact that after each replacement of any sensor with a new one, it must be rebooted (to add sensors to the system). And if it so happens that you have frequent replacements of sensors with new ones (the ship is 7 years old and sensors are just starting to fly out), then you will have to reboot it very often.
ETOs who work on ships over 10 years old know that old equipment should be rebooted less often. This has to be done if nothing else helps to solve the problem. I will not describe specific examples here, but it often happens that the equipment "glitches" (especially old) and needs to be rebooted. So, after such reboots, it happens that the unit "dies" completely.
Instructions for replacing fire detectors Autoprime Autronica
HOW TO REPLACE DETECTORS FOR FIRE DETECTION SYSTEM (AUTRONICA)
* Detectors for AUTRONICA has auto address functions.
- Check and compare defective sensor with new sensor specifications.
- Replace defective sensor.
- Alarm will be generated. New sensor connected and will ask to transfer old sensor setting to new.
- Go to Next supervisory level to transfer old detector settings to new on settings. Password: 9999
- Go to setting and reset. Save new configuration. Then restart Fire detection panel.
- Finish system reboot (Loading all loop driver).
- Loop Driver 1 – 56 Normal Operation
- Loop Driver 2 – 51 Normal Operation
- Loop Driver 3 – 51 Normal Operation
- Loop Driver 4 – 10 Normal Operation
- Panel Bus – 2
Check if new detector registered under which loop. (Normally new sensor will appear at the last of list with the same address used in old sensor).
As you can see (from the instructions above), you need to install a new sensor and reboot the system from the menu so that the sensor is initialized and added to the program. That is, the sensor is addressed automatically here.
In this case, the new sensor must be exactly the same as the old one, for example, it can be a combined Heat + Smoke (i.e. reacts to both heat and smoke) and if you install only a Smoke sensor, the fire system will give an error, or rather add this sensor to the system, but at the same time an error will hang in place of the old one.
An additional watch and patrols of the superstructure and engine room were temporarily established. In this situation, fortunately, the ship also had a separate Tyco Minerva sprinkler fire extinguishing system with its sensors, which partially covered the monitoring of the engine room.
1. New BSA200 board for Autroprime installed.
- Old firmware: 2.0.2 on existing board.
- On board the system was stuck in recovery mode so the configuration could not be loaded from the system.
- The vessel had a backup configuration file as well as a configuration file built using the latest software.
2. Replaced the board and restarted the system with the pre-installed firmware 2.1.8.3. The system had a failure on the 4th loop.
- The entire beam failed completely.
- Checked with AS2000, all OK.
- Checked the MCP manual call points which are external, some corrosion was found but nothing serious. When putting the A4010 manual call point back in, the pin was noticed to be broken so this MCP was replaced with a new unit from the vessel's spares.
- Checked other call points, no issues found.
- After a thorough troubleshooting, the problem could not be found.
- 4. Maker reported that firmware 2.1.8 does not support the special MCP used externally. Therefore, the firmware version was downgraded to 2.1.5.
Now the error showed that loop 4 was not configured correctly, so the configuration file was imported again, now the errors are gone.
5. Smoke sensors on loop 4 were checked, everything is fine now.6. Loops 1, 2 and 3 were checked and found to be working.
Important! On old fire systems, try to reboot the systems as little as possible. There is always a chance that after a reboot the system will stop working! Fight to the last with the sensors (perhaps a thorough cleaning will eventually give a positive result).
Important! Make backups of the fire system configurations, if they are not yet on the vessel. In the future, if there are problems, this will help to restore operability faster.
Video of working with the Autronica fire alarm system
Video of testing the Autronica fire sensor
Video of the cleaning procedure for the Autronica fire sensor
Autoprime by Autronica is a modern Norwegian marine fire alarm system designed to detect and quickly respond to fires on ships. Autronica, with extensive experience in fire alarm systems, focuses on the marine market, creating solutions that can withstand the harsh conditions of the marine environment.The Autoprime system is highly reliable and integrates various sensors to detect smoke, heat and other signs of fire. This allows for the precise location of the fire and immediate notification of the crew. Key features include:
- Fast fire detection. Thanks to advanced algorithms and sensitive sensors, the system detects even small fires.
- High immunity to false alarms. The system is configured to minimize false alarms, which is especially important on ships where conditions can provoke abnormal signals.
- Support for various detector types. The system can use smoke, heat and combined sensors, which provides comprehensive protection.
- Compatibility with other ship security systems. Autoprime can be integrated with other ship systems, such as automatic fire extinguishing and warning systems, which improves the overall efficiency of emergency response.
- Easy to maintain and configure. The system is designed with personnel convenience in mind, which simplifies maintenance and diagnostic procedures.
Autronica's Autoprime ship fire alarm system is a reliable fire safety solution that meets stringent international standards such as SOLAS and other maritime regulations.
Troubleshooting an Autoprime Autronica Fire Alarm System involves systematic checks to identify and resolve faults. Here are some common issues and troubleshooting steps:1. Power IssuesSymptoms:
- The panel is unresponsive.
- Display is blank or flickering.
Troubleshooting:
- Check the main power supply (230V/110V AC).
- Verify the battery backup connection and charge level.
- Inspect fuses and circuit breakers.
2. Communication ErrorsSymptoms:
- "Communication failure" or "Loop failure" messages.
Troubleshooting:
- Check loop connections for loose wiring.
- Inspect for damaged cables or ground faults.
- Ensure correct addressing of loop devices.
- Restart the control panel and monitor for error recurrence.
3. Device Faults (Detectors, MCPs, Sounders)Symptoms:
- A detector, manual call point (MCP), or sounder is showing as faulty.
Troubleshooting:
- Remove and reseat the device.
- Clean the detector (dust, dirt, or insects may cause false faults).
- Replace faulty devices if cleaning does not resolve the issue.
- Verify correct wiring and polarity.
4. False AlarmsSymptoms:
- The system frequently goes into alarm without a real fire condition.
Troubleshooting:
- Check for environmental factors (dust, humidity, high temperature).
- Ensure proper detector placement (avoid near kitchens, steam sources).
- Clean the affected detectors and recalibrate if needed.
- Review alarm event logs to identify recurring issues.
5. Panel Faults or Software IssuesSymptoms:
- Panel displays "CPU fault" or "Configuration error."
Troubleshooting:
- Restart the panel (soft reset).
- Verify the software configuration and correct any errors.
- If using networking, check for IP conflicts or connection issues.
- Update firmware or reload the configuration if necessary.
6. Sounder or Bell Circuit FaultSymptoms:
- Alarm sounders or bells do not activate.
Troubleshooting:
- Check wiring connections to sounders.
- Test output voltages at the sounder terminals.
- Verify configuration settings in the panel.
- Replace faulty sounders.
7. Ground FaultsSymptoms:
- "Earth fault" or "Ground fault" warning.
Troubleshooting:
- Inspect all wiring for damaged insulation.
- Disconnect sections of the loop to isolate the fault.
- Use a megohmmeter to check for grounding issues.
8. Network or Integration IssuesSymptoms:
- The system does not communicate with external monitoring or BMS.
Troubleshooting:
- Verify network settings (IP, subnet mask, gateway).
- Check physical connections (LAN cables, fiber optics).
- Restart network switches or routers if applicable.
Preventive Maintenance Tips
- Regularly test the system as per NFPA/EN standards.
- Keep the panel firmware up to date.
- Conduct periodic cleaning of detectors.
- Train personnel on system operation and fault response.
Manuals! If you need instructions, configuration files or software for the Autronica fire alarm, I recommend our closed telegram channel Marine Engineering Manuals.
.jpg)
.jpg)
.jpg)
.jpg)

Thank you very much for such a detailed troubleshooting of the Autoprime Autronica fire system.
ReplyDeleteWhat I want to know is whether there is a "walk test" mode, like the one on the Minerva system. In Minerva's walk test mode, sensors are more sensitive, and the entire system can be switched to test mode with a single button. Here, do we have to select the detectors to be tested one by one without activating the alarm?
ReplyDeleteService Menu → Unit Test → Detection Zones
DeleteYou can select one or several detection zones using the multiselect function and put them into test mode. Once a detection zone is in test mode, you can test any detector or manual call point within that zone individually, for example with test gas, without automatically activating the sounders, bells, Fire Protection Equipment (FPE), or Fire Alarm Routing Equipment (FARE).
So you do not have to select every detector one by one.
The important distinction from Minerva is that Autroprime’s test mode is zone-based, not a single global “Walk Test” button for the whole system. You select the required Detection Zone(s), activate their test condition, and then walk around testing the individual detectors.
The panel indicates that one or more detection zones/FADs are in Test Condition with the corresponding yellow indication.
thank you so much for information. i have a another problem loop mismatch fault, i dont have a WAS 2000 tool, what is posible reason for ``loop mismatch`` eror. thank you for all information
DeleteOn the Autronica Autroprime fire alarm system, a “Loop Mismatch” fault does not necessarily mean that you need the WAS 2000 tool. In most cases, it means that the actual devices detected on the loop do not correspond to the configuration stored in the fire alarm panel.
DeleteThe most common reason is that a detector, module, or other loop unit has been replaced, added, or removed. For example, if one detector was replaced with another type, or a detector was installed at a location where there was previously no device, Autroprime can detect that the loop topology has changed and generate a configuration mismatch.
Another possibility is a communication problem with one of the loop devices. A detector may not be responding because of a bad detector base, loose connection, corrosion, damaged cable, or an intermittent connection. In this situation the physical loop may still operate, but the panel sees a different topology from the one stored in its configuration.
I would first enter the Service Menu and check the loop topology shown by Autroprime. Compare the devices displayed by the panel with the actual detectors and modules installed on the loop. If, for example, the panel normally sees devices 1, 2, 3, 4, 5, 6, etc., but now one device is missing or the topology changes around a particular address, I would inspect that detector, its base and the cable connections around it.
If the complete topology is detected correctly but the panel still reports Loop Mismatch/Configuration Mismatch, then I would suspect that the stored configuration does not correspond to the actual devices. This can happen after maintenance or replacement of loop units. In that case the configuration may need to be updated and saved through the Autroprime service functions.
thankyu so much again, system not give a specific malfunction adres, i load again backup configuration later give me specific malfunction adress, i renew dedecetor and system turn to normal mode, i very difficult system for work
DeleteYou’re very welcome. Yes, Autroprime can be quite difficult to troubleshoot because sometimes the initial fault indication is not very specific. Reloading the backup configuration and getting the specific detector address was a good troubleshooting step. After replacing the detector, the system returning to normal confirms that the detector was most likely the source of the fault.
DeleteAutroprime has quite a different logic from older fire alarm systems, so it can take some time to get used to it. Once you understand the relationship between FAD address, detection zone, loop, and controller, troubleshooting becomes much easier.