Resources / After-sales Support
Let’s work through it.
Help us understand your device, setup and the issue you are seeing.
Resources for your device
FC8135
Embedded QR and card reader
Start with the device and the symptom.
A short, reproducible report helps us identify the right next step. Contact the team for device operation, installation references or integration questions.
Identify your equipment
Include FC8135 and its configuration, order reference if available, firmware and application version. A photo of the device label helps distinguish configurations.
Show the setup
Describe the power supply, interface, connected controller or host, and mounting. Include a wiring diagram or clear connection photo where relevant.
Describe what happens
List the steps, expected result, actual result and whether the issue is repeatable. A short video or sanitised log can help. Remove passwords, tokens and personal biometric information.
Find the right reference.
Use the download centre to find documents by model. If your configuration’s manual is not listed, request it with the model and firmware so the team can identify the appropriate version.
Before returning equipment.
Contact the team with the product and order details before sending a device back. Warranty eligibility, inspection, repair, shipping and return authorisation are reviewed against the applicable order and product terms.
Quality assurance & service →Documents for FC8135.
- Download PDF
FC8135 user manual
Manual · English · PDF · 615 KB
The source manual uses the Q350 hardware designation.
Common questions for FC8135.
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 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.