IoT Service
The IoT service (Internet of Things) on the CloudBox plays a key role in remotely monitoring and managing the system. This service allows the CloudBox to continuously send its status and configuration parameters to the Cloud, providing real-time visibility into the system's health and operation. Additionally, the IoT service enables users to perform remote operations such as START, STOP, and SHUTDOWN via the RUFUS Race Manager (RRM) software or their Cloud account. However, it’s important to note that passing information is not transmitted via the IoT service but is instead sent via HTTP to the Passing Ingestion service.
In this article, we’ll explore how the IoT service works, what data is transmitted, and the various remote commands that can be executed.
How the IoT Service Works
The CloudBox uses the IoT service to continually communicate with the Cloud. The main function of the IoT service is to keep the CloudBox’s status and configuration up to date in the Cloud, ensuring that administrators can always view the current state of the device.
Key Features of the IoT Service:
Status Transmission: Every 60 seconds, the CloudBox sends its full status to the Cloud, including details about the system’s battery level, CPU temperature, GPS information, and other important configuration parameters.
Remote Control: Through the RRM or the user’s Cloud account, the IoT service allows the remote execution of critical commands like START, STOP, and SHUTDOWN.
IoT Client Status: The IoT client on the CloudBox manages the connection to the Cloud. The current connection status can be one of the following:
Connected to IoT server: The CloudBox is successfully connected to the IoT server, and status updates are being transmitted regularly.
Disconnected from IoT server: The CloudBox has lost connection to the IoT server and is no longer transmitting status updates.
IoT server connection error: The CloudBox encountered an error while trying to connect to the IoT server. This could be due to internet connectivity issues.
Passing Information: It’s important to note that passings are not sent via IoT. Passings data is transmitted to the Cloud via HTTP to the Passing Ingestion Service.
Remote Commands via IoT
Through the RRM or the user’s Cloud account, the IoT service allows remote control over key operational commands. This is particularly useful for managing the CloudBox from a distance, ensuring flexibility and control during race events or when working in distributed environments.
The following commands can be executed remotely via the IoT service:
START: This command remotely initiates a timing session on the CloudBox, equivalent to pressing the START button on the interface or issuing the START TCP command. Once the session starts, the system begins tracking and transmitting passings data.
STOP: This command remotely stops an active timing session, allowing you to terminate the session from anywhere, provided the CloudBox is connected to the internet. This command ensures a smooth finish to race timing sessions without needing to be physically present at the device.
SHUTDOWN: This command safely powers down the CloudBox system. It is particularly useful for conserving battery or securing the device at the end of an event. The SHUTDOWN process ensures all data is properly saved before powering off.
IoT Service Status and Troubleshooting
To ensure proper communication between the CloudBox and the IoT server, the system regularly checks the connection status. If there are any issues, the system will notify the user through the Status Interface.
IoT Client Status Messages:
Connected to IoT server: This status confirms that the CloudBox is actively connected to the IoT server, and data transmission is occurring every 60 seconds.
Disconnected from IoT server: This status indicates that the CloudBox has lost connection with the IoT server, possibly due to a network issue. Status updates will not be transmitted until the connection is restored.
IoT server connection error: The CloudBox encountered a problem while attempting to connect to the IoT server, typically due to internet connectivity issues. In this case, ensure that the device has a stable connection and troubleshoot network settings if needed.
Troubleshooting IoT Connection Issues:
Internet Connectivity: The most common reason for IoT server connection errors is a lack of internet access. Ensure that the CloudBox is connected to a reliable WiFi network, Ethernet connection, or 4G (where applicable).
Reboot the CloudBox: If the IoT connection cannot be restored, try rebooting the CloudBox, which will refresh the system and attempt to reconnect to the IoT server.
IoT and Cloud Synchronization
The IoT service plays a crucial role in ensuring the CloudBox’s status and configuration are always synchronized with the Cloud. This is especially helpful for large-scale events or multiple timing points spread across different locations, as it allows race officials to monitor and manage all timing systems remotely.
Real-time Monitoring: The IoT service allows real-time monitoring of the CloudBox's health and operational status. Through the Cloud or RRM interface, users can view key metrics such as battery levels, CPU temperature, and GPS location.
Control via Cloud: All status updates transmitted via IoT can be viewed in the user’s Cloud account or through the RRM interface, enabling seamless coordination across multiple devices during race events.
Summary
The IoT service on the CloudBox provides continuous communication with the Cloud, ensuring that users can remotely monitor and control their device. By sending full system status updates every 60 seconds, the IoT service keeps the CloudBox’s operational data synchronized with the Cloud, making it possible to monitor device health and execute remote commands such as START, STOP, and SHUTDOWN.
However, it is important to remember that passing data is not transmitted via IoT but rather through HTTP to the Passing Ingestion service. If the CloudBox encounters any connection issues, users will be notified through the IoT client status, allowing for prompt troubleshooting. By leveraging the IoT service, event organizers and race officials can maintain control over their timing systems from anywhere, ensuring smooth and successful race timing operations.
Last updated