Quote from: qwertyasdfg on February 19, 2014, 03:03:11 AM

Quote from: qwertyasdfg on January 21, 2014, 07:26:56 PM

Quote from: qwertyasdfg on January 21, 2014, 07:01:36 PM

Quote from: Damnsammit on January 21, 2014, 06:59:35 PM

Quote from: qwertyasdfg on January 21, 2014, 06:55:18 PM

FINALLY today I received a new board via OC directly from yxt, now I've taken the old board out and put the new board in after switching over the mini blades and am trying to connect to it using 192.168.1.254:8000 but am unable to do so, I cannot even see the device anywhere in the wired devices section of my router!

Anyone got any advice on what I might be doing wrong here?? My routers subnet is 192.168.1.x

Do I have to flash this new board with some sort of firmware before I can use it to control the mini blades???

Your router isn't 192.168.1.254 is it? That was an issue I had when initially setting mine up.

Other than that, you might have to do a factory reset... strange though that you could connect with the old cube but not with the new boards.

Nope router is deffo not 192.168.1.254

I'm guna try a factory reset and will let you know if that works!

That seems to have done the trick however the x's have moved

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: x x x x x x x x 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

So I re-arranged the mini blades once again and the x's moved again, so I must have a faulty mini blade now which is rather annoying!

ASIC_01-16: x x x x x x x x 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

I received the replacement mini blade this morning and have replaced the faulty blade in my cube and it's all up and running now with no more x's but for some strange reason I cannot seem to get it functioning properly in High Clock mode!

Every time I try and switch to overclocked mode the cube starts loosing it's hashrate and efficiency till it functions no more and I'm left with all x's at which point I have to restart the machine to get it hashing again only in low clock mode, can anyone suggest what might be going wrong here?

Anyone able to offer me any advise on this?

Further info on my setup is as follows:
1 Cube
1 Corsair CX600 PSU
1 Win 7 64bit about a year old Laptop acting as the proxy WIRED to a netgear router
Using the latest version of proxy miner found here http://mining.bitcoin.cz/mining-proxy-howto