Confirm pulse behavior
Measure pulse width, count, voltage, and the machine start behavior.
Guides
Pulse to cloud
Pulse to cloud gateway for coin-op and timed machines.
Use QuLink when a coin, token, or pulse machine needs cloud commands, pulse simulation, relay output, and session or usage events in your own backend.
Pulse outputRelay controlCloud commandUsage events
Part of Machine Data Upload IoT Board for Self-Service Equipment
Project fit
For coin-op, arcade, laundry, and timed equipment
Buyer signals
- Kiddie rides, arcade machines, laundry, car wash, or massage chairs with pulse or relay input.
- Operators replacing coin or token modules with app or QR control.
- Projects that need pulse counting, session timing, or usage events.
- Fleets that need online status and fault visibility.
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
Not the right fit if
- You only need a pure payment acquiring account and no machine-side control.
- There is no physical machine action after payment, booking, or API approval.
- The project has no machine photo, board photo, wiring note, or interface clue yet.
Integration model
Cloud command becomes a pulse or relay action
QuLink translates a server command into a pulse count, relay duration, or dry-contact start, then reports the session and device status.
- Machine interface
- pulse input/output, relay, dry contact, sensor input, serial option
- Trigger source
- app approval, QR payment, operator panel, or server command
- Session control
- pulse count, relay duration, timed session, stop, status
- Data returned
- session start/end, pulse count, fault, online/offline, usage log
- Project mode
- coin-op retrofit, arcade rollout, OEM control box
Workflow
From machine interface to API-controlled result.
Map the session
Define price, pulse count or duration, stop behavior, and retry rules.
Connect the cloud
Choose HTTP, webhook, or MQTT transport and define the event schema.
Test one machine
Verify pulse output, session completion, duplicate commands, and offline behavior.
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/PULSE-18/commands
{
"command": "pulse_output",
"source": "app_command",
"reference_id": "PULSE-ORDER-018",
"machine_action": {
"pulses": 3,
"pulse_ms": 120
}
}
Project RFQ
Send a machine photo. We help identify the board, interface, and next test step.
Send the machine photos, coin or pulse wiring, target pulse count, payment or app flow, and rollout quantity.
A good first message
If you are unsure about the exact interface, send what you have. Photos often answer more than a long spec.
- Machine type and target country
- Machine photo, board photo, or wiring photo
- Action after payment or API command
- Need data upload? expected quantity?
Fastest first step
- Send a machine photo
- Describe the action after API or payment
- Tell us if data upload is needed
FAQ
Questions buyers usually ask before a sample test.
Can QuLink replace a coin acceptor?
In many retrofit projects, yes. The board can simulate pulse or relay behavior after app or payment approval, depending on the machine wiring.
Can it count pulses from the machine?
Yes when the pulse signal is compatible. The project can count credits, sessions, or usage events.
Can it control a timed session?
Yes. Relay duration and timed sessions can be defined per machine and price rule.
Can it report usage to our cloud?
Yes. Session start, end, pulse count, fault, and online status can be uploaded.
Related use cases