If you can do that and commit it I can get back to working on cgminer.

Neil

P.S. Now we have this we can move onto mobileminer and pluggings to. Sorry I have taken so long to git this image out, it seems every time I fixed a but I found a new one .

Can do, I already have all the branches forked, so I'll get to work on the email tonight, the image is being written to a card right now, I have about 20 miners standing around doing nothing since UPS delayed my shipment of hubs (yay), so I'll hook some up to test on donations.

If you can do that and commit it I can get back to working on cgminer.

Neil

P.S. Now we have this we can move onto mobileminer and pluggings to. Sorry I have taken so long to git this image out, it seems every time I fixed a but I found a new one .

Can do, I already have all the branches forked, so I'll get to work on the email tonight, the image is being written to a card right now, I have about 20 miners standing around doing nothing since UPS delayed my shipment of hubs (yay), so I'll hook some up to test on donations.

If you look in;-/opt/minepeon/http/inc/functions.inc.php

You will find the SMTP auth code already in there, you just need to uncomment it and make it optional (i.e. it is selected in settings.php)

I'm gonna flash this image and Put my 8 erupters on donate for 24h (i know its not much). Hope to see the adafruit plugin soon =D

When I say I need the donations tested I mean using the Web UI and add 15 minutes .

It is a new bit of code that does it all without restarting the miner using only the API. The code needs to be tested because I am basing new stuff (not included yet) that will allow you to add, remove, disable and change prioritizes of pools from the web ui.

I'm gonna flash this image and Put my 8 erupters on donate for 24h (i know its not much). Hope to see the adafruit plugin soon =D

When I say I need the donations tested I mean using the Web UI and add 15 minutes .

It is a new bit of code that does it all without restarting the miner using only the API. The code needs to be tested because I am basing new stuff (not included yet) that will allow you to add, remove, disable and change prioritizes of pools from the web ui.

Neil

when i say i'm gonna set it to 24hour donate it's not to test your system it's because not enough of the people who use your miner ever donate! if you'd rather i can set it to 15 min...

PS: i always wondered why you didn't have a drop down menu to let people set it to either per day or per hour?! i would set mine to 5min every hour for sure

when i say i'm gonna set it to 24hour donate it's not to test your system it's because not enough of the people who use your miner ever donate! if you'd rather i can set it to 15 min...

That is awfully nice of you but I would feel guilty taking all of your hash power. The idea with the donations is that everyone donates a little and we all get the features we want (plus I get a full time job running your miners ).

when i say i'm gonna set it to 24hour donate it's not to test your system it's because not enough of the people who use your miner ever donate! if you'd rather i can set it to 15 min...

That is awfully nice of you but I would feel guilty taking all of your hash power. The idea with the donations is that everyone donates a little and we all get the features we want (plus I get a full time job running your miners ).

Neil

i'll set it to 30 min per day after tomorrow it is Canadian thanksgiving after all =D. i know you just pushed a major update but any idea when we will get support for the adafruit displays back?

****EDIT****

there we go... 24 hour hash heading to stratum.btcguild.com:3333 still only 2500mhash but hash is hash

I am running the test version 0.2.4 with the fix applied for the double hash rate and noticed that the hardware errors reported via the web interface and the via ssh are different, the number of errors are the same but the percentage is much lower via ssh reported by the miner. The miner is showing .81% and the web interface is showing 3.22%. Not sure if it is a bug or a difference in the way the percentage is calculated between the web interface and the bfgminer. Anyhow thanks for the awesome work, donate is turned on.

I am running the test version 0.2.4 with the fix applied for the double hash rate and noticed that the hardware errors reported via the web interface and the via ssh are different, the number of errors are the same but the percentage is much lower via ssh reported by the miner. The miner is showing .81% and the web interface is showing 3.22%. Not sure if it is a bug or a difference in the way the percentage is calculated between the web interface and the bfgminer. Anyhow thanks for the awesome work, donate is turned on.

I saw that, I think the ssh rate is in error. I have just switched from cgminer to bfgminer and saw a large increase in HW errors. After several reboots it appears to have settled in and I'm seeing about 2.5-3% in bfgm, about the same as I saw in cgm, but now have twice the erupters, 13.3 Gh/s.

I'm using also MinePeon 0.2.4 PR1 for 5 hours, with 3 USB Block Erupters and 3 OC's Block Erupters (16 MHz crystal). BFGminer works better than CGMiner, as I don't need to include (and there is no option in this version to do that) icarus-timing short=90.

The email alert is working fine with gmail (without need for SSL connection). If the Gizmos fail, I receive 2 emails: one for less than minimum Hash rate and one for less than number of Gizmos.

I'm still waiting for some BlueFury Gizmos, to test also that feature.

I don't like the lack of miner options, backup features and live graphs, that I have in 0.2.3 version. I still can not pass graphics data between versions. Perhaps we would need some sort of feature (with a price, of course) in the web, where we could collect and see the graphics data of all our MinePeons.

I'll try this 0.2.4 PR1 version for some more days with these 6 Gizmos, before moving it to my 2 other RPI's (with a total of 40 USB Gizmos) and start using BFGminer instead of CGMiner.

I am running the test version 0.2.4 with the fix applied for the double hash rate and noticed that the hardware errors reported via the web interface and the via ssh are different, the number of errors are the same but the percentage is much lower via ssh reported by the miner. The miner is showing .81% and the web interface is showing 3.22%. Not sure if it is a bug or a difference in the way the percentage is calculated between the web interface and the bfgminer. Anyhow thanks for the awesome work, donate is turned on.

I saw that, I think the ssh rate is in error. I have just switched from cgminer to bfgminer and saw a large increase in HW errors. After several reboots it appears to have settled in and I'm seeing about 2.5-3% in bfgm, about the same as I saw in cgm, but now have twice the erupters, 13.3 Gh/s.

I really don't think it's related to MinePeon, however I will say I'm seeing a ton more HW errors in BFGMiner 3.3.0 versus 3.2.1 or 3.2.9. I've tried playing around with a few settings but still getting a high rate of HW errors then what I ever got before on BFGMiner.

However I also see that the display on the web versus display on the miner is incorrect as well. Web is showing 15.97% HW Errors while the miner is showing 1.5% HW Errors, I'm going to take a look at the code when I get done running errands, unless someone beats me to it.

I am running the test version 0.2.4 with the fix applied for the double hash rate and noticed that the hardware errors reported via the web interface and the via ssh are different, the number of errors are the same but the percentage is much lower via ssh reported by the miner. The miner is showing .81% and the web interface is showing 3.22%. Not sure if it is a bug or a difference in the way the percentage is calculated between the web interface and the bfgminer. Anyhow thanks for the awesome work, donate is turned on.

I saw that, I think the ssh rate is in error. I have just switched from cgminer to bfgminer and saw a large increase in HW errors. After several reboots it appears to have settled in and I'm seeing about 2.5-3% in bfgm, about the same as I saw in cgm, but now have twice the erupters, 13.3 Gh/s.

I really don't think it's related to MinePeon, however I will say I'm seeing a ton more HW errors in BFGMiner 3.3.0 versus 3.2.1 or 3.2.9. I've tried playing around with a few settings but still getting a high rate of HW errors then what I ever got before on BFGMiner.

However I also see that the display on the web versus display on the miner is incorrect as well. Web is showing 15.97% HW Errors while the miner is showing 1.5% HW Errors, I'm going to take a look at the code when I get done running errands, unless someone beats me to it.

This is why it is a pre release, I have not been sure about the error rates for a while now, and bfgminer seems to do something different then cgminer.

Feel free to jump into index.php and see if you can remedy the matter, one thing that might be of help is if you ssh in and;-

touch /opt/minepeon/DEBUG

That turns the debuging on and you will also get the raw api output at the bottom of the page. (Delete it when you want it to go away).

I am running the test version 0.2.4 with the fix applied for the double hash rate and noticed that the hardware errors reported via the web interface and the via ssh are different, the number of errors are the same but the percentage is much lower via ssh reported by the miner. The miner is showing .81% and the web interface is showing 3.22%. Not sure if it is a bug or a difference in the way the percentage is calculated between the web interface and the bfgminer. Anyhow thanks for the awesome work, donate is turned on.

I saw that, I think the ssh rate is in error. I have just switched from cgminer to bfgminer and saw a large increase in HW errors. After several reboots it appears to have settled in and I'm seeing about 2.5-3% in bfgm, about the same as I saw in cgm, but now have twice the erupters, 13.3 Gh/s.

I really don't think it's related to MinePeon, however I will say I'm seeing a ton more HW errors in BFGMiner 3.3.0 versus 3.2.1 or 3.2.9. I've tried playing around with a few settings but still getting a high rate of HW errors then what I ever got before on BFGMiner.

However I also see that the display on the web versus display on the miner is incorrect as well. Web is showing 15.97% HW Errors while the miner is showing 1.5% HW Errors, I'm going to take a look at the code when I get done running errands, unless someone beats me to it.

This is why it is a pre release, I have not been sure about the error rates for a while now, and bfgminer seems to do something different then cgminer.

Feel free to jump into index.php and see if you can remedy the matter, one thing that might be of help is if you ssh in and;-

touch /opt/minepeon/DEBUG

That turns the debuging on and you will also get the raw api output at the bottom of the page. (Delete it when you want it to go away).

Neil

Well, doing the math, not even BFGMiner displays it properly unless there's another factor involved, I'm going to go through the code in BFGMiner to see if there's another factor involved in computing the % of HW Errors, as I'm *assuming* that % is the amount put against the total # of shares. I could be way wrong on that, if I can't find anything I'll message Luke to see if he can shed some light on this.

Well, doing the math, not even BFGMiner displays it properly unless there's another factor involved, I'm going to go through the code in BFGMiner to see if there's another factor involved in computing the % of HW Errors, as I'm *assuming* that % is the amount put against the total # of shares. I could be way wrong on that, if I can't find anything I'll message Luke to see if he can shed some light on this.

I vagley remember may need to subtract error from the total shares before you work out the percentage (i.e. shares - error / error = percent).

But yeah, I agree, the is some sort of 'magic number' in there that we are not taking into account.