Repair Broken Shortcuts in FTView Studio Machine Edition
Summary
TLDRThis video script outlines the process of restoring and opening a factory communication setup in a project. It emphasizes verifying the communication path to the data source, typically a PLC. The script explains how to identify and recreate broken links between shortcut names and their references, whether they are direct reference tags or HMI tags. It provides a step-by-step guide on navigating the project tree to locate and resolve issues with shortcut names, ensuring seamless communication with the PLC at an IP address like 192.168.1.16.
Takeaways
- 🔌 The first step in restoring and opening a factory is to check the communication setup in the project tree to ensure the path to the data source (PLC) is intact.
- 🔗 It's common to find broken shortcuts to the PLC, which need to be recreated if they are missing or the link is broken.
- 🔍 To find the original shortcut name when it's missing, look for an object that references the PLC and check the connections tab for the shortcut name.
- 📝 Direct reference tags are one type of tag used in projects, where the shortcut name can be found in the connections tab of an object like a push button.
- 🏷️ HMI tags are another type of tag used, which are stored in a folder and can be checked for shortcut names in the address field.
- 📊 In projects using HMI tags, the shortcut name can be found by looking at the connections tab of an object like a numeric display.
- 📁 The 'system one' folder is an example of where HMI tags and their corresponding shortcut names are stored.
- 🔄 If the application has been stored and the shortcut name is missing, the process of recreating it involves checking the tag folder and address field for the original shortcut name.
- 🛠️ Recreating the link between the shortcut name and the PLC involves understanding the difference between direct reference tags and HMI tags and their respective locations in the project setup.
- 🎵 The script concludes with a reminder of the importance of maintaining proper communication setup and shortcut links for efficient factory operations.
Q & A
What is the first step to take when restoring and opening a factory talk view project?
-The first step is to go into the communication setup at the bottom of the project tree.
Why is it important to verify the communications path to the data source in a factory talk view project?
-Verifying the communications path ensures that the connection to the data source, typically a PLC, is still intact and functional.
What happens if the shortcut to the data source is not found in the communication setup?
-If the shortcut is missing, it needs to be recreated to establish the connection between the HMI and the data source.
How can you determine the shortcut name if it's missing?
-You can determine the shortcut name by checking an object that references the PLC, such as a push button object, and looking at the tag reference in the connections tab.
What are the two types of tags mentioned in the script that can be used in a factory talk view project?
-The two types of tags mentioned are direct reference tags and HMI tags.
How do you identify if a project uses direct reference tags or HMI tags?
-You can identify the type of tags used by checking the connections tab of an object. If a shortcut is visible, it's likely using direct reference tags. If not, and the project references a folder like 'system one', it's using HMI tags.
What is the significance of the 'system one' folder in the context of HMI tags?
-The 'system one' folder contains HMI tag names and their corresponding shortcut names and tag references, which are used when the project utilizes HMI tags.
How can you view the shortcut name and tag reference for HMI tags in a project?
-You can view the shortcut name and tag reference for HMI tags by navigating to the tag folder in the project tree, opening the 'system one' folder, and looking at the address field.
What should you do if the shortcut name is missing after storing your application?
-If the shortcut name is missing after storing the application, you should recreate the link by referencing the correct shortcut name found in the tag folder.
Why is it crucial to maintain the integrity of the link between the shortcut name and the PLC address?
-Maintaining the integrity of the link ensures that the HMI can correctly communicate with the PLC, which is essential for the proper functioning of the industrial process.
Outlines
🛠️ Restoring Factory Communications
The speaker begins by discussing the initial steps taken after restoring and opening a factory, focusing on the communication setup with a data source, typically a PLC. They emphasize the importance of verifying the communication path to ensure it remains intact. Often, they find that the shortcut to the PLC is missing or broken. To resolve this, they suggest recreating the link by referencing an object that connects to the PLC. The speaker differentiates between two types of tags used for references: direct reference tags and HMI tags. They demonstrate how to identify the shortcut name for both types by examining the connections tab of a push button object and a numeric display object, respectively. The process involves navigating through the project tree to the HMI tag folder and examining the address field to reveal the shortcut name. The speaker concludes by advising on how to recreate the shortcut if it's missing after saving the application.
Mindmap
Keywords
💡Communication Setup
💡Data Source
💡PLC (Programmable Logic Controller)
💡Shortcut
💡Tag
💡Direct Reference Tag
💡HMI (Human Machine Interface)
💡HMI Tag
💡Micrologic PLC
💡IP Address
💡Project Tree
Highlights
After restoring and opening a factory, the first step is to check the communication setup.
Verification of the communications path to the data source, typically a PLC, is crucial.
It's common to find that the shortcut to the PLC is missing or broken.
Recreating the link between the shortcut name and the PLC address is necessary if it's broken.
To find the shortcut name, reference an object that connects to the PLC.
Direct reference tags can be identified by checking the connections tab of an object.
The shortcut name can be revealed by examining the tag reference in the connections tab.
Some projects use HMI tags instead of direct reference tags.
HMI tags can be found in a specific folder within the project tree.
The shortcut name for HMI tags is displayed in the address field of the tag folder.
If a project uses HMI tags, the tag folder and address field are essential for identifying shortcut names.
If the shortcut name is missing after storing the application, the process to recreate it is clear.
The importance of maintaining and verifying communication links in industrial settings is emphasized.
The process of identifying and resolving communication issues with PLCs is outlined.
The distinction between direct reference tags and HMI tags is explained.
Practical steps for troubleshooting and fixing broken communication links are provided.
The necessity of knowing how to recreate shortcut names for both direct reference and HMI tags is highlighted.
Transcripts
[Music]
after restoring and opening a factory
talk view project the first thing I like
to do is go into communication setup at
the bottom of the project tree I then
verify that the communications path to
the data source which is typically a PLC
make sure that it's still there and
often times what I find is that the
shortcut is not there it doesn't exist
there is nothing in the shortcut window
I've seen other times where if I'm
referencing the shortcut the actual link
between the shortcut name and where it's
pointed to which in this case is a
compact logixs processor at 192 168
1.16 that link is broken when the link
gets separated or broken you have to
recreate that link one way to figure out
what the shortcut name was we'll close
this here is to go back to a screen and
then select an object that references
the p PLC there are two types of tags
direct reference is the first type of
tag we're going to see I'll click on
this push button object and then select
the connections tab when the connection
tab opens you can see that l340 is the
shortcut name the tag reference is
startor PB if the shortcut name was gone
I now know what it was some projects
don't use direct reference tags they use
what are called HMI tags and in this
situation you go into the HMI tag folder
to see what the shortcut name was we're
going to switch over and look at a
different application that actually uses
HMI tags if you go into this numeric
display object and then select the
connections Tab and you don't see a
shortcut the project is using HMI tags
the folder is called system one and the
actual tag name is called set point one
now we're going to go back into the HMI
tag folder so we'll cancel out of here
and select tags in the the project
tree we'll just hold up here for the tag
folder to open and then we'll maximize
it you can see all the folders and then
we're going to click on system one what
you're seeing are the HMI tag names and
then beside the address field you see
the shortcut name and the tag reference
this tag is actually a bit reference in
a micrologic PLC if your project uses
HMI tags you now know how to go into the
tag folder and look in the address field
to see the shortcut name if you've
stored your application and the shortcut
name is missing you know exactly what to
do to recreate
[Music]
it
関連動画をさらに表示
Allen Bradley Controllogix Compactlogix Ethernet Connection Studio 5000
Communication Strategy: Cara Buat Strategi Komunikasi | CPROCOM
How To Compile Source Code in Visual Studio!
How a DNS Server (Domain Name System) works.
Digital Twin Commissioning with Emulate3D
How To Transfer An Amazon Account To Someone Else
5.0 / 5 (0 votes)