# \[How to Article\] How to AMR Telemetry Streaming to WEDA Cloud Using Advantech Robotic Suite on Dragonwing™ IQ9 Platforms

**URL:** <https://forum.aim-linux.advantech.com/t/how-to-article-how-to-amr-telemetry-streaming-to-weda-cloud-using-advantech-robotic-suite-on-dragonwing-iq9-platforms/1529>\
**Category:** WEDA Developer Zone\
**Created:** [September 29, 2026, 9:17am UTC](https://forum.aim-linux.advantech.com/t/how-to-article-how-to-amr-telemetry-streaming-to-weda-cloud-using-advantech-robotic-suite-on-dragonwing-iq9-platforms/1529 "2026-09-29T09:17:11Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![phill.liu](https://avatars.discourse-cdn.com/v4/letter/p/a8b319/32.png) [@phill.liu](https://forum.aim-linux.advantech.com/u/phill.liu)\
**Post date:** [September 29, 2026, 9:17am UTC](https://forum.aim-linux.advantech.com/t/how-to-article-how-to-amr-telemetry-streaming-to-weda-cloud-using-advantech-robotic-suite-on-dragonwing-iq9-platforms/1529/1 "2026-09-29T09:17:11Z")

</div>

![1200X627_2](https://us1.discourse-cdn.com/flex016/uploads/aim_linux/original/2X/8/860d6a6ea6458753249dc2ecdc4020f2d5cd79f8.jpeg)

## 1. Introduction

Autonomous Mobile Robots (AMRs) are increasingly deployed in factories, warehouses, and healthcare environments, where operators need real-time visibility into robot status, mission progress, and operational events. While perception, navigation, and control are typically executed locally at the edge to ensure low latency and reliable operation, telemetry data must be securely transmitted to the cloud for centralized monitoring and fleet management.

Advantech’s Dragonwing™ IQ9-based solutions, powered by the Qualcomm Dragonwing™ IQ9075 platform, provide a high-performance foundation for robotics applications with support for Ubuntu 24.04 Pro and ROS 2. Combined with Advantech Robotic Suite and WEDA edge-to-cloud services, the platform enables AMRs to collect operational data and securely stream telemetry, including patrol status, detection events, battery information, and device-health metrics, to the cloud for centralized monitoring and management.

This article demonstrates how telemetry generated by an AMR application can be transmitted from the edge to WEDA Cloud for centralized monitoring and management. The solution combines Advantech Robotic Suite running on the Dragonwing™ IQ9 platform with WEDA edge-to-cloud services to create a complete telemetry pipeline from robot operation to cloud visualization.

What you will learn in this article:

- Build a working AMR application on Advantech’s IQ9-based solution using Ubuntu 24.04 Pro and Robotic Suite.
- Integrate key peripherals, including LiDAR, camera, and motor controllers, and verify sensor and motion data connectivity.
- Enable navigation, patrol, and human detection using Advantech Robotic Suite while processing workloads locally at the edge.
- Register and activate the IQ9 device in WEDA Cloud and obtain a managed device identity (deviceId).
- Deploy and configure the WEDA Sub-Node bridge to upload patrol and detection events as telemetry.
- Verify telemetry data in WEDA Cloud and confirm that events are displayed correctly through the web dashboard.

## 2. Solution Architecture

#### 2.1 Overall Architecture

The solution consists of three layers that enable operational and telemetry data to flow from the robot to the cloud for centralized monitoring and management.

- **Sensor Layer**

- **Computing layer — Advantech Dragonwing™ IQ9-Based Platform**

- **Cloud layer — WEDA Cloud**

#### 2.2 Telemetry Data Flow

During operation, Advantech Robotic Suite generates application events, including patrol status updates, human-detection results, mission states, and device health information. The WEDA Sub-Node bridge subscribes to these messages and converts them into standardized telemetry payloads.

Once received by WEDA Cloud, the telemetry data is stored and made available through WEDA Core services and the WEDA dashboard for remote monitoring, analysis, and operational management.

This architecture minimizes integration effort by enabling Robotic Suite events to be translated into cloud-ready telemetry through a lightweight bridge layer, eliminating the need to modify the core robotics applications.

 ![](https://us1.discourse-cdn.com/flex016/uploads/aim_linux/original/2X/2/221c0860a116a88426bd184ee362c6f03768ebe0.png)

_Figure 1 Three-Layer solution architecture_

## 3. Prerequisites

#### 3.1 Required Hardware

- **1 x Dragonwing™ IQ9-Based Computing Platform**

- **1 x AMR Chassis and Peripheral Set**

- **1 x Wi-Fi**

- **1 x Display**

- **1 x x86-Based Host PC**

#### 3.2 Required Software

The reference environment for this guide is based on Ubuntu 24.04 Pro (Arm64) running on an Advantech Dragonwing™ IQ9-based platform. To ensure compatibility and avoid dependency issues, use the software versions listed below whenever possible.

| Component | Where It Runs | Purpose | Version/ Reference | Download |
| --- | --- | --- | --- | --- |
| Ubuntu 24.04 Pro (Arm64) | IQ9 Edge Platform | Base OS for the platform | Ubuntu 24.04 Pro | [Link](https://docs.aim-linux.advantech.com/docs/utility/bsplauncher/) |
| Advantech Robotic Suite | IQ9 Edge Platform | Provides robot navigation, patrol, and object detection capabilities | ROS 2 Jazzy-based | [Link #1](https://docs.robotic-suite.advantech.com/) / [Link #2](https://docs.ros.org/en/jazzy/Installation/Alternatives/Ubuntu-Development-Setup.html) |
| WEDA Node Activator | IQ9 Edge Platform | Onboards the device and deploys the WEDA Node Agent | V1.1.0\_20260527.1 (Ubuntu-arm64-offline) | [Link](https://learn.advantech.com/zh-tw/weda/docs/Resources/WEDA_Node_Activator_Installer/Download/) |
| WEDA Sub-Node (Docker Container) | IQ9 Edge Platform | Forwards Robotic Suite data to the WEDA telemetry service | Reference implementation used in this guide | [Link](https://learn.advantech.com/zh-tw/weda/docs/Resources/SubNode_SDK/SubNode_SDK) |
| Postman | Host PC | Verifies onboarding status and telemetry data through WEDA APIs | 11.71.7 | [Link](https://www.postman.com/) |

_Note: The procedures described in this article were validated using the versions listed above. Different software versions may require additional configuration, dependency updates, or verification._

After preparing the required hardware and software components, the deployment process begins with installing Ubuntu on the IQ9 platform, followed by Advantech Robotic Suite installation, WEDA onboarding, telemetry integration, and cloud verification.

## 4. Ubuntu Deployment Through BSP Launcher

Instead of manually building and flashing the BSP, the IQ9 platform can be provisioned using Advantech BSP Launcher, a GUI-based tool that downloads validated images and flashes the target board through a guided workflow.

The deployment process consists of the following steps:

1. Install and launch BSP Launcher on the host PC.
2. Select Download Image and Flash, then choose the IQ9075 Ubuntu 24.04 Pro image.
3. Connect the IQ9 platform through USB and switch the board to recovery mode.
4. Confirm that the target is detected and start the flashing process.
5. Reboot the system after flashing completes successfully.

For the full install steps, screenshots, and the guided flashing wizard, refer to Advantech’s BSP Launcher user guide: [BSP Launcher — User Guide | AIM-Linux Developer Center](https://docs.aim-linux.advantech.com/docs/utility/bsplauncher/)

## 5. Install Advantech Robotic Suite / ROS 2

After Ubuntu has been deployed successfully, install Advantech Robotic Suite on the IQ9 platform. The suite provides a simplified installation experience for the ROS 2 software environment used by the AMR for navigation, patrol, and detection workloads. The current release supports Qualcomm-based Advantech platforms running certified Ubuntu 24.04 Pro.

Before proceeding, verify that the target system meets the following requirements:

- Ubuntu 24.04 Pro
- SUSI Driver and WISE-Agent installed
- Minimum 8 GB RAM
- Minimum 8 GB available storage
- Internet connectivity
- English-language operating system

Installation is straightforward:

1. Download the Robotic Suite installer package.
2. Extract and run it, then restart the board when prompted:

```bash
   $ tar zxfv adv-robotic-suite-installer-<version>.tar.gz
   $ sudo ./adv-robotic-suite-installer.run

```

On Ubuntu 24.04, verify success by confirming the Advantech Robotic Suite container has been created.

For the full download link, requirement notes, and verification screenshots, refer to the Robotic Suite basic installation guide: [Basic Installation Guide | Robotic Suite](https://docs.robotic-suite.advantech.com/docs/Software/installation-guide/v1-installation/)

_Remark: For the native ROS 2 Jazzy installation, please refer to [Link](https://docs.ros.org/en/jazzy/Installation/Alternatives/Ubuntu-Development-Setup.html)._

## 6. Robotics Application

The live demo serves as practical evidence of the overall solution architecture. The Dragonwing™ IQ9-based platform interfaces with the AMR peripherals, including LiDAR, motors, battery systems, and cameras, while executing the complete navigation, patrol, and detection workflow locally through Advantech Robotic Suite.

A web-based dashboard visualizes patrol activities, detection results, and device health information in real time, allowing operators to monitor the robot through a standard web browser. The same operational events can also be forwarded to WEDA Cloud, as described in Section 7.

 ![](https://us1.discourse-cdn.com/flex016/uploads/aim_linux/original/2X/b/b23c0fa6f8525357361d6eacbc1ce787069526fd.jpeg)

[![](https://us1.discourse-cdn.com/flex016/uploads/aim_linux/original/2X/c/cff45af7e4e5c1d24cdf8200251dbb0caf7baf21.jpeg "IQ9 AMR live demo") ](https://www.youtube.com/watch?v=YOUwiMo_Fms)

At this stage, the AMR application is fully operational on the Dragonwing™ IQ9-based platform. Navigation, patrol, and human-detection workloads are executed locally at the edge through Advantech Robotic Suite.

While local execution enables autonomous operation, many deployments also require centralized visibility into mission status, detection events, and device health across multiple robots. To address this requirement, the next section extends the solution to WEDA Cloud through a lightweight telemetry integration workflow.

## 7. Extending to the Cloud: Streaming Robot Telemetry with WEDA

The previous sections demonstrated how the IQ9 platform executes the complete robotics workload locally. The next step is to make operational data available outside the robot for centralized monitoring and management.

Using WEDA Cloud, patrol status, mission states, detection results, and device-health information can be streamed from the edge to the cloud without modifying the core robotics application. A lightweight WEDA Sub-Node bridge translates Robotic Suite events into WEDA telemetry and securely uploads them through the WEDA Node Agent.

 ![](https://us1.discourse-cdn.com/flex016/uploads/aim_linux/original/2X/5/50da8d0584059bca33ae9a5075173fc0375f5829.png)

_Figure 2 summarizes the deployment workflow used in this article._

#### 7.1 Connecting the Device to WEDA Cloud

Before telemetry data can be transmitted to WEDA Cloud, the IQ9 platform must be onboarded and activated. This one-time process creates a WEDA-managed device identity (`deviceId`), which is used by all subsequent cloud services.

- Install and start the WEDA Node Activator on the IQ9, and install Postman on the host PC.
- In Postman, select the WEDA environment and set the URL and login variables provided with your account.
- Follow the onboarding requests to retrieve the device’s hardware metadata: its primary MAC address becomes the `deviceId`, and its model becomes the `hwModel`. Add these two variables, then run the activation request.

When the device list returns the new entry with `"status": "Activated"`, onboarding is complete. Keep the `deviceId` — the sub-node bridge in Section 7.3 must use the same value.

 ![](https://us1.discourse-cdn.com/flex016/uploads/aim_linux/original/2X/3/36a3b6157db15b964d7f2d0c19a213f6aaf9949e.png)

_Figure 3 WEDA Cloud onboarding: the IQ9 device appears in the node list as “Activated”_

#### 7.2 Configure the Robotic Application

To generate the patrol and detection events used in this demonstration, build and configure the robot workspace on the IQ9 platform. The application is based on ROS 2 and uses a standard colcon workspace for build and deployment.

Build the robot workspace (skip any packages you do not need for the demo):

```bash
# From the robot workspace root
colcon build --symlink-install --mixin release \
  --packages-skip intra_process_demo

```

If the navigation packages are missing, install them and re-source the workspace:

```bash
sudo apt update
sudo apt install ros-jazzy-navigation2 ros-jazzy-nav2-bringup ros-jazzy-nav2-msgs
source /opt/ros/jazzy/setup.bash
source ~/robot_ws/install/setup.bash

```

At this point, the AMR can navigate on its own, and the patrol application publishes detection events on the `/patrol_detection_events` topic. The bridge forwards a few key fields from each event to the cloud:

- `mission_state` — the robot’s current patrol state (e.g. scanning, idle)
- `location_human_count` — number of people detected at the current location
- `event_id` — a unique identifier for each detection event (uploaded to WEDA as `patrol_event_id`)

#### 7.3 Bridge Robot Telemetry to WEDA Cloud

The WEDA Sub-Node is a small Docker service that maps selected Robotic Suite messages to WEDA telemetry data streams. It is bound to the same `deviceId` generated during the device activation process.

Build and start the sub-node container, then verify that it has been registered with the target device:

```bash
# Retrieve the NATS credentials from the WEDA Node Agent (dmagent),
# and set them in the Sub-Node configuration before building the container:
sudo docker inspect dmagent --format '{{range .Config.Env}}{{println .}}{{end}}' | grep '^NATS_'

# Build and launch the WEDA Sub-Node bridge
docker build -f apps/RobotSubNode/Dockerfile -t robot-subnode:latest .
docker compose up -d

# Confirm the deviceId registered
docker compose logs weda-subnode 2>&1 | grep -i registered

```

With the bridge running, launch the Robotic Suite bridge node so events start flowing to WEDA:

```bash
ros2 launch robot_subnode_bridge subnode_bridge.launch.py

```

You can verify the local node graph with the rqt tool — the bridge node should appear as a subscriber to these ROS 2 topics.

 ![](https://us1.discourse-cdn.com/flex016/uploads/aim_linux/original/2X/3/3905b1608459401cea5c48ec9fd279e4aaefe6d1.png)

_Figure 4 Robotic Suite node graph in rqt: the bridge node consuming patrol/detection topics._

To generate a known value for testing, publish a sample patrol event:

```bash
ros2 topic pub /patrol_detection_events \
  wheeltec_patrol_interfaces/msg/PatrolEvent \
  "{ event_id: 'test-event-001', event_type: 'location_human_count',
     object_type: 'person', mission_state: 'scanning',
     location_human_count: 2, patrol_human_count: 2 }"

```

#### 7.4 Verify Telemetry on WEDA Cloud

From the host PC, use Postman (or the WEDA dashboard) to confirm the data arrived. Verify the following items:

- Node List: Your AMR appears among the registered devices using the deviceId generated during onboarding.
- Sensor Settings — the telemetry names you published (e.g. mission\_state, patrol\_event\_id) are listed for the device.
- Latest Data Stream Value — the most recent value matches what the robot published (e.g. patrol\_event\_id = test-event-001).

If nothing appears in the data-stream list, reboot the device and confirm the sub-node container is running and registered.

#### 7.5 Telemetry Verification Results

With the integration completed, the AMR can operate locally on the Dragonwing™ IQ9-based platform while simultaneously publishing patrol and detection events to WEDA Cloud. The dashboard provides near real-time visibility into robot activity, mission status, and detection results without requiring any modifications to the core robotics application.

 ![](https://us1.discourse-cdn.com/flex016/uploads/aim_linux/original/2X/2/2623effe9d4fd12161b28e0ea046199d252f8800.jpeg)

_Figure 5 WEDA Cloud data-stream latest value confirming the AMR telemetry._

## 8. Troubleshooting

- **Scenario 1: Workspace Build Failure**

- **Scenario 2: Sub-Node Not Registered or No Telemetry Appears in WEDA Cloud**

- **Scenario 3: Device Status Remains “Not Activated”**

- **Scenario 4: Postman Authentication Fails**

## 9. Conclusion

This article demonstrated how an Autonomous Mobile Robot (AMR) can be deployed on Advantech’s Dragonwing™ IQ9-based platform using Ubuntu 24.04 Pro, Advantech Robotic Suite, and WEDA edge-to-cloud services.

By combining local robotics processing with cloud-based telemetry management, the solution enables navigation, patrol, and human-detection workloads to run entirely at the edge while making operational data available for centralized monitoring through WEDA Cloud.

Because the AOM-6741, ASR-A503, and AFE-A503 share the same Qualcomm Dragonwing™ IQ9075 architecture and software stack, the deployment workflow described in this guide can be applied across multiple IQ9-based products with minimal modification.