This chapter covers 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. It starts with the address that lets you reach a device on another network.
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 sells the platform on integration. A single controller, which Omron calls a Machine Automation Controller, runs the logic and a synchronised motion core, and a single tool, Sysmac Studio, engineers all of it. You don't bolt separate packages together: everything sits in one project and goes to the controller in one download. Tap each discipline to drop it into the project.
Source : industrial.omron.eu
📚 Libraries deliver features you don't have to rewrite: Omron's standard set plus your own, each one namespaced and versioned. (Deep dive D2.)
🧱 Hardware family covers the NJ/NX CPU units, NX/EJ I/O couplers and NY IPCs, all on the EtherCAT backbone. (Deep dive D3.)
🔀 Editions separate the legacy CJ/CP world (CX-Programmer) from the modern NJ/NX world (Sysmac Studio). (Deep dive D4.)
🗂️ Variable scope decides who can see each variable, and for how long. (Deep dive D5.)
In a FINS address, what does the first number (the network part) let you do?