Search content
Sort by
Showing 18 of 18 results by naituida
Re: Block Erupter Prisma (>=1.4 T/device, 0.75-0.78 W/G, <1 BTC/T, October Shipping)
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.
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.
Re: Block Erupter Prisma (>=1.4 T/device, 0.75-0.78 W/G, <1 BTC/T, October Shipping)
Finally got more prisma to debug!
Please checkout https://github.com/blockerupter/cgminer, I pushed my update of prisma driver to blockerupter's repo.
This update should fix board detection issues and many of the sync errors.
Please checkout https://github.com/blockerupter/cgminer, I pushed my update of prisma driver to blockerupter's repo.
This update should fix board detection issues and many of the sync errors.
Re: Block Erupter Prisma (>=1.4 T/device, 0.75-0.78 W/G, <1 BTC/T, October Shipping)
Is there anyone that can tell me what the pin layout of the uart is.
Which is GND/TXD/RXD?
Which is GND/TXD/RXD?
Code:
+----+ +--------+ +-----+
| | | | | |
| | | | | |
| | | | | |
| +-----+ +----+ |
| |
| |
| |
| |
+------------------------------+
| | | | | |
| | | | | |
| | | | | |
| +-----+ +----+ |
| |
| |
| |
| |
+------------------------------+
if we look at the port for data cable on board this way, from left to right: GND, TX, RX
Awesome thanks. Just to be certain that's left to right with the port facing me (fan facing me)?
Code:
RX
TX +-+-------------------------------------------------------------------------------------+
GND | | Data Port |
RX +-+ |
TX | | |
GND +-+ |
| |
| |
| |
| |
| |
| |
| |
+----+ |
| | Power |
+----+ |
| | |
+----+ |
+----+----------------------------------------------------------------------------------+
TX +-+-------------------------------------------------------------------------------------+
GND | | Data Port |
RX +-+ |
TX | | |
GND +-+ |
| |
| |
| |
| |
| |
| |
| |
+----+ |
| | Power |
+----+ |
| | |
+----+ |
+----+----------------------------------------------------------------------------------+
Re: Block Erupter Prisma (>=1.4 T/device, 0.75-0.78 W/G, <1 BTC/T, October Shipping)
Is there anyone that can tell me what the pin layout of the uart is.
Which is GND/TXD/RXD?
Which is GND/TXD/RXD?
Code:
+----+ +--------+ +-----+
| | | | | |
| | | | | |
| | | | | |
| +-----+ +----+ |
| |
| |
| |
| |
+------------------------------+
| | | | | |
| | | | | |
| | | | | |
| +-----+ +----+ |
| |
| |
| |
| |
+------------------------------+
if we look at the port for data cable on board this way, from left to right: GND, TX, RX
Re: Block Erupter Prisma (>=1.4 T/device, 0.75-0.78 W/G, <1 BTC/T, October Shipping)
A single USB controller can control up to 4 units (full Prisma with 4 boards). Detailed info of each board can be found with cgminer api.
Info in the OP says 8 devices = 32 units, same as with the Tube, because each hashing board has a 5 bit DIP switch = 32 different addresses.
As I tested, each prisma board would be identified as two boards (seems they purposely do this to make it compatible with ethernet controller). Also the 5th bit on switch is ignored by prisma board. So it's 16 prisma boards or 32 tube boards.
Re: Block Erupter Prisma (>=1.4 T/device, 0.75-0.78 W/G, <1 BTC/T, October Shipping)
ASICMINER has released their branch of cgminer: https://github.com/blockerupter/cgminer
This branch supports both Tube and Prisma, you'll need AM's USB adapter to connect to your USB port. A random CP2102X usb to uart adapter might work as well if you can customize the adpater by adding a pull resistor to the TXD.
How to build:
There's also a win32 binary here:
https://mega.co.nz/#!NY1FQbqB!4HFdFED73LbtrdNLU9ixJ-3asjmI1jhwc-7Qik9_x3w
How to run:
No extra command line parameters are needed. The Tube or Prisma will be identified as "BET" in cgminer.
This branch supports both Tube and Prisma, you'll need AM's USB adapter to connect to your USB port. A random CP2102X usb to uart adapter might work as well if you can customize the adpater by adding a pull resistor to the TXD.
How to build:
- ./autogen.sh
- ./configure --enable-blockerupter
- make
There's also a win32 binary here:
https://mega.co.nz/#!NY1FQbqB!4HFdFED73LbtrdNLU9ixJ-3asjmI1jhwc-7Qik9_x3w
How to run:
No extra command line parameters are needed. The Tube or Prisma will be identified as "BET" in cgminer.
Code:
./cgminer -o YOUR_POOL -u WORKER -p PASSWORD
can I use this with any mining pool ? like nicehash ?
Said yes before, but there turns out many "job not found" errors which causes hash rate loss after long time test.
Now I realize that nicehash has its own modification with stratum protocol, it seems either we patch official cgminer or we fork from nicehash's own branch and add driver for PRISMA.
Re: Block Erupter Prisma (>=1.4 T/device, 0.75-0.78 W/G, <1 BTC/T, October Shipping)
ASICMINER has released their branch of cgminer: https://github.com/blockerupter/cgminer
This branch supports both Tube and Prisma, you'll need AM's USB adapter to connect to your USB port. A random CP2102X usb to uart adapter might work as well if you can customize the adpater by adding a pull resistor to the TXD.
How to build:
There's also a win32 binary here:
https://mega.co.nz/#!NY1FQbqB!4HFdFED73LbtrdNLU9ixJ-3asjmI1jhwc-7Qik9_x3w
How to run:
No extra command line parameters are needed. The Tube or Prisma will be identified as "BET" in cgminer.
This branch supports both Tube and Prisma, you'll need AM's USB adapter to connect to your USB port. A random CP2102X usb to uart adapter might work as well if you can customize the adpater by adding a pull resistor to the TXD.
How to build:
- ./autogen.sh
- ./configure --enable-blockerupter
- make
There's also a win32 binary here:
https://mega.co.nz/#!NY1FQbqB!4HFdFED73LbtrdNLU9ixJ-3asjmI1jhwc-7Qik9_x3w
How to run:
No extra command line parameters are needed. The Tube or Prisma will be identified as "BET" in cgminer.
Code:
./cgminer -o YOUR_POOL -u WORKER -p PASSWORD
can I use this with any mining pool ? like nicehash ?
Yes. cgminer is handling all the stratum part.
Re: Block Erupter Prisma (>=1.4 T/device, 0.75-0.78 W/G, <1 BTC/T, October Shipping)
ASICMINER has released their branch of cgminer: https://github.com/blockerupter/cgminer
This branch supports both Tube and Prisma, you'll need AM's USB adapter to connect to your USB port. A random CP2102X usb to uart adapter might work as well if you can customize the adpater by adding a pull resistor to the TXD.
How to build:
There's also a win32 binary here:
https://mega.co.nz/#!NY1FQbqB!4HFdFED73LbtrdNLU9ixJ-3asjmI1jhwc-7Qik9_x3w
How to run:
No extra command line parameters are needed. The Tube or Prisma will be identified as "BET" in cgminer.
This branch supports both Tube and Prisma, you'll need AM's USB adapter to connect to your USB port. A random CP2102X usb to uart adapter might work as well if you can customize the adpater by adding a pull resistor to the TXD.
How to build:
- ./autogen.sh
- ./configure --enable-blockerupter
- make
There's also a win32 binary here:
https://mega.co.nz/#!NY1FQbqB!4HFdFED73LbtrdNLU9ixJ-3asjmI1jhwc-7Qik9_x3w
How to run:
No extra command line parameters are needed. The Tube or Prisma will be identified as "BET" in cgminer.
Code:
./cgminer -o YOUR_POOL -u WORKER -p PASSWORD
Utility = Shares per minute ( Utility*4.29/60 = Prf 
)
PwrDn = Power Down ( Chip with "." status )
ForceLP(Long Poll) = Force the board to accept a new job ( the board is doing nTime rolling by itself )
ReClock = Adjust time difference between local and pool
These two buttons are better removed... no one actually need them.
Real_LP = Guess should be the actual forced LP, but the number seems too small here...
RS = ReSync ( indicates errors on data cable)
RC = ReConnect ( reconnect to the pool )
Cmd/s and Ans/s are both looks like stats for the communications between boards and controller
RollNtime[ s] = How many seconds the board should change on nTime ( bigger means less communications to controller, default value should be OK)
WakeUp period[ s] =
Normal/Smart[0/1] = Firmware version would change, but I can't see any difference in hash rate
)PwrDn = Power Down ( Chip with "." status )
ForceLP(Long Poll) = Force the board to accept a new job ( the board is doing nTime rolling by itself )
ReClock = Adjust time difference between local and pool
These two buttons are better removed... no one actually need them.
Real_LP = Guess should be the actual forced LP, but the number seems too small here...
RS = ReSync ( indicates errors on data cable)
RC = ReConnect ( reconnect to the pool )
Cmd/s and Ans/s are both looks like stats for the communications between boards and controller
RollNtime[ s] = How many seconds the board should change on nTime ( bigger means less communications to controller, default value should be OK)
WakeUp period[ s] =
Normal/Smart[0/1] = Firmware version would change, but I can't see any difference in hash rate
A, B, and C are almost certainly different addresses in the same wallet, and belong to one person. But in case you're wondering, clicking "Show scripts & coinbase" in blockchain.info will show you exactly how much came from each address.
We can find how much BTC came from A, but can we tell how much does A want to send to D and how much to E?
Question rises from examples like :
http://blockchain.info/tx/cc4379b54e277492893a6b81a6a838b6bf308caa2ccc02720579277ac50dcf47
and
http://blockchain.info/tx/ed758629beeeac05bb61ffbadcb5a126a806c903b60c2f02489f56b6ba6d73d4
The first link is an example showing trasaction from multiple senders and at most two receivers ( refering from Ch 9 in orginal bitcoin paper).
Suppose we have a transaction as A and B and C send total amount of 5 bitcoins to D and E. From the transaction, we can tell how many
bitcoins sent by A or B or C and how many received by D or E. But how can we tell how many bitcoins sent from A to D?
The second link is an example of transaction from single sender to multiple receivers(more than 2) which is not shown in origianl paper.
Is this introduced by newer version in bitcoin?
Thx!
http://blockchain.info/tx/cc4379b54e277492893a6b81a6a838b6bf308caa2ccc02720579277ac50dcf47
and
http://blockchain.info/tx/ed758629beeeac05bb61ffbadcb5a126a806c903b60c2f02489f56b6ba6d73d4
The first link is an example showing trasaction from multiple senders and at most two receivers ( refering from Ch 9 in orginal bitcoin paper).
Suppose we have a transaction as A and B and C send total amount of 5 bitcoins to D and E. From the transaction, we can tell how many
bitcoins sent by A or B or C and how many received by D or E. But how can we tell how many bitcoins sent from A to D?
The second link is an example of transaction from single sender to multiple receivers(more than 2) which is not shown in origianl paper.
Is this introduced by newer version in bitcoin?
Thx!