 Show Posts
|
|
Pages: [1]
|
how to properly load an image so it displays the actual image, not the link?  |
|
|
|
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 |
|
|
|
...snip...
Some boards can not hold overclock. It is rare, but it happens. Your pictures are also small and blurred so I cannot make out a lot of detail. At least in your second picture the pool side average is 54 to 55. That's even with whatever dips you are seeing. It seems that your miner side average is 55 and your pool side average is 54 -- this looks good. Your pool side dips could be any number of reasons, including random network or pool issues. The real time is not important -- it is your average (and ultimately the pool side average and share submission rate) that is important. If you are staying in the ~55kSol range and your boards are not dropping, then you are in a good place. I have 1 board that I constantly have to reset as it goes to 0 -- it's on one system and does not happen on the others. One day it will be fine at 650, the next day it only wants 643. I cannot explain these things. Jason The higher is the temperature on chip, the lower frequency it will hold. If the difference between temperature during the night and day is 10-15 degrees, then max stable frequency during the night may be 25Mhz higher comparing to max stable frequency during the day. So adding a feature to automatically slightly overclock/underclock based on the chip temp could be a nice to have. To test this, check max stable frequency with fans on auto and then with fans on 100%. |
|
|
|
|
And very important benefit from voltage control
If i slightly undervolt, i can then overclock to higher frequencies. It has a max amp/power limitation.
My batch 2 could never hold stable anything above 650Mhz. I can do 737Mhz now.
Batch 1 owners should be able to go as high as 800Mhz.
|
|
|
|
After many many hours of investigation i finally managed to undervolt a Z9 mini. Power usage can be as low as 13.5Watt/Ksol at the wall(power meter) with a platinum power supply and this was a z9 mini batch 2, so all other batches should perform slightly better. I get 10Ksol with only 138W, which is almost 50% less power comparing to official specs. Undervolted Z9 mini, can be made silent, with 2 x under 20db fans and a fan simulator Same performance/watt can be reached on Z9 More details of my tests below Stock performance | Frequency | Watt | Ksol | W/Ksol | | 700 | 363 | 15.3 | 23.7 | | 600 | 311 | 13.1 | 23.7 | | 500 | 259 | 11.5 | 22.5 | | 400 | 210 | 9.3 | 22.6 |
Undervolted | Frequency | Watt | Ksol | W/Ksol | | 700 | 321 | 15.2 | 21.1 | | 600 | 237 | 13.0 | 18.2 | | 500 | 173 | 11.5 | 15.0 | | 400 | 126 | 9.2 | 13.7 |
I'm not sharing any how to details because my solution, at this stage, requires additional tools and is too difficult The software solution will be much better if it can reach the efficiency above. I've tried playing with the Antminer L3+ solution https://bitcointalk.org/index.php?topic=3546316.0but there is no "/dev/i2c-0" file on Z9 mini Anyone with more knowledge, please share your thoughts on how to get access to those chips through i2c in a similar way it was done for L3+ |
|
|
|
Could you please add one more feature related to fans? When Customize the fan speed percentage is ticked and set to 0%, all fan detection/monitoring should be disabled or at least ignored. A little bit of background, so because of the noise, people are trying to use no standard fans with fan simulators. Fan detection on Z9 controller gets burned easily by messing up middle pins on fan connector and controller becomes unusable, throwing something like no fan detected, everything else on controller seems to be working fine. So by adding this feature, there will be no more need to purchase fan simulators/spoofers, and everyone that has burned fan detection on controller, will be able to use that controller again.  |
|
|
|
If you have 4 x Z9 mini, you can connect 12 boards to 3 controllers
Interesting. Have you tried this? I have not personally tried it, but I can confirm the code will attempt to initialize 4 boards. -j I've tried all available Z9 and z9 mini firmwares Z9 mini firmware from May 26 - works fine with 3 boards only + overclocking Z9 mini firmware from August 31st - works fine with 4 boards but no overclocking above 550Mhz Z9 firmware from August 28th - works fine with 4 boards but no overclocking above 550Mhz and all temps are messed up Z9 Efudd's Custom Z9 OC Free - works fine with 3 boards and no overclocking above 575Mhz and all temps are messed up Z9 smartass111's Free Unlocked - works fine with 4 boards + unlocked overclocking but all temps are messed up Jason, do you happen to know which file needs to be updated to enable the 4th board on Z9 mini May 26th firmware? I hope it's not the cgminer. minerStatus.html will need to be updated as well but this one is only responsible for displaying the status. Please do not run the Z9 firmware on the mini.. Yes, I know people are saying it is working, but it really is not working the way you might think. There are certain conditions where during a retry algorithm, it will just stop functioning until the next reboot. The reason for this is the number of ASICs expected is hard coded in each binary. Mine works fine with 4 boards, just only 3 are listed.. at least, that's what I expect. Someone else tried it as I only have a Z9 here at the moment and 3 boards. .. so to answer your question, I expect just the status HTML. You can verify yourself by simply calling the API and/or looking a the logs to see if "4" chains are brought up (0-3) or just 3. If you are running my 575OC on a Z9 (not mini) and the temps are messed up, then I would like to know about that because you are the very first person to say that out of 1038 downloads (as of this response). Thank you, Jason I apologize for the confusion, all my tests above have been completed on a Z9 mini so absolutely no objections on the work you have done with your custom firmware, in fact, great job!!! And good luck with adding additional features you're currently working on! Back to Z9 mini firmware from May 26,with unlocked overclocking, only the fist 3 boards are hashing, the fourth one connected to the fourth connector is not displayed in stats and not hashing, the board/heat sinks are cold so it's not hashing at all and updating only the HTML didn't help. |
|
|
|
If you have 4 x Z9 mini, you can connect 12 boards to 3 controllers
Interesting. Have you tried this? I have not personally tried it, but I can confirm the code will attempt to initialize 4 boards. -j I've tried all available Z9 and z9 mini firmwares on the Z9 mini Z9 mini firmware from May 26 - works fine with 3 boards only + overclocking Z9 mini firmware from August 31st - works fine with 4 boards but no overclocking above 550Mhz Z9 firmware from August 28th - works fine with 4 boards but no overclocking above 550Mhz and all temps are messed up Z9 Efudd's Custom Z9 OC Free - works fine with 3 boards and no overclocking above 575Mhz and all temps are messed up Z9 smartass111's Free Unlocked - works fine with 4 boards + unlocked overclocking but all temps are messed up Jason, do you happen to know which file needs to be updated to enable the 4th board on Z9 mini May 26th firmware? I hope it's not the cgminer. minerStatus.html will need to be updated as well but this one is only responsible for displaying the status. |
|
|
|
I think I broke my Z9 Mini.
The fan is not getting recognized anymore:
Oct 11 21:36:21 (none) local0.notice cgminer[1335]: No Fan find, check again
Oct 11 21:36:22 (none) local0.notice cgminer[1335]: No Fan find, check again
Oct 11 21:36:24 (none) local0.notice cgminer[1335]: No Fan find, check again
Oct 11 21:36:25 (none) local0.notice cgminer[1335]: No Fan find, check again
I worked with a fan faker before the miner is not even responding when the original fan is attached.
Is there a work-around to disable the fan check or do I really have to send it in to bitmain?
You have more then one connector on the controllerboard for the fan! Have you tried other fan connector  any loose cables from fan? jiggle them little if bad connection in contact or cables. if nothing else perhaps you can buy controllerboard on ebay or somewhere else good luck! Try another fan before looking a new board, the control board is kinda spendy unless your under warranty. Buying though would have you hashing sooner if needed. Yes, I tried the fan2 connector but still the error. Also I tried other Bitmain fans but still the error occurs. I also flashed the new firmware and resetted the miner completelly with no change. I am in contact with Bitmain about a replacement but this can take time and the difficulty is rising  ... fukmylife Yes, connecting RPM signal from fan to the 12V pin kills the board or at least a part of it and fans are no longer recognized Did you have any luck with Bitmain? If you have 4 x Z9 mini, you can connect 12 boards to 3 controllers |
|
|
|
|
