Page 1 of 1

Suggestion: Wattage per miner via password argument

Posted: Sat Oct 22, 2016 2:33 pm
by Mrrt
So I was just moving some miners from one 'datacenter' (corner of my house :D) to another and since I'm a little OCD and hate knowing my graphs are wrong I decided I had to change the wattage I was reporting to ProHashing to reflect the downtime for each miner as I moved them.

Lucky for me we're only talking a couple miners but I could see this getting tedious as my mine grows, heading into settings and changing that number all the time.

How cool would it be to just pass, say "w=100" in the password for each 100watt miner? Complicates data storage/manipulation a little bit but not terribly so, and this would provide more accurate and potentially granular information on power usage.

Thoughts?

Re: Suggestion: Wattage per miner via password argument

Posted: Sun Oct 23, 2016 10:01 am
by Steve Sokolowski
This is a great idea. I added it to our intended feature list. It should only take a weekend to implement, if that, and I'm sure many miners would benefit.

We forked our codebase two weekends ago to add multiple algorithms, so we want to avoid the overhead of backporting changes, so we won't include this in the scrypt-only codebase. However, after multiple algorithms are released, this will be one of the first features to be added.

Re: Suggestion: Wattage per miner via password argument

Posted: Sun Oct 23, 2016 1:52 pm
by Mrrt
Good positive stuff! Looking forward to more algos

Re: Suggestion: Wattage per miner via password argument

Posted: Sun Oct 23, 2016 2:31 pm
by CritterDog
Mrrt wrote:
How cool would it be to just pass, say "w=100" in the password for each 100watt miner? Complicates data storage/manipulation a little bit but not terribly so, and this would provide more accurate and potentially granular information on power usage.

Thoughts?
I think this is a good idea but could you make it so we enter this info on the web site as a "worker/watts" then on the miner we would enter the user name as username.worker like most other pools do.. Hope this makes since.. On the A4 they only allow 1 argument in the software unless I am doing something wrong. Just a idea.

Re: Suggestion: Wattage per miner via password argument

Posted: Sun Oct 23, 2016 8:43 pm
by Chris Sokolowski
CritterDog wrote:
Mrrt wrote:On the A4 they only allow 1 argument in the software unless I am doing something wrong.
Are they using a GUI? Have you tried a password of multiple arguments encased in quotes? - for example "d=2048 h=10"

Re: Suggestion: Wattage per miner via password argument

Posted: Sun Oct 23, 2016 10:05 pm
by CritterDog
Chris Sokolowski wrote:
CritterDog wrote:
Mrrt wrote:On the A4 they only allow 1 argument in the software unless I am doing something wrong.
Are they using a GUI? Have you tried a password of multiple arguments encased in quotes? - for example "d=2048 h=10"
Hey thanks!! Putting the quotes in there worked!! I am still tweaking and learning this A4.. Trying diff settings getting it dialed in

Re: Suggestion: Wattage per miner via password argument

Posted: Mon Oct 24, 2016 12:03 am
by Chris Sokolowski
CritterDog wrote:
Chris Sokolowski wrote:
CritterDog wrote:
Are they using a GUI? Have you tried a password of multiple arguments encased in quotes? - for example "d=2048 h=10"
Hey thanks!! Putting the quotes in there worked!! I am still tweaking and learning this A4.. Trying diff settings getting it dialed in
I'm glad to hear it worked. We experienced the issue with our old Zeusminers. The GUI is not programmed well, and it doesn't sanitize inputs to cgminer. A good programmer would enclose all the data entered into the GUI in quotes before passing them to cgminer so that special characters like spaces wouldn't cause problems.

Let us know if for some reason the max share difficulty (currently 262144) is too low and a higher share difficulty would be necessary. We want low share difficulties so we can mine easy coins, but at the same time, as miners get more powerful, higher share difficulties will be needed to keep bandwidth usage reasonable.