ASICseer is separated into read-only and read-write. Your Panel is read-only and your Remote Config File is read-write.
You can use the "Powerful and Advanced" installation to quickly install ASICseer on multiple units via SSH.
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.
https://asicseer.com/config.txt
and host it yourself (see Setting up a Server)http://your-server.com/config.txt
http://your-server.com/config.txt
is an example. You must use your own link.If you do not have a remote server and do not want to use ConfigMaker, you can create a remote server with DigitalOcean.
cd /var/www/html
wget -O config.txt https://asicseer.com/config.txt
nano /var/www/html/config.txt
http://digital.ocean.ip.address/config.txt
Ubuntu Windows Subsystem for Linux (WSL) Instructions
Enter new UNIX username:
use asicseer
for both the username
and password
settings.username
and password
is set, sudo su
to become the root
user.
password
, enter asicseer
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".
sshpass
awk
sha256sum
curl
installed.vlan
or include
lists into your Remote Config File (see example)vlan
must look like 10.8.250.0-255
(last octet is a range)sudo su
sshpass
awk
sha256sum
curl
if your *nix environment does not have them, examples:
apt-get -fy install sshpass
apt-get-ubuntu -fy install sshpass
yum -y install sshpass
brew install http://git.io/sshpass.rb
apt-get update; apt-get -fy install sshpass
sudo apt-get -fy install sshpass
mkdir ~/.ssh && chmod 700 ~/.ssh
touch ~/.ssh/config && chmod 600 ~/.ssh/config
~/.ssh/config
(using nano
or your favorite text editor)Host *
KexAlgorithms=+diffie-hellman-group1-sha1
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:
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
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.
asicseer
if you followed *nix environment instructions)cd ~; ssh-keygen
and press ENTER (~3 times) until your fingerprint is generated (do not input/select any options)cat /home/asicseer/.ssh/id_rsa.pub
pubkey ssh-rsa AAAAB3gZk1XXX...this.is.a.long.string...XXX
NOTE: If you can't SSH to your test ASIC in Step 8:
echo "NO_START=0" > /etc/default/dropbear; /etc/init.d/dropbear restart
on your test ASIC to remove public key authentication.asicseer_installer
from the Restoring SSH page.MAKE INSTALL CODE
button.asicseer_installer
will unlock everything from command line.#
is considered a "comment" and is ignored.Formatting Overview for One-Time Installation Settings
The following settings are used only during ASICseer installation, they are specified like setting value
vlan
See Using the Multi-ASIC Installer on Linux, Mac, or Windows WSLinclude
See Including and Excluding lists of IPs in the Multi-ASIC Installerexclude
See Including and Excluding lists of IPs in the Multi-ASIC Installerpubkey
See Securing your ASIC with Passwordless Login and Public Keycongress
1
-200
(default is 15
). Customizes concurrent installations (speed) of Multi-ASIC Installer.autoinstall
1
-60
Reruns Multi-ASIC Installer every N
minutes that you specify. Requires unused DHCP leases.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.
asicid
is your ASIC ID (used as the worker name if your hostname
is stock) and is derived from the last 6 digits of its MAC address.setting
is the setting that you are applying to your ASIC.value
is what you are passing to the setting
Use global
instead of the asicid to apply a setting
and value
to all ASICs with the same Remote Config File.
Panel Settings
custompanel
takes a 12-digit alphanumeric string and sets a custom Panel using the first 6 digits. See setting custompanel.panelpass
takes a string which is used to password protect your Panel (if set, login is admin/panelpass
)autoupdate
takes values yes
or no
. Setting to yes
will update ASICseer to the latest version within 24 hours of its release.location
takes up to a 24-digit worker name (like rack1/rowb2/number34/shelfa5). See Customizing your Worker Name / Location)location
should only be applied to individual ASICs.response
takes values 1
-20
(i.e. global response 5
, default is 10
mins); altering response
sets Remote Config File pull rate.response
setting. This option is only for Remote Config Files hosted on other services.smallpipe
takes values yes
or no
. Setting to yes
will reduce bandwidth requirements associated with panel reporting.panelclear
takes a value in days (ex: 1
, 2
, 3
) and removes ASICs from your Panel if they stop reporting after panelclear
days.remove
takes a comma-separated list of asicids and removes them from your Panel.options
takes a comma-separated string like global options nightmode,nocolor,chips
nightmode
turns on nightmodenocolor
removes color rendering to increase loading speedchips
adds a hover that displays individual chip frequencies (slows down panel loading)See Deleting/Removing ASICs from your Panel for more information.
Pool Settings
poolname1
is the 1st defined pool to which your ASIC will try to connect. Use format pool.com:port
(don't include stratum+tcp://
)username1
is the 1st pool's username from your pool's site (don't define workers here, see Customizing your Worker Name / Location)poolpass1
is the 1st pool's password from your pool's site (leave as x
if your pool does not require a password)sendworker1
takes ip
location
username
custompanel
hostregex
ipregex
or no
to assign your worker name.extranonce1
ist the 1st pool's extranonce subscription status. Defaults to no
and takes yes
if necessary.Using REGEX to Derive a Worker name from your Hostname
You can use a regex string to derive a worker name either your ASIC hostname or ASIC IP:
global sendworker1 hostregex /REGEX/STRING/
global sendworker1 ipregex /REGEX/STRING/
The regex-derived worker name is sent to your pool without altering your actual ASIC hostname or ASIC IP.
Pool Settings for the Failover Pools
poolname2
,username2
,poolpass2
,sendworker2
,extranonce2
poolname3
,username3
,poolpass3
,sendworker3
,extranonce3
To prevent pool-related downtime, you must have poolname1
, poolname2
, and poolname3
defined to at least two different pool domains/companies (see ASICseer recommendation)
Whitelabel Settings
customer
takes an alphanumeric string to track stats across multiple Panels, replaces "ASICseer" in Logic/BMminer Versions.logo
takes a world-reachable logo (global logo http://domain.com/img.jpg
) and sets a company logo on your Panel / ASIC webUI.icon
takes a world-reachable favicon (global icon http://domain.com/icon.png
) and sets it on your Panel / ASIC webUI.link
takes a world-reachable link (global link http://domain.com/
) and sets a company link on your Panel / ASIC webUI.css
takes a world-reachable css file (global css http://domain.com/file.css
) and sets a custom css template on your ASIC webUI.css
option replaces /css/cascade.css
(click for source) on your ASIC.Setting an Operator Fee
The owner of the Remote Config File is typically the operator of the ASICs. In some cases, the operator and the actual ASIC owner are not the same entity. In this case, the owner and operator may decide on a revenue share agreement using the operator fee. The operator can set an additional pool and fee percentage. The operator fee instructs healthy ASICs to mine a certain percentage of the time to the operator pool.
global poolname-operator btc-us.f2pool.com:3333
global username-operator feeaccount
global poolpass-operator x
global sendworker-operator custompanel
global operator 2
feeaccount.abc123
poolname-operator
and username-operator
to the operator pool and username.operator
to a value between 1
-100
(this is a percent)The operator fee will trigger randomly every four hours, and mine to the operator pool equal to the operator
percentage. You can increase operator payouts by repairing and triaging ASICs, or by increasing the operator
percentage value.
Power Settings
asicboost
takes values yes
or no
. Setting to yes
will increase hashrate.autotune
takes values yes
, no
, fancheck
, or a numeric value.
yes
allows autotuning and increases hashrate.no
prevents autotuning.fancheck
prevents autotuning and sets fans to 100% (for visual checking of broken fans)X
(replace X with a numeric value) limits tuning to X cycles.allowed
takes values yes
(allows mining), no
(prevents mining), contact
(prevents mining, provides ability for fast power-up)echo "ascset|miner-enabled,0" | nc ip.of.asic 4028
or echo "ascset|miner-enabled,1" | nc ip.of.asic 4028
maxwatts
takes a watt value as low as 400
, and sets target/max watts for your ASIC. Increasing this value will increase hashrate.throttle
takes values 25
-200
, which throttles your maxwatts
setting if maxtemp
is reached (see Reducing Facility Overheats)Temperature Settings
maxtemp
takes two values: temp in C
hours
(default 90 6
) and is used for overheat protection and the cool-down period.maxfan
takes: maxfan 20
up to maxfan 100
(air cooling) or maxfan liquid 0
up to maxfan liquid 25
(immersion)exhaust
takes values 0
-100
(default 50
), which helps facility exhaust by running fans even during cool-down periods.Advanced Settings
threshold
takes values 1
-50
(i.e. global threshold 3
, default is 3
); increasing threshold
reduces tuning aggressiveness.hpc
takes values 60
-120
(i.e. global hpc 97
, default is 97
); using hpc
adjusts chip tuning and may alter hashrates/efficiency.mvt
takes values 5
-95
(i.e. global mvt 25
, default is 25
); using mvt
adjusts voltage tuning and may alter hashrates/efficiency.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 |
hashboard detection | (use both) |
blinkgreen board | blinks GREEN light extremely rapidly if all hashboards are ALIVE, turns it OFF if any hashboards are DEAD |
blinkred board | blinks RED light extremely rapidly if any hashboards are DEAD, turns it OFF if all hashboards are ALIVE |
NOTE: You can specify a chain like: global blinkred board 7 to ONLY blink RED if the specified chain/board (i.e. middle board) is down. | |
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 |
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 (1726666388
) for these settings, as it will always be higher.
asicid gethelp 1726666388
sends a gethelp diagnostics file to ASICseer support staff (replace asicid
with your ASIC's asicid)global retune 1726666388
retunes your ASICs.global reboot 1726666388
reboots your ASICs.global uncork 1726666388
deletes throttle data from your ASICs.global reset 1726666388
resets your ASICs as if you had just installed ASICseer for the first time.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 1726666388
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 your ASIC models and applies your setting
to any match. The model must be exactly as it appears on your Panel.
The below example reboots T9+
ASICs.
model=T9+ reboot 1726666388
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
poolname-bchdiff
and username-bchdiff
to your own BCH pool and username.poolname1
is a BTC pool.Now, you will automatically switch to your BCH pool whenever the BCH chain difficulty is low.
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:
asicid location customxname
in your Remote Config File (asicid
is your 6-digit asicid, customxname
is your new worker name)
ab34ef location rowc2
customxname
to username[1-3]
global username1 poolusername
global username1 poolusername.customxname
For more advanced worker settings, see Pool Settings.
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.
a1
,a2
,a3
...If your ASICs are reachable (i.e. they don't have a ❌ condition), you can reboot them remotely using your Remote Config File.
Due to environmental conditions (fan health, physical location, airflow, poor facility design, etc) not all ASICs can operate at the same maxwatts
setting.
Using the below settings, you can maximize hashrate by allowing ASICseer to tune your entire facility to the individual highest possible hashrate of each ASIC.
global maxwatts 1440
global maxtemp 90 6
global throttle 100
Overheats should not be considered normal.
If an ASIC overheats, it will enter a 6
hour cool-down period (1
is the smallest possible value).
The cool-down period is necessary to avoid cascading heat-related facility-wide failures.
With the above settings, each ASIC will...
1440
watts.90
C.6
hour cool-down period.maxwatts
by 100
watts (1340
, 1240
, 1140
, ...) each time an overheat is triggered.The minimum and maximum settings for throttle
(an optional setting) are 25
-200
watts.
Using the above settings, each ASIC will tune to its highest possible maxwatts setting automatically, 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 1726666388
(use the asicid instead of global)
ASICs throttling/overheating due to unaddressed environmental conditions will throttle/overheat 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.
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:
maxfan
to a higher value (NOTE: higher maxfan settings increase watts and reduce fan lifespan)maxwatts
to a lower value (this will retune your ASIC)maxtemp
to 90
if it has been set lower.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.
global custompanel publicsecret
in your Remote Config File (must be the same exact 12 alphanumeric characters on all ASICs)public
(EXACTLY 6 ALPHANUMERIC CHARACTERS) is your preferred Panel ID.secret
(EXACTLY 6 ALPHANUMERIC CHARACTERS) is your private key.global custompanel suresh987abc
will make all your rigs report to https://suresh.asicseer.comglobal custompanel suresh
will do nothing.Automatic Removal
panelclear
parameter as described in Writing your Config.panelclear
days.panelclear
+ another 10 days.Manual Removal
global remove
into your Remote Config File.NOTE: You can adjust the ASICIDs in the global remove
line to suit your preferences.
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
NOTE: This is an intensive script and is not meant to be run regularly.
When a new version is released, your Panel will alert you.
It is highly recommended to keep global autoupdate yes
in your Remote Config File. ASICseer drops support for all previous
versions whenever 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
curl -s -k https://install.asicseer.com/deploy/a/autoupdate | sh
For Multiple ASICs
include http://any.remotely.reachable.url/include_list.txt
to your Remote Config File (like the one from your Panel)#
in front of all other vlan
include
exclude
definitions to comment them (like #vlan
)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 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 08
(the last month):
https://asicseer.com/api/panel-kwh/asdemo/08
· per-panel kilowatt-hours (Google Sheet)https://asicseer.com/api/panel-hash/asdemo/08
· per-panel hashrate (Google Sheet)https://asicseer.com/api/asic-kwh/asdemo/08
· per-asic kilowatt-hours (Google Sheet)https://asicseer.com/api/asic-hash/asdemo/08
· per-asic hashrate (Google Sheet)How to load ASICseer API data in Google Sheets
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
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 pool's 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
ssh -v root@ip.of.your.asic
Copy-pasting Text: In Windows, CTRL+C copies text. In Windows WSL, CTRL+SHIFT+V pastes text.
--------------------------------------------------------------- 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 ----------------------------------------------------------------
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
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.
[
left hashboard (chain6) detected and working fine.|
middle hashboard (chain7) detected and working fine.]
right hashboard (chain8) detected and working fine.If you manage many different Panels, you can set a company name to track hashrates across all of them.
Use the asicseer_installer tool to remove "braiins" firmware.
If your facility has special requirements for scheduled power usage, you can use a php script to serve your Remote Config File.
mkdir -p /var/www/html/config && curl -o /var/www/html/config/index.php http://p.asicseer.com/raw/omcpl
nano /var/www/html/config/index.php
to edit your script.http://ip.of.your.server/config/
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
Powerful and Advanced
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.
Free 24/7 support: Free lifetime support 24/7 via the ASICseer Support Group.
Contact info@asicseer.com for an invitation.
Direct all Media and Business inquiries to info@asicseer.com
See Get Immediate 24/7 Support via Telegram for access to the ASICseer Support Group.