1. Socket client. Scoreboard OCR acts as a client and connects to a 3rd party application
2. Socket server. Scoreboard OCR acts as a server and waits for connections from a 3rd party applications. Only TCP server (not UDP) is currently supported

Socket TCP/UDP output option sends data as JSON lines to socket server.

Syntax to be used in Scoreboard OCR:

tcp://host:port/[stream_id]

udp://host:port/[stream_id]

udp://localhost:3322/stream1

The following command is sent when creating new connection, but ONLY if the stream_id has been specified (this is useful if your graphics service is serving multiple broadcasts at the same time):

{"type":"register", "stream":"stream1", "role":"ocr"}\LF

Command sent when updating data:

{“type”:”ocr”, “values”:{"field_name1": “value1”, "field_name2": “value2”}}\LF

{“type”:”ocr”, “values”:{"time": “3:12”, "score_a": “56”}}\LF

Socket TCP/UDP output option sends data as field=value lines to the server

Syntax to be used in Scoreboard OCR:

tcp://host:port

udp://localhost:3322

Command sent when updating data:

Clock=2:45\CR\LF
ShotClock=12\CR\LF