When you factory reset make sure you watch the LED, I just tap the pins (as in repeatedly) until It cycles from blinking slow, then fast, then turns off. Once it's gone through that then it's really reset, otherwise I think it ignores it.

D5jig3QPneFDqg88Foybgo61h7LfW8P4Q2

so inu wow, much crypto

So many doges!

such wow

D5jig3QPneFDqg88Foybgo61h7LfW8P4Q2

Many Inu

Sure I'd like to give this a try.

D5jig3QPneFDqg88Foybgo61h7LfW8P4Q2

So crypto

wow

I see, well that's quite unfortunate that board failed in the only way that currently can't be repaired. If the owner decides to part ways with it feel free to keep me posted or PM, I've a very high ebay feedback and am verified on paypal.

I've a good idea that the only way we'll get a firmware is if we ship them a 18F Pic on a demo board that has a programming header, get it back, desolder it and populate the board ourselves.

I somewhat doubt they have a hot socket for programming as it's all setup for ICSP, and they likely see sending the firmware as a loss of potential revenue... even though they don't sell these asics anywhere and they're being phased out.

And yes, the software BE speed thing seems to be a fallacy, still have to change the oscillator to get real improvement.

Also I'm curious why when you overclock blades you opt for ~14MHz instead of 16MHz, too much heat to deal with or the PSU circuitry overheats? (or maybe the 10A limit on the stock fuse)

I only ask because if it's heat you should explore the idea of thermal tape and thin heatsinks, I've done this to mine despite not being overclocked ATM and my temperatures are around in the <50C range.

Oh hey I recognize that handle, you overclock blades and stuff. I guess I shouldn't be surprised you found this.

I powered my cluster down then proceeded to freaked myself out when the blade simply reset on each read try and failed, I didn't realize there was a "18F_J_" option at first.

Unfortunately this looks like a no-go as all of my blades including the 'unique' one are indeed code protected. Bummer..

If you ever get your hands on the firmware I too would like a copy! I quite want to try and modify the code but don't plan on doing so unless I can recover the blade in case implementing a network stack proves to be too much...but...

Any chance you'd be willing to sell the pic-less blade towards development? Microcontroller code is a hobby of mine and I have a sneaking suspicion there are gains to be had here just like the Block Erupter USB's can be made to run 666MHs with a config flag option. https://bitcointalk.org/index.php?topic=357684 now imagine a BE blade possibly running 21.8GH on it's stock 12MHz crystal.

EDIT: Hmmm, I might have jumped the gun in the 'speed boost', and not read through far enough it appears it's just faking CGMINER out and the pool hash rate is only slightly rising, but so is error rate. Well, that idea is likely a bust, but I'd still be interested in trying to write my own firmware.

I've had these blades for a bit but recently realized that even on the Blue Rev2 boards that have both oscillators populated this option isn't even present in their web interface!

Only one blade in my cluster has this, so it seems rather unique..

Check it out on the far right buttons near the bottom: https://i.imgur.com/XjSMlW8.png And no I don't care if you see my Slush's account info, mine some for me if you'd like.

And again these are all Rev2 boards, running flawlessly so far.

Did they flash a Rev1 firmware? Is this an unlockable option they did by mistake?

I know if I click it the blade will just stall if it even works since it's a green rev and has no 2nd oscillator populated, also the voltages will need changing via replacement resistors. I have a pickit2 and will check and see if the F/W is read protected if there is enough interest in something like this. It shouldn't be like this, so who knows, maybe they forgot the protection also.

On the 20955 round you provided significantly less shares than the other rounds, It it likely this happened all towards the end of the round because later shares are weighted more, this prevents pool-hopping. You actually missed out on the beginning of the 20956 round as well. Your ratios as far as (submitted shares/all shares) are as follows:
Round#:   Ratio:
20957   96.8e-6
20956   77.5e-6
20955   29.4e-6
20954   98.9e-6

But basically you missed so many submissions towards the end you were rounded down to zero by the pool hopping mechanic. The only way to earn shares in Slushes is to be there when the round completes by a fair margin.

Because BTC is gaining traction and attracting new members. But I suppose I too would question if I saw something similar. A lot of us newbies had to learn the hard way that online wallets like BIPs are vulnerable. I was nearly one of them, bailed out a week before.

If anything though you should be happy to see a surge in growth, it's what makes the value rise. Supply/Demand.

My payout isn't happening since last maintenance, has been set to 0.015 and I'm at 0.035 (confirmed) now... please investigate. Moving to Eligius till this is sorted.

Edit: Payout recieved. Also though the JSON tables are borked, it says I have 0 active miners even though I clearly see that's not the case, so 3rd party apps can't report hashrates.

As far as I'm aware coinbase can do many of these same things and has a full payment API built in, also a better track-record thus far as well.

Not to be a downer but those blade prices are still pretty high, especially for the broken ones. I paid about 60% of that for new working blades. Else I was going to consider the defectives.

Can you please link to the ebay auctions here or send a PM?

As it should I suppose, I did read the warning but I suppose it's easy to brush those off as an "Oh pfft that will probably never happen, it's just a disclaimer" But in bitcoin it's just not. It should be plainly stated that because of the price demand BTC has worked up to and it's inherent decentralization and control that these attacks/scams/robberies happen at an alarming frequency to those who don't know how to protect their coin. I had a discussion over on reddit about the wallet system and I'll copy it in here, it's basically a recap of what happened when I tried to install bitcoin-QT before going to a web wallet and some improvements I think we can make to help introduce newer users as I was shortly ago:

It's simple, they don't justify it. Anyone who ordered a 7GH unit got ripped off.

The only ones that mine at 5GH are ones with possibly contaminated/defective chips or are software locked as far as I'm aware.

I don't really understand what's going on with ebay myself, I know the Price/BTC has gone up and so has the difficulty. But I just listed 4 USB Block Erupters that I bought at $9 a piece plus a cheap compatible USB hub and the bidding went up to $+150, like seriously wtf? I know prices were sorta high and I even gave it a buy it now price of ~120 because that's where demand was at the time.. guess not!

I'm seriously regretting not investing in these sticks when they were cheap before teh crazyness went full swing, but in this market everyone has those regrets.

I'm going to include a free USB fan I hacked together that keeps them nice and cool just to help ease my mind and their setup.. They earned it.

I just have a strong feeling they will be hashing with the hardware and only turning over it's power to the leasers when their money makes more than the hashing power is worth. just my 2 cents as they've shown they like to do 'burn in testing' for quite an extensive time.

Make sure your PC is on the same subnet as the cubes 192.168.1.x

You need to set each cube to have a separate IP address otherwise they will all conflict 192.168.1.250 - 192.168.1.251 - 192.... etc, do not use 192.168.1.255 though!(it's a special "broadcast address" used in networking so stay away from it.)

I'm going to assume these run nearly identical firmware to the ASICminer Blade Erupters I have and will need to use a Stratum Proxy on a PC. Here are the settings I'm using.

Current Server: 192.168.1.19:8332
Chip: OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO

IP         192.168.1.20
Mask         255.255.255.0
Gateway      192.168.1.1
WEB Port      8000
Primary DNS   192.168.1.1
Secondary DNS   8.8.8.8
Ports         8332,8332
Server addresses   192.168.1.19,192.168.1.19
user:pass      username:password,username:password

In my setup you can see my PC has a static IP set to 192.168.1.19

For the stratum proxy I'm using Slush's: http://mining.bitcoin.cz/mining-proxy-howto
By default you need to fill in the "username:password" fields in the ASICminer config page and they need to correspond to an existing account, otherwise no work will be handed over.

Alternatively if you want to use a server like say Eligius you can ignore the user:pass fields and create a *.txt file in the same folder as mining_proxy.exe.

paste this into that file:
mining_proxy -o stratum.mining.eligius.st -p 3334 -cu WALLET_ADDRESS_HERE -cp x

fill in the wallet address part accordingly

save the file, then rename it to a *.bat file, make sure you have the "show file extensions" option turned on in windows so you aren't naming it *.bat.txt by mistake. If it's opening in notepad when you try to run it you're doing it incorrectly.

Hope this helps, I had a hell of a time getting my BE Blades going the first time.

Also something you are saying is inconsistant. You say you're changing the IP of the miners, yet you can't access the config page, where are you changing the IP then? Also the miners will not show up for your router(inside it's management pages) because they don't use DHCP to grab a new IP address.

I might be able to try helping you through team viewer.

The timing of this is scary, because this nearly caught me as well.

A week  prior a coworker and I were having a conversation and started talking about web-wallets. After reading up online I came to the conclusion I wanted nothing to do with BIPS and scooted my measly 0.03BTC or so away from them. A week later and this happens.

I initially chose BIPS because it was recommended on the "choose your wallet" page and the site seemed reasonable well put together. I feel like it doesn't deserve a spot there anymore..

You might want to try and scan your system for any infections, a virus could in theory hijack your login session and when you try to send yourself the money it malforms the request and sends its owner BTC instead, that is indeed quite devious if it's the case.