home · news · about · security · documentation · changelog · used by · support/contact · S9 · T9 · restore ssh · fix hashboards · pool · psu
asicseer logo
 
ASIC management, monitoring, and optimization system.

ASICseer is running on 60,395 ASICs (53 megawatts).

download ASICseer 1.1.7 now · usflag · ruflag

Table of Contents


Quick Start Guide (with ConfigMaker)

ASICseer is separated into read-only and read-write. Your Panel is read-only and your Remote Config File is read-write.

  1. Go to ASICseer Downloads.
  2. Upon loading the page, a Remote Config File will automatically be generated and hosted on ConfigMaker.com for you.
  3. Under "Before Installation," save your secret Remote Config File editor link, you will need it to manage all of your ASICs.
  4. Under "Before Installation," save your new ASIC login information, you will need it login to your ASICs.
  5. Set your custompanel in your Remote Config File, which can be used for multiple farms to report to the same Panel.
  6. Follow the instructions under "Simple and Easy" installation and wait for the installation to complete.
  7. After the installation finishes, visit the "Miner Configuration" page on your ASIC.
  8. Make changes in your Remote Config File to manage your ASICs.

You can use the "Powerful and Advanced" installation to quickly install ASICseer on multiple units via SSH.


Setting up your own Remote Config File

If you want to avoid using ConfigMaker, you can host your Remote Config File on your own world-reachable remote server, vps, or shared hosting account.

  1. Copy https://asicseer.com/config.txt and host it yourself (see Setting up a Server)
  2. Get the link to your Remote Config File like http://your-server.com/config.txt
    NOTE: The link http://your-server.com/config.txt is an example. You must use your own link.
  3. Make changes to your Remote Config File to manage your ASICs. See Writing your Config for instructions.
  4. Paste the link to your Remote Config File into the "Remote Config File" field on the Downloads page and press "Regenerate Downloads."
  5. Re/install ASICseer with your new Remote Config File.

Setting up a Server for your Remote Config File

If you do not have a remote server and do not want to use ConfigMaker, you can create a remote server with DigitalOcean.

  1. Go to DigitalOcean (follow this link to get $50 credit), create an account, then press "Create -> Droplet."
  2. Click on "Marketplace" and select the "LEMP on 18.04" software stack.
  3. Scroll down, press the left arrow, select "$5/month" droplet (not $40/month), your closest region, "one-time password", and press "Create."
  4. After the droplet is created, follow the SSH guide to SSH to your DigitalOcean droplet.
  5. Descend into the world-readable html directory with cd /var/www/html
  6. Copy the sample Remote Config File to your DigitalOcean Droplet with wget -O config.txt https://asicseer.com/config.txt
  7. Make changes to your Remote Config File on your DigitalOcean droplet with nano /var/www/html/config.txt
  8. The link to your Remote Config File is now http://digital.ocean.ip.address/config.txt
  9. Paste the link to your Remote Config File into the "Remote Config File" field on the Downloads page and press "Regenerate Downloads."
  10. Re/install ASICseer with your new Remote Config File.

Using the Multi-ASIC Installer on Windows 10

Ubuntu Windows Subsystem for Linux (WSL) Instructions

  1. Update Windows 10 to at least Version 10.0.18362 (Build 18362)
  2. Download and Install Ubuntu 18.04 from the Microsoft Store.
  3. When Ubuntu prompts Enter new UNIX username: use asicseer for both the username and password settings.
  4. Once the username and password is set, sudo su to become the root user.
  5. When prompted for your password, enter asicseer
  6. Run the below line to install the required packages:
    apt-get update; apt-get -fy install sshpass

You have now prepared a *nix environment. Proceed with "Using the Multi-ASIC Installer on Linux, Mac, or Windows WSL".


Using the Multi-ASIC Installer on Linux, Mac, or Windows WSL

  1. Add your vlan or include lists into your Remote Config File (see example)
        NOTE: Each vlan must look like 10.8.250.0-255 (last octet is a range)
  2. Open your terminal.
  3. Become root with sudo su
  4. Install sshpass awk sha256sum curl if your *nix environment does not have them, examples:
    • ubuntu, debian: apt-get -fy install sshpass
    • ethos: apt-get-ubuntu -fy install sshpass
    • fedora, centos: yum -y install sshpass
    • mac: follow homebrew installation instructions, then brew install http://git.io/sshpass.rb
    • windows wsl: apt-get update; apt-get -fy install sshpass
  5. Follow the Quick Start Guide to generate your installer script.
  6. Copy-paste the line under MULTI-ASIC INSTALLER into your terminal and press ENTER.
  7. Watch the asyncronous installer output. When there is no more output (check by pressing ENTER a few times), installation is finished.

Including and Excluding lists of IPs in the Multi-ASIC Installer

These options are specified in your Remote Config File.

You can include additonal lists (optional) of ASIC IPs by adding include lines.

include http://any.remotely.reachable.url/include_list.txt
include http://another.remotely.reachable.url/another_include_list.txt

You can exclude lists of ASIC IPs (optional) to prevent them from re/installing ASICseer by adding exclude lines.

exclude http://any.remotely.reachable.url/exclude_list.txt
exclude http://another.remotely.reachable.url/another_exclude_list.txt

NOTE: exclude lists supersede include lists.

You can generate these lists with your Panel:

  1. Select any checkbox conditions and/or versions in the checkbox interface at the top of your Panel.
  2. Select "ip list" from the dropdown menu and press the "submit" button.
  3. Copy-paste the URL from your browser URL bar into your Remote Config File according to the above examples.

NOTE: When using include and exclude with panelpass, you must use proper authentication in the list URLs:
  https://admin:panelpass@public.asicseer.com/?showstyle=s_ips


Securing your ASIC with Passwordless Login and Public Key

To secure your ASIC and to prevent unauthorized logins, you should use passwordless public key authentication. This procedure disables passworded SSH logins and only allows the machine containing the private key to access your ASICs.

  1. Login to (or create) your *nix environment local to your ASIC network.
  2. Take appropriate precautions to secure this machine from outside users (vpn, ssh password protection, etc).
  3. Become the appropriate non-root user (usually asicseer if you followed *nix environment instructions).
  4. Run cd ~; ssh-keygen and press ENTER (~3 times) until your fingerprint is generated (do not input/select any options).
  5. Run cat /home/asicseer/.ssh/id_rsa.pub
  6. Copy your public key to your Remote Config File, starting with "pubkey ": pubkey ssh-rsa AAAAB3gZk1XXX...this.is.a.long.string...XXX
  7. Re/install ASICseer on a single test ASIC (open multiple SSH windows/sessions to this ASIC, just in case).
  8. SSH to your test ASIC from this machine in another separate window. If everything worked, you will not be prompted for an SSH password.
  9. Re/install ASICseer on all your ASICs.

NOTE: If you can't SSH to your test ASIC in Step 8:

  1. Remove the public key from your Remote Config File.
  2. Run echo "NO_START=0" > /etc/default/dropbear; /etc/init.d/dropbear restart on your test ASIC to remove public key authentication.
  3. Hire a security consultant to assist you with securing your network.

Writing your Config

Optional Faster Remote Config Responsiveness

You can change your Remote Confile File responsiveness to 2 minutes instead of 10 minutes.

  1. Host your own Remote Config File.
  2. Add RESPONSIVE to its URL (example: http://your-server.com/configRESPONSIVE.txt

Formatting Overview for One-Time Installation Settings

The following settings are used only during ASICseer installation, they are specified like setting value

Formatting Overview for Runtime Settings

After ASICseer is installed, edit your Remote Config File using the asicid setting value format to send runtime instructions to your ASICs.

Use global instead of the asicid to apply a setting to all ASICs on which you have installed the same Remote Config File.

Panel Settings

See Deleting/Removing ASICs from your Panel for more information.

Pool Settings

Pool Settings for the Failover Pools

To prevent pool-related downtime, you must have poolname1, poolname2, and poolname3 defined to at least two different pool domains/companies (see ASICseer recommendation)

Efficient chain switching between BTC and BCH

You can automatically switch to BCH mining whenever the BCH chain experiences low difficulty periods by adding a BCH pool endpoint to your Remote Config File.

global poolname-bchdiff bch.pool.bitcoin.com:3333
global username-bchdiff asicseer
global poolpass-bchdiff x
global sendworker-bchdiff location
  1. Add the above stanza to your Remote Config File.
  2. Change poolname-bchdiff and username-bchdiff to your own BCH pool and username.
  3. Make sure poolname1 is a BTC pool.

Now, you will automatically switch to your BCH pool whenever the BCH chain difficulty is low.

Power Settings

Advanced Settings

LED Settings

examples:

global blinkgreen hashrate
global blinkred idle

status 
hashrate blinks faster as hashrate increases, solid if tuning
idle turns on light if ASIC is not mining
fan turns on light if a fan is not detected and blinks if a fan is degrading
manual 
rapid blinks rapidly
solid solid light
normal blink speed similar to stock firmware
off no light
morse code 
sos blinks sos in morse code
worker blinks the worker name in morse code
ip blinks the ip in morse code
panel blinks the panel name in morse code
location blinks the location in morse code

Temperature Settings

ASIC Troubleshooting Settings

The below settings take an incrementing value. If the value is higher than the previously used value, the setting will reapply. Because of this, it is recommended to use the unix timestamp (1591440454) for these settings, as it will always be higher.

Applying Settings by Location

You must have locations defined to apply settings using locations. group= searches the beginning of your location for a string and applies your setting to any ASIC location that has a match. The location must start with the string to match.

The below example reboots ASICs with a location starting with rowc, and stops mining on ASICs with a location that has rowd in it.

group=rowc reboot 1591440454
group=rowd allowed no

Applying Settings by CIDR

Applying Settings by CIDR is useful if you have farms separated by IP ranges. cidr=10.8.200.0/21 matches all ASICs with IPs in a specific CIDR range and applies your setting to those ASICs.

The below example assigns a specific custompanel to a specific CIDR range.

cidr=10.8.200.0/21 custompanel 5xcolo123456 (all ASICs in 10.8.200.0/21 will then report to 5xcolo.asicseer.com)

Applying Settings by Model

Applying Settings by Model is useful if you have different ASIC models. model= searches the beginning of your ASIC model for a string and applies your setting to any ASIC model that has a match. The model must start with the string to match.

The below example reboots T9+ ASICs.

model=T9+ reboot 1591440454


Customizing your Worker Name / Location

You can use one Remote Config File for all ASICs. Specifying multiple workers does not require separate Remote Config Files.

To switch your worker name and assign a location, set asicid location newname


Assigning Worker Names / Locations with the IP Report Button

If you use hostnames to manage your worker names and ASIC locations, ASICseer will use them to set Worker Names / Locations during installation. If you have a big farm and don't know where any of your ASICs are located, you can order them with the IP Report button.

NOTE: It is important to do the below steps when your Internet is stable, and your ASICs are online and reporting.

  1. After installing ASICseer, go to your Panel. Then, physically go to your first Rack ("Rack A") and decide on an order for your ASICs.
  2. Press and hold the IP Report button for 5 seconds on each "Rack A" ASIC in order, one by one (wait at least 3 seconds between press-holds)
  3. Wait at least 3 minutes.
  4. Your Panel will show a number in the "ipr" column (seconds ago that the IP Report button was pressed)
  5. Select "assign workers" from the dropdown menu and press the "submit" button.
  6. Set your worker names like: a1,a2,a3...
  7. Continue this process for all rows/racks. If you press the IP Report button on all ASICs in your preferred order, they will be ordered correctly.

Assigning Worker Names / Locations with REGEX

If you use static IPs for your ASICs, you can use regex to assign IP octets for your worker name and location.

  1. After installing ASICseer, go to your Panel.
  2. Select "config template" from the dropdown menu and press the "submit" button.
  3. Copy-paste the config template into the "TEST STRING" field of the regex101 editor.
  4. Copy-paste the resulting "SUBSTITUTION" result into your Remote Config File.

After this is done, your worker and location names will update on your Panel and on your pool.


Remotely Rebooting ASICs

If your ASICs are reachable (i.e. they don't have a ❌ condition), you can reboot them remotely using your Remote Config File.

  1. Go to your Panel.
  2. Select any checkbox conditions and/or versions in the checkbox interface at the top of your Panel.
  3. Select "reboot manager" from the dropdown menu and press the "submit" button.
  4. Your Panel will generate settings for your Remote Config File to reboot your affected ASICs.
  5. Copy-paste the entire output into your Remote Config File.

Reducing Facility Overheats

Due to environmental conditions (fan health, physical location, airflow, etc) not all ASICs can operate at the same maxwatts setting. Using the below settings, you can maximize hashrate by tuning your entire facility to the individual highest possible hashrate of each ASIC.

global maxwatts 1480
global maxtemp 90 6
global throttle 80

Explanations

  1. Start mining/tuning at 1480 watts.
  2. If any hashboard reaches 90C, trigger an overheat and stop mining.
  3. Restart mining automatically after 6 hours passes.
    NOTE: The minimum possible value is 1 hour; this minimum is necessary to avoid cascading failure events.
  4. If mining is restarted after an overheat, throttle maxwatts by 80 watts (i.e. 1400, then 1320, etc)
    NOTE: The minimum and maximum settings for throttle (an optional setting) are 25-200 watts.
  5. Each ASIC will automatically tune to its highest possible maxwatts setting, with as much granularity as you prefer.

Temperature Legend

To restore throttled ASICs back to their original maxwatts setting, add this line to your Remote Config File:
global uncork 1591440454 (use the asicid instead of global)

ASICs throttling/overheating due to unaddressed environmental conditions will throttle again even after uncork is run.

You can use LED settings to find ASICs with temperature problems, and diagnose them for physical problems or environmental conditions. You can also physically swap ASICs in your farm.

ASICs that are too cold cannot maintain their hashrates. Decrease or block facility airflow and exhaust in sections of your facility that have an abnormal amount of cold ASICs.


Managing Temperature

If any hashboard temperature exceeds maxtemp, mining will turn off for the amount of hours defined (default 6)

Follow the below steps to reduce the chances of your ASICs overheating:


Setting a Custom Panel

ASICseer assigns a 6-character Panel based on a hash of your external IP. This way, all ASICs on one network can report to the same Panel.

If your public IP changes, your Panel link will change.

You can set your own Custom Panel with the custompanel parameter.


Deleting/Removing ASICs from your Panel

Automatic Removal

  1. Adjust the panelclear parameter as described in Writing your Config.
  2. ASICs on the latest ASICseer version will be removed after panelclear days.
  3. ASICs on older ASICseer versions will be removed after panelclear + another 10 days.

Manual Removal

  1. Select any checkbox conditions and/or versions in the checkbox interface at the top of your Panel.
  2. Select "remove units" in the dropdown menu and press the "submit" button.
  3. Paste the resulting line beginning with global remove into your Remote Config File.

NOTE: You can adjust the ASICIDs in the global remove line to suit your preferences.


Forcing Remote Config and Panel Sync

Sometimes, you may need to sync your Remote Config File to your ASICs.

For a Single ASIC

Navigate to your Miner Configuration page and press the sync config and panel button.

For Multiple ASICs

  1. Enter a Remote Config File:
  2. Copy-paste the following code into your *nix environment terminal (replace admin with your ASICs' SSH password):
    curl -s -k https://as.link/s/a/https://asicseer.com/config.txt | sed 's/SSHPASS/admin/g' | sh

NOTE: This is an intensive script and is not meant to be run regularly.


Updating to the Latest ASICseer Version

It is highly recommended that you keep global autoupdate yes in your Remote Config File. The ASICseer team drops support for all previous ASICseer versions as soon as a new version is released, in line with an aggressive development schedule. If any issues occur with previous versions, no support will be provided until you update.

NOTE: There is no difference between updating and installing ASICseer. You can always update by re/installing ASICseer.

If some ASICs miss their update, update them by either re/installing ASICseer or by using the below example methods.

For a Single ASIC

For Multiple ASICs

  1. Select any old version checkboxes in the checkbox interface at the top of your Panel.
  2. Select "ip list" from the dropdown menu and press the "submit" button.
  3. Using the resulting URL, add include http://any.remotely.reachable.url/include_list.txt into your Remote Config File.
  4. Add # in front of your vlan definitions to comment them out (like #vlan)
  5. Re-run the Multi-ASIC installer to update/reinstall ASICseer just the ASICs running older versions.

Importing a CSV of your Panel into Google Sheets

  1. Open the ASICseer API Example Sheet.
  2. This opens a read only sheet. To be able to edit the sheet, select 'File' -> 'Make a Copy' in the top left and press OK.
  3. Edit the A2 cell to reflect your 6-digit Panel name.

Note: Google Sheets does not support native authentication. If you have a panelpass specified, add your panelpass in cell B2


Using JSON API to load per-Panel or per-ASIC Data

Using historical API

The following API endpoints can load historical monthly per-Panel and per-ASIC data, useful for enterprise-class customer billing purposes.

https://asicseer.com/api/type-call/panel/month

examples using 05 (the last month):

How to load ASICseer API data in Google Sheets

  1. Open the ASICseer API Example Sheet (this example has an JSON loading function in the 'Tools' -> 'Script Editor' menu item)
  2. This opens a read only sheet. To be able to edit the sheet, select 'File' -> 'Make a Copy' in the top left and press OK.
  3. Select one of the API tabs at the bottom.
  4. Edit the A2 cell to reflect your 6-digit Panel name.

Note: Google Sheets does not support native authentication. If you have a panelpass specified, change the D2 cell to the below:

https://asicseer.com/apisecure/type-call/panel/month/panelpass


Using Nicehash for Mining

For mining on Nicehash, use only Nicehash AsicBoost endpoints and extranonce subscription. When Nicehash prompts you to "select algorithm", select SHA256-AsicBoost. ASICseer will automatically rewrite non-AsicBoost Nicehash endpoints to AsicBoost ones.

If you don't want to set up an account, you can use a wallet address as your username.

Use the following stanza as a guide for mining on Nicehash.

global poolname1 sha256asicboost.usa.nicehash.com:3368
global username1 15tXyQAYyiD4q1FUVcsdMgG78fFZG6J9zD
global poolpass1 x
global sendworker1 location
global extranonce1 yes
global poolname2 sha256asicboost.eu.nicehash.com:3368
global username2 15tXyQAYyiD4q1FUVcsdMgG78fFZG6J9zD
global poolpass2 x
global sendworker2 location
global extranonce2 yes
global poolname3 sha256asicboost.hk.nicehash.com:3368
global username3 15tXyQAYyiD4q1FUVcsdMgG78fFZG6J9zD
global poolpass3 x
global sendworker3 location
global extranonce3 yes

Using SSH to Login to ASICs from Windows 10

  1. Set up your *nix environment.
  2. Connect your computer to the same network as your ASICs, using VPN, or by SSHing to a jump box.
  3. Find the IP of your ASIC (either on your Panel or on your router DHCP client table)
  4. In your terminal, ssh -v root@ip.of.your.asic
  5. Enter your ASIC SSH password when prompted.
  6. A list of available commands will appear.

Copy-pasting Text: In Windows, CTRL+C copies text. In Windows WSL, CTRL+SHIFT+V pastes text.


List of Common ASICseer Terminal Commands

---------------------------------------------------------------
ASICseer | available commands:

dmesg		show kernel log
helpme          show this list of commands
gethelp         generate a diagnostics file for getting support
df | p          send output of piped (ex: df) to paste server
update          force a stats update to the panel server
putconf         redownload the contents of your remote config
rawstats        display non-formatted system info / miner stats
jsonstats	display json-formatted system info / miner stats
pool		display recommended pool statistics
----------------------------------------------------------------

Clearing your ASIC MAC addresses to Prevent Conficts

In large farms, there may be conflicting MAC addresses that result in multiple ASICs appearing as if they are one device. This results in arp conflicts, incorrect reporting, etc.

If you see multiple ASICs with the same MAC address, you should regenerate the MAC address on your ASIC and then reboot it:

rm /config/mac && sync && sleep 1 && reboot


Identifying Faulty Hashboards

Many people who install ASICseer are surprised to see faulty hashboards after tuning is complete. Don't shoot the messenger. These faulty hashboards existed before you installed ASICseer, you just did not know about them.

See the Restoring Hashboards guide for a detailed explanation regarding how to fix faulty hashboards.

Review the following points:

If your ASIC has identified a faulty hashboard, it will show a 🔗 or 🔘. You can identify the faulty hashboard using the Panel and the [ | ] hashboard detection symbols.

The below symbols identify which hashboard is detected and working fine from the exhaust side.

You can assist onsite staff in finding faulty hashboards by blinking the red LED.

  1. Select "blink red all inactive left board units" from the dropdown menu and press the "submit" button.
  2. Your Panel will generate settings for your Remote Config File to blink the red LED for those corresponding ASICs.
  3. Copy-paste the entire output into your Remote Config File.
  4. Instruct on-site staff to replace the left hashboard from the exhaust side.
  5. After replacements are complete, remove the stanza from your Remote Config File that was generated by Point 3.
  6. Repeat this procedure for all middle hashboards.
  7. Repeat this procedure for all right hashboards.

Using the Global Hashrate Viewer

If you manage many different Panels, you can set a company name to track hashrates across all of them.

  1. Add global customer yourcompanyname to your Remote Config File (use the same string on all Remote Config Files that you manage)
  2. Enter the companyname you used:

Removal of 'braiins' Firmware (and ASICseer Installation)

Use the asicseer_installer tool to remove "braiins" firmware.


Controlling Power Usage based on Scheduled Power

If your facility has special requirements for scheduled power usage, you can use a php script to serve your Remote Config File.

  1. Set up your own Remote Config File Server.
  2. Run: mkdir -p /var/www/html/config && curl -o /var/www/html/config/index.php http://p.asicseer.com/raw/omcpl
  3. Run: nano /var/www/html/config/index.php to edit your script.
  4. Re/install your ASICs using your Remote Config Link: http://ip.of.your.server/config/

Uninstalling ASICseer and/or Restoring to Factory Settings

Using the IP Report Button

Use the "Restore via IP Report Button" functionality as described in Point 3 of the Bitmain© factory restore guide.

Using the WebUI firmware Upgrade Page

  1. Download the correct Bitmain© firmware for your ASIC.
    NOTE: Be careful, any Bitmain© firmware described as having a "security" or "secure" firmware actually prevents SSH to your ASIC.
  2. Navigate to the ASIC webUI firmware upgrade page and upload the Bitmain© firmware to your ASIC.
  3. This will restore all settings and pools to factory settings.

Powerful and Advanced

Enter a Remote Config File:

For a Single ASIC
curl -s -k https://install.asicseer.com/deploy/a,force,stock,saveconf/https://asicseer.com/config.txt | sh

For Multiple ASICs (replace admin with your ASICs' SSH password)

Copy-paste the following code into your *nix environment terminal:
curl -s -k https://as.link/d/a,force,stock,saveconf/https://asicseer.com/config.txt | sed 's/SSHPASS/admin/g' | sh

Robust

Use ./asicseer_installer -u any.firmware.tar.gz ip.of.target.asic webuipass

For robust ASICseer un/installation tools, restoring SSH, and removal of foreign firmwares, use the asicseer_installer tool.


Get Immediate 24/7 Support via Telegram

Free 24/7 support: Free lifetime support 24/7 via the ASICseer Telegram channel.

https://t.me/ASICseer


Contacting the ASICseer Team

Direct all Media and Business inquiries to info@asicseer.com

Emails requesting technical support will be treated as spam. Get Immediate 24/7 Support via Telegram.






















































© 2019       ASICshack logo       All rights reserved.