Runtime issues

By default most output operations during runtime occur in the [DATA] or [RUN] location (see below for details). By default CitectSCADA configures the [RUN] location to the project directory. If you intend on making the project directory read-only, you need to modify the path(s) to a suitable read-write location.

• almsav.dat - Alarm data by default is saved in the [RUN] location, which is usually the project folder. You need to change this location if you intend on making the project folder read-only. Alternatively use the [Alarm]SavePrimary and [Alarm]SaveSecondary options in the citect.ini file to control the location of the output.
• Disk PLCs - If a user does not have the correct privileges for the [RUN] path, communications will be offline for disk PLCs. You need to change this location if intending to make the project folder read-only.
• User Cicode functions - Making a project read-only prevents the use of the following user functions: UserCreate, UserDelete, UserEditForm, UsetrSetPassword, UserSetPasswordForm. Attempting to use these functions results in an error code 262 (0x0106) ("Cannot open file").
• Alarm Cicode functions - Making a project read-only prevents the use of the following alarm functions: AlarmSetDelay, AlarmSetDelayRec, AlarmSetThreshold, AlarmSetThresholdRec. Attempting to use these functions results in a hardware alarm 400 (0x0190) ("Project or file is read-only"). You also cannot modify alarm properties such as threshold or delay.

Any files in your top-level project that require runtime read-write access have to be located outside of the project folder.