The TCP Connector accepts long-lived device connections, frames incoming streams, and associates traffic with endpoints when an extractor is configured.
Set an endpoint's Blocked field to Yes to close its connection when the connector identifies the blocked endpoint. The rejected message and remaining buffered messages are not published as receive events, and status becomes blocked. Changing the field alone does not change status or disconnect an existing connection. A connection configured to identify its endpoint only on the first message may continue until it reconnects. See Endpoint blocking for editing, bulk updates, and unblocking.
none, fixed_length, ascii_delimiter, or binary_delimiter.length, delim, and delimKeep.none, ascii_delimited, ascii_fixed, binary_fixed, json, or custom.tcp-sent after successful sends. Defaults to false.Generated when a connection is accepted. Contains required remoteAddr and optional reason.
Generated when a connection closes. Contains required remoteAddr and optional reason.
Generated for each detected frame. Contains remoteAddr, decoded payload, and the connection sequence.
Generated after a successful send when Send Events is enabled. Contains remoteAddr and decoded payload.
Send a string, byte array, or JSON-encoded object to an active connection. remoteAddr may instead be an endpoint key; the connector uses the endpoint's last active remote address. When an endpoint key is supplied, an empty serviceKey uses that endpoint's service.
Sending or receiving a TCP frame is billable.
Contact us about your device protocol and framing requirements or Sign up to evaluate.