The PLCnext function app easymon removes the hassle of setting up a remote monitoring of your control.
Instead of configuring all the nitty gritty bits and pieces of a cloud-based IoT services, it just leaves you with selecting your PLCnext project variables that you want to monitor on your mobile devices and setting notification thresholds.
This configuration takes place in the easymon configurator that runs on the PLCnext, in order to only propagate data to the cloud for variables that you explicitly selected.
The PLCnext store does a great job in easing the installation and management of Function Extensions on the connected PLCnext controllers. They can be equipped with new features without connecting to each controller individually. After installing easymon, you just need to open the PLCnext IP address in a browser window. This local IP address might be at hand if you just set up the controller but in case it is not, easymon provides a smart feature to detect any PLCnext controller running easymon in the local network without port scanning or network sniffing: The easymon finder
Upon startup, each easymon-equipped PLCnext pings the backend with its own local IP address. The backend updates its lookup list with the PLCnext external IP address that made the request. These two addresses differ as typically the PLCnext is hidden behind a firewall performing NAT and the external IP is the address of the internet gateway of the local network.
If you open a browser window (or a new tab actually as no one seems to open browser windows any more) and head to find.easymon.io, the finder webapp performs an http get request to the backend. As browser and PLCnext are expected to be on the same local network, they both use the same internet gateway and the request shows up at the backend from the same (or a close-by) external IP address. The backend can perform a simple lookup and provide the previously registered local IP addresses that may currently be in use of a PLCnext on the local network (sharing the same gateway with the request’s external IP).
The finder webapp then pings the local IP candidates and eventually gets a response from an easymon instance on a PLCnext as both run in the same network. The response contains device details like the device type and serial number. For each successful response, we can add an entry to the finder’s list of devices as we are sure we can reach the controller on our local network.
Leave a Reply
You must be logged in to post a comment.