Ahh, could be.  I was thinking the leading 0 issue was with the RPC command, I do not recall if I used a leading 0 on the --set as well.  I will confirm tomorrow.

As an aside, the RPC way of adjusting frequency is pretty darn cool since you can do it while they are running.  Couple that with the adjustable voltage, also while running, and you've got real time feedback from a very customizable piece of hardware!

I was unable to get --set cbm:clock=xNNNN to work.  I believe you said you used it on the pre-production stick that was sent to you, but I cannot duplicate your success on the production stick.

I am assuming you are offering a private party transfer through a licensed gun dealer, right?  At least here in Kalifornia you cannot sell any firearm without using a dealer unless it's an antique.

I carry a S&W M&P 40c when I'm out in the desert. 

I can imagine someone using two sets of Y cables to bridge 4 usb connections into 2, and then one more Y cable to bridge the 2 bridges down to 1, so you effectively have 4 usb ports into 1.  Commence fire and melted electronics. 

I won't be participating in the OC contest, but I will definitely be following along!

Yes, it's a known issue and I have brought it to luke-jr attention in the bfgminer thread.  The command line frequency adjustment will be fixed in 5.4.0 as he noted and as a result of that discussion, but in 5.3.0 the compacs will only run at "stock" 225 setting.  A work around it to use RPC's pgaset and set the frequency that way.

1) Start bfgminer and your sticks via command line like normal, but omit the frequency setting command.
2) Once running, open another command line and navigate to your bfgminer directory.
3) Input the following:
4) In the above command, the "0" refers to the position of the miner in the list in bfg.  If it is at the top of the list it is 0, second down is 1, third down is 2, etc.
5) Replace hex code at the end with hex code from first post in this thread for the freq you want, omitting the leading 0.
6) Hash away.

Feel free to copy/paste any of this into the first post of this thread until 5.4.0 is released.

See the following for the orig. discussions:
https://bitcointalk.org/index.php?topic=877081.msg12705080#msg12705080
https://bitcointalk.org/index.php?topic=877081.msg12732711#msg12732711
https://bitcointalk.org/index.php?topic=877081.msg12741394#msg12741394
https://bitcointalk.org/index.php?topic=877081.msg12747938#msg12747938

Memory has been brought to my attention before as a likely culprit.  My machine is old, here are it's specs:

Intel Core2 6600 @ 2.40 GHz
Nvidia GeForce GTX 550 Ti
4 GB ram, but WinXP only sees 2.75 GB
1 TB+ 7200 rpm of HD space on 3 physical drives

I will run memtest just for fun, but it's probably just the age and architecture of my machine that crashes core.


When bitnodes emails me that my node is down I can VPN to my machine and restart core.

The halving refers to the reward for solving a block.  Satoshi outlined in his white paper how the supply of bitcoin would be controlled, that the reward for solving a block would be cut in half every 210,000 blocks, roughly every 4 years.  The reward started at 50btc and is currently 25btc, it will go down to 12.5btc at some point in 2016.

Lots to read from a basic google search, https://www.google.com/search?q=bitcoin+halving

Contact my personal friend Fred Bart, http://www.executivecurrency.com/owners/, he is one of the country's top paper currency experts.  Tell him "Mike" sent you, but be sure to let him know that I don't know you in person, just that I saw this on a forum.

He could assist with the sale as well, should it turn out to be legitimate.

The buffer overflow bug was something I had been experiencing for a while, it would cause my client to crash, glad to see that has been fixed.

Core is still randomly crashing for me from time to time, but I think that is because I run it on a very old system.  I have not been able to pinpoint the cause of most of my crashes, and the log file doesn't give any clues.

That's because these new miners are not meant for home miners, they're being made probably mostly for internal use, with a few shipments going out to some big data center folk.  The SP50 was never intended for individual use or sales, probably one of the reasons they're so hush hush about pricing and such, because ultimately it doesn't matter unless you are in their inner circle.  It's like Ferrari where many of their models are only available for purchase by Ferrari owners that the company personally invites to buy one of their cars.

The only electronic stuff I've ever worked on is automobile related.  These electronics are so compact that I feel like you almost have to have a surgeon's hands even just to get your probe on those pads!

Photo for reference for folks who may be coming to this thread without reading any of the others.

And one more thing I have figured out, may be obvious to you all who know this command line stuff a lot better than I do, but the number in the pgaset command (|#,clock,freq) is the number of the miner in the list shown on bfgminer if you start at the top of the list with 0, i.e. if you have 8 miners running in bfg and your compac stick is the 6th one down from the top you would use 5 in the pgaset command.

Dang, a month or so ago that would have been a block solve!  And it looks like you are solo mining against your own node to boot, so that would have been a sweet solve, plus good advertising for the S7. 

I would say that as long as no one is cornering the market on your pods via trade-ins that you should let the market work itself out.  My only concern would be someone sending in a crap-ton of boards and hoarding all the pods you make, only to try and turn around and resell them to make a buck.  The only people that should profit from this venture are gekko science, I would hate to see someone try and take advantage of this opportunity.

Look in the support thread, there are a few recommendations there, including one that is running like 19 sticks I think.

In the last few days Bitmain has been selling S7s like there's no stopping them.  All this hash is coming to a difficulty adjustment near you soon!  My guess is the huge spike is a couple very large orders to a few people.  Those are the ones that are going to made a bump in the difficulty.  I think what we're seeing now is just the "little guys" getting their S7s running.

There's a small turn-screwy thing on the bottom right of the stick.  You turn it clock-wise to up the voltage, and vice versa.  You only need to turn it up if you are seeing HW errors, and then just a wee-little turn at a time (like 1/8 a full rotation) until the HW errors go away.  Very easy, and kind of better than software control since you can do it while the stick is hashing and get real-time feedback via the HW errors.  There are spots on the stick you can touch with a meter to measure the voltage if you are so inclined.

It would be cool if someone solved a block with one.  The chances of solving a block at today's difficulty with only 5GH is essentially 0, however, so don't hold your breath!  And the difficulty is only going up from here...

Still, looks like another fun toy to tinker with.  I'll probably buy one.

A solo block was just solved on ck's solo pool by a user with about 5TH, which is about what this clubs sees with the donation hash pointed at it.  So a block is definitely possible!  A long shot, sure, but still a real possibility.

Congrats to the 5Th solo solver!  That give me some hope that our little gekko compac stick club may hit one eventually, too!