Hardware control layer for unattended machines

Connect machines to your own control and data API.

QuLink turns MDB, pulse, relay, and serial machines into API-connected devices. Send commands, collect machine data, and use QuLink QR payment when the machine needs scan-to-start.

Request specs See the API model

QuLink Control Layerdevice: VM-1049

MachineMDB / Pulse / Relay / Serial

QuLink BoardTranslate + Connect

Your ServerCommands + Data + Events

POST /v1/devices/VM-1049/commands
{
  "command": "trigger_relay",
  "source": "api_or_qr",
  "duration_ms": 800
}

No platform lock-inNo closed SaaSNo protocol rebuild

Device control hardware

Your platform sends commands. QuLink moves machine data and actions.

Your platform controls

Your cloud, app, and business logic
Your payment provider, wallet, checkout, or QuLink QR payment workflow
Your customer data and backend
Your pricing, loyalty, and operations flow

QuLink hardware handles

Machine control board and connectivity
MDB, pulse, relay, serial, and QR payment trigger logic
Device commands, data upload, webhooks, and telemetry
OEM board customization for repeat deployment

Board examples

Real board styles for machine integration projects.

These board examples cover the machine-side jobs customers usually ask about: retail control, PLC vending, lift control, QR/API trigger, 4G data transmission, display/payment terminals, relay control, metering, charging, and lock control.

Retail / 4G / Data

Retail 100-channel 4G control board

Vending and smart retail main control, multi-channel I/O, 4G connectivity, telemetry, and remote commands.

PLC / Vending / Relay

PLC vending multifunction board

PLC vending control, relay outputs, motor/slot control, cabinet wiring, and API-driven operation.

Lift / Vend / Sensor

Lift vending control board

Lift cabinet control, elevator motor coordination, drop detection, serial/MDB integration, and vend result reporting.

4G / Cabinet / Telemetry

4G retail controller board

Retail cabinet controller with cellular module, SIM, multi-port wiring, machine status upload, and remote control.

QR / API / Trigger

QR / API trigger board

Scan-to-start and API command board for payment callback, relay trigger, timed run, unlock, or dispense actions.

4G / IoT / OTA

4G IoT terminal enclosure

Compact cellular control box for remote equipment connection, data upload, OTA support, and field installation.

4G / Retrofit / Data

Compact 4G control box

Small 4G controller for machine data transmission, remote command, and retrofit integration.

Module / Data / Server

4G data module board

Cellular data module for connecting legacy machines to a server with telemetry and command callbacks.

Android / Display / QR

Android display main board

Display or smart cabinet main board for touch screens, QR workflows, media UI, and peripheral connections.

Display / Payment / Serial

Display payment main board

Screen payment terminal board with SIM, USB, serial, audio, and API connectivity for scan-to-start machines.

Display / Terminal / API

Display payment main board variant

Another display-controller form factor for payment screens, interactive panels, and connected smart devices.

Face / Payment / Screen

Face payment terminal

Terminal-style hardware for face recognition, screen payment, wallet login, or identity-based machine start workflows.

Lock / Relay / Access

Door lock relay controller

Lock, gate, access, room, locker, and timed relay control with QR/API command trigger.

Metering / I/O / Relay

Multi-I/O metering control board

Water, laundry, charging, sensor input, metering, relay output, and equipment-state reporting.

Charging / Payment / Session

Charging payment controller kit

Charging and payment controller kit for display, card/QR module, relay output, and usage session control.

Machine coverage

Machine scenarios these boards can cover.

Use the real board examples above as building blocks. QuLink maps them to the control, connectivity, data upload, and payment-trigger layer for common unattended machines. AI vision, RFID parking, or highly specialized controllers should be evaluated as OEM projects.

Covered

Vending / Smart Retail Boards

Screen and no-screen vending boards, MDB equipment, PLC vending boards, lift controllers, drop sensors, and smart cabinet control.

MDB gateway / OEM controller

Covered

QR Payment / Payment Box

QR payment screens, payment boxes, card terminals, and scan-to-start controllers that need a payment callback to trigger the machine.

QR/API trigger board

Covered

Timed Pulse / Relay Equipment

Kiddie rides, amusement machines, massage chairs, laundry, car wash, charging sockets, table rooms, and timed relay devices.

Pulse / relay controller

Covered

Machine Data Upload

Status, fault alerts, usage logs, vend results, telemetry, video/result events, and cloud callback data.

Machine data bridge

Custom

Water / Charging / Metered Devices

Water control, liquid dispenser boards, e-bike charging, power metering, time billing, and full-stop charging logic.

OEM control board

Evaluate

AI / RFID / Vision Kits

Face recognition, AI cabinet vision, RFID parking, BLE beacons, and advanced sensing modules.

OEM integration

Control workflow

From your API command to a real machine action.

QuLink sits between your server and the machine interface. Your system sends a command, the board translates it into MDB, pulse, relay, or serial control, then reports the machine result back.

Identify device

Select the machine by device ID, route, cabinet, slot, relay channel, or timed session.

Send command

Your server sends a signed command such as start_session, trigger_relay, unlock, dispense, stop, or query_status.

Run machine

The QuLink board translates the command into MDB, pulse, relay, serial, unlock, or timed-run action.

Report result

The board returns online status, command result, telemetry, fault alerts, vend result, or session data to your cloud.

QuLink QR payment

Add QR payment when the machine needs scan-to-start.

QuLink can provide the QR payment workflow as an add-on. After payment is confirmed, QuLink turns the payment event into the same machine control command.

Generate QR

Create a QR code for a machine, product, price rule, relay channel, or timed session.

Confirm payment

Use QuLink QR payment, or connect your own wallet/provider callback when you already have a payment stack.

Trigger action

After confirmation, QuLink starts, unlocks, dispenses, pulses, or runs the machine and reports the result.

Machine categories

Built for equipment where software must trigger a physical action.

Vending and Smart Retail

MDB vend, QR vend, telemetry, inventory event, drop result.

Amusement and Kiddie Rides

Pulse simulation, timed play, token replacement, session start.

Laundry and Service Equipment

Timed relay, cycle start, QuLink QR payment or app callback, machine state event.

Lockers and Charging Devices

Unlock, rent, return, charge session, device online/offline, data upload.

Developer API

Control and data APIs for machine protocols.

Your software team should not need to rebuild MDB timing, pulse width, relay duration, serial frames, telemetry upload, or vend-result handling from scratch.

Commands

start_session, trigger_relay, dispense, unlock, stop, query_status

Data and Events

device.online, command.accepted, telemetry.updated, machine.fault, vend.result, session.completed

POST /v1/devices/{device_id}/commands
{
  "command": "start_session",
  "source": "api_command",
  "machine_action": {
    "type": "relay",
    "duration_ms": 800
  },
  "reference_id": "CMD-2026-10492"
}

POST /webhooks/qulink
{
  "event": "payment.confirmed",
  "device_id": "VM-1049",
  "action": "trigger_relay",
  "telemetry": {
    "online": true,
    "last_result": "session_started"
  }
}

Technical FAQ

Common questions from machine operators, OEMs, and system integrators.

Can QuLink provide QR payment?

Yes. QuLink can provide QR payment workflows for scan-to-start machines. Customers can also connect their own payment provider, wallet, app, or server callback.

Can QuLink collect machine data?

Yes. QuLink boards can upload status, telemetry, vend results, fault alerts, sensor values, and operation logs to your server.

Which machine interfaces can QuLink connect?

QuLink supports MDB, pulse, relay, UART, serial, RS485, QuLink QR payment workflows, and custom OEM board interfaces.

Who is this built for?

System integrators, machine operators, payment apps, wallet providers, and machine OEMs that want hardware connected to their own backend.

Project RFQ

Tell us what the machine needs to do, send, or report.

Send a short note first. We can confirm machine interface, API workflow, data upload, QuLink QR payment or your own payment callback, and quantity in the next step.