Troubleshooting
Fixing Invalid Bit Address Errors When Adding HMI Tags
Short answer
When the tag editor throws GUI-024: Invalid Address on a slash-form bit address like IO4/05 after a software upgrade, the fault is in the tag-entry dialog, not in the PLC point. Export the tag database, restore the full bit address in a spreadsheet, re-import, and verify the object against the intended output before the screen returns to service.
On this page
- What does GUI-024: Invalid Address actually mean?
- Why does the tag editor reject IO4/05 after the version 6 upgrade?
- Can I just use the word address IO4 without the bit?
- What else triggers GUI-024 besides the tag-entry dialog?
- How do I restore the bit address through export and import?
- How do I verify the imported tag against the right PLC point?
- Why did the hover tooltip stop showing the tag address?
- When should I escalate instead of re-importing again?
- Questions asked
GUI-024: Invalid Address on a newly added discrete tag is an address-entry fault in the HMI software, not a bad point in the PLC. In the documented case, a project converted from version 5 to version 6 lost the bit-level entry field in the Tag Add dialog, so a bit address written in slash form — IO4/05, card 4 output 5 — was rejected while the word address IO4 was accepted. The PLC point was valid the whole time. This article separates that dialog defect from the other documented causes of GUI-024, walks the export, spreadsheet and import workaround that restores the bit address, and sets the verification and escalation limits.
What does GUI-024: Invalid Address actually mean? #
GUI-024 means the address string you typed failed the editor's syntax check for the selected protocol — it is raised at the keyboard, before any download, and it says nothing about the health of the PLC, the driver or the panel. The published error list for this software family defines GUI-024 as an invalid address, and the check runs the moment you leave the address field: no download, no PLC query. Three documented triggers exist:
- The string does not match the addressing rules of the selected protocol, which is what happens to slash-form bit entries in the defective dialog.
- The address falls outside the device range of the selected PLC; the standard vendor guidance for address errors is to confirm the address lies inside the device range in use, and to check shared addresses first when every screen faults.
- The protocol selection does not match the actual PLC, which produces the octal rejections covered below.
Reproduce the fault with one new discrete tag and record the exact error text before changing anything, so the entry fault stays separated from any later runtime or communications fault.
Why does the tag editor reject IO4/05 after the version 6 upgrade? #
Because the upgraded Tag Add dialog no longer offers the bit-level entry field for discrete tags in the A, H, IO and W memory areas — it accepts only the word part, and the vendor confirmed the omission as a bug. The documented case had updated panel firmware, a project converted from version 5 to version 6, and a PLC reached over an Ethernet/FINS driver; everything that existed before the conversion kept working. The failure appeared only when creating a new discrete, bit-only tag in those four memory areas.
Version 5 offered a separate bit-level field in the Tag Add dialog. Version 6 exposes only the word address, and typing the slash notation directly returns Error GUI-024: Invalid Address while the bare word IO4 is accepted. The vendor said a fixed version would come through the manufacturer, but no fixed release was named. Retyping the same string changes nothing. Record the panel model, PLC model, driver, software version and conversion history now — the escalation at the end needs them.
Can I just use the word address IO4 without the bit? #
No — IO4 is the whole word on card 4, and the object needs bit 05, output 5, of that word; a discrete tag saved against the word alone points one level too high and will not behave as designed. The slash form is word/bit: IO4/05 means word IO4, the I/O image of card 4, and bit 05 of that word, which the wiring calls output 5. Bits count from 00, so bit 05 is the sixth bit of the word. A discrete tag saved with only IO4 carries no bit at all.
The documented case proves the distinction: the dialog accepted IO4 alone, but the screen object worked only after the import restored IO4/05. Spend the minutes on the workaround rather than shipping a word address on a discrete object.
What else triggers GUI-024 besides the tag-entry dialog? #
Two other documented triggers exist: addresses containing the digits 8 or 9 in an area the selected protocol numbers in octal — C208, C209, C218 and C219 all fail — and addresses outside the device range of the PLC selected in the project. Octal areas count in base 8, so every digit runs 0 through 7 and no address ending in 8 or 9 exists. A user blocked on exactly those four addresses was not typing anything wrong; those addresses cannot parse in an octal area.
Count it out with the arithmetic in decimal. The word after C207 is C210, because 207 in octal equals 2×64 + 0×8 + 7 = 135, and 210 in octal equals 2×64 + 1×8 + 0 = 136 — consecutive words one apart, even though the labels look three apart. The same step removes C218 and C219: after C217 comes C220.
The documented root cause is a mismatch between the protocol selection in the HMI software and the actual PLC. Decide which side is wrong: if the PLC numbers its points in decimal, the protocol selection is wrong — change it to the matching PLC type and C208 becomes valid. If the area is genuinely octal, C208 does not exist and never will; re-derive the point from the wiring, remembering the jump from C207 to C210. If the software offers no driver for your PLC at all, that is a different problem with a different path — see when the HMI software has no driver for your PLC.
How do I restore the bit address through export and import? #
Export the tag data from the project, change the word-only address of the affected discrete tag to the full slash form in a spreadsheet, and import the file back — the documented case recovered IO4/05 this way and the screen object then worked.
- Reproduce and record: create the discrete tag, capture the exact error text and the address you intended.
- Export the tag data from the project.
- In the spreadsheet, find the affected tag and replace the word-only address with the full bit address — IO4/05, not IO4.
- Keep an untouched copy of the export; it is the rollback if the import lands badly.
- Save the file in the same format the export produced and run the import.
- Reopen the tag database and confirm the entry reads IO4/05 before the tag is used anywhere.
Two limits apply. The import writes tag records; it does not repair the dialog, so future edits of that tag go through the same route. A malformed file stops the import with its own error — GUI-185 is the code documented on failed tag imports — so fix the file instead of retrying. Importing the tag list your HMI software exported is also not the same flow as importing a tag CSV generated by the PLC programming software; for that path, read why EasyBuilder asks for a tag CSV for a Mitsubishi Q PLC.
How do I verify the imported tag against the right PLC point? #
Two checks decide it: the tag database entry must read the full bit address IO4/05, and the screen object must respond to the intended card 4 output 5 point when exercised through the machine's approved procedure — both, before the screen returns to operators. Binding is where imports fail silently, so follow the documented tag-mapping guidance for GUI-024: check the tag database for the required element and any import warnings, and confirm the object actually references the imported tag.
Never force the PLC output solely to test an HMI tag; a forced output can move the machine. Watch the bit in the PLC's online diagnostics while the object is exercised under an approved commissioning or maintenance procedure, and confirm no unintended output changes occur.
Decision: database shows IO4/05 and the object follows the intended point — done, and keep the workaround notes with the project records. Either check fails — escalate rather than re-importing again on hope.
Why did the hover tooltip stop showing the tag address? #
It is a separate display change in the version 6 editor — the tooltip that showed a tag's address on hover stopped appearing for many users, and in converted projects it often returns after you click the tag, then click another control. Reports varied: no tooltip at all in converted projects, slow updates on fast machines, and restoration after a focus change. The working sequence is click the tag to trigger GotFocus, click another control to trigger LostFocus, then hover — after that the tooltip appears.
Use it only as a quick check. The tooltip is display behavior and the stored address is unaffected; one report found deleting and re-adding tags changed the tooltip, but that is not a fix for the address-entry defect and it churns a working project. Do not rebuild working tags to chase a tooltip.
When should I escalate instead of re-importing again? #
Escalate when the import will not retain the full bit address, when the object will not follow the intended point after a clean import, or when GUI-024 appears on addresses that parse correctly in the PLC's own software — those cases are beyond the workaround. The export-import route repairs the data, not the software, and the defect was confirmed as a bug with no fixed release named.
Send the panel model, PLC model, driver, software version, conversion history, the exact address, the exact error text, and whether the export-import route succeeded. Re-verify every workaround tag whenever the project is revised, converted or transferred, and do not commission the affected function until both the address and the object behavior are proven.
Questions asked
What is the difference between GUI-024, GUI-025 and GUI-026?
GUI-024 Invalid Address means the whole address string failed to parse; GUI-025 Bit cannot be empty means a discrete tag was saved without its bit; GUI-026 Invalid bit address means the bit part itself is malformed or outside the range for that memory area. In the dialog defect described here, the slash form raises GUI-024 because the string never parses at all.
Will a later software upgrade fix the tag entry dialog?
Not on any schedule you can rely on. The vendor confirmed the missing bit field as a bug and said a fixed version would come through the manufacturer, but no fixed release was named. Treat export-and-import as the standing procedure until the dialog accepts the bit entry again, and re-check every workaround tag after each software update or project transfer.
Is forcing the PLC output an acceptable way to test the imported tag?
No. A forced output can start motion or change machine state, and testing a tag does not justify that. Watch the bit in the PLC's online diagnostics while the object is exercised through the machine's approved procedure, or test during a scheduled commissioning window with the machine in a safe state.
Do I have to redo the workaround after another project conversion?
Yes. The workaround edits tag records; it does not repair the dialog, so any later conversion, software update or project transfer can expose the same entry path again. After each one, filter the tag database for the affected discrete tags and confirm every slash-form address such as IO4/05 survived before the screen goes back to operators.