Applies To:
  • CitectSCADA 1.00 1.01 1.10 1.11 1.20 2.00 2.01

Our driver source file ??_init.c has a structure of drv_info_buf called constants, which appears to be interrogated by Citect at startup. The first two number of this structure should contain the major and minor driver version numbers. Currently they identify version 2.0

If then the version fields in constants are changed to, say 2.1 and the driver re-compiled, then when startup up Citect again, the driver will not come online and the error message 'wrong driver version' is displayed in the Citect kernel.

How do we change the version number that Citect expects the driver to be?


The driver version number is used by Citect to verify that the driver is compatible with the current Citect version. This version number is only changed when the interface between the driver and Citect is changed to make them incompatible. For example in the future some enhancements may be included and the driver version changed to 3.0. On startup Citect would check the version number and if it was an older version it may either not allow the driver to run or use the driver in the version 2.0 mode (eg don't use any of the version 3.0 enhancements). If Citect finds a version 3.0 driver this it knows it may use all the new features of the version 3.0 driver.

As the driver version number is used for the driver interface between Citect and the Driver this version number can only be changed by the Citect Research and Development Team.