The world your code lives in. How one controller addresses another, how libraries deliver features, what the hardware family looks like, and where every variable's scope sits. Start with the address that makes networks reachable.
To send a message to another controller, you need its address. In the Omron world that's a FINS address: which network, which node on it, and which unit inside. Dial one in and route a message.
Devices on the plant network
Omron's whole pitch is integration. A single controller — a Machine Automation Controller — runs logic and a synchronised motion core, and a single tool, Sysmac Studio, engineers all of it. No bolt-together packages: one project, one place, one download. Tap each discipline to drop it into the project.
Source : industrial.omron.eu
📚 Libraries deliver features you don't rewrite — Omron's standard set plus your own, namespaced and versioned. (Deep dive D2.)
🧱 Hardware family — NJ/NX CPU units, NX/EJ I/O couplers, NY IPCs, all on the EtherCAT backbone. (Deep dive D3.)
🔀 Editions — the legacy CJ/CP world (CX-Programmer) vs the modern NJ/NX world (Sysmac Studio). (Deep dive D4.)
🗂️ Variable scope — who can see each variable, and for how long. (Deep dive D5.)
In a FINS address, what does the first number — the network — let you do?