A4 Dominator - Pre-Order Group Buy - 280mh, roughly 1000w, $1800 + shipping

[lokomotive]

Looks stable. But even older versions worked well when mining single coin and seperate pool. Autoswitches gave it problem.

[1714773362]

1714773362

[1714773362]

1714773362

[1714773362]

1714773362

[Searing]

Looks stable. But even older versions worked well when mining single coin and seperate pool. Autoswitches gave it problem.

Me I have Titans so (up until now with this price may change mind) not worth the  trouble to multipool in that litecoinpool no fee (save 5% multipool fee) and pays out at
103% (so that is 8% savings right there)

Again at these prices IF you have machines that can hack fast switching coins and/or multipools go for it...me I just find if I time when I switch my LTC to BTC when the
ratio is right..it all kinda works out the same (hoard and dump)

Tough sometimes to figure out which works best with btc price up/down/sideways and then the LTC to BTC ratio actually got way better when it dumped to 800 from 1177 btc that is

all very 'voodoo like' imho

All I know is 2 months ago my 3150 mh or just before the A4's really got to shipping I was making 2330 a month after electric etc..now it is 1330 ......

We all need a price pump for LTC and/or other alts to follow or this is all gonna go to the fate of Scrypt-N coins (ask the oldsters about that ..Titan miners were made to
mine scrypt-N asic resistant coins...they did so and blew up the coins in a couple weeks..thus no more scrypt-N ..if you blow difficulty up too fast and the coin has no way
to recover/for use or whatever.....POOF...)

But I mean really..the price of LTC was over 3 bucks at the first of the year BEFORE BTC halving for crying out loud..we need to catch a break on LTC ..this is not looking all that hot.

Watching the LTC difficulty rise (its a sickness) is my new 'morbid' hobby

[kurbeks]

Looks like 4-5% increase in diff again after 2 days

[usao]

Looks like 4-5% increase in diff again after 2 days

Yea, returns are all over the place.
Much of yesterday Nicehash was paying significantly over LTC, overnight I was working well on hash-to-coins, now Nicehash is back paying 0.04 BTC/GH/Day...
Normally the returns are a lot more stable, but past several days have been crazy.
Good thing mine are controlled via a postgres database, doing auto switching of my returns would have been crap the past few days.

[Longsnowsm]

Looks like 4-5% increase in diff again after 2 days

Yea, returns are all over the place.
Much of yesterday Nicehash was paying significantly over LTC, overnight I was working well on hash-to-coins, now Nicehash is back paying 0.04 BTC/GH/Day...
Normally the returns are a lot more stable, but past several days have been crazy.
Good thing mine are controlled via a postgres database, doing auto switching of my returns would have been crap the past few days.

I would love to know how to setup a database to do the switching.  Is there a tutorial or something online for how to do that? 

[usao]

Looks like 4-5% increase in diff again after 2 days

Yea, returns are all over the place.
Much of yesterday Nicehash was paying significantly over LTC, overnight I was working well on hash-to-coins, now Nicehash is back paying 0.04 BTC/GH/Day...
Normally the returns are a lot more stable, but past several days have been crazy.
Good thing mine are controlled via a postgres database, doing auto switching of my returns would have been crap the past few days.

I would love to know how to setup a database to do the switching.  Is there a tutorial or something online for how to do that?  

All custom. Postgresql running on RPI, scrips looks at returns from pool API's, determines best 5-minute average return and current return, and pushes the change to the A4 using web port. Fortunately the A4 dosent require any authentication or it would be more difficult.

[firehawk71]

Looks stable. But even older versions worked well when mining single coin and seperate pool. Autoswitches gave it problem.

I have noticed a huge difference since my re-flash I have Batch 1 and a single batch 2. I am not only stable on litcoinpool now but I am getting very close to the advertised hashrate. On the chart the little spikes are above spec the bottoms of the spike are a tad lower then spec.
Before I got flashed the best I could get on litecoinpool was 245mhs on the set of cubes now I am getting 270Mhs as seen in the graph the total the top line is like 410Mhs most the time.. I have 3 miners so that is 137Mhs each cube more or less.. Also before the re-flash I was still getting many re-boots on litecoinpool but now 8 days straight running it is very smooth.. I saw no difference between litecoinpool and PH payouts.

[vinylwasp]

Me I have Titans so (up until now with this price may change mind) not worth the  trouble to multipool in that litecoinpool no fee (save 5% multipool fee) and pays out at
103% (so that is 8% savings right there)

The payout values at Prohashing and Clevermining are both after fees have been deducted, so on the days they pay out 110% of LTC you're loosing 7% and the days they pay out 130% of LTC you're loosing 27%.

If you want to 'hold and dump', Prohashing will pay you out in any combination of 180 coins in the ratio you choose, including LTC so you can still hold and sell when you see fit, the difference being you could be earning more LTC per day by mining multi coins that are more profitable that day. At the moment I'm being paid out in Monero because the price has been falling and like you I intend to hold them until the price recovers. Next week I may choose Zcash.

I looked at using WhatToMine to decide where to point my miners in an attempt to save the 5% but in the end worked out that it's way simpler and more profitable to rely on the algo that ProHashing use.

[wlefever]

Me I have Titans so (up until now with this price may change mind) not worth the  trouble to multipool in that litecoinpool no fee (save 5% multipool fee) and pays out at
103% (so that is 8% savings right there)

The payout values at Prohashing and Clevermining are both after fees have been deducted, so on the days they pay out 110% of LTC you're loosing 7% and the days they pay out 130% of LTC you're loosing 27%.

If you want to 'hold and dump', Prohashing will pay you out in any combination of 180 coins in the ratio you choose, including LTC so you can still hold and sell when you see fit, the difference being you could be earning more LTC per day by mining multi coins that are more profitable that day. At the moment I'm being paid out in Monero because the price has been falling and like you I intend to hold them until the price recovers. Next week I may choose Zcash.

I looked at using WhatToMine to decide where to point my miners in an attempt to save the 5% but in the end worked out that it's way simpler and more profitable to rely on the algo that ProHashing use.

With that being said is it more profitable to run these at Prohashing or Nicehash?  I haven't been able to flash mine yet with the jig so have just left them on Nicehash getting around 230 MH/s on average each.

I want to hold some Litecoin so I am thinking about switching to Prohashing and taking maybe 80% BTC & 20% of my payout in LTC.  Has anyone split coin payouts there, do you see any value lost by automating the coin % balance?

[usao]

Don't look at the lower hashrate on nicehash. Look at the daily returns and compare that.
All sites (including nicehash) subtract a fee. Then there are transfer fees from your wallet to an LTC/BTC exchange (unless you are mining directly to the exchange).
Then there are the exchange fees,
Then there are the transfer fees from BTC back to your wallet (or additional fees for conversion to local currency).
When you add up all the fees along the way, I get more BTC in the end from nicehash with lower hashrate than I do at LTCpool with higher hashrates.
That said, it can vary. I keep all the historical pool and exchange data in a postgres database so I use querys to determine in real time where is the best place to mine, and switch my miners based on that query.

[vinylwasp]

With that being said is it more profitable to run these at Prohashing or Nicehash?  I haven't been able to flash mine yet with the jig so have just left them on Nicehash getting around 230 MH/s on average each.

I want to hold some Litecoin so I am thinking about switching to Prohashing and taking maybe 80% BTC & 20% of my payout in LTC.  Has anyone split coin payouts there, do you see any value lost by automating the coin % balance?

I don't perceive there to be any value lost with split payouts but one of the other great features of ProHashing is that you can try to work out the answer to your question by reviewing thier really detailed help and the totally transparent daily profit report. https://prohashing.com/profit.html

The difficult part is trying to work out how you'd make a meaningful comparison between pools because there are a number variables to consider such as time of day when the coin was mined, the luck factor (both +ve and -ve), the exchange rate from the coin mined to the payout coin at the time it was processed and the aglo that decides where, when and what to mine and sell.

If you want, they'll also payout in $USD if you have a Coinbase account.

To echo USAO's response below here's what Prohashing say about Hashrate:

Why Hashrate Isn't Everything

It's tempting to look at base hashrate, and arrive at the conclusion that a lower hashrate equals lower payouts. However, the relationship between hashrate and payouts is much more complicated.

Periodically, a coin has a period of low difficulty that increases its profitability to a very high level. The pool will switch some miners to that coin during these intervals. During these periods, base hashrate will appear to be lower than during periods when only litecoins are being mined because work restarts decrease hashrate. However, profitability during these periods is higher, because the blocks being mined are more valuable. Consider the following situation, which arises commonly during mining:

    Mine litecoins: Achieve 1 MH/s at 3 cents per MH/s/day = 3 cents per day
    Mine casinocoins: Achieve 0.5MH/s at 10 cents per MH/s/day = 5 cents per day

In this instance, it appears at first glance that mining casinocoins is suboptimal because the frequent work restarts lower hashrate. However, the math above demonstrates that the expected value of mining casinocoins is superior to that of mining litecoins, even though the hashrate of mining casinocoins is only half that of mining litecoins.

On cloud mining providers like Nicehash, "negative deltas" and other errors may appear that indicate that some hashrate is being wasted due to work restarts. Prohashing only sends work restarts when doing so would gain more profit even after the restart losses than would continuing to mine the same coin. When using these services, compare actual profitability at several pools to see where you can make the most money, rather than deciding by hashrate alone.

HTH

[Eyedol-X]

Another Update.

So after about 2-3 Hours of working normally after this post, the A4 went down again and started boot looping every 5 mins or so. I didn't have opportunity to check on it overnight and the next morning I found it completely offline and the Pi unable to be reached via ping, ssh, or accessible via web interface.

I power-cycled the entire unit and it came back online normally. Within 5 minutes, it rebooted again. I got the A4 back up and stopped mining. I changed the speed to 1000mhz and started it mining, rebooted again within 5 mins.

I want to stress this is the Pi rebooting for what appears to be a script going off, the A4 appears to be hashing normally when it happens.

I reapplied all the settings, set everything to 1200mhz, typed back in my pool information, added a 3rd pool and started mining again.

Now its be running for over 9 hours on PH without an issue.  

I've got new SD cards coming today and I'm going to replace the one in the Pi with a fresh 2.0.2 image/sd card the next time it goes down again.

I'm fairly certain at this point that I have not seen the end of this issue.

I reached out to Inno for assistance in steps I can take if this issue persists after I replace the SD Card / Image.

Hi Eyedol,

From the feedback of our customer who use v2.0.2beta, the performance of the A4 is stable without reboots issues. So something is wrong here.

Just curious that you can access to the SSH because till now we didn't open source. Please DON'T CHANGE CODE RANDOMLY. Because we don't know what will happen when you changed the code on your side.

For now, please get the Pi restarted first then try the new SD card.
We are glad to help if you need.

Inno Support Team

So after ~6 Days since my last post the A4 ran without issue on Prohash, until about ~2 hours ago now.

A couple of clarifications:

• I'm sharing this information with everyone here to be transparent with the community about my experience and hopefully as a community we can all find a solution to the issue(s) being experienced with the A4 at this time. I can be frustrated at times but I know this will get fixed, in time. My goal here is to communicate and collaborate with everyone involved
• I want to say thanks to Dominique, Chloe, and everyone at Innosilicon for their efforts in supporting us with the A4 issues we have been experiencing thus far.

In regards to changing the code randomly, at this time I have not changed any code. What I have done is deleted log files from the Pi and let the miner create fresh ones on a reboot and I've been attempting to review them. I've extracted the SD card images on my computer and have been trying to find whats causing the reboots over what I suspected(now confirmed) was 1 Get Failure.

In regards to SSH, My Raspberry Pi was configured the default username and password so I was able to easily login to it and start looking around.

I have a new SD card with a Fresh 2.0.2 image that I've been waiting to install in the A4, that will now happen this weekend since it's now rebooted again. I'm going to do what I'm now calling the "Reboot Dance" today to see if I can get it stable and mining again since it will be 2 days before I can get out to my remote site. I have no idea why its doing this or why it suddenly starts/stops working other than this information below.

I can now confirm that 1 Get Failure causes the Pi to reboot. User MjGraham has reported a similar issue in another thread so I'm going to include his response below.

Does look like any type of connection issue now reboots the Pi, internet goes down, reboot loop, pool goes down reboot loop. Why we decided to do this I have no idea.

Screen Capture I got on a 10 second refresh of 1 Get Failure this morning just before the Pi rebooted itself. Hope this information helps.



EDIT:

Stopped the A4 and set startup to Manual, left it there for about 15 mins, started it back up and its been running fine for about an hour now. Previously it was stuck in the reboot loop described above. Did not power-cycle the A4 or reboot the Pi manually this time around.

[jacobmayes94]

We have a new LTC pool to signal segwit support: www.sparkpool.org, a PPLNS pool. Looking for some miners This is not a multipool but a standard LTC pool.

[Chazaki]

My A4 will only hash at 200 mh/s on litecoinpool.org (or any other pool) for some reason. All of my boards are healthy, and the miner UI says its working at 275 mh/s. Hardware errors are %0.02 Device rejected is %0.05 and Pool Rejected is %0.05. I don't understand what is going on that would account for the discrepancy between local and pool hash rates... Anyone have any ideas/advice?

[kurbeks]

You tried hard restart. Just in case.

[Chazaki]

You tried hard restart. Just in case.

I have done - it doesn't seem to have any effect

[Rabinovitch]

Anyone have any ideas/advice?

Have you upgraded the firmware?

[firehawk71]

My A4 will only hash at 200 mh/s on litecoinpool.org (or any other pool) for some reason. All of my boards are healthy, and the miner UI says its working at 275 mh/s. Hardware errors are %0.02 Device rejected is %0.05 and Pool Rejected is %0.05. I don't understand what is going on that would account for the discrepancy between local and pool hash rates... Anyone have any ideas/advice?

You might try setting the difficulty manualy on litecoinpool.. It seemed to help me get a higher hashrate then letting the pool set it. This is what I use the xxx is just my password but it must be typed in quotes and coma with no space like this
"xxx,d=8192" And I set my mv at 830 and 1248Mhs

[Chazaki]

Anyone have any ideas/advice?

Have you upgraded the firmware?

I have, I am running 2.0.1.

My A4 will only hash at 200 mh/s on litecoinpool.org (or any other pool) for some reason. All of my boards are healthy, and the miner UI says its working at 275 mh/s. Hardware errors are %0.02 Device rejected is %0.05 and Pool Rejected is %0.05. I don't understand what is going on that would account for the discrepancy between local and pool hash rates... Anyone have any ideas/advice?

You might try setting the difficulty manualy on litecoinpool.. It seemed to help me get a higher hashrate then letting the pool set it. This is what I use the xxx is just my password but it must be typed in quotes and coma with no space like this
"xxx,d=8192" And I set my mv at 830 and 1248Mhs

I have also tried setting manual difficulty and unfortunately it didn't help at all. In fact, moving the voltage up and core speed up actually lowered my poolside hash rate (although it increased my local hash rate quite a bit). Im honestly quite stumped on this one...

Here is a picture of my stats after almost 40 minutes of uptime:


As you can see, one of the boards is getting rejected poolside %0.43... I have no idea what could be accounting for these rejected shares, but on a long enough timeline (few hours) it seems to settle down to around %0.1. on all boards.

[Eyedol-X]

Anyone have any ideas/advice?

Have you upgraded the firmware?

I have, I am running 2.0.1.

My A4 will only hash at 200 mh/s on litecoinpool.org (or any other pool) for some reason. All of my boards are healthy, and the miner UI says its working at 275 mh/s. Hardware errors are %0.02 Device rejected is %0.05 and Pool Rejected is %0.05. I don't understand what is going on that would account for the discrepancy between local and pool hash rates... Anyone have any ideas/advice?

You might try setting the difficulty manualy on litecoinpool.. It seemed to help me get a higher hashrate then letting the pool set it. This is what I use the xxx is just my password but it must be typed in quotes and coma with no space like this
"xxx,d=8192" And I set my mv at 830 and 1248Mhs

I have also tried setting manual difficulty and unfortunately it didn't help at all. In fact, moving the voltage up and core speed up actually lowered my poolside hash rate (although it increased my local hash rate quite a bit). Im honestly quite stumped on this one...

Here is a picture of my stats after almost 40 minutes of uptime:


As you can see, one of the boards is getting rejected poolside %0.43... I have no idea what could be accounting for these rejected shares, but on a long enough timeline (few hours) it seems to settle down to around %0.1. on all boards.

2.0.2 is current firmware -- I don't know if this will resolve your issue but just an FYI.

I am starting to find that setting static difficulty poolside causes issues with these miners. I want to stress that this is very preliminary information but I've been having trouble with mine and recently switched it to dynamic and for 3 days now its like a different machine running with PH. Previously I had been setting static difficulty poolside and been having nothing but problems with B3.

Here is a download link for 2.0.2 from another thread that I used to download it. This is not my dropbox share or link -- https://www.dropbox.com/s/9umhsbtky6t1c6j/2.0.2beta.rar?dl=0