Citect for Windows Version 1.20
This document contains important information that is not included in the Citect for Windows Documentation or in online Help.
Using Write to View This Document
If you enlarge the Write Window to its maximum size, this document will be easier to read. To do so, click the Maximize button in the upper-right corner of the window. Or open the Control menu in the upper-left corner of the Write window (press ALT+SPACEBAR), and then choose the Maximize command.
To move through the document, press PAGE UP or PAGE DOWN or click the arrows at the top and bottom of the scroll bar along the right side of the Write window.
To print the document, choose the Print command from the File menu.
For Help on using Write, press F1. Contents
1.0 Upgrade Information
1.1 Version 1.0 to 1.01
1.2 Version 1.01 to 1.10
1.3 Version 1.10 to 1.11
1.4 Version 1.11 to 1.20
2.0 Graphics Designer
2.1 Graphics Designer - Errata
1 Upgrade Information
You MUST use Windows version 3.1 or greater with this version of Citect. Citect no longer supports Windows version 3.0. We recommend that you should also use DOS Version 5.0 or greater as it is more compatable with windows and has better memory managment.
1.1 Version 1.0 to 1.01
This version fixes various minor bugs and adds some minor enhancements from version 1.0. You don't have to make any changes to your databases for this upgrade but you must recompile all your databases before running.
A problem you may encounter when upgrading is a change in the CITECT.INI file. Version 1.0 put some parameters under [CONFIG] when they should be under the [CTEDIT] section. Version 1.01 has fixed this bug and when you install version 1.01 it will move your parameters from [CONFIG] to [CTEDIT]. If you install on a network the install program will modify the CITECT.INI file of the computer you install on, but it cannot modify the CITECT.INI file of any other computer. You must modify the CITECT.INI file on any other computers on the network which share the same citect installation.
If you don't do this correctly CTEDIT will not be able to find your existing databases and CITECT runtime will say that NO DATABASES INSTALLED when it starts up.
If running on a network you must install this version on all machines before restarting your system. This version is incompatable accross the network with version 1.0, ie the client and server must both be version 1.01. If you try to use a mismatched version the client will not login to the server. The clients will report the hardware error NO SERVER COULD BE FOUND.
1.2 Version 1.01 to 1.10
This version fixes various minor bugs and adds Major enhancements from version 1.0. You don't have to make any changes to your databases for this upgrade but you must recompile all your databases before running. You may upgrade to this version from 1.0 or 1.01. A new form has been added which supports high resolution digital alarms. The first time you run CtEdit after installation or whenever you restore, the associated database will be created for all your databases.
If running on a network you must install this version on all machines before restarting your system. This version is incompatable accross the network with version 1.01, ie the client and server must both be version 1.10. If you try to use a mismatched version the client will not login to the server. The clients will report the hardware error NO SERVER COULD BE FOUND or the error INCOMPATABLE SERVER VERSION.
Whats New In This Version
The following enhancements have been added in version 1.10:
SQL Support
The SQL support allows Citect to access many other types of databases. The following database are supported: Oracle, Sybase, Gupta, NetWare SQL, DB2, Paradox, Microsoft SQL Server, Excel, dBase and ASCII. These databases may be accessed either by the Deivce system or directly via the SQL cicode functions.
SPC support
Statistical Process Control support will allow Citect to display SPC X bar, R bar and Standard
deviation graphs.
High Resolution Alarms
High resolution alarms are used when you require the exact order of alarm occurrence of the alarms in Citect. The exact time of each alarm is read from the PLC when the alarm is tripped. Once the time is read from the PLC Citect will sort the alarms into the correct order and display on the Alarm page and Alarm summary and log it to Alarm device.
Trend and low level graphic printouts
The trend printout functions allow you to printout trends directly to the printer instead of
displaying trends on the screen then printing the screen. This allows better print quality and
more control on the way the data is printed out. You also have access to the low level graph print functions so you may printout other data.
Serial Port Access
Cicode functions have been provided to allow direct access to the serial ports. This allows for the support of serial keyboards or other simple access to serial ports.
Citect DOS support
Citect DOS support allows a Citect for Windows IO Server to act as a Citect for DOS Scanner. This allows you to run a mixture of Citect for DOS and Citect for Windows systems on the same plant using the same IO Server.
CtEdit Enhancements
The following enhancements have been added to CtEdit. Accelerator keys to various menu
commands, eg Alt F10 to compile. Goto button on the Compiler Errors form, this button will go to the form which contains the error, you may also double click on the form to do this. Edit button on the Library and Report form, this button will call up the editor with the associated cicode or report source, you may also double click on the form to do this. Copy command under the File menu will allow you to copy a database onto the current selected database.
Serial NetBIOS
The serial NetBIOS support allows the use of remote Citect clients access to the Citect LAN over serial lines. This will allow you to connect remote Citects over phone lines or dedicated serial cables.
Documentation
The manuals have been upgraded to reflect the new enhancements as well as more examples and information added where required.
Configuration
A new trend definition has been added to Citect to cater for the Statistical Process Control (SPC). The number of the new trend that can be found in the Include database is 5 . In order to get the SPC system running without clashing with the already defined trend number 5 in
your system, please do the following:
1 - Record the details of your trend number 5.
2 - Delete trend number 5.
3 - Create a new trend number 5 as the one in the Include database.
4 - Create a new trend number as your old trend number.
5 - Change the old trend number in Pages Trend forms to the new one.
There are three new fonts for the trend graph system, namely GraphFont, GraphBigFont and
GraphSmallFont. If these fonts are not suitable for your printer system you can redifine them
in your database.
Alarm Parameters
The alarm parameters which effect the processing rate of the alarms have been simpilified in this version. The old parameters [Alarm] Process and [ALARM] WatchTime have been deleted and replaced with the single parameter [Alarm] ScanTime. See the documentation for full details.
Changed Functions
The DevOpen function has been changed to include an optional parameter.
hDev = DevOpen(sName, iMode);
Where iMode may be 0 (default) for shared mode or 1 to open the device in exclusive mode. If a device is opend in exclusive mode then the file or database can only be opened by a single machine.
1.3 Version 1.10 to 1.11
This version fixes various minor bugs from release 1.10 and some network problems. The network problems showed up with Windows for Workgroups, Novel Netware and DEC PCSA. Citect using these networks should now be stable. An extra option has also be added in the Citect.INI file to support multi protocols, see [LAN]LanaA option below.
The meaning of the [LAN] SesRecBuf option has changed with the fixes to the network. Citect will now allocate SesRecBuf buffers for each Server the machine is, plus that many for the local Client. For example if SesRecBuf=2 (the default), and the machine is a Alarm, Trend, Report and IO Server (also local client), Citect will use 2 * 5 = 10 buffers. You may have to increase the NetHeapSize option in the SYSTEM.INI file and allocate more NetBIOS Control Blocks (NCBs) in you Network Setup to allow for Citects increase use of buffers. If you have increased the SesRecBuf option above the default of 2 to get extra performance, you should try setting it back to 2 as the new changes should help with performance problems.
Lan Adaptor Option
The lan adaptor option has been added so you may specify which lan adaptor or protocol stack Citect will communicate with. As a default Citect will use lan adaptor 0. This option is used with LANs which support multi protocols and or Network adaptors, eg Lan Manager based networks or Windows for Workgroups. By specifying lan adaptor 1, Citect will communicate via the second adaptor or protocol stack. Note the stack must support the NetBIOS protocol. See you network documentation on multi adaptors and protocols.
[LAN]
LanA=0
Default is 0
Range is 0 to 8
Windows for Workgroups and Novel Netware
You may run Citect with Windows for Workgroups and Novel Netware in one of two ways. As Windows for Workgroups supports multi protocols stacks you may either use the Novell NetBIOS emulator or the NetBIOS which comes with WFW. It is better to use the WFW NetBIOS as it is built into WFW and does not consume low DOS memory. You must set the [LAN] LanA=1 option to tell Citect to use the second protocol stack, as the Novell IPX will be using the first stack.
If you want your WFW machines to communicate with other workstations which are not running WFW, ie just Novell NetBIOS you should use the Novell NetBIOS emulator. See the Networks.wri file which comes with WFW on how to setup. You should set [LAN] LanaA=0 (the default), to tell Citect to use the first stack.
Configuration
The help context strings in the MENU section of CITECT.FRM file have been replaced by context numbers. The users who have a customised CITECT.FRM file should modify the
respective section as shown in the CITECT.FRM file supplied with the installation disks.
New Functions
The following new functions have been included:
FileExist(sName); ! return TRUE(1) if file exists
FileSetTime(hFile,iTime); ! set the time of a file
iTime = FileGetTime(hFile); ! get the time of a file
FormRadioButton(col,row,sText,sBuf); ! add radio button to form
FormCheckBox(col,row,sText,sBuf); ! add check box to form
FormGroupBox(col,row,width,height); ! add group box to form
FormListBox(col,row,width,height,sBuf); ! add list box to form
FormComboBox(col,row,width,height,sBuf); ! add combo box to form
FormAddList(sText); ! add text to last list or combo box
The maximum size of 64k on .CI and .CII files has been removed. Files of up to 1Mb are now supported. However you should really keep your .CI files short and modular. Also the file to screen will display files up to 1Mb in size.
User paths are now supported. Up to 20 users paths may be defined in the CITECT.INI under the new PATH section. Then these paths may be used with any file name.
[PATH]
MyPath=c:\test\data
MyOtherPath=d:\moredata
Then use in any Cicode eg: FileOpen("[MyPath]:file.doc", "r");
1.4 Version 1.11 to 1.20
This version fixes various minor bugs and adds some enhancements to bring this version in line with Version 2.0. It includes the Version 2.0 Database Editor which has drop down scroll boxes, Edit Menu and new Protocol help. Several new protocols have been included, check online help for full details. This version is network compatable with Version 2.0 so you may mix version 2.0 and version 1.2 clients and servers.
The following functions have changed, see online help for full details:
Function Changes
FormComboBox mode added to control sorting
FormListBox mode added to control sorting
FileFind new documentation
FileSplitPath new documentation
FileMakePath new documentation
The alarm category database now supports a Alarm OFF Action field. When an alarm goes off in the specified category this command will execute.
New Mouse command keys have been defined. These key commands only operate when the mouse is clicked over the top of the command cursor. So if you configure the keyboard command 'KEY_LBTN_CMD_DN" on a symbol, that command will only execute if the left button is clicked on the symbol. If you use these commands you should not use the KEY_LBUTTON_UP keys and you should set the parameter [ANIMATOR] EatMouseClick=1. This parameter will cause the KEY_nBUTTON _nn type keys to be eaten when one of the KEY_nBTN_CMD_nn is being executed. The new commands may interfer with existing mouse keys, so you may disable this feature with [ANIMATOR] ConfigureMouseCommand=0. The following keys have been defined:
KEY_LBTN_CMD_UP
KEY_LBTN_CMD_DN
KEY_RBTN_CMD_UP
KEY_RBTN_CMD_DN
The following new drivers have been included:
TICIM Texas Instrumentas 550 CIM port
TAYLOR ABB Kent-Taylor
IZUMI IDEC IZUM FA Series
TELMAP Telemecanique MAPWAY
COMLI SattCon 05-30
MELSECF Mitsubishi Melsec FX
SIDIRECT Siemens Programming Port
SYENET Square D Ethernet
1.4 Font sizes in printed reports
There is now a function that provides the ability to change the font size of text in a report sent
to a printer. This function is the PrintFont() function. You should call this function only in a report. It will change the font style for the device (or group of devices) defined in the Reports form (output device field). It will only have effect on reports being printed to a PRINTER_DEV; it will have no effect on other types of devices such as
ASCII_DEV and dBASE_DEV.
Syntax PrintFont(String)
String The name of the citect defined font to use.
Return Value 0 (zero) if successful, otherwise an error number is returned. Refer to Appendix A for a list of Cicode errors.
Example The following report file...
{! example.rpt }
-------------------------------------
An example Report
-------------------------------------
{CICODE}
PrintFont("HeadingFont");
{END}
Plant Area 1
{CICODE}
PrintFont("ReportFont");
{END}
{Time(1) } {Date(2) }
PV_1 {PV_1:#####.##}
PV_2 {PV_2:#####.##}
----------End of Report---------------
...will print out as...
-------------------------------------
An example Report
-------------------------------------
Plant Area 1
04:41:56 19-10-93
PV_1 49.00
PV_2 65.00
----------End of Report---------------
2 Graphics Designer
2.1 Graphics Designer - Errata
A Driver for the Compaq QVision Graphics card is now shipped with Citect. The Driver can be found in the CITECT\BIN directory. To install the driver, the driver file must be copied to the CITECT.DSP file in the CITECT\BIN directory and the parameter "[DRAW] Mode=" must be set in the CITECT.INI file.
Compaq Q Vision Driver
Driver name AHDCQQV.DSP
Mode Resolution Colors
0 640 * 480 256
1 1024 * 768 256
See the Graphic Designer manual for details on other drivers supplied with Citect. If a driver for your Graphics card is not listed, contact Citect support.
3 Citect for DOS support
The Citect for DOS support allows a Citect for Windows machine to act as an DOS Scanner. So Citect for DOS machines may acces the PLC's which are connected to a Citect for Windows machines. The support also allows a Citect for DOS or DOS Scanner to act as an IO Server for a Citect for Windows machine. This allows you to mix Citect for DOS and Citect for Windows machines 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 to talk to PLC's on the Citect for Windows add the following parameters to the CITECT.INI file:
[LAN]
Disable=0
[CitectForDOS]
Server=1
This enables the Citect for Windows machine as a server for Citect for DOS clients. Configure the units on the Citect for DOS as REMOTE and units on the Citect for Windows as per the manual. The link will occur by matching the Unit numbers so they must be the same.
To allow a Citect for Windows to talk to PLC's 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 IO Server in the Citect for Windows using the above name (eg CitectForDOS). This IO Server must contain all the PLC units with the correct protocols and unit numbers 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.
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.
Related Links
Attachments