Hindustan Scale Company · Est. 1955Foundations — what connected weighing is and why it matters

Excel is fine. Typing into Excel is the problem.

Most Indian factories already keep their weighing records in a spreadsheet. The scale shows a number, someone writes it on a slip, and at the end of the shift someone else types the slips in. Getting weighing scale data to Excel automatically means cutting out the slip and the typing — the PC, the phone app or the cloud server writes the row for you. This guide covers the three ways that actually work, and the three quiet ways each can still fail: the pasted-in decimal, the missing scale ID and the sheet nobody updates.

Counting Platform Scale – HSC -CPS - the HSCo product this paper is about.
Route 1 in one frame: the scale weighs, the cable carries the number, the PC writes the row. Nobody types.

Why typing the number is the weak link

The scale is rarely the problem; it reads to its stamped accuracy every time. The error enters when a person carries the number from the display to the keyboard.

How often? A 2012 study in PLoS One measured it across 21,887 data fields. People typing hand-written numbers once made about 6.7 errors per 1,000 fields; for simple tick-box data the rate was 0.37 per 1,000. When that same structured data was captured automatically instead of typed, the rate fell to 0.046 per 1,000 — roughly eight times fewer errors. (The same reader was worse than a human on handwriting; the gain belongs to clean, machine-readable input — what a scale transmits.)

Checking by eye does not rescue it: a 2011 study in Computers in Human Behavior found visual checking produced 29–58 % more errors than typing everything twice, and was no better than a single unchecked entry.

Then the spreadsheet adds errors of its own. When Dartmouth’s Tuck School audited 50 working spreadsheets in 2009, 94 % contained at least one error and about 1–2 % of formula cells were wrong; the most common mistake was a number typed by hand into a formula. Field audits gathered by the University of Hawaii in 2000 agree: at least 86 % of the spreadsheets examined since 1997 had errors.

So the sheet is not the enemy. The keyboard between the scale and the sheet is.

Bar chart: 6.7 errors per 1,000 fields for hand-written numbers typed once, 0.37 for tick-box data, 0.046 for automatic capture
Hand-written numbers typed once: 6.7 errors per 1,000. The same structured data captured automatically: 0.046. The bars are to scale.

How do you get weighing scale data to Excel without typing it?

There are exactly three routes, and they differ in one thing: which device writes the row. Hindustan Scale Company has built all three; every option on its data logging and reports page ends in a file Excel opens directly.

Route Who writes the row Reach Best when How it still fails
1. Cable into PC software (USB / RS232 / RS485) PC weighing software One scale to one PC, about 15–20 m; RS485 about 1,200 m and 32 scales A fixed station where a PC already sits The PC is off, or the export is pasted rather than opened
2. The app writes the .xlsx (Bluetooth to a phone) The Android app A few metres; the file then travels anywhere A moving operator — a poultry shed, a mandi, a farm The file lives only on a personal phone
3. Cloud export (Wi-Fi or Ethernet to a server) The server; you download the report Every scale on the network, from a browser or a phone Many scales, or an owner away from the plant Someone downloads once, then keeps editing the copy
Diagram of the three routes from a scale to a spreadsheet: cable to PC software, Bluetooth to an app that writes .xlsx, Wi-Fi to a cloud dashboard
Three routes, one difference: which device writes the row — the PC, the phone or the server.

The three routes in detail

Route 1: a cable into PC weighing software

The oldest route, and still right for a fixed station. The indicator sends each stable weight down a USB or RS232 cable; software on the PC receives it, adds the time, the product and the operator, and stores the row. Excel opens the export.

Two rules of thumb from interface design notes published by Texas Instruments: RS232 is one scale to one PC over about 15–20 m of cable at the standard’s 20 kbit/s; if the PC is further away or several scales must share one line, RS485 reaches about 1,200 m with up to 32 devices on one pair of wires.

HSCo’s PC weighing-station software works this way in a textile mill: the platform scale weighs each lot, the station on the PC records it against the lot number, and the shift’s report opens in Excel. Its strength — a fixed, company-owned PC — is also its weakness: if nobody is at the PC, nothing is recorded.

Route 2: the app writes the .xlsx itself

The second route removes the PC. The scale sends each stable weight by Bluetooth to an Android app, which keeps the log and, at the end of the session, writes a real .xlsx workbook — not a text file that has to be pasted in.

The .xlsx format is a published open standard (ECMA-376 / ISO/IEC 29500), so a file an app writes correctly opens in Excel with every column already typed as number, date or text. No import wizard, no paste, no “we couldn’t convert to number”.

HSCo’s poultry and farm weighing app works this way: birds or crates are weighed on a Bluetooth platform scale, and the day’s log leaves the phone as an .xlsx file for the buyer or the office. Scales you already own can join this route — the Bluetooth module relays an existing indicator’s readings to the app.

Route 3: the cloud does the export

The third route needs neither a PC nor a phone at the scale. A Wi-Fi or Ethernet scale posts each stable weight to a server; the dashboard shows every scale on one screen, and batch-, shift-, operator- or product-wise reports are downloaded as Excel, CSV or PDF on demand.

This is the route for many scales, or for an owner who is elsewhere. OIML D 31:2023 describes it in its worked example: an instrument that stores its datasets in the cloud, buffers them locally while the connection is down, and sends them in order when it returns. Ask any supplier what happens during a three-hour internet outage before you sign.

If the destination is your ERP or Tally rather than Excel, the same server-side route feeds it — see ERP and billing integration.

Where each route still goes wrong

Automation removes the keying. Three quieter failures remain.

  1. The pasted-in decimal. Whether “12.345” lands in Excel as a number, as text or as 12,345 depends on the Windows regional settings of the PC — Microsoft’s own documentation says Excel takes its decimal separator from Control Panel, not the file. CSV makes it worse: the IETF’s RFC 4180 admits the format “has never been formally documented”, so separators differ by machine. Excel then edits silently: with default settings it keeps only 15 significant digits, so a 16-digit batch number has its last digit turned to zero, and it turns “JAN1” into a date. A 2016 study in Genome Biology found such conversions in 19.6 % of 3,597 scientific papers with Excel gene lists; in 2020 the gene-naming committee renamed whole gene families (SEPT1 became SEPTIN1) to stop it. Microsoft added a switch to turn the conversions off in October 2023 — if someone knows to tick it. The real fix is Route 2 or Route 3: a file written as .xlsx never passes through a paste.

  2. The missing scale ID. A row that says “412.5 kg, 14:32” is not a record. OIML D 31:2023 and the European WELMEC 7.2 guide both list what a weighing dataset must carry: the value with its unit, the time, the place, the identity of the scale that produced it, and a running number. Regulators go further: the UK MHRA’s 2018 guidance requires instrument-to-worksheet transfer to be validated, unaltered and audit-trailed; the PIC/S guide lists “scraps of paper for later transcription” as a major deficiency; the US FDA asks for secure, computer-generated, time-stamped audit trails. HSCo’s connected scales are designed to send their factory number with every reading, so a row can always answer “which scale, when, and has it been changed since?”

  3. The sheet nobody updates. A spreadsheet that has stopped growing looks exactly like one that is up to date. In 2020, Public Health England lost 15,841 positive COVID-19 test results between 25/09/2020 and 02/10/2020 because laboratory results were being loaded into the old .xls format, which stops at 65,536 rows, as The Register and the Associated Press both reported. No error message; the rows simply never arrived. A hand-kept weighing log fails the same way: the day the clerk is on leave is the day the sheet is silently short. Route 3 makes the server the keeper of the log; Routes 1 and 2 are safe as long as the export is opened fresh rather than copied and hand-extended.

Accounts clerk typing weights from a spike of hand-written slips into a spreadsheet late in the day
Every slip on that spike is one more hand-written number to be typed — the case the studies measured at 6.7 errors per 1,000.

What this is not

It is not a reason to abandon Excel. Your accountant, your auditor and your buyer already live there. The point is to let the scale fill it.

It is not a replacement for the stamped reading. In trade the verified display remains the legal weight; the exported row is a copy of it.

And it is not “any scale with a USB port”. The row must carry the unit, the time, the scale’s identity and a running number, and the file must open as numbers without a paste step. Ask for those by name.

What changes on Monday morning

  1. Nobody types a weight. The number on the display is the number in the cell.
  2. Every row has a scale, a time and a serial number. “Who weighed this, on which scale?” takes a minute, not a week.
  3. The file opens as numbers. No import wizard, no regional-settings surprise, no batch number quietly rounded to zero.
  4. Month-end shrinks. Shift, operator and product-wise reports are the same rows grouped differently — a download, not a day.

How to start: one scale, thirty days

  1. Pick the one scale whose slips get typed the most — usually dispatch or goods inward.
  2. Choose the route by where the row should be written: a PC beside the scale (Route 1), the operator’s phone (Route 2) or a server everyone can see (Route 3).
  3. Connect it. Confirm the export opens as numbers on the accountant’s PC — not only on the installer’s laptop.
  4. Keep the old slip-and-type sheet running in parallel for thirty days and count the differences. That is your error rate, measured on your own line.
  5. Roll out what the count justifies.

Hindustan Scale Company has made weighing scales in Mumbai since 1955 and builds the PC software, the Android app and the cloud platform itself — one supplier answers for the whole chain, from the load cell to the cell in the sheet. Connectivity options for platform, crane, table-top and weighbridge scales are on the IoT connected weighing scales page.

Frequently asked questions

How do I connect a weighing scale to Excel?

Three ways: a USB or RS232 cable into PC weighing software that exports the log; a Bluetooth link to an Android app that writes the .xlsx file itself; or a Wi-Fi or Ethernet scale that posts to a cloud dashboard from which you download Excel, CSV or PDF reports. Which one fits depends on where the row should be written — the PC, the phone or the server.

Can a weighing scale send data directly to a computer?

Yes, if its indicator has a data output. Most HSCo indicators offer USB, RS232, RS485 or Ethernet, and an existing indicator can be given Bluetooth with a relay module. The PC needs software to receive the readings; a bare cable does not fill a spreadsheet by itself.

Which is better for weighing data: USB, RS232 or RS485?

USB and RS232 are one scale to one PC over a short cable — about 15–20 m for RS232 as an engineering rule of thumb. RS485 runs about 1,200 m and lets up to 32 scales share one line, so it suits a plant with several stations feeding one PC. If there is no PC at all, Wi-Fi or Ethernet to a server is simpler than a long cable.

Why does my scale’s weight paste into Excel as text?

Because the decimal mark in the file does not match the Windows regional settings of the PC, so Excel reads “12.345” as text (or as 12,345) instead of a number. CSV has no formal standard, so this varies by machine. A file written natively as .xlsx by an app or a server carries each cell’s type inside the file and avoids the problem.

Does the exported file count as a legal record?

The stamped display remains the legal weight in trade. An exported row is a faithful copy of it — and it is only a complete record when it carries the value with its unit, the time, the place, the identity of the scale and a running number, which is what OIML D 31 and WELMEC 7.2 describe. Ask for those fields before you rely on the file in a dispute or an audit.

Do I need the internet to get weighing scale data into Excel?

No. Route 1 (cable to PC software) and Route 2 (Bluetooth to an app that writes .xlsx) work with no internet at all. Route 3 needs a connection to reach the server, and a well-designed scale buffers its readings during an outage and sends them in order when the link returns.

Next step

Send us a photo of the slip your clerk types from, and we will propose the route — cable, app or cloud — and a thirty-day pilot for that one scale.

Hindustan Scale Company (HSCo) · Mumbai · est. 1955 · www.hindustanscale.com · hsc@hindustanscale.com

Sources

  1. Paulsen A., Overgaard S., Lauritsen J. M. — “Quality of Data Entry Using Single Entry, Double Entry and Automated Forms Processing”, PLoS One 7(4): e35087 (2012): 21,887 fields; 6.7 errors per 1,000 for hand-written numbers, 0.37 for tick-box data, 0.046 with automated capture.
  2. Barchard K. A., Pace L. A. — “Preventing human error: The impact of data entry methods on data accuracy and statistical results”, Computers in Human Behavior 27(5) (2011): visual checking 29–58 % more errors than double entry.
  3. Powell S. G., Baker K. R., Lawson B. — “Errors in Operational Spreadsheets”, Journal of Organizational and End User Computing 21(3) (2009): 50 operational spreadsheets, 270,722 formulas; 94 % / 86 % with errors; 0.87–1.79 % of formula cells wrong.
  4. Panko R. R. — “Spreadsheet Errors: What We Know. What We Think We Can Do.”, EuSpRIG Spreadsheet Risk Symposium (2000): seven field audits, 367 spreadsheets; post-1997 audits ≥ 86 % with errors.
  5. Microsoft Support / Microsoft Learn — “Keeping leading zeros and large numbers”; “Floating-point arithmetic may give inaccurate result in Excel” (30/03/2026); “Set automatic data conversions” (October 2023 option); “Change the character used to separate thousands or decimals”; “Excel specifications and limits” (1,048,576 rows).
  6. Ziemann M., Eren Y., El-Osta A. — “Gene name errors are widespread in the scientific literature”, Genome Biology 17:177 (2016): 704 of 3,597 papers (19.6 %) with Excel-converted gene names.
  7. Tweedie S. et al. (HGNC) — “Genenames.org: the HGNC and VGNC resources in 2021”, Nucleic Acids Research 49(D1) (2020): MARCH#, MARC#, SEPT# and DEC1 symbol families renamed because Excel converts them to dates.
  8. The Register (05/10/2020); Associated Press via PBS NewsHour (05/10/2020); Dimakopoulos D., City, University of London (13/10/2020) — Public Health England: 15,841 positive results missed 25/09/2020–02/10/2020 after lab files were loaded into legacy .xls workbooks capped at 65,536 rows.
  9. OIML D 31:2023 — General requirements for software-controlled measuring instruments, clauses 6.2.7, 6.3.4.2, 6.3.4.4, 6.3.5.2 and 6.3.5.3.
  10. WELMEC Guide 7.2:2022 — Software Guide (Measuring Instruments Directive 2014/32/EU), requirements L1, L4, T1 and T4.
  11. MHRA — GXP Data Integrity Guidance and Definitions, Revision 1 (March 2018), section 6.8; PIC/S PI 041-1 (01/07/2021), sections 9.4, 9.10 and 11.2; US FDA 21 CFR 11.10(e).
  12. IETF RFC 4180 — Common Format and MIME Type for Comma-Separated Values (CSV) Files (2005): “never been formally documented”.
  13. Texas Instruments — SLLA037 (2002), SLLA067C (2017), SLLA070D (2010): RS-232 about 15–20 m at 20 kbit/s; RS-485 about 1,200 m, 32 unit loads (engineering rules of thumb, one publisher).
  14. Ecma International — ECMA-376 Office Open XML File Formats (corresponds to ISO/IEC 29500); Microsoft [MS-OI29500].
  15. Hindustan Scale Company — Data Logging & Reports page (September 2026): exports to PDF, Excel, CSV; batch-, shift-, operator- and product-wise reports; cloud storage, web portals, mobile viewing.