The Vending Dashboard Shows 12 Instead of 12.34. Where Did the Fraction Go?

Introduction

A commissioning demonstration can be persuasive: the connection is active, the gateway reports successful reads and the dashboard updates. Then the buyer notices that a source display showing a fractional value appears as a whole number in the receiving system. The team can see data moving, but it has not yet established that the business information survives the journey. A purchasing specification that asks only for connectivity leaves this question unresolved.

This guide concerns an optional data integration that has been explicitly proposed for a vending project. It does not assume that any WEIMI cabinet exposes Modbus points or works with the gateway family discussed here. Confirm interface availability before spending time on representation details. Where integration is offered, decide which values need fractional information and record that requirement in the engineering scope.

The example 12.34 is illustrative, not a measurement from a vending machine. It helps distinguish a connection test from a value-preservation test. A real acceptance file should identify the actual point, its purpose and an approved reference condition. Its result must be interpretable by both the supplier and the team responsible for the receiving application.

Quick Answer

Ask what happens to the value at every conversion boundary. Record the source representation, required destination representation, units, agreed transformation and observed result. If a fraction matters, require an end-to-end comparison using a suitable supplier-approved fractional reference. A whole-number sample cannot demonstrate preservation of a fractional part.

ProSoft’s product-specific FieldServer explanation describes a Float-array path that converts to an integer and removes the fraction. It separately describes splitting and joining floating-point data, with swapped variants for word order. Those manufacturer examples show why the representation needs agreement. They are not universal settings, instructions for a WEIMI cabinet or evidence that the listed machines support that integration.

Comparison Table

These are different acceptance claims. A software status marked healthy is useful evidence of communication, but it cannot stand in for a comparison of the actual engineering value. Likewise, a neatly formatted display may be visually correct while representing the wrong conversion.

Who Should Buy This

Use this review when a facilities integrator, operator or software contractor requests numerical equipment information through a confirmed interface. The relevant buyer may be purchasing the cabinet, an external monitoring device, a gateway or a complete engineering package. State which component produces the value and which business is responsible for changing it into the destination format.

A standalone retail deployment may not require an external data path at all. In that case, select the cabinet on its retail function and obtain the operating information included in the supplier’s offer. Do not order a gateway simply to imitate an integration shown elsewhere. A justified requirement explains what decision the receiving user will make and why a particular numeric precision is necessary.

How We Evaluate Smart Vending Machines

We evaluate the retail equipment and the proposed information path as separate purchasing questions. Cabinet assessment concerns product fit, shopping workflow, dispensing or recognition, payment, physical installation and support. Integration assessment concerns the meaning delivered to the receiving system. Neither a successful sale nor a successful read substitutes for the other test.

The equipment comparison is a procurement shortlist based on three public WEIMI listings reviewed on 21 October 2026. It is not an independent performance test. The ProSoft source was read on the same date for its documented conversion distinction. We have not connected these cabinets to FieldServer, observed their raw data or verified a compatible interface. Model-specific quotations and demonstrations remain necessary.

Key Buying Factors

Define the business field first. Name the quantity or condition the project actually needs. A count may deliberately be an integer, while another field may require a fractional part. The buyer should not demand more decimal places merely because the display permits them. State the required use, unit and acceptable agreement before selecting a representation.

Distinguish conversion from presentation. Ask the contractor whether it changes the numeric type, applies scaling, rounds or truncates the value, or merely changes the display format. These are requested explanations, not confirmed behaviors of a WEIMI system. Obtain a before-and-after example for each transformation that affects an acceptance field.

Trace multi-register interpretation. If the offered implementation carries one value across more than one register, require documentation of how those pieces become the destination value. Record the applicable word order and driver setting where relevant. Do not choose a swap option by trial until a screen looks plausible; ask for the device and driver evidence supporting the selection.

Choose a discriminating reference. Use a safe supplier-approved test condition with a fractional component when that component is required. Include more than one meaningful operating condition if the project warrants it. A single constant can leave scaling or conversion mistakes undetected. The responsible engineer should define tolerances and a test method appropriate to the information being accepted.

Retain ownership and versions. Identify who controls the source point definition, gateway configuration and receiving application. Preserve approved versions and configuration exports in the handover. A later driver update can require renewed evidence even when the destination tag name remains the same. Agree the change review before the installation becomes operational.

Best Smart Vending Machines

Three publicly listed equipment formats to discuss with WEIMI. These are retail choices, not a ranking of gateway performance. No FieldServer module, local point map or floating-point interface is implied to be included.

Feature Comparison

Choose the retail architecture that suits the assortment and site. Then compare only the integration options each supplier explicitly offers. A manufacturer’s public technical explanation for a gateway should not become an unquoted cabinet feature in the purchasing file.

Cost & ROI Analysis

Hypothetical planning calculation, not a product price or proven return. Suppose a pilot contains 24 numerical fields and the buyer budgets 8 minutes to compare each source and destination record. That is 24 × 8 = 192 minutes, or 3.2 hours. At an assumed internal engineering rate ofUSD 50 per hour, the planned comparison effort isUSD 160.

The calculation budgets review time; it does not predict savings, error rates or revenue. Actual effort may be lower for a small, well-documented interface or higher when several suppliers must resolve a conversion. Gateway hardware, licences, travel and corrective development are excluded. Obtain project quotations rather than using this example as a supplier rate.

Compare offers on the same deliverables and responsibilities. An integration line described only as “data connected” may leave most of the acceptance effort with the operator. Ask for that boundary to be priced and documented before committing to the equipment package.

Best Choice by Scenario

The destination needs whole numbers only: agree that requirement deliberately. Record how fractional source values will be treated, if they can occur, and who approved that treatment. A valid integer requirement should be explicit rather than an accidental result of a default configuration.

The destination must retain a fraction: make preservation part of the demonstration. Follow a known supplier-approved fractional reference through the offered path and retain the displayed result. Ask the engineer to document how precision, scaling and any relevant word order were handled.

An existing gateway will be reused: ask its owner to confirm the actual driver behavior and supported representation before the cabinet or accessory is ordered. A previously successful project may have used integer fields, different firmware or a different destination application.

A replacement is proposed: require a comparison against the approved record. Do not accept identical tag labels as evidence that the conversion is unchanged. Recheck the representative fields affected by the replacement and retain the new configuration version.

Applications

In a managed commercial installation, the handover can contain one trace sheet per agreed numerical field. It should connect the source identity and value to the gateway transformation and receiving display. The sheet also needs the versions and test condition, so a later technician can understand what the original result established.

For a multi-site operator, approve a representative combination before treating its configuration as a rollout standard. Separate the reusable engineering definition from site-specific details. If another controller or gateway is substituted, record the difference and determine whether the original value-preservation evidence still applies. A copied configuration is useful only within its approved scope.

FAQ

Final Recommendation

Accept the information the project needs, not merely a connection status. Define each field’s intended meaning and representation, require the responsible engineer to explain its transformations, and preserve an end-to-end comparison with the handover. If a fraction matters, the acceptance condition must be capable of revealing its loss.

Source: ProSoft Technology — How does field server modbus driver handle floats, reviewed 21 October 2026. The article uses its product-specific distinction between integer conversion and floating-point handling. It does not provide configuration commands or infer compatibility with WEIMI equipment. The three linked product listings establish retail-format identities only.

CTA

Tell WEIMI your destination, required quantity, product assortment and preferred retail format. If an external data integration is essential, include the receiving-system provider, required numerical fields, precision needs and the evidence your team expects at acceptance. Request written confirmation of interface availability and engineering responsibility.

Get My Custom Quote

Confirm equipment, software, integration charges, delivery terms and support in a configuration-specific offer. Public listings and technical examples are the starting point for project discussions.