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.
See the Mobile Module for more information.
4.13.1 Mobile Module Settings
There is very little setup involved with the mobile module. Usually the default settings should suffice
with the exception of the Server Address setting.
This is the path to the Java executable on the Ignition Gateway server machine. The Java 7 JRE is
required for the mobile module. A default value of “java” assumes that Java 7 is on the path and can be
invoked merely with the “java” keyword.
The amount of space allowed for each mobile client 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
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 then you can specify ones
you may find useful here.
Here you can specify any environment variables in the format of NAME=VALUE.
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.
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 http://localhost:8088. 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.
The port that the VMs use to communicate to the Gateway on. By default this is set to 45900, but if
this port is already in use then change this to an available port.
The interface that mobile client VMs should use to communicate back to the Gateway on. By default
Gateway Configuration 155
© 2014 Inductive Automation
this is localhost and 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
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.
Allows direct thin-client connection over VNC.
The port used for the VNC connection
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.
The width of the project when it's launched
The height of the project when it is launched