Chapter 01

HashLink is an energy management system for mining hardware. It continuously adapts the miners’ power to the energy that is actually available.

Once per second, HashLink reads the available surplus from the inverter, grid meter or battery system. When production rises, the miners ramp up. When it falls, HashLink reduces their power. The miners are not controlled individually by hand: HashLink takes over their control completely.

  1. 01Launcher

    Starts and monitors all services.

  2. 02Core

    Reads the energy, makes decisions and controls the miners.

  3. 03Dashboard

    Shows live values and provides the user interface.

  4. 04 · OptionalRFID service

    Enables login with a card.

Important: All components are supplied as one system. In normal operation, no individual programs need to be installed or started separately.

Chapter 02

Key terms

You will come across these terms throughout the interface. Once you can tell them apart, you will quickly find your way around.

  • EMS

    Energy source

    Inverter, meter, battery or interface from which HashLink reads the power currently available.

  • MIN

    Miner

    A mining device in the local network with an IP address, access details, minimum and maximum power and a priority.

  • PRO

    Profile

    The strategy for the entire miner fleet: optimised for the available energy or with a fixed power.

  • STB

    Standby

    Pauses all miners while the controller and the interface keep running.

  • PRI

    Priority

    Determines which miners receive energy first. Priority 0 is the highest.

A preset and a profile are not the same. A preset describes a particular miner type and how it is controlled technically. A profile describes the strategy of the entire installation.

EcoHash systems: Immersion-cooled installations show additional sections for cooling, PLC and cassettes. With standard installations, these terms can be ignored.

Chapter 03

The launcher starts Core, Dashboard and optionally RFID in the right order and monitors their state.

Normal start

  1. Switch on the controller and wait for it to boot.
  2. The launcher starts automatically. With a manual software installation, double-click launcher.exe.
  3. Wait a few seconds until Core and UI show the status “Running”.
  4. Open the dashboard and log in.

Close or quit completely?

  • X

    Close the window

    The launcher is only minimised to the notification area next to the Windows clock. All services keep running.

  • OFF

    Use Quit

    Shuts down Core, Dashboard and RFID in a controlled way. Only use it if the entire system is to be shut down.

Chapter 04

Logging in

The lock screen protects the settings and operation. A public system summary may be visible before you log in.

  • 01

    Backend address · first start only

    If asked, enter the address of the Core, for example http://192.168.1.50:8080, and test the connection.

  • 02

    Username and password

    Tap the screen, enter the access details and select “Log in”.

  • 03

    RFID card and password · optional

    Hold the card to the reader and then enter the matching password.

  • A session is logged out automatically after about one hour.
  • Too many wrong attempts lead to a short lockout.
  • Usernames and passwords must have at least four characters.
  • Only administrators can manage users and change miner presets.

Remote access and the HashLink login are separate. RustDesk opens the controller's desktop. Only after that do you log in to the HashLink interface.

Chapter 05

The header and the taskbar stay the same on all main pages. From there, every area of operation can be reached.

  1. 01Logo and clock

    Lead back to the homescreen from sub-pages.

  2. 02Notice island

    Opens pending messages and warnings.

  3. 03Live values

    Total power, hashrate and highest temperature.

  4. 04Power

    Switches between active operation and standby.

  5. 05Settings & scheduler

    Configuration, profiles and schedules.

  6. 06Statistics, errors & users

    Measurements, system status and account menu.

Chapter 06

The homescreen

The main view brings together the active profile, the energy flow, the installation’s values and the state of every miner.

  • Active profile and schedule: top left.
  • Energy flow: direction and speed of grid, battery and miners.
  • Installation values: available energy, power consumption, hashrate, battery flow and state of charge.
  • Miner tiles: name, status, preset, IP, priority, power range as well as live power, hashrate and temperature.
Colour Status Meaning
Green Running The miner is running normally.
Grey Disabled The miner is deliberately switched off or not active.
Yellow Starting The miner is ramping up.
Orange Stopping The miner is being shut down in a controlled way.
Red Error The miner cannot be reached or cannot be controlled.
Violet Mis­configuration Technical values are invalid, for example a minimum greater than the maximum.

Opening the miner's web interface: Press and hold a miner tile for about two seconds. Disable the miner in HashLink before making manual changes, as HashLink may otherwise overwrite them.

Chapter 07

Pausing mining

The power button at the bottom left is the central switch for active operation and standby.

  • Active

    HashLink controls the miners according to the active profile.

  • Standby

    All miners are paused. The controller and the interface keep running.

  • Error

    The power button first leads to the system status.

  1. Tap the power button.
  2. Confirm “Activate standby”. All miners are paused in a controlled way.
  3. To resume, tap the power button again.

Standby is kept across restarts. It is the safe way to pause mining without shutting down the entire system.

Chapter 08

Profiles and schedules

The scheduler sets what the miners do and at which time a strategy is active.

  • 01

    Select active schedule

    Select a profile, day plan, week plan or standby.

  • 02

    Manage profiles

    Create and edit strategies.

  • 03

    Manage day plans

    Assign profiles to particular time windows of a day.

  • 04

    Manage week plans

    Set a profile or day plan for each weekday.

Profile types

Profile Behaviour Key settings
Optimised energy use The miners follow the available energy automatically. Target grid feed-in, grid draw tolerance, change threshold, optional battery discharge.
Fixed power consumption HashLink holds a fixed power regardless of the PV yield. Desired power consumption in watts.

Day and week plans

  • A day plan consists of time windows of at least 20 minutes; time windows must not overlap.
  • A week plan assigns a profile, a day plan or standby to each weekday.
  • Without an active schedule or an assigned profile, HashLink stays in standby.

Chapter 09

Settings

The system settings connect the energy source and the miners. Account and user management are in the same area.

Saving: Many changes only take effect with the green tick at the top right. If you leave with unsaved changes, you are asked to confirm.

System settings

  • EMS

    Energy source

    Select the type and, depending on the system, enter the address, port or API access details.

  • MIN

    Miner configuration

    Active, name, user, IP address, port, password, preset, minimum and maximum power as well as priority.

  • ALL

    General miner configuration

    Shared pool address and the priority mode None, Soft or Hard.

  • PRE

    Miner presets · administrator

    Miner type and technical timing defaults for Braiins OS, WhatsMiner, Avalon or virtual miners.

Account and users

  • Own account: change the username, language and password; optionally link an RFID card.
  • Manage users: administrators can create accounts, assign roles and delete other users’ accounts.
  • Developer Settings: only for authorised technical work. Do not change them in normal operation.

Changes to a running installation: If in doubt, add or remove miners together with HASHLYNK support.

Chapter 10

Statistics and system status

Live values and historical data help you keep an eye on things. Errors and warnings are collected in the system status.

  • SYS

    System components

    Shows internal services and states such as Running, Starting or Error Recovering.

  • 24H

    Statistics

    Charts of power, hashrate, temperature and efficiency for each miner.

  • RAW

    Raw measurements

    Live view of all measured values for a detailed diagnosis.

  • PLC

    Cooling / PLC · EcoHash

    Additional views for immersion-cooled systems.

Acknowledging errors

  1. Open the system status from the header or the taskbar.
  2. Check the cause and the affected component.
  3. Fix the error.
  4. Use “Acknowledge all” if a confirmation is required.

Chapter 11

First commissioning

A delivered HashLink Controller comes prepared. It is commissioned with the device sheet, RustDesk and the dashboard.

  1. Have the device sheet ready

    The serial number, RustDesk ID and password are on the enclosed device sheet.

  2. Connect the controller

    Connect the power supply and LAN, switch on the controller and wait for it to boot.

  3. Connect via RustDesk

    Use the controller's ID and password.

  4. Log in to HashLink

    Use the default login on the first start and change it afterwards.

  5. Configure the EMS

    Enter the system type, IP address and port and test the connection.

  6. Add miners

    Set the name, IP, access details, port, preset and power limits for each device.

  7. Create a profile

    Select the algorithm and set the desired behaviour.

  8. Create a day plan

    Create time windows and assign the profile.

  9. Activate the schedule

    Check on the homescreen that the profile, schedule, EMS and miners are shown correctly.

Safe initial state: HashLink deliberately starts in standby without an active profile. Automatic control only begins once a schedule has been selected.

Only for service and software reinstallation

Technical requirements and folder structure

A full reinstallation requires 64-bit Windows 10/11 and Java 21 or newer. launcher.exe must sit next to the folders Core/, UI/ and optionally RFID/. Do not change this structure.

Preconfiguring Core and launcher

The technical initial configuration can be done in Core/config.txt. After the first start, changes are made in the interface. RFID and automatic restart can be enabled in launcher.config.txt.

This work is not needed for delivered controllers and should only be carried out by authorised persons.

Chapter 12

Everyday rules

These four rules prevent conflicts between HashLink and the directly connected miners.

  1. Miners ready and idle at the start

    The miners must be switched on, reachable and not yet mining manually. HashLink takes over their power.

  2. Disable before direct maintenance

    Disable a miner in HashLink before changing the pool, firmware or settings directly on the device.

  3. Do not intervene in parallel

    Do not operate the miner's web interface manually while the miner is enabled in HashLink.

  4. Standby instead of shutdown

    Use standby for a pause. Only quit the launcher if the entire system is to be shut down.

Chapter 13

Troubleshooting

The most common causes can be narrowed down with the launcher, the system status and the local network data.

“Java 21 not found in PATH”

Java 21 is not installed or the bin folder is missing from the Windows PATH. Install Java or correct the PATH and restart the launcher.

“Missing required files” or “validation failed”

A file or folder has been moved or is missing. Unpack the bundle again and make sure that launcher.exe, Core/, UI/ and, where used, RFID/ sit together unchanged.

Launcher is already running

Look for the window or the green H icon in the notification area next to the Windows clock. Only one launcher instance may run.

Dashboard cannot reach the backend

Wait a few seconds after the start. Check the backend address on the lock screen and check in the launcher that Core is green and “Running”. Open the Core log if needed.

Miner is red or violet

Red: check the IP address, access details, power supply and network. Violet: check the miner settings, especially the minimum and maximum power.

Core, UI or RFID has crashed

Select “Restart” for the affected row in the launcher. Optionally enable auto-restart. If it crashes repeatedly, save the log file and contact support.

RFID login does not work

Enable RFID in the launcher, check the reader and check that the RFID service is green. A reinstallation may also require the 64-bit Visual C++ Redistributable.

Stop mining but keep the system running

Use the power button at the bottom left and confirm standby. Do not quit the launcher.

Contacting support: Have the serial number, RustDesk ID, firmware version, the exact error message and a screenshot ready.