[SOLVED] Cannot reach configuration page of asicminer block erupter cube

[CompNsci]

Hi All,

Having read through most of the posts in this forum concerning keywords like those in the title, I thought I would start a new thread for those block erupter cubes which are really unreachable on the LAN port.

That is, I have a cube hooked to a LAN with a computer on the 192.168.1.0 subnet. I have factory reset the cube multiple times. The cube powers up and has a link light on the LAN interface, but is not reachable at its nominal address http://192.168.1.254:8000. Furthermore, it doesn't respond to a ping or to a broadcast ping.

What is the best procedure for trying to get one of these to work under these circumstances? Is there a known method of using the USB port to interrogate this or reset the firmware? Any documentation on the USB port?

thanks,

[xstr8guy]

I just started having the same problem with some old blades that have been running for a long time.  I've never had this problem with them before. Strange.

[CompNsci]

Yes, this cube that is having this problem also was previously working.

[xstr8guy]

My blades are mining just fine but I can't reconfigure user/pass for other pools now.  I'm stuck mining Maza, lol.

I was kind of hoping I could dump these on eBay soon but I won't unless I can solve this issue.

[CompNsci]

My blades are mining just fine but I can't reconfigure user/pass for other pools now.  I'm stuck mining Maza, lol.

I was kind of hoping I could dump these on eBay soon but I won't unless I can solve this issue.

Out of curiosity, you mention blades here, are they basically the same interface as the cubes?

[CompNsci]

Starting to work on USB port access. It appears the USB port has a Silicon Labs CP2102 USB-UART convertor. Drivers are available on this website: http://www.silabs.com/products/mcu/pages/usbtouartbridgevcpdrivers.aspx.

Under MacOS X, this driver does install and presents a serial communications port as /dev/SLAB_USBtoUART.

The serial port settings appear to be 115200 baud, 8 bit word, no parity, 1 stop bit.

Watching this port shows output indicating the device periodically starts into a boot loader, an number of tests, ending in 'All tests done! BE Cube started'.

Pressing the factory reset while powered on produces the message "Config saved!" then goes through the same sequence.

This cube has now started presenting the configuration page periodically, whenever it doesn't show that it is running the self test via messages on the serial port. It is unclear if this was due to yet another factory reset with a prolonged depression of reset button, or solely due to waiting until the 'BE Cube started' message appears on the serial terminal and then accessing its web page. Once on the page, reconfiguration to another ip address was possible.

During mining the serial port outputs a sequence of a,b,c,d letters, in a mixture of upper and lower case.

When the cube cannot reach its mining pools, it appears to periodically reset, and during self test cannot be reached on the LAN port.

Therefore, if a cube appears unreachable, checking its serial port is useful as one can wait until it says 'BE Cube started' and then try and reach the configuration page.

[xstr8guy]

My blades are mining just fine but I can't reconfigure user/pass for other pools now.  I'm stuck mining Maza, lol.

I was kind of hoping I could dump these on eBay soon but I won't unless I can solve this issue.

Out of curiosity, you mention blades here, are they basically the same interface as the cubes?

The Blades are strictly Ethernet, no USB.  So I imagine there is some difference in how they are configured.  To be frank, I know nothing about the Cubes so I wasn't even aware that they were USB.