[Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners - page 624.

patrike

legendary

Activity: 3556

Merit: 1095

Quote from: faxxer on October 19, 2016, 01:37:29 PM

Quote from: patrike on October 16, 2016, 01:13:29 PM

Hi,
1) Are you using Antminers or similar network based ASIC devices, or is it GPU mining? The Remote Agent is only intended for GPU mining.
In any scenario, you either need to setup a VPN solution (Hamachi or similar), or configure port forwarding. You need a public and static IP in the port forwarding scenario at least. With VPN solutions like Hamachi, it might work without.

This is a guide on the web site on this topic where you will find more information:
http://www.awesomeminer.com/help/remotenetworks.aspx

2) Yes. You can select a single miner, multiple miners or all miners and perform the Switch Pool operation. This will let you change pool for all your miners at once.

It's GPU mining, a custom 6 GPU for non bitcoin mining. I thought the agent already automatically port forward and listen to the socket connection. That's mean I can use no-ip or dydns as the external IP for my dynamic IP problem, correct?

It's still required for Awesome Miner main application to be able to connect to the Remote Agent. The Remote Agent itself will not setup any VPN.
Yes, you can use any of those DNS services for solving the dynamic IP issue.

ForumReader

newbie

Activity: 5

Merit: 0

Hello.
Interesting in your product and plan to buy Professional version. Very impressive work.

I have a question: why my miner does not show "Total: $ / day" as you can see in screenshot:
http://joxi.ru/p27oVgYi0ybQg2

faxxer

full member

Activity: 203

Merit: 100

Quote from: patrike on October 16, 2016, 01:13:29 PM

Quote from: faxxer on October 16, 2016, 02:52:04 AM

I just download the free version and will buy enterprise one in few days. Right now I have few question.

1. How to remotely the machine from outside? as per my understanding, I will install the remote agent to the mining rig and add the remote host , so that's mean if I host the mining rig in multiple location, the remote agent will automatically port forwarding the port right? so I would need the public IP or add the IP to any DNS services? because the connection is dynamic connection and the I.P keep changing.

2. Since I will handle large scale of mining rig in different location , but all rig will mining the same coin each day, is there any select all function, so all managed miner will follow to mining the same coin?

Hi,
1) Are you using Antminers or similar network based ASIC devices, or is it GPU mining? The Remote Agent is only intended for GPU mining.
In any scenario, you either need to setup a VPN solution (Hamachi or similar), or configure port forwarding. You need a public and static IP in the port forwarding scenario at least. With VPN solutions like Hamachi, it might work without.

This is a guide on the web site on this topic where you will find more information:
http://www.awesomeminer.com/help/remotenetworks.aspx

2) Yes. You can select a single miner, multiple miners or all miners and perform the Switch Pool operation. This will let you change pool for all your miners at once.

It's GPU mining, a custom 6 GPU for non bitcoin mining. I thought the agent already automatically port forward and listen to the socket connection. That's mean I can use no-ip or dydns as the external IP for my dynamic IP problem, correct?

wmabern

hero member

Activity: 658

Merit: 500

Visualize whirledps

Quote from: patrike on October 16, 2016, 01:06:11 PM

Quote from: wmabern on October 16, 2016, 12:40:25 PM

Well, I finally got it going.... Tongue

I had to uninstall the 1.7 version and download the newest version. Then it immediately started throwing up miner error messages on the screen, one on top of the other, on top of the other, etc. because I have a miner with a few dead chips. I finally had to kill it in task manager because the error messages had control of the screen and I couldn't get in to make any changes.

So I uninstalled that and tried to reinstall the older version. That installed but I had to reenter all of my miner info and customization configuration. Then that froze the program. I had to keep killing it in task manager and trying to restart it. But the program would never start. So finally, I uninstalled that and installed the newest version again. That worked. Then I went into "Options" and set things up. When I told it to allow API access, I guess that forced a restart of all my miners. At first I was a little miffed, but after the restart, the miner with the dead chips is showing all O's now. Hopefully if the X's come back it won't take over the program with error messages. I hope not. Time will tell.

Hi,
It was good that you downloaded the latest version from the web site. Sometimes the automatic upgrades can be prevented by pending Windows update restart or security software.

The 2.0 version will by default trigger Detect Dead Device for Antminer chip failures as well. If you edit the Detect Dead Device trigger, you can select if you want it to trigger on Antminer chip failures or not. You can also set a threadhold.

I will also take a look at the error message that probably is because the restart of the miner doesn't work if it's in restricted mode. Anyway, I will investigate that part to ensure you don't get in to this scenario with multiple error dialogs.

Thank you! I appreciate all the good, hard work. Seems to be running fine now. Yes, I have Detect Dead Device unchecked now because I thought that was probably what was triggering the error. (I'm glad the restart "fixed" my dead chips! I must have rebooted the miner a half dozen times before trying to get the X's to go away. I finally have it down-clocked to 575. I'm not going to press my luck moving it back to 600!) Grin

patrike

legendary

Activity: 3556

Merit: 1095

Quote from: faxxer on October 16, 2016, 02:52:04 AM

I just download the free version and will buy enterprise one in few days. Right now I have few question.

1. How to remotely the machine from outside? as per my understanding, I will install the remote agent to the mining rig and add the remote host , so that's mean if I host the mining rig in multiple location, the remote agent will automatically port forwarding the port right? so I would need the public IP or add the IP to any DNS services? because the connection is dynamic connection and the I.P keep changing.

2. Since I will handle large scale of mining rig in different location , but all rig will mining the same coin each day, is there any select all function, so all managed miner will follow to mining the same coin?

Hi,
1) Are you using Antminers or similar network based ASIC devices, or is it GPU mining? The Remote Agent is only intended for GPU mining.
In any scenario, you either need to setup a VPN solution (Hamachi or similar), or configure port forwarding. You need a public and static IP in the port forwarding scenario at least. With VPN solutions like Hamachi, it might work without.

This is a guide on the web site on this topic where you will find more information:
http://www.awesomeminer.com/help/remotenetworks.aspx

2) Yes. You can select a single miner, multiple miners or all miners and perform the Switch Pool operation. This will let you change pool for all your miners at once.

patrike

legendary

Activity: 3556

Merit: 1095

Quote from: wmabern on October 16, 2016, 12:40:25 PM

Well, I finally got it going.... Tongue

I had to uninstall the 1.7 version and download the newest version. Then it immediately started throwing up miner error messages on the screen, one on top of the other, on top of the other, etc. because I have a miner with a few dead chips. I finally had to kill it in task manager because the error messages had control of the screen and I couldn't get in to make any changes.

So I uninstalled that and tried to reinstall the older version. That installed but I had to reenter all of my miner info and customization configuration. Then that froze the program. I had to keep killing it in task manager and trying to restart it. But the program would never start. So finally, I uninstalled that and installed the newest version again. That worked. Then I went into "Options" and set things up. When I told it to allow API access, I guess that forced a restart of all my miners. At first I was a little miffed, but after the restart, the miner with the dead chips is showing all O's now. Hopefully if the X's come back it won't take over the program with error messages. I hope not. Time will tell.

Hi,
It was good that you downloaded the latest version from the web site. Sometimes the automatic upgrades can be prevented by pending Windows update restart or security software.

The 2.0 version will by default trigger Detect Dead Device for Antminer chip failures as well. If you edit the Detect Dead Device trigger, you can select if you want it to trigger on Antminer chip failures or not. You can also set a threadhold.

I will also take a look at the error message that probably is because the restart of the miner doesn't work if it's in restricted mode. Anyway, I will investigate that part to ensure you don't get in to this scenario with multiple error dialogs.

wmabern

hero member

Activity: 658

Merit: 500

Visualize whirledps

Quote from: wmabern on October 15, 2016, 08:11:35 PM

I have the purchased version of Awesome Miner Professional installed. Ver 1.7.6

It shows the red "updates are available" indicator, but when I try to update, it goes through the motions, restarts and everything, yet it doesn't update.
I have tried this about a dozen times.
Any hints or helpful information?
Thanks!

Well, I finally got it going.... Tongue

I had to uninstall the 1.7 version and download the newest version. Then it immediately started throwing up miner error messages on the screen, one on top of the other, on top of the other, etc. because I have a miner with a few dead chips. I finally had to kill it in task manager because the error messages had control of the screen and I couldn't get in to make any changes.

So I uninstalled that and tried to reinstall the older version. That installed but I had to reenter all of my miner info and customization configuration. Then that froze the program. I had to keep killing it in task manager and trying to restart it. But the program would never start. So finally, I uninstalled that and installed the newest version again. That worked. Then I went into "Options" and set things up. When I told it to allow API access, I guess that forced a restart of all my miners. At first I was a little miffed, but after the restart, the miner with the dead chips is showing all O's now. Hopefully if the X's come back it won't take over the program with error messages. I hope not. Time will tell.

NotFuzzyWarm

legendary

Activity: 3892

Merit: 2797

Evil beware: We have waffles!

Quote from: patrike on October 14, 2016, 03:44:33 PM

Quote from: NotFuzzyWarm on October 13, 2016, 05:41:31 PM

@ patrike
Just got a s9 batch-17 and... Bitmain has changed the firmware, is now BMminer v2.0. I will post in detail tomorrow but for a summary of changes:

They have changed the hash board channels and therefore die temp reporting channels. Now using channels 6, 7, and 8. Might need to come up with a routine to scan the die temp channels and only use ones reporting something...
Looks like changing the frequency may be gone. In the Bitmain GUI that choice is gone. On startup, the firmware goes through several checks per-board and sets the best freq and possibly Vcore as well. When all is done, the boards report different frequencies.

Looking at the Kernel Log it shows several lists of freq and voltage it tries for each board. A note at the beginning of each list says that freq is now stored in the PIC. Now does that mean that a warm boot bypasses the testing -- dunna know but hope so. I'll post the Kernel Log tomorrow. Also fan speed no longer has a setting on the BMminer GUI. Log says is set as needed starting at 40% Oh, the fans are on different channels as well. Think fans are now reported in positions ~~6 an 8~~. I'll verify tomorrow. edit: fans in positions 3 and 6.

Due to the time it takes for the new rebooting process -- around 4 min -- better set dead miner/offline/etc to wait at least that 4 maybe even 5 min before trying to issue another reboot call to the miner...

Other than that, everything else works fine inc the Web access and info to it.

Thanks for the update. Could you please send me an API report for one of these new miners? Then I can compare it in detail with previous batches. Many thanks!

The miner is in my farm at work so will have to send the API report on Monday. I do have the Kernel log posted https://bitcointalksearch.org/topic/m.16564008
and at the end of the log it shows many things I never seen reported. Thinks like range of freq's per-string and even best speeds per chip.

faxxer

full member

Activity: 203

Merit: 100

I just download the free version and will buy enterprise one in few days. Right now I have few question.

1. How to remotely the machine from outside? as per my understanding, I will install the remote agent to the mining rig and add the remote host , so that's mean if I host the mining rig in multiple location, the remote agent will automatically port forwarding the port right? so I would need the public IP or add the IP to any DNS services? because the connection is dynamic connection and the I.P keep changing.

2. Since I will handle large scale of mining rig in different location , but all rig will mining the same coin each day, is there any select all function, so all managed miner will follow to mining the same coin?

wmabern

hero member

Activity: 658

Merit: 500

Visualize whirledps

I have the purchased version of Awesome Miner Professional installed. Ver 1.7.6

It shows the red "updates are available" indicator, but when I try to update, it goes through the motions, restarts and everything, yet it doesn't update.
I have tried this about a dozen times.
Any hints or helpful information?
Thanks!

fedoros

full member

Activity: 171

Merit: 100

A Lot of serious work put in this software. Well done devs. Really Awesome

patrike

legendary

Activity: 3556

Merit: 1095

Quote from: NotFuzzyWarm on October 13, 2016, 05:41:31 PM

@ patrike
Just got a s9 batch-17 and... Bitmain has changed the firmware, is now BMminer v2.0. I will post in detail tomorrow but for a summary of changes:

They have changed the hash board channels and therefore die temp reporting channels. Now using channels 6, 7, and 8. Might need to come up with a routine to scan the die temp channels and only use ones reporting something...
Looks like changing the frequency may be gone. In the Bitmain GUI that choice is gone. On startup, the firmware goes through several checks per-board and sets the best freq and possibly Vcore as well. When all is done, the boards report different frequencies.

Looking at the Kernel Log it shows several lists of freq and voltage it tries for each board. A note at the beginning of each list says that freq is now stored in the PIC. Now does that mean that a warm boot bypasses the testing -- dunna know but hope so. I'll post the Kernel Log tomorrow. Also fan speed no longer has a setting on the BMminer GUI. Log says is set as needed starting at 40% Oh, the fans are on different channels as well. Think fans are now reported in positions ~~6 an 8~~. I'll verify tomorrow. edit: fans in positions 3 and 6.

Due to the time it takes for the new rebooting process -- around 4 min -- better set dead miner/offline/etc to wait at least that 4 maybe even 5 min before trying to issue another reboot call to the miner...

Other than that, everything else works fine inc the Web access and info to it.

Thanks for the update. Could you please send me an API report for one of these new miners? Then I can compare it in detail with previous batches. Many thanks!

NotFuzzyWarm

legendary

Activity: 3892

Merit: 2797

Evil beware: We have waffles!

@ patrike
Just got a s9 batch-17 and... Bitmain has changed the firmware, is now BMminer v2.0. I will post in detail tomorrow but for a summary of changes:

They have changed the hash board channels and therefore die temp reporting channels. Now using channels 6, 7, and 8. Might need to come up with a routine to scan the die temp channels and only use ones reporting something...
Looks like changing the frequency may be gone. In the Bitmain GUI that choice is gone. On startup, the firmware goes through several checks per-board and sets the best freq and possibly Vcore as well. When all is done, the boards report different frequencies.

Looking at the Kernel Log it shows several lists of freq and voltage it tries for each board. A note at the beginning of each list says that freq is now stored in the PIC. Now does that mean that a warm boot bypasses the testing -- dunna know but hope so. I'll post the Kernel Log tomorrow. Also fan speed no longer has a setting on the BMminer GUI. Log says is set as needed starting at 40% Oh, the fans are on different channels as well. Think fans are now reported in positions ~~6 an 8~~. I'll verify tomorrow. edit: fans in positions 3 and 6.

Due to the time it takes for the new rebooting process -- around 4 min -- better set dead miner/offline/etc to wait at least that 4 maybe even 5 min before trying to issue another reboot call to the miner...

Other than that, everything else works fine inc the Web access and info to it.

patrike

legendary

Activity: 3556

Merit: 1095

Quote from: Nesp on October 11, 2016, 07:39:39 AM

Is it possible to add Nicehash Miner to it? Not nicehash pools but their miner itself

The Nicehash Miner itself is just a tool that launches sgminer and similar software. So Nicehash Miner itself cannot be monitored, but it should be possible to use the External Miner feature in Awesome Miner, to point to the sgminer (or Claymore's Ethereum miner) that is started by the Nicehash Miner.

Can you see if the API access of sgminer and similar is enabled when started from the Nicehash Miner? If that's the case, you can go ahead and add them in Awesome Miner.

patrike

legendary

Activity: 3556

Merit: 1095

Quote from: FlensGold on October 10, 2016, 12:16:09 PM

Is there a tutorial or something about how to configure pool/rig in order to mine with miningrigrentals or nicehash?
I know that there are nicehash pools which can be imported, but only adding my BTC address does not work - Miningsoftware does stop right after start and I can not see any error messages.
Thank you

P.S.:
I also tried the Awesome Profit Miner (http://www.awesomeminer.com/guide/awesomeprofit.aspx) and followed the Guide. I assume as worker name my BTC address has to be used?
However, after startup it looks like this for a few seconds...

...and then the miner restarts :-(

Hi,
The Awesome Profit Switcher doesn't have any restart feature itself, so I guess sgminer is shutting down when switching to some specific algorithm. Is it only when you enable the profit switcher you get the restarts? If you disable the profit switcher and only use Nicehash X11 pool for example, is everything running fine then?

I assume you imported the pools from the website "Awesome Profit Switching complete configuration (recommended)"?

It's correct that you should use BTC address as worker name.

Nesp

full member

Activity: 124

Merit: 100

Is it possible to add Nicehash Miner to it? Not nicehash pools but their miner itself

FlensGold

legendary

Activity: 1405

Merit: 1001

Is there a tutorial or something about how to configure pool/rig in order to mine with miningrigrentals or nicehash?
I know that there are nicehash pools which can be imported, but only adding my BTC address does not work - Miningsoftware does stop right after start and I can not see any error messages.
Thank you

P.S.:
I also tried the Awesome Profit Miner (http://www.awesomeminer.com/guide/awesomeprofit.aspx) and followed the Guide. I assume as worker name my BTC address has to be used?
However, after startup it looks like this for a few seconds...

...and then the miner restarts :-(

toptek

legendary

Activity: 1274

Merit: 1000

Thanks

patrike

legendary

Activity: 3556

Merit: 1095

Version 2.0.1

- Added dashboard page to the web interface
- Improved design of the web interface
- Antminer chip failure detection improved with a threshold setting
- C# scripting support for setting custom coin statistics and profitability
- Corrections to the software upload feature

patrike

legendary

Activity: 3556

Merit: 1095

Quote from: toptek on October 07, 2016, 12:31:57 PM

hey man what happen to uploading custom software the issue I'm having now is it uploads every time but after it uploads it puts it on C drive on the remote PC i sent it to,to C drive without a folder and I can't access it unless i go to that PC and move those files in to a folder and name the folder were it thinks the upload went other wise no upload folder is seen and the upload location is locked if, I try to set the miner to the uploaded software.

I was able to reproduce this problem in some instances. I've just made a change for this in version 2.0.1 that will be made available very soon.

Topic: [Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners - page 624. (Read 703764 times)