Pages:
Author

Topic: [Guide] Dogie's Comprehensive ASICMiner Cube Setup [HD] - page 18. (Read 187411 times)

legendary
Activity: 1851
Merit: 1020
Get Rekt
no matter what I do I cant get to the config page
I tried 192.168.1.254:8000 192.168.1.254 and I reset the cube to factory settings, none of those helped. Not sure how I can config without connecting.
member
Activity: 87
Merit: 10
Thanks guys.  I feel stupid for putting in the blade while it was running  Tongue 
I'll look into the proxy problem.  Smiley
Thanks!
legendary
Activity: 1666
Merit: 1185
dogiecoin.com
...I accidentaly put a blade in while the machine was running and the blade shut it off and now if I ever start the machine with that blade in, the red light doesn't go on and nothing happens. What does the red light stand for?  I wonder if I should change the capacitors or it's something else?
Best guess is that you ruined that blade. Plugging it in while the cube was on will connect some of the connector contacts before others and apply voltages in an order that can ruin the board. Also best bet is that the capacitors are not the problem, more than likely it is some transistor based item like a chip. I would suggest _not_ ever plugging in the bad blade again--there is little to gain and it might cause more damage.

Just write the loss of the blade off to a learning experience.
Yep dont try that blade again. You can get things like shorted tracks which will make it electrically unstable for the motherboard.
member
Activity: 104
Merit: 10
...I accidentaly put a blade in while the machine was running and the blade shut it off and now if I ever start the machine with that blade in, the red light doesn't go on and nothing happens. What does the red light stand for?  I wonder if I should change the capacitors or it's something else?
Best guess is that you ruined that blade. Plugging it in while the cube was on will connect some of the connector contacts before others and apply voltages in an order that can ruin the board. Also best bet is that the capacitors are not the problem, more than likely it is some transistor based item like a chip. I would suggest _not_ ever plugging in the bad blade again--there is little to gain and it might cause more damage.

Just write the loss of the blade off to a learning experience.
legendary
Activity: 1008
Merit: 1001
Let the chips fall where they may.
I went through the mini blades to see how good each were...but I accidentaly put a blade in while the machine was running and the blade shut it off and now if I ever start the machine with that blade in, the red light doesn't go on and nothing happens. What does the red light stand for?  I wonder if I should change the capacitors or it's something else?  Huh
Thanks in advance!!!!!!!! Smiley
Also...does anyone else only get like 15 gh/s?  I can't seem to get anything near 30....

I don't know what the mini-blades look like, but check for short-circuits like bent pins or even the card installed backward (assuming a protection diode preventing reverse polarity).

The cube is supposed to shut-down if the fan fails could it be getting too hot?

If your controlling computer is really underpowered (talking 10 years old or more), that may cause reduced hashrates (but if that is the case, you CPU should be at 100% while hashing).
member
Activity: 87
Merit: 10
I went through the mini blades to see how good each were...but I accidentaly put a blade in while the machine was running and the blade shut it off and now if I ever start the machine with that blade in, the red light doesn't go on and nothing happens. What does the red light stand for?  I wonder if I should change the capacitors or it's something else?  Huh
Thanks in advance!!!!!!!! Smiley
Also...does anyone else only get like 15 gh/s?  I can't seem to get anything near 30....
legendary
Activity: 1666
Merit: 1185
dogiecoin.com
Right now I have 6 cubes but they only run between 20 GH/s and 25 GH/s.  They function just fine other than that. I’m currently running a mining proxy for Slush’s Pool but have the same problem.  The odd thing is I recently moved and at my last house I was getting the correct hash rates but have had nothing but problems at my new place.  I’m running each pair of cubes off of a Corsair TX850M PSU.

Have you tried running two proxies and putting 3 cubes on each?
newbie
Activity: 4
Merit: 0
Right now I have 6 cubes but they only run between 20 GH/s and 25 GH/s.  They function just fine other than that. I’m currently running a mining proxy for Slush’s Pool but have the same problem.  The odd thing is I recently moved and at my last house I was getting the correct hash rates but have had nothing but problems at my new place.  I’m running each pair of cubes off of a Corsair TX850M PSU.
member
Activity: 87
Merit: 10

Use a local stratum proxy
[/quote]

I'm trying to use that and it doesn't help my speed....  Huh  It starts out fast and then slows back down to like 15 gh/s.
Thanks in advance!
newbie
Activity: 36
Merit: 0
Statistically, you could find a block in the first 30 seconds, then again it might not happen till after the end of the universe. And it will get to the point where a single cube is not capable of generating enough in a pool to pay for the power used to run it. Doubling down doubles the return for double the cost. So, there is a perverse logic in going for broke.

So, question, how long will it take a single cube to generate 25 bitcoins? (the only valid answer is twice as long as half of it)
sr. member
Activity: 336
Merit: 250
Does anyone knows how to use Cube solo mining with mining_proxy?

You are a gambler!  Do you play the lottery too?  ;-)  One OC'd cube solo mining will take about 15 years to solo mine a block on average.  Good Luck!  ;-)

But if you are interested, you can set up a bitcoin as a server on a local computer, and point your Cube proxy to it ( or, bypass the proxy and connect with getwork, depends on how you set up server).  
There are lots of guides and tutorials on how to set up a solo miners, such as these --->>  Solo Mining setup


Cliff Notes version :
Code:
Bitcoin-qt.exe -rpcuser=userid -rpcpassword=password -server

Point your Cube to your computers address running bitcoin daemon.  Example:(192.168.1.11:8332) with the userid and password you selected in the bitcoin-qt command line.

BTW, I have a bunch of Ant Miner USB's solo mining for giggles.  I am a gambler too.  ;-)
member
Activity: 92
Merit: 10
Does anyone knows how to use Cube solo mining with mining_proxy?
legendary
Activity: 3766
Merit: 1742
Join the world-leading crypto sportsbook NOW!
I have looked inside and I am now running the cube without the outside box.  I tightened the heatsinks and everything, but the bottom chips still show 000.  If I move the blades it doesn't fix the problem.  My v2 blade has the same settings but has run without issues.  I have this wonky thing where the firmware shows less than its actually mining on bitminter on both machines.  How would I fix the comms pin?

Thanks in advance!  Will send BTC if anyone can get it fixed.

ASIC_01-16: O O O O O O O O O O O O O O O O
ASIC_17-32: O O O O O O O O O O O O O O O O
ASIC_33-48: O O O O O O O O O O O O O O O O
ASIC_49-64: O O O O O O O O O O O O O O O O
ASIC_65-80: O O O O O O O O O O O O O O O x
ASIC_81-96: O O O O O O O O O O O O O O O O
M_01-16: 041 041 013 110 041 027 041 013 096 013 027 069 041 027 069 013
M_17-32: 041 013 000 069 055 000 013 041 013 000 069 013 041 027 027 027
M_33-48: 000 041 000 013 013 000 055 013 055 027 013 000 027 013 000 041
M_49-64: 000 000 013 000 000 013 000 055 013 013 041 013 027 000 000 000
M_65-80: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
M_81-96: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
Jobs:0000001198 Accepted:0000000120 Rejected:0000000859 (0:6) F1 F2 F3
MHS:01656 Utility:023 Efficieny:010.01%
Started before: 0d,00h,05m,18s
Current pool: mint.bitminter.com (B)
Switch mode: Primary/Backup
Clock selected: Low
Long Poll: active, LP requests: 1

EDIT:
It seems to be working slower now?   Huh  What could be causing this issue  Cry

Use a local stratum proxy
member
Activity: 87
Merit: 10
I have looked inside and I am now running the cube without the outside box.  I tightened the heatsinks and everything, but the bottom chips still show 000.  If I move the blades it doesn't fix the problem.  My v2 blade has the same settings but has run without issues.  I have this wonky thing where the firmware shows less than its actually mining on bitminter on both machines.  How would I fix the comms pin?

Thanks in advance!  Will send BTC if anyone can get it fixed.

ASIC_01-16: O O O O O O O O O O O O O O O O
ASIC_17-32: O O O O O O O O O O O O O O O O
ASIC_33-48: O O O O O O O O O O O O O O O O
ASIC_49-64: O O O O O O O O O O O O O O O O
ASIC_65-80: O O O O O O O O O O O O O O O x
ASIC_81-96: O O O O O O O O O O O O O O O O
M_01-16: 041 041 013 110 041 027 041 013 096 013 027 069 041 027 069 013
M_17-32: 041 013 000 069 055 000 013 041 013 000 069 013 041 027 027 027
M_33-48: 000 041 000 013 013 000 055 013 055 027 013 000 027 013 000 041
M_49-64: 000 000 013 000 000 013 000 055 013 013 041 013 027 000 000 000
M_65-80: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
M_81-96: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
Jobs:0000001198 Accepted:0000000120 Rejected:0000000859 (0:6) F1 F2 F3
MHS:01656 Utility:023 Efficieny:010.01%
Started before: 0d,00h,05m,18s
Current pool: mint.bitminter.com (B)
Switch mode: Primary/Backup
Clock selected: Low
Long Poll: active, LP requests: 1

EDIT:
It seems to be working slower now?   Huh  What could be causing this issue  Cry
legendary
Activity: 1666
Merit: 1185
dogiecoin.com
I'm having a problem where I'm only getting about 17ghz.  I'm using getwork on Bitminter without a proxy and a cx500 for one cube. 
The last row of chips don't show they're bad but I'm getting just about 0 mhz on them.  Any solutions?  It doesn't seem to be a power problem......i have 11.91 volts on the 12v rail.  When I set the cube to high, nothing changes.  I do initially run at 25 gh/s but it quickly drops down to this 17 gh/s

IP   192.168.1.201
Mask   255.255.255.0
Gateway   0.0.0.0
WEB Port   8000
Primary DNS   192.168.1.1
Secondary DNS   8.8.8.8
Pool ports   8332,8332
Pool addresses   mint.bitminter.com,mint.bitminter.com
Miners user:pass   Lucky7Chess_Cube:x,Lucky7Chess_Cube:x

Thanks in advance!!

Open it up and see if there is anything obvious wrong. I doubt the OOOO is more complicated than a comms pin.
member
Activity: 87
Merit: 10
I'm having a problem where I'm only getting about 17ghz.  I'm using getwork on Bitminter without a proxy and a cx500 for one cube.  
The last row of chips don't show they're bad but I'm getting just about 0 mhz on them.  Any solutions?  It doesn't seem to be a power problem......i have 11.91 volts on the 12v rail.  When I set the cube to high, nothing changes.  My cube does initially run at 25 gh/s but it quickly drops down to this 17 gh/s

IP   192.168.1.201
Mask   255.255.255.0
Gateway   0.0.0.0
WEB Port   8000
Primary DNS   192.168.1.1
Secondary DNS   8.8.8.8
Pool ports   8332,8332
Pool addresses   mint.bitminter.com,mint.bitminter.com
Miners user:pass   Lucky7Chess_Cube:x,Lucky7Chess_Cube:x

Thanks in advance!!
legendary
Activity: 1666
Merit: 1185
dogiecoin.com
Hi,

Anyone know where i can get spare blade modules for an erupter cube? I have 1 faulty one that if inserted pulls all the others down.


Cheers
You'll have to talk to your distributor, they may have a cannibalised cube they can take a blade from rather than having to send back the entire unit.
full member
Activity: 161
Merit: 100
digging in the bits... now ant powered!
Hi,

Anyone know where i can get spare blade modules for an erupter cube? I have 1 faulty one that if inserted pulls all the others down.


Cheers
legendary
Activity: 1666
Merit: 1185
dogiecoin.com
I like the one on your site a bit better.

It definitely has a marked improvement in readability which really may help new users.

Good job.

Thanks, I'll keep going.
member
Activity: 98
Merit: 10
I like the one on your site a bit better.

It definitely has a marked improvement in readability which really may help new users.

Good job.
Pages:
Jump to: