So I've been scouring the forums, please forgive me if I missed the obvious answer.
This is the first bit of AM gear I've had recently, and I'm curious about the number of dupes I'm seeing on ghash.io. It averages out to about 6%, which seems a little high to me. I'm running a Block Erupter controller, although I should have the rPi running next week.
The machines are running 99.5% efficiency on the back end, and I've seen no PwrDns and the HWe is 0.1. Anyone else seeing similar results? I'm 30 minutes from the DC on the weekends, so I'm hesitant to reboot.
Let me know what you guys think!
Cheers.
Topic: [CLOSED] ASICMiner Prisma 1.4th/s - 1.47 BTC - page 17. (Read 49921 times)
Easy enough up and running Thanks Crazy Guy.
Update:
I think I am making progress. I took the first prisma and took off a problem hash board and inspected: some spots of flux stuck in the holes where the BE200 chips are mounted to the PCB, cleaned those up best I could and screwed it back down.
Fired up the hash boards one by one and I currently have it without any of the PwrDn counts on the controller.
Prisma #1 is now hashing great
On prisma #2 blade #4 it is getting PwrDn counts and not hashing, I will attempt the same procedure above here for it.
On prisma #3 blade #4 has not hashed yet and seems shorted somewhere I have not removed and inspected it yet.
I think I am making progress. I took the first prisma and took off a problem hash board and inspected: some spots of flux stuck in the holes where the BE200 chips are mounted to the PCB, cleaned those up best I could and screwed it back down.
Fired up the hash boards one by one and I currently have it without any of the PwrDn counts on the controller.
Prisma #1 is now hashing great
On prisma #2 blade #4 it is getting PwrDn counts and not hashing, I will attempt the same procedure above here for it.
On prisma #3 blade #4 has not hashed yet and seems shorted somewhere I have not removed and inspected it yet.
All usb adapters have been shipped!
RPI is still running strong for my 2 units. I forced a reboot to ensure the units starts mining automatically and all is well. With that said, I have no current reservations about running the Prisma on a Raspberry Pi.
RPI is still running strong for my 2 units. I forced a reboot to ensure the units starts mining automatically and all is well. With that said, I have no current reservations about running the Prisma on a Raspberry Pi.
Check the board for loose or missing screws. Also look for shorts. A big issue with the cubes was excessive Flux and sometimes solder flakes getting stuck to the board and shorting out compenents. I haven't seen this with the prisma/tube's yet, but worth giving a lookover.
Wow I should know better. Every screw was loose (literally all of of them). Been hashing now for 2 hours no spikes in HWe's and no board resets.
Wish I would have thought of that yesterday. Will keep you updated.
Damn...
EDIT: Well that was a premature celebration HWe just spiked and boards started resetting. The common denominator here is the controller there is no way this many boards are defective.
anyone that can post some help I got BE controller up and set to 240 plugged all wires in and started prisma but fan is on and I show no hashrate?
NVM had dip switches backwards thanks up and running cant wait for adapter to try pi with wifi
anyone that can post some help I got BE controller up and set to 240 plugged all wires in and started prisma but fan is on and I show no hashrate?
Update on the RPi. Miner uptime is now 8 hours. No issues or restarts.
Check the board for loose or missing screws. Also look for shorts. A big issue with the cubes was excessive Flux and sometimes solder flakes getting stuck to the board and shorting out compenents. I haven't seen this with the prisma/tube's yet, but worth giving a lookover.
@CrazyGuy The above post is exactly what I've been dealing with. I think it's the BEController as oppose to defective boards. Look at the previous image his first prisma in the chain has completely reset and look at the HWerror rates of the boards that are alive. Also he is missing all together board 12 which sometimes happens as well when boards start resetting.
I think I may have some problem hash boards with that last set 
Hashing fine for a few hours a little under but acceptable for sure then hashrate really dropped.
Isolated them one by one tried altering the way they are chained, two controllers, and two power sources.
One of the boards the row of large transistors gets so hot they will burn you just powered on without the controller, so I have it unplugged, but it will descend into ugliness anyhow like this picture:
gunna unplug it and fight it tomorrow
Hashing fine for a few hours a little under but acceptable for sure then hashrate really dropped.
Isolated them one by one tried altering the way they are chained, two controllers, and two power sources.
One of the boards the row of large transistors gets so hot they will burn you just powered on without the controller, so I have it unplugged, but it will descend into ugliness anyhow like this picture:
gunna unplug it and fight it tomorrow
Great job again.
Now is this with your fork or the main fork of Minera and cgminer?
Now is this with your fork or the main fork of Minera and cgminer?
First 2.5 hrs mining mining on the pi and 2 prismas. No reboots and running solid. Total hashrate display in minera is inaccurate. Device hash rate below is accurate and matches what I'm seeing poolside. I'll have to look at the source this weekend and see what's going on.
One thing I did notice is that ASICMiner's build of cgminer does not handle the frequency parameter . When passing "--bet-clk 23", I received a ton of errors: "BET0: Unexpected value 00 received". Starting with no parameters fixed the issue
One thing I did notice is that ASICMiner's build of cgminer does not handle the frequency parameter . When passing "--bet-clk 23", I received a ton of errors: "BET0: Unexpected value 00 received". Starting with no parameters fixed the issue
First 2.5 hrs mining mining on the pi and 2 prismas. No reboots and running solid. Total hashrate display in minera is inaccurate. Device hash rate below is accurate and matches what I'm seeing poolside. I'll have to look at the source this weekend and see what's going on.
One thing I did notice is that ASICMiner's build of cgminer does not handle the frequency parameter . When passing "--bet-clk 23", I received a ton of errors: "BET0: Unexpected value 00 received". Starting with no parameters fixed the issue
One thing I did notice is that ASICMiner's build of cgminer does not handle the frequency parameter . When passing "--bet-clk 23", I received a ton of errors: "BET0: Unexpected value 00 received". Starting with no parameters fixed the issue
What are these things?...
Naked flash drives?
Do these adapters work with the Tubes too? I'm looking to get a cheap Tube, would be nice to have it on USB as well.
Yes they do. I may have some used tubes up for sale soon. If anyone is interested, please PM me.
What are these things?...
Naked flash drives?
Do these adapters work with the Tubes too? I'm looking to get a cheap Tube, would be nice to have it on USB as well.
What are these things?...
I'll post some stats tonight. Group buy participants: if you haven't PM'ed me your preference on the adapters, please do so now.
I'll post some stats tonight. Group buy participants: if you haven't PM'ed me your preference on the adapters, please do so now.
Got my 3x more prisma in from CrazyGuy a few hours ago they'd be hashing @ 99% efficiency working to ROI 
Great little machines and CrazyGuy is easy, fast, honest, and reliable to work with. So refreshing to see a little integrity in this business.
Great little machines and CrazyGuy is easy, fast, honest, and reliable to work with. So refreshing to see a little integrity in this business.
Now that is great news!
Good job as always CG.
Good job as always CG.
The adapters are scheduled to be delivered today.
Anyone have an idea why Ghash.io is behaving like this? The black worker line (2nd line) is my Prisma, the other is a 1Th/s no name miner. I am on the Controller, would being in the RPI produce any different results? The miner itself is always running at 1.4Th/s so it must be Ghash.io?
SNIP
SNIP
I think Canary said he would not trust the Pi to run the Prisma's properly.
Anyone have an idea why Ghash.io is behaving like this? The black worker line (2nd line) is my Prisma, the other is a 1Th/s no name miner. I am on the Controller, would being in the RPI produce any different results? The miner itself is always running at 1.4Th/s so it must be Ghash.io?
Jump to: