The board does not start up electrically, nor does it light up its green and red LEDs when powered up or when waking from standby by pressing one of its buttons.
|
|
The circuit board does not respond when a remote control button is pressed or a code is entered on the wireless keypad. First of all, check that the remote control is working properly (LED lights up when a button is pressed, battery replaced, etc.). We recommend that you carry out the tests using several remote controls, to avoid a technical problem on a single remote control.
|
|
|
|
If radio range is lost :
|
If the card reacts when it is off standby (LED L0 on) but does not react when it is on standby (LED L0 off) :
|
Your actuator starts without a given command, or stops on its own during a cycle without an error code.
|
|
The card does not take into account your passage in front of the photocells:
|
|
The card takes into account your passage in front of the photocells, but only at the beginning and end of the closing cycle:
|
When the card encounters an error, either during a self-learning phase, or during an operating cycle, it will stop the current cycle and display one or more red LEDs. It’s important to note this error code so you can understand what’s happening. WARNING: Self-learning and operating cycle (command given by remote control or dry contact) have similar error codes (same LED lighting up), but different meanings. Pay attention to the operation the card is performing when the error occurs, to know which code to refer to.
This error code indicates that the board did not see the current peak of the M1 electric motor when the gate reached the stop during the first closing phase of self-learning.
|
|
|
|
This error code indicates that the board did not see the current peak of the M2 electric motor when the gate reached the stop during the first closing phase of self-learning.
|
|
|
|
This error code indicates that the board has not seen any current drawn by the electric motor connected to M1.
|
|
This error code indicates that the board has not seen any current drawn by the electric motor connected to M2.
|
|
This error code indicates that the card thinks that the M1 leaf has reached its opening stop in less than 3s, whereas the gate has started from its closed position.
|
|
|
|
This error code indicates that the card thinks that gate leaf M2 has reached its opening stop in less than 3s, whereas the gate has started from its closed position.
|
|
|
This error code indicates that the electronic board did not see the current peak of the M1 motor when it reached its opening stop.
|
|
|
This error code indicates that the electronic board did not see the current peak of the M2 motor when it reached its opening stop.
|
|
|
This error code indicates that the electronic board has not seen any current consumption by the M1 motor during the opening phase.
|
|
This error code indicates that the electronic board has not seen any current consumption by the M2 motor during the opening phase.
|
|
These error codes indicate that the board has failed to calculate motor currents correctly.
|
|
|
This error code indicates that the board has detected overconsumption of the M1 motor for a given time during a closing cycle. This error code is normal if the leaf has been held back by an obstacle, or possibly a prolonged gust of wind. If the fault persists :
|
|
|
If this error code appears when the motor reaches the closing stop:
|
This error code indicates that the board has detected overconsumption of the M2 motor for a given time during a closing cycle. This error code is normal if the leaf has been held back by an obstacle, or possibly a prolonged gust of wind. If the fault persists :
|
|
|
If this error code appears when the motor reaches the closing stop:
|
This error code indicates that the photocell beam has been cut during a closing cycle This error code is normal if there is an obstacle between the leaves when the closing cycle is started, or if someone has crossed the beam during a closing cycle.
If you do not have photocells :
|
If you have photocells, with no obstacles between them:
|
|
This error code indicates that the board has detected overconsumption of the M1 motor for a given time during an opening cycle. This error code is normal if the leaf has been held back by an obstacle, or possibly a prolonged gust. If the fault persists :
|
|
|
If this error code appears when the motor reaches the closing stop :
|
This error code indicates that the board has detected overconsumption of the M2 motor for a given time during an opening cycle. This error code is normal if the leaf has been held back by an obstacle, or possibly a prolonged gust. If the fault persists :
|
|
|
If this error code appears when the motor reaches the closing stop:
|
This error code indicates that the board has not seen any current drawn by the electric motor connected to M1.
|
|
This error code indicates that the board has not seen any current drawn by the electric motor connected to M2.
|
|
This error code indicates that the card has detected the end of the closing travel of leaf M1 before the arrival of leaf M2.
|
|
|
|
These error codes indicate that the card has detected several consecutive obstacle detections (over-consumption of a motor for a given time during an opening or closing cycle). This error code is normal if the leaf has been held back by an obstacle, or possibly a prolonged gust of wind. If the fault persists :
|
|
|
If this error code appears when the motor reaches the closing stop:
|
This error code indicates that the board has lost its power supply and has regained it This error code is normal if you have switched off the board, or if there has been a power cut. If this code appears when launching a self-learning or operating cycle :
|
|
|
This error code indicates that teach-in has not been performed, or that a setting requiring teach-in has been made.
If this error code appears systematically after an electrical restart, the board must be returned to the workshop for a software update.
This error code indicates that a wired control device connected to the board has its contact permanently closed.
|
|
|
A cross-test can be used to identify the precise source of a non-driving motor fault.
To do this, reverse the motor connections on the board.
Once this has been done, you need to run a new test cycle to see whether the initial error code is the same (and the fault appears on the motor that was working properly beforehand), in which case the board output is affected, or whether the error code changes (and the same motor is still faulty), in which case it’s the electric motor that’s at fault.