
FCC4904
Central controller for four reader ports, lock relays, door contacts and exit inputs.
Product details ↗Four-door access control solution
A four-door access control system brings readers, locks and exit controls together around the FCC4904. Shape each entrance around the people who use it, with a central point for door wiring and system integration.

The access journey
A clear operating sequence helps define the right hardware and software. Confirm reader compatibility and the permission logic for the selected configuration.
A reader captures the chosen credential at the entrance. Select QR, card or keypad hardware to fit the application.
The agreed controller and management setup checks the access request. Define permissions, schedules and offline behaviour with your integrator.
The configured relay and lock circuit provide the door action. Plan door contacts, exit buttons and emergency-release requirements together.
Explore the hardware
Start with the controller, then review the reader or keypad for each entrance. Reader options require a matching RS485 protocol and firmware. The separate keypad option uses Wiegand and is not presented as a direct FCC4904 reader connection.

Central controller for four reader ports, lock relays, door contacts and exit inputs.
Product details ↗
Compact QR reader option for the credential step at an entrance.
Product details ↗
QR reader option to review against the mounting and host interface requirements.
Product details ↗
Separate keypad option with Wiegand output. FCC4904 reader ports are RS485; a direct pairing is not established.
Product details ↗Define each connection
Installation reference

Disconnect external power before wiring. Have the installer confirm the supply, lock loads and fire-alarm integration. The following approved references show the controller terminals and wiring guidance.
Manual · English · PDF · 407 KB
Integration guide · English · PDF · 344 KB
Manual · English · PDF · 792 KB
Includes the FCC4901 / FCC4904 parameter table. Confirm enclosure dimensions and capacity with the team; the separate port and wiring references are also available.
Specification · English · PDF · 62 KB
For FCC4901, FCC4904
Shared table for single-door and four-door versions. Confirm variant, chassis dimensions and capacity before ordering or installation.
Possibly, but only after each reader is matched to the controller. A connector or catalogue listing does not establish compatibility.
FCC4904 provides four RS485 reader ports. The reader input is RS485 at 115200 baud, so a reader needs a matching RS485 protocol and firmware. A Wiegand device such as the FCS525, which documents Wiegand 26/34 output, is not presented as a direct FCC4904 reader connection. A third-party reader can work if it supports a protocol that the Feocey device supports; Feocey does not publish a tested third-party reader list, so confirm the protocol before ordering. FCC4904 communicates over TCP/IP, UDP, MQTT and RS485. OSDP is supported only on the reader or client side, so FCC4904 is not an OSDP controller.
On the door side, FCC4904 provides four relay outputs, door-contact inputs and exit-button inputs. Have the installer confirm the lock supply, lock load and wiring. FCC4904 has no cable specification on this page. For RS485, Feocey’s FC6820 wiring guide lists RVVSP 3 × 0.5 or Cat5e or better, up to 1,000 m as a theoretical maximum that can be shorter on site. Treat that as general guidance, not an FCC4904 limit. Feocey gives no Wiegand cable length.
Send the existing reader models and firmware, the lock type and load, and the exit controls when you ask for a review.
The FCC4904 specification sheet lists up to 100,000 users or cards and 100,000 offline records. Confirm the capacity for the version you are supplied.
The controller does not store permissions. Permissions are stored on the devices on the terminal or reader side, so plan user enrolment and removal for those devices.
The cost comes from the whole entrance scope, not from one reader or controller price. This page lists no prices; prices are quoted for the project.
For a four-door system, count the controller, a reader or keypad for each entrance, lock hardware and its power supply, exit buttons and door contacts, the network, and the management software or platform integration. Add installation and commissioning, plus any training and ongoing support you agree. Quantity, deployment market and site conditions affect the quotation.
Treat expiry and removal as permission changes that must reach every door, and test them before handover. Decide who may enrol users, grant access and remove permission, and where expiry rules run: on the device, in the controller or in your management platform.
Enrolling a person and granting permission are separate steps. Confirm the person, credential, door and schedule are linked, and that a removal was delivered. Then test a valid credential, an expired credential, a revoked credential and an unavailable network on the actual configuration. Permissions are held on the terminal or reader devices, not in the FCC4904 controller, so a removal must reach each device where the person is enrolled. Confirm the removal workflow for your configuration in the project review.
Test each reader and door separately: accepted and rejected credentials, exit-button operation, relay action and door-contact reporting. Agree the offline behaviour and have the installer verify the required emergency-release arrangement. Do not treat a successful card read as proof that the complete door circuit is correct.
Check the reader interface, protocol and firmware against the controller configuration. An interface name alone does not establish compatibility. A third-party reader can work if it supports a protocol that Feocey’s devices support, and the protocol should be confirmed before ordering. Feocey does not publish a tested reader list. Send the selected model list with your installation requirements.
Share the door count, reader models, lock type and load, exit controls, network plan and management software. Include the applicable fire-alarm and emergency-release requirements for the site.
Tell us how people enter, how they leave and which system manages permissions. We will help confirm the equipment and integration scope.
Allow optional Google Analytics to understand visits and interactions. We do not send your name, email or inquiry text.
Analytics stays off until you allow it. You can change your choice anytime.
Privacy notice