Define the output
Confirm pulse count, relay channel, voltage expectations, session duration, and stop behavior.
Pulse and relay control
API-ready pulse relay controller for laundry and timed machines.
Use QuLink when your software needs to start a timed machine, simulate a coin pulse, switch a relay, stop a session, or report machine status back to your server.
Timed relayPulse simulationQR/app/server triggerSession result upload
Project fit
Common machines
Buyer signals
- Laundry washers and dryers that need cycle start or timed relay control.
- Kiddie rides, amusement devices, massage chairs, and room/table timers.
- Car wash, water control, charging sockets, and metered self-service equipment.
- Retrofit projects replacing coin/token input with app, QR, or server approval.
What to send first
- Machine photo or existing board photo
- Interface or wiring note if available
- Target action after API command or payment
- Whether telemetry or data upload is required
Integration model
From software approval to physical output
Your backend decides the session; the QuLink controller turns that approval into pulse width, relay duration, timed run, stop command, and result reporting.
- Machine interface
- pulse input, relay output, dry contact, sensor input, UART/serial option
- Commands
- start_session, trigger_relay, pulse_output, stop, query_status
- Session data
- accepted, started, duration, completed, fault, online/offline
- Project mode
- coin-op retrofit, timed equipment rollout, OEM control box
Workflow
From machine interface to API-controlled result.
Map the trigger
Trigger can come from QR payment, app approval, operator panel, or your server command.
Run session
QuLink sends the pulse or relay output and tracks the session state.
Report back
Your system receives status, result, and fault events for operations follow-up.
API example
A clear server command or webhook for the machine-side action.
The exact command fields depend on machine interface, firmware profile, and whether payment or your own app triggers the action.
POST /v1/devices/LAUNDRY-18/commands
{
"command": "start_session",
"machine_action": {
"type": "relay",
"channel": 1,
"duration_ms": 1800000
}
}
Start the project
Send the first machine details before writing a full spec.
Send the machine photo, coin input wiring, relay requirement, session duration, and whether payment should be QuLink QR or your own callback.
Useful first message
- Machine type and target country
- Machine photo, board photo, or wiring photo
- Action after API command or payment
- Data upload and estimated quantity
FAQ
Questions buyers usually ask before a sample test.
Can QuLink replace coin/token input?
In many retrofit projects, yes. The controller can simulate pulse or relay behavior after your app or payment flow approves a session.
Can it stop or query a session?
That depends on the machine interface. Relay control, sensor input, or serial integration can be evaluated from the machine wiring.
Can the same board support data upload?
Yes. The project can include online status, session result, fault alerts, and telemetry upload.
Related use cases