Confirm the machine interface
Send the controller label, wiring photos, and the action the machine must perform.
Placa de control industrial
QL-4G-300 Controlador IoT 4G
Placa de control del lado de la máquina para vending, café, lavandería y equipos self-service. Conecta API, 4G o serie con tu pago y backend.
4G uplinkRS485 / pulseOffline bufferOwn backend
Ajuste del proyecto
Para máquinas y proyectos compatibles
Señales de necesidad
- Sites without reliable local network or a local PC.
- Machines that expose serial, RS485, pulse, or relay signals.
- Projects that need heartbeat, session, fault, or meter data.
- Teams that want data in their own backend, not a closed portal.
Qué enviar
- Fotos de la máquina o placa actual
- Notas de interfaz o cableado
- Acción objetivo después de API o pago
- Si necesita carga de datos
No es adecuado si
- The machine has no usable data or control interface.
- You need guaranteed cellular coverage before a site survey.
- You only need a local dashboard with no backend integration.
Modelo de integración
De comando API a acción de la máquina
Tu sistema de pago o backend envía un comando, QuLink ejecuta la acción de la máquina y devuelve el resultado. La interfaz se confirma en una muestra.
- Product model
- QL-4G-300
- Connectivity
- 4G LTE Cat.1; Wi-Fi and Ethernet optional
- Communication
- RS485 / RS232 / UART
- Relay
- 2 channels; NO / NC / COM
- Relay rating
- 10A 250VAC / 10A 30VDC
- Pulse input
- 2 channels; 5–24V opto-isolated
- Power input
- 12–24V DC; 2A
- Offline storage
- 8 GB; up to 30 days
- Data output
- HTTP API / webhook; MQTT optional
- Firmware
- Standard firmware; OTA update support
- Indicative sample price
- USD 149–229 for one sample; final quote after interface review
- Applications
- Remote monitoring, vending, laundry, lockers, utility equipment
Flujo de trabajo
De las fotos de la máquina al flujo probado.
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.
Ejemplo de API
Ejemplo de comando de servidor o webhook para una acción del lado de la máquina.
Los campos del comando dependen de la interfaz de la máquina, el perfil de firmware y si el pago o la aplicación activa la acción.
POST /v1/devices/SITE-12/events
{
"event": "telemetry",
"device_id": "SITE-12",
"fields": ["heartbeat", "session_state", "fault"]
}
Proyecto RFQ
Cuéntanos qué debe hacer, enviar o reportar la máquina.
Envía el modelo de máquina, fotos del controlador y la acción necesaria. Confirmamos la interfaz de Controlador IoT 4G y el siguiente paso de prueba.
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
Preguntas habituales antes de un test de muestra.
Does it work with our own backend?
Yes. Event delivery can be configured for your HTTP API, webhook, or MQTT broker, depending on the project.
What data can it report?
It depends on the machine interface. Heartbeat, session state, relay or pulse events, and fault signals are common starting points.
Does it need a SIM card?
Yes for cellular operation. SIM, antenna, and site coverage are confirmed during the sample test.
What should I send first?
Controller model, serial or pulse interface, data fields needed, and where the data should go.
Casos relacionados