Arlen Jacobs

1) Yes, there is a flag (one shot) when the file write is done; use the handshake connection. 2) Yes, you can manually log data to the file; use the trigger connection. 3) The handshake connection tells you when the file write has completed. It is an odd way for it to work, but when you use the handshake the system will set that connection to 1 and then clear to 0 after the file write is complete. It will also clear the "trigger" connection to 0. I think you can get it to work the way you want; log a string comment one time. - have a push button to manually trigger the data store write; after a comment is typed in. - assign a global macro to clear the comments string; use the same tag assigned to the handshake connection to also trigger the global macro. Give it a shot and post back on how you got it working.  

You can use one ingredient as a string and store the name there.

Macros let you change tag values, based on an event. It is a simple version of scripting. You create the macro files from the explorer window, then you assign them to an event somewhere else. These events can be assigned a macro: user login or logout display open or close based on an expression, when it changes from zero to non-zero (Remote macro in global connections) a user pushes a Macro push button on a graphicAssign a tag on the left side of a macro line and then assign a math expression on the right side. tag <---- math expression Whatever the right side evaluates to will be sent to the tag on the left side. You can use/assign strings and a few other items, but that is quite limited. Things to note The lines within a macro are not guaranteed to execute in order (ex. not always line 1, then 2, then 3...etc.). As an example, you may have line 23 complete before line 15 does. Macro files will be completed in order. So, if you trigger macro 1 it will execute before macro 2 starts. Macro lines within the same file are executed in blocks of 50. The first 50 lines are executed and completed before the next block of 50 lines are executed (should you actually have a macro with that many lines).

Can you use: #100 = [PLC] and #100 = [PLC]Program:ComponentX.

Given those two choices I'd go with Omron. I like where they are going for machine builders; at least what they are saying and put into the software. It pulls together motion, PLC, drives, safety and HMI. Sysmac Studio looks promising, but new (bugs? or lack of features?). You can get a trial copy and take a look. You should do that for Keyence as well. Definitely, look at tech support and local support (distributor, field services). You already gave Omron a +1 so that seems like your standard to beat.

Have you tried the security expression CurrentUserHasCode()? You can use that with visibility animation to hide buttons that you want secured (ex. change value, GoTo screen). Put your login GoTo button behind the "secured" button. Users hate it when buttons disappear. If you do hide buttons, make sure that you put another "unsecured" button immediately behind it. That way if the user does not have security access, there is always something there.

From an end-user perspective (or systems integrator), I love the "idea". As an OEM, I have mixed opinions. What I like is that it gives some common ground between different machines on a line. If they say "the whole line was built with PackML" right away it gives me a picture of what to expect. Basically, it saves time trying to learn how the machine works through its states. I don't remember seeing an end-user with 100% of their machines from the same vendor; which means each spaghetti coded machine is a different invention to figure out. For OEMs, I've seen it help where they had: to create ANY standard of programming for the first time (small # of engineers)no chance of agreeing on their own standard (large # of engineers)to sell their machines as better than competitors' (ex. this helps you end-user)But it doesn't mean that PackML is the best for that particular OEM. So they still change, add, delete guidelines as it suites them. I have seen very few machines using/claiming PackML (out of 1,000's). Unless more end-users demand PackML it will stay in limited use with machine builders. It's an end-user benefit, from my experience. Maybe others have seen different in the field?

Not easily, no. Each alarm trigger has an "optional trigger connection" that can write back to the controller. You would want to use the ACK connection. Whenever that alarm trigger is acknowledged (at that particular PanelView) the PanelView will send a non-zero value to the controller. Ex. writes 1 to the controller. You would need to setup the ACK for each of your alarm triggers, then have the controller do the logic if all of the alarms have been acknowledged. Those tag connections in the Alarm List that you found are read only; they are only used to change the display of the Alarm List. So, those will not help you in this case. Try it out just using memory tags in the PanelView and you'll figure out how it works.

(1) Make sure you have the {Stretcher}Pressure_Transducer tag added to the data log model (Connections tab of the trend) (2) Enable & select the Pressure_Trend model in the Startup settings of your project. In FTView Studio, the Startup settings are in the project explorer tree. (3) assign the data log to the trend, on the pens tab; as you have already done. It doesn't make sense, but you need to do all three to get the data log working.

PanelView Plus is the older hardware and supports up to version 5.x of the software. It is discontinued and no longer available for new sales. PanelView Plus 6 is newer and supports the latest version 8 of the software. PanelView Plus 7 just released this year and it also supports the latest version 8 of the software. The big difference in the PanelView Plus 6 is the extra memory and speed. If you had large projects, then you will notice screen changes are faster.

You would have to experiment with the ME Program Launcher activeX control. Set that up to open your web browser (IE, Chrome, Firefox, ?) and use the command parameter for the web address. The exact syntax for the command parameter is what you'll have to figure out by testing it. Use a momentary push button to trigger the Program Launcher to open your web browser.

I would start with (2) first; change to widescreen displays. Then work on (1) as time goes on; update the screens per High Performance HMI Handbook. The FTView screen do not scale well. It is best to manually resize them in FTView Studio for the widescreen display. Going from a standard display (4:3 ratio) to a widescreen (16:9 ratio) always has problems for any HMI. Either you stretch out the graphics or you have blank spots on the ends (like your t.v. does for "old" movies and shows).

Jeremy, what did you find out? Is there a good way to install an HMI into C1D2, outdoor and freezing temps?

np. Post back if you find any tips or gotchas.

There is an expression that will give you the name of the current language (string data type) CurrentLanguage( )Use a macro to copy that expression value to a string tag in the controller, process it there. How you trigger that macro could be done a few ways. Using the global connection "Remote Macro" is probably the easiest. Ex. when the current language is different than the last language run Macro1.

I don't think you can do this & use the PanelView security. You can use the auto-logout feature to change displays after 15 minutes of inactivity when in manual mode; & do nothing when in auto mode. But it would always log out the PanelView user. You would use the auto-logout to open a pop-up display (100x100 and off screen at x -100 y 100). That pop-up display can run a startup macro which could check for manual/auto. Based on that the macro could use the Remote Display Number feature to change the main replace screen to the real Login screen. Or do nothing if in auto.The problem with that idea is that it will log out the current user (PanelView FactoryTalk) after 15 minutes, just to run the popup and macro. So you would have to use some other method for users/security.

Take a look at AIS Pro and give them a call directly. http://www.aispro.com/ I have not used them personally, but they specialize in extreme & outdoor conditions. Your software choices for an operator panel are Wonderware InTouch Compact Edition, InduSoft CEView or Progea Movicon™ CE. Of course, you could go with an Industrial Computer and choose your favourite HMI.

FWIW one of the authors for the "High Performance HMI" book is also on the official list for the ISA101 standard. Ian Nimmo https://www.isa.org/templates/three-column.aspx?pageid=124562

"High Performance HMI Handbook" by PAS is a book that talks about WHY and HOW to design a good HMI. It is an easy and more enjoyable read. If you want a better understanding into HMI design then get this book http://www.pas.com/Technical-Books/High-Performance-HMI-Handbook.aspx "Effective Console Operator HMI Design Practices" by ASM is more of a guidelines & standards. It has a lot detail, but reads very dry. If you want a list of guidelines & recommendations, less of the why, then this book is good. http://www.asmconsortium.net/deployment/guidelines/Pages/default.aspx Note, those are direct links the author websites. You can buy either on Amazon as well.

I would guess you hear something public close to the end of this year. Or, maybe someone going to RSTechEd this year will hear an update? Rockwell's big show of the year is in November (AutomationFair), and they seem to announce or release new products around then. Sometimes they announce in June at the USA RSTechEd. If you haven't heard anything by now, then those two dates are the most likely.

yeah, the replacement is 2711P-T7C4D8 If you are using RIO or DNet communications, then that catalog will not work.

Yes, the PanelView Plus compact will work with a PLC 5 on Ethernet. It has the same communications as the PanelView Plus, except only 1 PLC can be setup.

If you just want the alarms file, look under the folder with your project name and then the "M_Alarms" folder. You can just copy the *.mal file onto your new laptop, same folder location. Going from memory, and very limited testing of v.8... Project (Application) files Your project files will be stored in this directory: C:\Users\Public\Documents\RSView Enterprise\ME\HMI Projects Confusion tip: FTView studio calls that an "application", but older versions and the file directory itself calls it a "project". V.7 and earlier You would also need to copy the *.RNAD file and the folder from this directory: C:\Users\All Users\Rockwell\RNAServer\Local Those files tell FTView Studio that you have a project in the other folder. Without the RNAD file the project will not show up in the FTView Studio "Open project" dialog. There are also some RSLinx files, but I don't recall exactly where those are. I just recreate them in FTView Studio. V.8 and later All of the needed files are stored inside the project folder. Just having the project folder in the right location makes it show up in FTView Studio. That change in v8 fixes the issue of losing your security accounts when moving a project from one computer to another; also fixes losing your security accounts when you restore a different project.

Rockwell has a product called FT ViewPoint to do just that. It is not free, but it will take your existing screens and make them webpage accessible (read, or read/write). If you are using PV+ it includes FT ViewPoint for free. But the caution there is the software runs on your PV+ and uses its resources. If you have busy screens with a lot of data you may have slower updates on the webpage. FT ViewPoint helps with a major concern, user security. You can explicitly allow users access to view data and it can tie into your existing user security (Windows, or just FT Security). A low-tech option is to host a VNC server on some client computers, and only allow view access. But, security is low and you can only see what the client computer is currently showing.

There is a lot to rant about for the PVP+ software. Easy setup, pain free, quick to learn, user friendly are not words I would use to describe it. But it is an advanced product with a lot of features unmatched in any other touchscreen; same for price. For whatever reason you end up working with one, I would recommend these as mandatory (for any automation software really): 1) Use a "clean" install of Windows Basically, install Windows onto a PC for the first time and then apply all the Windows updates. Do nothing else. NOW you are ready to install FTView Studio. Don't install anything else, except MS Office. 2) Use FTView Studio version 8 or higher There are a lot of features in FTView Studio and it has taken them a long time to make them better. If you use any version less than 8 you are going to hit many of the pains that used to be there (security, installs, activeX, communications setup). My general rule is a minimum version 5 or five years on the market for any automation software. Otherwise you run the risk of too many bugs, quirks, poorly thought out or incomplete features. 3) Use a virtual PC VMware ($) or use Oracle Virtual Box (free). You still need to buy a Windows license. That allows you to setup the software on a clean install of Windows and then save that point in time (snapshot). 4) Use snapshots in the Virtual PC If you feel adventurous after creating a saved snapshot, install other software. Use the PC however you want, and when you are done with the click of a button it goes right back to that saved, known good state. 5) Use a Logix PLC Yes, you can talk to other controllers (PLC 5, SLC, MicroLogix, Simatic, Modicon, any major controller you can name) but it is not ideal. PVP+ was designed for Logix and if you don't use that controller then you take away most of the benefits of the PVP+. Same goes for any other PLC. In general use the HMI from the company that designed the PLC, unless you have solid reasons not to. No one would say a PVP+ has a fast startup, is cheap, or pain free. But sometimes you need a Canyonero and nothing else will do.