Configuring tables
- Last UpdatedMar 24, 2026
- 2 minute read
There are several RealTime tables that contain records associated with Omnicomm. There are certain considerations that should be taken into account when working in these tables to ensure the connections are configured properly.
The following must be observed when configuring records in tables associated with Omnicomm:
-
All connections for a remote must use the same Omnicomm process.
-
Connections usually have datasets owned by one system. If the network routing allows, connections may also be switched from one system to another.
-
A remote’s dataset can usually be switched from one system to another.
-
Remotes may have distinct datasets from the connections.
Example
-
Dataset DS1 for connections C1 and C2; always owned by system A.
-
Dataset DS2 for connections C3 and C4; always owned by system B.
-
Dataset DS3 for remote R1; control of this remote may be switched between system A and system B.
-
On System A, R1 uses connections C1 and C2. On System B, R1 uses connections C3 and C4.
The following table lists the different tables involved in configuring Omnicomm.
|
Table |
Function |
|---|---|
|
Omnicomm |
This table lists all Omnicomm process on the system. |
|
Mbank |
This table is used to group modems into virtual banks. It also posts reservations for modems when no modems are currently available. |
|
Modem |
This table provides dynamic allocation of physical modems for connection use. |
|
Connection |
This table contains all unique paths of communication to the remotes. |
|
RemconnJoin |
This table contains all remote-connection assignments. |
|
Remote |
This table contains one row for each defined remote. |
|
Circuit |
This table is a placeholder that indicates the existence of a circuit within a connection. |
|
Sigconfig |
The signal configuration (sigconfig) table contains port configuration information (for example, baud rate, parity). |