Securing RSLogix5000 software access

[ARYankee 0]

I am currently working on getting access to RSLogix5000 for our electricians at our plant. All they need to be able to do is pull up the appropriate program for the processor, connect to said processor, and be able to search. I don't want them to change any programming, they may have to force some bits though. I have never had to do this before and I would really like to get it right on the first try.

[Cookie Monster 2]

You can implement factory talk security and require a login for each specific user, you can select options that will require a successful logon before even opening the software. I would recommend starting out by researching it Edited 15 Feb 2014 by Cookie Monster

[ARYankee 0]

Thank you. I started to research using Factory Talk and I think that is the way that I will go.

[daba 4]

Forcing I/O is, without doubt, a much more "dangerous" situation than making program edits. It's a sledgehammer By the way, you can't force "bits", you can only force I/O tag data. Personally speaking, I would prefer giving people full access, allowing program changes (online edits), etc., over just allowing them to view the code and apply forces. I have to say that in over 30 years in process control, and have commissioned many "large plant" processes, I have never used, or needed to use, I/O forcing on a live system (i.e. the plant is running product). Several of the customers I have worked for have even "banned" the use of forces by their maint techs, because of the dangers involved. Edited 5 Mar 2014 by daba