Block Erupter Prisma (>=1.4 T/device, 0.75-0.78 W/G, <1 BTC/T, October Shipping)

[PCComf]

So has anyone actually gotten these to work on a standard Linux machine yet? I keep getting the "Unexpected value 00 received" error. I've tried different git branches suggested in previous posts. I've re-cabled this in various ways also with no success.

I have a Pi somewhere I will try to repurpose for this if that is what it takes.

Try their cgminer branch which got updated recently.
https://github.com/blockerupter/cgminer

If this doesn't affect hash rate(around 350GH/s per board), just ignore this kind of error. I got several boards with occasional errors like this, yet all works well.

Thanks, I downloaded that branch again and tried it, but same issue. I never get any hashing and I've even tried each board individually.

[Blazed]

So has anyone actually gotten these to work on a standard Linux machine yet? I keep getting the "Unexpected value 00 received" error. I've tried different git branches suggested in previous posts. I've re-cabled this in various ways also with no success.

I have a Pi somewhere I will try to repurpose for this if that is what it takes.

Try their cgminer branch which got updated recently.
https://github.com/blockerupter/cgminer

If this doesn't affect hash rate(around 350GH/s per board), just ignore this kind of error. I got several boards with occasional errors like this, yet all works well.

Thanks, I downloaded that branch again and tried it, but same issue. I never get any hashing and I've even tried each board individually.

Most likely a bad USB adapter..pretty common. I had the exact same issue and sold my Prisma off to someone with a BE Controller, and it worked for him. If you do not have another controller you need to find one or sell that crap miner off.

[praeluceo]

So has anyone actually gotten these to work on a standard Linux machine yet? I keep getting the "Unexpected value 00 received" error. I've tried different git branches suggested in previous posts. I've re-cabled this in various ways also with no success.

I have a Pi somewhere I will try to repurpose for this if that is what it takes.

Try their cgminer branch which got updated recently.
https://github.com/blockerupter/cgminer

If this doesn't affect hash rate(around 350GH/s per board), just ignore this kind of error. I got several boards with occasional errors like this, yet all works well.

Thanks, I downloaded that branch again and tried it, but same issue. I never get any hashing and I've even tried each board individually.

Most likely a bad USB adapter..pretty common. I had the exact same issue and sold my Prisma off to someone with a BE Controller, and it worked for him. If you do not have another controller you need to find one or sell that crap miner off.

Has anyone had any success at getting additional USB adapters? I've sent emails to Phasebird, and PMs here, but no support whatsoever. It's like ASICMiner went bankrupt over the past month and entirely disappeared off the face of the earth.

We have really late miners here, and we really need support. That, or has anyone tried using a regular USB to UART adapter? I see the Prisma ones are 3 PINs, are these specific serial or I2C pins that we could use another device to talk to the miner over? I haven't looked closely to see if they have a visible USB FTDI (or knockoff) chip on it, but if so it'd at least be a step in the right direction.

[TheRealSteve]

or has anyone tried using a regular USB to UART adapter?

One user modified an old Block Erupter USB (those small things that plug straight into a USB port) to work with a Block Erupter Prisma;
[DIY] Tube/Prisma USB Adapter from USB Blockerupter

He notes:

You should theoretically be able to use any CP2102 USB-UART witha 1K pullup resistor from 3.3V to RXD in this fashion.

YMMV

[praeluceo]

or has anyone tried using a regular USB to UART adapter?

One user modified an old Block Erupter USB (those small things that plug straight into a USB port) to work with a Block Erupter Prisma;
[DIY] Tube/Prisma USB Adapter from USB Blockerupter

He notes:

You should theoretically be able to use any CP2102 USB-UART witha 1K pullup resistor from 3.3V to RXD in this fashion.

YMMV

Hey, that's great, thank you! Now to see if I have any of those laying around, I have a feeling though that I don't. But CP2102s should be easy to find I think.

[ManeBjorn]

I am seeing about doing a run of the USB adapters.  I will get it all set in a day or two and let you know prices and such.
Hopefully we can get these in more peoples hands.
They are harder to get a hold of than FiedCat right now. LOL

or has anyone tried using a regular USB to UART adapter?

One user modified an old Block Erupter USB (those small things that plug straight into a USB port) to work with a Block Erupter Prisma;
[DIY] Tube/Prisma USB Adapter from USB Blockerupter

He notes:

You should theoretically be able to use any CP2102 USB-UART witha 1K pullup resistor from 3.3V to RXD in this fashion.

YMMV

Hey, that's great, thank you! Now to see if I have any of those laying around, I have a feeling though that I don't. But CP2102s should be easy to find I think.

[praeluceo]

I am seeing about doing a run of the USB adapters.  I will get it all set in a day or two and let you know prices and such.
Hopefully we can get these in more peoples hands.
They are harder to get a hold of than FiedCat right now. LOL

or has anyone tried using a regular USB to UART adapter?

One user modified an old Block Erupter USB (those small things that plug straight into a USB port) to work with a Block Erupter Prisma;
[DIY] Tube/Prisma USB Adapter from USB Blockerupter

He notes:

You should theoretically be able to use any CP2102 USB-UART witha 1K pullup resistor from 3.3V to RXD in this fashion.

YMMV

Hey, that's great, thank you! Now to see if I have any of those laying around, I have a feeling though that I don't. But CP2102s should be easy to find I think.

No kidding, I've sent emails and PMs to Friedcat and Phasebird, no luck. Sorry to hear about your popping cap (haha, we're Bitcoin gangstas, popping caps in the process of obtaining hash). I wonder if the proximity to the fan controller contributed? Maybe there's a short near the fan socket, or the potential for bridging between the the fan power and a trace that runs to that cap?

As far as the CP2102 goes, I think I have an old Sparkfun USB/serial adapter, but I have to find it:
https://www.sparkfun.com/products/retired/8531
Unfortunately, now all of their USB to serial devices use FTDI chips, which although should work, won't be detected by cgminer.

I'd be interested in following your progress on this! We've done a few (non-Bitcoin) board runs for various prototypes, and looking at this USB adapter it shouldn't be too difficult to mimic the functionality. I was just hoping to have everything hashing stably without having to wait for a custom PCB, parts, and then assembling it. You know, the expectation was kinda sorta that these would work...in October. But, AM became a preorder scam company apparently, and my main priority is salvaging some of my investment in their hardware, and being glad I don't own shares.

[Blazed]

I have to say thank you AM for the amazing products and support...simply the best!

[tutorialevideo]

Customs problems, i need a invoice from friedcat and no answer on the email/qq. My prismas are at customs.

[Scorch]

have anyone any idea how to dispose error like that:
 [2014-11-20 18:04:29] BET1: Unexpected value 00 received
 [2014-11-20 18:04:29] BET1: Unexpected value 00 received
 [2014-11-20 18:04:29] BET1: Unexpected value 00 received
 [2014-11-20 18:04:29] BET1: Unexpected value 00 received
 [2014-11-20 18:04:30] BET1: Unexpected value 00 received
 [2014-11-20 18:04:32] Accepted 090fd4db Diff 7.23K/4096 BET 1

 [2014-11-20 18:04:33] BET1: Unexpected value 00 received
 [2014-11-20 18:04:43] BET1: Unexpected value 00 received
 [2014-11-20 18:04:43] BET1: Unexpected value 00 received
 [2014-11-20 18:04:43] BET1: Unexpected value 00 received
 [2014-11-20 18:04:43] BET1: Unexpected value 00 received
 [2014-11-20 18:04:44] BET1: Unexpected value 00 received
 [2014-11-20 18:04:44] BET1: Unexpected value 00 received

[TracerX]

have anyone any idea how to dispose error like that:
 [2014-11-20 18:04:29] BET1: Unexpected value 00 received
 [2014-11-20 18:04:29] BET1: Unexpected value 00 received
 [2014-11-20 18:04:29] BET1: Unexpected value 00 received
 [2014-11-20 18:04:29] BET1: Unexpected value 00 received
 [2014-11-20 18:04:30] BET1: Unexpected value 00 received
 [2014-11-20 18:04:32] Accepted 090fd4db Diff 7.23K/4096 BET 1

 [2014-11-20 18:04:33] BET1: Unexpected value 00 received
 [2014-11-20 18:04:43] BET1: Unexpected value 00 received
 [2014-11-20 18:04:43] BET1: Unexpected value 00 received
 [2014-11-20 18:04:43] BET1: Unexpected value 00 received
 [2014-11-20 18:04:43] BET1: Unexpected value 00 received
 [2014-11-20 18:04:44] BET1: Unexpected value 00 received
 [2014-11-20 18:04:44] BET1: Unexpected value 00 received

It's been suggested that restarting the mining software (repeatedly) will eventually clear those up.  I've found that I have to restart cgminer between 5-10 times before it finally "takes."  I know that's not an amazing solution, but the devices seem to run pretty trouble-free once they're hashing...

Cheers.

[Scorch]

have anyone any idea how to dispose error like that:
 [2014-11-20 18:04:29] BET1: Unexpected value 00 received
 [2014-11-20 18:04:29] BET1: Unexpected value 00 received
 [2014-11-20 18:04:29] BET1: Unexpected value 00 received
 [2014-11-20 18:04:29] BET1: Unexpected value 00 received
 [2014-11-20 18:04:30] BET1: Unexpected value 00 received
 [2014-11-20 18:04:32] Accepted 090fd4db Diff 7.23K/4096 BET 1

 [2014-11-20 18:04:33] BET1: Unexpected value 00 received
 [2014-11-20 18:04:43] BET1: Unexpected value 00 received
 [2014-11-20 18:04:43] BET1: Unexpected value 00 received
 [2014-11-20 18:04:43] BET1: Unexpected value 00 received
 [2014-11-20 18:04:43] BET1: Unexpected value 00 received
 [2014-11-20 18:04:44] BET1: Unexpected value 00 received
 [2014-11-20 18:04:44] BET1: Unexpected value 00 received

It's been suggested that restarting the mining software (repeatedly) will eventually clear those up.  I've found that I have to restart cgminer between 5-10 times before it finally "takes."  I know that's not an amazing solution, but the devices seem to run pretty trouble-free once they're hashing...

Cheers.

nope restarting dosn't help

[LordPaco]

It's been suggested that restarting the mining software (repeatedly) will eventually clear those up.  I've found that I have to restart cgminer between 5-10 times before it finally "takes."  I know that's not an amazing solution, but the devices seem to run pretty trouble-free once they're hashing...

Cheers.

I've noticed some of that too.. but the problem is, how do you run any amount of them in mass like that? Do they employ a team of peeps at the AMHASH1 data center rebooting arrays until they hash? What about a power blip that resets everything? What a headache 

[TracerX]

It's been suggested that restarting the mining software (repeatedly) will eventually clear those up.  I've found that I have to restart cgminer between 5-10 times before it finally "takes."  I know that's not an amazing solution, but the devices seem to run pretty trouble-free once they're hashing...

Cheers.

I've noticed some of that too.. but the problem is, how do you run any amount of them in mass like that? Do they employ a team of peeps at the AMHASH1 data center rebooting arrays until they hash? What about a power blip that resets everything? What a headache  

My machines are housed in a DC, so I feel your pain.  I've taken to using the "Mobileminer" APIs to monitor and restart them remotely.  That said, since these devices are likely running cgminer on a rPi, you could use a number of tools that plug into that API set to keep things running.

I imagine we could even scratch together a log monitoring system that would restart cgminer automatically until the errors cleared.  If I get some time this weekend (I won't) I'll work on that....

[TracerX]

have anyone any idea how to dispose error like that:
 [2014-11-20 18:04:29] BET1: Unexpected value 00 received
 [2014-11-20 18:04:29] BET1: Unexpected value 00 received
 [2014-11-20 18:04:29] BET1: Unexpected value 00 received
 [2014-11-20 18:04:29] BET1: Unexpected value 00 received
 [2014-11-20 18:04:30] BET1: Unexpected value 00 received
 [2014-11-20 18:04:32] Accepted 090fd4db Diff 7.23K/4096 BET 1

 [2014-11-20 18:04:33] BET1: Unexpected value 00 received
 [2014-11-20 18:04:43] BET1: Unexpected value 00 received
 [2014-11-20 18:04:43] BET1: Unexpected value 00 received
 [2014-11-20 18:04:43] BET1: Unexpected value 00 received
 [2014-11-20 18:04:43] BET1: Unexpected value 00 received
 [2014-11-20 18:04:44] BET1: Unexpected value 00 received
 [2014-11-20 18:04:44] BET1: Unexpected value 00 received

It's been suggested that restarting the mining software (repeatedly) will eventually clear those up.  I've found that I have to restart cgminer between 5-10 times before it finally "takes."  I know that's not an amazing solution, but the devices seem to run pretty trouble-free once they're hashing...

Cheers.

nope restarting dosn't help

I notice that you have "BET1" listed as the device.  Are you using more than one USB UART controller on your system?

[Scorch]

have anyone any idea how to dispose error like that:
 [2014-11-20 18:04:29] BET1: Unexpected value 00 received
 [2014-11-20 18:04:29] BET1: Unexpected value 00 received
 [2014-11-20 18:04:29] BET1: Unexpected value 00 received
 [2014-11-20 18:04:29] BET1: Unexpected value 00 received
 [2014-11-20 18:04:30] BET1: Unexpected value 00 received
 [2014-11-20 18:04:32] Accepted 090fd4db Diff 7.23K/4096 BET 1

 [2014-11-20 18:04:33] BET1: Unexpected value 00 received
 [2014-11-20 18:04:43] BET1: Unexpected value 00 received
 [2014-11-20 18:04:43] BET1: Unexpected value 00 received
 [2014-11-20 18:04:43] BET1: Unexpected value 00 received
 [2014-11-20 18:04:43] BET1: Unexpected value 00 received
 [2014-11-20 18:04:44] BET1: Unexpected value 00 received
 [2014-11-20 18:04:44] BET1: Unexpected value 00 received

It's been suggested that restarting the mining software (repeatedly) will eventually clear those up.  I've found that I have to restart cgminer between 5-10 times before it finally "takes."  I know that's not an amazing solution, but the devices seem to run pretty trouble-free once they're hashing...

Cheers.

nope restarting dosn't help

I notice that you have "BET1" listed as the device.  Are you using more than one USB UART controller on your system?

for a few min i have two of them plug into computer but no mater if it's one or two always this same error :/

[TracerX]

have anyone any idea how to dispose error like that:
 [2014-11-20 18:04:29] BET1: Unexpected value 00 received
 [2014-11-20 18:04:29] BET1: Unexpected value 00 received
 [2014-11-20 18:04:29] BET1: Unexpected value 00 received
 [2014-11-20 18:04:29] BET1: Unexpected value 00 received
 [2014-11-20 18:04:30] BET1: Unexpected value 00 received
 [2014-11-20 18:04:32] Accepted 090fd4db Diff 7.23K/4096 BET 1

 [2014-11-20 18:04:33] BET1: Unexpected value 00 received
 [2014-11-20 18:04:43] BET1: Unexpected value 00 received
 [2014-11-20 18:04:43] BET1: Unexpected value 00 received
 [2014-11-20 18:04:43] BET1: Unexpected value 00 received
 [2014-11-20 18:04:43] BET1: Unexpected value 00 received
 [2014-11-20 18:04:44] BET1: Unexpected value 00 received
 [2014-11-20 18:04:44] BET1: Unexpected value 00 received

It's been suggested that restarting the mining software (repeatedly) will eventually clear those up.  I've found that I have to restart cgminer between 5-10 times before it finally "takes."  I know that's not an amazing solution, but the devices seem to run pretty trouble-free once they're hashing...

Cheers.

nope restarting dosn't help

I notice that you have "BET1" listed as the device.  Are you using more than one USB UART controller on your system?

for a few min i have two of them plug into computer but no mater if it's one or two always this same error :/

That explains the log, then!  Which version of cgminer are you using?

[Chris_Sabian]

have anyone any idea how to dispose error like that:
 [2014-11-20 18:04:29] BET1: Unexpected value 00 received
 [2014-11-20 18:04:29] BET1: Unexpected value 00 received
 [2014-11-20 18:04:29] BET1: Unexpected value 00 received
 [2014-11-20 18:04:29] BET1: Unexpected value 00 received
 [2014-11-20 18:04:30] BET1: Unexpected value 00 received
 [2014-11-20 18:04:32] Accepted 090fd4db Diff 7.23K/4096 BET 1

 [2014-11-20 18:04:33] BET1: Unexpected value 00 received
 [2014-11-20 18:04:43] BET1: Unexpected value 00 received
 [2014-11-20 18:04:43] BET1: Unexpected value 00 received
 [2014-11-20 18:04:43] BET1: Unexpected value 00 received
 [2014-11-20 18:04:43] BET1: Unexpected value 00 received
 [2014-11-20 18:04:44] BET1: Unexpected value 00 received
 [2014-11-20 18:04:44] BET1: Unexpected value 00 received

Join the club.  I've tried almost everything to get this piece of crap to hash.  I can't even get a single board to hash.  I've tried 2 different urt adapters, various builds of cgminer, different r-pi, different PSU, different builds of minera, different white 3 wires.  I'm probably 20 hr into troubleshooting over the last week and still getting the BET0 Unexpected value 00 received.  Expect 0 help from ASICMiner.  And these things were 3 weeks late shipping.

Check my posts the things I've tried

My last hope is a block erupter controller coming tomorrow.


100% would not recommend buying.  AM failed terribly on this.

CrazyGuy and Canary have been great trying to help troubleshoot.  CrazyGuy has gone the extra 10 miles to help get it running.

[Scorch]

have anyone any idea how to dispose error like that:
 [2014-11-20 18:04:29] BET1: Unexpected value 00 received
 [2014-11-20 18:04:29] BET1: Unexpected value 00 received
 [2014-11-20 18:04:29] BET1: Unexpected value 00 received
 [2014-11-20 18:04:29] BET1: Unexpected value 00 received
 [2014-11-20 18:04:30] BET1: Unexpected value 00 received
 [2014-11-20 18:04:32] Accepted 090fd4db Diff 7.23K/4096 BET 1

 [2014-11-20 18:04:33] BET1: Unexpected value 00 received
 [2014-11-20 18:04:43] BET1: Unexpected value 00 received
 [2014-11-20 18:04:43] BET1: Unexpected value 00 received
 [2014-11-20 18:04:43] BET1: Unexpected value 00 received
 [2014-11-20 18:04:43] BET1: Unexpected value 00 received
 [2014-11-20 18:04:44] BET1: Unexpected value 00 received
 [2014-11-20 18:04:44] BET1: Unexpected value 00 received

It's been suggested that restarting the mining software (repeatedly) will eventually clear those up.  I've found that I have to restart cgminer between 5-10 times before it finally "takes."  I know that's not an amazing solution, but the devices seem to run pretty trouble-free once they're hashing...

Cheers.

nope restarting dosn't help

I notice that you have "BET1" listed as the device.  Are you using more than one USB UART controller on your system?

for a few min i have two of them plug into computer but no mater if it's one or two always this same error :/

That explains the log, then!  Which version of cgminer are you using?

4.6.0
https://mega.co.nz/#!NY1FQbqB!4HFdFED73LbtrdNLU9ixJ-3asjmI1jhwc-7Qik9_x3w
that one

Join the club.  I've tried almost everything to get this piece of crap to hash.  I can't even get a single board to hash.  I've tried 2 different urt adapters, various builds of cgminer, different r-pi, different PSU, different builds of minera, different white 3 wires.  I'm probably 20 hr into troubleshooting over the last week and still getting the BET0 Unexpected value 00 received.  Expect 0 help from ASICMiner.  And these things were 3 weeks late shipping.

Check my posts the things I've tried

My last hope is a block erupter controller coming tomorrow.


100% would not recommend buying.  AM failed terribly on this.

CrazyGuy and Canary have been great trying to help troubleshoot.  CrazyGuy has gone the extra 10 miles to help get it running.

i have be cotroller and if i will run it with him it's works but you can mining only in few pools :/

[TracerX]

i have be cotroller and if i will run it with him it's works but you can mining only in few pools :/

It sounds like everything you're doing should work.  Maybe it's time to try using BFGminer 4.10 as a proxy with your BE controller and see how that works.