Troubleshooting
Reading Twido %MF floating values on an XBTGT HMI
Short answer
The XBTGT shows nothing valid for a Twido %MF because the tag is typed as a word: a %MF holds a 32-bit REAL across two 16-bit words. Set the HMI variable to Float on the exact %MF address with Low byte first word order, or publish a scaled %MW in the PLC and divide by the scale factor in the HMI.
On this page
The XBTGT1130 reads a Twido %MF as soon as the HMI variable is typed correctly. A %MF holds an IEC 61131-3 REAL, 32 bits across two consecutive 16-bit words, and a tag typed Word or Integer decodes only one of them. Set the variable to Float against the exact %MF address on the proven Twido device — on Twido, the documented word order in Vijeo Designer is Low byte first — and where the driver in the project cannot map %MF at all, publish a scaled %MW in the PLC and divide by the scale factor in the HMI. Both paths apply to the TWDLMDA20DRT-to-Magelis pairing on this bench.
Why a word tag cannot show a %MF value #
IEC 61131-3 defines REAL as a 32-bit type, so one Twido %MF object occupies two consecutive 16-bit words. An HMI variable typed as Word fetches a single 16-bit word and presents it as an integer, so the numeric display shows 0, an overflow string, or a number unrelated to the process, while the TwidoSoft monitor on the same %MF shows a healthy temperature. The fault sits in the tag's data type, not in the PLC program or the cable. The write-direction version of the same mismatch is why an HMI writes the wrong PLC value above 9.
Prove the value and the link first #
Work through these four checks before changing any numeric format:
- In TwidoSoft, monitor the %MF object and confirm it holds a valid value that moves with the process temperature.
- Record the exact %MF address. The tag must reference that object; a neighboring %MW number is not an equivalent.
- Read one known %MW through the same HMI device. If that read fails, the device, cable and station addressing are the problem, and they come first.
- Check the tag quality or communication status in Vijeo Designer and clear any reported error.
Do not touch data types until the known %MW read works through the same device.
Configure the tag as a Float #
| HMI setting | Required selection | Commissioning check |
|---|---|---|
| Device | The Twido device proven by the %MW read | The known %MW still reads after the change |
| Address | The exact %MF object, in the syntax the driver accepts | No address or range error on download |
| Data type | Float | The value has the expected magnitude and a decimal part |
| Display format | Enough integer and decimal positions for the range | No overflow characters or clipped text |
Open the variable behind the numeric display, select that device, enter the %MF address, change the type from Word or Integer to Float, set the format, download the application, and compare against the live PLC value. The configuration passes only when the display follows the PLC value numerically, decimals included.
Word order: the documented Twido setting #
If the Float tag communicates but shows an absurdly large or tiny number, the words are arriving swapped. The documented correction for Twido — the same note covers Premium, Micro and M340 — is made in Vijeo Designer: double-click the network under IO manager and set the word order to Low byte first. Confirm the fix with two different controlled values that carry decimals, because a single test point can hide an offset error. The wider word-order procedure for real values on Modbus links is covered in displaying a PLC real value over Modbus on an HMI.
Worked example: scaling a %MW for 0.0 to 200.0 °C at 0.1 °C resolution #
Use this path when the driver in the project cannot address %MF as a Float. It is a deliberate scaled integer published by the PLC, never one word of the existing float read as an integer.
Inputs:
- Displayed variable: the Twido process temperature, the reader's own case.
- Required resolution: 0.1 °C, one decimal place, chosen for this readout.
- Highest process value assumed for this example: 200.0 °C.
- Carrier: one signed 16-bit word, range -32,768 to +32,767 counts.
- Scale factor: 10, one factor of ten per decimal place.
Rule in words: the PLC stores the engineering value multiplied by the scale factor as an integer in a dedicated %MW, and the HMI divides the word by the same factor for display.
Arithmetic:
- Largest stored value: 200.0 °C × 10 = 2000 counts, inside +32,767.
- Headroom: 32,767 ÷ 10 = 3,276.7 °C representable before overflow.
- A mid-range reading: 137.4 °C × 10 = 1374 counts; the HMI shows 1374 ÷ 10 = 137.4 °C.
- Resolution: 1 count ÷ 10 = 0.1 °C, exactly the requirement.
- Below zero: -15.2 °C × 10 = -152 counts, inside -32,768.
In TwidoSoft, move the scaled result into the dedicated %MW with a direct assignment in ladder, point an integer-typed HMI tag at that %MW, and build the divide into the numeric display. The general method behind this step is how to scale a PLC integer into an HMI display value.
Decision: with a one-decimal readout and a 200.0 °C ceiling, a factor of 10 in a signed word passes with wide margin, so commission it. If the highest expected value times the factor exceeds 32,767, reduce the resolution or split the range; that threshold, not habit, sets the factor. During these checks, force only a test object and leave the live process variable under its normal control.
Symptom-based diagnostic path #
| Symptom | Likely cause | Decisive check |
|---|---|---|
| Nothing displays and the tag reports an error | Connection, device or address | Read one known %MW through the same device |
| %MW reads fine but %MF shows nothing | Tag not typed Float, or the driver cannot map %MF | Retype the tag as Float; otherwise use the scaled %MW path |
| Stable but absurdly large or tiny number | Wrong data type or word order | Confirm Float, then set Low byte first and retest |
| Right magnitude, no decimals | Integer tag or display format | Check the tag type and the numeric display format |
| Correct at one value, wrong at others | Offset or word-order error | Test two controlled values with decimals |
| Value freezes while the process moves | Communication loss | Check the connection status, then break and restore the link |
Change one layer at a time — communications, address, data type, word order, scaling, display format — and confirm each correction before moving to the next.
End-to-end verification #
- Place the source at a controlled value with a decimal part and compare the online %MF with the HMI display.
- Repeat at low, middle and high points of the range, and include a negative value if the process goes below zero.
- Change the source and confirm the display follows without freezing on the previous reading.
- Interrupt and restore communications by the site's approved method, and confirm the panel reports the loss and recovers the current value.
- Return the variable to its live process source and confirm agreement under normal operation.
Questions asked
Does a %MF share its address with %MW?
No. Twido gives floating objects their own %MF addressing, and the tag must point at that exact object as TwidoSoft shows it. A %MW tag at a nearby number returns whatever integer is stored there, never your temperature.
Will changing the tag to Float change the Twido program?
No. The data type is a property of the HMI variable in Vijeo Designer; the %MF object and the PLC logic are untouched. Only the HMI application is downloaded, and the PLC keeps running throughout.
Does Low byte first affect my %MW displays?
No. Word order matters only for objects that span more than one word, such as Float and double-word tags. Single-word %MW reads are unaffected, so existing integer displays keep working after the setting is changed.
How much resolution does the scaled %MW method give up?
One decade per decimal place: a factor of 10 resolves 0.1 unit and a factor of 100 resolves 0.01 units. Take the smallest factor that shows the decimals you need, so the highest expected value stays inside the word.