You can help by commenting or suggesting your edit directly into the transcript. We'll review any changes before posting them. All comments are completely anonymous. For any comments that need a reply, consider emailing training@inductiveautomation.com.
Version:
LESSON LIST
-
2:56About Transaction Groups
-
4:42Types of Groups
-
2:48Group Update Rate
-
3:17Item Types
-
3:19Tag References vs. OPC Items
-
2:58Expression Items
-
4:03SQL Query Expression Items
-
3:14Run Always vs. Triggered Items
-
3:04Hour and Event Meters
-
3:17Resetting Hour and Event Meters
-
2:50Trigger – On Value Change
-
2:21Trigger – While Condition is True
-
1:42Trigger – Rising Edge (Once)
-
2:12Trigger – Reset Trigger
-
1:50Trigger – Handshakes
Take Topic Challenge
LESSON
Trigger – Handshakes
Description
Learn how to use the handshake mechanism to communicate successful and failed executions to other parts of the system.
Video recorded using: Ignition 7.9
Transcript
(open in window)[00:00] When a transaction group executes, one of two possible outcomes can happen. Either the group completes successfully or an error prevents successful execution. Both of these cases can be communicated to other parts of the system through the handshake mechanism. Handshake's on the Trigger tab. And there are separate settings for success and for failure. Each time the group completes successfully, the item set to the success handshake will be written with the value specified. If something occurs in the group that prevents execution, the failure handshake will be written. The items used for the handshakes must come from inside of the group. So we can either use tag references or we could use OPC items set to read only if we didn't have a reason to store them in the database. For example, we might choose to write a one in the group that's successful and a two if it fails. Since I've used a tag reference here, other parts of the system can watch and monitor what is going on in the group. It's important to note that the success handshake is very similar to the reset trigger condition. So if you're using a trigger with the reset event, it's not necessary to use a success handshake. Or, you may choose to use it in order to notify a different tag or different part of the system that the group has completed successfully.