Applies To:
  • CitectSCADA 5.41, 5.41 Service Pack A
  • CitectHMI 5.41, 5.41 Service Pack A

We have upgraded from an earlier version of Citect (5.21 Service Pack F) to Citect 5.41 Service Pack B, and have decided to use the new ABLOGIX Driver.

After installing this driver and compiling, we receive "Driver Error 259 (0x103) and Generic Error 25. In the Documentation of ABLOGIX the meaning of the error code 0x103 is:

" Bad parameter, size > 12 or size greater than size of element (RMW) "

We are having difficulty in understanding what this means, and it is not helping us in finding a solution to the problem at hand.


In this instance, the problem lies within the tag names. Some tags on the clients machine were missing a square bracket [ ] making it difficult for the driver to comprehend and compile thus giving an error 0x103. The error in this instance could not be improved to state that there is missing square brackets [ ], as the driver is reading in string values from the Tag and cannot make assumptions on what the values are in there.

Checking your tags in this case would be a way to find a solution to the problem.

If this does not solve your problem, then your next best option is to debug the driver and find where the fault lies.

Leave Citect off and make the following changes.

** Clear your SYSLOG.DAT file (simply delete it) which can be found in your WINDOWS directory (eg., C:\Windows)

** Modify your citect.ini file to have the following parameters in the [DEBUG] and [ABLOGIX] section;


***********CITECT.INI FILE SETTINGS*********
debugstr=port_name all


** For port_name, replace it with the name that you have given to your port in Citect referencing the ABLOGIX driver. Under Citect Project Editor.

Once the error is reproduced the information will be written into the SYSLOG.DAT file, from there the syslog.dat file can be analysed to understand what is causing this problem. This can be opened up using a text editor such as Notepad.

Once this is done, you can simply disable debugging options by removing the above parameters from your citect.ini file.

This file can also be diagnosed by Citect Support Engineers to evaluate the problem if it is not related to the way the tags are written.