Description
The exported <Tags> section includes tags with malformed names like $08bafe42$, $ef9325fd$, etc., and missing DataType attributes. These appear to be internal/system records that were not fully parsed, or object IDs that were never resolved to real tag names.
Example
<Tag Name="$08bafe42$" DataType="" ExternalAccess="Read/Write" .../>
<Tag Name="$ef9325fd$" DataType="" ExternalAccess="Read/Write" .../>
<Tag Name="$042a1fac$" DataType="" ExternalAccess="Read/Write" .../>
Impact
- These tags are not valid L5X and will cause import errors in Studio 5000.
- A project with 1,096 valid controller tags (per Logix Designer) shows 1,214 tags in the library export — approximately 118 extra tags, many of which are these corrupted entries.
Root Cause (suspected)
In Comps.Dat, not all FAFA records correspond to user-defined tags. Some are internal bookkeeping records (map devices, module I/O, etc.) whose comp_name is a raw object ID or hex placeholder because the parser did not have a resolved name for them. These should be filtered out during TagBuilder.
Tags with empty or $hex$-formatted names, or with no resolved DataType, should be excluded from the exported tag list.
Description
The exported
<Tags>section includes tags with malformed names like$08bafe42$,$ef9325fd$, etc., and missingDataTypeattributes. These appear to be internal/system records that were not fully parsed, or object IDs that were never resolved to real tag names.Example
Impact
Root Cause (suspected)
In
Comps.Dat, not all FAFA records correspond to user-defined tags. Some are internal bookkeeping records (map devices, module I/O, etc.) whosecomp_nameis a raw object ID or hex placeholder because the parser did not have a resolved name for them. These should be filtered out duringTagBuilder.Tags with empty or
$hex$-formatted names, or with no resolvedDataType, should be excluded from the exported tag list.