The source of the problem appears to be that the data exported from Bittrex does not match what the spreadsheet is expecting to see. There are definitely fewer fields coming from Bittrex than there are columns that expect data in the spreadsheet.

How do you get that type of status reporting for the ewbfminer? I don't get any hashrates (or anything) in the local console or in the miner.farm site.

The comparisons being made in this thread aren't apples and oranges, they are more like apples and Toyotas.

1. Poloniex uses Cloudflare for DDOS protection. You would not see the site using the same IP address over time.
2. The Mtgox problem has/had nothing to do with end user authentication. You definitely SHOULD set up 2FA anywhere and everywhere that is important to you. However, that will not prevent an attack against any exchange's back-end systems.

For whatever blockchain-based currency you are holding, if the keys reside anywhere other than offline storage, then there is a vulnerability. The severity depends on where those keys sit. If your currency is sitting in a virtual wallet on an exchange, then you either trust that exchange has a security posture that is worthy of a financial institution, or you don't. From a risk perspective, a virtual currency (VC) exchange should have higher security and more due diligence than a bank. With a bank, there is the possibility to roll back fraudulent transactions, and some amount of government protection (in the US). With VC, done is done.

Would I trust a few hundred dollars in an exchange such as Bittrex or Poloniex? Sure. A few thousand? Probably. Tens of thousands? No way. That is not an indictment of any particular exchange; it's just that there are risks that cannot be mitigated if someone else is holding the wallet keys.

Damn! Went from total ~450 Sols/s on previous version to ~650 Sols/s on 2x Asus STRIX-GTX980Ti. Stock memory settings.

Edit: ... and running two threads provides a 6% boost (~40 sols/s). I can't get my GPU memory clock to OC in the Asus GPU tweak - any suggestions? I change the value, hit accept, and it changes back to the default value.

I've come to the dark side and pointed my 2x 980ti's at lbry ... Getting about 430mh/s combined.

Yes! This.

While BTC isn't perfect, it really is a testament to the original author that it is so stable (as a protocol and technology). It's amusing that, since the DAObacle started, every "fix" just makes the situation worse.

Cool - thanks! Leaving the difficulty at auto for the moment - I've taken off the #xnsub - will see how it goes.

Well, now my S7 is just locking up. Going back to ipominer. :/

Wow. If that's not some fucking bullshit. Mine didn't fail over, as it was getting work and submitting shares.

Like, your car won't start now?

SHA256 is down?

Thanks for the additional info... It looks like 630 might not be the ticket either. I've got one board only showing 44 chips, and a half dozen HW errors.

Ohhhhkay.
Reverted to the original firmware, and everything behaved normally.
Programmed to 650/620, and the strange behaviour returned (showing less than 45 chips per chain - not showing xxx's, but just showing fewer ooo's)
Programmed to 660/630 @ 550m, and it was wonky for the first power cycle (hundreds of HW errors), but after another power cycle it's running with zero errors (one error after another 10 minutes), about 2500 GH/s drawing 560 watts.

I guess that, for whatever reason, these boards won't tolerate the 650/620.

(I would post screenshots, but I'm assuming I don't have that feature until I'm out of "Newbie" status)

Yes - I dumped the existing firmware before writing the new one. Will give that a shot tonight.

... And now it's gone totally wonky, with one board showing 33 chips and the other showing 43. Looks like I have some more work to do!

So, additional question: Intermittently, Chain 1 has shown up with all xxxxx, or with 1 chip x'd. Disconnecting the ribbon cable was a real mother*ucker - could damage to the control cable account for that? Again, it's intermittent. Power cycling will result in one of those error states, or a non-error state. It seems that if I power down and "fiddle" with the cable, it comes back up in the non-error state.

So, that's a point for the DIYers on the S7-LN - it would be better to remove the power supply and have plenty of room to work the control cable off while supporting the socket to ensure you don't damage the cable or the socket.

Sidehack -
You are a gentleman and a scholar. Applied your firmware to my S7-LN, with these results:

Before:
~2700 GH/S
Temp: 48-49
Fans: ~2800
Watts: 724


After:
~2050 GH/S
Temp: 42-44
Fans: 2280
Watts: 430

Watts measured with a belkin in-line meter.

That is brilliant. Daily power cost drops from $1.91 to $1.14 and overall profitability more than doubles.
[edit]Check your tip jar![/edit]

Strange - we have opposite problems! My lyra2v2 hash rate is spot on - on Zpool, the average over the course of the day is pretty damn close to what my rig sees. For my S7-LN, right at 20% of my hash rate is rolling over to the next pool on the list (and only 10% of that is recognized in the other pool, so I'm effectively losing 10% of my hash rate). This is without #xnsub - if I append it, my rate never goes about 800-900 Gh/s.

In looking at my hash rate graph against the pool's, and my dropouts line up fairly precisely with the pool's. How can that be expected behavior?

I had asked before about an issue with SHA256, and was told to "read the thread" ... Well, I did that, and am not sure what I was supposed to discover there. I'm still having the issue of only showing 2/3 my hash rate on Zpool, and it frequently being "dead" in the miner status. I would really prefer to mine here, but it doesn't make economic sense to do so. If this is a known issue, is it one that is being worked on, or is there something I can do on my end to make it better?

I was having this problem with a previous driver version, but haven't seen it since upgrading to the latest. Not in front of my machine right now, so I can't give you the version number. I will run 2 GPUs at auto intensity, or one at auto and one at 17, and they will run for days without issue.