![Phoenix Contact PLCnext Engineer with Zero Trust 1 7949c032 plcnext anyx guide](https://www.agilicus.com/www/7949c032-plcnext-anyx-guide.png)
PLCnext Engineer
The Phoenix Contact PLCnext Engineer is an software engineering tool designed for developing automation applications. By combining the software with Agilicus AnyX Zero-Trust secure remote access, secure programming from anywhere is possible
Configuring PLCnext Engineer as a Launcher
The Phoenix Contact PLCnext Engineer is a software engineering tool designed for developing automation applications. It is part of the PLCnext Technology ecosystem, which aims to provide a flexible and open automation platform. It is a versatile and powerful tool for developing modern automation solutions, offering flexibility, openness, and advanced features to meet the needs of various industrial applications.
When combined with the Agilicus AnyX platform, the software suite can access remote Industrial Control System automated applications via a reliable Zero Trust architecture.
![Phoenix Contact PLCnext Engineer with Zero Trust 2 7d547196 2024 07 12 10 01](https://www.agilicus.com/www/7d547196-2024-07-12_10-01.png)
Furthermore, when also deploying the Agilicus Connector at remote sites on the supported family of PLCnext AXC F (1152, 2152, 3152) high performance controllers , the end-to-end secure remote access components can entirely deployed within the Phoenix Contact family of products, making it an easily deployable and managed solution for both engineers and site planners.
For the purposes of this article, the version of PLCnext Engineer used is 2024.0.3
Creating Network Resources
![Phoenix Contact PLCnext Engineer with Zero Trust 3 8a616ed5 2024 07 12 09 26](https://www.agilicus.com/www/8a616ed5-2024-07-12_09-26.png)
Let’s first create a sample remote controller network resource to allow the Engineer software to access.
Navigate the Admin interface to Resources -> Networks -> New
In Step 1, select the appropriate connector where the remote controller is deployed. In this example, we are selecting a connector installed on a PLCnext AXC F controller at a remote site.
![Phoenix Contact PLCnext Engineer with Zero Trust 4 e1885001 2024 07 12 09 27](https://www.agilicus.com/www/e1885001-2024-07-12_09-27.png)
For Step 2, assign a relevant internal hostname for the remote network
![Phoenix Contact PLCnext Engineer with Zero Trust 5 c7c45b7c 2024 07 12 09 29](https://www.agilicus.com/www/c7c45b7c-2024-07-12_09-29.png)
In the following step 3, configure the valid local IP address and TCP port of the remote controller.
Eg: address of 172.17.2.131 , TCP port of 41100
![Phoenix Contact PLCnext Engineer with Zero Trust 6 9d5acc3d 2024 07 12 09 30](https://www.agilicus.com/www/9d5acc3d-2024-07-12_09-30.png)
In Step 4, Select Optional parameters to specify additional options. In this step, we will add “source port override” settings at the bottom of the menu. Keep the standard TCP port of 41100 .
![Phoenix Contact PLCnext Engineer with Zero Trust 7 b41bf29a 2024 07 12 09 31](https://www.agilicus.com/www/b41bf29a-2024-07-12_09-31.png)
Add a new and unique system address in the 127.x.x.x IPv4 local loopback network aka LocalNet space.
This optional parameter will be used for the Engineer software client to connect through the Agilicus platform via a temporary ‘Ad-hoc’ connection assigned to this unique local IP address that will be created on the workstation where the client software is installed and launched. One such unique address inside the Loopback network will be required for each remote controller, and should not be previously used on the workstation.
In this example, and for sake of addressing clarity and recall, we are using the same last 3 tuples of the controller remote IP address to form a loopback address.
So the remote controller network IP address of 172.17.2.131 is assigned through this option dialog to a local override IP address of 127.17.2.131 for the local Engineer workstation to bind to.
Click “Apply” in step 5
![Phoenix Contact PLCnext Engineer with Zero Trust 8 53de227b 2024 07 12 09 45](https://www.agilicus.com/www/53de227b-2024-07-12_09-45.png)
Repeat this Network Resource creation stepper for each remote network controller that requires access by the Engineer software. Ensure each “Source address override” in the loopback network remains unique .
Configuring PLCnext Engineer as an Agilicus Launcher
In the Agilicus Admin panel, first create a launcher for the Engineer software by navigating to the Resources -> Launcher -> New menu
![Phoenix Contact PLCnext Engineer with Zero Trust 9 1a52a44e 2024 07 12 09 50 1](https://www.agilicus.com/www/1a52a44e-2024-07-12_09-50_1.png)
Assign a name to the launcher, e.g.: PLCnextEngineer2024 and specify the valid path to the actual executable (not the shortcut). The default installation path will be:
C:\Program Files\PHOENIX CONTACT\PLCnext Engineer 2024.0\PLCNENG64.EXE
![Phoenix Contact PLCnext Engineer with Zero Trust 10 74dd6d9a 2024 07 12 10 48](https://www.agilicus.com/www/74dd6d9a-2024-07-12_10-48.png)
Note that the version string is present in the path and may need to be changed when a software update is done at a later time.
In Step 2, we will assign all the resource members previously configured so that the Engineer software can access them. In this case, the previously configured sitea-controller1 network is assigned.
![Phoenix Contact PLCnext Engineer with Zero Trust 11 a6322d54 2024 07 12 09 53](https://www.agilicus.com/www/a6322d54-2024-07-12_09-53.png)
In the third step, we will select NO for any advanced settings.
![Phoenix Contact PLCnext Engineer with Zero Trust 12 f4560270 2024 07 12 09 54](https://www.agilicus.com/www/f4560270-2024-07-12_09-54.png)
In the final configuration step, we can review the New Launcher settings and select Apply to confirm the configuration.
![Phoenix Contact PLCnext Engineer with Zero Trust 13 84a144b7 2024 07 12 09 55](https://www.agilicus.com/www/84a144b7-2024-07-12_09-55.png)
As part for of the Agilicus AnyX permission and resource assignments, we can use step 5 to assign the newly created Launcher to a set of Resource Groups , or assign the resource directly to a set of user identity or user groups.
If this step is skipped, authorization to this newly created Launcher resource can be assigned via the Access -> Resource Permissions admin menu
Launching the PLCnext Engineer application
After running the Agilicus “Refresh” desktop shortcut, any user workstation with Agilicus Desktop Integration will have a visible PLCnext Engineer launcher created in the Agilicus start menu.
![Phoenix Contact PLCnext Engineer with Zero Trust 14 88f32208 2024 07 12 10 39](https://www.agilicus.com/www/88f32208-2024-07-12_10-39.png)
Clicking on this launcher will run the Engineer software and also perform the necessary authentication and authorisation phase for the Agilicus AnyX platform.
The Engineer software will launch as usual, and an existing Project can be opened.
![Phoenix Contact PLCnext Engineer with Zero Trust 15 c937bd67 2024 07 12 10 00](https://www.agilicus.com/www/c937bd67-2024-07-12_10-00.png)
In order to access the remote controller via the Agilicus platform, select the controller and navigate to the Cockpit tab, and then select the ‘Ad-hoc IP address’ menu. To configure the IP address to connect via Agilicus, first “Enable” the setting, and then specify the IP address previously configured as the “source address override”. In this example, we will use 127.17.2.131 . Navigate away from the dialog in order to make sure the setting is saved. Saving the project will also preserve the assigned IP address.
![Phoenix Contact PLCnext Engineer with Zero Trust 16 d9c77931 2024 07 11 15 15 1](https://www.agilicus.com/www/d9c77931-2024-07-11_15-15_1.png)
With this configuration set, enabling ‘Ad-Hoc address’ will allow the Engineer software to connect to the remote controller via the Agilicus platform. Disabling ‘Ad-hoc address’ will set the Engineer software to connect via the configured IP address via the local network and interface selected in the general configuration parameters.
Note that the specified “Ad-Hoc address” will only be reachable when Engineer is started as an Agilicus Launcher and will otherwise not be active when run natively.
Connect to the remote controller with Ad-Hoc address enabled:
![Phoenix Contact PLCnext Engineer with Zero Trust 17 362b09bb 2024 07 12 10 13](https://www.agilicus.com/www/362b09bb-2024-07-12_10-13.png)
Verify connectivity via the Overview panel.
![Phoenix Contact PLCnext Engineer with Zero Trust 18 feef4dff 2024 07 11 15 15](https://www.agilicus.com/www/feef4dff-2024-07-11_15-15.png)