How to use HiveOS and Flight Sheets? (Rig configuration)

HiveOS Dashboard Navigation

1. After logging into HiveOS, users land on the main dashboard displaying real-time metrics for all registered mining rigs including hash rate, temperature, fan speed, and power consumption.

2. Each rig appears as a card with its hostname, status indicator (green for online, red for offline), and last seen timestamp.

3. Clicking a rig card opens the detailed rig view where operators can monitor GPU-specific telemetry, review logs, and access console output in real time.

4. The left sidebar provides quick access to sections such as Rigs, Pools, Benchmarks, and Scripts, enabling rapid configuration adjustments without switching contexts.

5. Rig grouping functionality allows administrators to organize hardware by location, model, or algorithm, streamlining bulk operations like firmware updates or overclocking profile application.

Flight Sheet Structure and Purpose

1. A Flight Sheet is a JSON-based configuration template used to define how HiveOS should manage a specific rig or group of rigs.

2. It contains fields for miner selection (e.g., T-Rex, GMiner), pool connection details (URL, worker name, password), device-specific tuning parameters (core clock, memory clock, voltage), and failover logic.

3. Flight Sheets decouple configuration from hardware identity, meaning the same sheet can be applied across identical rigs regardless of MAC address or serial number.

4. Users upload Flight Sheets via the Configuration → Flight Sheets section and assign them to rigs either manually or through auto-assignment rules based on GPU model or BIOS version.

5. HiveOS validates each uploaded Flight Sheet for syntax correctness and compatibility with installed miner binaries before allowing assignment.

Applying Overclocking Profiles via Flight Sheets

1. Overclocking parameters reside under the devices array in the Flight Sheet, where each GPU index maps to a set of tuning values.

2. Valid keys include core, mem, pl (power limit), and fan, each accepting integer values appropriate for the target GPU architecture.

3. HiveOS enforces safety limits: if a core clock value exceeds the GPU’s maximum supported frequency, the system ignores the override and falls back to default clocks.

4. Memory tuning requires careful calibration — aggressive mem values may trigger instability, resulting in rejected shares or kernel panics visible in the rig log tab.

5. Profiles can be tested in simulation mode first; HiveOS renders a preview showing estimated power draw and thermal output before deployment.

Pool Failover and Algorithm Switching Logic

1. Flight Sheets support nested pool arrays with priority ordering, enabling automatic switchover when primary pool latency exceeds 3000ms or share rejection rate climbs above 5%.

2. Each pool entry includes optional algorithm and coin fields, allowing rigs to shift between ETH, ETC, or RAVEN depending on profitability signals from HiveOS’s integrated calculator.

3. Failover timeouts are configurable per pool, ranging from 10 seconds for low-latency stratum endpoints to 120 seconds for geographically distant alternatives.

4. When switching algorithms, HiveOS terminates the current miner process, reloads the correct binary, applies the associated Flight Sheet segment, and restarts hashing within under eight seconds.

5. All failover events are logged with timestamps and reasons, accessible via the Events tab in the rig detail view.

Frequently Asked Questions

Q: Can I use the same Flight Sheet for both AMD and NVIDIA rigs?A: No. Flight Sheets contain device-specific tuning parameters and miner binaries that differ across vendor architectures. HiveOS blocks cross-vendor assignment during validation.

Q: What happens if my Flight Sheet references a miner not installed on the rig?A: HiveOS displays an error during assignment and prevents activation. The rig remains in idle state until a compatible miner is installed or the Flight Sheet is edited.

Q: Do changes to a Flight Sheet automatically apply to already-assigned rigs?A: No. Modifications require manual re-deployment. HiveOS does not push updates silently to avoid unintended downtime or misconfiguration.

Q: Is it possible to export a live rig configuration as a Flight Sheet?A: Yes. From the rig detail page, select Actions → Export Configuration to generate a downloadable JSON file reflecting current settings, overclocking, and pool assignments.