Applies To:
  • CitectSCADA 1.00, 1.01, 1.10, 1.11, 1.20, 2.00, 2.01
Summary:
The Citect for DOS support allows a Citect for Windows computer to act as an DOS Scanner. Citect for DOS machines may access the PLCs that are connected to a Citect for Windows computers. The support also allows a Citect for DOS or DOS Scanner to act as an I/O Server for a Citect for Windows computer. This allows you to mix Citect for DOS, and Citect for Windows computers on the same network. Note that this feature only allows the sharing of PLC data - you cannot share the Alarm, Trend or Reports between the two systems.

Citect for Windows only uses the NetBIOS protocol, so if you are using Citect for DOS on a Netware Network, you must load the Novel NetBIOS emulator. (Add the NetBIOS switch to the GRAPHIC.EXE line of the CITECT.BAT file, this tells GRAPHIC to use the NetBIOS protocol even when it finds Netware. You must get the latest version of GRAPHIC.EXE which has support for the NetBIOS switch.) If using a DOS Scanner then load the NetBIOS client driver on the DOS Scanner.

To allow a Citect for DOS computer to talk to PLCs on the Citect for Windows computer add the following parameters to the CITECT.INI file:

[LAN]
Disable=0
[CitectForDOS]
Server=1

This enables the Citect for Windows computer as a server for Citect for DOS clients. Configure the I/O Devices on the Citect for DOS computer as REMOTE and I/O Devices on the Citect for Windows as per the documentation. The link will occur by matching the Unit numbers - so they must be the same.

To allow a Citect for Windows computer to talk to PLCs on a Citect for DOS or DOS Scanner add the following parameters to the CITECT.INI file

[LAN]
Disable=0
[CitectForDOS]
Client=1
Name=CitectForDOS

You must also configure a dummy I/O Server in the Citect for Windows computer using the above name (eg CitectForDOS). This I/O Server must contain all the PLC units with the correct protocols and unit numbers that you want to talk to. (Note that these units may exist anywhere on the Citect for DOS network, so you only have to configure one IO Server.)

Note: the default name for the CitectForDOS I/O server is DOSServer so add the I/O server called DOSServer to the Citect for Windows I/O server database. In the past some users have added the I/O server called CitectForDOS without setting the name=CitectForDOS. This will cause you to get hardware errors and the server will not communicate correctly.

When you define the units in the Citect for Windows project, ensure the Port field is left blank for IO devices which are derived from the Scanner. If the ports field is not blank then Citect will assume that the I/O Server is a Windows I/O Server. Citect will try to find this Windows I/O Server and when it cannot be found you will get the hardware error '<name> NetBIOS server name not found'.

You may enable the Citect for Windows machine to be a DOS Server and a DOS Client at the same time as well as using other Citect for Windows IO Servers. 

Solution:
 
Keywords:
 

Attachments