EmbedOne EMI Web Client User Guide

September 14th, 2009 Leave a comment Go to comments

Installation

The EmbedOne EMI Web Client is provided as a package of javascript-enabled HTML files that can be run on a local computer and connect to a remote EMI Server residing on an remote system such as embedded board.

To install the EmbedOne EMI Web Client, select a location on your hard drive and uncompress the EmbedOne EMI Web Client package there.

Starting EmbedOne EMI Web Client

After installation, you can start the EmbedOne EMI Web Client by opening the index.html with a web-browser.

After opening the html page, you are presented with the following screen.

EMI Web Client Login

EMI Web Client Login

Type in the host (either domain name or IP address), user name and password to open a connection. The default username and password for EmbedOne Linux is “root” and “admin”. After logging on to the system, you will be presented with the system configuration dialog.

System Configuration Edit Dialog

The System Configuration Edit dialog allows you to edit the system settings that are saved on the unit.

EMI Web Client Configuration Edit

EMI Web Client Configuration Edit

On top of the configuration page, you will see the remote system IP address, hostname and the version of installed EMI Server (emid). The tabs allow you to navigate to other pages, such as statistics. Below the edit box are buttons to save the changes for later activation or apply the changes that have been made. To review changes before applying them, click on the “Review Changes” tab.

For documentation on the purpose and syntax of different configuration keys of the key=value pairs, see EMI.CONF Keys Field Guide.

Changing System Settings

The settings are presented as key=value pairs. A setting can be removed from the system by simply deleting it and new settings can be added by inserting new lines. To modify a setting, just change the value after the equal (‘=’) sign.

Example snapshot of IP configuration:

ip=""
ip.addr=""
ip.addr.br0=""
ip.addr.br0.1=""
ip.addr.br0.1.local=192.168.2.1
ip.addr.br0.1.prefixlen=24
ip.addr.eth0=""
ip.addr.eth0.1=""
ip.addr.eth0.1.local=192.168.1.2
ip.addr.eth0.1.prefixlen=24

To save the changes, click on the save button. You will be taken to the review changes screen.

EMI Web Client Configuration Review

EMI Web Client Configuration Review

On the review changes subtab of the Configuration tab, the changes that have been saved but not applied are visible in “changes”. Blue color means changed setting and green a completely new one. Red color text with strikethrough is a removed setting. You can review the changes before applying or discard them. You can also save the configuration to permanent flash memory by clicking the “Flash Configuration” button.

Statistics

After clicking the “Statistics” tab you will be presented with system statistics.

EMI Web Client Statistics

EMI Web Client Statistics

The statistics are displayed as key=value pairs similar to system configuration, but can not be edited. Statistics may change without user interaction from time to time depending on the system state.

NOTE! Depending on the system configuration, some of the statistics, such as wireless LAN measurements, may require some time to retrieve from the system on the first time the statistics page is accessed or later refreshed.

Bug Reporting

EmbedOne Web Client contains integrated bug reporting facility to send a bug report to EmbedOne.

EMI Web Client Bug Reporting

EMI Web Client Bug Reporting

When the “Attach logs” option is enabled, the configuration of the device and statistics are also sent together with the bug report.

Custom Request

From the custom request tab, you can send any EMI-RPC request to the node.

EMI Web Client Raw EMI-RPC Interface

EMI Web Client Raw EMI-RPC Interface

The main purpose for the custom request is to provide an easy-to-use interface for testing EMI-RPC protocol. For more information about EMI-RPC protocol and the supported methods and parameters, please see EMI-RPC API Documentation.

  1. No comments yet.
  1. No trackbacks yet.