Cloud Interface

The Cloud Interface in the CloudBox allows users to link their device to a Cloud Account for seamless cloud-based timing and data storage. By binding the CloudBox to the cloud, timing sessions are automatically saved using the Passing Ingestion service, and the CloudBox can be managed remotely through the Race Manager Software. This section of the interface is crucial for users who want to leverage the full cloud-based features of the CloudBox.

In this article, we will explore how to bind and unbind the CloudBox from the cloud and understand what happens when the device is connected to the Cloud Timing Service.

Key Features of the Cloud Interface

1. Device Token:

   • Input for the device token, a unique identifier used for binding the CloudBox to a user’s cloud account.

2. Passings Sent to Cloud:

   • This field shows the number of passings (timing records) that have been successfully transmitted to the Passing Ingestion service for the current session. This helps track how much data is being sent to the cloud.

3. Bind Device:

   • To bind the CloudBox to the cloud, the user must enter the bind token from their Cloud account. This token is generated in the user's Devices portal.

   • Once bound, the CloudBox will automatically transmit timing data to the cloud, allowing remote access and cloud-based race management.

   • Steps to Bind:

     • Log into your Cloud Account.

     • Generate the bind token from the Devices portal.

     • Enter the bind token into the Bind Device field in the CloudBox interface.

     • Click Bind Device to complete the binding process.

4. Unbind Device:

   • This option allows the user to unbind the CloudBox from the cloud. Once unbound, the CloudBox will no longer transmit data to the cloud, and the remote timing features will be disabled.

   • Note: Unbinding the CloudBox does not delete previously transmitted data to the cloud, but will make it inaccessible for the user.

Why Bind Your CloudBox?

Binding your CloudBox to the cloud unlocks several key features that make race timing more efficient and flexible:

1. Cloud-Based Data Storage:

   • The Passing Ingestion service processes and stores passings in the cloud, allowing for detailed analysis and post-event reporting. Users can access the data anytime through their cloud account, enabling flexible race management.

2. Cloud Timing and Race Management:

   • When bound to the cloud, the CloudBox becomes fully integrated with the Race Manager Software, allowing real-time race management, remote timing control, and monitoring.

   • This feature is especially useful for events with multiple timing points or geographically distributed races, as it centralizes timing control.

How to Bind and Unbind the CloudBox

Binding Your CloudBox:

1. Generate a Bind Token:

   • Log into your cloud account and generate a bind token.

2. Enter the Token:

   • In the CloudBox interface, enter the generated token in the Bind Device field.

3. Bind:

   • Click the Bind Device button. The CloudBox will now be linked to your cloud account, and timing data will be sent to the cloud.

Unbinding Your CloudBox:

To unbind the CloudBox, simply click the Unbind Device button. This action will disconnect the CloudBox from your cloud account and disable cloud-based data storage and race management.

Summary

The Cloud Interface is a powerful feature of the CloudBox, enabling seamless integration with cloud services for race timing and management. By binding the CloudBox to your Cloud Account, you gain access to remote timing, secure data storage, and advanced race management features. Through the Passing Ingestion service, all timing sessions are saved in the cloud, ensuring you can access and manage data anytime.

By properly managing the binding and unbinding process, users can ensure their CloudBox operates efficiently and securely within their cloud ecosystem.