DOCSEARCHbyAlgolia
Submit Docs

Cloudloop Documentation

website·Indexed 32 days ago

https://knowledge.cloudloop.com/

A network and device-agnostic IoT platform for managing Mobile Originated (MO) and Mobile Terminated (MT) messages. Features include Lingo unified message structures, support for SBD (RockBLOCK, 9602/9603) and Pebble protocols, and integrations with destinations such as AWS S3/SQS, Azure Storage/Queue/Service Bus, Google Cloud Storage/PubSub, MQTT, HTTP, and IoT platforms like Blynk, ThingsBoard, and ThingSpeak.

Tokens
41.2K
Snippets
218
Records
297
Agent score
57%

What's inside Cloudloop

  1. Overview of the Things page in CloudLoop UI

    The Things page serves as a central dashboard for managing active 'Things' within a CloudLoop account. It provides two primary views: a comprehensive list of all active Things and a map visualizing their last reported geographical positions.

  2. Overview of the Iridium Edge Solar (IES) Protocol

    The Iridium Edge Solar (IES) protocol is used to exchange positional data, text data, and configuration messages between the Iridium Edge Solar device and the Cloudloop platform. The protocol is divided into two primary directions: Mobile Originated (MO), where the device sends data to the platform, and Mobile Terminated (MT), where the platform sends data to the device. Cloudloop provides decoding and encoding services to abstract the low-level protocol standards into a simplified format for developers.

  3. Overview of the Iridium Edge Solar (IES) Protocol

    The Iridium Edge Solar (IES) protocol is used to transmit positional data, text data, and configuration messages between the Iridium Edge Solar device and the Cloudloop platform. The protocol is divided into two primary directions: Mobile Originated (MO) for messages sent from the device to the platform, and Mobile Terminated (MT) for messages sent from the platform to the device. Cloudloop provides decoding and encoding support to allow users to interact with these messages using a simplified structure without needing to manage the low-level protocol standards.

  4. Overview of Cloudloop Data for IoT Message Management

    Cloudloop Data is a store-and-forward IoT messaging service designed to manage data between satellite devices and the cloud. It provides a unified, device-agnostic message format to standardize data ingress and supports a wide range of transports and platforms. It is the successor to RockBLOCK Admin [Core].

  5. Understand the Lingo Unified Message Structure

    Lingo is the unified message structure created by Ground Control to simplify integration with Cloudloop Data. It represents all messages flowing through the system, regardless of the network, device, or delivery method.

    Key characteristics include:

    • Format: Messages are exposed in JSON format for exchanging data with customers.
    • Contents: Each message contains the message payload, transport-specific metadata (such as device identifiers), and derived information from Cloudloop.
    • Directional Types: There are two types of messages based on direction: LingoMO (Mobile Originated) and LingoMT (Mobile Terminated).

  6. Integrate CloudLoop with ThingSpeak IoT Analytics

    ThingSpeak is a third-party IoT analytics platform used to aggregate, visualize, and analyze live data streams in the cloud. When configured as a destination in CloudLoop (Direction: MO), the platform relays received messages to ThingSpeak in the prescribed format.

  7. Organize Things using Thing Groups

    Thing Groups provide a logical way to organize and group Things within an Account, typically categorized by Project, Site, or Location.

    Key properties of a Thing Group include:

    • Name: A unique identifier for the group (e.g., 'Oceanic Bouys').
    • Icon: An emoji used to visually categorize groups within the Account.

    Behavioral rules:

    • A single Thing can reside within multiple Thing Groups.
    • Destinations are associated with groups to determine how and where data is delivered.
    • Newly enrolled Things are automatically added to the default All Things group.

  8. Understand Thing Channel automatic creation

    Thing Channels are automatically created and reconfigured by the platform when a Thing sends a message for a channel that does not yet exist or is currently misconfigured. Manual pre-creation of channels is not required if the device is configured to send data for new channels.

  10. Supported hardware and networks for CloudLoop

    The CloudLoop platform is network and device-agnostic. It supports a variety of hardware communicating via Iridium SBD, Iridium IMT, or Cellular networks.

    Supported Devices

    • Ground Control Tracking Devices: RockSTAR, RockFLEET (SBD & Cellular), RockAIR (SBD & Cellular)
    • Ground Control IoT Devices (SBD): RockBLOCK, RockBLOCK+
    • Ground Control IoT Devices (Certus IMT): RockREMOTE, RockREMOTE Rugged
    • OEM Modules: Iridium 9602, Iridium 9603, and Generic SBD Devices
    • Third Party Tracking Devices: Iridium Edge Solar

    Supported Networks

    • Iridium SBD (DirectIP)
    • Iridium IMT (CloudConnect)
    • Cellular (TCP/IP) for Ground Control Tracking Devices

  11. RockSTAR Burst Hardware Overview

    The RockSTAR Burst is a handheld personal message receiver utilizing the Iridium Burst® satellite service for global paging. It is designed for outdoor use with a clear view of the sky, though it can penetrate buildings and partial obstructions.

    Key Hardware Specifications:

    • Display: Single color OLED (26 x 35 mm)
    • Input: 5-button keypad and a dedicated 'all message wipe' button
    • Battery: 5300mAh rechargeable battery
    • Connectivity: USB for charging and data transfer
    • Dimensions: 144 x 76 x 36 mm (excluding antenna)
    • Weight: ~305 grams
    • Durability: IP67 rated (dust/water resistant to 1m immersion) and MIL-STD-810G certified for vibration, temperature, and shock.
    • Radio Emissions: Receive-only device; it does not emit radio signals in any state.

  12. Understand the Mobile Originated (MO) Message structure

    Mobile Originated (MO) messages coming from devices into the Cloudloop platform follow a structured format consisting of six top-level fields:

    • ID: Unique platform-generated identifier for the message.
    • Received At: UTC timestamp when the message was first received from the network.
    • Identity: Cloudloop and hardware identifiers (Account, Subscriber, Device, etc.).
    • Header: Transport-specific metadata (SBD, Cellular, or IMT).
    • Message: The raw payload sent from the device in Base64 encoded bytes.
    • Decoded: The interpreted payload, depending on the device type (e.g., P6 for RockSTAR, IOT for RockREMOTE, IES for Iridium Edge Solar).