Skip to main content
The Innes DMB300 and DMB400 run Gekkota OS and connect to PADS4 through the HTML5 Viewer. This guide walks you through firmware, device configuration, and Viewer installation.

​
Before you begin

Make sure you have:
  • Installed and configured a PADS4 Server. Do this before configuring the device.
  • The device’s factory license number (sent by email when the device was ordered).
  • Network access to the device’s Administration console at http://<device_IP_address>/.
  • Contacted your PADS4 representative to obtain the extra server-side files required for the Innes DMB300/DMB400.
You must install additional software on the PADS4 Server before using the Innes DMB300 or DMB400. Contact your PADS4 representative to obtain and set up these files.

​
Minimum versions

​
First-time access

Both devices expose an Administration console at http://<device_IP_address>/. Default credentials:
  • Username: admin
  • Password: admin
Out of the box, the device plays a Test Card: a chart used to help with configuration. Deactivate it in the Administration console under Maintenance before pushing PADS4 content.
Innes DMB300/DMB400 Administration console

​
Update the firmware

PADS4 supports Gekkota OS 5, so the device firmware must be upgraded to a compatible version. In the Administration console, open Maintenance > Middleware and drop the .frm file into the Drop file here area.
When upgrading a DMB300 to Gekkota OS 5, contact Qeedji Support before proceeding.

​
Configure prerequisite device settings

PADS4 configures most device settings automatically, but a few must be set manually first. Configure them in the order shown. The Administration console will prompt you to validate and reboot as you go. Pull Webdav URL format
  • protocol — http, or https if the server uses a public signed SSL certificate.
  • port — optional. Include only if the PADS4 Server uses non-default HTTP/HTTPS ports.
  • PADS4_server — DNS name or IP address of the PADS4 Server.
  • PADS4_hostpath — the hostpath value configured in PADS4 System Management. Default is PADS4.
Ensure Use this URL for status server and software and configurations installation server is checked.

​
Install the PADS4 Viewer and connect to the server

After the prerequisite settings are saved and the device has rebooted, it automatically downloads the latest PADS4 HTML5 Viewer from your server. This can take a few minutes. Once the Viewer starts, it connects to the PADS4 Server. You can then manage Viewer settings such as screen orientation from PADS4 Agent.

​
Adjust Viewer settings on the device

To open the on-device options screen, hold the left mouse button (or touch the screen) for 3 seconds.
Because of resource limits on both devices, operating the Viewer settings on-device is not fully supported. Prefer PADS4 Agent for configuration.

​
Updating the Viewer

After the initial install, upgrading the PADS4 Server automatically triggers the Viewer to update to the matching version.

​
Install the Viewer with a script (advanced)

For programmatic setup, which is useful when configuring many devices, you can install the Viewer with a JavaScript configuration script that ships with the PADS4 Server. The default script location on a PADS4 install is:
Modify the script following the guidance in the file, then upload it to the device with a WebDAV client. For Windows we recommend WinSCP. Upload with WinSCP
  1. Start WinSCP and wait for the Login dialog.
  2. Select the WebDAV file protocol.
  3. Enter the device’s IP address (default port 80).
  4. Enter the device username and password (see First-time access).
  5. Select Login and wait for WinSCP to connect.
  6. In the left pane (local filesystem), navigate to the PADS4 apps directory.
  7. In the right pane (device), navigate to /.extension.
  8. Drag configuration.js from the left pane to the right.
WinSCP also supports automated file transfers via scripting, which is helpful when provisioning many devices. Contact Qeedji Support for guidance.
When using an automated script, add a wait time of at least 5 seconds between devices to avoid overloading the PADS4 Server.

​
Supported features