• 04/04/2017
  • Public Content

Helix Device Cloud Management Console

This section contains information on the management console to view device details, create rules and alerts, view device telemetry, and more. To sign in to and access the management console:
  • You must have an
    account on Wind River Helix* Device Cloud to view all of the items mentioned in this section. If you are using a non-administrator account, you may be able to view only a subset until you have administrator access.
Management console
The management console allows you to see the status of devices, create rules and alerts, and more.
Device details
With the management console, you can search for specific devices, view devices by geographical location, and track down which capabilities are available to individual devices.
Using the Device Details screen, you can examine data recorded during custom date ranges, with accuracy down to the minute. Choose between graphical or tabular formats – whichever best helps you analyze your data.
Rules and alerts
You can choose to create an alert, send an email, or forward data based on the rule you create; you can also perform actions on the affected device, such as resetting the device when it overheats.
Custom actions
Custom Actions are a flexible mechanism that enables you to control your device remotely. They can be used to run a script or a program. Once a custom action has been configured it can be used in a rule and is available via RESTful API call.
See the
Application Development section
of the Wind River Helix Device Cloud Agent Programmer's Guide, 2.3 for steps to create a custom action. Afterwards, you can apply an action from the management console to your device.
Dump and retrieve log files
Device Cloud agent basic debugging
  1. Navigate to the Device Cloud management console.
  2. From the
    Custom Actions
    drop-down list, select
    Dump Log Files
    . This dumps the log files on the selected device.
  3. From the
    Standard Actions
    drop-down list, select
    Retrieve Files
    . The log files are transferred from the device you selected earlier to your host computer. These log files are included in a .tar file. The following files are included in the tar file:
    • iot-ccg.log
    • iot-device-manager.log
    • iot-mux.log
    • iot-service.log
    • iot_install_updates.log (if any SW updates were executed)
Device Cloud agent basic debugging (Linux)
If you have release 2.2.2 of the agent or greater, you can use the command
iot-control -q
to get the status of all services in a single command. Use the command
iot-control -v
to confirm the agent release version.
If you have an older version, t
he Device Cloud agent runs as four services on Linux, named as follows:
  • iot-device-manager
  • iot
  • ccg
  • iotmux
Use the systemctl command to start, stop, and get the status of the services. For example:
systemctl status iot
Use the journalctl -u <service name> command to view log files for each service. For example:
To print the last 25 entries:
journalctl -u iot -n 25
To continuously print entries:
journalctl -u iot -f

Product and Performance Information


Intel's compilers may or may not optimize to the same degree for non-Intel microprocessors for optimizations that are not unique to Intel microprocessors. These optimizations include SSE2, SSE3, and SSSE3 instruction sets and other optimizations. Intel does not guarantee the availability, functionality, or effectiveness of any optimization on microprocessors not manufactured by Intel. Microprocessor-dependent optimizations in this product are intended for use with Intel microprocessors. Certain optimizations not specific to Intel microarchitecture are reserved for Intel microprocessors. Please refer to the applicable product User and Reference Guides for more information regarding the specific instruction sets covered by this notice.

Notice revision #20110804