Troubleshooting
Why CitectSCADA cannot read MicroLogix data-table tags with ABCLX
Short answer
ABCLX talks to the Logix tag database, and a MicroLogix 1400 programmed with RSLogix 500 has none: its bits live in numbered data files, so an address like PROGRAM:MainProgram.B33{0} can never resolve. Change the I/O device to the ABMLXEIP driver, address the bit by file/element/bit as B33:0/0, and enter the controller's IP as a bare host address (192.168.0.100), never with a /24 suffix.
On this page
ABCLX is the wrong driver for a MicroLogix 1400, and no re-spelling of the address will change that: PROGRAM:MainProgram.B33{0} names a program-scoped array element in a Logix tag database, and a controller programmed with RSLogix 500 has no tag database — its bits live in numbered data files. Change the I/O device to the ABMLXEIP driver, take the operand from the online data table as B33:0/0 (file B33, element 0, bit 0), and enter the controller's IP as the bare host address 192.168.0.100, with no /24 suffix. One support question travels with the fix: the documented ABMLXEIP controller list names the MicroLogix 1000, 1100, 1200 and 1500, not the 1400, so prove one read-only bit before converting the application.
The address names memory this controller does not have #
The ABCLX documentation is organized around program scope, array tag addressing and mapping individual elements of an array — the concepts of the Logix tag database, where tags are created at program or controller level. That is the model the Logix 5000 I/O and Tag Data manual, 1756-PM004, documents. PROGRAM:MainProgram.B33{0} is that model in use: a program named MainProgram, a tag B33, element 0 of an array.
An RSLogix 500 project has none of it. MicroLogix data lives in numbered data files — B33 is binary file 33 — in one flat namespace, with no program scope and no array syntax. MainProgram.RSS is the offline project's filename on disk; it is not a network-addressable container. Renaming the variable, renaming the project, or loading another test program changes nothing, because the fault sits in the communication configuration, upstream of ladder logic. Stop editing the tag name.
Switch the I/O device to ABMLXEIP #
The published supported-controller list for the ABMLXEIP driver names the MicroLogix 1000, 1100, 1200 and 1500; the 1400 is not on it. The same documentation covers reaching the 1000, 1200 and 1500 through a 1761-NET Ethernet interface module, the family members without built-in Ethernet — the 1400 has its own port, so no module sits in this path. A community claim that the 1400 works is a report, not documentation, so treat the point as open: read the driver help installed with your runtime release, where supported lists can differ, and if the 1400 is absent there too, get the vendor's written confirmation naming the release before converting the whole application.
The fix does not wait on the paperwork, because the test is cheap. ABMLXEIP is the documented path in this SCADA to MicroLogix data tables over Ethernet, the EtherNet/IP service small Allen-Bradley controllers serve to clients, covered from the client side in how a SCADA client reads a small PLC over EtherNet/IP. Configure the board, the port, then the I/O device, in that order, and let the installed help define what belongs in each field — including the port's Special Opt field.
What each symptom tells you #
| Symptom you see | Cause to check first |
|---|---|
The digital variable with PROGRAM:MainProgram.B33{0} never reads |
Driver and memory model do not match the controller; ABCLX cannot resolve data-table memory. |
Renaming the variable or the .RSS project changes nothing |
HMI variable names and project filenames are not part of the controller's addressing. |
| A different downloaded test program fails the same way | The fault is in the communication setup, before ladder execution matters. |
| The driver connects, but one bit still fails | Recheck the file, element and bit against the online operand, and the variable's data type against it. |
| Every variable on the device flags at once | The I/O server is not reaching the controller: board, port or endpoint. |
| The screen shows 0 but the machine disagrees | The displayed value is initial or cached; judge the read by its quality, not the number. |
When every variable carries #COM or #BAD together, the connection itself is down and no address spelling will repair it; the same board-port-endpoint chain is walked when fixing an ABCLX #COM #BAD error on CitectSCADA 7.2.
Converting PROGRAM:MainProgram.B33{0} on a MicroLogix 1400 at 192.168.0.100 #
Inputs, each with its source:
- Runtime: CitectSCADA 7.4, digital variable tag (the project at hand).
- Controller: MicroLogix 1400, programmed in RSLogix 500 (the machine's program).
- Address supplied with the project:
PROGRAM:MainProgram.B33{0}. - Operand guessed from it:
B.33/0— punctuation too ambiguous to map to a file, element and bit; discard it. - Controller IP: 192.168.0.100 on a /24 network (the controller's network settings).
- Authoritative operand, read online from the B33 data table in RSLogix 500:
B33:0/0.
Rule in words: an address must name memory the controller actually has, in the syntax the installed driver documents — for a MicroLogix bit that is file, element and bit — and an endpoint field takes a host address only.
Written out:
- Delete
PROGRAM:MainProgram. The MicroLogix has one flat data-table namespace; there is no program scope to qualify. B33is binary data file 33.{0}is Logix array-index syntax; the target it pointed at is element 0 of that file.- The bit comes from the online operand: bit 0. The full location is
B33:0/0— file B33, element 0, bit 0 — entered in the file/element/bit form the ABMLXEIP help documents. - Endpoint:
192.168.0.100/24fuses a host address with a mask suffix. The Special Opt field takes the host address alone:192.168.0.100.
Result: one read-only digital variable on the ABMLXEIP I/O device, address B33:0/0, endpoint 192.168.0.100, that toggles in step with the ladder bit.
Decision: that one bit is the gate. If it reads live, convert the remaining tags file by file — after the 1400 is confirmed in your installed release's supported list or by the vendor in writing. If it shows #COM or #BAD, stop: the fault is board, port or endpoint, and no address will fix it.
Prove one read-only bit before converting tags #
- Back up the project and make the test variable read-only, so commissioning cannot command the machine.
- Go online with the controller in RSLogix 500 and read the operand from the data table; confirm
B33:0/0in the downloaded controller, not only in the offline file. - Configure the ABMLXEIP board, port and I/O device as the installed help specifies, with
192.168.0.100wherever the help puts the controller address. - Compile, run, and watch the variable and the driver diagnostics together.
- Toggle a designated test bit — never force a real output on a running machine just to test a display — and confirm the screen follows both transitions.
- Treat a displayed 0 as unproven until quality is good and the value tracks the online operand; in a controlled maintenance window, break the connection and confirm the system reports the loss instead of a stale value, the habit built in how to create a SCADA PLC communication alarm for link loss.
Questions asked
Does the ABMLXEIP driver support the MicroLogix 1400?
The published supported-controller list names the MicroLogix 1000, 1100, 1200 and 1500, and the 1400 is not on it, so its support is undocumented. Check the driver help installed with your runtime release, because supported lists change between releases; if the 1400 is still absent, ask the vendor for written confirmation naming the driver release and the controller series. A ten-minute one-bit read test settles the practical question either way.
Should the port's Special Opt field contain 192.168.0.100/24?
No. Enter the bare host address, 192.168.0.100. The /24 is not part of the address; it is shorthand for the subnet mask 255.255.255.0, which describes the network the controller sits on and belongs in the IP configuration of the runtime computer, not in the field where a driver looks up a controller. Append a suffix only if your installed driver help explicitly requests it.
What do #COM or #BAD flags on the variables mean?
They mean the I/O server is not communicating with the device at all, which puts the fault in the board, port or endpoint configuration, long before tag syntax matters. When every variable on an I/O device flags together, fix the connection first; no address spelling can repair an offline device. If one variable flags while its neighbors update, the fault is that single address: recheck the file, element and bit against the online operand.
Can I keep ABCLX and write the MicroLogix address in Logix syntax?
No. The syntax is not the problem; the memory model is. ABCLX resolves names in a Logix tag database with program scope and arrays, and the MicroLogix 1400 offers nothing for it to resolve against, because its data lives in fixed data tables. Rewriting B33:0/0 as PROGRAM:MainProgram.B33{0} builds an address for memory that does not exist on this controller. The real choices are the driver that speaks data tables, ABMLXEIP, or a migration to the Logix controller family, where such addresses are native.