I'm waiting for their 2nd batch to consider this again..probably NOV/DEC .....5 units would put a crip in that plan
(I'm trying to keep an open mind...a price pump of LTC would go a long way towards my 'openmindedness' towards these miners price and warranty wise)
If we could find someone that knows what there doing and we can trust. Maybe we could start a fund pool to buy them one unit in exchange they fix it and the miner could be there payment.
Topic: A4 Dominator - Pre-Order Group Buy - 280mh, roughly 1000w, $1800 + shipping (Read 122523 times)
August 01, 2018, 03:11:45 AM
May 14, 2018, 02:14:54 AM
These things definitely need firmware update cause mine still dropped speeds after hashing for about 1.5 days. Something is not right at power level cause its either some sort of leak or just capacitor giving false signals and then safety feature kicks in. Heat is not an issue as mine are in labrador and its currently very cold over there.
May 14, 2018, 02:12:13 AM
Has anyone tried an A4 on LiteGuardien yet?
I remember a LOT of commentary when the Alcheminer (and it's OEM versions/clones) first showed up about it being VERY flaky on many pools but a couple (including LiteGuardian) let it run reliably even in the early software versions for it.
I remember a LOT of commentary when the Alcheminer (and it's OEM versions/clones) first showed up about it being VERY flaky on many pools but a couple (including LiteGuardian) let it run reliably even in the early software versions for it.
May 12, 2018, 02:19:11 AM
If we could find someone that knows what there doing and we can trust. Maybe we could start a fund pool to buy them one unit in exchange they fix it and the miner could be there payment.. Just a idea
May 12, 2018, 02:09:21 AM
Has anyone tried an A4 on LiteGuardien yet?
I remember a LOT of commentary when the Alcheminer (and it's OEM versions/clones) first showed up about it being VERY flaky on many pools but a couple (including LiteGuardian) let it run reliably even in the early software versions for it.
I remember a LOT of commentary when the Alcheminer (and it's OEM versions/clones) first showed up about it being VERY flaky on many pools but a couple (including LiteGuardian) let it run reliably even in the early software versions for it.
April 20, 2018, 03:04:24 AM
Dear customers,
our website have been updated. You can click here (http://www.innosilicon.com/html/product/index.html) to browse and order our all miners. Please enter "Ctrl+F5" to refresh the web if you have opened it before. We will continuously optimize the website to give you a better experience. Thanks!
our website have been updated. You can click here (http://www.innosilicon.com/html/product/index.html) to browse and order our all miners. Please enter "Ctrl+F5" to refresh the web if you have opened it before. We will continuously optimize the website to give you a better experience. Thanks!
March 27, 2018, 07:36:36 AM
anyone know the password for the G5-20-V1.1.1TF image for SSH the controller with the Orange PI .? .... or SSH login .
Try 'innosilicon' 
March 27, 2018, 07:27:09 AM
anyone know the password for the G5-20-V1.1.1TF image for SSH the controller with the Orange PI .? .... or SSH login .
November 18, 2017, 04:10:47 AM
I have a batch 2 A4 that needs the boards flashed. I've got a ST-link programmer and have identified the pins to program the microcontroller on the boards, but I don't have the newer firmware image to flash. Actual microcontroller image, not the SD card image that people are calling firmware. Does anyone have any solutions? Be it the mythical jig or something I could flash, or anything else, any input would be appreciated. I'm currently running 1.0.3 SD card image software.
November 08, 2017, 09:44:05 PM
I have a love / hate relationship with NiceHash. I appreciate the simplicity of it, and I personally prefer my mining proceeds to be in bitcoin rather than any altcoin at the moment. But, I can't help but feel like there is some sort of issue with these things and NiceHash and not getting our full hashrate out of them. I had tried ProHashing - love their interface and graphs, but felt like the income was slightly less. I have just now moved one of them over to ZPool.CA to check it out. My average hashrate at NiceHash without overclocking was around 490-ish for 2 A4s. After overclocking today for a few hours, the average on the graph for that period of time is about 515. So an increase of 166 hash between the two of them resulted in an increase of only about 25 at the pool average. I will admit I'm not being very scientific about this - if I was more patient I would split them between two pools and compare across several days. I also have 2 gaming PCs (single GPU) pointed at NiceHash so I can't even look at my daily earnings as a measure since those are pulling in a couple bucks themselves and I don't see an easy way to differentiate earnings in the NiceHash payment transactions. I may end up doing that comparison but I'm still learning and tinkering at this point so I'm probably not the best metric for this.
I also wonder if the Orange Pi could somehow be causing diminishing returns somehow - maybe that's why they're designed to support 3 tubes but they only came with 2? So another test could be running overclocked single tubes on controllers by themselves to see if that is an issue.
Here's the graph with the time block highlighted where the 2 A4s were there overclocked. I have only one there now, moved the other to zpool as I mentioned. The one at Zpool has been there now for 4 hours and 10 minutes and the unpaid balance is already 0.00045771 BTC - if that pace holds up then zpool might end up being waaay more profitable.
https://i.imgur.com/NoA7P9V.jpg
I also wonder if the Orange Pi could somehow be causing diminishing returns somehow - maybe that's why they're designed to support 3 tubes but they only came with 2? So another test could be running overclocked single tubes on controllers by themselves to see if that is an issue.
Here's the graph with the time block highlighted where the 2 A4s were there overclocked. I have only one there now, moved the other to zpool as I mentioned. The one at Zpool has been there now for 4 hours and 10 minutes and the unpaid balance is already 0.00045771 BTC - if that pace holds up then zpool might end up being waaay more profitable.
https://i.imgur.com/NoA7P9V.jpg
November 08, 2017, 06:59:53 PM
Anyone else tinker with overclocking these?
I have 2 so far and 2 more on the way tomorrow, all used. The 2 I already have are newer ones (april & june 2017) with Orange Pi controllers, running firmware v1.1.1. Using the login creds previously mentioned in this thread (root/innosilicon), I am launching the cgminer manually with a clock value of 1600 instead of 1248. This results in the hashing rate being around 364 instead of 276. I kept the voltage at the default value of 820. So far stable, temps are virtually unchanged. Can't get any higher than 1600 tho, I think that might be because the PLL or something runs at 1600 as well (saw something about this in the log). I figure if my temps are normal and voltage was not bumped any higher, how bad could it be. Result is about a 32% overclock. I'm assuming this is only possible because I have newer batches, so don't take this as a good reference point if you have older ones. Just wondering if anyone else was tinkering with overclocking these to squeeze every last ounce out of them, and if so what you did to get above 1600.
Another thing I'd like to try is get ahold of the firmware from an A4+ once they're around - wondering if the newer build of cgminer in there might have some improvements that could be copied over to this build.
Go to the web page, stop mining if you have it already mining. Putty into the miner, change directory to /var/www, and here is the command I use (changed the worker name in case anyone wants to donate some mining time to me in return for this info, so if not change that part to your own pool info)
sudo ./cgminer -o stratum+tcp://scrypt.usa.nicehash.com:3333/#xnsub -u 3Qk7dwXXn1Qr2jfK2aetLZod43v5sJy4ow.Donate -p x --A1Pll1 1600 --A1Pll2 1600 --A1Pll3 1600 --A1Pll4 1600 --A1Pll5 1600 --A1Pll6 1600 --A1Vol 820 --diff 8 --api-listen --api-network --cs 8 --stmcu 0 --hwreset > cgminer.log &
https://i.imgur.com/Mh98xJ5.jpg
I have 2 so far and 2 more on the way tomorrow, all used. The 2 I already have are newer ones (april & june 2017) with Orange Pi controllers, running firmware v1.1.1. Using the login creds previously mentioned in this thread (root/innosilicon), I am launching the cgminer manually with a clock value of 1600 instead of 1248. This results in the hashing rate being around 364 instead of 276. I kept the voltage at the default value of 820. So far stable, temps are virtually unchanged. Can't get any higher than 1600 tho, I think that might be because the PLL or something runs at 1600 as well (saw something about this in the log). I figure if my temps are normal and voltage was not bumped any higher, how bad could it be. Result is about a 32% overclock. I'm assuming this is only possible because I have newer batches, so don't take this as a good reference point if you have older ones. Just wondering if anyone else was tinkering with overclocking these to squeeze every last ounce out of them, and if so what you did to get above 1600.
Another thing I'd like to try is get ahold of the firmware from an A4+ once they're around - wondering if the newer build of cgminer in there might have some improvements that could be copied over to this build.
Go to the web page, stop mining if you have it already mining. Putty into the miner, change directory to /var/www, and here is the command I use (changed the worker name in case anyone wants to donate some mining time to me in return for this info, so if not change that part to your own pool info)
sudo ./cgminer -o stratum+tcp://scrypt.usa.nicehash.com:3333/#xnsub -u 3Qk7dwXXn1Qr2jfK2aetLZod43v5sJy4ow.Donate -p x --A1Pll1 1600 --A1Pll2 1600 --A1Pll3 1600 --A1Pll4 1600 --A1Pll5 1600 --A1Pll6 1600 --A1Vol 820 --diff 8 --api-listen --api-network --cs 8 --stmcu 0 --hwreset > cgminer.log &
https://i.imgur.com/Mh98xJ5.jpg
Nice overclock. Powerdraw per Mhash should be same as with stock cloks. As you didn't up voltage.
So, what is your real hashrate at nicehash? Can you show me your graph?
November 08, 2017, 03:06:59 PM
Anyone else tinker with overclocking these?
I have 2 so far and 2 more on the way tomorrow, all used. The 2 I already have are newer ones (april & june 2017) with Orange Pi controllers, running firmware v1.1.1. Using the login creds previously mentioned in this thread (root/innosilicon), I am launching the cgminer manually with a clock value of 1600 instead of 1248. This results in the hashing rate being around 364 instead of 276. I kept the voltage at the default value of 820. So far stable, temps are virtually unchanged. Can't get any higher than 1600 tho, I think that might be because the PLL or something runs at 1600 as well (saw something about this in the log). I figure if my temps are normal and voltage was not bumped any higher, how bad could it be. Result is about a 32% overclock. I'm assuming this is only possible because I have newer batches, so don't take this as a good reference point if you have older ones. Just wondering if anyone else was tinkering with overclocking these to squeeze every last ounce out of them, and if so what you did to get above 1600.
Another thing I'd like to try is get ahold of the firmware from an A4+ once they're around - wondering if the newer build of cgminer in there might have some improvements that could be copied over to this build.
Go to the web page, stop mining if you have it already mining. Putty into the miner, change directory to /var/www, and here is the command I use (changed the worker name in case anyone wants to donate some mining time to me in return for this info, so if not change that part to your own pool info)
sudo ./cgminer -o stratum+tcp://scrypt.usa.nicehash.com:3333/#xnsub -u 3Qk7dwXXn1Qr2jfK2aetLZod43v5sJy4ow.Donate -p x --A1Pll1 1600 --A1Pll2 1600 --A1Pll3 1600 --A1Pll4 1600 --A1Pll5 1600 --A1Pll6 1600 --A1Vol 820 --diff 8 --api-listen --api-network --cs 8 --stmcu 0 --hwreset > cgminer.log &
I have 2 so far and 2 more on the way tomorrow, all used. The 2 I already have are newer ones (april & june 2017) with Orange Pi controllers, running firmware v1.1.1. Using the login creds previously mentioned in this thread (root/innosilicon), I am launching the cgminer manually with a clock value of 1600 instead of 1248. This results in the hashing rate being around 364 instead of 276. I kept the voltage at the default value of 820. So far stable, temps are virtually unchanged. Can't get any higher than 1600 tho, I think that might be because the PLL or something runs at 1600 as well (saw something about this in the log). I figure if my temps are normal and voltage was not bumped any higher, how bad could it be. Result is about a 32% overclock. I'm assuming this is only possible because I have newer batches, so don't take this as a good reference point if you have older ones. Just wondering if anyone else was tinkering with overclocking these to squeeze every last ounce out of them, and if so what you did to get above 1600.
Another thing I'd like to try is get ahold of the firmware from an A4+ once they're around - wondering if the newer build of cgminer in there might have some improvements that could be copied over to this build.
Go to the web page, stop mining if you have it already mining. Putty into the miner, change directory to /var/www, and here is the command I use (changed the worker name in case anyone wants to donate some mining time to me in return for this info, so if not change that part to your own pool info)
sudo ./cgminer -o stratum+tcp://scrypt.usa.nicehash.com:3333/#xnsub -u 3Qk7dwXXn1Qr2jfK2aetLZod43v5sJy4ow.Donate -p x --A1Pll1 1600 --A1Pll2 1600 --A1Pll3 1600 --A1Pll4 1600 --A1Pll5 1600 --A1Pll6 1600 --A1Vol 820 --diff 8 --api-listen --api-network --cs 8 --stmcu 0 --hwreset > cgminer.log &
Nice overclock. Powerdraw per Mhash should be same as with stock cloks. As you didn't up voltage.
November 08, 2017, 12:38:49 PM
Anyone else tinker with overclocking these?
I have 2 so far and 2 more on the way tomorrow, all used. The 2 I already have are newer ones (april & june 2017) with Orange Pi controllers, running firmware v1.1.1. Using the login creds previously mentioned in this thread (root/innosilicon), I am launching the cgminer manually with a clock value of 1600 instead of 1248. This results in the hashing rate being around 364 instead of 276. I kept the voltage at the default value of 820. So far stable, temps are virtually unchanged. Can't get any higher than 1600 tho, I think that might be because the PLL or something runs at 1600 as well (saw something about this in the log). I figure if my temps are normal and voltage was not bumped any higher, how bad could it be. Result is about a 32% overclock. I'm assuming this is only possible because I have newer batches, so don't take this as a good reference point if you have older ones. Just wondering if anyone else was tinkering with overclocking these to squeeze every last ounce out of them, and if so what you did to get above 1600.
Another thing I'd like to try is get ahold of the firmware from an A4+ once they're around - wondering if the newer build of cgminer in there might have some improvements that could be copied over to this build.
Go to the web page, stop mining if you have it already mining. Putty into the miner, change directory to /var/www, and here is the command I use (changed the worker name in case anyone wants to donate some mining time to me in return for this info, so if not change that part to your own pool info)
sudo ./cgminer -o stratum+tcp://scrypt.usa.nicehash.com:3333/#xnsub -u 3Qk7dwXXn1Qr2jfK2aetLZod43v5sJy4ow.Donate -p x --A1Pll1 1600 --A1Pll2 1600 --A1Pll3 1600 --A1Pll4 1600 --A1Pll5 1600 --A1Pll6 1600 --A1Vol 820 --diff 8 --api-listen --api-network --cs 8 --stmcu 0 --hwreset > cgminer.log &
https://i.imgur.com/Mh98xJ5.jpg
I have 2 so far and 2 more on the way tomorrow, all used. The 2 I already have are newer ones (april & june 2017) with Orange Pi controllers, running firmware v1.1.1. Using the login creds previously mentioned in this thread (root/innosilicon), I am launching the cgminer manually with a clock value of 1600 instead of 1248. This results in the hashing rate being around 364 instead of 276. I kept the voltage at the default value of 820. So far stable, temps are virtually unchanged. Can't get any higher than 1600 tho, I think that might be because the PLL or something runs at 1600 as well (saw something about this in the log). I figure if my temps are normal and voltage was not bumped any higher, how bad could it be. Result is about a 32% overclock. I'm assuming this is only possible because I have newer batches, so don't take this as a good reference point if you have older ones. Just wondering if anyone else was tinkering with overclocking these to squeeze every last ounce out of them, and if so what you did to get above 1600.
Another thing I'd like to try is get ahold of the firmware from an A4+ once they're around - wondering if the newer build of cgminer in there might have some improvements that could be copied over to this build.
Go to the web page, stop mining if you have it already mining. Putty into the miner, change directory to /var/www, and here is the command I use (changed the worker name in case anyone wants to donate some mining time to me in return for this info, so if not change that part to your own pool info)
sudo ./cgminer -o stratum+tcp://scrypt.usa.nicehash.com:3333/#xnsub -u 3Qk7dwXXn1Qr2jfK2aetLZod43v5sJy4ow.Donate -p x --A1Pll1 1600 --A1Pll2 1600 --A1Pll3 1600 --A1Pll4 1600 --A1Pll5 1600 --A1Pll6 1600 --A1Vol 820 --diff 8 --api-listen --api-network --cs 8 --stmcu 0 --hwreset > cgminer.log &
https://i.imgur.com/Mh98xJ5.jpg
October 19, 2017, 10:31:39 AM
Anyone interested in buying the original A4 miner? I have 3 from last November looking to sell.
Make offers.
Make offers.
What kind of hashpower did you get from them? Where are you shipping them from and what kind of price do you have in mind?
They are in Arizona, nice and dry/clean. No rust or anything like that.
Price, probably around 0.2 BTC.
I also have seasonic PSU with PCIe cables if needed for around 0.02 BTC.
October 19, 2017, 07:23:30 AM
Anyone interested in buying the original A4 miner? I have 3 from last November looking to sell.
Make offers.
Make offers.
What kind of hashpower did you get from them? Where are you shipping them from and what kind of price do you have in mind?
October 19, 2017, 07:16:32 AM
Orange PI - TF version 1.1.1 (G5-20-V1.1.1TF) SSH password is:
login: root
password: innosilicon
Got all my workers, but still working bad. Changed ISP with lower pings.
From 6 tubes and 3 controllers im getting average of 737Mh/s on nicehash. That is 245 per unit.
login: root
password: innosilicon
Got all my workers, but still working bad. Changed ISP with lower pings.
From 6 tubes and 3 controllers im getting average of 737Mh/s on nicehash. That is 245 per unit.
October 13, 2017, 02:57:24 PM
Anyone interested in buying the original A4 miner? I have 3 from last November looking to sell.
Make offers.
Make offers.
October 13, 2017, 01:03:27 PM
Hey,
Recently I bought Innosilicon A4 Dominator miners but I'm really unsatisfied with my Nicehash results. Miners are updated with suggested firmware but still I'm getting very low real hashrate. This guy here is getting stable 272MH/s but im not even close to this result... I don't know from what batch are my miners.
Miners are working at 825MH/s total power but nicehash medium result from 6 hours is only 696MH/s - graph from nicehash. Im using xnsub parameter. Here is my miner statistics page from one node - I have two of them.
Because of controller failure I have 3 tubes in one controller but with two tubes in one controller results are that same weak... My controllers are TF card - Orange Pi. Ping to nicehash is 80ms.
Can you show me your results or have some suggestions to me?
I'm really disappointed, was wondering to invest more for L3+ but calculations resulted in favor of A4 products but not in this case. L3+ users are getting stable 488MH/s out of box when miner speed is 504MH/s!
Here are some cgminer summary:
[2017-10-10 23:22:16.876941] BA20 | (5s):68.92M | A:1998848 R:65536 HW:1 WU:48482.6/m
[2017-10-10 23:22:16.877127] BA21 | (5s):68.92M | A:2490368 R:229376 HW:78 WU:63873.8/m
[2017-10-10 23:22:16.877305] BA22 | (5s):68.92M | A:2228221 R:65536 HW:41 WU:53869.4/m
[2017-10-10 23:22:16.877495] BA23 | (5s):68.86M | A:1802239 R:32768 HW:71 WU:43095.6/m
[2017-10-11 00:27:11.848768] BA21 | (5s):70.30M | A:12025855 R:1048576 HW:136 WU:58184.4/m
[2017-10-11 00:27:11.848958] BA22 | (5s):70.30M | A:12877824 R:786432 HW:77 WU:60809.3/m
[2017-10-11 00:27:11.849159] BA23 | (5s):70.30M | A:10190848 R:393216 HW:1019 WU:47101.7/m
[2017-10-11 00:27:11.849356] BA24 | (5s):70.30M | A:11829247 R:589824 HW:705 WU:55267.9/m
[2017-10-11 00:27:11.849541] BA25 | (5s):70.30M | A:12353536 R:294912 HW:743 WU:56872.0/m
Really thanks for any help.
Recently I bought Innosilicon A4 Dominator miners but I'm really unsatisfied with my Nicehash results. Miners are updated with suggested firmware but still I'm getting very low real hashrate. This guy here is getting stable 272MH/s but im not even close to this result... I don't know from what batch are my miners.
Miners are working at 825MH/s total power but nicehash medium result from 6 hours is only 696MH/s - graph from nicehash. Im using xnsub parameter. Here is my miner statistics page from one node - I have two of them.
Because of controller failure I have 3 tubes in one controller but with two tubes in one controller results are that same weak... My controllers are TF card - Orange Pi. Ping to nicehash is 80ms.
Can you show me your results or have some suggestions to me?
I'm really disappointed, was wondering to invest more for L3+ but calculations resulted in favor of A4 products but not in this case. L3+ users are getting stable 488MH/s out of box when miner speed is 504MH/s!
Here are some cgminer summary:
[2017-10-10 23:22:16.876941] BA20 | (5s):68.92M | A:1998848 R:65536 HW:1 WU:48482.6/m
[2017-10-10 23:22:16.877127] BA21 | (5s):68.92M | A:2490368 R:229376 HW:78 WU:63873.8/m
[2017-10-10 23:22:16.877305] BA22 | (5s):68.92M | A:2228221 R:65536 HW:41 WU:53869.4/m
[2017-10-10 23:22:16.877495] BA23 | (5s):68.86M | A:1802239 R:32768 HW:71 WU:43095.6/m
[2017-10-11 00:27:11.848768] BA21 | (5s):70.30M | A:12025855 R:1048576 HW:136 WU:58184.4/m
[2017-10-11 00:27:11.848958] BA22 | (5s):70.30M | A:12877824 R:786432 HW:77 WU:60809.3/m
[2017-10-11 00:27:11.849159] BA23 | (5s):70.30M | A:10190848 R:393216 HW:1019 WU:47101.7/m
[2017-10-11 00:27:11.849356] BA24 | (5s):70.30M | A:11829247 R:589824 HW:705 WU:55267.9/m
[2017-10-11 00:27:11.849541] BA25 | (5s):70.30M | A:12353536 R:294912 HW:743 WU:56872.0/m
Really thanks for any help.
Are you on V2.0.3beta?
Ensure that you are on this firmware or better.
For Nicehash, the #xnsub wont work with A4s -- the L3+ does not support #xnsub too.
I get 280MHs++ consistently by just putting "d=131072" in password field.
My A4s are 815mV.
Still the same weak result... I disconnected one tube due to replacement.
WORKER81: 2 tubes 280MH/s (innosilicon value)
WORKER82: 3 tubes 420MH/s (innosilicon value)
Expected real nicehash value 272MH/s + 408MH/s = 680MH/s (as showed by nicehash on firmware update news)
Real reached nicehash value 556MH/s
GRAPH
Till today I tested this values:
d=131072, d=65536, x as password
810mV/815mV/820mV
clock 1000MHz, 1200MHz, 1244MHz
--queue 0
--scan-time 1
--expiry 1
Stratum proxy (results very weak).
Wanted to test Raspberry cgminer but it's not working on Orange PI. Don't know where to download older TF card versions to test older cgminers (<1.1.0).
Sadly that nicehash is not providing graphs for individual workers.
Anyone has different ideas?
October 11, 2017, 10:37:16 AM
Maybe should I use older firmware? I run now at V1.1.0 because I have TF version - Orange Pi.
This version was released with V2.1.0 for SD so its probably the same version of cgminer for another hardware. I got message that XNSUB is working. Maybe I should also remove #xnsub parameter from url?
Restarted miners: both with d=131072, one with #xnsub, second without. I'll let it run for few hours and write results here.
This version was released with V2.1.0 for SD so its probably the same version of cgminer for another hardware. I got message that XNSUB is working. Maybe I should also remove #xnsub parameter from url?
Restarted miners: both with d=131072, one with #xnsub, second without. I'll let it run for few hours and write results here.
October 11, 2017, 10:15:06 AM
Hey,
Recently I bought Innosilicon A4 Dominator miners but I'm really unsatisfied with my Nicehash results. Miners are updated with suggested firmware but still I'm getting very low real hashrate. This guy here is getting stable 272MH/s but im not even close to this result... I don't know from what batch are my miners.
Miners are working at 825MH/s total power but nicehash medium result from 6 hours is only 696MH/s - graph from nicehash. Im using xnsub parameter. Here is my miner statistics page from one node - I have two of them.
Because of controller failure I have 3 tubes in one controller but with two tubes in one controller results are that same weak... My controllers are TF card - Orange Pi. Ping to nicehash is 80ms.
Can you show me your results or have some suggestions to me?
I'm really disappointed, was wondering to invest more for L3+ but calculations resulted in favor of A4 products but not in this case. L3+ users are getting stable 488MH/s out of box when miner speed is 504MH/s!
Here are some cgminer summary:
[2017-10-10 23:22:16.876941] BA20 | (5s):68.92M | A:1998848 R:65536 HW:1 WU:48482.6/m
[2017-10-10 23:22:16.877127] BA21 | (5s):68.92M | A:2490368 R:229376 HW:78 WU:63873.8/m
[2017-10-10 23:22:16.877305] BA22 | (5s):68.92M | A:2228221 R:65536 HW:41 WU:53869.4/m
[2017-10-10 23:22:16.877495] BA23 | (5s):68.86M | A:1802239 R:32768 HW:71 WU:43095.6/m
[2017-10-11 00:27:11.848768] BA21 | (5s):70.30M | A:12025855 R:1048576 HW:136 WU:58184.4/m
[2017-10-11 00:27:11.848958] BA22 | (5s):70.30M | A:12877824 R:786432 HW:77 WU:60809.3/m
[2017-10-11 00:27:11.849159] BA23 | (5s):70.30M | A:10190848 R:393216 HW:1019 WU:47101.7/m
[2017-10-11 00:27:11.849356] BA24 | (5s):70.30M | A:11829247 R:589824 HW:705 WU:55267.9/m
[2017-10-11 00:27:11.849541] BA25 | (5s):70.30M | A:12353536 R:294912 HW:743 WU:56872.0/m
Really thanks for any help.
Recently I bought Innosilicon A4 Dominator miners but I'm really unsatisfied with my Nicehash results. Miners are updated with suggested firmware but still I'm getting very low real hashrate. This guy here is getting stable 272MH/s but im not even close to this result... I don't know from what batch are my miners.
Miners are working at 825MH/s total power but nicehash medium result from 6 hours is only 696MH/s - graph from nicehash. Im using xnsub parameter. Here is my miner statistics page from one node - I have two of them.
Because of controller failure I have 3 tubes in one controller but with two tubes in one controller results are that same weak... My controllers are TF card - Orange Pi. Ping to nicehash is 80ms.
Can you show me your results or have some suggestions to me?
I'm really disappointed, was wondering to invest more for L3+ but calculations resulted in favor of A4 products but not in this case. L3+ users are getting stable 488MH/s out of box when miner speed is 504MH/s!
Here are some cgminer summary:
[2017-10-10 23:22:16.876941] BA20 | (5s):68.92M | A:1998848 R:65536 HW:1 WU:48482.6/m
[2017-10-10 23:22:16.877127] BA21 | (5s):68.92M | A:2490368 R:229376 HW:78 WU:63873.8/m
[2017-10-10 23:22:16.877305] BA22 | (5s):68.92M | A:2228221 R:65536 HW:41 WU:53869.4/m
[2017-10-10 23:22:16.877495] BA23 | (5s):68.86M | A:1802239 R:32768 HW:71 WU:43095.6/m
[2017-10-11 00:27:11.848768] BA21 | (5s):70.30M | A:12025855 R:1048576 HW:136 WU:58184.4/m
[2017-10-11 00:27:11.848958] BA22 | (5s):70.30M | A:12877824 R:786432 HW:77 WU:60809.3/m
[2017-10-11 00:27:11.849159] BA23 | (5s):70.30M | A:10190848 R:393216 HW:1019 WU:47101.7/m
[2017-10-11 00:27:11.849356] BA24 | (5s):70.30M | A:11829247 R:589824 HW:705 WU:55267.9/m
[2017-10-11 00:27:11.849541] BA25 | (5s):70.30M | A:12353536 R:294912 HW:743 WU:56872.0/m
Really thanks for any help.
Are you on V2.0.3beta?
Ensure that you are on this firmware or better.
For Nicehash, the #xnsub wont work with A4s -- the L3+ does not support #xnsub too.
I get 280MHs++ consistently by just putting "d=131072" in password field.
My A4s are 815mV.
Jump to: