Build your workspace from the first frame.
These docs describe the current Uartix+ release and follow the actual order of work: connect, define, visualize, and control.
Quick start
Choose an interface, configure it, and connect. Without hardware, launch the demo source to explore a mixed protocol stream.
Import an Anonymous V7, WIT, Modbus, NMEA, or CSV preset from Protocol Templates, or start from a blank template.
- Inspect the real bytes in the frame canvas
- Enable a 2D curve from its legend
- Filter frames in the table and export CSV / Excel
Data interfaces
Serial, TCP client, TCP server, and UDP share the same parsing, plotting, and control pipeline. Switching interfaces does not require rebuilding a protocol definition.
- Serial: hot-plug, reconnection, and up to 3M baud
- TCP client: remote IP and port with reconnect
- TCP server: listen locally and replace the prior connection
- UDP: receive from any source and send to a default peer
Protocol templates and frame canvas
The frame canvas renders real bytes. Drag across continuous cells, then use the context menu to define a field. The skeleton grid remains editable before data arrives.
- Edit headers, tails, length, and identity fields
- Insert or delete byte cells with automatic field-offset adjustment
- Set field names, types, scale, offset, and units
- Group, copy, paste, import, and export templates
Fields and checksums
Fields support U8, U16, S32, Float, text, and more numeric types. Field length follows the selected type. Invalid frames are counted and marked.
- Endian, scale, offset, and units
- Identity fields for multiple frame types under one header
- Sum8, Sum16, XOR8, CRC16-Modbus, CRC16-CCITT, and more
Visualization
One parsed variable can serve multiple engineering views at the same time, without copying or converting data between tools.
- Hex stream: raw bytes, field selection, Ctrl+F search, and an independent pause
- 2D curves: line types, zoom, dual-cursor measurement, pointer coordinates, and relative seconds
- 3D attitude: map Euler angles or quaternions to a model across protocol bindings
- Data table: frame list, sort, filter, visible columns, CSV / Excel
- Video panel: TCP / UDP source, mirror, flip, pause, save, and clear
Command factory and console
The console supports ASCII / Hex modes, colored timestamps, separated TX/RX, history, recording, and chunked file sends. The command factory assembles readable downlink frames.
- WIT register writes can unlock, write, and save automatically
- Anonymous V7 trigger and parameter commands fill parameters and checksums
- Modbus RTU supports function codes 01 through 06 with CRC16
- Custom frames combine fixed bytes, variables, length, and checksum segments
Control canvas
Drag sliders, buttons, switches, LEDs, buzzers, monitors, and joysticks from the library, then bind a variable, template, or script.
- Ghost placement drops only into free grid cells
- Quick commands and the command tree share one source
- Scripts support send, beep, delay_ms, get, variables, and printf-style formatting
- Multiple control pages import and export as JSON
Data and settings
Templates, control canvases, and command libraries are saved locally as JSON. Settings include theme, zoom, language, legend decimals, and control-grid size.
- Automatic updates: Settings → About → Check for updates
- Diagnostic HUD: FPS, long tasks, and render counts
- Product data stays local and never uploads device protocols
FAQ
If a serial device is missing, install the CH340, CP210x, or vendor driver. Linux users may need to join the dialout group.
A TCP send can be unavailable while the client reconnects or before a TCP server has a peer. Sending UDP to 127.0.0.1 produces local TX and RX, which is expected during testing.
If the video panel is empty, check the TCP / UDP source, address, port, and video parameters against the device stream.
An unplugged device is detected and disconnected in about two seconds. Reconnect it to continue. The Windows installer is currently unsigned, so choose “More info → Run anyway” in SmartScreen.