NexusLinkStudio

Nexus A desktop workstation for communication debugging, protocol verification testing, and AI-assisted joint debugging. [ [](https://github.com/RRQM/NexusLinkStudio) [](https://githubRRQM/NexusLinkStudio) [](https://avaloniaui.net/) [](https://touchsocket.net/) [](https://qm.qq.com/q/QYRKIcHqkq) [GitHub](github.com/RRQM/NexusLinkStudio) · [Gitee](https://gitee.com/RRQM_Home/NexusLinkStudio) NexusLinkStudio a traditional debugging assistant that only opens ports, sends and looks at response packets. It's more like a can accompany you for a long time in the development supports common communication scenarios such as TCP, UDP, serial port, named pipe, MQTT, HTTP, Modbus, etc., with built-in message recording, playback, filtering, preset messages, automatic reply, variable management, data adapter, communication flow chart, MCP server, and other capabilities, making protocol debugging a reproducible, sedimentable, automatable, and AI-collaborative workflow. The project is built based on . Avalonia, TouchSocket TouchSocketPro a modular architecture, providing a modern desktop UIable configuration filesible communication components, and MCP interfaces for AI tools. Icons           ## Why Choose Nexus - Multi-pro-stop debugging: TCP TCP Service, UDP Session, Serial Port, Named Pipe Client, Named Pipe Server, MQTT Broker, HTTP Client, Modbus Master, Modbus Slave, and other modules are unified in one workstation. - Not just sending and receiving messages: the communication page has built-in message recording, recording file management, message playback, combined filtering, variable view, preset messages, automatic reply, loop sending, and log export. - For real projects: configuration can be saved independent file, can be recorded processes can be reused, making it suitable-term maintenance of protocols, devices, production linesways, upper computers, and IoT- TouchSocket technology communication capabilities are basedSocket / TouchSocketPro, covering high-performance Socket,, Modbus, MQTT pipe, HTTP MCP. - AI built-in MCP Server can expose the currently components, variables,, automatic reply, real-time reports communication snapshots to external- Extensible global data adapters and adapters, supports plug-in package import, and is suitable for precipitating team internal parsing rules, and## Feature Overview Communication Debugging NexStudio unifies the of different protocols into: configure connection parameters, start connections or services,, observe sending and record the scene, filter and playback verification. communication pages include: | Capability | | --- | --- | | TCP Connect to TCP server/receive messages, support preset messages, automatic reply, recording playback, | | TCP Service TCP server, manage, support broadcasting,, single/batch removal, connection statistics | | UDP Session | Bind local send UDP data to specified target, suitable for connection and device broadcasting scenarios | | Serial Port | Serial and receiving debugging, encoding, variables messages, recording playback, and filtering | | Named | Named pipe client| Named Pipe Server | Named debugging | Client | MQTT connection, publishing, and | | MQTT Broker MQTT broker server debugging HTTP Client | HTTP request debugging and configuration saving | Master | Mod variable reading and writing search, automatic execution tracking | | Modbus Slave | Modbus slave data area, variable grouping, request response debugging | Each communication configuration can be saved as an independent file for easy reuse, sharing, and version management. ### Message Recording and Playbackugging often involves fear of "how did that packet come from". NexusLinkStudio provides message recording and playback capabilities: - Can start/stop message recording on the communication page. - Recording files are saved to the `MessageRecordings` directory under the application directory by default. - Supports exclusive recording extensions for different protocols, such as TCP, UDP, serial port, MQTT, HTTP, Modbus, etc. - Can manage recording files: refresh, rename, export, open location, move to recycle bin. - Supports reading messages from one or more recording sources and sorting them by timeline. - Supports modes such as only viewing, playback sending traffic, playback receiving traffic, etc. - Supports immediate playback, fixed interval to original time interval. - Supports speed pause, resume, stop, clear, and progress statistics. This makes communication debugging change from "look at the scene" to "can review, can demonstrate, verify". ### When communication logs grow, it's essential to quickly find critical messages.Studio provides a unified: - Search. - Search by message tag. - Filter by sending, receiving, system, protocol-specific types. by start date and. - Supports combined filtering. - The filtering status still updates incrementally with new messages. Modbus and provide dedicated message type for easy problem location according to function codes, master business messages. ### Preset Messages Many protocol debugging involves repeatedly sending the same commands. NexusLinkStudio preset message designer to maintain common message templates and directly select and send them on the communication page. Preset messages dynamic templates: -- Time - time - Timestamp - GUID - Line break - Input parameters This allows common messages like "login packet, heartbeat packet, query packet, control command, abnormal command" to be clearly organized, rather than scattered, text files, or temporary notes. Automatic reply is suitable for simulating devices,, constructing protocol responses, or doing simple closed-loop testing. NexusLinkStudio provides an automatic reply designer that supports: - Unified maintenance of automatic reply rules. - Enabling automatic reply for different communication modules. - Matching messages according conditions. - Returning fixed content or generating replies logic. - Reusing automatic response capabilities in debugging processes like TCP, UDP, serial port, named pipe, MQTT, Modbus, etc. When you need to device that hasn't yet, reproduce an or let the client program run through the process, this capability can save a lot of time Variable View Communication only involves "messages" but also often requires observing "status" and "data points" in protocols. NexusLinkStudio adds variable multiple communication pages: - Supports variable grouping. -, editing, and deleting variables. - Supports updates and runtime management. - Supports combining with communication tools, Modbus variable reading and writing. The Modbus module provides a more professional variable experience: - Coil - Discrete input - Holding- Input register - Read and write operations - Data format display - Automatic execution - Address search - Draggable grouping layout ### Data Adapter Real TCP protocols are often not "one line of text per packet" but complex forms like sticky packets, sub-packets, fixed length, delimiters, JSON frames, custom frame headers, etc. NexusLinkStudio provides a global data adapter configuration capability to handle communication data-in adapters `BetweenAnd`:截取数据包according to start and end markers. - `FixedSize`:分包according to fixed length. - `Period`:分包according to terminators or delimiters. - `Json`:识别JSON data packets. - `script`:通过C#脚本动态编译TouchSocket data processing adapters. Script data adapters can write complete C# and dynamically compile it into recoverable assemblies. The system checks for compilation errors, type existence, inheritance of `SingleStreamDataHandlingAdapter`, and instantiability. For custom binary protocols, special frame formats, and vendor-private protocols, this is a strong extension point. ### Communication Flow Diagram The communication flow diagram is used to string multiple communication components into executable processes, suitable for describing and verifying "send -> receive -> judge -> output result" debugging processes. The current flow diagram has built-in nodes including: - Start - Communicator - Send - Receive - Result It is suitable for turning manual joint debugging steps into clearer process expressions and facilitating subsequent regression, demonstration, and AI-assisted analysis. ### Communication Configuration and Real-time Report The project also includes: - Communication configuration: used to build visual/ configuration pages for communication data. - Real-time report: used to organize real, debugging results, and scene status into report views. These capabilities make NexusLinkStudio not only stay at the "debugging tool also gradually have the form of "communication workstation" and "scene observation station". ### Shortcut Tools NexusLinkStudio has multiple small tools in development and debugging: - String- JSON formatting - Base64 encoding and decoding - URL encoding and decoding - GUID generation conversion - Hash calculation - Output window Terminal entrance These tools are placed in the, which can reduce the switching between multiple small web pages, and scripts during debugging. ## AI and MCP Nex has a built-in MCP ServerNexusLinkStudio.Mcp When the MCP service starts, external AI clients the current workstation through MCP. The provided cover: - Communication component list and capability description Current open tab information. - Start, stop, configuration, send messages, and snapshot reading of TCP, UDP port, named pipe, MQTT, Mod other components. - Adding, deleting, and describing communication variables. - Preset message list, template list, creation, update, and deletion. - Automatic reply configuration, matching, and change. - Global data adapter list, definition query, saving, deletion, and verification. - Script data adapter Prompt template acquisition. - Real-time report-related tools. - Communication flow diagram operation and snapshot. This means you can let AI do some things that could only be done manually before, such as: - me create TCP client configuration to 127.0.0.1:778- "Generate a script data adapter according to this protocol description." - "Read the last 50 Mod and help which register- "Organize these common commands into preset messages." - "Create an automatic reply rule to simulate the device handshake process." NexusLinkStudio's not to let AI replace debugging personnel but to truly enter the debugging scene, understand the currently opened variables, messages, and configurations. ## and Extensions LinkStudio's core be saved to Common extensions include: Extension | | --- | | Configuration | `.tcp | | TCP | `.tcpservice` | | UDP Session Configuration | `.udpsession` | | Serial Portserialport` | | Named Pipe Client Configuration | `.namedpipeclient` | | Named Pipe Server `.namedp` | | MQTT Client Configuration | `.mqttclient` | | MQTT Broker Configuration | `.mqttbroker` | | HTTP Client Configuration | `.httpclient` | | Modbus Master Configuration | `.modbusmaster` | | Modbus | `.modbusslave` | Flow Diagram |flowdiagram` | | | `.mi` | | Report | `.port` | Message are saved separately from configuration files. The default recording files is `MessageRecordings`, and are used according types for easy longiving and playback Technology Stack NET 10 - C# preview onia 12 Toolkit.Mvvm TouchSocket - TouchSocketPro - TouchSocket.Mcp - Live- LiveMarkdown.Avalonia -Edit / TextMate - NLog Acquisition and Usage NexusLinkStudio is not an open-source software currently but can be used forYou can obtain release information, usage instructions, and subsequent updates from the project homepage: - GitHub:github.com/RRQM/NexusLinkStudio - Gitee: https://gitee.com/RRQM_Home/NexusLinkStudio If you want to provide feedback, propose suggestions, discuss usage scenarios, or follow new versions, you can use the GitHub / Gitee repository entrance first. ## Suitable Users NexusLinkStudio is particularly suitable for: - IoT, industrial control, device communication, upper computer, gateway, edge computing project developers. who need to debug TCP, UDP, serial port, Modbus, MQTT, HTTP, named pipe. - Test personnel who need to simulate clients, servers, devices, brokers, or slaves. - Teams that need to record communication scenes, review problems, and do regression verification. - Developers who want AI to participate in protocol configuration, message analysis, automatic reply, and adapter generation. - .NET developers who are already using or plan to use the TouchSocket technology stack. ## Project Characteristics ### Unified but Not Coarse Different protocols have different details, but NexusLinkStudio tries to maintain consistent operation modes: connection configuration, message area, sending area, recording playback, filtering, variables, saving configuration. This allows you to switch between TCP, serial port, UDP, MQTT, Modbus without having to relearn an interface. ### Reproducible Configuration files, recording files, preset messages, automatic replies, data adapters can all be saved. Debugging experience will not only exist in a certain session but also not only exist in a person's brain. ### Automatable Communication flow diagrams, automatic replies, loop sending, variable automatic execution, MCP tools gradually abstract manual steps into automatically operable and externally callable capabilities. ### Extensible Built-in adapters solve common unpacking problems, script adapters solve special protocol problems, and plug-in management leaves space for subsequent module extensions. ### AI Native Collaboration Many tools just use AI as a chat window, but NexusLinkStudio goes further: exposing communication components, configurations, messages, variables, and adapters as MCP tools, allowing AI to operate in real context. ## Route Direction The project is still under rapid development, and the current focus includes: - Improving more communication protocols and industrial protocol debugging capabilities. - Enhancing communication flow diagrams and automated testing capabilities. - Continuing to expand MCP tools, allowing AI to participate more deeply in protocol analysis and configuration generation. - Optimizing communication configuration, real-time reports, and variable visualization experience. - Precipitating more data adapters and script adapter templates. - Improving plug-in mechanisms, capabilities to be distributed and reused more easily. ## Authorization Description Nexus is currently free for users but not open-source. Please do not decompile,er, repackage, modify, or redistribute it as part of another product without authorization. If you have enterprise integration, customization development, business cooperation, offline distribution, or special authorization needs, you can contact the author through the project homepage. ## Author and- Author: 若汝棋- QQ: 505554090 QQ Group: [Click to join discussion](https://qm.qq.com/q/QYRKIcHqkq) ## Related Links - GitHub: https://github.com/RRQM/NexusLinkStudio - Gitee: https://gitee.com/RRQM_Home/NexusLinkStudio - TouchSocket: https://touchsocket.net/ If you're doing communication debugging, NexusLinkStudio hopes to become the kind of tool that you can "open and leave it on the side": able to send packages, record scenes; able to look at logs, precipitate processes; able to manually verify, let AI participate in the next step.