Bitcoin Forum
December 10, 2016, 09:07:08 AM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 [27] 28 29 30 31 32 33 »
  Print  
Author Topic: BTCMiner - Open Source Bitcoin Miner for ZTEX FPGA Boards, 215 MH/s on LX150  (Read 153839 times)
ztex
Donator
Sr. Member
*
Offline Offline

Activity: 367

ZTEX FPGA Boards


View Profile WWW
October 01, 2012, 08:10:59 AM
 #521

If Inaba means that BTCminer does not support difficulty >1 checking he is right. This is obsolete because it is done by the bitcoin server / pool.

You probably cannot be more wrong with this. All pools were working with diff1 shares for almost two years, but with rising hashrates of miners, submitting diff1 shares is wasting of resources - too much traffic and pool load for no reason. So all modern pools are slowly implementing dynamic difficulty for their workers. Submitting low-diff shares to the pool may be considered as a flooding and may be a reason for ban.

Please add checking difficulty for next release, it is literally five lines of code.

At difficulty=1 the get-work frequency is approximately twice as high as the submit-work frequency. I hope this is not considered as flooding too.

1481360828
Hero Member
*
Offline Offline

Posts: 1481360828

View Profile Personal Message (Offline)

Ignore
1481360828
Reply with quote  #2

1481360828
Report to moderator
1481360828
Hero Member
*
Offline Offline

Posts: 1481360828

View Profile Personal Message (Offline)

Ignore
1481360828
Reply with quote  #2

1481360828
Report to moderator
1481360828
Hero Member
*
Offline Offline

Posts: 1481360828

View Profile Personal Message (Offline)

Ignore
1481360828
Reply with quote  #2

1481360828
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
ztex
Donator
Sr. Member
*
Offline Offline

Activity: 367

ZTEX FPGA Boards


View Profile WWW
October 01, 2012, 08:24:42 AM
 #522

Check the PSU. They often die slowly / become unstable over time if they run permanently  at high temperatures (liquid electrolytic capacitors).

What effect does a dying or unstable PSU have? Dropping voltage, interruptions, anything else?


Liquid electrolytic capacitors loose their capacity over the time if they run permanently at high temperatures.  This causes voltage drops or interruptions at the load step after configuration. Possible effects are:

* Full loss of configuration ==> bitstream upload errors
* Partial loss of configuration ==> FPGA delivers wrong results ==> dowclocking
* device disappears from the USB if PSU interrupts (e.g. due to undervoltage or overload protection)

The same effects occur is PSU is to weak or output capacitance of PSU us to small.

slush
Legendary
*
Offline Offline

Activity: 1358



View Profile WWW
October 01, 2012, 11:30:41 AM
 #523

At difficulty=1 the get-work frequency is approximately twice as high as the submit-work frequency. I hope this is not considered as flooding too.

Ok, getwork is slowly going to die. I'm not sure if you're aware of Stratum or GBT, but there are no "getwork requests" in these proposals at all. And with faster miners (or big mining operations based on ZTEX), submitting diff1 shares really may look like flooding. Where's the sense of sending 10 diff1 submits per second?

rupy
Hero Member
*****
Offline Offline

Activity: 724



View Profile
October 03, 2012, 01:45:37 PM
 #524

ztex any plans for stratum for BTCMiner?

BANKBOOK GWT Wallet & no-FIAT Billing API
BTC 14xr5Q1j61A1eA6Mrs5MRhUmYZKboY8iq2 | Vanillacoin FPGA Miner
ztex
Donator
Sr. Member
*
Offline Offline

Activity: 367

ZTEX FPGA Boards


View Profile WWW
October 04, 2012, 08:28:49 AM
 #525

ztex any plans for stratum for BTCMiner?

The bandwidth requirement of your ZTEX cluster is a few hundred bytes per second. Your Internet connection should be able to handle this.

Implementation is not planned within the next release (but maybe later).




deeplink
Hero Member
*****
Offline Offline

Activity: 602


In cryptography we trust


View Profile
October 04, 2012, 08:39:13 AM
 #526

ztex any plans for stratum for BTCMiner?

The bandwidth requirement of your ZTEX cluster is a few hundred bytes per second. Your Internet connection should be able to handle this.

Implementation is not planned within the next release (but maybe later).


In the meantime you could use slush's Stratum mining proxy.
rupy
Hero Member
*****
Offline Offline

Activity: 724



View Profile
October 04, 2012, 10:32:38 AM
 #527

@ztex its not about bandwidth but stales...
@deeplink thanks!

BANKBOOK GWT Wallet & no-FIAT Billing API
BTC 14xr5Q1j61A1eA6Mrs5MRhUmYZKboY8iq2 | Vanillacoin FPGA Miner
Nachtwind
Hero Member
*****
Offline Offline

Activity: 700



View Profile
October 09, 2012, 09:01:16 AM
 #528

Hi,
after testing the Ztex 1.15x on CGMiner (and really not liking the experience.. unfortunately) i tried to get back on BTCMiner but i have a problem:

Code:
C:\ztex>java -cp ZtexBTCMiner-120703.jar BTCMiner  -host "http://de.btcguild.com:8332" -u Nachtwind_fpga -p yup -f ztex_ufm1_15d4.ihx
Error: Device lost after uploading Firmware: No new device found

I cant find a way to revive it for BTCMiner... CGMiner still works "fine" (as in the limits set by CGMiner) though..

Any ideas?
Turbor
Legendary
*
Offline Offline

Activity: 1008


BitMinter


View Profile WWW
October 09, 2012, 10:37:19 AM
 #529

Hi,
after testing the Ztex 1.15x on CGMiner (and really not liking the experience.. unfortunately) i tried to get back on BTCMiner but i have a problem:

Code:
C:\ztex>java -cp ZtexBTCMiner-120703.jar BTCMiner  -host "http://de.btcguild.com:8332" -u Nachtwind_fpga -p yup -f ztex_ufm1_15d4.ihx
Error: Device lost after uploading Firmware: No new device found

I cant find a way to revive it for BTCMiner... CGMiner still works "fine" (as in the limits set by CGMiner) though..

Any ideas?

Did you change the usb driver back ? IIRC you can do that with Zadig.

Nachtwind
Hero Member
*****
Offline Offline

Activity: 700



View Profile
October 09, 2012, 10:42:18 AM
 #530

Hi,
after testing the Ztex 1.15x on CGMiner (and really not liking the experience.. unfortunately) i tried to get back on BTCMiner but i have a problem:

Code:
C:\ztex>java -cp ZtexBTCMiner-120703.jar BTCMiner  -host "http://de.btcguild.com:8332" -u Nachtwind_fpga -p yup -f ztex_ufm1_15d4.ihx
Error: Device lost after uploading Firmware: No new device found

I cant find a way to revive it for BTCMiner... CGMiner still works "fine" (as in the limits set by CGMiner) though..

Any ideas?

Did you change the usb driver back ? IIRC you can do that with Zadig.

*edit*
Ok, changing the driver to libusb did the trick. Thanks.
Nachtwind
Hero Member
*****
Offline Offline

Activity: 700



View Profile
October 15, 2012, 09:51:45 AM
 #531

By the way... any chance to see Stratum soon in BTCMiner?
ztex
Donator
Sr. Member
*
Offline Offline

Activity: 367

ZTEX FPGA Boards


View Profile WWW
October 17, 2012, 02:14:55 PM
 #532

By the way... any chance to see Stratum soon in BTCMiner?

See https://bitcointalk.org/index.php?topic=40047.msg1244118#msg1244118

ztex
Donator
Sr. Member
*
Offline Offline

Activity: 367

ZTEX FPGA Boards


View Profile WWW
October 17, 2012, 02:20:51 PM
 #533

A new testing version has been released.
Binaries: http://www.ztex.de/btcminer/ZtexBTCMiner-121017.jar
Source: http://www.ztex.de/btcminer/ZtexBTCMiner-121017.tar.bz2

New features are:

    * Temperature sensor support for USB-FPGA Modules 1.15y rev. 2 (temperature limit is set using the paramter -t)
    * X-Mining-extensions: midstate, submitold
    * Target checking, must be enabled using -tc
    * MAC address printed at -i

thph
Sr. Member
****
Offline Offline

Activity: 333



View Profile
October 18, 2012, 02:48:30 PM
 #534

Total hash rate: 3398,6 MH/s
Total submitted hash rate: 3418,7 MH/s
 --------
works great - i have arround 200 MH/s more submitted shares with 2 quads.
2 questions -
how to set the temp option exactly and - which temp range is ok for the quads
narousberg
Hero Member
*****
Offline Offline

Activity: 714



View Profile
October 18, 2012, 03:21:02 PM
 #535

Total hash rate: 3398,6 MH/s
Total submitted hash rate: 3418,7 MH/s
 --------
works great - i have arround 200 MH/s more submitted shares with 2 quads.
2 questions -
how to set the temp option exactly and - which temp range is ok for the quads

what?!! so many MH/s with only 2 quads??? can you tell me more about your mining soft & hardware.

thph
Sr. Member
****
Offline Offline

Activity: 333



View Profile
October 18, 2012, 04:17:32 PM
 #536

sorry - 4 quads !
BR0KK
Hero Member
*****
Offline Offline

Activity: 742



View Profile
October 18, 2012, 07:29:19 PM
 #537

What is target checking good for?

I'll have to try it this night Smiley


tried it on p2pool sseing this:
Code:
bus-0-0: ztex_ufm1_15d4-04A32E1205-1: f=204,00MHz,  errorRate=0,07%,  maxErrorRate=0,90%,  hashRate=203,9MH/s,  submitted 16 new nonces,  luckFactor=1,21
bus-0-0: ztex_ufm1_15d4-04A3468E00-1: f=208,00MHz,  errorRate=0,07%,  maxErrorRate=0,86%,  hashRate=207,9MH/s,  submitted 16 new nonces,  luckFactor=0,97
bus-0-0: ztex_ufm1_15d4-04A3469756-1: f=212,00MHz,  errorRate=0,41%,  maxErrorRate=1,25%,  hashRate=211,1MH/s,  submitted 15 new nonces,  luckFactor=0,87
bus-0-0: ztex_ufm1_15d4-04A346BF8B-1: f=212,00MHz,  errorRate=0,03%,  maxErrorRate=0,71%,  hashRate=211,9MH/s,  submitted 14 new nonces,  luckFactor=1,00
bus-0-0: ztex_ufm1_15d4-04A346D523-1: f=216,00MHz,  errorRate=0,02%,  maxErrorRate=0,50%,  hashRate=216,0MH/s,  submitted 17 new nonces,  luckFactor=1,02
bus-0-0: ztex_ufm1_15d4-04A346E12C-1: f=204,00MHz,  errorRate=1,17%,  maxErrorRate=2,36%,  hashRate=201,6MH/s,  submitted 18 new nonces,  luckFactor=1,22
bus-0-0: ztex_ufm1_15y1-04A3461185-1: f=228,00MHz,  errorRate=0,00%,  maxErrorRate=0,00%,  hashRate=228,0MH/s,  submitted 10 new nonces,  luckFactor=0,57
bus-0-0: ztex_ufm1_15y1-04A3461185-2: f=228,00MHz,  errorRate=0,68%,  maxErrorRate=1,36%,  hashRate=226,4MH/s,  submitted 20 new nonces,  luckFactor=0,93
bus-0-0: ztex_ufm1_15y1-04A3461185-3: f=228,00MHz,  errorRate=0,00%,  maxErrorRate=0,00%,  hashRate=228,0MH/s,  submitted 14 new nonces,  luckFactor=0,89
bus-0-0: ztex_ufm1_15y1-04A3461185-4: f=228,00MHz,  errorRate=0,13%,  maxErrorRate=0,51%,  hashRate=227,7MH/s,  submitted 10 new nonces,  luckFactor=0,91
bus-0-1: ztex_ufm1_15y1-04A34644C6-1: f=220,00MHz,  errorRate=0,00%,  maxErrorRate=1,00%,  hashRate=220,0MH/s,  submitted 12 new nonces,  luckFactor=0,80
bus-0-1: ztex_ufm1_15y1-04A34644C6-2: f=228,00MHz,  errorRate=0,07%,  maxErrorRate=0,82%,  hashRate=227,8MH/s,  submitted 8 new nonces,  luckFactor=0,69
bus-0-1: ztex_ufm1_15y1-04A34644C6-3: f=224,00MHz,  errorRate=0,00%,  maxErrorRate=0,94%,  hashRate=224,0MH/s,  submitted 14 new nonces,  luckFactor=0,80
bus-0-1: ztex_ufm1_15y1-04A34644C6-4: f=228,00MHz,  errorRate=0,00%,  maxErrorRate=0,00%,  hashRate=228,0MH/s,  submitted 15 new nonces,  luckFactor=0,93
bus-0-1: ztex_ufm1_15y1-04A36E24F2-1: f=220,00MHz,  errorRate=0,74%,  maxErrorRate=1,32%,  hashRate=218,4MH/s,  submitted 15 new nonces,  luckFactor=1,03
bus-0-1: ztex_ufm1_15y1-04A36E24F2-2: f=216,00MHz,  errorRate=0,00%,  maxErrorRate=0,00%,  hashRate=216,0MH/s,  submitted 21 new nonces,  luckFactor=1,12
bus-0-1: ztex_ufm1_15y1-04A36E24F2-3: f=220,00MHz,  errorRate=0,00%,  maxErrorRate=0,98%,  hashRate=220,0MH/s,  submitted 24 new nonces,  luckFactor=1,06
bus-0-1: ztex_ufm1_15y1-04A36E24F2-4: f=216,00MHz,  errorRate=0,75%,  maxErrorRate=1,03%,  hashRate=214,4MH/s,  submitted 21 new nonces,  luckFactor=1,09
bus-0-0: poll loop time: 49ms (USB: 46ms network: 3ms)   getwork time: 7ms  submit time: 2ms
bus-0-1: poll loop time: 51ms (USB: 49ms network: 3ms)   getwork time: 8ms  submit time: 3ms
Total hash rate: 3931,1 MH/s
Total submitted hash rate: 3699,5 MH/s
 --------
bus-0-0: ztex_ufm1_15y1-04A3461185-1: Set frequency from 228,00MHz to 232,00MHz
New block detected by long polling (submitold = true)
New block detected by long polling (submitold = true)
New block detected by long polling (submitold = true)
bus-0-0: ztex_ufm1_15y1-04A3461185-1: Set frequency from 232,00MHz to 228,00MHz
New block detected by long polling (submitold = true)
New block detected by long polling (submitold = true)


Code:
2012-10-19 00:25:32.438000 P2Pool: 17421 shares in chain (9537 verified/17425 total) Peers: 14 (4 incoming)
2012-10-19 00:25:32.439000  Local: 3736MH/s in last 10.0 minutes Local dead on arrival: ~4.2% (2-7%) Expected time to share: 13.1 minutes
2012-10-19 00:25:32.440000  Shares: 7 (1 orphan, 3 dead) Stale rate: ~57.1% (25-85%) Efficiency: ~49.2% (18-86%) Current payout: 0.0174 BTC
2012-10-19 00:25:32.441000  Pool: 353GH/s Stale rate: 12.8% Expected time to block: 10.4 hours


ztex
Donator
Sr. Member
*
Offline Offline

Activity: 367

ZTEX FPGA Boards


View Profile WWW
October 19, 2012, 07:53:48 AM
 #538

Total hash rate: 3398,6 MH/s
Total submitted hash rate: 3418,7 MH/s
 --------
works great - i have arround 200 MH/s more submitted shares with 2 quads.
2 questions -
how to set the temp option exactly and - which temp range is ok for the quads

The temperature limit is set using the parameter -t, e.g. -t 65 sets it to 65°C. If this temperature is reached the FPGA is shut down.

Up to 70°C (default temperature limit) is ok. But try to stay below 60°C in order to achieve the maximum performance.



ztex
Donator
Sr. Member
*
Offline Offline

Activity: 367

ZTEX FPGA Boards


View Profile WWW
October 19, 2012, 08:03:01 AM
 #539

What is target checking good for?

I'll have to try it this night Smiley

See https://en.bitcoin.it/wiki/Target, if pool difficulty is > 1 it only submits shares that met the target. (By default all shares smaller then the maximum target are submitted).

gr0bi42
Full Member
***
Offline Offline

Activity: 158


View Profile WWW
November 08, 2012, 04:44:56 PM
 #540

A new testing version has been released.
Binaries: http://www.ztex.de/btcminer/ZtexBTCMiner-121017.jar
Source: http://www.ztex.de/btcminer/ZtexBTCMiner-121017.tar.bz2

New features are:

    * Temperature sensor support for USB-FPGA Modules 1.15y rev. 2 (temperature limit is set using the paramter -t)
    * X-Mining-extensions: midstate, submitold
    * Target checking, must be enabled using -tc
    * MAC address printed at -i


Hi,

I've integrated the recent changes into my httpd version of BTCMiner.

Source is online here: https://github.com/gr0bi42/BTCMiner

Made some changes regarding target checking too, although there are still problems with pool.itzod.ru.

Added a cool looking JSON based Webinterface. See photos below.

Precompiled package is available here: https://github.com/downloads/gr0bi42/BTCMiner/ZtexBTCMiner_gr0bi42_20121108.tar.bz2

See the README for further infos.

Happy mining  Smiley






Edit: lower resolution screenshots (was a retina display side effect)

Donations are welcome: 1Btf3BqUegfe5iFdWsgfBf1Ew3YsAvsrLT
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 [27] 28 29 30 31 32 33 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!