IMDTouchKnowledge BaseShop main store

Troubleshooting

Fix a PanelView Float Display Showing the Wrong Value

HMI and touchscreens Published 5 min read

Short answer

The PLC is right and the display is misreading it: a PanelView numeric display shows 6040 because its tag's Data type is set to unsigned integer while F8:9 holds a 32-bit float. Set the tag to IEEE Float/REAL in the tag form editor, confirm the object uses that tag, and the display reads 1.60072.

On this page
  1. Why does the PanelView show 6040 when F8:9 holds 1.60072?
  2. Where is the Data type setting for the tag?
  3. How do I fix the tag step by step?
  4. What does 1.60072 look like to an unsigned integer tag?
  5. Why can't scaling or a PLC change fix it?
  6. How is this different from a Modbus word-order fault?
  7. What if the display is still wrong after the type change?
  8. Questions asked

When a PanelView numeric display shows 6040 while the PLC holds 1.60072 in the floating-point element F8:9, the PLC and the address are both correct and the terminal tag is not: its Data type is set to unsigned integer, so the terminal decodes the float's bits as a plain integer. Change the tag's Data type to IEEE Float/REAL in the tag form editor, confirm the display object references that tag, and the screen reads the real value. This is a terminal-side configuration fault; no PLC logic, scaling, or conversion code belongs in the fix.

Why does the PanelView show 6040 when F8:9 holds 1.60072? #

Because the tag's Data type is set to unsigned integer, so the terminal decodes the 32-bit float bits as a plain integer word; set it to IEEE Float/REAL and the same address displays 1.60072 with no PLC changes.

The evidence for this diagnosis is already in your hands: the PLC programming software shows 1.60072 at F8:9, and the terminal shows a stable, unrelated integer on an object pointed at that same element. A stable wrong number on a live address is an interpretation fault, not a communication fault — a broken link normally announces itself with error indicators or a frozen value rather than a plausible-looking integer that tracks the word contents. Do not try to reverse a conversion formula out of 6040; that artifact depends on which word the tag maps to, and the fix never uses it.

Where is the Data type setting for the tag? #

It is the Data type field on the tag form editor for the tag the numeric display uses, and in that list IEEE Float/REAL sits two entries below unsigned integer.

Open the application in the terminal's editor and open the tag database; select the tag bound to the display. Read two things on that form: the address, which must be F8:9 (element 9 of the float file), and the Data type. Pick the entry by the name shown on screen rather than by its position in the list — a neighboring entry such as a signed integer produces a different wrong number, not a right one.

How do I fix the tag step by step? #

Five steps, all on the terminal side: open the tag, verify the address, change Data type to IEEE Float/REAL, transfer the application, and confirm the reading against a known PLC value.

  1. Open the application in the PanelView editor and open the tag form editor for the tag the numeric display uses.
  2. Confirm the address is F8:9 — the element the programming software shows holding 1.60072 — and not a neighboring element.
  3. Change Data type from unsigned integer to IEEE Float/REAL.
  4. Save, then transfer the updated application to the terminal so the running copy, not just the development copy, carries the change.
  5. With the PLC value known and steady, confirm the display now matches it to the number of decimals you configured.

What does 1.60072 look like to an unsigned integer tag? #

Like two unrelated integers: one F8 element is a single 32-bit IEEE 754 value spanning two consecutive 16-bit words, and this value's words are 16,332 and 58,469.

The encoding, worked for this exact value:

  • 1.60072 lies between 1 and 2, so the exponent is 0 and the biased exponent field is 127.
  • The fraction field is 0.60072 × 8,388,608 = 5,039,204.6, which rounds to 5,039,205.
  • The 32 bits are 0 (sign), 0111 1111 (exponent) and the 23 fraction bits, giving 0011 1111 1100 1100 1110 0100 0110 0101, written 0x3FCC E465.
  • Split into words: 0x3FCC = 16,332 (high word), and 0xE465 = 58,469 unsigned, or −7,067 read as a signed integer.

An integer tag on this element can only ever show one of those word values, never 1.60072, because the interpretation changed, not the data. The exact artifact a given terminal shows — 6040 in the reported case — depends on which word the tag maps to and carries no diagnostic meaning beyond "wrong type".

Why can't scaling or a PLC change fix it? #

Because scaling multiplies an already-misread number: the tag must decode the bits as a float first, and only a tag whose type is correct and whose span is wrong needs a multiplier at all.

A scale factor tuned to turn one artifact reading into one plausible value is wrong at every other value, because the mapping from float bits to the displayed integer is not proportional. When the type is right and you need span correction, such as raw counts to engineering units, that is the separate job covered by scaling a PLC integer into an HMI display value. And do not touch the PLC value itself to make the screen look right: F8:9 feeds the logic that computed it, and bending a live process value to suit a misconfigured display sends a corrupted value to every other consumer of that element.

How is this different from a Modbus word-order fault? #

Here the type itself is wrong; with word order the type is float but the two words arrive swapped, which shows up over Modbus links rather than on a native float file tag.

With the native float file tag, the terminal reads the element whole and the type is the only thing that can be wrong. Over Modbus the same 32-bit value arrives as two registers, so a second fault exists: the registers can be swapped. The test is to set the type correctly first, and if the value is still wild, swap the register pair — displaying a PLC real value over Modbus on an HMI walks through that check.

What if the display is still wrong after the type change? #

Check three things in order: the object must reference the exact tag you edited, the terminal must be running the transferred application, and the tag address must still point at F8:9.

  • A look-alike tag: two tags with similar names, with the display bound to the one you did not edit. Re-open the object's tag reference and read the name on screen.
  • A stale application: the edit saved in the development copy while the terminal still runs the old one. Re-transfer and watch the runtime restart.
  • An address off by one element: F8:8 and F8:10 hold other floats, and a float-typed tag on the wrong element still shows a perfectly plausible wrong number.

Only when all three are confirmed and the Data type reads IEEE Float/REAL does the investigation move to the controller: the value at F8:9 as the programming software shows it, then the communications path.

Questions asked

Can I fix the 6040 reading by changing the numeric display's decimal places?

No. Decimal places change how the interpreted number is printed, not how the bits are interpreted. An integer tag reading 16,332 still reads 16,332.00 with two decimals. The correction is the tag's Data type in the tag form editor, set to IEEE Float/REAL; adjust formatting afterwards for display precision.

Did the wrong tag type corrupt the value in F8:9?

No. The mis-setting is entirely on the terminal side. The PLC stored 1.60072 in IEEE 754 form the whole time; the PanelView was decoding those bits as an integer for display only. Fixing the tag type changes what the terminal shows, not what the controller holds, and no PLC download is part of the repair.

What if another object on the same screen also uses that tag?

Every object bound to the tag switches to the float interpretation at once, which is what you want for indicators and numeric displays on F8:9. Check any numeric-entry objects on the same tag: after the change they write floats, so confirm the receiving instruction in the PLC expects a floating-point operand before an operator uses them.

Does the same fix apply when the float arrives over Modbus?

The data-type part does: a Modbus tag holding a 32-bit float must also be configured as a float type. But over Modbus there is a second failure a native float file tag does not have, namely word order. If the type is correct and the value is still wild, swap the two registers and test again before touching the PLC.

Keep reading

  • Troubleshooting

    Why an HMI Writes the Wrong PLC Value Above 9

    When an HMI display and its PLC register agree up to 9 but the PLC then reads 16 for a setting of 10, 25 for 19 and 32 for 20, the HMI tag is encoding BCD into a binary register. Set the tag data type to Signed Int 16, download, and step through the full range to confirm both numbers match.

    HMI and touchscreens

  • How-to

    Keep a PanelView Plus Trend Logging After Screen Changes

    A PanelView Plus Trend object only records while its screen is visible. Configure a Data Log model to start at power-up, show it through an XY trend with pen 2 as the X axis, and give the log a bounded record limit so it overwrites the oldest records instead of growing without bound.

    HMI and touchscreens

  • Troubleshooting

    Displaying a PLC Real Value Over Modbus on an HMI

    An INTEGER display that reads the register proves the link, station and address, so a blank REAL display is a 32-bit mapping fault. Declare the HMI variable as a 32-bit float on the register pair (40064/40065), set the device double-word order to Low Word First to match the PLC, and give the numeric field six integer digits for 628402.0.

    HMI and touchscreens