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

That's just for the management interface, I switched it to port 80 so it'd be the regular http port.  The cube communicates to the stratum proxy via port 8332.

*I will try it just in case, I'll switch the port back to 8000 and refresh.

*Result was no change to performance.

Just a thought, default port is 8000 not 80, so unless you made some changes that could be part of your problem

I'm actually not familiar with android phones, but I'd imagine there might be a QoS setting in there somewhere.  But, what I was talking more about would be QoS settings in your home WiFi router(s).  You might have some luck just turning that off.  Where it is on your routers depends on the interface; I wouldn't know where to look on yours - you'd just have to log in with admin access and go 'xploring, sorry.

Cubes and Blades are handshaking-hogs with all the getworks they trade, and my guess is that anything that causes retransmits or pauses throws them for a loop.  A different brand might help, but I wouldn't be sure.

I too, have to wonder if these cubes are screwed... I've been struggling to get mine over 300Mhps.

I've used this thread as my guide for installation and troubleshooting.  Now I've exhausted what I think should be looked at... I'd like to get someones else's perspective.  I'm using slush's pool, and his proxy; I've compiled on a fresh Linux install (I've also tried it on Windows, and received about the same results).  From many comments on this thread, I'm now using this string to run the proxy:  "/opt/slush0-stratum-mining-proxy-17d3226/mining_proxy.py -o stratum.bitcoin.cz -p 3333 -gp 8332".

The cube has a dedicated 700W power supply using two separate 6pin PCIE power leads, I've also installed it in a datacenter to make sure cooling and power would be both protected and adequate.  I've also tried another 750W power supply; no difference.

My settings:
BE Cube V9.17 ASIC GT (Proxy, Auto Longpoll support)

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 O
ASIC_81-96: O O O O O O O O O O O O O O O O
M_01-16: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
M_17-32: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
M_33-48: 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
M_49-64: 000 000 000 000 000 000 000 000 000 000 000 000 000 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:0000000006 Accepted:0000000000 Rejected:0000000000 (0:0) F1 F2 F3
MHS:00000 Utility:000 Efficieny:000.00%
Started before: 0d,00h,01m,55s
Current pool: 10.242.130.200 (A)
Switch mode: Primary/Backup
Clock selected: Low
Long Poll: inactive

IP
10.242.130.201
Mask
255.255.255.0
Gateway
10.242.130.1
WEB Port
80
Primary DNS
156.154.71.1
Secondary DNS
156.154.70.1
Pool ports
8332,8332
Pool addresses
10.242.130.200,10.242.130.200
Miners user:pass
BIT242.CUBE1A:X,BIT242.CUBE1A:X

What Slush is reporting:
Login   Password   Found blocks   Current shares   Score   Last share at   Mhash/s*
BIT242.CUBE1A   X   0   187   1100172.9292   1 minute   246.292



I've also changed out the network cable that goes to my ProCurve switch, and hard set the port the 10HDX; although it was auto-sensing this anyway.


A little bit of the proxy log:
2014-01-04 14:56:41,916 INFO proxy jobs.submit # Submitting 3b273ed3
2014-01-04 14:56:42,003 WARNING proxy getwork_listener._on_submit # [86ms] Share from 'BIT242.CUBE1A' accepted, diff 1
2014-01-04 14:56:44,197 INFO proxy client_service.handle_event # New job f4e0 for prevhash 8c84d998, clean_jobs=False
2014-01-04 14:57:15,092 INFO proxy client_service.handle_event # New job f4e1 for prevhash 8c84d998, clean_jobs=False
2014-01-04 14:57:44,313 INFO proxy client_service.handle_event # New job f4e2 for prevhash 8c84d998, clean_jobs=False
2014-01-04 14:58:14,534 INFO proxy client_service.handle_event # New job f4e3 for prevhash 8c84d998, clean_jobs=False
2014-01-04 14:58:44,465 INFO proxy client_service.handle_event # New job f4e4 for prevhash 8c84d998, clean_jobs=False
2014-01-04 14:59:09,658 INFO proxy getwork_listener._on_authorized # Worker 'BIT242.CUBE1A' asks for new work
2014-01-04 14:59:09,682 INFO proxy getwork_listener._on_authorized # Worker 'BIT242.CUBE1A' asks for new work
2014-01-04 14:59:09,691 INFO proxy getwork_listener._on_authorized # Worker 'BIT242.CUBE1A' asks for new work
2014-01-04 14:59:09,713 INFO proxy getwork_listener._on_authorized # Worker 'BIT242.CUBE1A' asks for new work
2014-01-04 14:59:09,792 INFO proxy getwork_listener.render_POST # Worker 'BIT242.CUBE1A' subscribed for LP
2014-01-04 14:59:09,841 INFO proxy getwork_listener._on_authorized # Worker 'BIT242.CUBE1A' asks for new work
2014-01-04 14:59:09,865 INFO proxy getwork_listener._on_authorized # Worker 'BIT242.CUBE1A' asks for new work
2014-01-04 14:59:09,888 INFO proxy getwork_listener._on_authorized # Worker 'BIT242.CUBE1A' asks for new work
2014-01-04 14:59:14,749 INFO proxy client_service.handle_event # New job f4e5 for prevhash 8c84d998, clean_jobs=False
2014-01-04 14:59:44,000 INFO proxy client_service.handle_event # New job f4e6 for prevhash dc70261b, clean_jobs=True
2014-01-04 14:59:44,001 INFO proxy getwork_listener._on_lp_broadcast # LP broadcast for worker 'BIT242.CUBE1A'
2014-01-04 14:59:44,002 INFO proxy getwork_listener._on_lp_broadcast # LP broadcast for worker 'BIT242.CUBE1A'
2014-01-04 14:59:44,003 INFO proxy getwork_listener._on_lp_broadcast # LP broadcast for worker 'BIT242.CUBE1A'
2014-01-04 14:59:44,003 INFO proxy getwork_listener._on_lp_broadcast # LP broadcast for worker 'BIT242.CUBE1A'
2014-01-04 14:59:44,004 INFO proxy getwork_listener._on_lp_broadcast # LP broadcast for worker 'BIT242.CUBE1A'
2014-01-04 14:59:44,918 INFO proxy client_service.handle_event # New job f4e7 for prevhash dc70261b, clean_jobs=False

Thank you, hope to hear where I went wrong and what can be done....

Oh, I just returned from the data center where I again took it a part and inspected that all the cards were seating well and the heat sync's were all on.  Nothing loose, and the 30A fuse is good too.

I can believe the trouble everyone is having with these cubes. My first night since I could not get a 1050w 'imcompatible' Seasonic PSU to work. I hooked up an antec 80+ 380w PSU (3-4 years old) from my HTPC and it still ran it fine in low mode getting 32GH+. Mind you, in High clock, it ran much slower about 15 GH's at best.

 I have to wonder if some of the cubes are screwed.

Thank you for your help I appreciate When I connect my 2 android phones to WiFi, the performance drops down like crazy... Do you have any trick ? I don't have any option of QoS (Quality of Service)...  

Damn! See that's what I was expecting to see... that's ridiculous... I need to get me a multimeter or voltameter or whatever and see what my 800W Bronze is pulling from the wall with just one Cube. 

I have 2 cubes running on a Corsair CX750, and they are pulling 724 Watts on high clock. 

And it all went wrong...

http://bayimg.com/aAfiMaAfp


Not getting anything above 500mhs and the proxy is reporting a lot of errors.


ok this is because of the settings I had set for the cube on bitminter. Back to 5ghs...


So a little further experimenting. I put a noname 400w in one of the power sockets and kept the 550 corsair on the other.

My think was that only the first three blades were showing any real out put so was thinking that one power socket powered 3 blades etc.

I let it run for 10 mins but with two psus the hashrate didn't get above 2300 less than half of what I was getting with the corsair alone.

I decided to try the 400w on it's own and it is giving me:



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 O
ASIC_81-96: O O O O O O O O O O O O O O O O
M_01-16: 073 114 114 114 032 122 139 122 278 098 188 155 220 220 139 261
M_17-32: 130 171 139 179 130 106 171 269 106 237 155 155 179 122 147 130
M_33-48: 049 147 098 089 065 114 024 016 016 000 000 032 000 065 000 000
M_49-64: 000 000 000 016 016 008 000 024 000 000 016 000 000 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:0000001367 Accepted:0000000701 Rejected:0000000002 (0:4) F1 F2 F3
MHS:05732 Utility:078 Efficieny:051.28%
Started before: 0d,00h,08m,57s
Current pool: 192.168.1.105 (A)
Switch mode: Primary/Backup
Clock selected: Low
Long Poll: active, LP requests: 0


Almost 700mhs more than the 550...

Can't wait til monday when the new 750 arrives. And if that doesn't do the job I know an electrical engineer

Thanks!  Was definitely curious about that

It depends on the efficiency of your PSU. For the advertised power consumption you need at least a 80Plus Gold PSU.

PSU: Corsair RM750 (80Plus Gold) ~ 90% efficiency

Kill-A-Watt at wall:

Low ~ 225 Watt
High ~ 325 Watt

PSU: When it still was working with a Corsair TX750 (80Plus Bronze) ~ 80% efficiency

Kill-A-Watt at wall:

Low ~ 255 Watt
High ~ 355 Watt

Ok now work fine 31 gh. I change dns servers on outer dns.

Perfect!  Glad to be able to help, and (sort of) glad my network problem wasn't a one-off.  I had been wondering if my house was just plain electrically screwed-up.    Anyway, great news - now enjoy those BTC!

Thanks alexrossi 

I solved it !!! I was before at 6400-8400MHS...

Now fully 30000-31000MHS Thank you twib2

It was a network issue, I bought a DLink Gigabit Switch... I was using the Router's switch (I think it's a crap...)

So guys if you have the same problem, just check your network: cut off WiFi and other things like that...  !

http://img11.hostingpics.net/pics/765504933.png

have you tried changing the fuse?

I tried everything I could think of again to get my Cube running off my Corsair CX750.  It plain doesn't work off that PSU.

It runs about 95% stable off the OCZ 600W, which isn't the most ideal PSU, as it's split rail, only 2x25A rails and all the useful connections run off 12V2.  I'm waiting on a 8-pin CPU extension lead to arrive, which I'll butcher on to one of my PCI-E extensions, so I can use both 12V rails.

to you guys who is having a problem with low efficiency/low hashrate, try changing to another ethernet port then make sure you press refresh on the config page a couple of times to see if the hash rises. Or maybe you guys are having problem with your psu, maybe it is not supplying enough to your miner.

also if you want to reach the highest possible hashrate of your miner you should set your clock settings to High.

i hope these can help.

Celebrated too early:




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 O
ASIC_81-96: O O O O O O O O O O O O O O O O
M_01-16: 142 136 131 117 138 132 154 171 188 196 176 198 193 194 193 192
M_17-32: 172 179 174 167 159 160 156 162 143 135 129 145 141 131 124 128
M_33-48: 119 133 128 118 093 076 055 033 020 007 005 002 000 000 000 000
M_49-64: 001 000 000 000 000 000 000 000 000 000 000 001 000 000 000 000
M_65-80: 000 000 000 000 001 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:0000076488 Accepted:0000041842 Rejected:0000000356 (0:3) F1 F2 F3
MHS:05881 Utility:080 Efficieny:054.70%

I'd like to blame the RPi but I've seen rigs that handle higher work loads...


I'm wondering if I need to bridge the wifi and the ehternet on the RPi. I removed the wifi adapter from it and didn't get any work even though it is plugged into the same router as the cube. Then I put the wifi adapter back in and took out the ethernet cable and couldn't connect to the pool.

Technically all those showing zero are the slowest