Skip to main content

Linak Actuator - Failed to Start Error

Sumaiya
Updated

Overview

This error is reported when the actuator fails to start. There are many issues that can cause this, including:  

 

Resolving the Error

You won't be able to schedule the Bay until the error is cleared.

Lost Position

You can identify if the actuator has lost its position from the Actual Position it's showing on Monitor. Go to the Monitor card of the actuator and click on the 'Summary' field:

This will expand into a graph and you'll be able to see the Actual Position of the actuator. If the position is 3276.6 mm, the actuator has lost its position. In other words, the actuator no longer knows what position it's at, and it will need to be initialised.

Lost_position.png

The Initialise command is found in the cog menu of the Monitor Card. There are two options, Initialise Inwards or Initialise Outwards. 

Initialising the actuator inwards will leave it in a fully retracted state ('Open' for iRisers, while 'Closed' for iLifters).

Initialising the actuator outwards will leave it in a fully extended state ('Closed' for iRisers, while 'Open' for iLifters). 

Try running the actuator with a regular Open/Close command after running the initialisation to confirm the actuator moves. If it doesn't, try the steps in Initialisation Issues below.

 

Communications Timed Out

If the Failed to Start error is accompanied by Communications Timed Out error, it is possible that the wiring between the actuator and C3 is loose or damaged. Check if the wires and cables are connected securely to the field unit and Linak Actuator. Also check for any damage, shorts, pinching, etc. 

If a wiring issue has been found and fixed, run the actuator to remove the error. The action is found in the cog menu of the Monitor Card.

Cog_menu.png

Screen_Shot_2018-01-24_at_4.57.29_pm.png

 

Low Voltage Error

This error is due to low voltage on the power supply, which indicates the actuator is drawing more current than the field unit can support. There are a number of likely causes for this, which are described in detail in this article.

 

Initialisation Issues

If none of the above errors are associated with the "Failed to Start", running the initialisation routine on the actuator a couple of times can help resolve the issue.

If the actuator is in a fully extended state ('Closed' for iRisers, while 'Open' for iLifters):

  1. Initialise inwards.
  2. If that works, initialise outwards.
  3. Then initialise inwards.
  4. Finally try running the actuator out with a regular command, i.e. 'Close' for iRisers, or 'Open' for iLifters.

If the actuator is in a fully retracted state ('Open' for iRisers, while 'Closed' for iLifters):

  1. Initialise outwards.
  2. If that works, initialise inwards.
  3. Then initialise outwards.
  4. Finally run the actuator in with a regular command, i.e. 'Open' for iRisers, or 'Close' for iLifters.

If the above doesn't help, the actuator electronics have probably failed. See next section. 

 

Water Ingress

If the Failed to Start error keeps occurring, it is likely the actuator has been damaged with water. As a result, it will fail to operate and will need to be replaced. 

Powered by Zendesk