r-tec Error Codes and Fault Symptoms

When a door opens but will not close, or a code appears on the display, the first question is which system is reporting the symptom. Identify the motor, control board and stage of movement before deciding which part needs replacement. The same symptom can have different causes on different boards.

This guide brings model manuals together for dealers’ and partners’ technical teams. An end user can record an externally visible symptom; electrical connections, door mechanics, force, brake and limit settings belong to trained technicians. Alkur handles manufacturer assessment through dealers, distributors or partners. It does not provide site surveys, installation or direct end-user servicing.

Where should the assessment start?

1. Identify the equipment: Record separate model/revision labels for the motor, board and receiver. The door name alone does not identify the board.
2. Describe the symptom: Record the display, LED state, movement direction and whether it occurs during opening, closing or learning.
3. Choose the correct section: Use the code table for LUVI/R2; use the behaviour and indicator descriptions for other boards.
4. Verify the cause: The technical team checks mechanical movement, safety inputs and connections against the installed model’s manual. Safety devices must remain active during testing.
5. Record the outcome: Add the work performed, symptoms before/after and any unresolved problem to the fault information package.

Stop use if movement is uncontrolled, the door fails to stop at its limit or there is visible mechanical damage. Repeated commands are not a fault-finding method.

What do LUVI/R2 error codes mean?

This table follows the fault scope on PDF pages 13–14 of the LUVI manual. It does not apply to other boards. The manual writes o1–o9; some FAQ rows use 05 and 08. A photograph preserves the actual display notation.

Code	Meaning in the manual	Direction of assessment
o1	Door jammed while opening	Record where movement stops; the technical team checks obstructions and mechanical movement.
o2	Door jammed while closing	Assess an obstruction in the closing path separately from mechanical binding.
o3	High-current protection	The warning alone does not prove motor failure. Assess mechanical load and the control/motor circuit.
o4	Button fault	Assess the command button and associated input rather than assuming the entire board has failed.
o5 / 05	Radar fault	The manual identifies continuous radar commands, excessive sensitivity and viewing angle as checks.
o6	Mechanical jam	Check movement and the leaf assembly. Increasing force is not the first remedy.
o7	Low battery voltage	Technicians assess battery and supply condition; the code does not establish battery life or replacement intervals.
o8 / 08	Photocell fault	Sensors may be misaligned or a cable damaged. Check alignment, cable and input.
o9	Low mains voltage	Assess the power supply. Electrical measurement is not an end-user procedure.
10	Encoder error	The encoder/cable or mechanical binding during relearning can produce the same warning.
11	Sustained overcurrent protection	The manual describes protection when excessive current lasts over 5 seconds. Assess the cause before restarting.
St	Service due	A maintenance/service reminder does not by itself mean the motor has failed.

Menu entries and faults differ: In the settings menu on PDF page 12, o1 is opening acceleration distance. In the fault table it means a jam during opening. Record the display mode alongside the notation.

Learning indicators are separate: Sequential flashing 1-2-3 relates to the learning movement. If the door does not progress, the manual directs checks of the leaf guide and tension-wheel pressure. A single continuously flashing 1 is associated with the function-selector connection. Neither is read as the o1 fault.

Clearing a warning, relearning and a factory reset are different operations. Removing the display message does not establish that its cause has been resolved. Resetting before recording the symptom can make diagnosis harder.

Motor, limit-switch and board symptoms

For these models, diagnosis follows the LED indicators and movement symptoms. Interpret each symptom using the relevant model and manual page.

Symptom and model	Possible cause / technician’s assessment
Door closes on an open command: 220-K, HITIT 1000, FU	Verify motor and limit directions together. Direction-setting methods differ; a DIP number from one board must not be applied to another.
Door reaches the limit switch but does not stop: 220-K, HITIT 1000	Assess limit direction, switch assembly and connection matching. Keep the system out of use.
Motor operates in one direction only: 220-K, HITIT 1000	The manual lists switch-assembly wiring as a possible cause. The symptom alone does not justify replacing the motor.
No LEDs illuminate: 220-K, HITIT 1000, G24	Assess supply, fuse and, for G24, transformer possibilities before assessing board failure.
Other G24 LEDs illuminate but D3 does not	The manual lists processor protection as a possible cause. A persistent condition needs board assessment. D4 indicates motor type; it is not an error number.
Motor moves briefly then stops: G24, I-380	Manuals identify current/power settings as checks. First establish free mechanical movement and motor/door matching; raising a setting is not a universal remedy.
I-380 green LED is on but the motor does not move	Assess the STOP circuit, safety switches, manual mode/crank and thermal protection. Green does not prove the complete system is operational.
I-380 red LED is steady or flashing	The manual associates flashing red with phase sequence and steady red with a unit fault. Record the two states separately.
I-380 motor hums but does not move	Output connections/supply wiring are checks in the manual. Humming alone does not prove a burnt-out motor.
380A D30 or D31 flashes with C78	D30+C78 points to phase sequence; D31+C78 to a possible missing R/S phase. All LEDs flashing is associated with the neutral line. Technicians perform electrical checks.

Source scope: 220-K and HITIT 1000 PDF p.7; G24 TR pp.3–4 and 8–9; I-380 EN p.8; 380A TR p.6. Live electrical measurement, phase/wiring changes and relay intervention are not presented here as end-user procedures.

Photocell fault or expected safety response?

A door that opens but does not close does not necessarily have a failed photocell. An obstruction, misalignment and cable damage are separate possibilities. External observation can record an obstruction, dirt or a displaced sensor. Technicians check alignment, supply, cable and the board input.

G24 TR PDF p.3 distinguishes direction: Photocell 1 stops and reopens the door when detecting an obstruction during closing. Photocell 2 stops opening movement while the obstruction remains, then allows opening to continue. Record movement direction when reporting that a photocell stopped the door. These behaviours do not apply automatically to every board or input.

For LUVI/R2 08, assess the photocell circuit first. For an I-380 door that opens but does not close, assess LED 7/the photocell circuit as described in its manual. Do not substitute another model’s LED name or reset sequence. Bypassing a safety input or disabling a photocell is not a repair.

Remote controls: is matching frequency enough?

433 MHz on both devices does not establish compatibility. Consider FIX/ROLLING protocol, receiver variant, operating mode and the ROLLING company code together. Record whether one transmitter or all transmitters fail. If the door works from a local command, the remote/receiver path can be examined separately; that observation is not a definitive component diagnosis.

The procedures below are for an authorised person who has identified the correct receiver and manages access permissions. Socket and electrical work belongs to the technical team.

RF-433/F FIX pairing and deletion

Pairing: Press the learn button and release when the red LED lights. Hold the transmitter button to be paired and release when the receiver LED goes out. Repeat for each new transmitter.

Delete all: Hold the learn button. The LED lights steadily; release when it begins flashing. Once the LED goes out, stored transmitters have been erased. This does not erase only a lost transmitter. The manual gives neither a fixed button-hold duration nor an individual-record deletion method.

RF-433 ROLLING pairing, deletion and mode

Pairing: Press the learn button and release when the red LED lights. Hold the relevant transmitter button; release when the receiver’s red LED starts flashing. The transmitter can be used when the LED goes out.

Delete all: Hold the learn button. The LED lights, goes out and lights again; release at the second illumination. It stays on for 20 seconds, then goes out: all transmitter records are erased. This does not remove company-code binding. Individual deletion is not described in this document.

Standard/common mode: Common mode uses DIP 4 on the plug-in receiver and DIP 1 on the wired receiver. The manual describes switching power off and restoring it after 5 seconds; four LED flashes are followed by approximately 20 seconds of steady illumination. The technical team performs this hardware operation. Changing mode also erases existing transmitter records. Common mode retains the same-company-code and same-transmitter-button conditions; a transmitter from another company is not assumed compatible.

Pairing a PULL1000 remote

The procedure is for an authorised person who has verified the installed model/revision and manages access permissions:

1. Press CODE; the display shows SU.
2. Hold the open/close button on the transmitter to be paired.
3. When the display text starts flashing, communication with the device has taken place.

The hold-button step follows the current device-operation confirmation. PDF p.4 of the TR and EN manuals describes this stage as one and two presses respectively. The dealer verifies the installed device/revision; this procedure does not extend to other PULL models.

Delete all: TR PDF p.4 describes holding CODE through SU to DL, then releasing it to erase all codes. Assess affected users and transmitters that will need pairing before deletion.

What should the dealer send for assessment?

The following record gives manufacturer assessment a useful starting point. Customer identity, transmitter codes and private access details must stay out of public photographs or examples.

• Motor, board and receiver model/revision, with readable label photographs.
• Exact code/LED notation, steady/flashing state and display mode.
• Opening, closing, learning or the stage after power is supplied.
• Affected commands: one/all transmitters and the local-command result.
• When the problem began and the last maintenance, adjustment or part change.
• Manual name/page, checks performed by the technical team and their results.
• A short observation video from a safe distance, without recreating dangerous behaviour.

The dealer, distributor or partner submits this package. A photograph or code does not constitute a confirmed replacement decision or a completed remote repair.

Handling differences between manuals

The G24 TR document contains differences between supply/installation voltage statements and between LED names. The EN document supplied under the G24 name is headed 3S; it is not treated as an exact translation. DIP, fuse and wiring instructions from the two documents must not be combined.

Direction/brake recommendations on FU TR PDF p.9 do not agree with the DIP functions on p.4. Use the symptom table, but verify conflicting DIP/brake instructions for the installed revision before applying them. The FU symptom table is not an inverter error-code table.

Related reading

The division of responsibilities is explained in Who Gets the Call When the Door Stops?