Skip to main content

Engineering FAQ · Wanlin

Click-and-Collect Device Board Integration Requirements

Published: · Updated:

Direct answer

Review Click-and-Collect Device Board Integration Requirements using the actual interfaces, software, environment and acceptance evidence. Confirm the exact configuration against controlled project documents.

Published configuration: confirm against controlled documents

The AS-RK3588-OPF-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.

BlockSpecification
SoCRockchip RK3588 octa-core Cortex-A76/A55 up to 2.4GHz; RK3568 / RK3566 quad Cortex-A55; RK3399; RK3288; Allwinner A133, H618 or T527 on the value tiers
NPURK3588 6 TOPS INT8; RK3568 1 TOPS; value tiers without NPU
GPURK3588 Mali-G610 MP4; RK3568 Mali-G52 2EE; A133 PowerVR GE8300
MemoryLPDDR4 / LPDDR4X / LPDDR5, 2GB to 16GB depending on tier
StorageeMMC 5.1 8GB / 16GB / 32GB / 64GB / 128GB; UFS 2.1 option; TF card; M.2 NVMe on the RK3588 carrier
DisplaySingle, dual, triple or six independent outputs: LVDS / eDP / MIPI DSI / HDMI; 1920x1080, 3840x2160 or 7680x4320 decode; independent or mirrored; portrait or landscape per output
TouchCapacitive 10-point / 20-point; dual touch controllers on request; IR touch on request
Payment and peripheralsQR / NFC / face payment, barcode imager, thermal printer, cash drawer, weighing scale, load-cell front end, RFID, fingerprint, ID card reader
CameraMIPI CSI 2-lane / 4-lane, ISP, 30 fps multi-camera capture for device vision and liveness checks
I/O4x USB 2.0, 2x USB 3.0, RS232 / RS485, up to 6 isolated serial ports, GPIO island up to 48 channels, relay, PWM, I2C, SPI, CAN bus, RS232 pass-through with hardware flow control
NetworkDual Gigabit Ethernet, PoE+ option, WiFi 5 / WiFi 6, Bluetooth 5.0, 4G LTE / 5G module, SIM slot, 2.4 GHz radio island for shelf labels, GPS option
OSAndroid 11 / 12 / 13 / 14 / 15; Linux; Ubuntu; Debian; OpenHarmony; AOSP; GMS or GMS-free; kiosk mode
Power12V DC standard; wide-voltage 9-36V on request; PoE+ on request; hold-up capacitor for brownout ride-through; battery-first variants under 1.2W idle
Thermal and reliabilityFanless 6-layer carrier; 0C to 50C standard, -20C to 70C wide temp; 52C sealed-cabinet rating; 24/7 duty; hardware watchdog; RTC backup; ESD and EMC design
Form factor3.5-inch SBC, Pico-ITX, Mini-ITX, or core board plus custom carrier; signage player box and locker controller enclosures

Application matrix: 8 customization scenarios for the AS-RK3588-OPF-CUS

The AS-RK3588-OPF-CUS is one carrier platform across eight different O2O deployments. The matrix below shows the most common OEM/ODM customization angles an R&D hardware lead in Oceania walks through in the first scoping call.

ScenarioCatalog board limitAS-RK3588-OPF-CUS customization
O2O smart terminal and kioskConsumer image, single output, 3.1 s handoverGMS-free kiosk image, dual-facing output, 0.7 s handover
Smart device controllerNo load-cell path, 1 Hz pollingCompensated load cell, real-time 1 min cadence
Vending machine and cabinet8 GPIO, 44C throttle, no 4G failover36-channel island, 52C sealed rating, dual-path failover
Smart locker and parcel bank8 GPIO, 1 Hz door poll48-channel island, sub-200 ms hardware interrupt
Digital signage player box1080p ceiling, memory leak8K decode, 30-day soak-tested loop
Dual-screen self-service terminalMirrored output, 380 ms driftTwo framebuffers, sub-16 ms sync
Order pickup and fulfilmentCloud-only match, 2.8 sLocal match under 900 ms, 30 min offline hold
Multi-platform O2O familyFour carriers, two contractsOne enclosure, one BSP train, one MOQ

OEM/ODM workflow: 8 steps from kickoff to first article

Below is the actual OEM/ODM workflow an R&D hardware lead in Wellington walks through when commissioning a custom O2O smart device Android motherboard from AndroidSBC. No step is a placeholder.

  1. Day 0-2 — Requirements intake. A 90-minute call captures the device format, the I/O map, the payment stack, the OS choice, the certification scope and the volume profile. Output: a one-page requirements sheet.
  2. 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.
  3. Day 7-11 — Schematic and PCB layout. The AS-RK3588-OPF-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.
  4. Day 12-16 — BSP porting. Android, Linux, Ubuntu, Debian or OpenHarmony BSP is ported to the customer's OS choice, with PREEMPT_RT patches and kiosk-mode locking where needed. Output: a BSP build for the customer's evaluation team.
  5. Day 17-21 — 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.
  6. Day 22-24 — Customer evaluation. The customer's evaluation team runs thermal, EMC, payment-peripheral and field-replication tests. Output: an evaluation report with sign-off or change requests.
  7. Day 25-26 — 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-seven days from kickoff to first article. Ninety days from kickoff to mass production. This is the OEM/ODM rhythm that the R&D hardware lead in Oceania 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 O2O smart device 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: 27 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 an O2O terminal?
Answer: RK3588 for device vision, multi-camera capture, 8K decode and triple or six independent display; RK3568 for interactive terminals, lockers, vending cabinets and signage boxes where 1 TOPS and 4K dual display are sufficient; A133, H618 or T527 for shelf-edge and cost-driven tiers. AndroidSBC builds all of them on the same enclosure cut-out.

Can the board run offline when the network drops?
Answer: Yes. Durable offline queues, a signed local ledger, a 30-minute pickup session hold and a last-known-value cache for shelf pricing are all standard customization options, with LAN plus 4G dual-path failover.

Can you drive two or more screens with independent content?
Answer: Yes. Up to six independent outputs on the RK3588 carrier with per-screen resolution, refresh and rotation, independent LVDS and eDP clock domains, sub-16 ms frame sync, and optional dual touch controllers.

How do you handle an interrupted firmware update?
Answer: The OTA path is atomic with A/B redundancy and a bootloader-level rollback, so a device that loses power mid-update boots the previous known-good image instead of a dead unit.

Can the board drive a locker or vending bank directly?
Answer: Yes. A 48-channel isolated GPIO island with per-door current sensing for lockers, or a 36-channel motor and door-sensor island with per-channel current sense for vending cabinets, plus 400,000-cycle relay drivers.

What certifications can you pre-scope for our market?
Answer: CE / FCC / RoHS standard. UL / UKCA / KC / PSE / SAA, GMS / Google EDLA, EMVCo L2 and PCI PTS are all pre-scoped on request. EMC pre-scanning is done in-house before third-party testing.

Do you support OEM/ODM and private label?
Answer: Yes. Custom logo, custom firmware, custom boot animation, custom UI, private-label PCBA and custom SDK modules are all standard OEM/ODM deliverables, with the boot identity and UUID owned by the customer.

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 17-21 day window. Small-batch and large-volume pricing is available on request.