Integration
TCP and UDP relay control with raw strings
Switch RELO IO8 relays with a TCP or UDP string from any control system, script or touch panel, and bridge TCP to UDP between devices that speak only one.
Any device that sends a string
Most control systems, touch panels and show controllers can send a raw TCP or UDP string. Set the RELO IO8 to listen for "lift-up", and the moment that string arrives a relay pulses, for anything from 250 milliseconds to 15 minutes. The same flow can answer with a string of its own.
Bridging TCP and UDP
Receive nodes and send nodes are independent, so a message can come in on TCP and go out on UDP, or the other way around. That makes the RELO IO8 a protocol bridge between gear that was built for different network stacks.
- TCP for commands where delivery matters
- UDP for fast, fire-and-forget triggers
- Match exact strings, then branch on conditions
Questions
Common questions.
TCP when you need to know the command arrived, UDP when speed matters more than confirmation. Our TCP vs UDP article goes through the trade in detail.
TCP Message Receive listens on port 8081 and UDP Message Receive on port 8888, both fixed. A TCP Persistent node can listen on a port of its own if a system needs one. Each receive node then matches its own string, case-sensitive, so watch for trailing newlines your sender adds.
Start with one. Scale when you need to.
Order the RELO IO8 from our store, or talk to us about your project.