Resources / FAQ

A clearer starting point.

Answers to common questions about product selection, device integration and development.

Clear filters

Resources for your device

FC7735

86-box QR and card reader

21 answers for FC7735

Questions about FC7735.

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 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.

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.

What should I share when choosing a device?

Tell us which credentials people will use, where the device will be installed, which interfaces are required and what should happen in the software workflow. A mounting drawing, host-equipment description or simple process diagram helps us identify the questions that must be confirmed before recommending a configuration.

Does every configuration include the same features?

No. Credential modules, interfaces, mounting parts, network options and software can vary within the same product family. Confirm the exact model and selected options in writing before designing an enclosure, cable set or integration around it.

How can I get a manual or datasheet?

Find available documents by model in the download center. If the manual, specification or installation drawing you need is not listed, send the model and configuration to our team so we can identify the matching document.

How should we evaluate a product for our project?

Sample orders for access-control devices and smart locks start at two units. Turnstile quantities depend on the cabinet and lane configuration. Minimum quantities for custom orders are confirmed for the project. Start with the credential, mounting, interfaces and software flow that matter to the final installation. Confirm the sample configuration in writing, test it in the intended environment and record any differences before planning a larger rollout.

What is DejaOS used for?

DejaOS is Feocey’s Linux-based embedded operating system for smart access terminals, HMI and edge devices. It provides a JavaScript development environment, with a native C/C++ SDK for low-level work. Developers can build device interfaces and application workflows using the modules available for the selected hardware, SDK and firmware.

Does every Feocey product support DejaOS?

No. DejaOS is pre-installed on selected Feocey access-control and video intercom models, and not every Feocey device runs it. Android models such as FCV4906 and FCV5006 are outside DejaOS. Confirm the exact overseas model and configuration with Feocey before choosing a development device, and check the matching SDK, firmware and hardware modules in the current official documentation.

Can an example for one device run on another?

Some JavaScript logic and resources can be reused. Native modules, SDK versions, screen dimensions and hardware capabilities must match the target. Use an example as a starting point. Test every hardware-dependent part on the actual device.

What should I check when a device module cannot load?

Check that the project targets the correct device and SDK, then reinstall the matching module version and synchronize it to the device. A file being present in the project does not prove that its native library is compatible with the target hardware.

Are the application interface and boot screen customized in the same way?

It depends on the product type. On DejaOS developer devices, which are embedded devices you buy and develop on yourself, you can customize the boot screen, home UI, logo, color theme and menus in your own application. On Feocey standard (off-the-shelf) products, branding or boot-image customization may need separate firmware preparation and a different delivery process. Share the exact model, whether the devices are new or already deployed, and the desired asset before planning the change.

What do we need before starting DejaOS development?

Start with a confirmed supported development device, the required power and USB connection, and the current DejaOS development tools described in the official documentation. Confirm the exact target model before installing modules or adapting an example.

What does a typical DejaOS development workflow look like?

Select the target device, prepare the project and matching modules, synchronize the application, then run and debug it on the hardware. Validate the user interface, peripherals and failure behavior on the target device before preparing a production release.

Why can a device restart while an application is being debugged?

A sample may include watchdog behavior, or the application or a hardware module may be failing during execution. Check whether a watchdog is enabled, reproduce the restart with a minimal project and collect the device log before deciding that the hardware is faulty.

What changes when moving from development to production?

Development and production configurations can differ in startup behavior, debugging access and how the application is delivered. Confirm the release procedure for the exact firmware and test a production-configured unit before preparing the rest of the devices.

What should I include in a technical support request?

Include the overseas product model, firmware or software version, connection method and a short sequence that reproduces the issue. Screenshots, indicator behavior and relevant logs help; do not send passwords, access credentials or personal biometric data.

What should we check if a device repeatedly restarts?

Compare the power supply voltage, current capacity and wiring with the specification for the selected configuration. If the problem continues, record whether it happens at startup or during a particular action and send the model, firmware and observations to technical support.

Can I customize the UI and business logic of an access control device?

Yes, on a model that runs DejaOS. DejaOS is the embedded operating system for that work. JavaScript is the primary language, and you can replace the default access UI with your own application, including the business logic of the access workflow. Not every Feocey device runs DejaOS. Android models such as FCV4906 and FCV5006 are outside it. Confirm the model before you start.

Is Feocey an access control hardware manufacturer?

Yes. Feocey supplies access control hardware as OEM and ODM. Manufacturing follows the confirmed project scope. Software customization is available. Hardware customization is discussed case by case, and only when it follows Feocey’s product direction.

Can Feocey build a face recognition terminal under our brand?

Feocey can discuss a face recognition terminal under your brand. Software customization, including branding and the device application, is available when the selected model supports that change. Hardware customization is discussed case by case. Samples of standard hardware products start at 2 units. Custom hardware has a minimum order of 1,000 units.

← All resources