Create new solution in Merbon IDE, assign a PLC and download the configuration. In the PLC properties, we check the network connection IP address, network mask, default gateway and DNS. In the proxy parameters (Network settings – Proxy parameters) we insert the Proxy ID, URL and Keep-alive Interval, which determines how often the PLC will report to the server. Finally, we enable Proxy.
Upload the configuration to the PLC.
Restart the PLC.
After restarting the PLC, upload the project to the PLC and start debugging. In the system status, you will see the status of the proxy server, the number of free slots and the number of occupied slots.
End debugging mode. If you want to use profiles switch you solution to full mode. Create a derived profile from the profile in use. Switch to the derived profile, edit the Parameters for the connection with the PLC -> change the connection type to Proxy. Add the URI and Proxy ID to the connection parameters. Compile the assembly and start debugging.
In the system status is the connection status and you can see that one slot is occupied. All data from the controller is now available in the same way as if we were connected directly to the IP address of the PLC.
If you want to use a proxy connection also in the Merbon Visual mobile application, create a new terminal, e.g. of type External rev. 2.2. Assign a template to it and add a PLC to its terminalChannel.
Now you can compile the terminal, right-click on it and select export definition, then send the resulting zip file to the mobile and open it in Merbon Visual. The mobile application does not support encrypted transmission, therefore the PLC will be set with port 12349 (or 6677 in case of old proxy ID) and the client with port 12348. If we use the user profile in the application, it is necessary to enter the translated address 188.8.131.52 instead of proxy.merbon.cz, or 184.108.40.206 instead of proxy.mervis.info if you are using an old proxy ID starting with PRX2C.