Compatibility Libraries

IronPLC bundles compatibility libraries: independently authored implementations of functions, function blocks, and constants from vendor PLC libraries, under their exact vendor names. They exist so that source code written against a vendor’s library checks, compiles, and runs in IronPLC without changes.

Compatibility libraries stay dormant until activated. A library is activated in one of three ways:

  1. Project reference — a discovered project file (for example a TwinCAT .plcproj) references the library by name. This is the normal path; see Use Beckhoff Libraries.

  2. Explicit option — ironplcc check --library <name> (repeatable), for sources without a project file.

  3. Implicit — a library that the vendor’s environment provides to every project with no reference (for example Tc2_BuiltIns) is activated automatically whenever a project for that vendor is discovered.

Referencing a library that IronPLC does not bundle reports problem P6011. Library names are matched exactly and case-sensitively.

Bundled Libraries

Library

Provides

Activation

Tc2_System

System constants (PI)

Reference

Tc2_Math

LREAL math functions (LTRUNC, LMOD, MODABS, FRAC)

Reference

Tc2_Utilities

Formatting functions (LREAL_TO_FMTSTR)

Reference

Tc2_BuiltIns

TwinCAT’s implicit built-in operators (BOOL_TO_STRING)

Implicit

Independence

IronPLC is an independent open-source project and is not affiliated with, endorsed by, or sponsored by the vendors whose library interfaces the compatibility libraries reproduce. Each compatibility library is authored independently from the vendor’s public documentation and contains no vendor code. See Trademarks.