Your telegrams —
Your protocol. Your rules.
Client and server development over RFC 1006 (ISO-on-TCP) for .NET. Exchange raw data and your own telegrams between applications, controllers, and systems — vendor-independent, over an open transport protocol.
Exchange raw data.
Client and server in a few lines.
From server start to the first received telegram — and from client connect to the first transmit. All in C#.
// Start an RFC 1006 server and wait for messages
using (var server = new Rfc1006Server("rTSAP", "lTSAP")) {
server.Start();
server.Connect(); // Wait for a client
var message = server.ReceiveString();
Console.WriteLine($"Received: {message}");
}
Start the server, wait for clients, receive data.
Define TSAPs, start the server, wait for incoming connections. Receive messages as byte arrays or strings — the SDK handles the TPKT/COTP packets behind the scenes.
// RFC 1006 client — send a message
using (var client = new Rfc1006Client(
"192.168.0.80", "rTSAP", "lTSAP")) {
client.Connect();
client.Transmit("Hello World!");
}
Connect and send — in three lines.
Provide an IP address and TSAPs, Connect, Transmit — done. Send byte arrays, strings, or your own binary telegrams. The SDK automatically partitions the data into RFC 1006-compliant DT packets.
// Event-driven communication
var server = new Rfc1006Server("rTSAP", "lTSAP");
server.AutoReceive = true;
server.Received += (s, e) =>
Console.WriteLine(
$"Data: {e.BufferLength} bytes");
server.Connected += (s, e) =>
Console.WriteLine("Client connected");
server.Start();
Event-driven — AutoReceive and events.
With AutoReceive and the built-in events, your server reacts automatically to incoming data and connection changes — no manual polling. Ideal for permanent communication channels.
Six reasons that make the difference
Each of these addresses a real problem that development teams hit when integrating over transport protocols.
Client and server — in one SDK
Both roles in a single package. Start a server that waits for connections, or connect as a client to an existing endpoint — with the same API.
Royalty-free — one license, unlimited applications
Build as many applications as you want. No per-unit licenses, no runtime fees, no hidden per-deployment costs.
Industrial reliability — around the clock
Stable in continuous operation, automatic reconnect on dropped connections, PDU-optimized access for consistent data. In production since 2015.
Vendor-independent — one open protocol
RFC 1006 is an open, vendor-independent transport protocol. Talk to S7 controllers, other PLCs, or your own applications — regardless of manufacturer.
Support straight from the development team
Support requests for the LINK SDK are answered by the team that builds and maintains it — short paths, technically grounded answers, no ticket cascade through external call centers.
Raw data — your format, your structure
Send and receive byte arrays, strings, or your own binary telegrams. The SDK handles the TPKT and COTP packets — you define the payload.
„We've been running the SDK for a few years now. Everything has worked flawlessly so far and left nothing to be desired.
Best value for money!"
One SDK. Client and server.
Free evaluation with a 30-minute trial license per application launch. Royalty-free licensing and developer support included.
TR1K6 LINK .NET SDK
RFC 1006 client and server development for .NET. Exchange raw data and your own telegrams between any participants — over the open ISO-on-TCP transport protocol.
RFC 1006 defines an ISO transport service (TP0, ISO 8073 Class 0) over TCP/IP. Standard port 102. Usable regardless of vendor — from controllers to gateways to your own applications.
What's inside the SDK
One open transport protocol, a symmetric API for client and server, robust connection mechanics. The key facts at a glance. Behind the name: TR1K6 — Traeger RFC 1006, in engineering notation: 1K6 = 1006.
Rfc1006LibNet.AdvancedRfc1006Client, Rfc1006Server, Rfc1006Base, Rfc1006IPEndPointTransmit(byte[]) · Transmit(string)Receive, ReceiveString · AutoReceive mode with Received eventLicense once. Deploy without limits.
License model
License type
All licenses are royalty-free — unlimited applications, no per-deployment unit costs.
License models in detailGet started in minutes
SDK download
Download Rfc1006LibNet.Advanced — with a 30-minute trial license per launch.
DownloadDocumentation
Features, API reference, and requirements — all in one place.
Open docsAPI reference
Rfc1006Client, Rfc1006Server, events — the complete class library.
Open docsQuestions?
Our development team advises you on architecture and deployment scenarios.
Get in touch
„RFC 1006 is the Swiss Army knife of industrial communication — open, proven, and vendor-independent. Our SDK makes it accessible to .NET developers."
Dominik Scharnagl Managing Director & CTO, Traeger GmbH
TLX-S LINK SDKs
When you want direct access to data blocks, flags, and inputs/outputs of S7 controllers — for .NET, COM/VBA, and MATLAB.
Explore LINK PLC
Codabix Middleware
When you want to use RFC 1006 as a gateway — Codabix connects controllers via OPC UA and REST API, with no custom development.
Explore CodabixReady for open communication
over ISO-on-TCP?
Download the SDK, send your first telegram — or talk directly to our team.
