unCoreInternals 9.3.0
|
This document details the step by step procedure on how to develop a PVSS-UNICOS application. It is a natural following of the document CREATION OF A WINCC OA - CPC 6 APPLICATION. The content of that document is intended as already executed before following the content of this document. Procedure on creating a WIN CC OA project and importing CPC devices can be found in the mentioned document.
From this point onwards, the following acronyms will be used:
Synoptic: PVSS panel.
Any problem during installation or development can be reported to the following email address: UNICO.nosp@m.S.Su.nosp@m.pport.nosp@m.@cer.nosp@m.n.ch.
As a general rule, the following characters must not be used to name folders, files, panels, DP, DPE, device name, device type, PVSS system name and PVSS project name:
Use instead "_".
For the development of the PVSS-UNICOS application the following hardware will be needed:
The following software must be installed:
Please note that if PVSS is already installed, it is better to de-install it, re-install it again and apply the patches.
Do not use the " " and "-" character In reply to: the folder and path name of the PVSS installation folder, use instead the "_" character or the capital letters. E.g.: C:\ETM\PVSS2 The UNICOS core team will provide the following zip files:
The component installer must be downloaded from the EN/ICE web site: http://www.cern.ch/wikis/display/EN/PVSS+Service+Download+3.8SP2
The Windows computer will act as a DS and OWS. Note: For Linux DS computer, contact the UNICOS support. To develop the application the following procedure can be applied:
1.) Collect information on the project: Section 4.2.
2.) Create a PVSS project, set up the PLCs and install the components refer to document CREATION OF A WINCC OA - CPC 6 APPLICATION.
3.) Set-up the UNICOS-S7 communication: Section 4.4.
4.) Validate the UNICOS devices: Section 4.6.
5.) Develop the synoptics and configuration of the WindowTree: described in unTree component documentation
6.) Configure the TrendTree: described in unTree component documentation
7.) Configure the systemIntegrity: Section 4.9.
8.) Configure the application security: Section 4.10.
9.) Modify if necessary the configs of the devices: Section 4.11.
10.) Configure the email: Section 4.12.
11.) Configure the alarm archive: Section 4.13.
12.) Package the development to the target application: Section 0.
The following information must be decided before starting the PVSS-UNICOS:
The ip numbers of the DS and PLCs can be the one used at consortium site. Note: Temporary IP numbers can be given for the development of the application in LAB, they can be replace afterwards on the production site by re-importing the communication file (without the Delete keywork) or by changing the IP number of the PLCs.
13.) Start the manager running unicos_scripts.lst. Add the created PLC into the systemIntegrity (from the configuration menu, Figure 1 and Figure 2). Select the unicosS7PLC option from the list (left side), select the PLCs, the add option and press the proceed button. A click on the refresh button shows the list of the PLCs that are included into the systemIntegrity. The time out delay to send the DS ip number (IP Sending delay in msec.), synchronized the PLC date and time (PLC Time Synchro delay in sec.) and the checking of the PLC state (PLC Checking delay in sec.) can also be modified. Default settings can be restored.
14.) From the systemIntegrity run-time panel disable the PLCs (from the Diagnostic menu, Figure 3 and Figure 4). Select unicosS7PLC option from the list (left side). Select the line with the text Communication PLCname by double click and then right click.
15.) From the PVSS Console, stop the simulation driver.
This step has to be done whenever the characteristics of the archive are modified.
1.) From the menu Utilities (Figure 3), select Value archive.
2.) Select an archive from the list and click on the Activity buttons.
3.) Do the file switch (Figure 5).
1.) If the DS is in a local network and there is no DNS defined in the environment, define each PLCs in the file C:\wnt\system32\drivers\etc\hosts.
2.) Start the S7 driver: PVSS00S7.
3.) Enable the PLC (if there is more than one PLC, enable one PLC at a time): Figure 4.
4.) Open the Front-end diagnostic; select the PLC by double click on a PLC (Figure 3 and Figure 6). The behaviour shall be:
5.) If there is PLC-PLC communication: text of type Communication plc->plc, the alarm state should be green (Figure 6).
From the Front-end diagnostic (Figure 6), it is possible to force a synchronization of the PLC time to the DS time, to reset the S7 error, to request all the PLC data except the event data and to delete un-used PLC applications.
Note: this section is only for connection with Schneider PLCs. For Siemens PLC, refer to section 4.4.
6.) if the DS is in a local network and there is no DNS defined in the environment, define each PLCs in the file C:\wnt\system32\drivers\etc\hosts.
7.) Start the modbus driver: PVSS00mod.
8.) Enable the PLC (if there is more than one PLC, enable one PLC at a time): Figure 4.
9.) Open the Front-end diagnostic; select the PLC by double click on a PLC (Figure 3 and Figure 6). The behaviour shall be:
10.) If there is PLC-PLC communication: text of type Communication plc->plc, the alarm state should be green (Figure 6).
To find the default in the communication with the PLC use the Front-end diagnostic panel (Figure 6) and the PVSS console log.
The MODBUS error codes (ModPlc run-time data) are:
11.) 1: the PLC is not reachable (Figure 8).
12.) 2: there is a timeout in the connection with the PLC, the PLC is considered as dead.
For these two errors, the systemIntegrity handles the re-connections and reset the error code. These errors means that the PLC is not started or not well defined in the hosts file. Figure 9 is a typical error when the PLC is not defined in the hosts file.
13.) 4 to 6: MODBUS errors. These errors are not reset by the systemIntegrity. This must be done from the Front-end diagnostic panel by clicking on the enable/disable button and the reset modbus error (Figure 6). The typical errors are:
14.) the Ip number is sent (every 4.5 sec. the Ip is set to a value and then to 0) the sentFrame counter is incremented but no data are received:
15.) The colour of the events in the eventList is cyan or the time of the counter in the Front-end diagnostic is the DS time +1msec. or the invalid is set and there is an alarm Time synchronisation (Figure 6).
16.) The counter is not changing
In some cases it is better to restart the modbus PVSS driver.
Each PLC is also checking the state of the connections of the other PLCs it is in communication with. For example for a Quantum communicating with a Premium, two additional alarms will be in the Front-end diagnostic panel (Figure 6):
17.) Communication Premium -> Quantum.
18.) Communication Quantum -> Premium.
These alarms are evaluated by each PLC and reported to PVSS, this is to report that the PLC has detected a communication problem with its partner. They should be green, however if they are red it should not prevent the PLC-DS communication to work fine.
From the Front-end diagnostic (Figure 6), it is possible to force a synchronization of the PLC time to the DS time, to reset the modbus error, to request all the PLC data except the event data and to delete un-used PLC applications.
There is no need to do a synoptic to validate the UNICOS devices.
1.) Set the time-out of the automatic deselection: open the Select/deselect diagnostic panel (Figure 12) from the Diagnostic menu (Figure 3), and set the time out of the automatic deselection (Figure 12).
2.) From the unicosHMI panel open the Device Overview panel (Figure 13).
3.) Select the PLC, the application, the device type and press the Apply button (Figure 13). In the tree device overview, the filtering criteria can be modified by clicking on the Filter button (Figure 14).
4.) If there are more devices than free space in the screen, one can navigate between devices of the same type by selecting the range number of devices to show (Figure 13).
5.) Select the device, the contextual buttons of the device is shown in the contextual area in the bottom left side (Figure 13).
6.) If the device state is not changing according to the requested action check:
The systemIntegrity component checks that the PVSS-UNICOS application is running in good condition:
3.) It checks the state of the drivers, the state of the archives, the database size, the version of the imported file with the version of the front-end software and of the state of the remote PVSS systems. Note: For unicosS7PLC only.
4.) It checks the state of the PLCs connected to the DS.
5.) It sends the DS ip number to the PLCs.
6.) It checks the state of the PLC-PLC connections.
7.) It checks if the date and the time setting of the PLCs is coherent with the date and time settings of the DS.
In the systemIntegrity configuration panel (from the configuration menu, Figure 1):
1.) Select archive in the list of components: value archive and alarm archive. Add the archives configured for the PLCs (Figure 42). Select the archive, the add option and press the proceed button. A click on the refresh button shows the list of the archives that are included into the systemIntegrity. Note: The systemIntegrity for the value archive checks if there are less than two file switch during the Archive checking delay, if the manager is off, if the archive is offline, in the latter case the manager is stopped. For the alarm, it checks if there are less than teo file switch during the alarm checking delay, if the size of the current alarm file is less than 100Mb and if the size of the overflow alarm file is less than 50Mb.
2.) Select driver in the list of component. The drivers configured for the PVSS application (Figure 43). Select the driver, the add option and press the proceed button. A click on the refresh button shows the list of the drivers that are included into the systemIntegrity.
3.) Select dist in the list of component. Any remote PVSS system (in case of PVSS distributed system) into the systemIntegrity (Figure 44). Select remote system, the add option and press the proceed button. A click on the refresh button shows the list of the remote systems that are included into the systemIntegrity. Note: The PVSS local system is never added because this is the one currently running.
4.) Add the check of the database size (Figure 45). By default the size of the db/pvss/alertrr.db is checked every 30 sec. and must be less than 100Mb. New files can be added in the “Internal configuration setup of the PVSS DB” (click on Internal configuration button and select PVSSDB (Figure 46). The first entry is the timeout and the following entries are the files to check.
5.) For the S7PLC: add the checking of the versions (Figure 47). If the version read from the S7PLC and the one read during the import of the device list differs an alarm is raised.
The state of the different components can be analysed with the systemIntegrity operation panel (Figure 4, Figure 48, Figure 49, Figure 50, Figure 51 and Figure 52). Right click operation are allowed. Remote system can be accessed.
Action to take in case of alarm:
6.) Memory: the DS is running with low memory. Stop any process using too much memory. PVSS will go to emergency mode if the DS stays too long time with this alarm. The only way to quit the emergency mode is to stop and start the PVSS project.
7.) Disk: the DS is running with too low disk space.
8.) Distributed: re-start the remote PVSS system.
9.) Driver: re-start the driver.
10.) ValueArchive:
11.) AlarmArchive:
12.) PLC:
13.) PVSSDB:
14.) ImportFile:
The application state shows the alarm status of the critical components of the UNICOS application. This is an easy way to know the state of the systemIntegrity alarms of the PVSS-UNICOS application.
1.) Open the Application of Configuration menu (Figure 1 and Figure 53).
2.) Add into the Application status, the PLCs imported in PVSS (Figure 55).
3.) Add into the Application status, the archives configured for the PLCs (Figure 56).
4.) Add into the Application status, the drivers configured for the PVSS application (Figure 57).
5.) Add into the Application status, the remote system if any.
6.) Add memory and disk space alarm (Figure 58).
7.) Other PVSS alarms can also be added (Figure 53).
8.) Configure the synoptic (Figure 53) opened at start-up of the unicosHMI.
9.) Configure the GIF logo file and the Application name shown in the header of the unicosHMI panel.
10.) Configure if necessary (Figure 54):
11.) Configure the ManReg time-out. This time-out is the length of the pulse sent to the PLC for the validation of the commands that are sent to the PLC.
12.) The device prefix, this prefix will be used to create the devices in PVSS during the import.
13.) The manReg timeout: this is the time out used to reset the bit of the manReg when a command is sent to the PLC.
14.) Event16/event32 protocol event type. The UNICOS event protocol support event16: only the current 16 bits event and event32: old and current 16 bit event value combined in a 32 bit event value. During the installation of the unicosObjects component, the event protocol is set to event32.
15.) The DPE used in the objectList to get the state of the devices.
16.) The DPE used in the eventList to get the list of events of the devices.
17.) If the default time shown in the EventList, ObjectList, AlarmList and MessageText is in UTC or LTI: local time format (the other time format that the one set can be shown via a right click).
18.) The DPE used by the device selector provided by the unicos-pvss package. This DPE is used to list the device name.
19.) The default setting of the hierarchy display can also be modified (Figure 59). These settings will be the default one used during further installation or update of the unicosObjects components.
20.) The state of the Application alarm is shown in the unicosHMI panel. Open the run-time panel of the Application (Figure 60) by double-clicking on the System Status of the unicosHMI panel. Remote system can be accessed.
21.) A double click on one application name on the left side list and a double click on a line of the list of alarm of the selected application followed by a right click (Figure 60) gives access to the detail and the possible actions of the alarm (Figure 61).
The PVSS configs can be modified online into the PVSS application for fast modification and to check if the setup is correct:
1.) Open the Device configuration from the configuration menu (Figure 1 and Figure 62) and select a device. The current configs can be re-loaded, saved and discarded. Note: The configuration of the address, smoothing, alias/description, archive, pv_range, and alert pop-up panels are automatically saved when the Apply button is pressed (Figure 63).
2.) Select the configs to modify. The following configs can be modified:
3.) Data point element config: Archive (Figure 63), pv_range (Figure 63), alarm range (Figure 63), address (Figure 63), and smoothing (Figure 63) on local and remote system.
4.) Data point element config: unit (Figure 62), format (Figure 62) and alias/description (Figure 63) can only be modified on local system.
5.) Description, diagnostic, synoptic, html, alias, domain and nature (Figure 62) can only be modified on local system.
6.) Name for the PCO and PID (Figure 62) can only be modified on local system.
7.) The Y scale in the faceplate: Faceplate Trend table.
Any modification must be reported into the specification file otherwise the next time the data will be imported into PVSS the modifications will be lost or an export of the devices must be done and then report back to the specifications.
Email (and also CERN SMS message sent by email) can be configured (from the Alert Mails button of the systemIntegrity configuration panel Figure 2). A report for each category can be sent periodically: the list of DPE to send via the report and frequency can be configured. The unSystemAlarm category is configured by default: email for systemIntegrity alarms. Categories can be added/removed/enabled/disabled8 (Figure 64).
An email is sent to all the defined receiver of all categories at startup of the PVSS00ctrl.
It is possible to configure an email/SMS for an AnalogInput, AnalogOuput, DigitalInput and DigitalOutput device from the faceplate (Figure 65 and Figure 66) and for Alarm device from the right click on the widget (Figure 67). This email configuration can also be imported and exported into text files.
The unMessageText component (Figure 68) is a kind of log book. Each action on a device (select/deselect, device button action) and any relevant error of the UNICOS utilities is reported to the unMessageText. The last messages are visible from the unicosHMI (bottom-right). Four types of message can be logged: INFO, EXPERTINFO, ERROR and WARNING. Filters are available to configure which type of message to show (Figure 69). The history (Figure 70) is accessible from the unicosHMI with a right click on the unMessageText (Figure 68).
The alarm must be configured to avoid too large file size:
1.) Open the Alarm archive (Figure 71) from the Utilities menu.
2.) Set the file switch frequency and number of files to keep.
The following data have to be packed:
1.) The specifications.
2.) The WindowTree and TrendTree configuration: export of the WindowTree and TrendTree hierarchy and the panel, plot and page navigation. Note: The UNICOS core team will provide a tool for the export.
3.) The zip file of all the folders of the project except the db, config, printers and log folder. This can be done with the online backup of the project (Figure 74 in Section 5.3).
During the development of the new application that has to be merged into an existing one, one should take care of the following:
1.) Use the same PVSS system name and system number as the final one.
2.) During the development of the synoptic, do not use the same synoptic name as the one already existing in the running DS.
3.) Do not use the same names for the WindowTree configuration:
4.) Panel
5.) Folder
6.) Do not use the same name for the TrendTree configuration:
7.) Page
8.) Plot
9.) Folder
To install the application in the existing DS the following procedure can be followed:
1.) From the systemIntegrity run-time panel disable the configured PLCs (from the Diagnostic menu, Figure 3 and Figure 4). Select the line with the text Communication PLCname by double click and then right click.
2.) Stop all the OWS computers.
3.) Stop the modbus driver.
4.) Do an online backup of the current application: Section 5.3.
5.) Do a zip of all the folders of the project except the db and log folder.
6.) Extract all the data from the current project and send them to the LHC Logging.
7.) Unzip the new project folders into the project in the DS computer: panels, etc. are restored into the DS. Existing files must not be overwritten. In case there is a redundant or a bad definition into the new project, this shall be corrected before continuing.
8.) Collect the info: Section 4.2.
9.) Modify the specifications: see document CREATION OF A WINCC OA - CPC 6 APPLICATION.
10.) Import the specification into the PLCs: see document CREATION OF A WINCC OA - CPC 6 APPLICATION.
11.) Import the specifications into the PVSS project: see document CREATION OF A WINCC OA - CPC 6 APPLICATION. Note: The PLC configurations of the previous PLC must not be overwritten.
12.) Set-up the UNICOS-MODBUS communication for all the previous configured PLCs: Section 4.4.
13.) Validate the UNICOS devices of all the previous PLCs: Section 4.4.
14.) Set-up the UNICOS-MODBUS communication for all the new configured PLCs one per one: Section 4.4.
15.) Validate the UNICOS devices of all the new PLCs: Section 4.4.
16.) Restore the WindowTree and TrendTree: import of the WindowTree and TrendTree hierarchy and the panel, plot and page navigation. Note: The UNICOS core team will provide a tool for the import.
17.) Configure the systemIntegrity with the new PLCs and archives: Section 4.9.
18.) Configure the application security with the new PLCs, new archives and new PVSS remote systems (if any): Section 4.10.
19.) Modify if necessary the configs of the devices: Section 4.11.
20.) Configure if necessary the email: Section 4.12.
21.) Configure if necessary the alarm archive: Section 4.13.
22.) Modify the WindowTree and TrendTree if necessary, e.g.: do a new hierarchy, mix in the same hierarchy the synoptics of the old PLCs with the ones of the new PLCs, etc.
23.) Do an online backup.
To do an online backup of the PVSS application:
1.) do an online backup of the database:
a.) Open the Online backup utility (Figure 72) from the Utilities menu.
b.) Configure the backup location (Figure 73) and press the Apply button.
c.) Start the backup (Figure 72).
2.) do an online backup of the parametrization of the project (all folders except log, help, msg, printer and source and an ascii export of all the DPTs and DPs of the project):
a.) Open the Online backup utility (Figure 72) from the Utilities menu.
b.) Configure the backup location (Figure 73) and press the Apply button.
c.) Start the backup (Figure 74).
The list of existing backups is accessible by pressing the refresh button (Figure 75).
The device data widget of devices from different PVSS system can be mixed in the same synoptic (panel) and plot. If the remote system is not available the device data colour will set to Device not connected colour (Figure 95). As soon as the remote system is up and running, the device data will be set accordingly to the current state of the device.
The configuration of the device name from the PVSS00NG can be done:
3.) While the remote systems are up and running and therefore the filtering device selector has access to all the device names of all the PVSS system. Filters on the PVSS systems are supported: Figure 15, Figure 16 and Figure 17.
4.) Even if the remote systems are not connected. The device names of the remote systems are not available, but the name can be still entered: Figure 17. Similarly plots can be configured with data from the local system and remote systems.
5.) While the remote systems are up and running and therefore the filtering device selector has access to all the device names of all the PVSS system. Filters on the PVSS systems are supported: Figure 32, Figure 35 and Figure 36.
6.) Even if the remote systems are not connected. The device names of the remote systems are not available, but the name can be still entered: Figure 32. It is also possible to configure:
7.) The list of plots in a page with plots from the local system and remote system.
8.) The horizontal navigation of a plot, page and panel can also be configured with plots and pages from a remote system. However this is not recommended, the plots and page should always be taken from the local system. The panel's device instances are always taken from the local system.
The PVSS application must have been configured as a distributed system. To declare the remote systems:
1.) Define all the remote PVSS systems the local system is connected to by starting the Distributed System configuration tool (Figure 1 and Figure 76):
2.) the PVSS system name, PVSS system ID.
3.) the hostname, post number must be entered, "" are for default value local host and default port number.
4.) Start (stop and restart if it was started before) the PVSS00dist manager from the PVSS console.
5.) Include the remote system into the systemIntegrity (Section 4.8) and into the application (Section 4.10).
6.) Do this configuration in all the other systems.
The state of the remote systems can be monitored (Figure 3 and Figure 77).
The unicos-pvss package allows the creation of new device type and the modification of:
7.) existing device type.
8.) UNICOS front-end device type.
9.) systemIntegrity device type.
This must be done in collaboration with the UNICOS core team.
To add a new device type:
10.) Create a data point of type _UnObject with the name deviceType_unicosInfo.
11.) Set the config of the device type (Section 7.1).
To add a new front-end device type:
12.) Create a data point of type _UnFrontEnd with the name deviceType_unicosInfo.
13.) Set the config of the device type (Section 7.2).
To add a new systemIntegrity device type:
14.) Create a data point of type _UnSystemIOntegrity with the name deviceType_systemIntegrityInfo.
15.) Set the config of the device type (Section 7.3).
The following items of the UNICOS device type data can be modified (Figure 1 and Figure 78):
16.) The list of widget.
17.) The faceplate.
18.) The contextual menu.
19.) The select state.
20.) The functions configured for the device.
The following items of the front-end device type data can be modified (Figure 1 and Figure 79), the function are called during the import of the devices and the device configurations:
21.) The function that check the delete command.
22.) The function that executes the delete command.
23.) The function that check the front-end settings.
24.) The function that executes the import of the front-end settings.
The following items of the systemIntegrity device type data can be modified (Figure 2 and Figure 80):
25.) The function called during the initialization of the systemIntegrity of this device type.
26.) The function called whenever a request is sent to this device type: add/delete/enable/disable/diagnostic.
27.) The function called whenever the config data of this device type are modified.
28.) The config data of this device type.
29.) The panel to configure the systemIntegrity of the devices of this device type.
30.) The panel to show the status of the systemIntegrity of the devices of this device type.
The list of devices and their configuration can be exported (Figure 81) to an ASCII file having the same format as the file to import. The file may contain the following data #VALUE! when the device data configuration cannot be read, for instance if the device has no alarm configuration, the HH, H, L and LL value cannot be read and are replace by #VALUE!.
Since unicos-pvss-3.6 it is possible to configure the main interface and introduce a user defined panel to be pop-up, the panel name, X and Y position (Figure 53).
Since unicos-pvss-3.6, the masking of event is possible when a device is flipping; this will result in having no archive history in the event list for this particular device. When the event is masked an "e" letter appears in the top right position of the widget (Figure 85) and the check in the device faceplate (Figure 92). Unmasking will re-enable the archive on the event, thus resulting in having the event in the event list. The mask and un-mask is accessible via the right click on the widget (Figure 85). The masking state of the event is exportable (Section 8.1) and can also be imported. The list of devices with the event masked can be listed from the Utilities menu as well as the list of masked alarms.
Since unicos-pvss-3.6, it is possible to link device, the list of linked devices is accessible from the right click from the widget (Figure 89), the faceplate of the linked devices can be opened by selecting the device. The linked device can be imported and is also exported with the device data (Section 8.1). Links can be added dynamically from the device configuration (Section 4.11).
A new feature was introduced in unicos-pvss-3.6 for the AnaDig and Analog device. When one of the device links is of type Controller and on the same PVSS system a "R" letter appears in the bottom right position in the widget (Figure 90) and a new tabulation appears in the faceplate (Figure 91): Regulation that shows data from the Controller (maximum four) and the Analog/AnaDig device.
In unios-pvss-3.6 the application backup utility was introduced. It is triggered by the online backup (Section 5.3). The result is a backup of the PVSS database, panels, pictures, images, scripts and libs folders of the project without the value archive and alarm archive. This backup is in the folder configured for the online backup.
31.) Mode: This letter displays current object mode with its associated color. Only one mode could be active.
Mode | Letter | Color |
---|---|---|
Auto | None | None |
Manual | M | White |
Local | L | White |
Forced | F | Yellow |
Regulation | R | White |
Tracking | T | White |
32.) Data quality: This letter displays current object warning.
Data quality | Letter | Color | Priority |
---|---|---|---|
Invalid | N | Cyan | Highest |
Old data | O | Cyan | Highest |
IO Error | E | Orange | Highest |
IO Simulated | S | Orange | High |
Forced <> Auto | W | Orange | Normal |
Manual <> Auto | W | Orange | Normal |
Position Warning | W | Orange | Normal |
... | W | Orange | Normal |
If any data of the current object is invalid (PVSS _invalid), a letter N in cyan is displayed in the warning letter position.
The letter O is shown if the PLC is enabled and the driver handling the communication with the PLC is running and the PLC counter is changing periodically.
33.) Alarm This letter displays the current object alarm state.
Alarm | Letter | Color | Priority |
---|---|---|---|
Full Stop Interlock | F | Red | Highest |
Stop Interlock | S | Red | High |
Start Interlock | I | Red | Normal |
Position Alarm | P | Red | Normal |
Mask | Letter | Color | Priority |
---|---|---|---|
Alarm Blocked (in PLC) | B | Yellow | Highest |
Alarm Masked (in PVSS) | M | Yellow | High |
If no alarm is defined in PVSS (_alert_hdl), for all the AnalogInput and AnalogOutput devices all the square boxes of the alarms/Limits are in black (Figure 93). For the DigitalInput/DigitalOutput the alarm square boxes are greyed out (Figure 94).
34.) Event masked: This letter shows the mask/unmask state of the event.
Event mask | Letter | Color |
---|---|---|
Event masked | e | Yellow |
Event unmasked |
35.) Selection: When the object is selected, the selection shape goes white.
36.) Body
Body | Color | Priority |
---|---|---|
Invalid | Cyan | Highest |
Alarm Unack. | Red Blinking | High |
Alarm | Red | Normal |
Forced Mode | Yellow | Low |
Auto Mode | Green | Lowest |
Each device has a faceplate and associated contextual buttons. The faceplate (Figure 97) shows the detail information of the device. The operation on the device is done via the contextual buttons in the bottom of the faceplate (Figure 97).
If any data of the current device is invalid (PVSS _invalid), all the displayed data are in colour cyan in the faceplate (Figure 96).
If the PLC is disabled, or the driver handling the communication with the PLC is not running or the PLC counter is not changing periodically all the displayed data are in colour cyan in the faceplate (Figure 96). Figure 98 shows the list of UNICOS widgets.