it's a 2.5/5.5mm plug.
Hey, that's the same as BFL's box. Now Cablesaurus really needs to create proper 6-pin molex to barrel plug adapters. He could make a mint.
Topic: FPGA development board "Icarus" - DisContinued/ important announcement - page 17. (Read 207288 times)
March 10, 2012, 08:19:10 PM
March 10, 2012, 08:16:43 PM
i repeat, test in progress. will not answer any email until bulk orders finish (3/11-13).
Help us! It's the Flying Spaghetti Monster!
Flying Spaghetti Monster gets 30TH/s @ 5W though...
March 10, 2012, 08:02:40 PM
it's a 2.5/5.5mm plug.
Sorry you're right, I did not double check before I spoke
Quote from: rjk
Hey, that's the same as BFL's box. Now Cablesaurus really needs to create proper 6-pin molex to barrel plug adapters. He could make a mint.
You're right. I for one would buy some. For large fpga farms using a 80 Plus Gold power supply (or better Platinum rated - but more expensive) is the way to go.
March 10, 2012, 07:49:27 PM
it's a 2.5/5.5mm plug.
Hey, that's the same as BFL's box. Now Cablesaurus really needs to create proper 6-pin molex to barrel plug adapters. He could make a mint. March 10, 2012, 04:32:12 PM
I really like your work, ngzhang.
Now I have to wait for eldentyrell to make progress to decide where my money goes next....
March 10, 2012, 03:21:03 PM
it's a 2.5/5.5mm plug.
March 10, 2012, 01:56:31 PM
Wow ngzhang, that's pure geek heaven there (Icarus towers)!!!
On a different note, is anyone selling premade ATX power supply leads to power these boards? (ie with the correct 2.1 x 5.5 mm barrel connector). I saw a guide on ztex's site but it would be more convenient to buy some instead of spending hours making them.
On a different note, is anyone selling premade ATX power supply leads to power these boards? (ie with the correct 2.1 x 5.5 mm barrel connector). I saw a guide on ztex's site but it would be more convenient to buy some instead of spending hours making them.
March 10, 2012, 12:30:09 PM
heh! where is the new one 
?
?https://github.com/TheSeven/Modular-Python-Bitcoin-Miner/tree/testing
Completely untested on Icarus though. Feel free to contact me on IRC (#mpbm on irc.freenode.net) if you need help setting it up.
Code:
2012-03-11 01:27:00.423000 [100]: Untitled Icarus worker: Traceback (most recent call last):
2012-03-11 01:27:00.423000 [100]: File "C:\TheSeven-Modular-Python-Bitcoin-Miner-8c43ba7\modules\theseven\icarus\icarusworker.py", line 208, in main
2012-03-11 01:27:00.423000 [100]: interval = min(60, 2**32 / 1000000. / self.stats.mhps)
2012-03-11 01:27:00.423000 [100]: ZeroDivisionError: float division by zero
2012-03-11 01:27:00.423000 [100]:
2012-03-11 01:27:00.453000 [500]: BTCGuild (donation): Got 1 jobs
2012-03-11 01:27:00.453000 [300]: BTCGuild (donation): New block detected
2012-03-11 01:27:01.083000 [500]: Eligius (donation): Got 120 jobs
2012-03-11 01:27:02.912000 [300]: Untitled Icarus worker: Running at 0.000000 MH/s
2012-03-11 01:27:02.912000 [100]: Untitled Icarus worker: Traceback (most recent call last):
2012-03-11 01:27:02.912000 [100]: File "C:\TheSeven-Modular-Python-Bitcoin-Miner-8c43ba7\modules\theseven\icarus\icarusworker.py", line 208, in main
2012-03-11 01:27:02.912000 [100]: interval = min(60, 2**32 / 1000000. / self.stats.mhps)
2012-03-11 01:27:02.912000 [100]: ZeroDivisionError: float division by zero
2012-03-11 01:27:02.912000 [100]:
2012-03-11 01:27:05.558000 [300]: Untitled Icarus worker: Running at 0.000000 MH/s
2012-03-11 01:27:05.558000 [100]: Untitled Icarus worker: Traceback (most recent call last):
2012-03-11 01:27:05.558000 [100]: File "C:\TheSeven-Modular-Python-Bitcoin-Miner-8c43ba7\modules\theseven\icarus\icarusworker.py", line 208, in main
2012-03-11 01:27:05.558000 [100]: interval = min(60, 2**32 / 1000000. / self.stats.mhps)
2012-03-11 01:27:05.558000 [100]: ZeroDivisionError: float division by zero
2012-03-11 01:27:05.558000 [100]:
2012-03-11 01:27:08.008000 [300]: Untitled Icarus worker: Running at 0.000000 MH/s
2012-03-11 01:27:08.008000 [100]: Untitled Icarus worker: Traceback (most recent call last):
2012-03-11 01:27:08.008000 [100]: File "C:\TheSeven-Modular-Python-Bitcoin-Miner-8c43ba7\modules\theseven\icarus\icarusworker.py", line 208, in main
2012-03-11 01:27:08.008000 [100]: interval = min(60, 2**32 / 1000000. / self.stats.mhps)
2012-03-11 01:27:08.008000 [100]: ZeroDivisionError: float division by zero
2012-03-11 01:27:08.008000 [100]:
2012-03-11 01:27:10.513000 [300]: Untitled Icarus worker: Running at 0.000000 MH/s
2012-03-11 01:27:10.513000 [100]: Untitled Icarus worker: Traceback (most recent call last):
2012-03-11 01:27:10.513000 [100]: File "C:\TheSeven-Modular-Python-Bitcoin-Miner-8c43ba7\modules\theseven\icarus\icarusworker.py", line 208, in main
2012-03-11 01:27:10.513000 [100]: interval = min(60, 2**32 / 1000000. / self.stats.mhps)
2012-03-11 01:27:10.513000 [100]: ZeroDivisionError: float division by zero
2012-03-11 01:27:10.513000 [100]:
2012-03-11 01:27:13.015000 [300]: Untitled Icarus worker: Running at 0.000000 MH/s
2012-03-11 01:27:13.015000 [100]: Untitled Icarus worker: Traceback (most recent call last):
2012-03-11 01:27:13.015000 [100]: File "C:\TheSeven-Modular-Python-Bitcoin-Miner-8c43ba7\modules\theseven\icarus\icarusworker.py", line 208, in main
2012-03-11 01:27:13.015000 [100]: interval = min(60, 2**32 / 1000000. / self.stats.mhps)
2012-03-11 01:27:13.015000 [100]: ZeroDivisionError: float division by zero
2012-03-11 01:27:13.015000 [100]:
2012-03-11 01:27:44.516000 [300]: Untitled Icarus worker: Running at 0.000000 MH/s
2012-03-11 01:27:44.516000 [100]: Untitled Icarus worker: Traceback (most recent call last):
2012-03-11 01:27:44.516000 [100]: File "C:\TheSeven-Modular-Python-Bitcoin-Miner-8c43ba7\modules\theseven\icarus\icarusworker.py", line 208, in main
2012-03-11 01:27:44.516000 [100]: interval = min(60, 2**32 / 1000000. / self.stats.mhps)
2012-03-11 01:27:44.516000 [100]: ZeroDivisionError: float division by zero
2012-03-11 01:27:44.516000 [100]:
?
March 10, 2012, 12:10:51 PM
heh! where is the new one ?
?https://github.com/TheSeven/Modular-Python-Bitcoin-Miner/tree/testing
Completely untested on Icarus though. Feel free to contact me on IRC (#mpbm on irc.freenode.net) if you need help setting it up.
March 10, 2012, 12:05:21 PM
wow, 13 port hubs? where did you get those?
And it would be really awesome if you could test the new MPBM on such a huge cluster
My board didn't arrive yet, so I'm not sure if the ported module even works at all right now.
(Seems to be stuck at customs - grrr.)
And it would be really awesome if you could test the new MPBM on such a huge cluster
My board didn't arrive yet, so I'm not sure if the ported module even works at all right now.
(Seems to be stuck at customs - grrr.)
i must say...
Germany's customs is ****.
but , your MBPM is solid stable. like all Made in Germany stuff .
about the HUB:
here:
http://www.360buy.com/product/511117.html
very stable. with a 4A 5V adapter. about 24$/ea
Heh, calling that crappy garbled up display stable? You really need to try the new one
And I bet that hub is two cascaded 7 port hubs internally.
heh! where is the new one
? March 10, 2012, 12:03:22 PM
wow, 13 port hubs? where did you get those?
And it would be really awesome if you could test the new MPBM on such a huge cluster
My board didn't arrive yet, so I'm not sure if the ported module even works at all right now.
(Seems to be stuck at customs - grrr.)
And it would be really awesome if you could test the new MPBM on such a huge cluster
My board didn't arrive yet, so I'm not sure if the ported module even works at all right now.
(Seems to be stuck at customs - grrr.)
i must say...
Germany's customs is ****.
but , your MBPM is solid stable. like all Made in Germany stuff .
about the HUB:
here:
http://www.360buy.com/product/511117.html
very stable. with a 4A 5V adapter. about 24$/ea
Heh, calling that crappy garbled up display stable? You really need to try the new one
And I bet that hub is two cascaded 7 port hubs internally.
March 10, 2012, 11:58:14 AM
wow, 13 port hubs? where did you get those?
And it would be really awesome if you could test the new MPBM on such a huge cluster
My board didn't arrive yet, so I'm not sure if the ported module even works at all right now.
(Seems to be stuck at customs - grrr.)
And it would be really awesome if you could test the new MPBM on such a huge cluster
My board didn't arrive yet, so I'm not sure if the ported module even works at all right now.
(Seems to be stuck at customs - grrr.)
i must say...
Germany's customs is ****.
but , your MBPM is solid stable. like all Made in Germany stuff .
about the HUB:
here:
http://www.360buy.com/product/511117.html
very stable. with a 4A 5V adapter. about 24$/ea
March 10, 2012, 11:40:06 AM
wow, 13 port hubs? where did you get those?
And it would be really awesome if you could test the new MPBM on such a huge cluster
My board didn't arrive yet, so I'm not sure if the ported module even works at all right now.
(Seems to be stuck at customs - grrr.)
And it would be really awesome if you could test the new MPBM on such a huge cluster
My board didn't arrive yet, so I'm not sure if the ported module even works at all right now.
(Seems to be stuck at customs - grrr.)
March 10, 2012, 10:46:22 AM
ngzhangs rig towers... i'm glad that they sell so well. A very good product you have there Zhang. March 10, 2012, 10:34:22 AM
i repeat, test in progress. will not answer any email until bulk orders finish (3/11-13).
March 10, 2012, 06:41:58 AM
Not sure if you meant this, but a Hardware Error is simple - it's when the value returned was no good
(and cgminer keeps track of that also)
So what I meant was each time a bad share was returned you simply step the clock down as small as possible.
As I've mentioned before - I've had zero HW errors since I started mining with my 2 Icarus.
That's true, but ztex does more in this area. They don't just check difficulty 1 nonces, but rather the current nonce the FPGA is working on every couple of milliseconds. That way they can judge a lot better whether an invalid was just bad luck (some single event glitch) or whether that chip is being constantly overloaded.(and cgminer keeps track of that also)
So what I meant was each time a bad share was returned you simply step the clock down as small as possible.
As I've mentioned before - I've had zero HW errors since I started mining with my 2 Icarus.
Still zero HW errors - 7 days
It certainly wouldn't bother me in the least if it was 1 or 2 MHz below the failure point since I would hazard a guess that the life of the FPGA would not be very good if it was constantly at borderline failure.
(from what Energizer posted the current setting is obviously further below the limit than 1 or 2)
ngzhang: is that a difficult thing to consider? (Being able to adjust the MHz clock speed with a command?)
in my plan, a similar feature maybe add to next version of bitsteam: adjust frequency full-automatic.
March 10, 2012, 05:49:40 AM
Not sure if you meant this, but a Hardware Error is simple - it's when the value returned was no good
(and cgminer keeps track of that also)
So what I meant was each time a bad share was returned you simply step the clock down as small as possible.
As I've mentioned before - I've had zero HW errors since I started mining with my 2 Icarus.
That's true, but ztex does more in this area. They don't just check difficulty 1 nonces, but rather the current nonce the FPGA is working on every couple of milliseconds. That way they can judge a lot better whether an invalid was just bad luck (some single event glitch) or whether that chip is being constantly overloaded.(and cgminer keeps track of that also)
So what I meant was each time a bad share was returned you simply step the clock down as small as possible.
As I've mentioned before - I've had zero HW errors since I started mining with my 2 Icarus.
Still zero HW errors - 7 days
It certainly wouldn't bother me in the least if it was 1 or 2 MHz below the failure point since I would hazard a guess that the life of the FPGA would not be very good if it was constantly at borderline failure.
(from what Energizer posted the current setting is obviously further below the limit than 1 or 2)
ngzhang: is that a difficult thing to consider? (Being able to adjust the MHz clock speed with a command?)
March 10, 2012, 05:35:50 AM
Not sure if you meant this, but a Hardware Error is simple - it's when the value returned was no good
(and cgminer keeps track of that also)
So what I meant was each time a bad share was returned you simply step the clock down as small as possible.
As I've mentioned before - I've had zero HW errors since I started mining with my 2 Icarus.
That's true, but ztex does more in this area. They don't just check difficulty 1 nonces, but rather the current nonce the FPGA is working on every couple of milliseconds. That way they can judge a lot better whether an invalid was just bad luck (some single event glitch) or whether that chip is being constantly overloaded. (and cgminer keeps track of that also)
So what I meant was each time a bad share was returned you simply step the clock down as small as possible.
As I've mentioned before - I've had zero HW errors since I started mining with my 2 Icarus.
March 10, 2012, 04:39:38 AM
Lytro pic of my Icarus miner: https://bitcointalksearch.org/topic/taking-lytro-pictures-of-my-fpgas-68115
March 10, 2012, 02:17:01 AM
for those of your that have the boards, do they come with iron rods so you can stack them?
Jump to: