I am working with Shtrix-M (ШТРИХ-М) scales, which are very popular in CIS countries. These devices primarily communicate over the UDP protocol (default ports: 1111 for receiving and 2000 for sending) using binary/hex payloads.
Currently, QZ Tray provides excellent support for TCP and Serial (COM) ports, but it lacks a direct way to send and receive raw UDP datagrams.
Proposed Solution
It would be highly beneficial if the qz.serial or a new qz.networking module could support UDP communication. Specifically:
- Ability to open a UDP socket to a specific IP and Port.
- Ability to send Hex/Base64 encoded binary data via UDP.
- A callback mechanism to listen for incoming UDP responses (since many scales send a status response immediately after a command).
Example Use Case
- Device: Shtrix-Print Scale
- Protocol: UDP
- Target IP: 192.168.85.208
- Port: 1213
- Payload (Hex):
02 01 13 (Get Status)
- Expected Response (Hex):
02 02 13 00
Additional Context
Adding UDP support would expand QZ Tray's compatibility with a wide range of industrial hardware (scales, sensors, and IoT controllers) that rely on connectionless transport for speed and simplicity.
Thank you for the great tool and constant improvements!
I am working with Shtrix-M (ШТРИХ-М) scales, which are very popular in CIS countries. These devices primarily communicate over the UDP protocol (default ports: 1111 for receiving and 2000 for sending) using binary/hex payloads.
Currently, QZ Tray provides excellent support for TCP and Serial (COM) ports, but it lacks a direct way to send and receive raw UDP datagrams.
Proposed Solution
It would be highly beneficial if the
qz.serialor a newqz.networkingmodule could support UDP communication. Specifically:Example Use Case
02 01 13(Get Status)02 02 13 00Additional Context
Adding UDP support would expand QZ Tray's compatibility with a wide range of industrial hardware (scales, sensors, and IoT controllers) that rely on connectionless transport for speed and simplicity.
Thank you for the great tool and constant improvements!