How instrument wire numbers are assigned
By Saad, practising automation engineer · Updated 2026-09-25
Wire numbers must be unique where they are printed. SchematicForge stores them per signal and draws them on the loop sheet. A project-wide from-to list is not a download yet.
Unique in the loop versus unique in the project
A ferrule that repeats PT-1001-1 on two loops will be printed twice. Commissioning wants a number that is unique on the job. Many shops still number per loop and accept the prefix as the discriminator.
SchematicForge validation rule V18 flags a duplicate wire number inside one loop. It does not yet reject the same number used on two tags.
Where the number is stored
Each signal has a wire_numbers list, one entry per core. If the list is empty, the drawing engine generates {tag}-{seq}-{core}. Overrides you type in the Loop Register are kept.
Those numbers print beside the wire on the loop sheet and appear on the termination list. There is no separate from-to CSV in the package download today.
Worked example
PT-1001 signal 1, two cores, no override: PT-1001-1-1 and PT-1001-1-2. A typical analog pair on JB-01 terminals 1–2. If you set wire_numbers to 1-11 and 1-12, the sheet and the termination list both show 1-11 / 1-12.