Industrial scale PLC integration is not complete when a weight appears on an HMI. A value used to stop a filling valve and an approved value recorded against a production lot need different signals, timestamps and owners. This guide turns the survey, protocol selection, interlocks, procurement specification and FAT/SAT for a Thai factory into requirements a buyer can actually test.
Our guide to weighing-scale data integration explains what makes a defensible weighing event, while PLC data collection compares extraction routes across machines. Here we focus on the work between those layers: connecting an indicator to control and proving filling, discharge and fault behavior. The design examples are engineering proposals, not guarantees that a given model implements a function or that an installation has legal metrology approval.
Start industrial scale PLC integration with three distinct uses
The same displayed weight has three uses. Control needs a current value, valid status, communication health and behavior during motion. Operator display helps staff see progress and deviation. A production record needs one approved result tied to an order, item, lot, scale, operator, unit, tare and time. Copying each displayed number straight into a production database mixes these purposes.
During hopper dosing, a PLC may use changing weight to switch from coarse to fine feed. MES needs the accepted net mass after the step finishes. If every intermediate value becomes a production actual, material totals become meaningless. Specify cyclic control data and committed weighing events separately. Define how the machine responds when cyclic data stops and how a committed event is held or replayed if MES is offline.
Identify the equipment and weighing application
A bench scale, tank or hopper, checkweigher and bagging machine perform different actions. A static scale can wait for load, stability and approval. A flowing hopper sometimes cannot wait for a stable flag while feeding. A checkweigher needs synchronized transport, judgment and reject actuation. A request for “one scale connection” leaves vendors to assume different applications, making bids incomparable.
Create an asset register with line and scale ID, purpose, capacity and division, load-cell and indicator make/model/firmware, current drawings, PLC CPU and free ports, allowable shutdown, washdown environment, calibration record, UI language and maintainer. Flag any trade, evidential, regulated or customer certification use separately. Confirm such use with the competent Thai authority, manufacturer and qualified local specialist; adding communication does not itself establish that an existing approval remains valid.
Architecture: responsibility from load cell to MES
A common route is load cell → indicator or transmitter → PLC → edge/MES → quality records and ERP. The indicator handles excitation, conversion, filtering, zero/tare, display and device status. The PLC handles machine sequence, valve and conveyor interlocks and immediate response. MES binds an accepted result to order, item, lot and operator. ERP receives an approved production or inventory transaction at the agreed level of detail.
The dangerous assumption at this boundary is that a number arriving in the PLC is automatically valid. During overload, error, zeroing or a tare change, a register may retain an earlier value depending on model and implementation. Inspect the actual device data map. Ask for status bits, communications health and a value-update counter or timestamp, as well as weight. If upstream software must infer a missing state, document that inference and test its limits; do not silently present it as an instrument-native signal.
Who may zero, tare or accept a result?
Zero and tare alter the meaning of net weight. Remote zeroing with material still on the platform can invalidate a record. The RFP must say whether remote commands are allowed, which role can issue them, preconditions, audit logs and failure responses. If PLC performs tare while MES assigns the lot, fix the transaction order. For monitoring-only integration, verify read-only permissions and network paths instead of assuming that nobody will send a write command.
Separate immediate control from quality approval
PLC stop decisions belong to the machine time scale; quality approval depends on specification version, order and authorized reviewer. Do not put all quality logic into ladder code or delay a safe stop until MES answers. Test machine response to MES failure separately from reconciliation of unsent results. Emergency stops and other safety functions require their own engineering process, outside the weighing-data interface.
Receive weight as value, state, unit and generation
A PLC tag containing 12.35 does not say whether it is gross, tare or net, kilograms or grams, stable or moving, current or stale. Define sign, out-of-range, sensor fault, communications validity and reset/update generation. Use the exact manufacturer map for the ordered model and option. Mark unavailable fields explicitly rather than inventing them in PLC logic without documentation.
When an indicator can switch between gross and net, read the type flag and value coherently. If the PLC scans them separately at the switch boundary, a new gross flag may be paired with an old net value. Determine whether the device provides a consistent I/O image or sequence counter. A double-read rule is only an application workaround; it may not replace a model’s guaranteed atomic update.
Specify units, digits, sign and byte order
The integer 12345 might mean 12.345 kg or 123.45 kg depending on scaling. Specify scale factor, signedness, overflow, byte order and the point of rounding. Apply the same test load and compare indicator display, PLC internal value, transmitted value and stored value. Around a limit, state whether the decision uses the display-rounded number or a more precise internal number. A unit change must not cause historical grams to be interpreted as kilograms.
Translate stability into a process acceptance rule
An indicator’s stable bit describes its own configured measurement condition, not necessarily a completed production step. A container just loaded, a half-filled container during a pause and a load held by an operator might each look stable. Combine stability with an active order, scanned item and lot, assigned scale, end-of-feed state, approved range and duplicate check. Inspect how instrument filtering affects the stable bit on the actual device. The goal is one accepted event, not a record on every transition to “stable.”
Choosing PROFINET, EtherNet/IP or serial for an industrial scale
Choose the protocol from the installed PLC and the exact indicator model and option. A&D lists AD-4411 variants separately: AD-4411-PRT for PROFINET, AD-4411-EIP for EtherNet/IP and AD-4411-485 for RS-485/Modbus RTU, among others. These are variants, not a promise that every interface is simultaneously present on one unit. Verify the ordered part number against the A&D product page.
For PROFINET, import the device maker’s GSDML into the engineering tool, then match device name, IP, I/O modules and diagnostic area. PROFINET International explains that the GSD describes device capabilities and diagnostics. Record versions of GSDML, PLC engineering software and indicator firmware in the RFP, and connect physical units in FAT. Importing a file alone does not prove that weight, state and faults are interpreted correctly. See PROFINET International’s GSD guide.
For EtherNet/IP, establish the assembly, data length, update period and connection-loss behavior for the selected model. A serial connector likewise does not specify framing: baud rate, parity, termination, command, checksum, timeout, reconnect and error indication still need agreement. Analog output needs explicit mapping for range, resolution, break and calibration, and usually needs another route for stability and tare state. METTLER TOLEDO lists USB, serial, analog and industrial-bus choices across its products; confirm the actual device rather than extrapolating from a brand portfolio.
Do not confuse measurement sampling with PLC throughput
A&D states 1,200 measurements per second for the AD-4411 series. That is an instrument sampling specification, not a promise of 1,200 valid PLC records per second. Filtering, fieldbus updates, PLC scan, application reads and committed-event creation have separate timings. In rapid filling, valve latency, falling material, line residue and vibration may dominate the result. Test stop error and variation with the real product and faults, rather than buying only against a brochure’s fastest number.
Boundary when adding an indicator to an existing PLC
A free PLC port does not answer questions about the machine builder’s warranty, source ownership, communication load or address management. Back up the running PLC project; record the code change, I/O map and rollback plan. A read-only edge route may suit monitoring, but stopping a fill valve requires a designed and tested control loop. Split display, recording and control requirements before choosing the destination so that an MES outage does not accidentally become an unsafe control condition.
Define an event for automatic weighing-data recording
Separate a diagnostic stream of changing values from an approved production result. A committed event should carry a unique ID, machine and scale ID, order, item, lot, operation, container and operator, gross/tare/net and unit, relevant status, event and receipt times, specification version and approval state. Replaying the same ID after an outage must return the same result, not add a second material transaction. Decide where IDs are assigned and how they remain unique after power loss.
At network failure, the approved choice may be safe machine stop, limited local continuation with a buffer, or a controlled paper fallback. The process and quality requirement decide. If buffering is used, specify capacity, retention, full-buffer behavior, replay order, encryption, clock drift, duplicate rejection and gap detection. A paper fallback needs an approver, later reconciliation and protection against double posting. Restored connectivity alone must not push unapproved values directly into ERP.
Language and time in a Thai factory
A Thai HMI, English technical documents and Japanese headquarters approval may coexist. Error text, units, permissions and training material must be understandable to the operators, and translations must point to the same device state. Identify whether the instrument, PLC, edge or MES stamps the event. Document the relationship between ICT and stored time; test drift and date changes after power or network failure. If the indicator has no clock, call an upstream timestamp “receipt time,” not “instrument measurement time.”
Prevent wrong-lot binding
An accurate weight linked to the wrong lot is a false traceability record. Verify order, item, lot and container before weighing, then accept only when they agree with the PLC process state. Decide whether an unfinished weight is discarded or held on order change. Test simultaneous results from multiple scales so port, scale ID and lot cannot be crossed. Our lot management implementation guide covers the wider genealogy design.
Sixteen requirements for a comparable RFP
Break “PLC connection, one lot” into the same response matrix for every vendor. Ask each to mark standard feature, configuration, custom development, exclusion and assumption.
| Item | Buyer supplies | Vendor answers |
|---|---|---|
| 1 Assets | Lines, count, use, working hours | Covered models and scope |
| 2 Metrology | Range, division, product, vibration | Applicable model and conditions |
| 3 Hardware | Load cell, indicator, cabinet, wiring | Reuse and replacement |
| 4 PLC | CPU, firmware, ports | Interface and code changes |
| 5 Signals | Gross, tare, net, state, fault | Data map and update rule |
| 6 Numeric form | Units, digits, sign | Conversion and boundary rules |
| 7 Commands | Zero, tare, accept, cancel | Rights, logs, forbidden states |
| 8 Control | Coarse/fine feed, stop, discharge | State transition and fault stop |
| 9 Records | Order, item, lot, user | Event schema and source of truth |
| 10 Network | Ports, VLAN, direction | GSDML or frame version, diagnostics |
| 11 Failure | Link/power loss, full buffer, clock | Fail response and recovery |
| 12 Calibration | Checks, records, replacements | Due-date and failure block |
| 13 Security | Accounts, remote service | Roles, logs, patch boundary |
| 14 Support | Language, spares, local contact | Service terms and documents |
| 15 FAT/SAT | Workpieces, test loads, dates | Cases, pass criteria, evidence |
| 16 Handover | Drawings, source, settings, training | Deliverables, versions, rights |
Tailor the matrix to the application. A logging-only bench scale does not need fine-feed control; an automatic filler needs valve delay, moving load, empty or doubled bag and discharge-fault cases. Two bids for the same number of scales can differ because one excludes cabinet work, ladder changes, MES, quality approval or testing. Compare the scope that satisfies the same acceptance conditions, not just the equipment subtotal.
Attach a model-by-model compatibility matrix
List indicator part number, option and firmware against PLC CPU, communications module and engineering-tool version. For each combination state whether weight, gross/net flag, stable, fault, remote zero/tare, link diagnostics and a GSDML/EDS or frame specification exist. Mark unknowns “pending verification” and assign the owner and method of checking. A function shown in a manufacturer’s series brochure still has to be confirmed in the purchased option.
Include the data contract and change control in the quote
A data contract goes beyond tag names. Define each field’s type, unit, required/optional status, meaning when missing, update condition, maximum size, response to a repeated event ID and schema version. An absent net_weight is different from zero. Keep instrument time, edge receipt time and MES registration time in separate fields. Store short cyclic control data in PLC and associate variable-length order, lot and operator context in MES so new products do not require unnecessary ladder changes.
Specify who requests a change, how the affected machine, tag, HMI, report and API are identified, and which tests repeat. Even an indicator firmware update may alter initialization or a data map: back up the old settings and retest communication and faults. A ladder edit touching a safe-stop condition deserves a stricter review than an HMI wording change. An MES item-master change may alter tolerance or unit version. A change record should include old and new versions, cutover time, owner, rollback decision, affected lots and retest evidence. “Tested at delivery” describes only that day’s configuration and workpiece. Define a risk-based regression test for a new container, changed vibration, replacement load cell or additional scale, and retain the reason if not every original case is repeated.
Compare costs by work package and owner
Separate instrument, cabinet and wiring, networking, PLC/HMI edits, MES/API work, migration, FAT, SAT, training, local commissioning, spares and support. A missing state bit or an undocumented legacy frame can change the development effort. A short shutdown window may require a test cabinet and rehearsed cutover/rollback. Confirm local Thai support, replacement lead time, language of work instructions and out-of-hours terms. A single invented “typical cost” is less useful than identifying which scope items move each quote.
Scale-to-PLC FAT/SAT: leave evidence of acceptance
FAT checks the indicator, simulated or real PLC and application before shipment. SAT checks installed wiring, vibration, real material, operators, network and MES on the Thai line. For each case record input, expected result, observed result, pass/fail, software and setting versions, logs or images, tester, witness and time. Record temporary operating conditions and a retest date for open items. A displayed number alone is not a pass criterion.
| Test | Input or action | Acceptance principle |
|---|---|---|
| Normal | Known test load; gross/net switch | Indicator, PLC, MES and stored meanings/units agree |
| Limit | Just below, at and above limit | Rounding and judgment match approved rule |
| Motion | Stop feed during vibration | Unstable value is not committed |
| Tare | Change container; clear tare; unauthorized command | Net result and audit log agree |
| Link failure | Unplug cable; restart PLC or indicator | Defined safe response; no stale reuse |
| Power loss | Restart edge and MES separately | Replay by event ID; no double posting |
| Fault | Overload, error, overdue check | Machine and record are held or stopped as specified |
| Multiple scales | Simultaneous feed and send | No scale or lot cross-assignment |
| Time | Drift and date rollover | Event/receipt time distinguished and drift detected |
| Replacement | Restore settings to spare | Version, parameters and communication reproduced |
Do not copy generic numbers for test loads, tolerance, update period or stop delay. Put values from the selected instrument, product, process requirement, calibration procedure and manufacturer’s guidance into the contract before award. Capture diagnostics at each layer so a failure can be assigned to measurement, communication, PLC or MES. Version-control the PLC project, GSDML, indicator and edge settings and API contract so the tested configuration can be recreated.
Write the safe failure response first
If a numeric register retains its previous value after link loss, a PLC may see no increase and leave a feed valve open. Monitor link health and value freshness separately, and move the process to its risk-assessed safe state on timeout. Conversely, a momentary lost packet may not justify stopping an entire line. Define timeouts and restart conditions from the application risk assessment. Safety instrumentation and emergency-stop performance need their own design and validation.
Calibration, daily checks and replacement
Good communications cannot fix mechanical interference, moisture, vibration, off-center loading or poor mounting. Define where daily checks and calibration results are stored and who blocks use on an overdue or failed check. After changing a load cell or indicator, restore settings, check zero/span, recheck data mapping and status, and verify MES scale identity. Reusing an old scale ID without recording the physical replacement breaks equipment history; keep a change record.
Roll out in four stages
First survey models, ports, cabinets, load-cell wiring, calibration evidence, PLC source, MES API and work instructions; list unknowns. Second prove a representative difficult device, including weight, state, units, link loss and tare. Third implement machine state and event integration and close abnormal cases in FAT. Fourth perform site SAT with real workpieces, operators and maintenance staff, then hand over recovery procedures.
Selecting only the newest, easiest scale for the pilot hides cost in old models. Represent interface differences, PLC constraints, dynamic weighing, washdown and hard-to-stop lines. Fix one connection template and data contract, then capture model differences in the compatibility matrix. This is a method to surface rework early, not a promise of a universal project duration.
What to receive at handover
Collect commented PLC source, I/O and tag list, indicator configuration backup, device description files, network drawing, data contract, error catalogue, FAT/SAT records, restart and rollback procedures, calibration/check instructions, service-account ownership, licences and spare-parts list. Keep the documents aligned with the running versions. State where secrets are held and how access transfers; do not put passwords in the operating manual.
Frequently asked questions
Is an Ethernet port sufficient for industrial scale PLC integration?
No. Ethernet names a physical network; the application may be PROFINET, EtherNet/IP, Modbus TCP or proprietary TCP depending on model and option. Confirm PLC support, device file, data map, status and loss behavior model by model, then test control and records.
Is a stable bit enough for automatic weighing-data recording?
No. Stability is an instrument condition. Acceptance also needs the correct order, lot, container, scale, process and operator, plus unit, tare, error state, time and replay protection. Confirm the stable bit’s meaning under actual filter settings.
Does importing a GSDML finish a PROFINET scale installation?
No. Match versions, device name, I/O layout, value types, update period, diagnostics and PLC fault behavior. FAT/SAT must compare display, PLC and MES with actual material.
Where are scale-to-PLC FAT/SAT limits set?
Use the selected instrument, product, process tolerance, check procedure and manufacturer information to specify numeric limits and test method before contract award. The table here lists test topics, not universal pass values. Confirm Thai regulatory requirements separately for regulated uses.
Can an old RS-232 scale remain in service?
Sometimes. Inspect real frames for value, unit, gross/net, stable and error markers, poll or push mode and replay on reconnection. If required status is absent, upstream inference has limits; compare replacing the indicator for control-critical use.
Conclusion: acceptance means safe faults and one definitive result
Before purchasing, separate control, display and committed record; identify the exact instrument and option. Include value meaning, unit, status and update rule in the data map. Specify safe PLC behavior separately from MES event posting. Use an RFP compatibility matrix and FAT/SAT evidence for normal operation, boundaries, link and power loss, tare, lot assignment and replacement.
Even if the models of all existing scales and PLCs are not yet known, a Thai factory can start with an asset survey and a comparable RFP and FAT/SAT plan. Contact TOMAS TECH with the current equipment configuration and whether control or recording is the first priority.
References
- A&D, AD-4411 Series specifications: model-specific interfaces and instrument sampling.
- A&D, AD-4411-EIP/PRT/ECT manuals: model manuals linked from the product page.
- METTLER TOLEDO, Data Communications: interface options across industrial weighing products.
- METTLER TOLEDO, ACT350 PLC integration: example for a specific transmitter.
- METTLER TOLEDO, Engineering Note on PLC Connectivity: engineering integration example.
- PROFINET International, GSD Files: device description and configuration.
- PROFINET International, Configuration Demonstration: setup workflow.
