Efudd Z-Series Fuddware 2.3 -Z11/Z11e/Z11j/Z9/Mini

[efudd]

i know sometime is good to not say anything but i used this dev fee firmware  and i dont see any profit other than making less than usual just because the fee. i went back to smartass111 free overcloked firmware and i have been running @650 just fine making way more than yours.

this dev fee is killing us, im following your work wich is awsome and i dont take anything off it. but since theres is a free FW and its working flawless i dont see why anyone should pay or use this dev fee fw just to kill their machines to not even make anything other than your dev fee.

@dohckiller - Thank you for your review and feedback. I am thrilled that you have not had any issues with smartass111's firmware and I do hear that you believe the development fee is "killing you". I would not want that to happen, so I do encourage you to use the other firmware and make "way more than [mine]".

Your experience is the unusual one as I have had multiple users and farms with thousands of machines approach me after having issues with smartass's firmware modification. I know for a fact that his modification misses a couple of pieces in the frequency calculations and will throw a system off.

Here is a list of the check-ins to my code repository for these modifications. The time I've put in is not trivial by any means. I personally value my time and have put significant effort into the current modifications and the upcoming modifications. I'd also like to point out that I respond near-instantly to almost every inquiry both public and private. The value I provide is more than just the firmware, but also the service and support.

Code:

Date:   Sat Nov 10 00:50:45 2018 -0500
Date:   Fri Nov 9 00:44:33 2018 -0500
Date:   Tue Nov 6 22:35:25 2018 -0500
Date:   Tue Nov 6 21:53:50 2018 -0500
Date:   Tue Nov 6 17:57:51 2018 -0500
Date:   Sun Nov 4 01:10:25 2018 -0400
Date:   Sun Nov 4 01:10:17 2018 -0400
Date:   Sat Nov 3 01:23:08 2018 -0400
Date:   Fri Nov 2 21:28:52 2018 -0400
Date:   Fri Nov 2 01:38:06 2018 -0400
Date:   Fri Nov 2 01:15:48 2018 -0400
Date:   Thu Nov 1 15:51:31 2018 -0400
Date:   Sun Oct 28 18:30:35 2018 -0400
Date:   Thu Oct 25 13:00:42 2018 -0400
Date:   Wed Oct 24 16:19:16 2018 -0400
Date:   Wed Oct 24 15:57:50 2018 -0400
Date:   Wed Oct 24 15:20:41 2018 -0400
Date:   Wed Oct 24 14:49:28 2018 -0400
Date:   Wed Oct 24 03:15:15 2018 -0400
Date:   Wed Oct 24 00:36:36 2018 -0400
Date:   Tue Oct 23 23:31:10 2018 -0400
Date:   Tue Oct 23 23:21:51 2018 -0400
Date:   Tue Oct 23 02:57:34 2018 -0400
Date:   Tue Oct 23 01:33:11 2018 -0400
Date:   Tue Oct 23 00:50:24 2018 -0400
Date:   Mon Oct 22 22:26:09 2018 -0400
Date:   Mon Oct 22 15:40:27 2018 -0400
Date:   Mon Oct 22 15:20:47 2018 -0400
Date:   Mon Oct 22 02:05:09 2018 -0400
Date:   Sun Oct 21 16:08:25 2018 -0400
Date:   Sun Oct 21 14:14:46 2018 -0400
Date:   Sat Oct 20 15:24:51 2018 -0400
Date:   Sat Oct 20 12:39:39 2018 -0400
Date:   Fri Oct 19 20:49:18 2018 -0400
Date:   Fri Oct 19 19:25:15 2018 -0400
Date:   Thu Oct 18 22:55:13 2018 -0400
Date:   Wed Oct 17 22:00:18 2018 -0400
Date:   Wed Oct 17 01:09:55 2018 -0400
Date:   Tue Oct 16 19:29:07 2018 -0400
Date:   Mon Oct 15 02:57:36 2018 -0400
Date:   Mon Oct 15 01:45:40 2018 -0400
Date:   Sun Oct 14 20:52:57 2018 -0400
Date:   Sun Oct 14 20:14:59 2018 -0400

Thank you,

Jason

[roymunn]

@efudd - just want to check that the latest firmware 2.0d works on the latest batch of z9? Thanks

[efudd]

@efudd - just want to check that the latest firmware 2.0d works on the latest batch of z9? Thanks

@roymunn- yes, that is my understanding. I have not personally been able to test. Please provide feedback if you find out different from your testing.

Thank you,

Jason

[roymunn]

@efudd - just want to check that the latest firmware 2.0d works on the latest batch of z9? Thanks

@roymunn- yes, that is my understanding. I have not personally been able to test. Please provide feedback if you find out different from your testing.

Thank you,

Jason

@efudd - sure, will give it a go. Thanks

[Czepot]

Good Morning.

Just want to ask if firmware update is available for payd users? Currently I'm running 1.1 version. And it's great. Both z9's are running on 650mhz.

The only thing I did was turn the fans around so they sucking hot air out instead of blowing in. And now temp is stable around 52-56C.

Thank you

[mikeywith]

Waiting for the z9 mini version, if ever !

[CrypticMiner]

Any update on the paid version of the firmware without the dev fee? Any ETA on release? I would like to use the individual board clocking feature but do not want to pay the fee since I already bought the firmware.

[efudd]

Waiting for the z9 mini version, if ever !

Me too!

Jason

[efudd]

Any update on the paid version of the firmware without the dev fee? Any ETA on release? I would like to use the individual board clocking feature but do not want to pay the fee since I already bought the firmware.

@CrypticMiner - I'm working on it as quickly as I can, I swear. I'm beyond disappointed in myself with how long this is taking me. I keep running into road blocks and I simply cannot release until the main issues are resolved. I apologize.

The upcoming features are more about the long-run of the units instead of the near-term performance -- tunings that can help ensure they are remain profitable as time progresses.

I will release as soon as I can. I am not sitting idly by.

Thank you,

Jason

[caveman-sam]

Hey Efudd,

Sent you a PM about buying the Z9 firmware, when you have some time please get back to me.

Thanks

[efudd]

Folk,

I know I have not provided a lot of update here recently, and I apologize. The reason is simple, I didn't have any news worth reporting.
I am now confident the release is imminent (a couple of more evenings) although I will scale it out slowly to ensure the infrastructure and miners are working properly.

The current status is this:

* Almost done with the infrastructure
* Testing various positive and negative infrastructure conditions such as server down, not found, license not found, etc.
* Licenses can be upgraded on the fly and clients will "magically" pick up the updates (have a license for 2, need 4, can do it on the fly, no need to change firmware)
* the dev fee version will be updated along with this one and will bring them to feature parity.
* and more...

I still have a reasonable amount of work to do, but the hard parts are behind me (I think....). I'm still in the process of updating the webUI with support for providing a messages to the user (for example "upgrade available") in the dashboard, displaying the licensing information and current counts,

per hashboard feature: This will be enabled in all next releases, both paid and developer fee supported.

For dev-fee users, I am working with a couple of the pools to optimize how the underlying aspects work -- the benefit there is that I will be able to greatly reduce the impact of a dev-fee on hash rate (should be close to 0 when all is said and done). It may be that this functionality will be pool specific in the near-term; I'll provide more detail here as it is available.

NiceHash: I've generated the traces requested by nicehash and submitted them for analysis. My eye does not see anything obvious as to the failure reasons, so I am reliant on them to provide information in order to try to add in support.

Fan Control: Hardware aspects like fan/voltage are the next items on my list. I've done a lot of pre-work on this and honestly things don't look great, but I am not out of ideas just yet.
Voltage Control: see fan control.

Mini: This will follow on the footsteps of the next release. I've been testing. I will likely have a lower dev fee rate for the mini.

Dev-fee: I am strongly considering lowering the dev-fee over time; I will be able to handle this with the infrastucture I've been building. What this means is the longer a node runs, the lower the dev-fee goes to some minimum amount.

Other: I'm sure I'm forgetting something(s)... more soon.

Thank you for your patience and support,

Jason

[CrypticMiner]

Thanks for the update, we know you are working on this everyday. Just like us, none of us have quit our day jobs....yet

[chipless]

today I received 2 new z9 mini's and found they wont run batch 1 firmware correctly. When running the batch 1 it will not show the temps on more then 1 hashboard but if I use the current version from bitmain everything runs fine showing all the temp's. Tried all the resets and everything but sameissue. When the temps arentshowing the thing hashes finefull speed just no temps which cause fan to run full speed and fault light to be on. Anyone else have this issue on any mini shipped after nov 1st

[efudd]

today I received 2 new z9 mini's and found they wont run batch 1 firmware correctly. When running the batch 1 it will not show the temps on more then 1 hashboard but if I use the current version from bitmain everything runs fine showing all the temp's. Tried all the resets and everything but sameissue. When the temps arentshowing the thing hashes finefull speed just no temps which cause fan to run full speed and fault light to be on. Anyone else have this issue on any mini shipped after nov 1st

Eh, that's probably their crappy web interface and nothing more... but it's possible they think they are being tricky.... the fault like thing is a little interesting, but probably still a simple fix if it's what I think it is.

On your miner, go to these two URLs and PM me the output please: /cgi-bin/get_miner_status.cgi as well as the output from this /cgi-bin/get_status_api.cgi

Jason

[chipless]

first url

{
"summary": {
"elapsed":"6663",
"ghs5s":"16.20",
"ghsav":"15.84",
"foundblocks":"0",
"getworks":"98",
"accepted":"1096",
"rejected":"0",
"hw":"0",
"utility":"9.87",
"discarded":"3462",
"stale":"0",
"localwork":"3804",
"wu":"157.91",
"diffa":"17536.00000000",
"diffr":"0.00000000",
"diffs":"0.00000000",
"bestshare":"0"
},
"pools": [
{
"index":"0",
"url":"stratum+tcp://us1-zcash.flypool.org:3333",
"user":"MYWALLET",
"status":"Alive",
"priority":"0",
"getworks":"98",
"accepted":"1096",
"rejected":"0",
"discarded":"3462",
"stale":"0",
"diff":"16",
"diff1":"0",
"diffa":"17536.00000000",
"diffr":"0.00000000",
"diffs":"0.00000000",
"lsdiff":"16.00000000",
"lstime":"0:00:12"
}
,
{
"index":"1",
"url":"stratum+tcp://eu1-zcash.flypool.org:3333",
"user":"MYWALLET",
"status":"Alive",
"priority":"1",
"getworks":"0",
"accepted":"0",
"rejected":"0",
"discarded":"0",
"stale":"0",
"diff":"",
"diff1":"0",
"diffa":"0.00000000",
"diffr":"0.00000000",
"diffs":"0.00000000",
"lsdiff":"0.00000000",
"lstime":"0"
}
,
{
"index":"2",
"url":"stratum+tcp://asia1-zcash.flypool.org:3333",
"user":"MYWALLET",
"status":"Alive",
"priority":"2",
"getworks":"0",
"accepted":"0",
"rejected":"0",
"discarded":"0",
"stale":"0",
"diff":"",
"diff1":"0",
"diffa":"0.00000000",
"diffr":"0.00000000",
"diffs":"0.00000000",
"lsdiff":"0.00000000",
"lstime":"0"
}
],
"devs": [
{
"index":"1",
"chain_acn":"4",
"freq":"737,fan_num=1,fan1=5880,fan2=0,fan3=0,fan4=0,fan5=0,fan6=0,temp_num=3,temp1=0,temp2=0,temp3=35,temp2_1=0,temp2_2=0,temp2_3=46,temp_max=0,Device Hardware%=0.0000,no_matching_work=0,chain_acn1=4,chain_acn2=4,chain_acn3=4,chain_acs1= oooo,chain_acs2= oooo,chain_acs3= oooo,chain_hw1=0,chain_hw2=0,chain_hw3=0,chain_rate1=4.99,chain_rate2=5.97,chain_rate3=5.24|",
"fan":"5880",
"temp":"0",
"chain_acs":" oooo"
}
,
{
"index":"2",
"chain_acn":"4",
"freq":"737,fan_num=1,fan1=5880,fan2=0,fan3=0,fan4=0,fan5=0,fan6=0,temp_num=3,temp1=0,temp2=0,temp3=35,temp2_1=0,temp2_2=0,temp2_3=46,temp_max=0,Device Hardware%=0.0000,no_matching_work=0,chain_acn1=4,chain_acn2=4,chain_acn3=4,chain_acs1= oooo,chain_acs2= oooo,chain_acs3= oooo,chain_hw1=0,chain_hw2=0,chain_hw3=0,chain_rate1=4.99,chain_rate2=5.97,chain_rate3=5.24|",
"fan":"0",
"temp":"0",
"chain_acs":" oooo"
}
]
}

second url

STATUS=S,When=1542085277,Code=11,Msg=Summary,Description=cgminer 4.9.0|SUMMARY,Elapsed=6700,GHS 5s=14.85,GHS av=15.84,Found Blocks=0,Getworks=99,Accepted=1099,Rejected=0,Hardware Errors=0,Utility=9.84,Discarded=3482,Stale=0,Get Failures=0,Local Work=3828,Remote Failures=0,Network Blocks=1,Total MH=106101468.0000,Work Utility=157.48,Difficulty Accepted=17584.00000000,Difficulty Rejected=0.00000000,Difficulty Stale=0.00000000,Best Share=0,Device Hardware%=0.0000,Device Rejected%=0.0000,Pool Rejected%=0.0000,Pool Stale%=0.0000,Last getwork=1542085275|
STATUS=S,When=1542085277,Code=70,Msg=CGMiner stats,Description=cgminer 4.9.0|CGMiner=4.9.0,Miner=9.0.0.5,CompileTime=Sat May 26 20:42:30 CST 2018,Type=Antminer Z9-Mini|STATS=0,ID=ZCASH0,Elapsed=6700,Calls=0,Wait=0.000000,Max=0.000000,Min=99999999.000000,GHS 5s=14.85,GHS av=15.84,miner_count=3,frequency=737,fan_num=1,fan1=5880,fan2=0,fan3=0,fan4=0,fan5=0,fan6=0,temp_num=3,temp1=0,temp2=0,temp3=35,temp2_1=0,temp2_2=0,temp2_3=46,temp_max=0,Device Hardware%=0.0000,no_matching_work=0,chain_acn1=4,chain_acn2=4,chain_acn3=4,chain_acs1= oooo,chain_acs2= oooo,chain_acs3= oooo,chain_hw1=0,chain_hw2=0,chain_hw3=0,chain_rate1=5.14,chain_rate2=5.20,chain_rate3=4.52|
STATUS=S,When=1542085277,Code=7,Msg=3 Pool(s),Description=cgminer 4.9.0|POOL=0,URL=stratum+tcp://us1-zcash.flypool.org:3333,Status=Alive,Priority=0,Quota=1,Long Poll=N,Getworks=99,Accepted=1099,Rejected=0,Discarded=3482,Stale=0,Get Failures=0,Remote Failures=0,User=MYWALLET,Last Share Time=0:00:18,Diff=16,Diff1 Shares=0,Proxy Type=,Proxy=,Difficulty Accepted=17584.00000000,Difficulty Rejected=0.00000000,Difficulty Stale=0.00000000,Last Share Difficulty=16.00000000,Has Stratum=true,Stratum Active=true,Stratum URL=us1-zcash.flypool.org,Has GBT=false,Best Share=0,Pool Rejected%=0.0000,Pool Stale%=0.0000|POOL=1,URL=stratum+tcp://eu1-zcash.flypool.org:3333,Status=Alive,Priority=1,Quota=1,Long Poll=N,Getworks=0,Accepted=0,Rejected=0,Discarded=0,Stale=0,Get Failures=0,Remote Failures=0,User=MYWALLET,Last Share Time=0,Diff=,Diff1 Shares=0,Proxy Type=,Proxy=,Difficulty Accepted=0.00000000,Difficulty Rejected=0.00000000,Difficulty Stale=0.00000000,Last Share Difficulty=0.00000000,Has Stratum=true,Stratum Active=false,Stratum URL=,Has GBT=false,Best Share=0,Pool Rejected%=0.0000,Pool Stale%=0.0000|POOL=2,URL=stratum+tcp://asia1-zcash.flypool.org:3333,Status=Alive,Priority=2,Quota=1,Long Poll=N,Getworks=0,Accepted=0,Rejected=0,Discarded=0,Stale=0,Get Failures=0,Remote Failures=0,User=MYWALLET,Last Share Time=0,Diff=,Diff1 Shares=0,Proxy Type=,Proxy=,Difficulty Accepted=0.00000000,Difficulty Rejected=0.00000000,Difficulty Stale=0.00000000,Last Share Difficulty=0.00000000,Has Stratum=true,Stratum Active=false,Stratum URL=,Has GBT=false,Best Share=0,Pool Rejected%=0.0000,Pool Stale%=0.0000|

[Pizzi_h]

Try lowering mhz. Almost the same happened to me in batch 2.
Try lower to 650 an go up from that.

[efudd]

...snip....
{
"index":"1",
"chain_acn":"4",
"freq":"737,fan_num=1,fan1=5880,fan2=0,fan3=0,fan4=0,fan5=0,fan6=0,temp_num=3,temp1=0,temp2=0,temp3=35,temp2_1=0,temp2_2=0,temp2_3=46,temp_max=0,Device Hardware%=0.0000,no_matching_work=0,chain_acn1=4,chain_acn2=4,chain_acn3=4,chain_acs1= oooo,chain_acs2= oooo,chain_acs3= oooo,chain_hw1=0,chain_hw2=0,chain_hw3=0,chain_rate1=4.99,chain_rate2=5.97,chain_rate3=5.24|",
"fan":"5880",
"temp":"0",
"chain_acs":" oooo"
}
...snip...
...snip...

Ok, weird. temp1 and temp2_1 both go together. One is the PCB (first one, i think) the other is the ASIC. For some reason the temps are coming out empty. I figured it was their web UI because if anything is wrong in the numbers, the web UI goes blank.

The firmware that came on it -- what frequency options exist? Beyond that, is the version1 firmware providing you the frequencies you expect?

Also, for anyone reading, I just want to be clear this is on the latest batch minis with the factory firmware.. :-)

Jason

[chipless]

...snip....
{
"index":"1",
"chain_acn":"4",
"freq":"737,fan_num=1,fan1=5880,fan2=0,fan3=0,fan4=0,fan5=0,fan6=0,temp_num=3,temp1=0,temp2=0,temp3=35,temp2_1=0,temp2_2=0,temp2_3=46,temp_max=0,Device Hardware%=0.0000,no_matching_work=0,chain_acn1=4,chain_acn2=4,chain_acn3=4,chain_acs1= oooo,chain_acs2= oooo,chain_acs3= oooo,chain_hw1=0,chain_hw2=0,chain_hw3=0,chain_rate1=4.99,chain_rate2=5.97,chain_rate3=5.24|",
"fan":"5880",
"temp":"0",
"chain_acs":" oooo"
}
...snip...
...snip...

Ok, weird. temp1 and temp2_1 both go together. One is the PCB (first one, i think) the other is the ASIC. For some reason the temps are coming out empty. I figured it was their web UI because if anything is wrong in the numbers, the web UI goes blank.

The firmware that came on it -- what frequency options exist? Beyond that, is the version1 firmware providing you the frequencies you expect?

Also, for anyone reading, I just want to be clear this is on the latest batch minis with the factory firmware.. :-)

Jason

Yes it is weird...I am trying to find the batch 2 firmware to try it and see if you can f12 overclock so far no luck finding it only batch 1 and 3

These were fresh from china don't know if it is a hidden batch 4 or what since bitmain don't have them onsite as available. I have 2 both the same issue

[Marchcat2008]

NiceHash: I've generated the traces requested by nicehash and submitted them for analysis. My eye does not see anything obvious as to the failure reasons, so I am reliant on them to provide information in order to try to add in support.

Other: I'm sure I'm forgetting something(s)... more soon.

Thank you for your patience and support,

Jason

More info for software developers for Nicehash - https://www.nicehash.com/software-developers?lang=en

[FrozenChip]

today I received 2 new z9 mini's and found they wont run batch 1 firmware correctly. When running the batch 1 it will not show the temps on more then 1 hashboard but if I use the current version from bitmain everything runs fine showing all the temp's. Tried all the resets and everything but sameissue. When the temps arentshowing the thing hashes finefull speed just no temps which cause fan to run full speed and fault light to be on. Anyone else have this issue on any mini shipped after nov 1st

Eh, that's probably their crappy web interface and nothing more... but it's possible they think they are being tricky.... the fault like thing is a little interesting, but probably still a simple fix if it's what I think it is.

On your miner, go to these two URLs and PM me the output please: /cgi-bin/get_miner_status.cgi as well as the output from this /cgi-bin/get_status_api.cgi

Jason

Z9 mini Batch 4 has a different PCB
https://i.imgur.com/j3uQMam.jpg