Introduction

Initial setup of the control system

DHCP: The controller is delivered with the network setting DHCP by default. If a DHCP server is available in the network, the controller automatically receives an IP address from its network. The studio can then automatically find the controller in the network.
Static IP address: The controller has a virtual static IP address 172.31.1.100. Using this IP address, the controller can always be reached in the network, even if no DHCP server is available. In this case you also give the PC an IP address from the same network, for example 172.31.1.200/24.Note that if the controller is set to DHCP, a DHCP server must also be available in the network. The second static IP address is only for configuration and not for continuous operation. If no DHCP server is available, DHCP must therefore always be switched off.

In this example it is assumed that the controller is set to a static IP.

Enter the IP address of the controller or (172.31.1.100 if no DHCP) in the browser, a query of the user and password follows, the default settings are "admin" and "z-server". See also: Beschreibung Webinterface.

In the tab "Network" the settings can now be adapted to the local network.

Connection from the studio

Now start the Studio on your PC and create a new project. To establish a connection to the controller, a connection must be created in the project. To do this, click the Manage connections icon in the toolbar and click Add to the connection settings:

The wizard for setting up a connection is displayed:

Click on "Search control".	All controls available in the network are listed, select a control off to click on Next.	The data of the selected controller are listet in the fields. Click on Connection test	If the connection was successful, click on Save.

The new connection is displayed in the dialog. In this way, several connections can be set up, for example one for the local network and one for remote access.

Important: The controller can always be reached under the IP address 172.31.1.100. If the controller is set to DHCP and no DHCP server is available, a static IP address must always be set. Otherwise, there will be interruptions when connecting via 172.31.1.100 because the DHCP client will be restarted cyclically as long as no IP has been assigned via DHCP.

Tip: If the control is not found automatically, this can have the following causes:

The PC running the studio and the controller are not in the same network (check IP address, network mask), in any case the web interface of the controller must be accessible via the browser.
Programs such as virtual Box install their own network adapters under Windows, then it can happen that the controller is not found.
If a VPN is running on the PC, for example to connect to the Internet, the controller may not be found.
With certain network configurations such as LAN + WLAN, there may also be problems. For initial setup, it is recommended to operate the controller and PC in the same network (wired) and to switch off WLAN.
If certain router configurations do not allow broadcast messages to pass, the controller will not be found either.

It is always possible to give the controller a static IP address and enter it manually in the connection settings.

Edit project

After the connection to the controller has been established, you can start working on the project. See also

Transfer project to controller

By switching between editing and operating mode, the changes are transferred to the working memory of the controller. If you restart the controller, the controller reloads the previous project. If you have made a mistake, it is sufficient to restart the controller in order to continue working with a functioning status.

If you are sure that all changes work, you must save the project permanently on the controller. To do this, press the tool button "Save project persistently on controller".

The following dialog is then displayed:

Click Start to permanently save the current project on the controller.