Whether a DB enters the result depends on project-tree scope, read access, access attributes, supported types, and rule configuration. Exclusions for backup, history, or temporary DBs should be configured explicitly in Rule Center.
Whether a DB enters the result depends on project-tree scope, read access, access attributes, supported types, and rule configuration. Exclusions for backup, history, or temporary DBs should be configured explicitly in Rule Center.
If a DB does not appear in the result, first confirm that it is inside the selected project-tree scope, belongs to the current PLC, is not excluded by rules, and can be read through Openness by the current user. The selected project-tree scope defines the scan boundary.
Standard DBs can usually provide a DB number, byte offset, and bit offset for absolute addressing. Optimized DBs are safer as symbolic addresses. When TIA Portal or the PLC does not provide stable offsets, the result should use the symbolic access path.
UDTs, structs, arrays, and nested objects are treated as engineering structure. When they can be expanded to supported scalar members such as BOOL, INT, DINT, REAL, LREAL, or STRING, those members are exported. Arrays are expanded by index when index, type, and address are reviewable.
A DB or member needs readable engineering attributes or online access attributes before it belongs in the delivery list. For OPC UA symbolic mode, enable OPC UA on the PLC and confirm the target DB is accessible.
Recognizable exportable DB scalar points inside the intended scope should enter the result. Items outside the result should be attributable to scope, read failure, access attributes, container objects, unsupported types, unstable structure expansion, rule exclusion, or manual deletion.
