Published configuration: confirm against controlled documents
The AS-RK3568-RSC-CUS carrier board is a 6-layer PCB in a 3.5-inch SBC form factor, industrial-grade components throughout, with conformal coating optional. The specifications below are the OEM/ODM default; every line is re-specable on request.
| Block | Specification |
|---|---|
| SoC | Rockchip RK3588 octa-core Cortex-A76/A55 up to 2.4GHz; RK3568 / RK3566 quad Cortex-A55; RK3399; RK3288; Allwinner A133 on the value tiers |
| NPU | RK3588 6 TOPS INT8; RK3568 1 TOPS; value tiers without NPU |
| GPU | RK3588 Mali-G610 MP4; RK3568 Mali-G52 2EE; A133 PowerVR GE8300 |
| Memory | LPDDR4 / LPDDR4X / LPDDR5, 2GB to 16GB depending on tier |
| Storage | eMMC 5.1 8GB / 16GB / 32GB / 64GB / 128GB; UFS 2.1 option; TF card; M.2 NVMe on the RK3588 carrier |
| Display | Single, dual or triple independent outputs: LVDS / eDP / MIPI DSI / HDMI; 1920x1080, 3840x2160 or 7680x4320 decode; independent or mirrored; portrait or landscape per output |
| Touch | Capacitive 10-point / 20-point; dual touch controllers on request; IR touch on request |
| Ticket and print | Thermal ticket printer, receipt printer, ticket dispenser, barcode imager, QR reader, document printer, A4 printer option; current-budgeted rails |
| Calling and audio | On-board audio decode, amplifier control, voice broadcast module, speaker module, microphone input, per-counter and per-zone volume, runtime multi-language voice packs |
| Display network | Window screen, counter display, waiting area display, room display, hall display status board; multicast push so 60 displays refresh from one host; LED controller and LCD controller options |
| Identity and payment | ID card reader, bank card reader, NFC reader, RFID reader, fingerprint reader, face recognition option, QR payment |
| Camera | MIPI CSI 2-lane / 4-lane, ISP, 30 fps capture for people counting and document capture |
| I/O | 4x USB 2.0, 2x USB 3.0, RS232 / RS485, up to 6 isolated serial ports, GPIO island up to 32 channels, relay, PWM, I2C, SPI, CAN bus |
| Security | Secure boot chain, trusted execution environment, trusted platform module option, discrete secure element, hardware key storage, signed audit trail |
| Network | Dual Gigabit Ethernet, PoE+ option, WiFi 5 / WiFi 6, Bluetooth 5.0, 4G LTE / 5G module, SIM slot, GPS option |
| OS | Android 11 / 12 / 13 / 14 / 15; Linux; Ubuntu; Debian; Kylin OS; UOS; OpenHarmony; AOSP; GMS or GMS-free; kiosk mode; runtime locale packs |
| Power | 12V DC standard; wide-voltage 9-36V on request; PoE+ on request; hold-up capacitor for brownout ride-through; RTC wake and scheduled power profile |
| Thermal and reliability | Fanless 6-layer carrier; 0C to 50C standard, -20C to 70C wide temp; 46C glazed-hall rating; 24/7 duty; hardware watchdog; RTC backup; ESD and EMC design |
| Form factor | 3.5-inch SBC, Pico-ITX, Mini-ITX, or core board plus custom carrier; counter-top, floor-standing and wall-mounted enclosures |
Application matrix: 8 customization scenarios for the AS-RK3568-RSC-CUS
The AS-RK3568-RSC-CUS is one carrier platform across eight different queue terminal deployments. The matrix below shows the most common OEM/ODM customization angles a restaurant chain operations lead in Southeast Asia walks through in the first scoping call.
| Scenario | Catalog board limit | AS-RK3568-RSC-CUS customization |
|---|---|---|
| Hospital and clinic ticket terminal | Printer brownout, no on-board audio | Budgeted printer rail, on-board audio path |
| Bank branch queue kiosk | 3.7 s card read, no secure element | Under 800 ms read plus issue, discrete secure element |
| Government and tax office counter | One serial port, 40 s session timeout | Three-function serial map, 20-minute offline hold |
| Window screen with voice calling | 11 s refresh poll, single-line render | Push refresh under 1 s, multi-line layout |
| Restaurant and service centre terminal | One serial port, cloud-only queue table | Multi-port serial map, on-board local queue table |
| Dual-screen ticket plus advertising | Mirrored output, 380 ms drift | Two framebuffers, per-screen proof-of-play |
| Multi-zone waiting area network | 60 unicast polls, blanking on a blip | Multicast push, local content mirror |
| Multi-platform queue family | Four carriers, two contracts | One enclosure, one BSP train, one MOQ |
OEM/ODM workflow: 8 steps from kickoff to first article
Below is the actual OEM/ODM workflow a restaurant chain operations lead in Surabaya walks through when commissioning a custom queue management kiosk Android motherboard from AndroidSBC. No step is a placeholder.
- Day 0-2 — Requirements intake. A 90-minute call captures the counter format, the I/O map, the language and voice list, the OS choice, the calling workflow, the print and pager peripherals and the volume profile. Output: a one-page requirements sheet.
- Day 3-6 — Feasibility study. AndroidSBC engineers validate the SoC choice (RK3588, RK3568, RK3566, RK3288, RK3399 or A133), the carrier I/O map, the BSP availability, the certification gap and the thermal envelope. Output: a feasibility report with go / no-go on each customization.
- Day 7-10 — Schematic and PCB layout. The AS-RK3568-RSC-CUS carrier board is laid out on a 6-layer stack-up with the customer's I/O map. Output: schematic and PCB review package.
- Day 11-14 — BSP porting. Android, Linux, Ubuntu, Debian, Kylin OS, UOS or OpenHarmony BSP is ported to the customer's OS choice, with PREEMPT_RT patches, kiosk-mode locking, secure boot, runtime voice packs and multicast display support where needed. Output: a BSP build for the customer's evaluation team.
- Day 15-18 — Sample fabrication. Five to ten engineering samples are fabricated at the Shenzhen source factory, with conformal coating and stencil rework as required. Output: samples shipped to the customer by air.
- Day 19-21 — Customer evaluation. The customer's evaluation team runs thermal, EMC, print, calling-latency, audio and field-replication tests. Output: an evaluation report with sign-off or change requests.
- Day 22-23 — Design freeze and mass-production tooling. Any change requests are absorbed, the design is frozen, and mass-production tooling is opened at the source factory. Output: a frozen Gerber and a frozen BOM.
Twenty-eight days from kickoff to first article. Ninety days from kickoff to mass production. This is the OEM/ODM rhythm that the restaurant chain operations lead in Southeast Asia learns to expect from a Shenzhen source factory that does this work for a living.
Frequently asked questions
What is the MOQ for a custom queue management kiosk Android motherboard?
Answer: 150 units for OEM (a re-spin of an existing carrier board), 500 units for ODM (a from-scratch PCB layout). Sample orders of five units are accepted with an engineering report.
How long does OEM/ODM customization take from kickoff to first article?
Answer: 28 days on the workflow described above, including schematic, PCB layout, BSP porting, sample fabrication and customer evaluation. Mass production starts around day 90.
Should I choose RK3588 or RK3568 for a queue kiosk?
Answer: RK3588 for dual-screen ticket plus advertising kiosks and multi-zone display controllers with heavy video; RK3568 for hospital ticket terminals, bank branch kiosks, government counters, window displays and restaurant terminals where 1 TOPS and 4K dual display are sufficient; A133 or RK3566 for cost-driven ticket and display tiers. AndroidSBC builds all of them on the same enclosure cut-out.
Can the board keep issuing tickets when the server is unreachable?
Answer: Yes. The on-board queue table and the non-volatile ticket counter keep issue running offline, and the branch or clinic call order survives a hard power cut.
Can the window screen refresh within a second of a call?
Answer: Yes. Call events are pushed rather than polled, with sub-second window screen refresh, sub-400 ms voice announcement and a local content mirror so a zone keeps showing the last call during a network blip.
Can one host drive sixty zone displays?
Answer: Yes. A multicast receive path lets 60 waiting-area displays refresh from one queue host, with sub-800 ms propagation across five rooms and per-zone language selection.
Do you support multi-language voice announcements?
Answer: Yes. Runtime voice packs are selected per counter or per zone with no per-language re-spin of the firmware image, including right-to-left layouts where the market requires them.
Can the board drive a printer, a card reader and a pager base at once?
Answer: Yes. The peripheral power tree is budgeted for ticket printer, card or ID reader, scanner, pager base and voice module together, with isolated rails and soft-start sequencing so nothing browns out at peak.
What certifications can you pre-scope for our market?
Answer: CE / FCC / RoHS standard. UL / UKCA / KC / PSE / SAA, GMS / Google EDLA and payment pre-scoping are all available on request. EMC pre-scanning is done in-house before third-party testing.
Do you accept sample and small-batch orders?
Answer: Yes. Samples ship in 1-3 days from stock where available; custom samples ship inside the 15-18 day window. Small-batch and large-volume pricing is available on request.
