Applies To:
  • CitectSCADA 5.xx, 6.XX
  • CitectHMI 5.xx, 6.XX

What are some of the common issues which may be encountered when upgrading to the new ABMLX driver?

1. What does driver error 0x1000 mean?

This error can be caused by a number of reasons. Here is a list of possible known causes for this error:
- Data File requested does not exist in the PLC.
- Data File size on PLC is smaller than data requested by driver (address out of range).
- Data Request size is larger than the maximum supported by the PLC.

The maximum data request size for SLC 500, SLC 5/01, SLC 5/02 processors is 95 bytes. While for the SLC 5/03 and SLC 5/04 processors, the maximum is 236 bytes. The Micrologix series support a request size of 248 bytes. To resolve this issue, you may need to edit the Protdir.dbf file in the Citect\Bin and Citect\User\Include directory. Set the BIT_BLOCK and MAX_LENGTH setting for the ABDF1FD to the maximum number of bits supported by the specific PLC you are communicating with. For instance, the SLC 5/01 values would be 760, while the SLC 5/04 would be 1888. You must also set the block setting in the driver to this new request size. I.e. for the SLC 5/04 set:

2. What can cause the error "Response bad or garbled", Generic error 6 Driver error 6?

- This can be caused by incorrect parity settings.
- This can also occur when enabling the CH0 communication setting Embedded Response: Enabled.

The ABMLX driver (ABDF1FD or ABMLXEIP) does not currently support Embedded Responses. Please set Embedded Response to "Auto". This will resolve the Response bad or garbled problem.

3. Using the parameter [KE500]Delay=300 used to work in the KE500 driver, but now in the ABDF1FD, it causes intermittent #COM and unit offline errors.

The Delay parameter is not supported by the ABDF1FD driver, and hence should not be used. Please remove this parameter from your Citect.ini file.

4. After upgrading a KE500 project which uses bit access from a word (N7:5/1), a compile error is returned. Does the ABDF1FD driver support this address?

Yes, the ABDF1FD does support bit access from a word. The original release had an omission in the ABDF1FD.DBF file, which the compiler uses to check variable tag addresses. This has been resolved in ABDF1FD version This can be downloaded from the Citect DriverWeb.