Simple Sample” are small projects that demonstrate simple features. The target is give a quick overview about the theme and be used as start point for related discussions. Follow there are a short description and the configuration main steps.

Concept:

ProDiag is an efficient and easy to use message system specially developed for operation supervision of machines / plants.

An special characteristic is the possibility to show in the HMI/SCADA system, the user program logic (e.g. ladder) online that generates the message. It makes easier to the operator to find and correct by itself (without help of maintenance people / configuration software) operations problems (like “a forgotten open door”).

ProDiag features could be applied to tags or to blocks interface (FB's inputs/outputs - object of this simple sample).

Principle:

An alarm will appear if the supervised signal AND the condition (one or more, sometimes optional) are present during at least a configured (optional) time.

An alarm will go out immediately if supervised signal OR condition will not present.

While the alarm is active, if it is selected in Alarm view object and a command is given (e.g. by button), the PLC Code View object will show the user program that trigger the message.

Divisions / Types:

ProDiag permits to classify the message in different levels / types.

Some of then are fixed, some are user configured.

Types this is a fixed division of ProDiag. All types has the same configuration properties (despite some attributes are mandatory for some types). This division are mainly as classification proposes (I.e. the user could use them with other intends...):

• Interlock: monitor if something are “interlocking” a condition (trigger) (for example, the motor didn't start because “a door was open”). Mandatory information: Interlock (itself) and one condition.
• Action: monitors if a desired action (e.g. movement) really has been started. Mandatory information: action (itself), one condition and a start-up time.
• Reaction: monitors if an desired action (e.g. movement) really has been reached. Mandatory information: reaction (itself), one condition and a reaction time.
• Position: monitor if a movement reached a position. Mandatory information: position (itself) and one condition.
• Operand: monitors the signal state (TRUE or FALSE) of a boolean operand (simple state indication, that doesn't match with others types). Mandatory information: Operand (itself)
• Error message: show error messages. Mandatory information: error signal (itself)
• Text message: show text messages. Mandatory information: text signal (itself)

Configuration:

PLC side

• Create a FB.
• Define an input on FB
• Select the create input → Properties → Supervision → click on “add new supervision” (configure it as desired, e.g. selecting “interlock”).

Notes:

up to TIA V14, when a Supervision is added, a block Default_SupervisionFB is created on the CPU program block folder, a instance DB and a specific OB (ProdiagOB) are also created.

SCADA Side

• Place the object PLC Code viewer on a screen (in our example, the screen is the Screen_1 and the PLC Code viewer has the default name, “PLC Code Viewer_1”).

• Place the object ProDiag Overview on the screen.

• Link the ProDiag Overview object to the PLC's Default_SupervisionFB block: Select the ProDiag Overview → Properties → General. Select the Default_SupervisionDB Block on CPU program block folder (Project tree). Select the variable “State” in the Project tree → “Details view” division and drag and drop it to the ProDiag Overview → Inspection Window → Properites → General → Process → Tag.

• Place a Alarm View on screen.

• Create a Bottom. In events call the function “ShowPLCCodeViewFromAlarm”, use the parameters Alarm Screen Name = Screen_1, Alarm view name = Alarm view_1, Basic screen name = Screen_1, Screen window name = not felled, Screen name of the PLC code view = Screen_1, Name of the PLC code view = PLC code view_1, Error tag = not felled.

TIP:

ProDiag could be run under S7-1500 CPU FW >= 2.0

ProDiag is free of charge up to 25 supervisions. It is possible to configure more then 1000 supervisions, but it demand licenses.

For tag supervisions, just interlock type leaves the ladder logic to the HMI / SCADA system.

If more the monitored operand (tag) is used more than one time in the program, CodeView will shows the first usage of the tag at start. PLC Code viewer buttons could be used to navigate to the other usages.

There is a relation ship between Supervision Type and PLC Tag Type (I, Q, M) the TIA help system shows a table about it in the topic “Information System → Visualize process → Using the diagnostic functions → Supervising machinery and plants with Prodiag → Create ProDiag supervision settings (S7-1500) → Possible uses of supervisions.”

PLC's Default_SupervisionFB block instance DB could be used in PLC user program / HMI / SCADA System to get information similar as displayed for the ProDiag Overview block.

Simple sample Project:

The attached project is an example of different types of the tag supervisions.

The trigger variables enable the messages together with the respective conditions.

The aux, aux1 and aux2 variables are used to illustrate online monitoring.

Once triggered a supervision, select the line in alarm window, and (if the text box shows that code monitoring is possible) click on “Show code” buttom.

References:

The TIA Portal Information System could be used as reference for ProDiag. There is two main path of information:

On PLC Side:

Information System → Visualize process → Using the diagnostic functions → Supervising machinery and plants with Prodiag.

On HMI/SCADA Side:

Information System → Programing a PLC → Supervising machinery and plants with Prodiag.

Hi,

ProDiag have same features regarding process diagnose. The "motion" feature, however is not  implemented in this version.