In Today's article I discuss why your FactoryTalk View Studio Site Edition Parameter Files may not work.
While I was recording lessons for my View Studio Site Edition course, “ViewSE Basics,” I ran into a new issue with Parameter Files.
I was demonstrating how your can use the same Graphic Displays with multiple different PLCs and Tag sets, when I found most of my Parameter Files were not working.
After reviewing the files, I found that the first line of each Parameter File had this extra line of text: @!=1
Then I ran the application again, and this time I found that all of my Parameter Files worked.
Unsure if this was just a v9 bug, I opened View Studio v10, v8 and v7, and in each of those I created a new Test application as well as a new Parameter File.
Surprisingly, I found the same erroneous first line of text was present in the Parameter Files I created in v10, v8, and v7.
So while removing the “@!=1” did solve the issue I ran into with v9, I still have no idea why Rockwell would add this first line of text to all new Parameter Files in so many different versions.
In my experience, it's unlike Rockwell to ship multiple versions of a software product with what appears to be a feature breaking bug?
PS – If you have any experience or information about this, I'd love to hear from you! Just click on the “post a comment or question” link below to leave a comment.
UPDATE: A kind reader informed me that the !@=1 disables inline comments.
In my course I use a lot of inline comments, and with the !@=1 present ViewSE was interpreting them as part of the command string.
Not sure who needs to use the “!” symbol in their commands, but since I want to include inline comments for my students, I'll continue to remove the !@=1 from my parameter files so they'll work 🙂
To watch a video demonstration of the above, check out Episode 47 of The Automation Minute Season 4 below:
If you found this article helpful, please share it with your colleagues on LinkedIn, Facebook, Twitter or Goggle Plus!
And if you know anyone who would benefit from Allen-Bradley PLC, HMI, or SCADA training, please let them know about my affordable courses over at TheAutomation School.
You can also share your own thoughts and opinions on this subject by clicking on the “post a comment or question” link below.
Enjoy the benefits of membership! Insider news, rewards, & more: Patreon.com/automation
If you enjoyed my article, you may like my courses at TheAutomationSchool.com
Have a question on this topic? Click here to scroll down to the comment link
Have a news tip? Share it with us here
Latest posts by Shawn Tierney (see all)
- RSView32 Direct Drivers to MicroLogix on DH485, PLC5 via DF1 (Early Access) - April 2, 2020
- RSView32 to SLC-5/04 & PLC-5 over DH Plus via Ethernet and 1756 Gateway (S36) - March 27, 2020
- Mitsubishi VFD Product Overview (P51) - March 26, 2020
Click HERE to scroll down to view or leave comments
- I have a similar problem with parameter files which is driving me nuts. I am converting an application from RSView32 to FTV SE 10. I've imported the project and largely it's ok. I have a number of screens which are passed parameter files when called. The parameters displaying values in the PLC all appear to be working ok but I have a number of pushbuttons on the screen and command parameters for these are also passed over.
So for example I have a line #22=Display Vent Cells /pVC01param which is being seen by the system as a macro rather than recognising Display as a command. The line #2=coolant\coolant_auto_hours is recognised as a tag and works just fine.
I am currently looking through the manual to see if there has been some change to the syntax of commands in the parameter file.
I also noticed the !@=1 line at the start of the parameter file created by the system. I don't have that in my files so I added it to see if it made any difference. Didn't appear to but it was only a cursory check.
If you've got any ideas it would be much appreciated!Good morning Steve,
You'll find ViewSE requires screen names containing spaces to be in quotes.
What probably is happening is the command Display Vent is being issued, and then the command Cells is being issued.
You can check your diagnostic log to be sure, but you may want to make a backup of the project and then find and replace all instances of Display Vent Cells with Display "Vent Cells"
As far as the
Hope this helps,
Instructor, ViewSE Basics