Advanced applications settings

From SpinetiX Support Wiki

(Redirected from Advanced Applications)
Jump to: navigation, search
Note  
Applies to HMP350, HMP300, and HMP400/HMP400W with DSOS license.

Description

The "Advanced Applications" page of HMP Control Center contains the following sections:

  • Interactivity
  • Touchscreen
  • Network API
  • Webstorage API
  • RPC Security
  • Multiscreen
  • NTP
  • Streaming
  • Firmware
  • RPC Concentrator
  • Pull Mode

Interactivity

Interactivity settings

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

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.

See also MultiTouch support section.

Network API

Note  

This sections allows configuring the usage of the Shared Variables Network API. Starting with firmware 4.3.0, a secure Network API based on RFC8323 (CoAP REST API over TLS-PSK) is available.

Network API settings

For firmware 4.3.0 or later, the following options are present:

  • Enable secure server
    Click to toggle whether the secure Shared Variables server is enabled.
  • Enable legacy unprotected server
    Click to toggle whether the legacy and unprotected Shared Variables server is enabled.
  • Port
    Configure the port used by the Network API. Default "1234".
  • Generate Client Config
    Click to start a wizard that will generate a file to configure clients of this Network API secure server. It will automatically configure the credentials, the default Network API server address and optionally set this player as the time server. You will need to save the generated configuration file and upload it to all players connecting to this "master" player.
  • Upload Client Config
    Click to upload a Network API client configuration generated from a "master" player.
  • Default network API server address
    Enter a Network API server address to be used whenever a Shared Variable doesn't specify one using the @ notation.


Network API settings

For firmware below 4.3.0, the following options are present:

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

APIs Security

Note  
Applies to HMP350 and HMP400/HMP400W with DSOS SYSTEMS license. Added in firmware 4.6.3.
APIs Security settings

From this section, you can configure the following options:

  • Enable CORS requests
    Toggle allowing requests originating from another host to the player's API endpoints (rpc, webstorage) with an API key. This option is deactivated by default.
  • API Key
    The key (automatically generated) to be used for CORS requests, thus protecting against CSRF (Cross-site request forgery) attacks. The API key must be provided with each call as an additional query string parameter, like this: /rpc?spx-api-key={rpcApiKey}.
    If you want to change it, enter a new key and click the "Apply" button.
  • Enable security token access to the Webstorage API
    Toggle authenticating requests on the Web Storage REST API endpoint with a security token, instead of user credentials. This option is deactivated by default.
  • Security Token
    The token (automatically generated) to be be provided with each call through a "Bearer Authorization" header or as an "access_token" query string parameter (like this: /webstorage?access_token={securityToken}).
    If you want to change it, enter a new token and click the "Apply" button.
Note Notes:

Multiscreen

Multiscreen settings
Note  

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

Note  
Applies to HMP350, HMP300, and HMP400/HMP400W with DSOS WIDGETS license (or higher).
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 ensure that NTP servers are started before the HMP.
Note Notes:
  • For the NTP servers to be used, the "Automatic time from Internet (NTP)" option from the System > Date & Time must be enabled.
  • 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 content.
  • 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.

Streaming

Note  
Streaming capture settings
Streaming capture settings before 4.5.0

From this section, you can enable capturing the network packets received by the player in order to debug issues related to streaming and/or the HTTP traffic.

  • Click on the "Capture stream packets" option to start/end a stream capture.
    Reload the page and find a file, which name starts with "CAP_" followed by a unique ID, above this option. Make sure to stop the capture before downloading the capture!
    See the full procedure on the Streaming page.
  • Click on the "Capture http packets" option to start/end an HTTP traffic capture.
    Reload the page and find a JSON file which name starts with "HTTP-player-network", followed by the current timestamp. Make sure to stop the capture before downloading the capture! Drag & drop the HTTP traffic capture into Developer Console > Network tab to analyze the HTTP traffic.
    This option was added in firmware 4.5.0.
  • Click the "Clear Files" button to remove all the capture files.
Note Warning:
Be aware that a streaming capture might create large files on the device storage and should not be left enabled for a long period of time.

Firmware

Note  
Applies to HMP350, HMP300, and HMP400/HMP400W with DSOS WIDGETS license (or higher).
Firmware update settings

This section allows configuring the following:

  • Server URI
    Enter the address of a custom update server.
  • Automatic updates
    Enable / disable automatic update of the firmware from the server
  • Update time
    Time of the automatic update, if enabled. A variable delay is added to prevent multiple requests at the exact same time.

To revert to the default SpinetiX update server address, follow these steps:

  1. Open Operations > Reset
  2. Select the "Firmware updates server" checkbox.
  3. Click the "Clear Selected" button.

RPC Concentrator

Note  
Applies to HMP350, HMP300, and HMP400/HMP400W with DSOS WIDGETS license (or higher).
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

Note  
Applies to HMP350, HMP300, and HMP400/HMP400W with DSOS WIDGETS license (or higher).
Pull Mode using local ics file
Pull Mode using remote ics file

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.

See also

This page was last modified on 7 December 2020, at 21:47.