Confirm coin signal
Check pulse width, pulse count, voltage, and the ride's start behavior.
Kiddie ride retrofit
Kiddie ride coin pulse controller for QR or API start.
Use QuLink when a kiddie ride or amusement machine needs coin pulse replacement, QR payment trigger, timed relay run, or app-controlled session start.
Coin pulseTimed runQR triggerField retrofit
Project fit
For amusement and coin pulse machines
Buyer signals
- Kiddie rides and amusement devices that accept coin pulse or start signals.
- Operators moving from coin/token payment to QR scan-to-start.
- Machines that need timed run and session result upload.
- Projects that need a compact controller box for field installation.
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
Simulate the coin signal after approval
QuLink turns QR payment or server approval into pulse count, relay duration, or custom start behavior based on the machine wiring.
- Machine interface
- coin pulse input, relay output, dry contact, sensor input
- Trigger source
- QR payment, app approval, operator panel, or server command
- Session data
- accepted, started, duration, completed, fault
- Project mode
- coin-op retrofit, amusement operator rollout, custom control box
Workflow
From machine interface to API-controlled result.
Map payment rule
Define price, ride duration, and whether one payment creates one or multiple pulses.
Trigger ride
QuLink sends pulse or relay output to start the machine.
Report outcome
Your backend receives session result and online status.
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/RIDE-09/commands
{
"command": "pulse_output",
"source": "qr_payment",
"machine_action": {
"pulse_count": 1,
"pulse_width_ms": 120
}
}
Start the project
Send the first machine details before writing a full spec.
Send the ride controller photo, coin acceptor wiring, pulse requirements, target duration, and payment workflow.
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 simulate coin insertion?
Yes, when the machine accepts compatible pulse or relay start signals.
Can the board work offline?
Project behavior can be designed around network availability, but payment and server callbacks normally require connectivity.
Can it support several ride models?
Yes, if the interface profiles are documented and tested per model.
Related use cases