Advanced applications settings

From SpinetiX Support Wiki

Jump to: navigation, search

This page is related to the Control Center interface present on HMP300 and HMP350 devices.

Description

The "Advanced Applications" page of HMP Control Center contains different sections that allows configuring settings related to:

  • interactivity and touchscreens,
  • Network API,
  • streaming and Multiscreen (HMP350 only),
  • NTP,
  • firmware update server address,
  • RPC concentrator,
  • and Pull Mode.

These sections are further detailed below.

Interactivity

Interactivity settings

For HMP200 and HMP130, see Display Settings 3.x page.

This sections allows configuring the following:

  • Maximum rendering latency
    Select the HMP rendering latency value. Default: 1500ms.
  • Accept touchscreen and keyboard events
    Enable / disable interactive event processing. Default: disabled.
  • Limits latency to 60ms when events are received
    Enable / disable interactivity boost. Default: enabled.

Touchscreen

For HMP200, HMP130, and HMP100 devices, see Display Settings 3.x page. See also MultiTouch support section.

Touchscreen calibration settings

Many touchscreens (or other input devices reporting absolute coordinates) are usually already calibrated and require no further configuration to be used. If you notice that the touchscreen is not working properly or it's not very accurate, then you should run the touchscreen calibration procedure:

  1. Connect the HID-compliant touchscreen device to the HMP via the USB port.
  2. Open HMP Control Center > Advanced Applications > Touchscreen.
  3. Ensure that the "Accept touchscreen and keyboard events" option above is checked, otherwise enable this option and restart the HMP.
  4. Press the "Start Calibration" button and follow the instructions displayed on the touchscreen.
  5. Note the calibration offset values displayed on the touchscreen and enter them manually into the XX, XY, TX, YX, YY, and TY input fields within the "Touchscreen" section.
  6. Press the "Apply" button.

Network API

Network API settings

For HMP200 and HMP130, see Network Settings 3.x page.

This sections allows configuring the following:

  • Network API
    Enable / disable Network API server.
  • Port
    Configure the port used by the Network API. Default "1234".

RPC Security

RPC Security settings

For HMP200 and HMP130, see Network Settings 3.x page.

This sections allows configuring the following:

  • Enable RPC request using AJAX (CORS)
    Enable / disable RPC request using CORS.
  • API Key
    The RPC API key protects the HMP against CSRF (Cross-site request forgery) when using CORS (Cross-origin resource sharing).

When doing an RPC request using AJAX from a web page located on another host, i.e. using CORS, an additional query string parameter spx-api-key must be present in the request and the content of the query must be set to the value of the API Key configured above, i.e /rpc?spx-api-key=[rpc-api-key].

Multiscreen

Multiscreen settings

This section is present only on HMP350. For HMP200 and HMP130, see Network Settings 3.x page.

This sections allows configuring the multiscreen ID of the player, which is useful when the HMP is part of a video wall displaying a multiscreen project.

NTP

For HMP200 and HMP130, see Date/Time page.

NTP settings

This section allows configuring up to five NTP servers that the player can use for clock synchronization with UTC.

  • Server 1, ... , Server 5.
    Enter the IP or hostname address of the NTP server.
    Enabling the "Monitor only" option next to a NTP server tells the player to only consult that NTP server, but not use it actively as a time source; this is useful when using an HMP as NTP server for other HMP devices.
  • Pause device at startup to wait for NTP servers by
    Select a delay period from 0 to 150 seconds to increase the boot time of the player in order to insure that NTP servers are started before the HMP.


Note Notes:
  • The NTP statistics page describes the statistics shown on the top of this section.
  • By default the HMP comes configured with a list of public NTP servers from ntp.org. These are fine for regular projects, however, a better accuracy is necessary in the case of running time synchronized projects.
  • An HMP is an NTP server itself and therefore its IP address can be used as NTP server for other HMPs, especially for the case of running synchronized content without an NTP server. The "Monitor only" check box is an advanced options needed this case.

Streaming

Stream Capture

This section is present only on HMP350. For HMP200 and HMP130, see Maintenance page.

In case of problems when streaming video / audio to the HMP, it is possible to capture the stream packets received by the HMP (see the full procedure on the Streaming page) and send that capture to SpinetiX Support to help diagnose the problem and find possible solutions. Be aware that a capture stream might create large files on the device storage and should not be left enabled for a long period of time.

  • To start a stream capture on the HMP, enable the "Capture stream packets" option.
  • To end stream capturing, disable the "Capture stream packets" option.
  • To download a stream capture, click on its link under the "Streaming Captures" section. The capture name starts with "CAP_" and is followed by a series of characters.
  • Remove all the captures stored on the device by clicking on the "Clear Stream Captures" button.

Firmware

For HMP200 and HMP130, see Firmware page.

Firmware update settings

This sections allows configuring the following:

  • Server URI
    Address of the update server. SpinetiX server - depending on the HMP model this could be:
    • HMP350 -> http://download.spinetix.com/hmp350/updates/
    • HMP300 -> http://download.spinetix.com/hmp300/updates/
  • Automatic updates
    Enable / disable automatic update of the firmware from the server
  • Update time
    Time of the automatic update if enabled

RPC Concentrator

For HMP200 and HMP130, see Content Settings page.

RPC Concentrator settings

This sections allows configuring the following:

  • Enable RPC concentrator
    Enable / disable the RPC concentrator.
  • Concentrator uri
    Address of the RPC concentrator.
  • Polling interval
    Frequency at which the RPC concentrator is contacted. Typical values are between 10s and 120s.
  • Notification only
    Check the "Notification only" if you don't want the RPC concentrator to be able to send commands to the HMP. In this case the Concentrator will only receive ready(), restarted() and pull_status() information.

Pull Mode

Pull Mode using local ics file
Pull Mode using remote ics file

For HMP200 and HMP130, see Content Settings page.

This sections allows configuring the following:

  • Settings
    Enable / disable the Pull mode.
  • From uploaded iCalendar file (ics)
    Use this option to control the Pull Mode using an ics file that you have uploaded onto the HMP.
  • From remote iCalendar file (ics)
    Use this option to control the Pull Mode using an ics file that you have uploaded onto a web server.
    Use the option labeled "Check calendar every" to specify the maximum duration after which the HMP must contact the server to find out if the calendar has been updated in the meantime. Note that if the current calendar contains an event during this interval, the HMP automatically checks for updates before executing that event (and restarts the timer).
    The "Schedule URI" field can contain the special notation "[serial]", which is automatically replaced by the HMP serial number - this is useful for cases when the remote calendar is actually generated by a script and is different depending on the HMP requesting it.
This page was last modified on 8 May 2017, at 16:38.