I am attempting to implement tag substitution for a faceplate in order to display the description of my AOI. While using the tag /*S:0 {[Packaging Line 1]MyP_PF52x.@Description}*/ yields successful results, using /*S:0 {#2.@Description}*/ results in question marks appearing. I have directed #2 to [Packaging Line 1]MyP_PF52x, but the issue persists. Could the problem lie in incorrectly executing the syntax? I seem to be overlooking something crucial.
dternosky asked for help with tag substitution on a faceplate to display the description of their AOI. Using the tag /*S:0 {[Packaging Line 1]MyP_PF52x.@Description}*/ worked perfectly, but when trying /*S:0 {#2.@Description}*/, question marks appeared. Despite pointing #2 to [Packaging Line 1]MyP_PF52x, the issue persisted. Is there a mistake in the syntax? Unsure of what is missing. Remember to GO BLUE!
Experience the thrill of a Big 10 sniper drive-by! Count me in. Hey dternosky, could you try entering the direct tag reference version to find what you're searching for? While I may not be a pro at FTVS, I've never seen a data member with a format like .@Description before. Is this just a placeholder for this post, Keith?
Kamenges asked Dternosky to try using the direct version of the tag reference to locate the desired information. While not expert in FTVS, Kamenges mentioned never encountering a data member with a format of .@Description before, unless it is used as a placeholder in the post. It was noted that the direct reference was successful, indicating an extended tag property related to the description of the specified tag. Logix has supported extended tag properties since version 21. The FTView ME manual provides detailed information on this topic. In relation to the original poster's issue, the tag seems to not be resolving properly when using the parameter. It might be due to an improper loading of the parameter or an input error. Testing with a simpler substitution like '/*S:0 {[Packaging Line 1]#2.@Description}*/' where #2 is 'MyP_PF52x' can help determine if the parameter is loading correctly. If it does not work, the focus should be on fixing the parameter loading issue before delving into syntax errors. If it works, then there may be a syntax problem such as the parameter not accepting square brackets or spaces.
I've discovered that your parameter reference includes spaces in the initial section ("Packaging Line 1"). Dealing with spaces in parameter file references can be troublesome due to an issue with the ASCII code for that space character that FTView does not favor. One solution is to delete each space and input ALT + 0160 (no-break space) instead to see if that resolves the issue. Another option is to rename your shortcut without spaces. Additionally, while going through parameter files for a recent project, I noticed a double colon before the tag reference (Example:::[Packaging Line 1]MyP_PF52x). You could also consider trying this approach. I hope these suggestions are beneficial to you.
After encountering an issue with my processor shortcut, I resolved it by changing it to simply "L1," which successfully fixed the reference. Grateful for the support from everyone!
From what you've shared, it sounds like you're on the right track but just missing a tiny detail. Tag substitution can be a tricky process sometimes. For your condition, instead of using /*S:0 {#2.@Description}*/, it might work if you specify the exact path in your tag substitution rather than using a shortcut. Sometimes the system doesn't pick up the reference correctly if not given the full path, which could be causing the question marks. Try replacing "#2" with the exact location of your AOI, such as "[Packaging Line 1]MyP_PF52x".
I suspect it could be a scope issue. When you use specific tags like [Packaging Line 1]MyP_PF52x, they have the global scope and it's clearly defined where the PLC is looking for it. When you use local reference like #2, it depends on where it's being referenced. Ensure that your local tag #2 is correctly directed to [Packaging Line 1]MyP_PF52x. Check if the tag substitution is done in the same scope as the reference tag. Another reason can be the use of unsupported/invalid characters in the tag's description causing the question marks. Try simplifying the description to test. Hope this helps!
It sounds like you're on the right track, but the issue might stem from the way the tag reference for #2 is set up or how it's being interpreted in that context. Make sure that #2 is properly linked to the right path and that there aren’t any permissions or visibility settings affecting it. Sometimes, even a slight mismatch in the tag path can lead to those question marks. Double-check the overall configuration and try refreshing the connections to see if that resolves the issue!
It sounds like you're on the right track, but those question marks usually indicate that the system isn't able to resolve the tag you're trying to access. Double-check that #2 is correctly linked to [Packaging Line 1]MyP_PF52x, and ensure that the tag path is properly formatted without any spaces or typos. It could also help to verify that the AOI's description is indeed populated in the data source. Sometimes the tag may not be accessible at runtime, so make sure it’s active and has data when you're testing. Good luck!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: 1. How can I implement tag substitution for a faceplate in Factory Talk View Studio ME? - You can use tag substitution by specifying the tag path within appropriate syntax like /S:0 {[ControllerName]TagName}/.
Answer: - The issue of question marks appearing may be due to incorrect syntax or path referencing. Double-check the syntax and ensure the tag path is correctly specified.
Answer: - The issue might be related to how the tags are linked or the way the tag path is referenced. Verify that the tag path is accurately directed to the desired AOI description.
Answer: - To troubleshoot tag substitution errors, review the syntax used, confirm the tag path connections, and ensure that the referencing is correctly set up between the faceplate and the AOI description tag.
Answer: - When setting up tag substitution for faceplate descriptions, it is crucial to accurately reference the tag path, use the correct syntax, and ensure proper linking between the faceplate and the desired tag.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.