Topic: GekkoScience Compac BM1384 Stickminer Official Support Thread - page 82. (Read 268015 times)

Thanks guys!  

I'll ramp it down a few notches which will hopefully make it use less power, if that is what is causing the upset.

Last time I was testing I was using bfgminer 5.3.0 which might explain a few things as to why it wasn't running at the speed I tried to set...doh!  

Jumprope?

BFG 5.3 requires hex; BFG 5.4 works with MHz. cgminer-gekko uses the product ID info in the CP2102 on the stick to identify the Compac, and we forgot to make sure it recognized bitshopper's custom ID. This has nothing to do with drivers. Novak's been busy with a couple other projects and hasn't gotten back to the cgminer code so it's still a known issue. 125MHz should run you just shy of 7GH.

You have to use hex value with bfgminer (I'd recommend cgminer as well, works good for me ):

My VCore is showing as 0.69V

I am starting BFGminer with this switch: --set compac:clock=125

I'm not entirely sure if BFGminer is looking at that or not as 10ish GHs is not what I'd expect for 125MHz unless I am mistaken?

Note that for bfgminer you have to use the hex value for a given clock rate, whereas for cgminer you specify the clock rate in MHz.
A table of values to use in BFGminer is as follows:
        { 100,          0x0783 },
        { 106.25,       0x0803 },
        { 112.5,        0x0883 },
        { 118.75,       0x0903 },
        { 125,          0x0983 },
        { 131.25,       0x0a03 },
        { 137.5,        0x0a83 },
        { 143.75,       0x1687 },
        { 150,          0x0b83 },
        { 156.25,       0x0c03 },
        { 162.5,        0x0c83 },
        { 168.75,       0x1a87 },
        { 175,          0x0d83 },
        { 181.25,       0x0e83 },
        { 193.75,       0x0f03 },
        { 196.88,       0x1f07 },
        { 200,          0x0782 },
        { 206.25,       0x1006 },
        { 212.5,        0x1086 },
        { 218.75,       0x1106 },
        { 225,          0x0882 },
        { 231.25,       0x1206 },
        { 237.5,        0x1286 },
        { 243.75,       0x1306 },
        { 250,          0x0982 },
        { 256.25,       0x1406 },
        { 262.5,        0x0a02 },
        { 268.75,       0x1506 },
        { 275,          0x0a82 },
        { 281.25,       0x1606 },
        { 287.5,        0x0b02 },
        { 293.75,       0x1706 },
        { 300,          0x0b82 },
        { 306.25,       0x1806 },
        { 312.5,        0x0c02 },
        { 318.75,       0x1906 },
        { 325,          0x0c82 },
        { 331.25,       0x1a06 },
        { 337.5,        0x0d02 },
        { 343.75,       0x1b06 },
        { 350,          0x0d82 },
        { 356.25,       0x1c06 },
        { 362.5,        0x0e02 },
        { 368.75,       0x1d06 },
        { 375,          0x0e82 },
        { 381.25,       0x1e06 },
        { 387.5,        0x0f02 },
        { 393.75,       0x1f06 },
        { 400,          0x0f82 },
        { 412.5,        0x1006 },
        { 425,          0x0801 },
        { 437.5,        0x1105 },
        { 450,          0x0881 },
        { 462.5,        0x1205 },
        { 475,          0x0901 },
        { 487.5,        0x1305 },
        { 500,          0x0981 },

My VCore is showing as 0.69V

I am starting BFGminer with this switch: --set compac:clock=125

I'm not entirely sure if BFGminer is looking at that or not as 10ish GHs is not what I'd expect for 125MHz unless I am mistaken?

Hi Everyone,

I got my EU version of the compac through rom bitshopper.de to play with and I have an interesting issue with my stick that I'd appreciate some input on.

I can get the stick hashing ok from BFGMiner since it doesn't get detected by the novak version of cgminer but I have read that this is a known thing so that doesn't really bother me.

Then things get interesting as it will sit happily at around 10-11 GHs and then after what feels like a few minutes the hash rate starts dropping down slowly to zero so I started to investigate.

I got my mains plug power meter and stuck that between the wall socket and the power supply for my admittedly crappy (!) USB hub and when its hashing its drawing about 7.1W from the wall but then it drops out to hardly anything when the has rate starts dropping and putting a DMM on the stick reveals that I have no vCore voltage when this happens but the rest of the voltage rails check out ok!?

Has the stick upset my crappy hub and activated some sort of protection? Taking the USB and power off the hub and plugging it back in restores the vCore on the stick and it will hash again which is making me think its the hub doing something.

The hub is powered by a 5V 2A wall wart style power supply.

I find it interesting that the power is still going to the stick since the green LED stays on and I thought if a USB port "trips" due to power consumption it cuts the power? or perhaps it limits the power?

Do you think a USB Y-Cable would sort the above if its a, per port on the hub, power related issue? Maybe I need a new hub?

best way to start is to check at what V the core chip is running.

So get your favorite multimeter and verify using ground + vcore pads at the back.

then force it to run at 150Mhs for a start.

and then take it from there depending on your usb hub W per port.

Check this for speed / W correspondence:

https://docs.google.com/spreadsheets/d/16epfBXVscFFZV1G3_Gn8SHDzB46bq93CUnH8cHoyoxQ/edit#gid=0

anyone running minepeon on a pi with this compac plugged in?

i cant get it to hash over 3ghs
it is in a powered usb hub 2.0 5v4a

if anyone has a step by step so i can see if i  missed anything.

or if you have a better idea on how to go about setting up the pi to work... im open to any ideas

anyone running minepeon on a pi with this compac plugged in?

i cant get it to hash over 3ghs
it is in a powered usb hub 2.0 5v4a

if anyone has a step by step so i can see if i  missed anything.

or if you have a better idea on how to go about setting up the pi to work... im open to any ideas

Could the hub be running out of power, like it can't supply enough to the last stick so the stick generate HW errors? You would expect this if the voltage wasn't turn up enough on the stick, but since it's a different stick dependent on how many other sticks are ahead of it then it might be the hub.

because it does not matter which stick I try (it is a different one each time), but tend to be one of the latter slots (CBMs).