I/O list to TIA Portal.

A reviewed I/O list becomes a GlobalDB block and a PLC tag-table CSV. Tag names sanitized for IEC 61131-3, data types assigned by signal class, %IW / %QW / %I / %Q addresses allocated from a configurable start. Ready for an S7-1200 or S7-1500 project.

Upload a drawing Pricing

What the GlobalDB export produces.

The same reviewed I/O list reshapes to every other PLC platform and data-exchange format your project might use.

From I/O list to project tree.

01UploadI/O list or P&ID set
02MapColumns to TIA fields
03Allocate%IW / %QW addresses
04ImportGlobalDB or tag table

How the columns map.

Every I/O list column has a TIA Portal destination. Auto-mapped fields populate from defaults you can override at export; derived fields use I/O list values when present and fall back to auto-allocation otherwise.

I/O list column	Target field	Notes
Tag	`Name`	auto
Service description	`Comment`	preserved
Signal class = AI	`LogicalAddress %IW`	auto
Signal class = AO	`LogicalAddress %QW`	auto
Signal class = DI	`LogicalAddress %I`	auto
Signal class = DO	`LogicalAddress %Q`	auto
Cabinet / Card / Ch	`LogicalAddress`	derived
Loop number	`Comment suffix`	optional
Sub-class (BPCS/SIS)	`GlobalDB target`	optional
Range / units	`not exported`	optional

Other targets.

GlobalDB XML.xmlBlock imported via TIA Portal Openness into the project tree PLC tag table.csvFlat tag-table CSV for the tag-table editor import path Studio 5000.L5XLogix5000 controller tag file for ControlLogix and CompactLogix PLCCreator.csvDevice IO List CSV for PLCCreator project scaffolding DEXPI.xmlISO 15926-aligned payload for asset-information systems

Common questions

Does the export produce a GlobalDB XML or a PLC tag table?

Both. The GlobalDB XML imports via TIA Portal Openness and arrives as a single block in the project tree. The flat PLC tag table CSV covers shops that import through the tag-table editor. The two formats carry identical tag names, data types, and addresses.

Which CPU families are supported?

S7-1200 and S7-1500 with TIA Portal V15 and later. ET 200SP CPUs that use the standard STEP 7 import path are also covered. The GlobalDB format and Openness import path are the same across both CPU families.

How is signal class mapped to data type and address space?

AI rows take Real data type at consecutive %IW word offsets. AO rows take Real at %QW. DI rows take Bool at %I bit addresses. DO rows take Bool at %Q. Starting addresses are configurable per export, with %IW256, %QW256, %I10.0, and %Q10.0 as the defaults.

Are tag names sanitized for IEC 61131-3 identifier rules?

Yes. Hyphens, dots, and other separators in the source tag are converted to underscores. The original tag string is preserved in the Comment field so the TIA Portal project traces back to the source document.

Can the same I/O list export to TIA Portal and Studio 5000 at the same time?

Yes. Each export endpoint reads the same reviewed I/O list. A site running mixed Siemens and Rockwell hardware can export both formats from one workspace without re-extracting.

What if a TIA Portal block already exists at the chosen number?

TIA Portal rejects an import when a GlobalDB with the same block number already exists. Either change the block number in the export dialog before downloading, or remove the conflicting DB from the project tree before importing.

Bring it into your project.

Upload an I/O list or a P&ID set, review the rows, export a GlobalDB XML or a PLC tag-table CSV ready for an S7-1200 or S7-1500 project.

Upload a drawing See pricing