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

When creating a second driver instance for the Modnet Driver (called ModnetX for testing purposes) outlined in KB Q4104. The MODNETX driver ignores the Maxbits protocol parameters section under [MODNETX] as well as ignoring the entries made to the Maxbits section of the Protdir.DBF. However, if the [MODNET] section with Maxbits is then modified, the MODNETX driver then reads these values and interprets them according to the MODNET settings. 

This is currently not supported by the Modnet driver when a second driver instance is created. Some parameters explained in KB Q4104 are parameters which have been hard coded into CitectSCADA. This is by design.

Currently an enhancement request has been requested that the driver support this functionality.
Citect has confirmed this to be a problem in all Modnet versions. We are researching this problem and will post new information here as it becomes available. 

Modnet Modnetx Maxbits driver ignores section protdir.dbf citect.ini second instance