somdn-pro
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/storm/sites/dev-imca-int-com-1/public/wp-includes/functions.php on line 6121woocommerce-services
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/storm/sites/dev-imca-int-com-1/public/wp-includes/functions.php on line 6121woocommerce-conditional-shipping-and-payments
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/storm/sites/dev-imca-int-com-1/public/wp-includes/functions.php on line 6121woocommerce-eu-vat-number
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/storm/sites/dev-imca-int-com-1/public/wp-includes/functions.php on line 6121woocommerce-memberships
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/storm/sites/dev-imca-int-com-1/public/wp-includes/functions.php on line 6121woocommerce-order-status-control
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/storm/sites/dev-imca-int-com-1/public/wp-includes/functions.php on line 6121woocommerce-sequential-order-numbers-pro
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/storm/sites/dev-imca-int-com-1/public/wp-includes/functions.php on line 6121imca-website-2020
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/storm/sites/dev-imca-int-com-1/public/wp-includes/functions.php on line 6121What happened?<\/strong><\/p>\n During diving operations, there was a power loss scenario within dive control whereby both circuit breakers after the uninterruptible power supply (UPS) tripped, causing a loss of power to the electronic components of the dive system. Power was re-established using the UPS bypass switch. The dive was aborted to carry out investigation. No-one was harmed.<\/p>\n What went wrong? What were the causes?<\/strong><\/p>\n During setup of the dive system the UPS was set to work on approx. 220VAC input (the input from a vessel generator power supply typically fluctuates). The UPS was also set up on the assumption that the power from the vessel would not drop below 85% of the expected supply voltage (a drop to 187VAC).<\/p>\n Investigation confirmed that this is in fact what happened – the supply voltage did indeed drop below the minimum threshold of 187VAC. When this happened, an automatic and internal bypass in the UPS kicked in to keep power supplied to the outlet side. Therefore, the low voltage was transferred through the internal UPS bypass and into the circuit breakers that protected all the electronic equipment in dive control.<\/p>\n When attached to a fixed output load (such as electronic equipment), a voltage drop will necessarily cause an increase in current flow. The current increased to the point where the circuit breakers tripped to further protect the electronic equipment. This disconnection of the power to the electronics shut them down without the UPS taking over or giving any sort of alarm condition.<\/p>\n This voltage drop may have been gradual and therefore was not noticed. It wouldn’t have affected any other circuit breakers as there wouldn’t have been any power spike. However, since the UPS corrects to 85% of the input voltage, once that limit was reached it automatically transferred to the bypass, thereby immediately causing a power spike on the output side as the voltage changed from 220VAC (UPS corrected) output to <187VAC (UPS bypassed output).<\/p>\n Further investigation revealed that the low voltage was a result of a large current draw, in turn as a result of other equipment on the same power bus being used at the same time. In this case, it was discovered that the ROV was being recovered from the water at the time of the power loss. On this vessel, the dive system power is taken from the same power bus as that which is used for the ROV.<\/p>\n What actions were taken? What were the lessons learned?<\/strong><\/p>\n Members may wish to review the following incident:<\/span><\/p>\n\n