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

deeplink

hero member

Activity: 728

Merit: 500

In cryptography we trust

Quote from: ztex on October 04, 2012, 04:28:49 AM

Quote from: rupy on October 03, 2012, 09:45:37 AM

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.

ztex

donator

Activity: 367

Merit: 250

ZTEX FPGA Boards

Quote from: rupy on October 03, 2012, 09:45:37 AM

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).

rupy

hero member

Activity: 725

Merit: 500

ztex any plans for stratum for BTCMiner?

slush

legendary

Activity: 1386

Merit: 1097

Quote from: ztex on October 01, 2012, 04:10:59 AM

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?

ztex

donator

Activity: 367

Merit: 250

ZTEX FPGA Boards

Quote from: antirack on September 30, 2012, 06:25:28 PM

Quote from: ztex on September 26, 2012, 07:52:33 AM

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.

ztex

donator

Activity: 367

Merit: 250

ZTEX FPGA Boards

Quote from: slush on September 26, 2012, 10:12:36 AM

Quote from: ztex on September 26, 2012, 07:59:48 AM

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.

antirack

hero member

Activity: 489

Merit: 500

Immersionist

Quote from: ztex on September 26, 2012, 07:52:33 AM

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?

Turbor

legendary

Activity: 1022

Merit: 1000

BitMinter

Quote from: rupy on September 30, 2012, 07:44:21 AM

How do you enable backup pool with BTCMiner?

-b http://us2.eclipsemc.com:8337 Turbor_XXXX XXXXXX

Turbor_XXXX is your worker and XXXXXX your password

rupy

hero member

Activity: 725

Merit: 500

How do you enable backup pool with BTCMiner?

EDIT: Nevermind found it! '-b host name pass'...

BR0KK

hero member

Activity: 784

Merit: 500

it should switch to your backup pool, if you enabled one in your config?

@Ztex
Yes my power supplies died ore wer slowly dying. After six month of contious mining.

rupy

hero member

Activity: 725

Merit: 500

I'm still getting (not your fault):

001-0: ztex_ufm1_15d4-04A346E2B9-1: Error: connect timed out: Disabling URL http://pit.deepbit.net:8332 for 30s

But after a few of these in a row the whole cluster shuts down (problem with BTCMiner)!?

BR0KK

hero member

Activity: 784

Merit: 500

changed the power supplies.

and now im testing if it works ....

i really do have to make some connectors for my pc power supply. Couldn't be that hard to do it myself?

slush

legendary

Activity: 1386

Merit: 1097

Quote from: ztex on September 26, 2012, 07:59:48 AM

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.

BR0KK

hero member

Activity: 784

Merit: 500

Thx for the answer ill try other power supplies.

ztex

donator

Activity: 367

Merit: 250

ZTEX FPGA Boards

Quote from: BR0KK on September 24, 2012, 03:13:25 PM

Quote from: Inaba on September 23, 2012, 07:09:05 PM

Looks to me like that software does not support > difficulty 1 shares.

Thats his answer ?

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.

Maybe I will add this on the next release.

You can ignore these warnings.

ztex

donator

Activity: 367

Merit: 250

ZTEX FPGA Boards

Quote from: BR0KK on September 25, 2012, 05:37:23 PM

Code:

ztex_ufm1_15y1-04A36E24F2-4: Set frequency to 200,00MHz
bus-0-0: ztex_ufm1_15y1-04A36E24F2-4: added
2 new devices found.

Summary:
Bus bus-0-0 : 5 miners
Total : 5 miners

Disconnect all devices or enter `q' for exit. Enter `h' for help.

bus-0-0: ztex_ufm1_15y1-04A36E24F2-4: Using LongPolling URL http://127.0.0.1:9332/long-polling
New block detected by long polling
New block detected by long polling
New block detected by long polling
New block detected by long polling
New block detected by long polling
Warning (try 1): libusb0-dll:err [control_msg] sending control message failed, win error: Ein an das System angeschlossenes GerΣt funktioniert nicht.

New block detected by long polling
New block detected by long polling
bus-0-0: ztex_ufm1_15d4-04A32E1205-1: f=200,00MHz, errorRate=0,00%, maxErrorRate=0,00%, hashRate=200,0MH/s, submitted 4 new nonces, luckFactor=1,43
bus-0-0: ztex_ufm1_15y1-04A36E24F2-1: f=200,00MHz, errorRate=0,00%, maxErrorRate=0,00%, hashRate=200,0MH/s, submitted 3 new nonces, luckFactor=1,08
bus-0-0: ztex_ufm1_15y1-04A36E24F2-2: f=200,00MHz, errorRate=0,00%, maxErrorRate=0,00%, hashRate=200,0MH/s, submitted 1 new nonces, luckFactor=0,36
bus-0-0: ztex_ufm1_15y1-04A36E24F2-3: f=200,00MHz, errorRate=0,00%, maxErrorRate=0,00%, hashRate=200,0MH/s, submitted 1 new nonces, luckFactor=0,36
bus-0-0: ztex_ufm1_15y1-04A36E24F2-4: f=200,00MHz, errorRate=0,00%, maxErrorRate=0,00%, hashRate=200,0MH/s, submitted 6 new nonces, luckFactor=2,15
bus-0-0: poll loop time: 57ms (USB: 57ms network: 0ms) getwork time: 1ms submit time: 1ms
Total hash rate: 1000,0 MH/s
Total submitted hash rate: 1071,3 MH/s
--------
New block detected by long polling
New block detected by long polling
New block detected by long polling
New block detected by long polling
bus-0-0: ztex_ufm1_15d4-04A32E1205-1: Set frequency from 200,00MHz to 204,00MHz
bus-0-0: ztex_ufm1_15y1-04A36E24F2-2: Set frequency from 200,00MHz to 204,00MHz
bus-0-0: ztex_ufm1_15y1-04A36E24F2-1: Set frequency from 200,00MHz to 204,00MHz
bus-0-0: ztex_ufm1_15y1-04A36E24F2-3: Set frequency from 200,00MHz to 204,00MHz
bus-0-0: ztex_ufm1_15y1-04A36E24F2-4: Set frequency from 200,00MHz to 204,00MHz
Warning (try 1): libusb0-dll:err [control_msg] sending control message failed, win error: Ein an das System angeschlossenes GerΣt funktioniert nicht.

New block detected by long polling
New block detected by long polling
New block detected by long polling
Warning (try 1): libusb0-dll:err [control_msg] sending control message failed, win error: Ein an das System angeschlossenes GerΣt funktioniert nicht.

New block detected by long polling

i dont need to reset the boards. they are just dying one by one.
Sometines a Single FPGA and then two to four. (all randomly x and y boards).

I Checked the HUPS and the Cables ... everything is at least bought from "good quality" vendors (Hubs are from Belkin and trust) cables are shielded etc...

I'm thinking about buying a small Netbook or a router (i have tried TPlink but ddnt succeed ...) that's going to be my miner ...

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

BR0KK

hero member

Activity: 784

Merit: 500

Code:

ztex_ufm1_15y1-04A36E24F2-4: Set frequency to 200,00MHz
bus-0-0: ztex_ufm1_15y1-04A36E24F2-4: added
2 new devices found.

Summary:
Bus bus-0-0 : 5 miners
Total : 5 miners

Disconnect all devices or enter `q' for exit. Enter `h' for help.

bus-0-0: ztex_ufm1_15y1-04A36E24F2-4: Using LongPolling URL http://127.0.0.1:9332/long-polling
New block detected by long polling
New block detected by long polling
New block detected by long polling
New block detected by long polling
New block detected by long polling
Warning (try 1): libusb0-dll:err [control_msg] sending control message failed, win error: Ein an das System angeschlossenes GerΣt funktioniert nicht.

New block detected by long polling
New block detected by long polling
bus-0-0: ztex_ufm1_15d4-04A32E1205-1: f=200,00MHz, errorRate=0,00%, maxErrorRate=0,00%, hashRate=200,0MH/s, submitted 4 new nonces, luckFactor=1,43
bus-0-0: ztex_ufm1_15y1-04A36E24F2-1: f=200,00MHz, errorRate=0,00%, maxErrorRate=0,00%, hashRate=200,0MH/s, submitted 3 new nonces, luckFactor=1,08
bus-0-0: ztex_ufm1_15y1-04A36E24F2-2: f=200,00MHz, errorRate=0,00%, maxErrorRate=0,00%, hashRate=200,0MH/s, submitted 1 new nonces, luckFactor=0,36
bus-0-0: ztex_ufm1_15y1-04A36E24F2-3: f=200,00MHz, errorRate=0,00%, maxErrorRate=0,00%, hashRate=200,0MH/s, submitted 1 new nonces, luckFactor=0,36
bus-0-0: ztex_ufm1_15y1-04A36E24F2-4: f=200,00MHz, errorRate=0,00%, maxErrorRate=0,00%, hashRate=200,0MH/s, submitted 6 new nonces, luckFactor=2,15
bus-0-0: poll loop time: 57ms (USB: 57ms network: 0ms) getwork time: 1ms submit time: 1ms
Total hash rate: 1000,0 MH/s
Total submitted hash rate: 1071,3 MH/s
--------
New block detected by long polling
New block detected by long polling
New block detected by long polling
New block detected by long polling
bus-0-0: ztex_ufm1_15d4-04A32E1205-1: Set frequency from 200,00MHz to 204,00MHz
bus-0-0: ztex_ufm1_15y1-04A36E24F2-2: Set frequency from 200,00MHz to 204,00MHz
bus-0-0: ztex_ufm1_15y1-04A36E24F2-1: Set frequency from 200,00MHz to 204,00MHz
bus-0-0: ztex_ufm1_15y1-04A36E24F2-3: Set frequency from 200,00MHz to 204,00MHz
bus-0-0: ztex_ufm1_15y1-04A36E24F2-4: Set frequency from 200,00MHz to 204,00MHz
Warning (try 1): libusb0-dll:err [control_msg] sending control message failed, win error: Ein an das System angeschlossenes GerΣt funktioniert nicht.

New block detected by long polling
New block detected by long polling
New block detected by long polling
Warning (try 1): libusb0-dll:err [control_msg] sending control message failed, win error: Ein an das System angeschlossenes GerΣt funktioniert nicht.

New block detected by long polling

i dont need to reset the boards. they are just dying one by one.
Sometines a Single FPGA and then two to four. (all randomly x and y boards).

I Checked the HUPS and the Cables ... everything is at least bought from "good quality" vendors (Hubs are from Belkin and trust) cables are shielded etc...

I'm thinking about buying a small Netbook or a router (i have tried TPlink but ddnt succeed ...) that's going to be my miner ...

randomguy7

hero member

Activity: 527

Merit: 500

Quote from: BR0KK on September 24, 2012, 05:50:35 PM

Quote from: BR0KK on September 24, 2012, 03:13:25 PM

Quote from: Inaba on September 23, 2012, 07:09:05 PM

Looks to me like that software does not support > difficulty 1 shares.

Thats his answer ?

and i'm facing massive USB Connection errors out of no reason (i cant think of one, since it worked flawless for several month now).

My Setup:
A Windows 7 VM on a MAX OSX Mountain Lion Host ( Since i'm totally unable to get BTC miner < or anything else that can mine with OSX> working natively on MAC)

A 7 Port USB Hub.
A Silex SWX2000W+ device Server (All boards connected to this device server)

It worked realy good for at least 4 month now .... All of a sudden, after a small Software update and a brief restart of my MAC all my board are facing massive USB Connection errors ....

If i connect them to the device server or directly to my mac they wont be stable at all. After some time they randomly shut down with libusb connection errors.

--> Im buying a video card tomorrow .... need to ged rid of the MAC / VM solution.

Does it help when you pull the power plugs from the boards and then plug them in again (while keeping the usb cables connected!)?

BR0KK

hero member

Activity: 784

Merit: 500

Quote from: BR0KK on September 24, 2012, 03:13:25 PM

Quote from: Inaba on September 23, 2012, 07:09:05 PM

Looks to me like that software does not support > difficulty 1 shares.

Thats his answer ?

and i'm facing massive USB Connection errors out of no reason (i cant think of one, since it worked flawless for several month now).

My Setup:
A Windows 7 VM on a MAX OSX Mountain Lion Host ( Since i'm totally unable to get BTC miner < or anything else that can mine with OSX> working natively on MAC)

A 7 Port USB Hub.
A Silex SWX2000W+ device Server (All boards connected to this device server)

It worked realy good for at least 4 month now .... All of a sudden, after a small Software update and a brief restart of my MAC all my board are facing massive USB Connection errors ....

If i connect them to the device server or directly to my mac they wont be stable at all. After some time they randomly shut down with libusb connection errors.

--> Im buying a video card tomorrow .... need to ged rid of the MAC / VM solution.

BR0KK

hero member

Activity: 784

Merit: 500

Quote from: Inaba on September 23, 2012, 07:09:05 PM

Looks to me like that software does not support > difficulty 1 shares.

Thats his answer ?

Topic: BTCMiner - Open Source Bitcoin Miner for ZTEX FPGA Boards, 215 MH/s on LX150 - page 7. (Read 161510 times)