A thumbwheel that reports the wrong address type on an integer entry is seeing a data-type label where a complete operand belongs. Enter the address in full file-and-element form such as N7:0, confirm the element exists in the PLC program, download, and watch the write land in the controller's data view.
A thumbwheel that reports the wrong address type on an integer entry is asking for a complete operand. The fix is a string such as N7:0 typed in full. File-based PLC addressing puts three things inside one address: a letter for the data type, a file number and an element number. A label such as Integer names only the type, so the driver has no file to open and no word to write. The message appears while you assign the address, which tells you the string failed the documented format check before any traffic crossed the serial cable. This article walks the checks in order: read the accepted forms, pick an element that exists in your program, download, and confirm the write landed. It also separates a format error from a DF1 fault, because the two call for different fixes.
Why does the thumbwheel call an integer address the wrong type?
The message means the object was given a data-type label where a complete operand belongs. Enter the address in the driver's full file-and-element form, such as N7:0 for integer file 7, element 0.
In file-based addressing the format is fixed and numeric, and the letter in front of the file number is part of how the format carries the data type. That is why the panel software's help file documents accepted operands in its PLC setup section, in exactly these shapes. A bare type label supplies none of the three parts, so there is no file to open and no word to address, and the object refuses it at assignment.
Read the message you actually get, because each one points somewhere else:
- Wrong type the moment you assign the address: the string is incomplete or malformed. Rewrite it in the full form shown below.
- Wrong type on a string that looks complete: compare it character by character against the accepted forms in the help file, then take the exact string, the selected driver and the message text to the panel vendor's support channel.
- An invalid-address message instead: that is a different fault with its own walk-through, in fixing HMI invalid address errors when tagging PLC memory.
- Address accepted but values never move: the format problem is behind you and the serial path is the next suspect, covered near the end of this article.
What does a complete PLC operand look like?
A complete operand names the data type, the file number and the element in one string. The four forms the help documents are N7:0 for an integer element, C5:0.ACC for a counter accumulator, C5:0.PRE for a counter preset and T4:0.TT for a timer status bit.
The letter names the file family: N for integers, C for counters, T for timers. The number before the colon picks the file, the number after it picks the element, and text after the dot picks one field inside an element that has several. Elements are numbered from 0, and the common integer file layout is a table of 256 elements of 16 bits each, so valid entries run from element 0 to element 255.
| Operand | What it addresses | Where it belongs on a panel |
|---|---|---|
| N7:0 | integer file 7, element 0, one 16-bit word | thumbwheels and numeric setpoints |
| C5:0.ACC | counter file 5, element 0, accumulator field | a count shown as it climbs |
| C5:0.PRE | counter file 5, element 0, preset field | a setpoint the operator trims |
| T4:0.TT | timer file 4, element 0, a timer status bit | lamps and status flags |
A field can step down one more level, to a single bit inside it, written with a backslash and a bit number; the accumulator bit addressing page works through the full C5:0.ACC\0 form. Keep the help file's PLC setup section open while you type, because it is the reference your strings have to match.
Which address should the thumbwheel write?
A thumbwheel that sets a number should target an integer-file element that exists in your program, such as N7:12. It should never target a status bit, because T4:0.TT holds one bit while the object needs a whole number.
Open the running PLC program, find the word that holds the setpoint, and enter its file and element exactly. If the program keeps the target in integer file 7, element 12, the object takes N7:12. Do not borrow C5:0.ACC, C5:0.PRE or T4:0.TT just to make the message disappear: those words carry meanings the program depends on, and a thumbwheel aimed at a status bit has no number to write. One integer element is a signed 16-bit word spanning -32,768 to 32,767 counts, so the value the operator dials has to fit inside that band. If it cannot, change the counting unit and keep the address format. Where the intent is to let an operator trim a timing value, ask for the preset field, and follow setting the correct HMI data format for a PLC timer preset for the display side.
Recommendation: Enter the thumbwheel's operand in full file-and-element form, using an integer element that already exists in the program, such as N7:12 for a setpoint stored in file 7, element 12. Reserve C5:0.ACC, C5:0.PRE and T4:0.TT for objects that genuinely read or drive those fields. If the number to dial is larger than 32,767 counts, keep the address format and dial a smaller counting unit, such as hundreds, with the multiplication done in the PLC program.
What do you check before downloading the project again?
Check the operand string first, the program second and the download last. The error judges the address text, and a fresh download copies whatever string is still stored, including a bare Integer.
- Open the thumbwheel object and read the address string exactly as stored.
- Compare it against the four accepted forms and rewrite any type-only entry with the file and element your program actually contains.
- In the PLC program, confirm the file and element exist: in the common layout an integer file holds elements 0 to 255, so a request for element 300 has nothing to land on.
- Confirm the project's controller selection still matches the connected controller and the DF1 settings are the ones the link has always used.
- Run the software's project validation, then download under your normal change control, with the machine in a safe state.
If the rewritten string is still rejected, stop editing the running project and take the exact operand, the driver selection and the complete message text to the panel vendor's official support channel.
Example: which element does a case-count target thumbwheel take?
A packing line needs a thumbwheel for the shift target stored in integer file 7, element 12, so the object takes N7:12. The file's 256 elements run from 0 to 255, element 12 sits inside that range, and the target of 1,200 cases fits a signed 16-bit word.
The original entry read Integer, and the object rejected it at assignment. The rewrite passes three checks:
- Address range: N7:12 is file 7, element 12, and 12 is inside the file's 0 to 255.
- Capacity: one element is a signed 16-bit word with a ceiling of 32,767 counts, and 1,200 is inside it with room to spare.
- Ownership: the program reads this element when the shift target changes, so a thumbwheel writing it is the intended use.
Now stress the band. Suppose the plant switches the count to individual units and the target becomes 40,000 units. That is above 32,767, so one signed 16-bit element has no room for it. Dial hundreds instead: the operator enters 400, the program multiplies by 100, and 40,000 units = 400 x 100 puts a stored value of 400 well inside the band. The address string stays N7:12; only the meaning of one dial step changes.
How do you verify the write reached the right word?
Dial one controlled test value such as 250 counts and watch integer file 7, element 12 in the programming software's data view, where the word should show 250 on the driver's next poll.
Enter 250 at the panel and read the data view. If it shows 250, the operand and the link both work. Let the sequence run and confirm the machine treats the new target as expected. If the word moves and then drifts back, another rung owns that element and the thumbwheel is fighting the program for it; move the setpoint to a word nothing else writes. If the panel's own display of the same word shows nonsense while the data view reads cleanly, that is a data-format mismatch of its own, and the article on an HMI panel showing nonsense numbers from a PLC BCD analog register walks through that fault. Record the validated operand next to the object configuration in the maintenance notes, so a later project edit never quietly reintroduces a bare type label.
Treat the first write as a live setpoint change and make it with the machine in a safe state, because the value reaches the program the moment you confirm the entry.
When is the serial link the problem instead?
A wrong-type message is a format fault: it names the address text, so fix the operand first. Treat the DF1 link as a suspect only when a correctly formed address is accepted but values still refuse to move.
The two faults announce themselves at different moments. A format error appears while you configure the object, against the string itself. A DF1 fault appears later: the address is accepted, the project runs, and values stall, arrive stale or drop out. When the operand passes every check in this article and data still refuses to move, work the serial path on its own terms: the controller selection in the driver, the RS-232 cable and port settings, and the polling between panel and controller. Fixing dropped PLC-triggered messages on a serial HMI panel covers the message-loss pattern, and an HMI screen slow to update over serial with no errors covers the slow, error-free stall.
Do you need the HMI to double as the message board?
Keep the two jobs separate: the HMI panel and its thumbwheel do the control work, and a notice or andon-style board is separate hardware that plays its own content. This fix never involves turning a control screen into a message board.
The panel behind the thumbwheel stays control hardware after the fix. If a station also needs a board for cycle counts, shift notices or andon messages, that display plays its own content with no PLC address of its own; our shop-floor signage category is the place to start.
Questions
Why do all the examples use N7:0?
N7:0 is integer file 7, element 0, the first word of the conventional sample integer file, which is why help pages and examples lean on it. Your program may use a different file number entirely, and its element 0 may hold a value the logic depends on, so read the real file and element out of the running project before you type anything.
Can a thumbwheel write a timer or counter value?
Only a numeric field, such as the counter accumulator C5:0.ACC, and only where the program is built for an operator to change it. Never point a whole-number object at a status bit such as T4:0.TT: a bit holds a single 0 or 1, so a dialed value has nowhere to land. For a timing value the operator may trim, ask the controls engineer for the preset field.
Is this a software bug in the panel?
No. The accepted operand forms are documented in the help file's PLC setup section, so a rejection of a bare type label is the software enforcing its own documented format. If a complete, correctly formed address that exists in the program is still rejected, stop editing and take the exact string, the selected driver and the full message text to the panel vendor's official support channel.
How large a number can one integer element hold?
One signed 16-bit element spans -32,768 to 32,767 counts, which covers most setpoints once you pick a sensible counting unit. Where a genuine value sits outside that band, the program can keep it in a floating-point element written in the same file-and-element style, such as F8:3, and the panel object is given that data type instead of a new syntax.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.