Which Logix5000 platforms are supported?

ControlLogix L7x and L8x families, CompactLogix L3x family, with Studio 5000 v32 and later for the L5X import path. Earlier platforms that take L5X also work but are not tested.

Are tag names sanitized for IEC 61131-3?

Yes. Hyphens, dots, and other non-alphanumeric characters in the source tag are converted to underscores. The original tag string is preserved in the Description attribute.

How does signal class map to data type?

AI and AO take REAL. DI and DO take BOOL. The raw integer or float is what L5X carries; engineering-unit scaling is implemented in application logic.

What if a tag name collides with a Studio 5000 reserved word?

Tagsight prefixes the conflicting tag with an underscore at export time. The original tag is still in the Description attribute, so the round-trip back to the I/O list is intact.

Can the export create UDTs?

Not in the L5X export. UDT structures live inside the application logic and are not part of the I/O list import contract.

What about Add-On Instructions?

AOIs are application logic, not tag list. The L5X export carries controller tags only.

I/O list to Studio 5000.

Convert a Tagsight I/O list into a Logix5000 L5X file with controller tags ready to import into ControlLogix or CompactLogix. Tag names sanitized per IEC 61131-3 identifier rules, data types assigned per signal class, descriptions carried through.

Generate the L5X See the I/O list schema

Read one of your own drawings.

Drop a P&ID, instrument index, or schedule. Tagsight reads it to the tag and opens a workspace you keep when you sign in.

PDF · DWG · DXF · TIFF · PNG · XLSX

Browse filesor drop a file anywhere on this card

Column mapping.

Every I/O list column has an L5X destination. Auto-mapped fields populate from signal class; derived fields use cabinet, slot, and channel when present.

#	I/O list column	L5X field	Data type	Mapping	Rule
01	Tag	`Tag.Name`	string	auto	Hyphens and dots converted to underscores so the name is IEC 61131-3 compliant. Original tag preserved in Description.
02	Service description	`Tag.Description`	string	preserved	Service text from the I/O list. Equipment tag and line number appended when present.
03	Signal class = AI	`Tag.DataType`	REAL	auto	Analog input rows are REAL with default value 0.0.
04	Signal class = AO	`Tag.DataType`	REAL	auto	Analog output rows are REAL with default value 0.0.
05	Signal class = DI	`Tag.DataType`	BOOL	auto	Digital input rows are BOOL with default value false.
06	Signal class = DO	`Tag.DataType`	BOOL	auto	Digital output rows are BOOL with default value false.
07	Cabinet / Card / Channel	`Tag.Alias`	derived	derived	When cabinet, slot, and channel are filled, an alias tag is generated to the corresponding I/O module input or output.
08	Sub-class (BPCS / SIS)	`Tag.Scope`	routing	optional	SIS rows route to a separate program scope when the project enforces IEC 61511 separation.
09	Range / units	`not exported`	-	optional	Engineering range stays in the I/O list. Application logic handles scaling.

Other targets.

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 controller tags.

01UploadI/O list
02ValidateColumns
03GenerateL5X
04ImportInto Studio 5000

Bring it into your project.

Upload an I/O list or a P&ID set, review the rows, export an L5X ready for a ControlLogix or CompactLogix project.

Start a workspace Pricing