Do not replace working vibrating wire sensors just because the old software has no online access. First determine what the datalogger can do: send data, expose it locally, or export it through the manufacturer cloud. Then add an adapter that preserves measurement time, identifier, raw value, temperature and status, and forwards the data to the new platform. Turn off the old system only after a parallel pilot and a channel-by-channel comparison of results.
In brief
- The sensor, datalogger, telemetry and platform are four separate layers. Replacing one does not force replacement of the others.
- The lowest-risk integration preserves frequency, period or digits, plus a separate temperature reading. Calculations must have a documented source.
- The adapter can pull data from the datalogger interface, a local file, database, API or broker. Not every model has every option.
- Local buffering, UTC, retries and idempotency decide whether a loss of coverage creates a gap or only a delay.
- The pilot must compare numbers, completeness and alarms. A nice dashboard is not the switch-over criterion.
This text is not a general guide to connecting any datalogger. That architecture was already described in the article on integrating existing devices with an online platform. Here we solve a narrower problem: how to migrate a vibrating wire path, avoid confusing Hz with period or digits, keep the thermistor and status, and avoid applying the calibration twice.
Start with the VW channel card, not the cloud diagram
On a long-standing asset, one wire can appear in documents under four different numbers. A reader shows 2828 Hz. The datalogger file contains about 354 µs. The old program stores 8000 digits, and the report displays pressure. Before the integrator chooses a transmission protocol, they must establish where each representation is created.
A VW channel card should carry one point from the physical input to the number on the chart:
| Place | Question to verify | Evidence |
|---|---|---|
| sensor and coil | what frequency range is expected | manual for the specific model |
| datalogger input | what sweep and excitation level are set | copy of the input configuration |
| local record | does the record contain Hz, µs, digits or a result | raw file or interface response |
| thermistor | is temperature a resistance, °C or already corrected value | thermistor sample and formula |
| data reduction | where zero, coefficient and temperature correction are applied | calibration sheet and software configuration |
| status | are amplitude, SNR, sweep error or range status available | datalogger documentation |
| platform | which value is to be stored, calculated and alarmed | calculation sheet and SAT test |
Without this card, the adapter may work perfectly from the network side and still pass misinterpreted data. That is what separates a vibrating wire migration from ordinary time-series copying.
Decide where conversion happens before writing the adapter
The best option preserves the value close to the source, the temperature and the status, and calculates the engineering unit in an explicit calculation layer. Not every existing datalogger provides that access. The decision depends on what actually comes out of the device.
| Available export | What the adapter should send | What not to do | Pre-pilot test |
|---|---|---|---|
| frequency in Hz | Hz, temperature, status and time | do not square it without a model definition | comparison with the handheld reader |
| period in µs | exact period and its unit | do not treat µs as seconds | independent 1 000 000 / T |
| digits | digits and the name of the definition used | do not treat digits as a standard across brands | reconstruction from Hz at three points |
| engineering result | result, unit and a copy of the source configuration | do not calibrate twice | comparison with the old software and the card |
| wire plus thermistor in Ω | both readings and statuses separately | do not substitute temperature without the formula | thermistor table check |
| wire without thermistor | wire and explicit absence of temperature | do not send 0°C as a replacement | test for missing input in the equation |
Double conversion is a typical migration error. The datalogger turns digits into pressure, the adapter reads the column without a unit and multiplies by the coefficient a second time. The result still reacts to changes, so the error can pass acceptance based only on the shape of the chart.
The opposite problem appears when the new platform receives Hz, while the old result was calculated from rounded digits. Both algorithms can be logically correct and differ by a small amount. The team should define the tolerance in advance and decide which representation becomes the source after the switchover.
The datalogger output can take several paths
The record may come from a local interface, file, database, manufacturer API or gateway. The general choice of connection point is covered in the related guide. For a vibrating wire path, there is an extra condition: the chosen path must preserve the same precision and status as the local record.
Worldsensing G7 Vibrating Wire Data Logger shows an example of a device that measures the wire and thermistor and forwards data through a gateway to the edge or cloud layer. Worldsensing hydropower modernization case study describes periodic synchronization through an API and cooperation with traditional wired dataloggers. These materials confirm that a mixed architecture is possible. They do not confirm compatibility with any specific legacy device.
If the available path trims decimal places, removes status or returns only a report image, you should look for an earlier access point. A lack of trustworthy output may ultimately justify replacing the datalogger. It does not automatically justify replacing an embedded sensor.
Data contract for a vibrating wire sensor
The data contract should fit on a few pages and be understandable without access to the code. For each field, provide the name, type, unit, source, missing-data rule and example. Broader tender requirements for this layer are collected in construction monitoring data specification for the technical requirement.
Minimal record
| Field | Meaning | Acceptance requirement |
|---|---|---|
| source | stable datalogger identifier | does not change after restart or update |
| measurement point | stable sensor or input identifier | maps to the asset documentation |
| measurement time | moment of observation | UTC, not the time sent to the cloud |
| wire reading | Hz, period or digits | explicit definition and precision |
| temperature | thermistor reading | separate field and status |
| quality status | result of device checks | must not get lost in translation |
| counter or record key | helps with replay handling | allows duplicate or order detection |
| configuration version | firmware or adapter map | indicates the interpretation method |
Not every device provides a counter. In that case, the combination of source, point and time can identify the observation. What matters is that the rule is written down and tested. A repeated send after a lost acknowledgement must not create a second point on the chart.
RFC 3339 describes the date and time format used in internet protocols, including the offset from UTC. For a monitoring system, it is safer to store time in UTC and localise it only at presentation. Daylight saving time should not create two hours with the same label.
Raw or converted value
If the datalogger can only send the engineering-unit result, integration is still possible, but it requires preserving its configuration. A better situation is access to the source reading and temperature. The new platform can then reconstruct the formula, compare both paths and document the difference.
Double conversion is a common mistake. The datalogger turns digits into pressure, the adapter thinks it received digits and multiplies again. The chart may remain smooth. Before mapping, define not only the unit in the header, but also the point where calibration is applied. The three-point control of representation is described in the guide Hz, period, digits and calibration.
The buffer must not change the meaning of a VW record
After a link outage, the adapter sends the backlog. Each record must keep its original time, reading representation, temperature and status. It is not acceptable to reread the current configuration and recalculate the old Hz using a coefficient that changed during the outage.
The safest approach is to buffer the unchanged input record together with the identifier of the map used for interpretation. Server acknowledgement decides whether the copy is removed from the queue. A retransmission must not create a second measurement, and the queue after an adapter restart must not lose the thermistor or status just because optional fields were stored in separate memory.
Calculate capacity in full-path records, not in frequency values alone. One point can include time, Hz, temperature, diagnostics and metadata. GeoLogger Linx is an example of a datalogger with local memory and conversions, and GeoLogger CR combines measurement, reduction, storage and remote communication. Your own installation parameters must still be calculated from its cadence and format.
Parallel pilot for VW: five comparisons, not one chart
The current system remains the source of decisions until the acceptance protocol is signed. For the pilot, choose a stable point, a highly variable point, a long cable, a sensor with a history of interruptions and at least two different transducer types. Perform a parallel field reading for each one.
| Comparison | Data | What to accept as explanation | Red flag |
|---|---|---|---|
| period to Hz | same moment and full precision | difference caused by explicit rounding | mistaken microsecond multiplier |
| Hz to digits | three points across the range | precisely described manufacturer definition | agreement at only one point |
| digits to unit | calibration card, zero, sign | difference within the defined tolerance | constant multiplier or opposite sign |
| thermistor to °C | resistance and sensor table | rounding consistent with the configuration | substituting 0°C when missing |
| old to new system | full pilot period | classified differences and completeness | unexplained smoothing or missing statuses |
Then test retransmission of the same packet, internet failure, adapter restart with a non-empty queue, and sending a short fragment of history. After each test, compare the wire reading, temperature and calculated result separately. One checksum for the whole packet will not show that the translator swapped columns between two points.
Switch alarms at the end. A controlled test should cover a threshold exceedance at the quantity where the threshold actually operates, the return through hysteresis and the absence of data. If the old alarm was based on pressure and the new one accidentally on digits, matching transmission will not save the procedure.
The protocol should include a copy of the field map, calibration documents, control values, tolerances, thermistor-missing cases, adapter version and open limitations. Do not write a generic "results matched". Write which representations were compared and with what error.
Business example: a dam with working wires and an expiring license
Illustrative example. The owner has 120 vibrating wire points. The sensors and dataloggers work properly, but access to the old portal expires in four months. The vendor proposes replacing the whole network because the new cloud version does not support the old gateway.
The team does not start with the price of 120 new sensors. It checks the local datalogger interfaces and finds that time, frequency, temperature and status are available. A field adapter reads records without changing the measurement program, buffers them and sends them to the new platform. Two months of parallel operation reveal 11 points with a different sign convention and three legacy equations whose documentation was incomplete.
The purchase decision splits into two parts. Working sensors and most dataloggers stay in place. Three undocumented paths receive a separate verification plan, and two dataloggers with unstable clocks are scheduled for replacement. The budget goes to the places that actually created the risk, not to concrete and cables only because the portal changed.
This does not prove that an adapter is always cheaper. With a closed protocol, missing parts or unstable excitation, replacing the datalogger may be the best decision. The pilot provides the numbers for that decision.
What this looks like in Inclify
Inclify can act as the online layer for existing dataloggers if the device, gateway or adapter can send agreed HTTP/JSON frames. The platform does not connect automatically to every model on the market and does not read any protocol without integration. Compatibility must be confirmed on a sample frame.
Current data and history can be sent through the same channel with the original UTC time. A repeated record for the same source and time updates the existing entry instead of creating a copy. The platform does not have direct import of measurement series from CSV or XLSX. If the archive exists in a file, the adapter or a controlled script must convert it to the same HTTP/JSON contract.
In a project, you can store inputs and calculate engineering units with explicit equations. Dashboards display series and temperature, and data from a selected range can be exported to CSV. Per-channel thresholds, hysteresis and a separate NO_DATA alarm support operations. Notifications are available by e-mail, SMS and app, with acknowledgement by person and time plus muting until a date.
Exact requests and responses from devices go to a communication log with metadata and the ability to download the raw body. Retention is configurable and defaults to seven days. This is a diagnostic tool, not a multi-year archive of all frames. Measurement history and export rules must be assessed separately.
Criteria for switching to production
- [ ] All points have stable mapping and names from the asset documentation.
- [ ] Measurement time is in UTC and does not change on retransmission.
- [ ] The source value format is defined for each sensor type.
- [ ] Temperature and quality status do not get lost along the way.
- [ ] Equations match the calibration sheets.
- [ ] Three samples per sensor type were calculated independently.
- [ ] Repeated records do not create duplicates.
- [ ] Internet outage ends in backlog, not data loss.
- [ ] Buffer capacity is sufficient for the agreed outage window.
- [ ] Differences between the old and new systems are classified.
- [ ] WARNING, ALARM and NO_DATA alarms have been tested.
- [ ] Recipients can acknowledge and close the procedure.
- [ ] Export returns data from the agreed range and units.
- [ ] The rollback plan does not require field sensor reconfiguration.
- [ ] The contract describes access to data after the cooperation ends.
Before signing the handover protocol, compare the pilot result with the full platform selection checklist for structural monitoring. Frame compatibility does not yet confirm roles, export, retention or the exit procedure.
Limitations and red flags
Not every installation can be connected without hardware changes. A closed protocol, missing documentation, damaged memory, an unstable clock or a non-repeatable measurement may justify replacing the datalogger. The adapter should not bypass safeguards or rely on fragile screen clicking if the alarm depends on the system.
Do not promise "real-time data" without a number either. Vibrating wire sensors usually measure quasi-static processes, and the expected cadence depends on the asset and procedure. Define the measurement interval, maximum transmission delay and notification time separately. One second on the dashboard does not improve the decision if the datalogger measures once an hour.
FAQ
Can every vibrating wire datalogger be connected to the cloud?
No. You need a documented way to read the data or a way to configure sending. That can be an API, MQTT, local port, database, file or the manufacturer gateway. If the device exposes only a screen, or the protocol is closed, integration may be uneconomic or risky. Start verification with the model, firmware and a sample.
Do sensors need recalibration when the platform changes?
A software change alone does not change sensor calibration, but you do need to reconstruct and check the equations, coefficients, zero, sign and corrections. If the documentation is incomplete or the comparison reveals a difference, field verification may be needed. Do not accept equivalence only because two charts have a similar shape.
How do you migrate history from files?
First establish the column semantics, time zone, units and calculation configuration. Then a controlled adapter or script converts the records to the same contract as the current data and sends them with the original time. In Inclify there is no direct import of series from CSV or XLSX, so a file does not enter the measurement database with a single button.
What happens after internet loss?
A properly designed setup stores measurements locally and sends them after the link returns. You need to know the buffer capacity, acknowledgement rules, retries and behaviour after a restart. The presence of memory alone is not enough. Acceptance should include a controlled network disconnect and a completeness comparison after synchronisation.
How long should a parallel pilot run?
There is no single number for all assets. The pilot should cover typical changes in the measured quantity, at least one gap and retransmission test, and the full alarm procedure. For a seasonal process, a short period may not be enough. The criterion is representative events and explained differences, not the number of days.
When is replacing the datalogger better than using an adapter?
When there is no stable and supported interface, the clock is unreliable, frequency measurement is unstable, there is no memory for the required failure window, or the cost of maintaining the integration exceeds the cost of new hardware. It is worth making the decision after a short technical test, with separate assessment of the sensors, datalogger and telemetry.
Sources and further reading
- Worldsensing, G7 Vibrating Wire Data Logger, node architecture, gateway, edge/cloud and formula-based processing.
- Worldsensing, modernization of monitoring at two hydropower plants, API integration and cooperation between new and traditional dataloggers.
- Geosense, GeoLogger Linx Series, local memory, vibrating wire readings and engineering conversions.
- Geosense, GeoLogger CR Series, an example of remote acquisition, reduction, storage and notifications.
- Campbell Scientific, VibratingWire instruction, frequency, thermistor measurement and datalogger diagnostics.
- IETF, RFC 3339: Date and Time on the Internet, unambiguous time representation in internet exchange.
If the old datalogger still measures but the data ends up on one computer, send the device model and an anonymised record sample. We will first indicate the possible connection point and the risks. Hardware replacement should be the result of a test, not a reflex.