Ewon Flexy: Troubleshooting Bulk Tag Deletion Errors

Jason IP2 min read
Other ManufacturerOther TopicTroubleshooting
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

Bulk deletion through var_lst.txt can work for MEM tags, but the reported Ewon Flexy import failed when tags belonged to another I/O server. The confirmed workaround is to erase the configuration, then rebuild the required tags from the maintained tag list.

Use the required deletion-file structure

Format the import as a semicolon-delimited file with Name and DoDelete columns. A value of 1 requests deletion:

Name;DoDelete
DI110;1
DI111;1
DI112;1

This exact structure was verified with MEM tags. The evidence does not establish that quotation marks are required; both quoted and unquoted attempts failed in the affected case, so changing quotes alone does not address the reported I/O-server problem.

Interpret the Flexy event-log errors

Observed event Engineering interpretation
23304 varld-Import config error at line (Line: 104) The configuration importer rejected the identified line. Inspect that line and determine whether its tag belongs to the same I/O server as the failing group.
7501 gio-Server Name requested does not exist The importer requested an I/O-server name that the device could not resolve. This supports an I/O-server-specific failure, but the evidence does not identify the exact server name or root cause.
Watchdog error The first bulk attempt coincided with a watchdog event. Stopping all I/O servers and rebooting did not eliminate the subsequent per-line import errors.

Separate the confirmed behavior from the unresolved fault

A minimal DoDelete import succeeded for MEM tags. Repeating the method with the affected I/O server reproduced the problem, indicating that the field itself was not universally broken. The available evidence does not identify an affected firmware version, a corrected version, or whether the failure applies to every non-MEM server.

Use a small file containing known MEM tags to validate the import syntax. If that succeeds while the target-server tags generate events 23304 and 7501, treat the issue as server-specific rather than changing the delimiter or quotation style repeatedly.

Apply the confirmed full-list workaround

  1. Retain the authoritative tag list in an external source such as the existing Excel workbook so the required tags can be recreated.
  2. On the Flexy, open System Setup > Storage > Erase & Format and select Erase Config.
  3. Recreate or import only the tags required by the application.
  4. Verify that the expected tags are present and review the event log for new import errors before returning the application to service.

This procedure was confirmed to remove the complete tag list in the reported case. Because the evidence does not enumerate every configuration object affected by Erase Config, preserve the configuration needed for recovery before using it.

FAQ

What format deletes Ewon Flexy tags with var_lst.txt?

Use the header Name;DoDelete, followed by one tag per line in the form TagName;1. This format was confirmed with MEM tags.

What does Ewon Flexy event 7501 mean during tag import?

Event 7501 reports gio-Server Name requested does not exist. In this case it accompanied an I/O-server-specific bulk-deletion failure, although the evidence does not establish the underlying cause.

How can I delete the entire Ewon Flexy tag list?

Open System Setup > Storage > Erase & Format and select Erase Config, then rebuild the required tags from the maintained tag list. Preserve the configuration needed for recovery first because the full scope of Erase Config is not documented in the available evidence.

Back to blog