Topic: Antminer D3 Blissz firmware (10/12 v1.12 update) - page 42. (Read 125911 times)

whats this mean?

Dec 10 10:53:48 (none) local0.warn cgminer[4188]: Lost 10 shares due to stratum disconnect on pool 0

M

15min
hashrate showed on btxpool is 0....

for how many time you have tested?

reject meaning your miner calc hash, but it hash was not correct.
TT algo have some different way to calc hashes, and only one way same as X11.
you calc only X11 by D3, and sometime it's hash correct for TT algo.
No, it's sooooooo badly way to use D3 (in stock firmware) to dig TT algo (MachineCoin).
May be some custom firmware will correctly generate TT hashes. who knows...

yes. it's about I talk. sooooooo many rejected. wasting time.

https://ibb.co/hq13Pb
https://ibb.co/g97MAG I have try but the result is not good!

dont worry it s only 15% hidden now ...

---->[]  

forget other algo like timetravel10 , be logic men ... instead if you want burn your miner , you wont have profit

and how to do it, that is the question

Really? Can it be done? Any side effect if it gets many rejects?

You can dig TimeTravel algo without any firmware changes. It's not joke.
You will get many many rejected, and so few accepted..

ps: of course, it's not right way to use D3.

Blissz,  How is the other algorithm coming along with your explore?   Is there still a possibility? 

Can someone with experience please give their opinion on what the target chip temp should be? I have heard many different numbers floating around. These D3 seems to run very hot imho. For example, my room temp is no more than 50 degrees with plenty of circulation. I have fans manually at 95%, frequency at 500, and voltage at 12. I am still getting chip temps all in the 80's. Using latest Blissz 1.11

What is a good target temp longterm? What are the real risks of running outside this range?

Thanks!

Ok so where to start: the kernel log will be really helpful if you experience problems. Furthermore you can run a ping on the pool for a few hours to see if you get lost packages. If you're still in doubt: just post your problem here (describe it good and post your kernel log) so myself or a fellow forum member can help you out.

edit: added the last line, which is a possibility of course :')

[/quote]

Thanks for the thorough explanation. Great job on the firmware buddy. I appreciate the work you have done to improve our space heaters’ efficiency.
[/quote]

For skeptics, how is dev fee calculated :

Duration dev pool : 110 secondes every two hours(see attachments) is 1320 secondes per day.

If you subtract this result by the number of minutes per day, and that you calculate  1.5% of this value you will find:1276

If we compare to the 1320 second we are close to 1.50 is exactly 1.565% !








[/quote]

Issue:

First, I think Blissz deserves every thing he gets! I love the capabilities of this software.

I swore I would leave this alone, but I lied.

I have to say that dev mining 1.83 min every 2 hrs, is a loss of 2.17 minutes at least for the miner=1.8% loss to my mining to start.  

I am addressing the fact that dev mining is performed first, after a restart.

I guess if I add the ten restarts a day This adds another 1100 seconds to Blissz's total, am I right?

Now I am at about 33 minutes of dev mining (at least 36 Minutes of my lost mining a day). Because of HW errors shutting down a string. or otherwise restarting from day to night mining speeds.

Lets call it 0.55hrs divided by 24= 2.3%

In my opinion it would be more fair to let the miner mine for two hours and then start dev mining, not start with dev mining and again after two hours.

Thats 3 dev mines per 4 hours....(If you have found yourself restarting like every 4 hours...) 6 minutes out of 240 = 2.5% @ 10 bucks a day is 7.50 dollars a month. Hmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm from each and every one of us that tried this FW?

If there are 100 of us, well, Does he really deserve 750 Dollars a month from us? FOREVER? Thats a TESLA payment!  

And this is the cause of negative attitude and my disrupting this wonderful forum.


PLUS, I think that shutting off my pools every two ours is maybe not the optimal way to maintain a good psow, or ppsow attendance record, so to speak. And I can not help thinking it cuts our mining payouts in addition to the dev fee.

Thus we pay a LOT more than Blissz Gets, and Blissz deserves everything he gets, so we pay 2.5-3% ((depending on restarts, WE give him detailed observation of his software at ZERO cost (Just to help the software performance out).

He develops a Fan and temperature controlling, money stealing, FW for us to each individually give him 7.5 Bucks a month for the rest of the miners life? Software worth, 7.5 to 10.00 in total to me, not 7.5 Bucks a month. (Although I agree, that percentage will go down over time and less restarts).

What if the FW was aimed at creating HW faults, and making you restart more than normal.....hmmmmmmmm.

and to boot, I have tried to deny the FW its pool port numbers, It (the Kernel) said "WTF no dev pool" (That was the fun of my day) But then it started some API ip port address finder program (Oh yea, Blissz thought of this) and got connected to dev pool, said warning warning warning, and then it mined for him another 3.5 min/s...lol

Like a Penalty...



But my fans are quiet.



So I stay with this software...

Idea/
Solution:

Set up the miner to mine for Blissz once a week for exactly 140 minutes, or once a day for 18 minutes, if you like. Because that is 1.5%, not my present 2.5% including my ++ restarts.

Both of which better than disconnecting from my pool every two hours...

Just my opinion, and again I am only looking for improvement, not complaining.

M

I think the key to unlocking minera access is opening up the API in the firmware. Premium awesomeminer has the ability to configure this. I guess there's a command line way to do it via SSH, but I can't seem to figure it out.

Yep awesome miner found everything instantly, minera did not.

Why not delete this moderator...?

I shall give awesome miner a shot tomorrow, thanks. Let me know if anyone gets minera working tho.

My miner has a low hashrate report in the kennel, what does it mean? I am using frequency 400.

Dec 10 02:47:59 (none) local0.warn cgminer[17743]: low hashrate detected. Expected: [12585.600000], real: [9823.994141]

autoune algorithm ?

can this be what 1219 people expect ?

https://www.change.org/p/https-twitter-com-bitmaintech-d3-antminer-firmware-update-for-additional-mining-algorithms?recruiter=831205993&utm_source=share_petition&utm_medium=copylink&utm_campaign=share_petition&utm_term=share_petition

just use awesome miner... works great even with Blissz FW... when you put your pools in, it will auto switch the pool order to what is paying the most. I like being able to see right in the program if there are any HW errors so I know what needs to be tended to.

I haven't tried it, but it should work as it uses probably the same API as awesomeminer. I might give it a go soon to find it out myself

By the way: I made some good steps on the autotune algorithm. I will release a test version soon to get some feedback from you guys.