EasyConverter from EasyBuilder Pro Opens eMT3000 Log Files

What is the screen telling you when EasyConverter rejects an eMT3000 file?

You pull a log file off an eMT3000 panel, open it in EasyConverter, and get nothing: the file will not load, or the converter errors out with no data grid. The same workstation may open MT6000 or MT8000 files without complaint. The file is fine. The converter is the wrong generation.

EasyConverter is a binary-format parser. It reads the history and log files the HMI runtime writes and turns them into spreadsheet-friendly output. The runtime on each panel generation writes the format that matches the EasyBuilder Pro build it was compiled with. An older standalone converter has no parser for a format revision it predates, so it rejects the file outright.

The known failure point: EasyConverter V.1.00 cannot open files generated by eMT3000 series panels. The version tested as working is EasyConverter V.1.40, the copy that sits in the EasyBuilder Pro installation directory. That copy also opens files from MT6000 and MT8000 series panels.

Check before moving on: open the converter you have been using and read its version from the About dialog. If it reports V.1.00, you have found the cause.

Which EasyConverter executable are you actually launching?

Workstations that have been in service for years often carry two or more copies: a standalone download installed long ago, and the one bundled with each EasyBuilder Pro install. Desktop shortcuts and file associations frequently point at the oldest one.

Copy	Where it lives	eMT3000 files	MT6000 / MT8000 files
EasyConverter V.1.00 (standalone)	Separate install or copied folder	Will not open	Legacy tool; replace it
EasyConverter V.1.40	EasyBuilder Pro installation directory	Opens	Opens

When an older copy still opens your MT6000 or MT8000 files, both tools appear to work for those panels. Standardize on the EasyBuilder Pro copy anyway: one parser covers all three series, and technicians stop guessing which tool matches which panel.

1. Right-click the EasyBuilder Pro shortcut and choose Open file location. This takes you to the installation directory.
2. Locate the EasyConverter executable in that folder.
3. Launch it directly from there, not from an old desktop shortcut.
4. Read the version from the About dialog.

Check: the About dialog reports V.1.40 or later. If the EasyBuilder Pro install is old enough to bundle an earlier converter, update EasyBuilder Pro first. The current package is available from Weintek's official download channel or your authorized distributor.

Is the file you copied off the panel intact?

A correct converter still fails on a truncated or altered file, and that failure looks identical to the version problem. Rule it out before you blame the tool.

Setting / habit	Where	Effect if wrong
Copy log files while the runtime is not writing to them, or copy the closed daily file	HMI storage (internal, USB, or SD)	Partial last record; converter may reject or truncate
Transfer as a binary copy	USB stick, SD card, or network transfer	Text-mode or "helpful" transfer tools corrupt binary files
Keep the original file name and extension	Workstation folder	Converter file dialog filters on extension; renamed files seem to vanish
Never open and re-save the raw file in another editor	Workstation	File structure destroyed

Check: the file size on the workstation matches the size shown on the source media, and it is non-zero. Keep an untouched copy of the original in a separate folder before any conversion attempt.

How do you open and export the file in the correct converter?

1. Launch EasyConverter from the EasyBuilder Pro installation directory.
2. Use the converter's open command and browse to the copied file.
3. Confirm the data grid populates with timestamps and channel columns.
4. Select the export format your downstream tool needs (spreadsheet or delimited text).
5. Save the output to a different folder from the raw file so the original is never overwritten.

The tag is right; the parser was wrong. Once the matched converter loads the file, column names and values come straight from the data sampling or event definitions in the HMI project. Nothing needs remapping.

Check: pick three records at the start, middle, and end of the file. Compare their timestamps and values against the same records on the panel's trend or history display. They should match exactly.

How do you keep V1.00 from coming back?

The fix breaks again when someone double-clicks a log file and Windows hands it to the old executable. Clean up every path that leads there.

Recurring pitfall	Where to look	Correction
File association points to the old converter	Windows Open with / default apps for the log file extension	Re-associate with the EasyBuilder Pro copy
Desktop or Start menu shortcut targets the standalone install	Shortcut properties, Target field	Delete it or repoint it to the installation directory
Standalone V.1.00 still installed	Installed programs list, old tool folders	Uninstall or remove the folder
Multiple EasyBuilder Pro versions installed side by side	Program folders	Use the converter from the newest install
Laptops shared across sites with old images	Every service laptop	Apply the same cleanup to each machine

Check: double-click a log file in Explorer. The converter that opens must report V.1.40 or later in its About dialog.

How do you prove the whole chain works end to end?

Run one test per panel series in your fleet, because the goal is a single converter that handles all of them.

1. Copy one fresh, closed log file from an eMT3000 panel, one from an MT6000, and one from an MT8000 (whichever series you run).
2. Verify each file's size on the workstation against the source media.
3. Open each file by double-clicking it in Explorer, so you also test the file association.
4. Confirm the About dialog shows V.1.40 or later on the instance that opened.
5. Export each file and spot-check first, middle, and last records against the panel's on-screen history.
6. Open the exported file in the downstream spreadsheet or reporting tool and confirm timestamps parse as dates, not text.

The chain is proven when all three series open by double-click in the same converter instance and the spot-checked records match the panel displays value for value.

FAQ