İçeriğe geç
İletişim Başlayın

Installation

Bu içerik henüz dilinizde mevcut değil.

Two things are installed: the Development System, the engineering software, and the Runtime, which executes what it produces. Simulation runs on the real Runtime, so a Runtime is on the engineering PC as well as on the target. How it gets onto the engineering PC is what differs between Windows and Linux.

goes on
Development Systemthe engineering PCDownload
Runtimethe target, and a Linux engineering PC for simulationDownload

Both are 64-bit x86_64. The Development System runs on Windows and on Linux, and the Runtime you download is a Linux package. On Windows a Runtime comes with the Development System instead, and that one simulates and nothing else: a machine is driven by a Runtime on Linux.

Simulation is not installed the same way on both

Section titled “Simulation is not installed the same way on both”

On Windows the Development System brings its own Runtime and starts it for you when you connect to a simulated target. There is nothing further to install and nothing to start by hand.

On Linux the Development System starts nothing. It reaches a Runtime over the network, so one has to be installed, on the same PC or on the target. Installing it is what starts it.

Installing the package starts the Runtime and sets it to start at every boot, so there is nothing to launch by hand and nothing to launch again after the machine is restarted.

sudo systemctl status nev-runtimewhether it is running
sudo journalctl -u nev-runtime -fwhat it is doing, as it happens
sudo systemctl restart nev-runtimestarting it again

The Development System reaches it on port 14522.

A real-time kernel, which is what makes the cycle deterministic, and a network interface that can drive EtherCAT. The Runtime runs either on the NEV system image, which comes ready, or on a Linux system of your own.