Q967 Readme V3.3

ArticleID: Q967
Created: 2/09/2008

 

Welcome to Citect for Windows Version 3.30

All the information you require to implement a Citect system is included in the Design Guide, a new multimedia based help system included with the Citect software, and installed on your computer with the Citect installation program.

Ø To display the Design Guide

1. Start either the Project Editor or Graphics Builder (with an icon from the Citect group).

   NOTE: If you are upgrading from an earlier version of Citect, backup all existing projects before starting the Project Editor or Graphics Builder.

2. From the Help menu, select Design Guide.

Ø To learn how to use the Design Guide

1. From the Design Guide Help menu, select How To Use This Guide.

Ø Changes to CITECT.FRM file

This release of Citect for Windows version 3.30 requires a modification to the CITECT.FRM file for Project Editor to run Citect correctly. If you use the standard CITECT.FRM file then simply install this version of Citect and upgrade your projects. Please note that you should backup all your projects prior to upgrading so that you can revert back to your previous version of Citect if need be. If you have a customised CITECT.FRM file you will need to backup your customised version prior to installing Citect for Windows version 3.30. Then after installing version 3.30 you will need to manually merge the installed CITECT.FRM with your customised version. In particular you will need to change the following lines in the FRM file:

COMMAND "Compile", "ctcmp", Master.NAME;

COMMAND "Run", "citect";

COMMAND "Archive", "ctbackup", Master.NAME;

Replace these three lines with the following:

COMMAND "Compile", "ctcmp", "/I", Master.NAME;

COMMAND "Run", "citect", "/I";

COMMAND "Archive", "ctbackup", "/I", Master.NAME;

After merging save the new customised FRM file into your bin directory and upgrade your projects as suggested in the previous case.

Ø Cannot compile and run a Citect project when using Windows 3.1

If you are using Windows 3.1 and are experiencing problems with compiling and/or running a Citect project it is probably because Citect is running out of file handles. To fix this problem add the following line to your AUTOEXEC.BAT file:

C:\DOS\SHARE /f:4096 /l:120

Ø Note on COMX Com port Driver

The configuration of the Boards and Ports Forms for using a com port now supports the format used in the 32 Bit version of Citect (Version 4). It is still backward compatible with the previous format so you do not need to change your configuration. However, if you want your project to run on both Version 3.30 and Version 4.10 you must follow the procedure outlined below.

These changes apply to Boards and Ports using the COMX driver only. In a Citect project there must be at most one COMX board. The physical computer com port to be used is given in the Port Number field of the Ports form, NOT in the Address field of the Boards form.

The following procedure will correct projects from previous versions.

1. Using Project Editor edit the first Board which uses COMX, set the Address field to 0.

2. Edit all the Ports which reference any COMX Board so that:

i) they reference only the first COMX Board form.

ii) the Port Number field contains the physical com port number to use.

3. Delete all Boards which are now unreferenced.

1. Compile and Test project.

   Ø Fixing printing problems

If you are experiencing problems printing through the protection key then you can use an updated driver that has been shipped with 16 Bit versions after Version 3.21. This driver can be installed by running the program INSTSENT.EXE which is located in the BIN directory of your Citect installation.

Ø Running Citect on Windows 95

This Version of Citect will run on both Windows 3.x and Windows 95. However, long filenames are not supported. Most importantly, when using the Backup utility, any long filenames in the project directory will be backed up with their corresponding short filename. Therefore, when restored, the file will only have its short filename.

• Windows 95 NETBIOS Not Found and LANA

Citect Node Setup does not auto-detect the network protocols installed on your computer when running under Windows 95. Version 3.30 supports a new mode of LANA so Citect can automatically find the correct protocol. You should set [LAN]LANA=-1. See KB Q1855 for full details.

Ø Latest Information

For the latest information (including upgrading from Citect Version 2.xx, and errors in the documentation), click on The Latest Information button. (For information about new features, click on the What's New in This Release button.)

Ø Bug Fixes

Some bug fixes may only take effect if a full re-compile of your project is performed. To do a full re-compile switch the incremental compile option off in Project Editor and click on the compile toolbar button.

Ø Upgrading the CITECT.FRM from Version 2.x

If you have modified the CITECT.FRM file and are upgrading from Version 2.x, you must upgrade the CITECT.FRM file using the following this procedure:

1. Back up your projects before installing version 3.xx.
   
   
2. Back up your existing CITECT.FRM file.
   
   
3. Rename your existing CITECT.FRM file to VERSION2.FRM.
   
   
4. Install Version 3.xx (Do not run the Project Editor or Graphics Builder).
   
   
5. Rename the CITECT.FRM file (installed with Version 3.xx) to VERSION3.FRM. (You need this file to merge with your version 2.xx CITECT.FRM, so that the final

   CITECT.FRM file will have both your changes and version 3.xx updates.)

6. Copy VERSION2.FRM to CITECT.FRM.
   
   
7. Using a text editor, copy the following form definitions from VERSION3.FRM to CITECT.FRM:

   Animated Symbols ("pgansym")

   Size and Move ("pgsizmve")

   Sliders ("pgslider")

   Events ("events")

   Accumulators ("accums")

8. Add the following option to your WINDOWS\CITECT.INI file:

   [Convert]HardCodedVersion2FormFile = 0

   (The conversion program bypasses the predefined database formats and uses the formats from your CITECT.FRM file.)

9. Run the Graphics Builder to convert your library, template and DBF files into Version 3 format, using your modified (Version 2) CITECT.FRM file.

   NOTE: If any database warnings display, contact Citect Technical Support.

10. Close both the Graphics Builder and the Project Editor.
    
    
11. Using a text editor, merge the remainder of the changes in VERSION3.FRM with CITECT.FRM. (Open both files with a text editor and manually copy any changes from VERSION3.FRM to CITECT.FRM.)
    
    
12. Set [CTEdit]Upgrade=1 in the WINDOWS\CITECT.INI file.
    
    
13. Run the Project Editor or Graphics Builder and select "Yes" to confirm the upgrade (DBF files only).

Ø ANSI & OEM Character Sets

Windows ANSI characters are converted to OEM characters by default. This conversion is controlled by the Citect.ini parameter [Ctedit] ANSIToOEM described below. You may need to change the setting of this parameter if the text in your projects appears incorrectly on your version of Windows.

[Ctedit] ANSIToOEM

Indicates whether Windows ANSI characters are converted to OEM characters.

Allowable Values 0 (Characters are not converted)

1 (Characters are converted)

Default Value is 1.

Users of European versions of Windows who are upgrading projects created with v3.21 to v3.30 will need to set ANSIToOEM to 0.

Users of Arabic versions of Windows will need to set ANSIToOEM to 0.

A new parameter has been added to control ANSI to OEM character conversion when printing to LPTx.DOS. Normally, this parameter should be left set to the default value of 1, however, if the characters are not printed correctly then you may need to change the setting.

[Device] LptDosANSIToOEM

Indicates whether Windows ANSI characters are converted to OEM characters when printing alarms and reports to LPTx.DOS. The conversion is required due to differences between Windows and DOS character sets.

Allowable Values 0 (Characters are not converted)

1(Characters are converted)

Default Value is 1.

See the Using Parameters topic in the on-line Help for information on how to change these parameters.

TITCPIP DRIVER

The TITCPIP driver is released in a Beta state. The Citect Testing Department have not completed formal testing of this driver. Some problems have been reported when using the driver with CAMP messaging turned on. This feature has been turned of by default to avoid these problems.