Program epcot provides clients with an EPOCH Version 3 device handler interface to the telemetry channel(s) of a CORTEX unit. As such, epcot links the CORTEX telemetry channel to a virtual device handler that serves telemetry data to any connected clients:
CORTEX <-----> EPCOT <-----> Reader(s)
epcot creates a Link object for each link to a CORTEX telemetry channel. Associated with each Link object is:
A Channel object contains the network connection to the CORTEX telemetry port. The VME-based CORTEX has separate ports for the different channels; the NT-based CORTEX has a single telemetry port to which the Channel object sends a request for the desired channel. If the CORTEX connection is broken for any reason, the Channel object periodically attempts to re-establish the connection.
Reader objects accept, acknowledge, and ignore most device commands from their clients; a read request must be received from a client before telemetry frames are sent to it.
When a telemetry frame is received from the CORTEX by a Channel object, the channel packages the frame in an EPOCH named variable set and passes it to its parent Link object. The link then broadcasts the frame to each of its connected readers.
% epcot [-aperror] [-daemon] [-debug] [-help] [-nt] [-vme] channel[@host] readerPort
aperror()message output on.
aperror()messages are low-level error messages generated by a href="../index.html#libgpl">libgpl functions; normally, they are disabled. If enabled, the messages are output to stderr.
- causes epcot to become a daemon process.
- enables debug output (written to stdout).
- displays information about running epcot.
- specifies the type of CORTEX unit, NT-based (the default) or VME-based.
- specifies the link between a CORTEX telemetry channel and an EPOCH device interface. The CORTEX telemetry channel is specified by its name and the host name or IP address of the CORTEX unit itself. The channel name must be specified as "TMX-Y", where X is "R" (real-time) or "H" (history) and Y is the desired telemetry channel ("A" through "F" inclusive). The EPOCH device interface is specified as a network server port (i.e., service name or port number) to which readers connect.