Setting Up Mobile Clients
With the Mobile module installed, you can launch your projects on any modern smartphone or tablet. This ability does not require any re-design of your projects – a mobile Client launches the same projects that the Vision Clients launch.
smartphone or tablet. This ability does not require any re-design of your projects - a mobile client
launches the same projects that the Vision clients launch.
© 2014 Inductive Automation
How it works
Normally, you can't launch Vision Module projects on mobile devices. This is due to the technical
limitation that Java SE (Standard Edition) does not run on mobile devices. The Mobile Module gets
around this limitation by launching the client on the Gateway in a special headless (invisible) mode,
and then using HTML5 and AJAX to show the client's screen on the mobile device's browser.
Typically, the mobile device will connect to the Ignition Gateway via the facility's wireless LAN (802.11)
infrastructure. To launch a mobile client, the mobile device simply connects to the Ignition Gateway by
pointing its web browser to the Gateway's LAN address. It is important to understand that normally,
the traffic is not going over the device's cellular connection. This wouldn't work, because the cellular
connection connects to the internet, and without explicit setup, an Ignition Gateway is not accessible
from the outside internet.
Remote (as in, beyond the reach of 802.11 wireless LAN) mobile access can be enabled through the
same networking strategies that enable remote access for standard Vision clients. Somehow, the
mobile device must be able to access the Ignition Gateway via its cellular connection. One strategy
would be to set up a VPN router and configure the mobile device as a VPN client. This way, the mobile
device could directly access the LAN address of the Gateway as if it were on-site. Another technique
would be to put the Ignition Gateway in a DMZ so that at least one NIC had a public IP address. Or, an
edge router could be configured to port-forward the HTTP and HTTPS ports to the Gateway.
Coordination with your I.T. department would be advised when attempting to set up remote access.
There is very little setup involved with the mobile module. Usually, with the exception of the the Server Address setting, you can keep all the the default settings.
- Go to the Configure section of the Gateway.
- Scroll down and go to Mobile > Settings page.
Here you will see all the settings and shown in the following table:
|Java Path||The path to the Java executable on the Ignition Gateway server machine. The Java 8 JRE is required for the mobile module. The default is java, which assumes that Java 8 is on the path and can be invoked merely with the java keyword.|
|Client Memory||The max amount of heap space allowed for each mobile client VM that is launched. Mobile clients are virtual clients that are launched on the server. All of the work is done on the server and transmitted to the mobile device so keep in mind that more mobile clients means more memory and CPU consumption on the server.|
|JVM Options||Command-line JVM options to use when launching mobile client VM's. Multiple options are separated with spaces. This option is made available mostly for troubleshooting by technical support staff, but if you are familiar with java and comfortable with command-line arguments, you can specify ones you may find useful.|
The environment variables to pass to the mobile client VM process. Use the NAME=VALUE format, one per line.
|Idle VMs||The number of client VMs to startup and wait for incoming mobile connections. These will start when the Gateway is started and sit idle until a mobile connection is made. This should be left at the default value of 0 unless it is taking a long time to launch a mobile client. It's important to note that the VMs that are sitting idle are not connected to a project so it will still take time to load the selected project.|
|Server Address||This is the address to use when launching from the QR code on the launch page. This is a setting that often causes confusion. Initially this value is blank by default which results in the QR code pointing to the address of . Since Ignition is not running on your mobile device, this address will not actually launch the mobile homepage. This should be set to the Ignition server address that can be reached by the mobile device.|
|Callback Port||The port that the mobile Client VMs use to communicate to the Gateway on. The default is 45900, but if this port is already in use, you need to change this to an available port.|
|Callback Interface||The interface that mobile client VMs should use to communicate back to the Gateway on. The default, localhost, makes use of the loopback adapter, however if this host doesn't have a loopback adapter or if there are two network cards, set this to the IP address of the NIC that should be used for local loopback.|
|AJAX Timeout||The max time, in milliseconds, that each request has to complete. The default is 10,000 (10sec).|
The Mobile Module also has an option to allow VNC connections. This allows certain thin clients that do not support the Java Runtime Environment and also do not have an HTML 5 compatible browser to launch Ignition clients. The settings listed under the advanced properties section all have to do with configuring the VNC connection.
|Enable VNC||Allows direct thin-client connection over VNC (also known as, RFB) protocol.|
|VNC Port||The port used for the VNC connections.|
|Project Name||The Mobile module only allows one of the projects on the Ignition Gateway to be viewed through VNC so you have to specify that project here. Unlike the normal mobile launch screen that allows you to choose a project, the project that you specify in this setting will be automatically launched when you connect via a VNC viewer application.|
|Project Width||The width of the project when it's launched.|
|Project Height||The height of the project when it is launched.|
In this section ...