Export Current Result in the modern UI supports Excel workbook .xlsx, CSV UTF-8 .csv, and JSON UTF-8 .json. Use Excel for manual review, CSV for table tools or batch processing, and JSON for custom transformation scripts. Non-preview CLI output can also generate reviewed-tags, normalized-tags, report, and export-manifest files.
Export Current Result in the modern UI supports Excel workbook .xlsx, CSV UTF-8 .csv, and JSON UTF-8 .json. Use Excel for manual review, CSV for table tools or batch processing, and JSON for custom transformation scripts. Non-preview CLI output can also generate reviewed-tags, normalized-tags, report, and export-manifest files.
Exportable points come from scalar members resolved from global DBs and instance DBs. DBs outside the project-tree selection, rule-filtered objects, unreadable objects, complex structures, and non-tag engineering objects are not part of the final export list.
Online scan points come from variable nodes currently browseable through the PLC OPC UA Server. It does not read the local TIA project tree and does not infer optimized DB structure through S7 port 102. Online export fits projects where the PLC explicitly exposes the required OPC UA variables.
DB is the primary scan and export scope. DB points keep symbolic addresses first. Offline scan adds DB number, byte offset, bit offset, and access type when TIA metadata provides stable values.
DB absolute addresses support DBn.DBXbyte.bit, DBn.DBBbyte, DBn.DBWbyte, and DBn.DBDbyte. Optimized DBs, online OPC UA nodes, and some structure-array members use symbolic addresses when stable offsets are not available.
Exportable data types are scalar-oriented: BOOL; BYTE, SINT, USINT, CHAR; WORD, UINT; DWORD, UDINT; LWORD, ULINT; INT, DINT, LINT; REAL, FLOAT, LREAL; TIME, DATE, TIME_OF_DAY/TOD, DATE_AND_TIME/DT, LTIME, LDATE, LTIME_OF_DAY/LTOD, LDT, DTL; STRING, STRING[n], WSTRING, and WSTRING[n]. The export normalizes them to BOOL, BYTE, WORD, DWORD, LWORD, INT, DINT, LINT, REAL, LREAL, STRING, WSTRING, or the matching time/date type.
UDTs, structs, arrays, nested objects, FB/FC objects, DB containers, and complex object references describe engineering structure. When they expand to supported scalar children, those children are exported. Values required for independent collection should be organized as explicit scalar members in the PLC project.
Reviewed export rows include PLC name, symbolic address/source path, absolute address, DB number, offset, bit offset, data type, scan period, alarm flag, trend flag, address state, and comment. JSON also includes export time, project path, output directory, tag count, alarm count, trend count, and rows.
Symbolic addresses should be unique within one device. deviceCode must exactly match the target system device code. Symbolic addresses are for OPC UA/S7 symbolic mode; absolute addresses are for S7 port 102 or similar absolute-address paths. Confirm the target address mode before import.
Alarm and trend are classification flags on a point, not new PLC data types. Rule Center can mark points by symbolic address, comment, source path, and data type. The export uses alarm and trend fields to show whether each point is enabled for those categories.
