I am in the process of designing a text box for a screen that features the following layout: /*N:2 {::[MACHINE]Program:UN_Machine.EventSlot1} NOFILL DP:0*/#1#2#3 /*N:2 {::[MACHINE]Program:UN_Machine.EventSlot2} NOFILL DP:0*/#1#2#3 /*N:2 {::[MACHINE]Program:UN_Machine.EventSlot3} NOFILL DP:0*/#1#2#3 /*N:2 {::[MACHINE]Program:UN_Machine.EventSlot4} NOFILL DP:0 */#1#2#3. The challenge I’m encountering is that FactoryTalk interprets the #1, #2, and #3 as references for parameter files, but my intention is to use them as simple numerical indicators. Does anyone have advice on how to properly incorporate the hashtag symbol in a text box as a text object, so that it is not misconstrued as an instruction by FactoryTalk?
For valuable insights, you might want to explore the following threads: [PLC Talk Discussion 1](http://www.plctalk.net/qanda/showthread.php?t=94578) and [PLC Talk Discussion 2](http://www.plctalk.net/qanda/showthread.php?t=83001). These resources could provide the assistance you're looking for. Best regards!
Are you currently using FTView ME or SE? If so, which version do you have? JJH mentioned: "I am in the process of creating a text box..." Click to expand for more details. Are you working with a Text object or another type of object? JJH continued: "...for a screen designed with the following layout: /*N:2 {::[MACHINE]Program:UN_Machine.EventSlot1} NOFILL DP:0*/ #1#2#3." Click to expand for additional context. I conducted a test using a similar code within an FTView ME screen, and it produced the expected outcome, displaying #1, #2, and #3 literally on the screen. Could you please share a screenshot of the object's properties to assist with troubleshooting?
FTVME HashtagAttached features a screenshot of the property in question. I typically utilize a simple text object for displaying information, incorporating various variables as needed. I intended to apply the same method here, but I overlooked the fact that the # symbol is interpreted as a parameter file in FTV, which doesn't align with my intent.
Certainly! Here's a rephrased version of your text that enhances its quality, uniqueness, and SEO-friendliness: --- I recently conducted a test using FTVME version 6.10 and successfully replicated the issue on FTVME version 8.10. I've identified a couple of effective workarounds that may help resolve this problem: a) **Utilize a String Tag in HMI**: Instead of using the hashtag directly, create a string tag within your HMI Tags. For instance, if you set up a tag named "hashtag" (type: string, length: 1, data source type: memory, initial value: #), you can reference it in your Text object like this: ``` /*N:5 Variable1 NOFILL DP:0*/ /*S:1 hashtag*/1 /*S:1 hashtag*/2 /*S:1 hashtag*/3 /*N:5 Variable3 NOFILL DP:0*/ ``` b) **Insert a Space Between the Hashtag and the Number**: Another simple workaround is to add a space between the hashtag and the number. You can format your code as follows: ``` /*N:5 Variable1 NOFILL DP:0*/ # 1 # 2 # 3 ``` If I come up with additional solutions, I will be sure to share them. --- This revision incorporates keywords and phrases that enhance searchability, ensuring that it communicates the same core message while improving engagement.
An alternative approach that does not involve the creation of an HMI tag is as follows: Code: you receive /*LS1{#}*/2 --------> #2 This method allows for efficient system management without the need for additional HMI tag setups.
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.