Re: [Guide] Dogie's Comprehensive ASICMiner Cube Setup

Hi miners. I have this problem.

My cube run good when i am in work. When i am not at home.

When come home parrents and me and turn on computers or TV or i dont know what cube stop hashing and start next day on morning.

I dont know where is problem. Can any pc or TV with lan interrupt my cube?

Please if have anybody any solution send me any settings for cube.
Here or on email donkezz@gmail.com

Maybe set two different subnets? All devices in first subnet and notebook with proxy and cube to second subnet ?

I try setup different dns, web port, IPs i dont know how can i fix it.

Here is when is hashing very slow.
http://i.imgur.com/R0rr5Wu.jpg

Here is when hashing good.
http://i.imgur.com/DvnZkbH.jpg

I try it setup about 20 days but not working 24 hours nonstop. Max 10-12 hours.

Thanks

Yes, it is possible that you cannot draw enough power on the circuit you have the cube's power supply plugged into if you have a lot of other equipment (tv's, computers, etc) all plugged into the same power cable. I'm not sure where you are physically located (globally), but in the US we usually have no more that 12 plugs (6 outlets) on a single circuit. If this is the case, you should try moving your cube to another room, one that perhaps doesn't have anything else in it... maybe an unused bedroom, or little used basement area.

Hmm i can try but i have it in the roome where is only one notebook with proxy one cube and one fridge (icebox).
Problem is in the power or can be in the lan subnet ?. If only power circuit i try it change.

Thanks

The only reason your LAN would affect it is if you have miss IP'ed something so that the cube shares an IP with one of your computers. You could verify that each device has an IP address separate from the others on your network; this is one reason I wish the cubes would use DHCP. I digress, just make sure each device has it's own unique IP on your LAN and you should be fine there... One way to ensure this is to have your router's DHCP server issue IP addresses in a known range; say... 192.168.1.10 ~ 192.168.1.50, and then set your cube IP addresses manually to 192.168.1.101, 102, ... etc. Then when computers or devices fetch a DCHP address, they'll automatically be assigned within your range (10 ~ 50) and would never interfere with the cubes.

Just a thought.