Starting, Pausing, and Stopping a Timing Session

The CloudBox provides multiple ways to manage a timing session, offering flexibility in how events are timed. Whether through the CloudBox Interface, hardware buttons, TCP socket commands, or the IoT service, the system ensures accurate and efficient session management.

The CloudBox also introduces a Pause option, which temporarily suspends recording without creating a new session. This allows operators to halt passings momentarily without generating extra backup files or splitting sessions.

In this article, we’ll explore the different ways to start, pause, and stop a timing session, the internal processes triggered during these actions, and the commands affected while a session is active.

Ways to Start a Timing Session

  1. Via the CloudBox Interface:

    • The most common way to start a timing session is by pressing the START READS button in the CloudBox web interface. This action begins the session, enabling the CloudBox to start reading and transmitting RFID tag data.

  2. Using the Start Button on the CloudBox:

    • Pressing the Start Button on the physical CloudBox also initiates a timing session. This is useful in scenarios where access to the web interface is not immediately available.

  3. Via TCP Socket Command:

    • You can also start a session through a TCP socket connection by sending the START command. This method allows for integration with external systems or custom applications that control the CloudBox remotely.

  4. Through the IoT Service:

    • If the CloudBox is connected to the Cloud Service, a session can also be initiated remotely from the cloud. This allows race managers to start sessions from anywhere with internet access, without physically interacting with the device.

Internal Processes During Session Start

When a timing session starts, several key operations are triggered within the CloudBox to ensure data accuracy and reliability:

  1. Session Creation in the Cloud:

    • The CloudBox connects to the Passing Ingestion service, creating a new session that logs all incoming timing data. This ensures real-time tracking and cloud-based storage for post-event analysis.

  2. Backup File Creation:

    • A local backup file is created on the CloudBox, ensuring all passings are saved even if internet connectivity is lost. This file is essential for data integrity and recovery.

  3. Data Transmission to TCP Clients:

    • Any connected TCP clients will start receiving real-time timing data (passings). The CloudBox transmits the tag reads to all clients connected via TCP.

  4. Counter Reset:

    • All session-related counters (e.g., passings count) are reset to zero to ensure accurate data collection for the new session.

  5. Buzzer Activation:

    • The CloudBox will emit a start signal via the buzzer to notify race officials or timing personnel that the session has begun.

  6. LED Indicator Changes:

    • The Start LED on the CloudBox changes to blue to visually indicate that a timing session is in progress.

Possible Responses After Starting a Session:

  • START_MODE: Indicates that a session has already started.

  • READERNOTOK: The RFID reader is not detected.

  • DEVICE_INTEGRITY_FAILED: The CloudBox integrity check failed.

  • INVALIDREADERMODEL: The connected reader model is unsupported.

  • ERRREADER: There’s an issue with the reader.

  • ERRCONNECT: Error connecting to the reader or network.

  • OK: The session started successfully.

Commands Affected During a Timing Session

Once a timing session is active, the majority of configuration commands are ignored to avoid disruptions during the session. Commands that cannot be executed during a session include:

  • Reader configuration commands (SETREADERPORT, SETREADERMODEL): You cannot change the reader’s port or model during a session.

  • IP address changes (CHANGESYSTEMIPADDRESS): Network changes are blocked to ensure continuous connectivity.

  • Date/time sync changes (SETSYSTEMTIME, SETDATETIMESYNC, CHANGETIMEZONE): Any changes to time-related settings are ignored.

  • System shutdown and restart commands (SHUTDOWN): The system cannot be shut down or restarted during a session.

These commands will return a START_MODE response, indicating that they cannot be executed while a session is active.

Pausing a Timing Session

The Pause feature allows operators to suspend passings without ending the session.

  • Via the CloudBox Interface: Click Pause to temporarily stop recording passings.

While paused:

  • No new passings are logged or transmitted.

  • The session remains open, preventing creation of new backup files or sessions when resumed.

  • Resuming is done by pressing Start again, continuing from the same session.

Use case: Pausing is ideal if you need to temporarily block passings (e.g., for setup, maintenance, or a break in the race) without fragmenting event data.

Ways to Stop a Timing Session

  1. Via the CloudBox Interface:

    • To stop a timing session, press the STOP button in the CloudBox interface. This ends the session and initiates the data-saving processes.

  2. Using the Stop Button on the CloudBox:

    • Pressing the Start Button again on the CloudBox will stop the session, making it a quick way to end a session without accessing the web interface.

  3. Via TCP Socket Command:

    • Send the STOP command through the TCP socket connection to remotely stop the session.

  4. Through the IoT Service:

    • The session can also be stopped remotely through the Cloud Service, giving race managers control over the session from anywhere with internet access.

Internal Processes During Session Stop

Stopping a timing session triggers several operations to ensure the safe storage and transmission of the session’s data:

  1. Cloud Session Closure:

    • The active session on the Passing Ingestion service is closed, finalizing the race data for cloud storage.

  2. Queue Cleanup:

    • Any remaining passings in the data queue are processed and sent to connected clients before the system stops reading tags.

  3. Buzzer Activation:

    • The stop signal is emitted via the buzzer to alert personnel that the session has ended.

  4. Global Counter Update:

    • The global passings counter is incremented, ensuring that cumulative data for all sessions is maintained.

  5. LED Indicator Changes:

    • The Start LED returns to red, indicating that the session has ended and the CloudBox is no longer reading tags.

Possible Responses After Stopping a Session:

  • READERNOTOK: The RFID reader is not detected or disconnected.

  • INVALIDREADERMODEL: The connected reader model is unsupported.

  • ERRREADER: There’s an issue with the reader.

  • ERRCONNECT: Error in network connection.

  • OK: The session stopped successfully.

Summary

The CloudBox now supports starting, pausing, and stopping sessions with flexibility across the interface, hardware, TCP commands, and IoT.

  • Start: Creates a new session and begins logging passings.

  • Pause: Suspends logging without ending the session, avoiding fragmentation of backup files.

  • Stop: Closes the session, finalizes data, and ensures safe storage.

By understanding these functions, operators can manage timing sessions efficiently while preserving data integrity and adapting to event needs.

PreviousBoot SequenceNextAccessing Backup Files on the CloudBox

Last updated