Application illustration of an FC7788 flush QR reader beside a shared meeting room

QR readers.
Made to fit.

From a meeting-room door to connected equipment. Find the form that fits your workflow.

Find your model

Small devices.
Connected spaces.

A display for guided interactions. A compact reader for the door. An embedded module for your equipment.

Application illustration of an FC6820 display terminal at a shared workspace entrance

Give the workflow a screen.

FC6820 combines a display with QR and card options.

Application illustration of an FC7780 QR reader beside a shared study-room door

At the door.

FC7780 for QR and NFC credential reading.

Application illustration of an FC8135 reader integrated into an equipment panel

Part of your equipment.

FC8135 fits embedded reader applications. Confirm the opening and host interface for your project.

Already in
everyday spaces.

Field photographs of FC7780 at a shared study-room entrance and FC7788 at a shared meeting room.

Explore solutions
FC7780 reader beside the entrance of a shared study room, field photograph
FC7780 · Shared study room
FC7788 reader at a shared meeting-room doorway, field photograph
FC7788 · Shared meeting room

AI-generated application scenes illustrate possible settings, not customer installations or installation specifications. The two field photographs above show actual deployment environments.

Find your fit.

Start with the physical format, then confirm code source, credential mix, host interface and mounting.

Compare models
Available features vary by configuration.
ModelDisplayCore useCredentialsInterface / mounting
FC68203.33-inch touch displayQR and card access with an on-device interaction pointQR code, password and card options by configuration86-box surface mounting; Ethernet, RS485, Bluetooth and optional Wi-Fi
FC68223.33-inch touch displayIntegrated QR and card input for flush-mounted installationsQR code, password and card options by configurationFlush mounting; Ethernet, RS485, Bluetooth and optional Wi-Fi
FC6825Compact touch displayQR and card workflows that need clear on-device feedbackQR code and card options by configurationInstallation and host interfaces are selected for the project
FC7735No displayCompact QR input at doors and connected equipmentQR code and optional NFC card86-box mounting; Ethernet, Wiegand, RS485 and relay options
FC8135No displayQR input integrated into gates, kiosks and equipmentQR code and optional NFC cardEmbedded mounting; Ethernet, Wiegand and relay options
FC7785No displayNarrow-format QR and card access pointsQR code and card options by configurationWall or 86-box installation depending on configuration
FC7780No displayDoor and shared-space credential readingQR code and NFC card86-box mounting; Ethernet, RS485, Wiegand and relay options
FC7788No displayIntegrated QR input for meeting rooms and connected spacesQR code and NFC cardFlush 86-box mounting; USB, RS232, RS485, Wiegand, Wi-Fi and Ethernet options

A few things worth knowing.

What should I check if serial output is missing or unreadable?

Match the baud rate, data format and electrical interface on both sides, then inspect the cable and any serial-to-USB adapter. Also confirm whether the reader is sending raw content or a framed protocol message before treating additional bytes as corrupted data.

Why can output differ from the original QR content?

A reader in transparent output mode may send the original content, while a protocol or development mode can add a header, length, device information and check data. Select the mode that matches the host application and use the protocol reference for that model and firmware.

Can repeated scans of the same code behave differently?

Yes. Single-read and interval modes can treat repeated presentation of the same code differently, while a different code may still be accepted immediately. Confirm which modes and repeat intervals are available for the selected reader before defining the user flow.

Can the same configuration tool be used for every reader?

Do not assume so. Reader firmware and access-control firmware can use different tools, configuration codes or platform commands. Share the overseas model, firmware and intended operating mode so the matching method can be checked before changing settings.

What should we check when a reader does not react to a code?

First confirm that the reader has started normally and that the code is complete, correctly generated and presented within the usable reading area. For codes shown on a phone, raise the screen brightness and remove glare; if known-good codes still produce no response, record the indicator and buzzer behavior for support.

Does registering a person automatically grant access?

Not necessarily. Identity enrollment and access permission are separate steps in many systems. Confirm that the person, credential, target device, schedule and permission group have been linked and that the authorization was delivered successfully.

Is a network connection the same as a connection to the management platform?

No. A device can have local network access without maintaining its platform or messaging connection. Check the physical network, IP settings and service connection separately, using the indicators or logs available for the selected system.

What should we check when a controller receives no reader data?

Compare the RS485 wiring, polarity, grounding and communication settings with the instructions for both devices. Then confirm the reader output mode and controller input configuration; a correct cable cannot compensate for mismatched communication settings.

Let's find the right device.

Configuration, compatibility and delivery scope are confirmed for your project.

Shop products Downloads Discuss your project