Confirm the machine interface
Send the controller label, wiring photos, and the action the machine must perform.
Guides
Multifunction controller
QL-MF-400 multifunction controller
One board for projects that need MDB, pulse, relay, serial, and cellular connectivity across mixed machine fleets.
MDB + pulseRelay outputs4G / RS485OEM options
Project fit
For mixed fleets and OEM projects
Buyer signals
- Projects that need more than one interface path on one board.
- Fleets that mix MDB, pulse, relay, and serial equipment.
- OEM builds that need connector or firmware customization.
- Retrofit projects that also need data in their own backend.
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 need a replacement for the machine's safety controller or PLC.
- The machine has no controllable interface or usable feedback signal.
- You need a guaranteed multi-interface result before a sample.
Integration model
One control layer for mixed interfaces
QuLink maps your API command to the interface available on each machine, then reports the result and status from one device profile.
- Product model
- QL-MF-400
- MDB
- MDB master / slave; MDB 4.2 / 4.3 profile
- Pulse input
- 4 channels; 5–24V opto-isolated
- Pulse output
- 4 channels; 20–1000 ms configurable
- Relay
- 6 channels; NO / NC / COM
- Relay rating
- 10A 250VAC / 10A 30VDC
- Power input
- 12–24V DC; 4A
- Communication
- UART / RS232 / RS485
- Connectivity
- 4G LTE Cat.1; Wi-Fi and Ethernet optional
- Offline storage
- 16 GB; up to 60 days
- Firmware
- Standard or custom; OTA update support
- Indicative sample price
- USD 299–449 for one sample; final quote after interface review
- Applications
- Mixed vending, coffee, laundry, lockers, OEM equipment
Workflow
From machine interface to API-controlled result.
Map the command
Define the API command, machine action, result fields, timeout, and fault behavior.
Test one machine
Validate the command, machine action, result, and reconnect behavior on a sample.
Configure the rollout
Confirm connector, firmware, quantity, and support before production.
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/MF-400-01/commands
{
"command": "start_session",
"interface": "mdb_or_relay",
"duration_ms": 600000,
"reference_id": "ORDER-3001"
}
Project RFQ
Send a machine photo. We help identify the board, interface, and next test step.
Send the machine model, controller photos, and the interfaces you need to use.
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 MDB, pulse, and relay work on the same board?
The board supports these interface blocks. Concurrent operation is confirmed against the target machine and firmware profile.
Can it replace a PLC or existing controller?
No. It is a machine-side control and data board. The existing controller and safety design remain part of the machine.
Can you customize connectors or firmware?
Yes, OEM customization is available after the machine interface and volume are defined.
What should I send first?
Machine model, controller photos, target action, data fields, and estimated quantity.
Related use cases