IMDHMIControls LibraryShop main store

Explainer

Why a MicroLogix 1200 has no read-only password for techs

PLC programming Published 7 min read

Short answer

No. RSLogix 500 gives SLC 500 and MicroLogix controllers a single controller-level password, set in Controller Properties: whoever holds it can view, edit, and download, and whoever does not is locked out. Clear online edits per ladder file and treat the memory module as recovery — monitoring access must be solved procedurally, because no read-only login exists.

On this page
  1. Can a MicroLogix 1200 give a tech read-only access to the program?
  2. Where do I set the controller password in RSLogix 500?
  3. What does clearing online edits in a ladder file actually stop?
  4. Why do I remember passwording individual files in RSLogix 5?
  5. Does loading from the memory card at power-up protect the program?
  6. How do I give techs monitoring access without the programming software?
  7. Does any of this make the press safer?
  8. Questions asked

No — a MicroLogix 1200 cannot give a field technician read-only access, and no combination of settings changes that. RSLogix 500 implements exactly one controller-level password for SLC 500 and MicroLogix controllers: whoever holds it can view, edit online, and download, and whoever does not is locked out of monitoring too. The "see but not touch" login you want does not exist in this family. What you can do is put each real control where it belongs — password, per-file online edits, memory module — and solve monitoring access a different way.

Can a MicroLogix 1200 give a tech read-only access to the program? #

No — the access model has one level: RSLogix 500 holds a single controller password for the whole project, so a user who has it can view, edit online, and download while a user who does not have it cannot even monitor, and read-only exists nowhere between those two states.

Run the numbers on a finished press with illustrative round figures: 8 field techs who need to watch logic, 2 controls engineers who may change it. Hand the password to the techs for monitoring and you have 8 + 2 = 10 holders of the credential, every one of them able to edit and download, so "monitor but not modify" is met for 0 of the 8 techs. Withhold it, and monitoring is met for 0 of 8 as well, because a locked-out user sees nothing. Zero out of eight on both branches of the decision settles it: no distribution policy can create a tier the controller does not have. Stop searching the menus — the function is absent, not hidden.

Where do I set the controller password in RSLogix 500? #

In the RSLogix 500 project tree: Controller Properties, Passwords tab. That single tab is the entire access-control surface for the controller, and it applies to the project as a whole — there is no second screen where user roles might be hiding.

  1. Open the commissioned MicroLogix 1200 project in RSLogix 500.
  2. In the project tree, open Controller Properties and select the Passwords tab.
  3. Enter and confirm the password in the fields the installed software presents; do not reuse a credential from another machine.
  4. Save the project as the controlled master copy and record the password in the owner's engineering records — not on a label inside the panel door.
  5. Download through your normal commissioning process, then close RSLogix 500 and reconnect from a fresh session to verify the gate; an already-open authorized session proves nothing.

The saved master copy matters as much as the password: an unarchived program turns every later fault call into archaeology, which is what recovering alarm data from an undocumented SLC 5/04 looks like from the other end of a machine's life.

What does clearing online edits in a ladder file actually stop? #

Online edits for that one ladder file, nothing more. Each program file in RSLogix 500 has its own properties dialog with an online edits option; clearing it stops a connected user from making runtime edits to that file, and it does not stop a download that replaces the program.

Open the properties of every ladder file you want locked and clear the option there — it is deliberately per-file, so walk the file list instead of assuming one checkbox covers the program. Hold onto two limits. The setting narrows one modification path while a download still replaces the whole application, so test the download path separately before trusting it. And it carries an operational cost, because the same lock that stops a tech also stops a legitimate live correction during a breakdown. Decide in writing who may re-enable it in the master project and how that change gets approved.

Why do I remember passwording individual files in RSLogix 5? #

Because that capability is real, and it belongs to the Enhanced PLC-5, not to this controller. Enhanced PLC-5 processors programmed with RSLogix 5 support four access levels and per-file password protection, which is where memories of masked data tables come from.

RSLogix 500's access model for SLC and MicroLogix is one level; the Enhanced PLC-5's is four. The three tiers between full access and locked out — the band where a read-only technician account would live — are exactly what this platform lacks, so the memory is correct and the feature simply did not come across. If a plant standard demands per-class credentials, that requirement points at a controller migration, not at a setting you have not found yet.

Does loading from the memory card at power-up protect the program? #

No — it restores, it does not restrict: a memory module set to load at power-up puts a designated image back into the controller after a restart, and it never governs what a connected user can do while the machine runs, so it is recovery rather than access control.

It does buy one real defense: if someone downloads a changed program, the next restart can put the approved image back, so an unauthorized change does not survive a power cycle — protection against permanent drift, and none at all against the machine running wrong between the edit and the restart. Before enabling it, decide which revision is authoritative: the engineering archive, the memory module image, and the running controller must hold the same approved revision, or a routine restart silently undoes a legitimate service change. The load options and their exact names for your hardware are in the controller's user manual; set the power-up load, prove it with a controlled power cycle, and compare what comes back against the master. Ship the prototype with the card image matching the master exactly.

How do I give techs monitoring access without the programming software? #

Through a separate read-only surface plus procedure, because the controller cannot do it. Push the diagnostics the techs actually need — faults, states, counts, alarm history — onto an HMI or SCADA screen, and keep the RSLogix 500 password as an engineering credential held by people authorized to modify.

If the press has no monitoring station yet, mount an industrial panel PC for the SCADA client at the machine and give the techs their fault and state views there, with the programming software never installed on it. On the software side, get the driver addressing right the first time; a SCADA package that cannot see MicroLogix data-table tags is a known failure mode, and why CitectSCADA cannot read MicroLogix data-table tags with ABCLX walks through one such case. When a tech truly must watch rungs execute, make it a supervised session on the engineering laptop and log it — treat every password holder as a modifier, because that is what the controller makes them.

What each control on this platform actually buys:

Control What it stops What it does not stop
Controller password (Controller Properties, Passwords tab) All access by anyone without it, monitoring included Nothing from a holder: viewing, online edits, and download stay open
Online edits cleared, per ladder file Runtime edits to that one file A download that replaces the program; files left enabled
Memory module load at power-up Unauthorized changes surviving a restart Anything a connected user does between power-ups

Does any of this make the press safer? #

No — and this is the one place not to lean on the PLC at all: a standard MicroLogix 1200 is not a control-reliable device, and OSHA's press requirements expect hazardous motion to be removed by control-reliable external means or a safety-rated controller, never by application logic or its password.

The password protects the program; it protects nothing about the operator. On a press, the safety functions — stop, gate interlocks, light curtains, two-hand control — belong to hardware that removes control power independently of the PLC: redundant safety relays with monitored contacts, positively actuated switches and interlocks, or a safety-rated controller where the architecture calls for one. The requirement is control reliability: a single failure must not defeat the stop, which ordinary ladder logic cannot guarantee. Function-test every safety device and safety output after any download or memory-module restore before the machine makes product.

Questions asked

What happens if the MicroLogix 1200 password is lost?

The documented recovery clears controller memory: the program is erased, not unlocked, so treat the password as an access gate rather than encryption. Keep the archived project file and a memory module image so an erased controller is a restore job instead of a rewrite. Plan that recovery under the owner's change control before anyone needs it at 2 a.m.

Can I at least hide rungs or mask data table values from techs?

No. The single controller password is all-or-nothing at the project level: RSLogix 500 offers no rung hiding and no data masking on this family. Selective protection of individual data files is an Enhanced PLC-5 capability under RSLogix 5, which is why it seems familiar and why it is absent here.

Which RSLogix 500 release does a MicroLogix 1200 need?

The user manual specifies RSLogix 500 revision 4 or later to program the controller, and the reference manual 1762-RM001-EN-P asks for version 6.10.10 or higher to use all of its documented features. Run a current install regardless: release notes for RSLogix 500 12.00.01, dated December 2018, still mention trouble going online with a password-protected MicroLogix project.

Should I use the same password on every MicroLogix in the plant?

You can, because each project carries its own controller password, but do not. One shared password is one credential: whoever holds it holds full access to every controller that uses it, and a single leak retires the lot. Give each machine its own password and record them in the controlled engineering archive with the master project files.

Keep reading

  • Troubleshooting

    Recovering alarm data from an undocumented SLC 5/04

    An upload from an SLC 5/04 returns the running logic and data files but no symbols or descriptions, because the processor never stores them. Recover alarm meaning from the operator interface tag database, any older backup and the electrical drawings, trace each alarm backward through the logic, then map only explained addresses into the gateway.

    PLC programming

  • Troubleshooting

    Why only Studio 5000 programs a ControlLogix 5571

    A ControlLogix 5571 is programmed only with Studio 5000 Logix Designer (RSLogix 5000 in older releases) over an RSLinx or FactoryTalk Linx driver path. The USB port feeds that driver, not a terminal: PuTTY, minicom or picocom never reach a prompt on this VxWorks-based runtime. A controller missing from a device list means you check installed Studio 5000 revisions and the communications path first, and you flash firmware only to match an installed release's major revision — never to cure a browse fault.

    PLC programming

  • Troubleshooting

    Why Modbus cannot transfer a PLC ladder program over TCP

    No Modbus address reaches ladder memory: the application protocol defines four data tables — coils, discrete inputs, input registers, holding registers — and program storage is not in any of them. Swapping RTU for TCP changes transport, not protocol. On DirectLogic PLCs the program moves only over K-Sequence or DirectNET through the vendor's programming tools; Modbus stays for mapped user data.

    PLC programming