This procedure prepares a 32-bit KingSCADA 3.8 installation to connect to MySQL through an ODBC System DSN. The documented setup uses the MySQL ODBC 8.0 ANSI Driver and creates a data source named KSMySQL.
Confirm the Connection Architecture
In the documented application, MES task data reaches KingSCADA through an API and is stored in MySQL. KingSCADA then decomposes the tasks and sends them to an Inovance AC810 control PLC. Navicat provides a visual interface for database administration, while the ODBC driver provides the database connection required by KingSCADA.
| Component | Confirmed requirement or role |
|---|---|
| KingSCADA 3.8 | 32-bit application; configure a matching 32-bit ODBC data source |
| MySQL ODBC driver | Install the 32-bit driver |
| ODBC data source | Create it under System DSN |
| Selected driver | MySQL ODBC 8.0 ANSI Driver |
| DSN name | KSMySQL |
| Navicat | Optional visual tool for operating the MySQL database |
Install Navicat and the 32-Bit ODBC Driver
The exact Navicat release and the MySQL ODBC installer version are not identified. Use licensed installation media and confirm that the ODBC package is 32-bit before installation. Creating a Windows restore point before installing new software provides a recovery path if the installation destabilizes the workstation.
- Create a Windows system restore point.
- Run the Navicat installer as an administrator, accept the license terms, select the installation location, start the installation, and finish the wizard.
- Run the 32-bit MySQL ODBC driver installer.
- Accept its license terms, select Complete, click Install, and then click Finish.
Create the 32-Bit System DSN
Open Windows Tools from Control Panel and launch the 32-bit ODBC Data Source Administrator. Do not configure the 64-bit administrator for this KingSCADA 3.8 setup; the ODBC administrator and driver must match the application's 32-bit architecture.
- Select the System DSN tab and click Add.
- Select MySQL ODBC 8.0 ANSI Driver and click Finish.
- Enter the required connection information shown by the driver dialog, including the password.
- Name the data source
KSMySQL. - Click Test. Accept the configuration only after the dialog reports
Connection successful. - Confirm that
KSMySQLappears in the System DSN list, then close the administrator.
Resolve Driver Selection and Verify the Result
The available driver list contained both ANSI and Unicode variants, but the evidence does not define their character-handling differences or establish a general selection rule. The tested configuration selected the ANSI driver and returned Connection successful; treat that result as validation of this specific setup, not proof that ANSI is correct for every database schema or character set.
Before configuring KingSCADA, verify three items: the DSN appears in the 32-bit System DSN list, its name is exactly KSMySQL, and its built-in connection test succeeds. This completes the documented workstation preparation; application-level connection configuration inside KingSCADA is a separate step.
FAQ
Which ODBC driver bitness does KingSCADA 3.8 require?
The documented KingSCADA 3.8 installation is 32-bit, so install the 32-bit MySQL ODBC driver and create the DSN with the 32-bit ODBC Data Source Administrator.
Should the KingSCADA MySQL connection use a User DSN or System DSN?
Create a System DSN. In this configuration, select the MySQL ODBC 8.0 ANSI Driver and name the data source KSMySQL.
How do I verify the KingSCADA MySQL ODBC data source?
Enter the required connection information and password, then click Test. Continue only when the driver reports Connection successful and KSMySQL appears in the 32-bit System DSN list.