The ODBC server support allows Citect SCADA to function as an SQL database server. This will allow third-party applications that support ODBC to access data directly from Citect SCADA. This means that users can have direct access to data in Citect SCADA without having to develop Cicode or reports to export the data.
Currently, the Citect SCADA ODBC server allows variable tags to be accessed. The table for the variable tags is named 'TAGS' and the format is as follows.
NAME |
Variable tag name |
read only |
VALUE |
The current runtime value |
read/write |
Citect SCADA can only function as a database server at runtime. Using tags through ODBC at runtime can still add to your Citect SCADA License point count. Once the dynamic point count is greater than the license point count, the software protection mechanism will shutdown Citect SCADA runtime. Therefore, when accessing tags via the ODBC server, it's important to keep aware of how many points you have used. For details see License point count in the Installation and Configuration Guide.
Setting up the Citect SCADA ODBC server:
You need to have TCP/IP installed on your computer first.
Note: If you select other tabs you will see that the Citect SCADA ODBC driver has been automatically installed.
Accessing the Citect SCADA ODBC server using MS Query (V2.00):
All ODBC capable applications use different ways to construct queries for accessing Citect SCADA tags. The example instructions for using MS Query, given here, show a simple implementation. MS Excel and MS Access use the same method.
Accessing the Citect SCADA ODBC server using MS Query (V8.00):
Unlike Version 2.00, User DSNs are not used by Version 8.00. Instead it uses File DSNs which by default are stored in Program Files\Common Files\ODBC\Data Source
folder. File DSNs are not stored in the Windows registry, they are text files given the .DSN extension. When you connect to an existing data source, only the available File DSNs that are stored on that PC are displayed. MS Query V8.00 does not display User or System DSNs. The simplest solution is to create a File DSN that points to a User DSN.
To create a file DSN that points to a user DSN:
[ODBC]
MyUsrDSN
DSN=<>
where <MyUserDSN> is the name of an existing user DSN that you have created via the ODBC icon in the Control Panel.
MyUsrDSN
>. For example:MyUsrDSN
>).When you run MS Query, you can now select your File DSN from the list.
See Also
Published June 2018