Yes and no.  It doesnt show on the BAMT stats screen if you direct your browser to your miners local IP, but if you SSH into your system and use screen -r to look at your cgminer screen then you will see it there.

Okay, I have 3 suggestions.

1) You have too many plugged into one hub.  That doesnt solve the "no devices found" problem, but generally I have always found it better to run 1 less BE in a hub than what the maximum is.

2) Download and run bfgminer.  Once you have downloaded the drivers for your BE you wont need to do anything with drivers (will get to that later with cgminer setup).  Then you would run bfgminer with bfgminer.exe -o [url of pool] -u [username of pool] -p [password of pool] -S All --icarus-options 115200:1:1 --icarus-timing 3.0=100 -G     The -G is to disable it from using your GPU's, unless you also want to use your GPU(s), then in that case delete that part.

3) If you want to use cgminer, then you need to do a little tricking with the drivers, as well as use an updated version of cgminer.  People still like using 3.1.1 because it was the last version to use the old FTDI windows drivers, instead of winusb and people dont want to mess around with switching the drivers.  However, the newer versions just acts better, and there are far less configuring you have to do once you switch over the drivers.  So....

     

• Download the latest version of cgminer (as of this writing I believe its 3.4.1)
  
• Also download zadig (also available from ckoivas git)
• Unplug all of your erupters except for one
• Start zadig, go to options, and tell it to show all devices
• Find your BE and select it, then below it will show the current driver, and a list next to it of available drivers.  Select the winusb driver and then change it
• Now when you plug in the rest of your BE's they should all associate themselves with the winusb driver
• Fire up cgminer like normal and input your pool, username, password.  Thats it.  No other options needed unless you want to disable your GPU (again using -G, or running cgminer-nogpu.exe)

   

I still run BAMT on two of my machines.  I have updated them to be able to handle updated GPUs, as well as scrypt and ASIC's.  One sits in my basement and I access it via SSH when needed.

If you are using this tut, it says right in it that its for pool mining, and to not even bother with solo mining.  So, what did you change in your setup to alter this?  If you followed this step by step, then it set you up for pool mining, not solo mining (i.e. you are not accessing a pool, but rather you are trying to find and solve a block on your own).

I would check your EMC stats directly from their site first (could be an API problem).  If you still see that you do not have any shares, then maybe its time to move over to one of the more mainstream miners (cgminer or bfgminer).  Guiminer is okay, but the learning curve on cgminer and bfgminer isnt that much that someone who puts 10 minutes of effort into cant learn it, especially on a Windows machine.

I think pinwheel had it right, the configuration is correct, but since you are solo mining, there is no accepted shares or anything like you would get out of a normal pool.  You either solve a block, and thus get the reward, or you get nothing. 

I have seen where someone use -S erupter:all instead of -S all, dont know if that worked in bfgminer.  Also, you have to make sure you have the icarus options configured right, --icarus-options 115200:1:1 --icarus-timing 3.0=100"

Check their thread.  Looks like the site is down, but you can still connect to the servers and do work.

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

If you installed cgminer using the referenced guide, and you are trying to mine scrypt, it wont work.  

cgminer does not enable scrypt mining by default, when you ./configure it, you have to add the argument of --enable-scrypt.  By default, cgminer only enables gpu mining in linux, so if you are mining scrypt or asics, you have to enable those options when compiling, which is why its telling you that it doesnt recognize --scrypt as being valid.

So, redo install cgminer and use these options (also, that guide enables cpumining, which cgminer doesnt even support anymore).


This will enable scrypt mining, as well as support for BFL ASICS, Avalon devices, and block erupters in case you want to add them later.

Well I have used a proxy for two reasons, one, I have hardware in a different site and the firewall there likes to block port 3333 which is used a lot of the time for stratum, so I would bounce my connection out of an open port to my proxy running at home so I could keep it connected.  Secondly, there were some places that would ban you if it caught you using multiple IP addresses for the same account, so I had to use my proxy in order to have rigs setup in different places show the same IP address.

Didnt know this had been disabled, which explains why when I tried using it the other day to mine scrypt I couldnt because P2Pool uses a port thats blocked and I attempted to bounce it off my proxy and it failed....

That almost sounds like a pool or internet connection issue, not a cgminer issue.

If you are running Windows, I would suggest cgwatcher.  It will monitor your instance and restart if things go bad.

It depends on the coin and the algorithm its in.  BE's are coded to only work with sha256.  Many of the alt coins are coded to run scrypt, so no you cannot use your BE's to mine them.

They keep an update as to where they are in their shipping queue.  Probably why they arent responding because the information is there.  This is something that everyone should know about before ordering. 

https://forums.butterflylabs.com/blogs/bfl_jody/

Did you not know of how backordered these units were before you placed your order?

.....you know, I had typed up this big, long reply, but instead I am going to ask this, when did you order? And did you know about the delays/where they are in their shipping queue before you placed your order?

You shouldnt have to enable icarus, its enabled by default.  When you compile, did you scroll up and check that it shows icarus as enabled?

Maybe there is a "sync" thats missing somewhere, like after you do "make".  I dont know, sometimes I have success without sync and sometimes I dont.

-d command I believe is only for GPUs.  Looks like you want to separate your GPU and block erupter mining instances.  So, per the README....

instance 1: use --usb :0  (this will disable USB devices in this instance and only use your GPUs), then set your normal GPU settings (gpu engine, memclock, etc)

instance 2: use -G (this will disable all GPU devices for this instance and only use your USB devices)

We will need more info like what OS you are running, what arguments you are using with cgminer, what version of cgminer you are using, etc....

This is what the command should look like for bfg, it still uses icarus timing.

-S All --icarus-options 115200:1:1 --icarus-timing 3.0=100 --disable-gpu

Remove the --disable-gpu if you actually want to use the gpu as well as your block erupters.

You might try adding "api-listen" : true, to your settings in your config file. Not sure if this is whats affecting it, but I know CGWatcher needs full API access in order to work properly.