Just wanted to confirm that for the life of me I couldn't get it to work until I tried a trailing slash after the port number.

Downloaded and compiled from github this morning on ubuntu 14.04.1 32-bit. Using solely as a proxy for my ASICMiner tubes. When I try to connect, Berliner shows 100% HW errors and no work is ever done for the pool. Miner interface shows 100% rejected.

I looked on github for a related issue but nothing jumped out at me. Is it possible I screwed something up with dependencies? Any known issues that just aren't on github? Any help would be appreciated.

Edit: just realized I pulled from master. When I get home later I'll try the 4.7.0 release and see if it works.

Had a similar issue at some point. Make sure you set diff=n in bfgminer, where n is a max difficulty presented to the miner. From whatbi can tell, without setting it the miner->proxy difficulty stays at 1 even when the proxy->pool difficulty is higher. Bfgminer seems to not pass on the pool difficulty unless you set a max in bfgminer, even if that max is super high. After I did this, my reject rate was comparable to without the proxy. I think the controller or the boards get tripped up at difficulty 1 after some period of time. But I have no hard proof of this, just an observation.

Dogie- any chance for an explanation of the somewhat cryptic options towards the bottom of the settings page?

Specifically

RollNtime[ s]
WakeUp period[ s]
Normal/Smart[0/1]

It should be better even just using a single feed with two connectors. I believe it should reduce the stress on the connectors, long term.

Website down? Also my last payout was awfully small...

Are the giveaways over now? Is the bonus still running? I'm afraid I was late to the party...

I believe with these you can run 5 tubes off 4 PSU.

Kinda looks like the 140mm one might be good to also run air over the surface of the boards in addition to through the tube.

Well, I look forward to it.

Maybe we can merge the threads? Or you can just contribute here? No need to spread the info around even more. I just wanted to put it all in one place so owners don't have to go searching multiple threads.

Hi Everyone-

I started a thread where we can consolidate information from the various ASICMiner Tube -related threads. the thread is here:

https://bitcointalk.org/index.php?topic=768500

I added what info I could in the time I had to spare. All contributions are welcome. I will monitor that thread and add info to the OP as it is posted.

Hi Everyone-

I started a thread where we can consolidate information from the various ASICMiner Tube -related threads. the thread is here:

https://bitcointalk.org/index.php?topic=768500

I added what info I could in the time I had to spare. All contributions are welcome. I will monitor that thread and add info to the OP as it is posted.

Hi Everyone-

I started a thread where we can consolidate information from the various ASICMiner Tube -related threads. the thread is here:

https://bitcointalk.org/index.php?topic=768500

I added what info I could in the time I had to spare. All contributions are welcome. I will monitor that thread and add info to the OP as it is posted.

I'm starting this as a resource for ASICMiner Tube owners. There are currently 2-4 threads spread around the forums with various info that will be useful to have all in one place. Please post additional info here and I will try to keep the OP updated.

Note, this is entirely unofficial. I would love for someone to "officially" weigh in on these topics (Friedcat? PhaseBird?).

Anywhere you see a "" I'd love to have some input from other users.


Getting started

Note: see the useful links section for some setup pictures and videos.

Default IP of controller = 192.168.0.254

You can change the IP from the Settings page (see below), but you'll need to configure your computer/tablet/phone to be on the 192.168.0.xxx subnet initially (or configure your router's subnet mask to include the 192.168.0.xxx range).

On first boot, you should open the controller page in a broswer at http://192.168.0.254:8000 and check the "Test Status" page to make sure the right number of boards is showing up. If it is correct, go to http://192.168.0.254:8000/FlashMega to flash the boards to the latest firmware.


Pool Compatibility

Works out of the box with:

- ghash.io
- Slush's pool (mining.bitcoin.cz)
- Bitcoin Affiliate Network (mining.bitcoinaffiliatenetwork.com)
- mmpool.org
- BTC Guild (using stratum-lb-usa48.btcguild.com:3333 to connect)

Other pools may need to use a proxy.


Using BFGMiner as a proxy (Windows, Linux, Raspberry Pi, OpenWRT)

run BFGMiner with these options: -o <real pool url> -u <real pool username> -p <real pool password> --stratum-port 3333 --set-device PXY:diff=850

While BFGMiner is running, point the tube to the IP address of the machine BFGMiners is running on. Username and password don't matter.

Full instructions here: https://bitcointalk.org/index.php?topic=735728.msg8310763#msg8310763

Note: sometimes there is a problem with bfgminer where it reports an error with bufferevent and the controller will lock up and/or reset. When this happens, it seems the only solution is to power down and power back up your whole rig.

Note2: sometimes bfgminer starts kicking back tons of duplicaates causing a high reject rate. I cannot find a pattern to this.


Using ckpool as a proxy

Download, compile, and run ckpool from https://bitbucket.org/ckolivas/ckpool and run in proxy mode.

Using slush gekko proxy

Try out the code here: http://www.gekkoscience.com/misc/slush_gekko.tar

(documentation included in archive)


Interface

Test Status

For each healthy board you will see this:


Where "Board xx" is the unique board number and "V:x.xx" designates the firmware version of the board. If you have fewer status lines on this page than connected boards (4 boards per tube unit) then you have a bad board. If any of your boards doesnt show up as the above, but instead the "O" is replaced by a "-" or "." then you have bad chips on a board.

Statistics

For each running board you will see a line like this:


Prf = hashrate of board
ExP = expected hashrate of board
Uti = Shares per minute
Efi = Efficiency = Prf/ExP
HWe = Hardware error rate (Currently there seems to be a bug where HWe is periodically, incorrectly reported at 100%)
PwrDn = number of chips on this board that are dead (equal to number of "." characters for that board on the Test Status page)

Below the lines explained above, there is a row of buttons. In the middle of the buttons is the current clock speed of the miners. It looks like this:


ReSession = restart current mining session
ForceLP = Force Long Poll - Force the board to accept a new job
Clock Up = increase clock speed of mining boards by 10 MHz
Clock Down = decrease clock speed of mining boards by 10 MHz
Wake Up = (I think this just refreshes the page, but I'm not sure)
ReClock = Adjust time difference between local and pool

You will also see lines below that give a sumary of performance for the entire unit, which is however many boards you have chained together. It looks like this:


Accepted = total number of accepted shares
Rejected = total number of rejected shares
Hardware errors = (you guessed it) total % hardware errors
PwrDn = total number of chips that are dead
Real performance = total hashrate
Expected performance = total expected hashrate
Utility = total utility (not sure how calculated)
Miner = total efficiency
Network diff = total network difficulty
Worker diff = worker difficulty
Real_LP = number of real Long Poll events
Running time = uptime
Session time = total time in current session (I think time since starting hashing at current pool and connection... can anyone confirm?)
RS = number of resyncs on the data cable (errors on the data cable)
RC = number of reconnects to the pool
Sha/m = (I think shares per minute???)
Subm/m = (I think submissions per minute???)
Jobs/m = (I think jobs per minute???)
Nonce/m = (nonce per minute???)
Cmd/s = (related to communication between controller and boards)
Ans/s = (related to communication between controller and boards)


Settings

Settings is broken into 3 sections: LAN (network settings of the miner), Stratum (pool settings), and ASIC (settings for the device itself).

LAN Section

IP = IP address of miner
Mask = subnet mask of network miner is attached to
Gateway = gateway of network miner is attached to
WEB Port = port for accessing web interface
System port =
Primary/Secondary DNS = DNS servers for miner to use

Stratum Section

Pool URL = URL of mining pool to connect to (format like pool.server.com -- do not include "stratum+tcp://" or the port)
Pool port = port to connect to on the mining pool
User name = mining pool user name / worker name
Password = password for the mining pool user / worker

ASIC Section

Clock[Mhz] = starting clock speed of the boards (this can be adjusted dynamically from the Statistics page
RollNtime[ s] = How many seconds the board should change on nTime ( bigger means less communications to controller, default value should be OK)
WakeUp period[ s] =
Normal/Smart[0/1] = (all I can tell is that the firmware version on Test Status page shows difference, but no apparent impact to hash rate


Useful Links

- Setup guide (not english): http://www.iasicminer.com/index.php/action-viewnews-itemid-51
- HW assembly and SW setup guide: http://youtu.be/zEL5EKWwBx0


To-Do/Welcome Contributions

These are some things I think it would be useful to have included here but I haven't had time to put together myself. If you want to write them, I will include them. Or if they are present somewhere I can easily link to, please post a link.

- Prf and ExP of boards at different clock speeds along with power consumption at those speeds (so we can identify the most efficient clock speed to run at)
- More info on pools that work "out of the box"
- Information on anything above marked with , especially the ASIC settings (what do these things do?!)
- More complete guides for bfgminer and ckpool proxy
- Actual screenshots of all of the above
- Assembly instructions

Where did you see mention of a refund?

EDIT: checked OP. Saw bit about refund for early round 2 purchasers.

that would be excellent. I'd love to know if these settings can fix some of our problems.

Is anyone else using bfgminer as a proxy and periodically seeing a huge jump in duplicate shares causing high reject rates? I've noticed it periodically on ghash and initially it seems to happen on westhash as well...

I dont think I mind using BFGMiner as proxy, but I'll need a dedicated connection running it for best performance and less stales/dupes.

I was happy with it running on my HTPC, but when you start watching 1 HDTV MPEG2 stream and recording 2 others, the connection gets a little saturated @ 15-20mbps/stream, especially when its running in a virtualbox with bridged networking :/

@FriedCat

Have you seen all of the requests for better firmware? Is this even something you can personally do anything about? And if so, do you plan on updates?

I'd like to know before I invest in a Raspberry Pi or something similar. Please let us know publicly.