Created Date: August 23,2010

Created by: Steve Bailey

In essence you have to "log in " every time you use an object protected by a password. Touch the object and the password prompt pops up. C-More passwords apply to individual objects, not to sessions.

The only way I can think of to make a C-More behave the way you appear to want would be to have the C-more power up to a main screen and have password protected navigation buttons to a different set of screens for each password. Once you 've entered the password and the C-More shows the new screen, none of the objects on that screen would use passwords. You would also need to revert to the main screen after an inactivity timeout period.

Created Date: August 24,2010

Created by: Steve Bailey

In my opinion passwords are of limited utility. I 've lost count of the number of systems I 've seen where the password is written down for anybody to see somewhere close to the HMI panel.

Remember the dear, departed days when every component on a control panel was hardwired? Somehow we managed to operate our production lines without limiting access to the high priesthood.

Furthermore, I suggest you experiment a little with the simulation to get a feel for how it works. Each option gives you the ability to use passwords or not. You need only apply passwords to the areas where you feel they 're necessary. And, as I mentioned, you could put all of those adjustments on a single screen and password protect access to the screen.

One of the biggest hurdles to learning how to work with a new brand is overcoming the desire to make it behave just like the brand you already know.

Created Date: August 24,2010

Created by: KPrice

Mike6158, you do not have to enter a password every time you want to change a setpoint. You can create a button to change to a screen. This button can require a password. This screen-change, or "log-in " can be logged to an event log, if needed. This protected screen can include screen-change buttons to allow access to screens with all your needed setpoints or data. These screen-change buttons can be created without passwords. So, once you entered your password to get to the "protected screens ", you do not have to enter a password every time you want to change a setpoint. You can include copies of "operator " screens to allow you to view the operator data without leaving the "protected screens ". This way you can return to your setpoint screen without having to re-enter your password. To "log-out ", you can create a button to change to the "home screen ". This screen-change, or "log-out " can also be logged to an event log, if needed.

Hope this helps.

Created Date: August 24,2010

Created by: jwbaker3

The way I do this is I have a passworded button on the screen that turns on a "c " output in the plc that is set when I press the button and is reset by a timer in the logic. When the c output is on I make the adjustment options on the screen visible, when the c output is off I hide the adjustments. This way I can have the adjustments (setpoints, etc.) on until the timer times out and no other passwords needed. I use the hidden buttons a lot, I make functions only show on the screen when the logic allows the function to work. If the program need operator input/setup before the function will work I have a warning on the screen telling the operator to complete the input/setup and when its is done the same logic turns off the warning and turns on the buttons/inputs.

JWB

Created Date: August 24,2010

Created by: Mike6158

The way I do this is I have a passworded button on the screen that turns on a "c " output in the plc that is set when I press the button and is reset by a timer in the logic. When the c output is on I make the adjustment options on the screen visible, when the c output is off I hide the adjustments. This way I can have the adjustments (setpoints, etc.) on until the timer times out and no other passwords needed. I use the hidden buttons a lot, I make functions only show on the screen when the logic allows the function to work. If the program need operator input/setup before the function will work I have a warning on the screen telling the operator to complete the input/setup and when its is done the same logic turns off the warning and turns on the buttons/inputs.

JWB

I like this method a lot. It's clean and it will "look " like what they are already used to. Thanks a ton!

Created Date: August 23,2010

Created by: Mike6158

I 've been working on a little C-More panel app for a customer and I'm down to the point where I need to add Login and Logout buttons. I can't find them. I 've built a lot of AB Panelview Plus apps and the Login / Logout buttons are "canned " selections in the software.

(1) How do I login and logout?

(2) Is there a way to set the login to time out after x minutes of no screen input?

It doesn't make sense to make password protection available if you can't log in and out...