Help - Search - Members - Calendar
Full Version: CX_Designer/NS Screen
Forums.MrPLC.com > PLCs and Supporting Devices > Omron > CX-Designer
BITS N BYTES
While working on a CX-Designer project the Level1 Password and Keypad suddenly started to malfunction.
When entering the Level1 parrword the NS Screen popsup a message invalid password even though I know for sure the password matches the one set in the Project.
Also the keypad popup screen will no longer acept data input,

What is going on here??
Worked fine yesterday but today it doesn't work!!

Do I need to upload firmware again?
Why did this happen??

ranting.gif
PdL
QUOTE(BITS N BYTES @ Jul 25 2007, 02:03 AM) [snapback]56936[/snapback]
While working on a CX-Designer project the Level1 Password and Keypad suddenly started to malfunction.
When entering the Level1 parrword the NS Screen popsup a message invalid password even though I know for sure the password matches the one set in the Project.
Also the keypad popup screen will no longer acept data input,

What is going on here??
Worked fine yesterday but today it doesn't work!!

Do I need to upload firmware again?
Why did this happen??

ranting.gif


It indeed sounds weird, and if you can't reproduce it it will be difficult to explain, but perhaps a little background info on the password level system will make you understand what is happening.
The following questions might explain the behaviour.
  • Although you enter the correct password for level 1 on the object you operate, are you sure the object has level 1 configured at the security properties ?
  • With the keypad not accepting data input do you mean it pops up and you can't enter any data or doesn't it pop up at all ? (the last would be the case if you use the password level function mode and you are already authenticated for this objects level or a higher level)
  • Which password function have you set in PT > Password setting menu ?
With the top "password" function, privileges are exclusive, meaning each object operation requires that only the particular security level password is entered which matches the level set in the objects Password properties.
I.E. you have 2 objects, one with a level 3 security and one with a level 2 security.
If you operate the level 3 object, you need to enter the level 3 password. If you move on to operate the levle 2 object, you need to enter the level 2 password.

With the bottom "password with level" function, privileges are hierarchical, meaning each object operation requires the password which matches the objects security level is entered, OR any lower higher level. You kind of "log in" on the security level when you enter a certian password, after which all objects which are on the same or lower security level can be operated without having to re-enter a password.
I.E. you have 2 objects, one with a level 3 security and one with a level 2 security.
If you operate the level 3 object, you need to enter the level 3 password. After this you can operate the level 2 object without entering a password.

Note only what in my opinion is a bug with the password with level function: if you operate an object for the first time, you always have to enter the password that matches the security level which is set for that particular object. For instance when you operate a level 3 object for the first time, you cannot enter a level 4 password, you must enter the level 3 password. But once you have operated an object of level 4 and thus are "logged in" on level 4, you can operate the level 3 object without problems.

The last function makes it possible to create a general global "login/logout" system, by using a global "login at level #" button for each level which only has the security level configured so that the password entry keypad pops up when pressed, a "logout" button which has the system function "authentication cancelled" set.
You can use system memory adresses $SW39 to detect authentication level and a simple global script which runs on the system memory pulse like

CODE
IF ($W39==0);
STRW2M($W300,"Guest");
ELSEIF ($W39==1);
STRW2M($W300,"Level 1");
ELSEIF ($W39==2);
STRW2M($W300,"Level 2");
ELSEIF ($W39==3);
STRW2M($W300,"Level 3");
ENDIF;


to display the current authentication level with a "string display/input" object.
Now a user can "log in" on level 3 and operate all objects throughout the project with level 3 or lower set as security level.

Hope this helps.
BITS N BYTES
Hi Pim,
thanks fo the detailed description on password levels.



Founds my problem today where a RELEASEFOCUS(); macro was active when tring to access an object requiring a password. Because focus was released the password keypad was not transferring temporary input data to the password.



smile.gif





This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2010 Invision Power Services, Inc.