RUFUS Help
RUFUS CloudBox
RUFUS CloudBox
  • Introduction to RUFUS CloudBox
  • GETTING STARTED
    • Getting Started with RFID Technology
    • Introduction to Race Timing
    • RFID for Race Timing
    • Networks 101: Understanding the Basics for Race Timing
    • CloudBox Ports & Characteristics
  • PROTOCOL
    • How to Connect to the CloudBox
    • Protocol Commands and Responses
    • Receiving Timing Data Passings During a Session
  • CONNECTIONS
    • Connecting to the CloudBox: LAN, WiFi, and 4G Overview
    • Connecting the CloudBox via Ethernet Cable
    • Connecting the CloudBox via WiFi Access Point
    • Connecting the CloudBox to an External WiFi Network
    • Connecting Two or More CloudBox in the Same Network via a Hub or Router
    • Connecting the CloudBox to a 4G Network
  • Interface
    • Accessing the CloudBox Interface: General Guide
    • Timing Interface
    • Status Interface
    • Configuration Interface
    • Backup Interface
    • GPS Interface
    • Cloud Interface
  • General Operations
    • RFID Reader Configuration
    • RFID Reader Installation
    • Knowing your CloudBox IP Address
    • Boot Sequence
    • Starting and Stopping a Timing Session
    • Accessing Backup Files on the CloudBox
    • Time Synchronization Methods
    • LED Signals and Alarm Notifications
    • Connecting your CloudBox with RUFUS Race Manager (locally)
    • Connecting your CloudBox with Wiclax (locally)
  • ADVANCED OPERATIONS
    • Firmware Update
    • Network Configuration
    • GPS Service
    • Backup Rewind Function
    • IoT Service
    • 4G Modem
  • Cloud
    • Introduction to CloudBox Cloud Service
    • Binding the CloudBox with the RUFUS Cloud Service
    • Accessing Stored Cloud Timing Sessions
    • Connecting your CloudBox with RUFUS Race Manager (remote)
  • Care and maintenance
    • Warning!
    • Battery Care
    • Taking Care of your CloudBox
    • General Recommendations
    • Special Note on UHF Cables
  • Common problems
    • FAQ
    • Common Problems and Troubleshooting
Powered by GitBook
On this page
  • Key Considerations for Connecting Multiple CloudBox
  • Testing the Network
  • 1. Ping Each CloudBox:
  • 2. Check Router Settings:
  • Benefits of Connecting Multiple CloudBox in the Same Network
  • Summary
  1. CONNECTIONS

Connecting Two or More CloudBox in the Same Network via a Hub or Router

When connecting two or more CloudBox in the same network using a hub, switch, or router, several important considerations must be taken into account to ensure seamless communication and avoid network conflicts. This setup is often used for large events where multiple timing points or separate CloudBox are needed to cover different areas of the event.

Key Considerations for Connecting Multiple CloudBox

  1. Unique IP Addresses:

    • Each CloudBox must have a unique IP address on the network to avoid conflicts. Ensure that each CloudBox has a different IP (e.g., 192.168.1.10 for the first CloudBox, 192.168.1.11 for the second, and so on).

  2. Same Subnet:

    • All CloudBox devices and the timing computers or other devices on the network must be in the same IP range and subnet. For example, if your router assigns IPs in the 192.168.1.x range, all devices should follow this format.

    • The subnet mask (usually 255.255.255.0) must be the same across devices to ensure proper communication.

  3. Router or Switch Capacity:

    • Ensure that the router, switch, or hub has enough ports and bandwidth to handle all connected CloudBox units and any other connected devices (e.g., timing computers, backup systems). The switch or router should support simultaneous data transmission to avoid slowdowns.

  4. Firewall and Security Settings:

    • Verify that firewall settings on your network do not block communication between devices. Some routers isolate devices by default, so you may need to adjust these settings.

    • Temporarily disable antivirus or firewall programs on timing computers while troubleshooting, to ensure they are not blocking connections between CloudBox devices.

Testing the Network

After connecting multiple CloudBox units to a hub or router, it is important to test the network to ensure everything is working correctly:

1. Ping Each CloudBox:

  • Determine the IP addresses of each CloudBox by checking your router’s device list or accessing each CloudBox’s configuration.

  • Open the Command Prompt on a device connected to the same network and ping each CloudBox:

    ping 192.168.1.10  # First CloudBox
    ping 192.168.1.11  # Second CloudBox

You should see replies from each IP if the connections are successful.

2. Check Router Settings:

  • Access your router’s management interface and ensure that all CloudBox devices are listed with unique IP addresses. Confirm that there are no IP conflicts or issues with the devices dropping from the network.

Benefits of Connecting Multiple CloudBox in the Same Network

  • Expanded Coverage: Multiple CloudBox units can cover different areas of an event, such as the start line, intermediate checkpoints, and the finish line, enhancing event coverage.

  • Centralized Management: Connecting all CloudBox units to the same network allows for centralized monitoring and management of timing data.

  • Real-Time Data: With all CloudBox devices in the same network, data can be synchronized and accessed in real-time across the event.

Summary

Connecting multiple CloudBox devices in the same network via a hub or router requires careful attention to IP address uniqueness and subnet configuration. Ensure that your network infrastructure can handle the bandwidth and that security settings do not block device communication. Testing the setup through ping commands and monitoring router logs will help ensure a smooth and reliable network connection.

This setup allows for efficient management of large events, with multiple CloudBox units working together to provide comprehensive timing and tracking coverage.

PreviousConnecting the CloudBox to an External WiFi NetworkNextConnecting the CloudBox to a 4G Network

Last updated 8 months ago