BTCMiner - Open Source Bitcoin Miner for ZTEX FPGA Boards, 215 MH/s on LX150

[slush]

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]

ztex any plans for stratum for BTCMiner?

[ztex]

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]

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]

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

[Nachtwind]

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]

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]

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]

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

[ztex]

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

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

[ztex]

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]

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]

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]

sorry - 4 quads !

[BR0KK]

What is target checking good for?

I'll have to try it this night


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]

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]

What is target checking good for?

I'll have to try it this night

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]

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  






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

[gr0bi42]

A new Bugfix version is available here: https://github.com/downloads/gr0bi42/BTCMiner/ZtexBTCMiner_gr0bi42_20121109.tar.bz2

Changes: bugfix - with disabled target checking, no shares were submitted *doh*

[fydel]

grobi42: Thanks you for the fancy webinterface. I am running the miner on a QNAP NAS. But the Webserver doesn't start up. Are there any logs where I can see why ?

edit: typo