Creating a New Project • First ISaGRAF : Import tags from a First ISaGRAF project into the Shared Tags folder of the current project, and, if enabled, configure the communication interface with the ISAGR driver automatically. • ISaGRAF : Import tags from a ISaGRAF project into the Shared Tags folder of the current project, and, if enabled, configure the communication interface with the ISAGR driver automatically. • Think & Do : Import tags from a Think & Do project into the Shared Tags folder of the current project, and, if enabled, configure the communication interface with the TND driver automatically. • SteepleChase :
Import tags from a SteepleChase project into the Shared Tags folder of the current project, and configure the communication interface with the VLC driver automatically. • SixNet : Import tags from a SixNet project into the Shared Tags folder of the current project, and configure the communication interface with the SNET driver automatically. • OpenControl : Import tags from an OpenControl project into the Shared Tags folder of the current project, and configure the communication interface with the OC driver automatically. • Straton :
Import tags from a Straton project into the Shared Tags folder of the current project, and configure the communication interface with the STRAT driver automatically. Note: PC-based control has its own, customized interface that requires you to provide information about the PC-based control application in order to share tags with the IWS project. ALARM HISTORY DATABASE The alarm history can be saved either in the IWS proprietary format or to an external SQL Relational database by ADO. The alarm history settings can be configured in the project settings ( Options on the Project tab of the ribbon): Project Settings:
Options tab The Alarm History and Events interface allows you to configure the following settings: When saving the alarm history in the proprietary format, each alarm event is saved in a new line, using the pipe character ( | ) to delimiter the different fields, as illustrated below: P1|P2|P3|P4|P5|P6|P7|P8|P9|P10|P11|P12|P13|P14|P15|P16|P17|P18|P19|P20|P21 P1|P2|P3|P4|P5|P6|P7|P8|P9|P10|P11|P12|P13|P14|P15|P16|P17|P18|P19|P20|P21 . . Page 76 InduSoft Web Studio Field Remarks Syntax History Life Time (days) The history for alarm/event messages older than the number of days specified in this field are automatically deleted, following a FIFO (First-In, First-Out) behavior.
If this field is left in blank, the history of alarms/events are not deleted automatically. Number History Format Defines the format of the history of alarms/events: • Proprietary: Saves the history in the proprietary format. The alarm messages are saved in a text file with the name ALyymmdd.ALH, where: • yy is the last two digits of the current year. • mm is the month. • dd is the day There will be one history file for each day. By default, the alarm history files created with the proprietary format are stored in the \Alarm sub-folder of the project. However, it is possible to direct the alarms to a different directory by using the SetAppAlarmPath function from the built-in language.
• Database: Saves the history in a third-party SQL Relational Database (e.g., SQL Server). Combo-box Alarm Database When selecting Database as the format for the history of alarms, the specific settings to interface with the third-party SQL Relational Database can be configured by the dialog launched when pressing this button. For further details about support for third-party SQL Relational Databases, see Database Interface. —