Use Hashtag (#) in FactoryTalk Text Box

I am creating a text box for a screen that has 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

Problem is, FactoryTalk thinks the #1, #2, #3 are for parameter files, when I really mean is for Number (#), not Parameter.

Anyone know the right way for me to use a hashtag symbol in a text box as a text object and not an instruction for FactoryTalk to do something else?

http://www.plctalk.net/qanda/showthread.php?t=94578

http://www.plctalk.net/qanda/showthread.php?t=83001

The above threads may help you out.
Regards,

Are you using FTView ME or SE? What version?

JJH said:

I am creating a text box...

Click to expand...

Are you using a Text object or another object?

JJH said:

... for a screen that has the following layout:

/*N:2 {::[MACHINE]Program:UN_Machine.EventSlot1} NOFILL DP:0*/
#1
#2
#3

Click to expand...

I tested a similar code in a FTVME screen and it works correctly (#1, #2, #3 are printed literally on screen).

Could you post a capture of the object's properties?

FTVME Hashtag

Attached is a screenshot of the property.

I'm just using a basic text object as I often do displays with that and just have the variables in there. Thought I could do the same thing, but I forgot the # symbol is interpreted as a parameter file in FTV, which is not what I want it for.

Ok. My first test was in FTVME 6.10. Now I was able to reproduce the issue on FTVME 8.10.

I think there are some workarounds:

a) Create a string tag in HMI Tags and use it instead of the hashtag. For example: if the tag's name is hashtag (type: string, length: 1, data source type: memory, initial valur: #), you can use it the Text object:

b) Add and space between the hashtag and the number

If I can think of another solution, I'll post it.

Another solution without creating an HMI tag: