Troubleshooting
Reading M580 I/O in Plant SCADA without mapped memory addresses
Short answer
Bad I/O on %Q1.1.20 means Plant SCADA is reading a topological M580 channel address that no driver can resolve as a register, and no Modbus table exists to look up. Serve the points through the OFS gateway using PLC tag names, with an XVM export now and the Data Dictionary permanently, and add the missing variables by online change so the 24/7 line never stops.
On this page
- Why a topological address reads as Bad I/O
- Rule out the link before touching addresses
- Four routes to the channels
- Test the topological address in OFS first
- Add the missing variables by online change
- Short-term: serve tags from an XVM export
- Permanent: enable the Data Dictionary
- Bind the tags in Plant SCADA
- What each symptom points to
- Questions asked
Bad I/O on %Q1.1.20 is an addressing fault, not a network fault. The tag names an M580 output channel by its position in the rack — a topological address — and the program never mapped that channel to a located memory word such as %M or %MW, so the SCADA read has nothing to resolve and no Modbus table exists to look up. The supported fix is the OFS gateway (OPC Factory Server) serving PLC tag names to Plant SCADA's OFSOPC driver: an XVM export works today, the Data Dictionary is the permanent form, and variables for the missing channels are added by online change without stopping the 24/7 line.
Why a topological address reads as Bad I/O #
On the M580, %I and %Q channel names can be topological: the numbers carry a position, not a memory offset. A located reference — %M for bits, %MW for words — points into controller memory, which is what a register-style read resolves. Type %Q1.1.20 into a SCADA variable and the read travels tag to driver to controller, then dies at the last hop: the channel exists physically, but no located variable stands for it. The driver reports the point as Bad I/O and the operator screen shows it invalid or hash-filled. Schneider has been moving the M580 platform away from topological addressing, so treat it as something to test once, not something to build on.
Rule out the link before touching addresses #
If any other tag on the same M580 reads good, the TCP/IP path is healthy and only the definitions are wrong. Check it with the tag counts once:
Take an example project polling 120 tags on the M580, where 116 read good and 4 show Bad I/O. 116 + 4 = 120, so every configured point reports and the device is reachable. 4 ÷ 120 is about 3 % of tags failing, while a dead Ethernet path fails 100 % of them. Decision: leave the network alone and fix the four definitions. When every tag on the device goes bad together, that is link loss instead — set up a SCADA PLC communication alarm for link loss and chase the connection, not the addresses.
Four routes to the channels #
| Route | PLC change | Reaches channels with no variable | Survives PLC tag edits | Where it fits |
|---|---|---|---|---|
| A. Type the topological address in OFS | None | Yes | Not applicable | First test; costs nothing |
| B. Export an XVM file and load it in OFS | Export only | No | No; re-export after every edit | Short-term delivery |
| C. Enable the Data Dictionary in the PLC | Yes, a download | No | Yes, automatic | Permanent |
| D. Online change to add variables, then B or C | Adds declarations, program keeps running | Creates them | Through B or C | Naming the unnamed points |
Decision: test A first. If the quality is bad, use D to give the points variables, run on B, and move to C at the next scheduled download. B and C can only serve what exists in the project — neither exposes a channel that has no variable.
Test the topological address in OFS first #
Plant SCADA delivers OFS with it, the same build as the standalone server — V3.63SP3 was the version noted as latest when this was reported — and the installer enables its license through the Plant SCADA serial number and product code. OFS runs as a Windows service on a node of its own between the SCADA server and the controller; for a new gateway node, an industrial mini PC beside the controller is the usual fit. Schneider's support site publishes a step-by-step OFS-to-M580 setup guide (FAQ FA407730) with the exact field names per version.
Create the device alias with the M580's IP address, then read %Q1.1.20 in the OFS test client. Good quality means the point is reachable with no PLC work: bind it and finish. Bad quality means this controller does not serve topological access — stop there, because retyping the address in Plant SCADA cannot change what the server resolves, and the platform is moving off that mode anyway.
Add the missing variables by online change #
Online change adds declarations to the running project. Work connected, in this order:
- Take a project backup before anything else.
- Connect to the PLC from the programming software (Unity Pro or Control Expert, whichever matches the project); do not edit offline and connect afterwards.
- Build while connected. The status bar at the bottom of the screen must read "equal" and "built" before you add anything.
- Add variables bound to the channels SCADA needs, then transfer by online change.
- Confirm the status bar returns to "equal".
Never build while disconnected: that clears online change, the status shows "not equal", and the only way back is restoring a backup or uploading the project from the PLC. On a live line that is the one real downtime risk in this job, which is why the backup comes first.
Short-term: serve tags from an XVM export #
Export the variable tag database from the programming software to an XVM file, set that file as the tag source in the OFS device configuration, then save, start the server and confirm the alias connects. The cost is maintenance: every PLC tag edit leaves the file stale, and a stale XVM returns Bad quality on renamed or moved variables, which reads like a network fault but is not one. Each reload can also briefly interrupt communication. While this route carries the SCADA, the working routine is the one for handling topological address changes in a Unity OFS tag export: edit, re-export, copy to the OFS node, reload.
Permanent: enable the Data Dictionary #
The Data Dictionary is a PLC-side project setting: it places the variable tag library — variables with their EDT and DDT types — into controller memory, where OFS reads it directly instead of from a file. Enable it, download the project in a scheduled window, and on the OFS alias enable the "Online Changes" capability so tag edits reach OFS without file handling. From then on, a variable added by online change appears to OFS on its own and the XVM cycle stops. Resolving M580 OFS variable address drift with the Data Dictionary comes down to that one setting plus the download that activates it.
Bind the tags in Plant SCADA #
The OFSOPC driver reaches OFS over OPC DA. Add the board, port and I/O device for OFSOPC, point the device at the OFS alias, and create variable tags with the PLC's own tag name as the address — the supported route, in place of direct topological entry. Match each Plant SCADA data type to the PLC variable's type. If OFS connects but the Plant SCADA Studio import throws errors, the link is fine and the failures are tag-level: test each name in the OFS test client. A tag that is good there but fails the import is a naming or data-type mismatch in the SCADA definition — the same definition-level fault as when a SCADA write to a PLC real address fails silently. A tag missing from OFS is a stale XVM, a name that is not in the project, or a dictionary that is not enabled.
What each symptom points to #
- Bad I/O on %Q1.1.20 while other tags read good: a topological address with nothing behind it — route A, then D.
- Every tag on the device bad at once: link or OFS node down — network, not addressing.
- Good in the OFS test client, failing in Plant SCADA Studio: name or data-type mismatch in the SCADA definition.
- Absent from OFS entirely: stale XVM, name not in the project, or Data Dictionary not enabled.
- Bad quality appearing right after a PLC edit: XVM staleness — re-export and reload, or finish the move to the dictionary.
Questions asked
Is there a Modbus address table for the M580 I/O channels?
No, and not because it is hidden. A Modbus-style read resolves located memory references such as %M and %MW. Your program never created located variables for these channels, so no table exists to look up; the %I and %Q names are topological positions. The only way to give those points a readable identity is to add variables for them, by online change if the line cannot stop, and serve the names through OFS.
Can I type %MW or %M addresses directly into OFS instead of importing tags?
Yes. Without a dictionary or an imported XVM file, OFS accepts typed addresses such as %MWxx, %Mxx, %Qxx and %Ixx. Two limits apply: the address must exist as located memory in the controller or the read goes bad, and a typed %Q or %I still depends on the controller allowing topological access. Located words the program actually uses are the safe candidates for typed entry.
OFS connected fine, so why did the tag import into Plant SCADA Studio fail?
Because the connection is device-level and the import failures are tag-level. The OFSOPC driver reached the server; individual names did not resolve. Test each tag in the OFS test client: a tag that reads good there but fails the import has a naming or data-type mismatch in the Plant SCADA definition. A tag missing from OFS altogether means a stale XVM file, a name that is not in the project, or a Data Dictionary that is not enabled.
What breaks if someone edits PLC tags after the XVM file is loaded?
The file goes stale. Renamed or moved variables return Bad quality in OFS and in Plant SCADA, which looks exactly like a network fault but is not one. The fix is to re-export the variable tag database, copy the XVM to the OFS node and reload it, and the reload can briefly interrupt communication. That maintenance cost is the reason to move to the Data Dictionary, which OFS reads directly.
Does enabling the Data Dictionary stop the controller?
It is a project setting, so it takes effect with a download of the project rather than an online change; schedule a short window for it. Until that window, the XVM route keeps the SCADA running, and online change can still add new variables meanwhile. Once the dictionary is in, OFS picks up tag edits automatically and the file handling stops.