Author

Topic: Post your BFL SC 60 proc/engine details here (Read 1364 times)

sr. member
Activity: 272
Merit: 250
November 11, 2013, 03:19:07 PM
#7
Any other ways to see it on Linux?
hero member
Activity: 725
Merit: 503
November 11, 2013, 02:58:04 PM
#6
With the new singles with aluminium heatsinks you can't do this it seems.
hero member
Activity: 924
Merit: 1000
November 05, 2013, 06:32:38 AM
#5

This is like a car manufacturer building a serial design flaw; BFL should pull all of it's miners and deliver working products.


Sound familiar?

Quote
With its 1957 models already rusting out, Plymouth had to confront the rust problem in a big way. The spectre of a rusting-out unibody with no frame to hold it together was simply too scary to contemplate. A series of six chemical sprays and seven dips into chemical baths plus four coats of paint prevented rust where its damage could be worst - on all those structural inner beams. The wheel wells, exposed as they were to road salt, still proved to be subject to rust, however.

Original is at Chrysler moves to Unibody (unit-body construction): 1960 http://www.allpar.com/fix/body/unit-body.html#ixzz2jlnPnO2U
Follow us: @allparcom on Twitter | allparcom on Facebook
hero member
Activity: 725
Merit: 503
November 05, 2013, 05:15:40 AM
#4
Ok, seems the BFL products don't like power cycling. At least if it's mining you will break engines just by pulling the power.

Got some kind of official confirmation from support: "Some times, the number of engines can change after initialization. Power cycling a unit usually shows this, but it doesn't vary greatly from cycle to cycle."

This is like a car manufacturer building a serial design flaw; BFL should pull all of it's miners and deliver working products.
legendary
Activity: 1178
Merit: 1014
Hodling since 2011.®
What if I use cgminer with direct usb communication and I don't have serial port dedicated to BAS? Flow control?
hero member
Activity: 725
Merit: 503
DEVICE: BitFORCE SC
FIRMWARE: 1.2.9
IAR Executed: NO
CHIP PARALLELIZATION: YES @ 16
QUEUE DEPTH:40
PROCESSOR 1: 14 engines @ 234 MHz -- MAP: EFF7
PROCESSOR 2: 14 engines @ 237 MHz -- MAP: 7FBF
PROCESSOR 3: 16 engines @ 247 MHz -- MAP: FFFF
PROCESSOR 4: 10 engines @ 229 MHz -- MAP: 4DF5
PROCESSOR 5: 16 engines @ 237 MHz -- MAP: FFFF
PROCESSOR 6: 15 engines @ 234 MHz -- MAP: FFDF
PROCESSOR 7: 14 engines @ 241 MHz -- MAP: AFFF
PROCESSOR 8: 10 engines @ 238 MHz -- MAP: 67E6
PROCESSOR 9: 15 engines @ 231 MHz -- MAP: FFFE
PROCESSOR 10: 13 engines @ 248 MHz -- MAP: EFF6
PROCESSOR 11: 15 engines @ 231 MHz -- MAP: FFFE
PROCESSOR 12: 15 engines @ 228 MHz -- MAP: FFFE
PROCESSOR 13: 15 engines @ 238 MHz -- MAP: FFFE
PROCESSOR 14: 14 engines @ 231 MHz -- MAP: FFF6
PROCESSOR 15: 5 engines @ 238 MHz -- MAP: 0332
THEORETICAL MAX: 47460 MH/s
ENGINES: 201
FREQUENCY: 291 MHz
CRITICAL TEMPERATURE: 0
TOTAL THERMAL CYCLES: 0
XLINK MODE: MASTER
XLINK PRESENT: NO
OK
hero member
Activity: 725
Merit: 503
We all receive "60" GH... lets see what we really got?

---

To dump these just stop your miner and:

Windows:

Download putty.

Then run it and switch the radio button from SSH to serial.

Enter the COM port that your miner is on and 115200 as Speed.

Press Open, then type ZCX and press enter.

Linux: (Untested)

echo ZCX > /dev/ttyUSB0 && cat /dev/ttyUSB0

Where /dev/ttyUSB0 should be changed to whatever you got I guess?

---

Copy the output (remove tabs if garbled) and post here.
Jump to: