PLC I/O List Builder with CSV Export
List your I/O modules, one per line, and get a complete I/O list with addresses and tag names. Copy it into Excel or download a CSV.
Address format
These patterns are common starting points. The exact address of a point depends on the module and its profile, so compare the first rows with your PLC software and edit the pattern if needed.
Modules (one per line)
Type is DI, DO, AI or AO. Only the first three values are required. Leave the description blank to mark points as SPARE. Lines starting with # are ignored.
How it works
Each module line expands into one row per channel. The tag is the prefix followed by a two-digit number counting up from your start number. The address comes from the pattern, where these tokens are replaced for each channel:
| Token | Replaced with |
|---|---|
{slot} | The module's slot number |
{ch} | The channel number, starting at 0 |
{dir} | I for inputs, O for outputs |
{dirq} | I for inputs, Q for outputs (Siemens style) |
{byte} and {bit} | Byte (start byte plus channel ÷ 8) and bit (channel remainder) for discrete points |
{wbyte} | Start byte plus two bytes per channel, for 16-bit analog points |
{type} | DI, DO, AI or AO |
Worked example
The line DI, 1, 16, PB_, 1, 0, Operator pushbuttons and sensors creates 16 rows. The first is tag PB_01 at address Local:1:I.Data.0, and the last is PB_16 at Local:1:I.Data.15. With the Siemens format and a start byte of 4, the same module gives %I4.0 through %I5.7.
Common questions
Does this create the tags in my PLC software?
No. It builds the list for documentation and review. You can paste it into a spreadsheet, and many PLC packages can import tag lists from CSV in their own format. Check your software's import format before relying on the file.
What does the duplicate warning mean?
Two rows have the same tag or the same address, usually because two lines use the same slot or the same prefix and number range. Fix the line that overlaps.
This tool is provided for convenience. Verify generated addresses against your PLC software and the module documentation before using them in a program.