Amino A540 Release Notes

Technical documents, including Release Notes and How-To guides.

Amino A540 Release Notes

Postby Cilutions Support » Fri May 06, 2011 11:29 am

Release Summary

Current Release: 2.2014
General Release: Yes
The following package consists of release notes and basic operational procedures for the Enterprise AmiNet540 Receiver (Version 2.2014).

February, 2014

Packages Included: Enterprise AmiNet540 Receiver (v2.2014)

Product Specification:

What's New

1) Support for either the HTML5 Opera Browser or Digital Media Bridge (DMB) Screen Manager on the TV display.

2) A new HTML4 Browser asset included with the DMB Screen Manager.

3) Support for Wireless USB Dongle. Includes both the Amino-supplied 3x3 MIMO USB and the C.Crane Super USB designed for outdoor use over long distances (e.g., stadium deployments).

4) Support for many containers for h.264 video files: mkv, avi, mov, mpg, ts, flv, m4v and more.

5) Support for auto-recovery or reflashing an A140 with a factory default image.

6) Support for music-only playback. The video asset now supports an audio URL (e.g., mp3://...) for audio playback and no display.

7) Support for auto-format of the internal HD at boot-up, if necessary. The image is installable and usable on an A540 right from the factory with no extra operational procedures needed to prepare for deployment.

Installation & Configuration : Installation

Installable images: mc2_540_2014_02_24.mcfs

The image is typically pre-installed in the factory but can also be upgraded in the field. Contact for field upgrades.

Installation & Configuration : Configuration

Basic and advanced Amino configuration values (e.g. the IP address) can be set using telnet to log into the Amino STB as follows:
1) telnet <IP of AmiNet540>
2) login: root
3) password: *********
4) Follow procedures as described in the Amino STB management Configuration Guide (Version 116)

Secondary IP Address:
A second, well-known, IP address for the A540 network interface is permanently configured and can be used to telnet to the A540 to inspect/repair an STB with mis-configured primary IP address settings. The secondary IP settings are:
Static IP :
Subnet Mask :

Browser Based Configuration

The following fields are settable via the Amino Configuration page on the A540. This page can be accessed either by directly entering the URL in your web browser:

http://<IP of AmiNet540>

General Settings
ID - An optional field which a user can set to identify the STB (e.g., A540_1). Can be up to 100 characters long.
Description - An optional field which a user can set to include additional information about the STB (e.g., Aminet540 in the Lobby). Can be up to 200 characters long. Note: when this field's value is the zip code of where the box is located, a user can include local weather updates on their digital signage screens.
Screen Manager - Can be Digital Media Bridge or the classic Opera HTML browser.

Network Settings
Use DHCP (Y/N) - Use Dynamic IP Assignment
IP Address - The Static IP if DHCP is N
NetMask - The network mask (e.g., if DHCP is N
Gateway - The IP of the gateway out of the local subnet (e.g., if DHCP is N
Time Server - The IP or Domain Name of an optional time server
Time Zone - STB local time zone

Wi-Fi Settings
This section only applies to STBs configured to work with the Amino USB Wireless Dongle.

Region - The correct region must be set for the dongle to work. Each country defines its own set of Wi-Fi frequency bands. STBs that do not have a wireless region set will not be able to use wireless.
SSID - The public name for the Wi-Fi network access point.
Security Type - The type of security used on the Wi-Fi network.
Security Key - Sometimes referred to as a Wireless Key it is a case sensitive 32 alphanumeric character string necessary to connect the STB to an available Wi-Fi network (SSID).

EPD Settings
EPD Site ID - The 8 character siteid used to identify this receiver for multicast file reception
EPD Public IP Address - The public multicast IPMC:Port (e.g., to tune for multicast file reception. Consult with the PDSender administrator for this setting.
Delete on unregister - One will automatically delete a locally cached file when the Multicast Sender unregisters it, zero will leave it on the local STB. This is useful for automatic hard drive clean-up.
File Checkpoint Freq (sec) - How often to "checkpoint" files-in-progress during reception. Such checkpointing is useful to recover any partially received files when an STB reboot occurs. This feature is especially useful on multicast networks where file retransmissions should be avoided. Zero disables checkpointing.

SNMP Settings
This section only applies to STBs configured to work with the DMB SNMP Proxy Server, a separate Cilutions' product. This
configuration supports SNMP management of STBs deployed over the Internet or in a network where the STBs are not directly accessible by an SNMP Manager. Refer to the network administrator to determine if these values need to be set.

SNMP Engine ID - A user-defined field which uniquely identifies the STB in the network. By default this is the serial no of the STB.
SNMP Proxy IP - The IP address of the server where the DMB SNMP Proxy Server is staged.
SNMP Proxy Port - The Port address of the DMB SNMP Proxy Server.
SNMP Heartbeat Freq (sec) - How often the STB should send heartbeat messages to the DMB SNMP Proxy Server. Refer to the network administrator to set this value. It is typically determined by the NAT timeout settings in the routers between the STB and the DMB SNMP Proxy Server.
SNMP Local Port - The local UDP Port used by the SNMP agent on the STB. Set this value only to override the default of 161.

Telnet Settings
This section only applies to STBs configured to work with Cilutions' DMB Telnet Proxy Server, a separate product. This configuration supports telnet access to STBs deployed over the Internet or in a network where the STBs are not directly "telnet" accessible by a support engineer. Refer to the network administrator to determine if these values need to be set.

Telnet Agent ID - A user-defined field which uniquely identifies the STB in the network. By default this is the serialno of the STB.
Telnet Proxy IP - The IP address of the server where the DMB Telnet Proxy Server is staged.
Telnet Proxy Port - The Port address of the DMB Telnet Proxy Server.
Telnet Heartbeat Freq (sec) - How often the STB should send heartbeat messages to the DMB Telnet Proxy Server. Refer to the network administrator to set this value. It is typically determined by the NAT timeout settings in the router(s) between the STB and the DMB Telnet Proxy Server.

FTP Settings
This section only applies to STBs configured to work with an FTP Server (e.g., FileZilla) to periodically "pull" content onto the local STB. Refer to the network administrator to determine if these values need to be set. Note that this method can be used in conjunction with other file reception methods (e.g., multicast reception and FTP "push" [where an external machine FTPs into the local STB and "puts" files in the local /PVR directory - see the DMB Screen Builder documentation for more information]).

Video Settings
Video Resolution - Corresponds to the local TV capabilities.
Graphics Resolution - Also corresponds to the local TV capabilities (e.g., 720 HD images will render on a 1280x720 TV).
Video Output - Corresponds to the physical video connectors on the STB; like HDMI, SVideo, Composite, etc.
Enable RF - Controls whether or not to enable or disable RF output on the Composite connector.
RF Channel - Select Channel 3 or 4 if RF is enabled.

Operator Considerations

The default configuration for this release of the AmiNet540 is as follows:

Default configuration:
Site ID: <last 8 digits of the box's serialno>
GFX Resolution: HD720
Video Output Resolution: HDMI+YPbPr+Composite

Video streams and files can be sent to the AmiNet540 STB using the DMB Sender. Reference the DMB Sender documentation for instructions on how to register content.

The Digital Media Bridge Screen Builder is a Windows application useful for building screens playable on the AmiNet540. Reference the Screen Builder User's Guide for more detailed information. Assets and configuration data built using the DMB Screen Builder application can be loaded to an AmiNet540 in any one of the following ways:

1) Publishing the file set to a multicast file distribution application, like DMB Sender, for "push" distribution to one ore more A540's
2) Publishing the file set to a unicast file distribution FTP Server for "pull" distribution to one or more A540s. See the Setup FTP Server section elsewhere in this document
3) Publishing directly to an A540 using the built-in FTP client in the Screen Builder application
4) Placing the file set on a Flash Drive and inserting the drive into the USB port on the A540. The operator should view the activity LED on the Flash Drive to determine when it is safe to remove.

Graphics Resolution

The A540 supports both standard (480p) and high (720p) definition graphics resolution. HD graphics offers 1280 pixels across and 720 pixels down the screen. This allows for higher quality image display. The graphics resolution will determine how all of the assets are built and positioned on the screen. For example, with a standard graphics resolution a background image for the screen will be 720x480. Also, a quarter screen size video will be 360x240. However, with a HD graphics resolution a background image will be 1280x720 and a quarter screen size video will be 640x360.

Management and Control

The SNMP MIB for this product, provided separately, is named: AMINO-540-MIB. The SNMP agent in the AmiNet540 supports these standard MIBs:
- RFC1213
- Host Resources

Refer to the AMINO-540-MIB for the list of SNMP variables unique to the A540 application.

The SNMP Write Community is "public" and the Read Community is "public". The AmiNet540 MIB is needed by an SNMP Manager application to monitor and control an A540 platform. A recommended freeware SNMP MIB Browser is available at

The optional SNMP Proxy Agent in the A540 is enabled and configured using the Web Browser-based interface described elsewhere in this document. By default, this feature is disabled and the AmiNet540 supports direct SNMP connectivity to the SNMP Manager. That is, each AmiNet540 has a unique IP address which is configured in the SNM P Manager. The SNMP Proxy Agent supports NAT'd connections where the AmiNet540 may be on a local LAN with, say, Internet connectivity to the SNMP Manager. In this case the SNMP connection between each AmiNet540 must be routed through an SNMP Proxy Server in the Network Management Center. To enable this connection the operator should set the SNMP Proxy IP, Proxy Port and Heartbeat Frequency to values specified by the network administrator.

Like the SNMP Proxy Agent the Telnet Proxy Agent offers network management connectivity on a NAT'd network. To enable this connectivity the user should configure /PVR/pdreceiver/tunnel.cnf, using the "vi" editor, and set the PROXY_IP, PROXY_PORT and PUNCH_FREQUENCY_SEC values as directed by the network administrator.

Configure Using a USB Keyboard
An STB in Opera Screen Manager mode (see General Settings) supports configuration through a locally attached USB Keyboard, for input, a local TV for output. This mode supports the Amino Management Pages and the Amino Preferences Pages offering review and management of basic Amino configuration settings. Contact for detailed documentation for each Amino STB model.

Note: A local user can force the STB to boot-up in Opera Screen Manager mode (and override the DMB Screen Manager Setting) by pressing F7 during the boot sequence of the STB. This is a convenient way to review configuration settings independent of any network connections (e.g., useful, as an example, when first setting up a W-Fi connection, before any network connectivity has been established).

The Amino configuration pages are invoked as follows:

    Alt-P: Preferences Pages. No password required.

Setup FTP Server

The A540 supports automatic FTP file retrieval (i.e., pulling content from an external FTP Server). This feature is optional and is configured through the Browser Based Configuration section discussed elsewhere in this document. If enabled, the A540 will periodically attempt to connect and login to the configured FTP Server.

The FTP Server can be any one of a variety of 3rd party applications (e.g., Filezilla). The installation and configuration procedures for the FTP Server are specific to the particular application selected for use and, as such, are beyond the scope of these release notes. The A540 can operate with an FTP Server which supports either of the following modes:

Unencrypted file transfers with no security (i.e., in the clear). This method typically applies to private networks which are already secure so there is no need to add additional security for file transfers.


FTPS (also known as FTP Secure and FTP-SSL). This method, which is commonly used for Internet-based file transfers, involves installation of a public-key authentication certificate at the FTP Server. If configured, the A540 will operate as an FTPS client to accomplish file transfers with the FTPS Server.

Note that configuring the FTPS Server involves network configuration, especially for environments where the FTPS Server is behind NAT'd devices, router and firewall issues and private keys and certificates. It is recommended that configuring the FTPS Server (e.g., Filezilla Server) be performed by a network administrator familiar with these technologies.

There must be an FTP account which corresponds with the account name and password as specified in the FTP Settings through the A540(s) Web Browser configuration. There must be at least one <home> directory underneath the root directory for this account. Each <home> directory corresponds to a content "group" used to store any and all files relevant to the group. For example, all files destined to the A540s deployed in a particular geographic location. The home directory name also corresponds to the FTP Settings in the A540(s) Browser Based Configuration.

The following describes the directory subtree used to support a <home> directory named "Content":
<root> - The current directory after a successful login
<root>/Content - The repository of all files to be retrieved by all A540s configured to use this FTP Server for content acquisition. Note that this is often the same directory where the Screen Builder (a separate DMB application) publishes all content and metadata destined for one or more A540s.
<root>/Content/<specificA540> - An optional subdirectory with files for a particular A540. By default the A540 is identified by its unique serial number (found on the outside of the box). For example, an A540 with a serial number of B50410G000142 would correspond to directory: <home>/Content/B50410G000142. Here the user can place content unique the specific A540. In addition, the A540 will use this directory, if present, to place its playback logs for optional user review.
<root>/Content/siteid - A special purpose location to support sites without serial number identifiers (e.g., Windows-based players)
<root>/Content/upgrade - Software upgrade images applicable to all A540s tuned to this FTP Server, login account and <home>. The A540 will automatically retrieve any upgrade images needed and reboot to apply.
<root>/Content/log - Log files from individual A540s
Cilutions Support
Site Admin
Posts: 139
Joined: Mon Feb 07, 2011 3:03 pm

Return to Documents

Who is online

Users browsing this forum: No registered users and 1 guest