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

Swimmer63

legendary

Activity: 1593

Merit: 1004

This is the email they told us to use. I got a response right away when I emailed a few weeks ago.

[email protected]

LordPaco

full member

Activity: 120

Merit: 100

I have still yet to receive any response from AsicMiner in regards to my bad boards, out of 32 boards, only 18 are working, or 56% of the paid hashrate. Sad

bigredbutton

full member

Activity: 209

Merit: 100

IF/when I determine a board is not hashing then what? Does ASICMiner offer any sort of RMA? I bought the unit via Canary's GB.

Blazed

legendary

Activity: 2128

Merit: 1119

Quote from: bigredbutton on November 21, 2014, 09:31:20 AM

So after about a day or two of hashing at 1300-1400GH something happened and now my Prisma only reaches about 1000GH poolside.

I believe one of the boards went out? or isn't hashing for some reason? I didn't make any changes to my system so I'm not sure how to diagnose the problem. PSU is good and everything checks out, boards switches are correct etc. Running CrazyGuy's version of cgAM on a RPi.

The Kill-a-watt meter fluctuates from 950-1200 Watts. Sort of reminds me of my Titan with the failing die. Hopefully that is not the situation. Any ideas on how to trouble shoot?

I would try running 1 board at a time and find the bad one that way...or run 3 at a time unhooking a different one each time.

bigredbutton

full member

Activity: 209

Merit: 100

So after about a day or two of hashing at 1300-1400GH something happened and now my Prisma only reaches about 1000GH poolside.

I believe one of the boards went out? or isn't hashing for some reason? I didn't make any changes to my system so I'm not sure how to diagnose the problem. PSU is good and everything checks out, boards switches are correct etc. Running CrazyGuy's version of cgAM on a RPi.

The Kill-a-watt meter fluctuates from 950-1200 Watts. Sort of reminds me of my Titan with the failing die. Hopefully that is not the situation. Any ideas on how to trouble shoot?

praeluceo

full member

Activity: 123

Merit: 100

Quote from: novak@gekkoscience on November 20, 2014, 04:27:56 PM

Quote from: TheRealSteve on November 18, 2014, 03:38:00 PM

Quote from: praeluceo on November 18, 2014, 03:28:26 PM

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:

Quote from: novak@gekkoscience on November 13, 2014, 09:43:35 PM

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

YMMV

Probably worth pointing out that someone else followed those steps and got a generic CP2102 adapter working. Looking at tubes the reason the 1K resistor is needed is that the controller on the tube board connects to the UART via a 7407, which is an open drain buffer.

https://bitcointalksearch.org/topic/prismatube-cp2102-mod-working-865503

Thanks for the link! That's a good explanation too, the resistor is good to know about. Now I have a project for the weekend! Gotta rummage through my parts bins to see if I even have the CP2102 adapter.

novak@gekkoscience

full member

Activity: 173

Merit: 100

Quote from: TheRealSteve on November 18, 2014, 03:38:00 PM

Quote from: praeluceo on November 18, 2014, 03:28:26 PM

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:

Quote from: novak@gekkoscience on November 13, 2014, 09:43:35 PM

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

YMMV

Probably worth pointing out that someone else followed those steps and got a generic CP2102 adapter working. Looking at tubes the reason the 1K resistor is needed is that the controller on the tube board connects to the UART via a 7407, which is an open drain buffer.

https://bitcointalksearch.org/topic/prismatube-cp2102-mod-working-865503

--
novak

TracerX

hero member

Activity: 918

Merit: 1002

Quote from: Scorch on November 20, 2014, 03:40:59 PM

Quote from: TracerX on November 20, 2014, 03:34:20 PM

Quote from: Scorch on November 20, 2014, 03:10:57 PM

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.

now i'm waiting for rpi and i will try to have fun with it ;p

PM me when you get your rpi and I'll make sure you have everything you need!

Scorch

newbie

Activity: 9

Merit: 0

Quote from: TracerX on November 20, 2014, 03:34:20 PM

Quote from: Scorch on November 20, 2014, 03:10:57 PM

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.

now i'm waiting for rpi and i will try to have fun with it ;p

TracerX

hero member

Activity: 918

Merit: 1002

Quote from: Scorch on November 20, 2014, 03:10:57 PM

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.

Scorch

newbie

Activity: 9

Merit: 0

Quote from: TracerX on November 20, 2014, 02:57:28 PM

Quote from: Scorch on November 20, 2014, 02:55:39 PM

Quote from: TracerX on November 20, 2014, 02:50:36 PM

Quote from: Scorch on November 20, 2014, 02:15:46 PM

Quote from: TracerX on November 20, 2014, 01:57:30 PM

Quote from: Scorch on November 20, 2014, 01:11:13 PM

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

Quote

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

Chris_Sabian

legendary

Activity: 896

Merit: 1001

Quote from: Scorch on November 20, 2014, 01:11:13 PM

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.

TracerX

hero member

Activity: 918

Merit: 1002

Quote from: Scorch on November 20, 2014, 02:55:39 PM

Quote from: TracerX on November 20, 2014, 02:50:36 PM

Quote from: Scorch on November 20, 2014, 02:15:46 PM

Quote from: TracerX on November 20, 2014, 01:57:30 PM

Quote from: Scorch on November 20, 2014, 01:11:13 PM

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?

Scorch

newbie

Activity: 9

Merit: 0

Quote from: TracerX on November 20, 2014, 02:50:36 PM

Quote from: Scorch on November 20, 2014, 02:15:46 PM

Quote from: TracerX on November 20, 2014, 01:57:30 PM

Quote from: Scorch on November 20, 2014, 01:11:13 PM

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

hero member

Activity: 918

Merit: 1002

Quote from: Scorch on November 20, 2014, 02:15:46 PM

Quote from: TracerX on November 20, 2014, 01:57:30 PM

Quote from: Scorch on November 20, 2014, 01:11:13 PM

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?

TracerX

hero member

Activity: 918

Merit: 1002

Quote from: LordPaco on November 20, 2014, 02:37:11 PM

Quote from: TracerX on November 20, 2014, 01:57:30 PM

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 Sad

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....

LordPaco

full member

Activity: 120

Merit: 100

Quote from: TracerX on November 20, 2014, 01:57:30 PM

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 Sad

Scorch

newbie

Activity: 9

Merit: 0

Quote from: TracerX on November 20, 2014, 01:57:30 PM

Quote from: Scorch on November 20, 2014, 01:11:13 PM

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

TracerX

hero member

Activity: 918

Merit: 1002

Quote from: Scorch on November 20, 2014, 01:11:13 PM

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

newbie

Activity: 9

Merit: 0

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

Topic: Block Erupter Prisma (>=1.4 T/device, 0.75-0.78 W/G, <1 BTC/T, October Shipping) - page 8. (Read 107983 times)