The customer configures the register numbers using the satscada gui. Each of the tags can have a register number that the customer chooses from the full range of modbus registers.
The registers are accessed via the SatSCADA Proxy. This can be installed on a customer server or Bentek can host it in the cloud.
The host can communicate to a satscada terminal's internal registers in FlowThru mode using ip ports 1xxxx, 2xxxx, or 3xxxx where x is the terminal number preceded by leading zeros (e.g. 10002). These connect to terminal ports 1, 2, and 3 respectively. For example, 10002 connects to terminal 2 and port 1 on that terminal.
Modbus Registers appear in the flowthru map only if they have been associated with tags in the terminal configuration. The register numbers and register format are set by the customer using the satscada gui.
The host can retrieve call out data by connecting to ip port 5xxx, where x is the terminal number with leading zeros, and the ip address of the computer where the client is installed (usually localhost). For example, ip port 5002 is used to get call out registers from terminal 2.
Registers appear in the callout map only if tags have been associated with tags in the terminal configuration. Digitals are returned as one bit that can be 0 or 1. Analogs are returned as 32 bit IEEE 754 float big endian.
Callout registers are stored in the SatSCADA Server database and are accessed without using air time. Accessing these registers therefore in faster than accessing flowthru registers. A callout transaction takes about 100 msec whereas a flowthru transaction takes about 25 sec by satellite and 5 sec by cell. However callout registers are historical and do not represent the current terminal state as flowthru registers do.