Overview
The Cortex Interface is a modular interface for controlling machines and plants. It is not a one-size-fits-all program: it is a common foundation on which the interface for each individual project is built.
The core is the same for every installation. Standard modules, ready-made and already field-tested, plug in on top of it, along with one or more custom modules written for the customer's machine or process.
The result is an interface built for that project, which stays easy to maintain and to expand with new modules.
Features
- Core common to all installations
- Ready-to-use standard modules
- Custom modules for every project
- OPC UA communication
- Data logging to a database
How it is built
Scroll: the interface is assembled one module at a time.
01 / 05
The core
Every installation starts from the same core: the interface, module management and the shared look and feel. It is the stable foundation that all modules plug into.
02 / 05
Standard modules
Ready-made modules, identical across all projects, for the functions that are always needed: OPC UA communication, database logging and other recurring functions.
03 / 05
The custom module
The part that changes from project to project: a module written for your machine or process, with the screens, logic and controls you actually need.
04 / 05
An example: the biaxial machine
For the biaxial testing machine, the custom module handles axes, homing, tare and tests, building on the same core and the same standard modules.
05 / 05
One interface for every project
The core, standard modules and custom module become a single interface for the operator, which can grow over time as new modules are added.
Modules
One core, standard modules and custom modules.
STANDARD
OPC UA
Communication with PLCs, machines and systems that expose an OPC UA server.
STANDARD
Database
Logging of measurements, tests and events to a database for review and analysis.
STANDARD
Other standard modules
List being updated.
CUSTOM
Your project's module
Screens, logic and controls written for your machine or process.
How a custom module is made
Analysis
It starts with the machine and the people who use it: what the operator needs to see, what to control, which data to log.
Module development
The module is built on top of the core, reusing standard modules where needed.
Integration
Connection to PLCs, drives and sensors, and testing on the real machine.
Delivery and support
Interface installed, documented and ready to grow with new modules.
Documentation
| Code | Document | Rev. | Format | Status |
|---|---|---|---|---|
| CX-CI-OV | Platform overview | – | In preparation | |
| CX-CI-REQ | System requirements | – | In preparation |
Documents will be available to download from this table as soon as they are ready.