Here are some visuals.. not the wire-frame is missing some connections but not needed to understand the daisy chaining. Ill see about getting the latest or a nice pic of one .. not gonna tear my apart right now   This is a 3 board set up, with the master taking the usb plug http://www.amazon.com/gp/product/B000IV6S9S/ .. You need 3 daisy chain cables, Unfortunately Im not sure if these are custom, I can try to find out.. Slave 1 and Slave 2 connect together, the slave 1 connects to master 1 as in the diagram. Then plugging in the usb to the master usb connector controls all 3 boards. Here is also a shot of my sierra, not in this case Slave 1 is under Master 1 and Slave 2 is to the right.  |
|
|
|
There is a USB 5-pin header also near the top right of the board.
Typically, USB motherboard (IDC) connections are red-white-green-black-black for (power, D-, D+, Gnd, Gnd) (note that the last ground is typically not connected). But in the photo you can clearly see (from the outside of the board inward) black-green-white-red-black, which is completely wrong for USB. Testing the pins and then using my own USB IDC to Type A cable, I found the header on the board is correct. If you connect a standard IDC cable to the board with red starting on the outside of the board, it works perfectly. Don't know why they would use a USB cable with messed up color coding.
Hey Kikaha - I am prepping for MPP units (yeah pre-mature... but gives something to do while waiting). We haven't heard/seen much documentation on the actual hashing modules. Is that IDC USB header on the board used for daisy chaining (or for direct communication with the miner controller/host computer)? Trying to figure out if I should order some of these: http://www.amazon.com/Adapter-designed-motherboard-external-connector/dp/B000V6WD8A/ref=sr_1_1?ie=UTF8&qid=1390922831&sr=8-1&keywords=idc+usb+cableIf your wanting to mimic how a sierra is built you need 1 usb cable to the main board, the rest are daisy chained together. So with the sierra's their are 3 boards.. the top one has the usb as the main board that controls the others that are daisy chained at the bottom, and connected to the main board at the top. One thing to note is power, right now with the 2 power supplies, each board gets one pci-e connector for each power supply.. so the board has a pci in the front and back and one comes from psu left and one from psu right. |
|
|
|
[minepeon@minepeon ~]$ tar -xvf cgminer-3.11.0.tar.bz2
bzip2: (stdin) is not a bzip2 file.
tar: Child returned status 2
tar: Error is not recoverable: exiting now You can try bzip2 first.. bzip2 -d cgminer-3.11.0.tar.bz2 or try tar -xzvf cgminer-3.11.0.tar.bz2 |
|
|
|
You can run it off any PC, and that's preferable anyway since the RPi is a piece of shit. Just plug in a USB cable. The sierras don't even have one so you have to run them via USB. Any instability still around is firmware related and remember it's still early days since release (even though release was late) but once my sierra is running it does not miss a beat.
Mine is happily hashing from an old mini PC desktop. Will try to resolve a driver conflict with Karin's help and get it hashing on the Mac mini later today. Interestingly, after running overnight, this BJ seems a little off-spec. It's doing about 395-7 g/hash (running cgminer 3.11). OTOH, my HW error rate is very low and with an ambient temp of 21c (70f) my processor temp is 69-70c. What did other people get for out of the box processor temps? I guess I should experiment with overclocking next... I've seen 610 mentioned... other suggestions? And sorry ckolivas, I didn't mean to suggest the Mac driver issue was your problem. It was intended merely as an observation. And finally... why don't we try to move all this operational discussion over the the user's thread? I would still like a thread more focused on the company and its operations (and interesting cast of characters), like this one was before HF really started shipping. In fact, I'm going to xpost over there. 610 is good but you might void your warranty by doing this FYI and with any ocing you risk damaging the hw. So do this at your own risk.. Sorry needed to add this disclaimer. |
|
|
|
Anyone is using rapsberry pi to connect to sierra? Does RPi+minepeon support sierra?
I'm using an old notebook with ubuntu desktop right now, I'm sure a pi would work, I can see about getting one. |
|
|
|
I highly recommend using the latest cgminer 3.11x with these devices, quite a bit of work to the hf driver was done. Also you do not need to supply the --hfa-hash-clock if you are just going to run at 550 since thats default, a good number to try is 610, of course will use more power but should get you more hashing and not many if all hw errors..
Thanks. I turned on automatic HF updates again and after a reboot I see I now have a new version: cgminer3.9.0 h2 It is still not 3.11.x but I'll leave the 'h2' version running for a bit to see if that improves stability. I did notice it caused my hashrate to drop slightly from 422 to 417. I assume HF will push 3.11 automatically once it is ready for primetime. Will post future updates in the HF user thread as not to spam this one. Yep cheers.. I also started a thread for Sierra owners here.. https://bitcointalk.org/index.php?topic=433350 |
|
|
|
My BJ hashes @ 422 GH/s consuming 407W at the wall using stock settings:  #!/bin/bash
sleep 10
/usr/bin/screen -dmS miner /opt/minepeon/bin/cgminer -c /opt/minepeon/etc/miner.conf --hfa-hash-clock 550 I highly recommend using the latest cgminer 3.11x with these devices, quite a bit of work to the hf driver was done. Also you do not need to supply the --hfa-hash-clock if you are just going to run at 550 since thats default, a good number to try is 610, of course will use more power but should get you more hashing and not many if all hw errors.. |
|
|
|
General Info:- These puppies are heavy and love to eat power so make sure you now how many amps your plugs can take and what fuses they might be on.
- 3 Boards come in each Sierra and are daisy chained together.
- 2 Power supplies with paper clip trick to enable you to turn them on *see powering up the device
Power:- For example I think a typical us household plug might take 20 amps per fuse which could be spread over a few sockets or one.
- These devices seem to take about 1W per Gh, so if you over clock it to lets say 1.4 Th/s your running around 1400 watts and maybe around 11amps.
- Plugging in two into one socket might might be to much and you might get the feeling that the devices are not working but it might just be you do not have enough power, so check this first if your having issues.
Getting Started:I would personally suggest using a flavor of unix, for my miners I usually use ubuntu desktop 12.04x 64 bit, and enable vnc so I can remote desktop into my boxes. I then compile cgminer or bfgminer depending on your preference with the proper switches for the hashfast devices. [maybe someone using these on windows can explain the process of getting it setup] Once you have the miner software compiled its time to fire up your first box. Do these in order for now until some bugs are resolved. If you have one sierra make sure you have enough power, see power section above. Turning On Single:- With your pc booted into linux and terminal window open, turn on both power supplies on the Sierra.
- Plug in the USB cable into the back of the Sierra if you haven't done already.
- Plug in the USB cable into your pc
- Start Miner software ... wait a few seconds while it recognizes the device.
You should be up and mining if no issues like power or other are plaguing you. Multiple Sierras one pc:- Do the same as above with the first Sierra to get it mining, make sure you do not have all Sierras plugged in to the box just one.
- Once one is hashing, plug in the next, and wait for it to recognize and start hashing, rinse and repeat on other boxes.
- note** if your having issues make sure you have enough power **
Once hashing, leave them alone or you can try the oc settings which I can talk about in another post and be aware if you use these your going to use more power from the outlet so the other sierras that are plugged in might stop working since you do not have enough power. This should get you hashing, ill try to keep this updated and post other things about the Sierra's as I get time. cgminer stuff:If your using cgminer you have 2 additional options right now with 3.11x --hfa-hash-clock <arg> Set hashfast clock speed (default: 550) --hfa-temp-overheat <arg> Set the hashfast overheat throttling temperature (default: 85) Ill talk about overclocking later and please make sure to read the warranty of your device before doing so and understand you could void it or cause issues with your mining hardware. Getting cgminer to work on windows with your HF device.. - Start cgminer (no extra options)
- Plug in device, wait for windows to finish installing the driver it thinks is right, then run zadig as administrator and tell it to use the WinUSB driver for the "M1" device which is what the hashfast comes up as.
- cgminer should just hotplug it at that point.
|
|
|
|
|
I figured since some people will start to get their Sierras that we could have a separate thread for sharing information about these devices such as how to get started, software updates, firmware updates, general info, tips and over clocking.
|
|
|
|
What are the instructions for running cgminer on windows with BJ attached via USB? Or at least a commandline? Is it plug and play?
I think it goes something like this. Download a flavor of linux on your windows box, use that box to burn the cd or hell put it on usb, restart your windows box with either one an install linux, then compile cgminer with hashfast driver enabled sorry couldnt help my self Honestly I dont know but I would assume you could try the latest 3.11.x first before using zadig. Rule of thumb with any HF device that is not starting. 1. unplug the usb cable connected to the pc 2. power cycle the jet/sierra 3. plug in the usb cable (windows users might need to use zadig??) 4. fire up cgminer with default settings, it should hopefully see your device, some times it takes a few seconds |
|
|
|
While I knew that you could donate manually to the pool, I didn't know you could set it up to take a fee. Someone above had posted that info. Can't recall who it was, but you know who you are, so thanks! I set it to 1 percent, 33/33/34 respectively. Whizkid, if you do the accounting as I believe you do, and think it would work better set differently, please tell me so and I'll change it accordingly. I would encourage everyone to do the same. It's on the configurable options link under the "my eligius" tab. This is a great pool, and deserves to be supported. 1 or two percent is cheaper than most other pools, and if enough of us do it, wk can quit his day job +1 |
|
|
|
The formula you posted is correct for the most basic estimate of the next difficulty. Its disadvantage is that the estimate can fluctuate considerably just after a difficulty change and it will only become more accurate as the next difficulty change approaches. Another approach is to always look at the time spent on the last N blocks, where a larger N gives a more stable prediction, but less accurate in times of quickly changing hashrate.
An even more advanced technique would be to assume that the network hashrate is, at least locally, increasing exponentially. You can then take several datapoints with the time spent on solving the last N blocks, the time spent on solving the last 2N to N blocks, 3N to 2N, etc... and fit an exponential curve to this data.
ahh ok .. great thanks for the info.. I need think If I want to go that route.. cheers! |
|
|
|
Ya I know their are a few sites that do this, I was more looking for the formula they use to calculate estimated diff change |
|
|
|
|
Curious what the refund policy is.. the btc you paid originally or a conversion of what the US to btc exchange rate currently is.
|
|
|
|
Anyone, im kinda stuck at the moment |
|
|
|
haha crap, typing to fast causes booboo's. title changed.. thanks guys. I stepped away for a meeting and came back to this |
|
|
|
check it out, did a screen shot of of the checkout page bitcoin page..  One company down more to come I hope |
|
|
|
Hey everyone, I think this been covered before but I couldnt find a solid answer to the question. I'm querying my bitcoind to get various details out it then I wanted to calculated the estimated change or best possible way to do it. Here is the current data that I'm collecting, I hope I also got the right first block of the current diff and last block right.. Estimated formula 1418481395.2626*(600/((1389220457 - 1388624318)/1170))
Estimated New Hash Rate = 1,670,372,077
Estimated Change = 1.1775777125805
Current Block = 279378
Current Difficulty = 1,418,481,395
Current Block Hash = 0000000000000000eea976a669c940e408e269d4984370ad1c3059db09dad86a
Current Block Hash Time = 1389220457 or January 8, 2014, 2:34 pm
First Block at current Difficulty = 278208
Last Block at current Difficulty = 280223
Next Difficulty at Block at = 280224
Number of Blocks till next Difficulty 846
Number of Blocks posted since Difficulty started 1170
Next Difficulity in 5 days 21 hours so what im using to estimate the next diff is the following.. current difficulty*(600/((time of latest block - time of first block of this difficulty)/number of blocks since first block of this difficulty)) Does that look right, or can anyone shed some light on what I might be doing wrong or missing. Cheers! |
|
|
|
|
Show Posts
