Modules

A module is a package that belongs to a product, so Modules groups them under that product’s name and asks a different question from PLC Libraries: what is this machine made of. A module brings programs of its own, its alarm text, and the starting files the machine builder edits.

Module	Starting files it offers
CNC Core	Machine configuration, IO mapping, Machine M codes, Tool change
Probing	Probe wiring
Handwheel	Pendant selector
Auto levelling	none

Adding one

Ticking a module compiles it in and brings the plain libraries it needs with it. Another module it needs does not arrive on its own, and neither does one go out from under a module that reads it:

What you see	What it means
add Probing first	the module you ticked reads a module that is not in the project
remove Auto levelling first	a module in the project reads the one you are taking out

A module’s alarm text is merged into the project’s at build time, so its events reach the operator as words as soon as it is in.

Starting files belong to you

Add files copies a template’s files into the project once. From that moment they are yours to edit, and the package will not write over them again, whatever version it reaches. What each row says:

Status	What the button does
Not added	Add files writes the set into the project
Added v1.0.0	nothing to do
Added v1.0.0, files missing	Restore missing files writes back only what is gone
Update available v1.0.0 -> v1.1.0	Update to v1.1.0 writes the files you have not edited
Added v1.0.0, package is v1.1.0	every file here is yours, so there is no update to write

Compare is offered on a file you have edited that the package has since changed, and shows the package’s version against yours. Removing a template takes back only the files still identical to what was installed: anything you touched stays.

A starting file’s program asks for a slot

Each template’s programs come with the slot they want in the call order. When your own machine already uses that number, the file still lands and the program does not:

PRG_ToolChange goes in without a place: slot 850 is taken by PRG_Loader. Give it one in PLC Task.

The next build refuses a program with no place, so this is settled on Call Order before building.

What a module will not do

A module knows a condition, never a mechanism. Its starting files are where your machine’s mechanism goes, and they are deliberately unfinished: terminals, valves, timings and step sequences are yours to write.

Where to go next

• What Your Code Owns: the surfaces a module reads and writes.
• Libraries: the plain packages, and the call order.
• Building & Deploying a Project: what compiling produces, and how it reaches a target.