Development System
Bu içerik henüz dilinizde mevcut değil.
The NEV Development System is the engineering software of the platform. An application is configured, programmed, compiled and deployed from here, and the same environment connects to a running target to read its values and load changes into it. It runs on any PC, separate from the target.
What a project holds
Section titled “What a project holds”One project covers the whole application in one tree:
- Motion: the real-time tasks, the NC channels and the axes, with their limits and their kinematics.
- PLC: the logic, in IEC 61131-3 Structured Text, organised with global variable lists and user-defined types.
- Devices and I/O: the EtherCAT network, described from the vendor’s ESI files and compiled into an ENI network image.
- Connectivity: the OPC UA and Modbus interfaces the Runtime exposes.
- HMI: the operator screens, bound to the same project’s variables.
Compiled, not streamed
Section titled “Compiled, not streamed”The Development System does not send settings to a running target one at a time. The configuration and the PLC code are compiled into binaries, and those binaries are what is deployed. The Runtime maps them into memory as it starts, so there is nothing to parse at start-up.
The live link
Section titled “The live link”Once a target is running, the Development System connects to it over a WebSocket link. Values are read while the program executes and shown inline beside the code that sets them, and changes are loaded into the running system.
Where to go next
Section titled “Where to go next”- PLC & Structured Text: the language, and how logic is organised.
- Building & Deploying a Project: what compiling produces, and how it reaches a target.
- The NEV Platform: how the Runtime, the Development System and the HMI relate.