Registrazione dati HMI Weintek: salvare produzione giornaliera e dati Modbus

Choose an interval that serves the report

For one continuously sampled group:

• One sample every 10 seconds produces 8,640 rows per day.
• One sample every second produces 86,400 rows per day.

Actual file size depends on the fields, storage format and overhead. Measure it with a representative trial rather than estimating capacity from register payload alone.

Fast sampling is useful only when the source changes quickly enough and the communication path can support it. Logging the same slowly refreshed measurement ten times does not provide ten independent measurements.

For completed batches or shifts, use a deliberate trigger sequence. Prepare the record first, then request sampling. Avoid a short pulse that may disappear between HMI polls.

Weintek supports resetting a trigger bit after sampling, but that action should not be treated as proof that a CSV has been exported or an external archive has committed the record. 

Configure historical storage separately from the display

Enable historical saving and select a destination supported by the panel.

The manual describes daily yyyymmdd.dtl files for eMT, iE, XE, mTV and iP series. Its cMT/cMT X section uses different history and synchronization settings, including .db handling. Follow the relevant series section rather than assuming every panel creates the same daily file. 

Set retention deliberately. The HMI should hold enough history to survive the expected collection delay, while an independent archive should preserve records for the required business period.

On cMT/cMT X systems, review external-storage synchronization. The manual warns that missing media and certain file-rotation conditions can lead to loss of earlier records. Reinserting a USB drive later does not guarantee complete recovery. 

Include storage status in the operator workflow. A missing drive should be visible before someone needs yesterday’s report.

Export a file that the production team can use

Native history and CSV export are separate stages. In a documented cMT3072 example, WeintekUSA confirms that saving samples to USB produces a .db file; it recommends the Backup object for CSV export. 

For an initial export:

1. Add the appropriate Backup object.
2. Select Historical data sampling as its source.
3. Choose the correct Data Sampling object index.
4. Select a supported destination and CSV format.
5. Set the required range and file-splitting behavior.
6. Run a manual export and inspect the result on a computer.

The current manual includes touch and external triggers. Range selection may refer to files, while output splitting can use dates or row counts; customized file handling also affects the result. Read the fields shown for your model instead of assuming “one file” always means “one day.” EasyBuilder Pro V6.10.01, Chapter 13, pages 13-187–13-191.

After the manual export works, automate the same verified operation. Separate the stages: close the production period, capture its final record, complete the applicable storage step, then export. Triggering sampling and backup simultaneously can create a race over the final row.