top of page

HMI Decimal Places: Verify the Stored PLC Value Before Changing the Display

Nov 1
4 min read

An operator enters 25.7 on an HMI, but the PLC stores 257. In another project, the screen shows 25.7 while the controller retains 25.74. Either arrangement can be deliberate. The fault is assuming that the visible decimal point tells you how the value is stored or written.


Before changing a numeric object, define three things separately: the controller’s data type, the conversion between stored and engineering values, and the display format. Then test the complete read-and-write path. This guide provides a practical method without assuming that different HMI software packages use identical settings.


Display precision and storage are separate decisions


Rockwell Automation’s Studio 5000 View Designer 10 Numeric Input documentation describes decimal-place and rounding properties for how a numeric tag appears. It also notes that its decimal-place property is ignored when the value is assigned to an integer tag. This is a product-specific example of why a formatting option must be read in context, rather than treated as a universal scaling instruction.


A floating-point value can contain a fraction while the screen displays fewer digits. An integer holds whole-number counts; a project can assign those counts an engineering meaning, such as tenths of a degree. Adding decimal places to a display does not, by itself, define that meaning or improve the accuracy of a connected sensor.


Keep units visible and document the conversion beside the tag definition. “Temperature setpoint, °C, stored in tenths” is more informative than a tag called Setpoint with no scaling note. A later engineer should be able to determine the expected controller value without opening every HMI screen.



Worked example: a stored integer in tenths


Hypothetical project requirement: an adjustable temperature parameter uses 0.1 °C steps and is stored as an integer N. The agreed conversion is engineering value E = N ÷ 10. Thus N = 257 represents E = 25.7 °C. The reverse conversion for a valid one-decimal entry is N = E × 10.


If the operator enters 25.7 and the PLC stores 257, the conversion is working as specified. If the HMI also multiplies by ten while another conversion layer already performs that step, the PLC could receive 2,570. If neither layer converts an entry to the intended counts, the result can be wrong in the opposite direction.


Name one location as the owner of each conversion. It may be a supported HMI scaling feature, a defined communication mapping or PLC logic. Read and write conversions must agree. Check intermediate calculations too: a calculation that discards the fractional result before display cannot regain it merely by showing another decimal place.


Decide what happens if someone enters 25.74 when only tenths are supported. The project may reject the entry or apply a documented rounding rule. Do not leave that behaviour to assumption. Test values on both sides of a rounding boundary, and test negative values if the application allows them.


A rounded display can conceal an active fraction


In a different hypothetical project, a REAL parameter retains 25.74 °C and the display shows one decimal place, giving 25.7 °C under the selected rounding rule. The visible number and stored value differ without a communication fault. Any calculation using the stored parameter must be assessed against the stored value, not a screenshot of the rounded display.


Write behaviour also depends on the destination. Rockwell’s FactoryTalk View ME 16 implicit-decimal example shows the same fractional entry producing different results for floating-point and integer connections. This example is not a specification for ProSight or Coolmay equipment. Check the manual for the actual numeric object, software version and tag type in your project.


Commission the complete path


1. Record the contract. Document the tag address, data type, signedness, units, scale factor, permitted range and input step. Identify the read expression and write expression, including conversions outside the HMI.


2. Test in a safe environment. Use a simulator, test project or approved maintenance arrangement that prevents unintended equipment operation. Do not edit live operating parameters merely to demonstrate a display issue. Application-specific control changes require competent design and validation.


3. Compare all representations. For each test value, record the keypad entry, value actually stored in the controller, engineering interpretation and value displayed after a fresh read. A matching keypad preview alone does not prove that the write succeeded.


4. Include boundaries. Test zero, a normal value, permitted negative values, minimum and maximum entries, and values just beyond the allowed range. Check the defined handling of extra decimal places. Ensure the representation can hold the largest permitted scaled value.


5. Confirm acceptance and refresh. Cancel an edit and verify that the stored value remains unchanged. Commit an allowed edit, navigate away and return, then confirm the value after a new read. If controller logic validates or replaces a requested value, show the accepted value clearly.


Common mistakes to avoid


Do not confuse keypad limits with complete controller-side validation. Other interfaces may write the same parameter. The responsible designer should define validation for every permitted write path; a numeric input object is not a certified safety function.


Avoid copying a screen object into another project without checking the destination tag’s representation. Identical labels can hide different scale factors. Also avoid adding decimal places as a response to a measurement discrepancy before reviewing the sensor, conversion and calculation chain.


Close commissioning with a small test record that another technician can repeat. The useful acceptance statement is specific: an entry of 25.7 writes 257 counts, reads back as 25.7 °C and behaves correctly at the agreed limits. “The screen looks right” leaves the important work unverified.


Sources and pictured controller





Need help with your application?


For instrument and controller enquiries, visit ProSense Instruments, email sales@prosenseinstruments.com.au or call 1800 560 854. Include the exact controller model, HMI software version, tag type and required engineering units.


For monitoring and automation projects, visit ProSense Solutions or email sales@prosense.com.au.


For software enquiries, visit ProSight Software or email info@prosightsoftware.com. Device and protocol integration must be confirmed for your application.

Comments


bottom of page