Bitcoin Forum
December 06, 2016, 02:27:29 PM *
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 153758 times)
Schrankwand
Full Member
***
Offline Offline

Activity: 224


View Profile
June 15, 2013, 01:52:27 PM
 #601

HI, quick question for everyone.

I have a ZTEX 1.15y with one of the chips broken/Not working. With other FPGAs, reflashing the software has often taken care of such problems.


So, if I wanted to reflash, is THIS the right command?

Code:
java -cp ZtexBTCMiner-121126.jar BTCMiner -m p -pt ztex_ufm1_15y1 -f ztex_ufm1_15y1.ihx

Code is right. What's the problem with the chip ? Immediate downclocking ? I have to restart my board over and over again to use the broken chip. It will mine then with 144 MHz, the others at normal speed. When I have to reboot my PC I do it again. Sometimes it works after 3 times, sometimes after 20 but it always works. Start, let overheat kick in, control C and restart the board. Just set -oh to 0.7 or bigger.

100% Hardware errors.

All others run at 220 and 216 straight. Other chip is declared sick fast, then declared dead and then off within an hour.

The broken chip does not even bring a single piece of work though. I bought it broken and knew it, I was just thinking about a few options that might not have been considered yet. I did reflash and get the code running, however it seems that the FPGA chips cannot be configured one by one, is that right?
1481034449
Hero Member
*
Offline Offline

Posts: 1481034449

View Profile Personal Message (Offline)

Ignore
1481034449
Reply with quote  #2

1481034449
Report to moderator
1481034449
Hero Member
*
Offline Offline

Posts: 1481034449

View Profile Personal Message (Offline)

Ignore
1481034449
Reply with quote  #2

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

Posts: 1481034449

View Profile Personal Message (Offline)

Ignore
1481034449
Reply with quote  #2

1481034449
Report to moderator
1481034449
Hero Member
*
Offline Offline

Posts: 1481034449

View Profile Personal Message (Offline)

Ignore
1481034449
Reply with quote  #2

1481034449
Report to moderator
Turbor
Legendary
*
Offline Offline

Activity: 1008


BitMinter


View Profile WWW
June 15, 2013, 09:10:38 PM
 #602

Sounds like cgminer. Try BTCminer for this one board. Gives you more information when the chip goes out.

HI, quick question for everyone.

I have a ZTEX 1.15y with one of the chips broken/Not working. With other FPGAs, reflashing the software has often taken care of such problems.


So, if I wanted to reflash, is THIS the right command?

Code:
java -cp ZtexBTCMiner-121126.jar BTCMiner -m p -pt ztex_ufm1_15y1 -f ztex_ufm1_15y1.ihx

Code is right. What's the problem with the chip ? Immediate downclocking ? I have to restart my board over and over again to use the broken chip. It will mine then with 144 MHz, the others at normal speed. When I have to reboot my PC I do it again. Sometimes it works after 3 times, sometimes after 20 but it always works. Start, let overheat kick in, control C and restart the board. Just set -oh to 0.7 or bigger.

100% Hardware errors.

All others run at 220 and 216 straight. Other chip is declared sick fast, then declared dead and then off within an hour.

The broken chip does not even bring a single piece of work though. I bought it broken and knew it, I was just thinking about a few options that might not have been considered yet. I did reflash and get the code running, however it seems that the FPGA chips cannot be configured one by one, is that right?

ztex
Donator
Sr. Member
*
Offline Offline

Activity: 367

ZTEX FPGA Boards


View Profile WWW
June 18, 2013, 08:23:09 AM
 #603

100% Hardware errors.

All others run at 220 and 216 straight. Other chip is declared sick fast, then declared dead and then off within an hour.

The broken chip does not even bring a single piece of work though. I bought it broken and knew it, I was just thinking about a few options that might not have been considered yet. I did reflash and get the code running, however it seems that the FPGA chips cannot be configured one by one, is that right?

For a reparation request please use the contact form http://www.ztex.de/contact.e.html

If you bought it broken I wold charge a fee if it can be repaired successfully.


ztex
Donator
Sr. Member
*
Offline Offline

Activity: 367

ZTEX FPGA Boards


View Profile WWW
June 18, 2013, 08:23:33 AM
 #604

Yes, the version 2 of the board, is it sensing the die temperature? The board temperature near the FPGA? Does it somehow sense the temperature of the heat sink?

Temperature sensors IC16 to IC19 (see schematics) are placed on the PCB near the FPGA. The measure a mixture between PCB temperature and air temperature below the heat sink. It's not an exact science but this sensors can detect overheating of the heat sink as well as improper installed heat sink (heat sink cold, PCB hot).







Schrankwand
Full Member
***
Offline Offline

Activity: 224


View Profile
June 18, 2013, 08:30:15 AM
 #605

100% Hardware errors.

All others run at 220 and 216 straight. Other chip is declared sick fast, then declared dead and then off within an hour.

The broken chip does not even bring a single piece of work though. I bought it broken and knew it, I was just thinking about a few options that might not have been considered yet. I did reflash and get the code running, however it seems that the FPGA chips cannot be configured one by one, is that right?

For a reparation request please use the contact form http://www.ztex.de/contact.e.html

If you bought it broken I wold charge a fee if it can be repaired successfully.



From the design I believe it is a chinese rip off copy of your boards, actually. So I would not take your service for repairing a ripoff board here Wink

Would you also repair one of those for a fee? I would first supply with you better data though, before making a decision.
ztex
Donator
Sr. Member
*
Offline Offline

Activity: 367

ZTEX FPGA Boards


View Profile WWW
June 18, 2013, 08:52:56 AM
 #606

100% Hardware errors.

All others run at 220 and 216 straight. Other chip is declared sick fast, then declared dead and then off within an hour.

The broken chip does not even bring a single piece of work though. I bought it broken and knew it, I was just thinking about a few options that might not have been considered yet. I did reflash and get the code running, however it seems that the FPGA chips cannot be configured one by one, is that right?

For a reparation request please use the contact form http://www.ztex.de/contact.e.html

If you bought it broken I wold charge a fee if it can be repaired successfully.



From the design I believe it is a chinese rip off copy of your boards, actually. So I would not take your service for repairing a ripoff board here Wink

Would you also repair one of those for a fee? I would first supply with you better data though, before making a decision.

I would only repair it if it was produced by me. Please contact me via http://www.ztex.de/contact.e.html for verification details.

Schrankwand
Full Member
***
Offline Offline

Activity: 224


View Profile
June 19, 2013, 04:06:03 PM
 #607

Quote
Sounds like cgminer. Try BTCminer for this one board. Gives you more information when the chip goes out.


Here you go:

Code:
2013-06-19T16:01:30:
(Re)Scanning bus ...
2013-06-19T16:01:30: ztex_ufm1_15y1-0019-03-12: New device: bitfile=ztex_ufm1_15y1   f_default=200,00MHz  f_max=248,00MHz  HpC=1.0H
2013-06-19T16:01:30: ztex_ufm1_15y1-0019-03-12: MAC address: 0004a36dd5f2
2013-06-19T16:01:31: ztex_ufm1_15y1-0019-03-12: FPGA 1: configuration time: 313 ms
2013-06-19T16:01:31: ztex_ufm1_15y1-0019-03-12: FPGA 2: configuration time: 313 ms
2013-06-19T16:01:32: ztex_ufm1_15y1-0019-03-12: FPGA 3: configuration time: 312 ms
2013-06-19T16:01:32: ztex_ufm1_15y1-0019-03-12: FPGA 4: configuration time: 313 ms
2013-06-19T16:01:32: ztex_ufm1_15y1-0019-03-12-1: New FPGA
2013-06-19T16:01:32: ztex_ufm1_15y1-0019-03-12-1: Set frequency to 200,00MHz
2013-06-19T16:01:32: Starting mining thread for bus bus-0-0
2013-06-19T16:01:32: bus-0-0: ztex_ufm1_15y1-0019-03-12-1: added
2013-06-19T16:01:32: ztex_ufm1_15y1-0019-03-12-2: New FPGA
2013-06-19T16:01:32: ztex_ufm1_15y1-0019-03-12-2: Set frequency to 200,00MHz
2013-06-19T16:01:32: bus-0-0: ztex_ufm1_15y1-0019-03-12-2: added
2013-06-19T16:01:32: ztex_ufm1_15y1-0019-03-12-3: New FPGA
2013-06-19T16:01:32: ztex_ufm1_15y1-0019-03-12-3: Set frequency to 200,00MHz
2013-06-19T16:01:32: bus-0-0: ztex_ufm1_15y1-0019-03-12-3: added
2013-06-19T16:01:32: ztex_ufm1_15y1-0019-03-12-4: New FPGA
2013-06-19T16:01:32: ztex_ufm1_15y1-0019-03-12-4: Set frequency to 200,00MHz
2013-06-19T16:01:32: bus-0-0: ztex_ufm1_15y1-0019-03-12-4: added
2013-06-19T16:01:32: 1 new devices found.
2013-06-19T16:01:32:
Summary:
2013-06-19T16:01:32:   Bus bus-0-0 : 4 miners
2013-06-19T16:01:32:   Total   : 4 miners

2013-06-19T16:01:32:
Disconnect all devices or enter `q' for exit. Enter `h' for help.

2013-06-19T16:01:33: bus-0-0: ztex_ufm1_15y1-0019-03-12-4: Using LongPolling URL http://api.bitcoin.cz:8401
2013-06-19T16:01:34: bus-0-0: ztex_ufm1_15y1-0019-03-12-3: Set frequency from 200,00MHz to 196,00MHz
2013-06-19T16:01:36: bus-0-0: ztex_ufm1_15y1-0019-03-12-3: Set frequency from 196,00MHz to 200,00MHz
2013-06-19T16:01:39: bus-0-0: ztex_ufm1_15y1-0019-03-12-3: Set frequency from 200,00MHz to 196,00MHz
2013-06-19T16:01:41: bus-0-0: ztex_ufm1_15y1-0019-03-12-3: Set frequency from 196,00MHz to 192,00MHz
2013-06-19T16:01:44: bus-0-0: ztex_ufm1_15y1-0019-03-12-3: Set frequency from 192,00MHz to 196,00MHz
2013-06-19T16:01:46: bus-0-0: ztex_ufm1_15y1-0019-03-12-3: Set frequency from 196,00MHz to 192,00MHz
2013-06-19T16:01:48: bus-0-0: ztex_ufm1_15y1-0019-03-12-3: Set frequency from 192,00MHz to 188,00MHz
2013-06-19T16:01:48: bus-0-0: ztex_ufm1_15y1-0019-03-12-3: Error: Hash rate drop of 6,0% detect. This may be caused by overheating. FPGA is shut down to prevent damage.: Disabling device
2013-06-19T16:02:32: bus-0-0: ztex_ufm1_15y1-0019-03-12-1: f=200,00MHz,  errorRate=0,00%,  maxErrorRate=0,00%,  hashRate=200,0MH/s,  submitted 3 new nonces,  luckFactor=1,08
2013-06-19T16:02:32: bus-0-0: ztex_ufm1_15y1-0019-03-12-2: f=200,00MHz,  errorRate=0,00%,  maxErrorRate=0,00%,  hashRate=200,0MH/s,  submitted 1 new nonces,  luckFactor=0,36
2013-06-19T16:02:32: bus-0-0: ztex_ufm1_15y1-0019-03-12-3: Error: Hash rate drop of 6,0% detect. This may be caused by overheating. FPGA is shut down to prevent damage.: Device disabled since 2013-06-19T16:01:48
2013-06-19T16:02:32: bus-0-0: ztex_ufm1_15y1-0019-03-12-4: f=200,00MHz,  errorRate=0,00%,  maxErrorRate=0,00%,  hashRate=200,0MH/s,  submitted 2 new nonces,  luckFactor=0,72
2013-06-19T16:02:33: bus-0-0: poll loop time: 15ms (USB: 7ms network: 8ms)   getwork time: 44ms  submit time: 103ms
2013-06-19T16:02:33: Total hash rate: 600,0 MH/s
2013-06-19T16:02:33: Total submitted hash rate: 429,4 MH/s
2013-06-19T16:02:33:  --------
2013-06-19T16:02:45: bus-0-0: ztex_ufm1_15y1-0019-03-12-2: Set frequency from 200,00MHz to 204,00MHz
2013-06-19T16:02:45: bus-0-0: ztex_ufm1_15y1-0019-03-12-4: Set frequency from 200,00MHz to 204,00MHz
2013-06-19T16:02:46: bus-0-0: ztex_ufm1_15y1-0019-03-12-1: Set frequency from 200,00MHz to 204,00MHz
2013-06-19T16:02:48: bus-0-0: ztex_ufm1_15y1-0019-03-12-4: Set frequency from 204,00MHz to 200,00MHz
2013-06-19T16:04:00: bus-0-0: ztex_ufm1_15y1-0019-03-12-2: Set frequency from 204,00MHz to 208,00MHz
2013-06-19T16:04:00: bus-0-0: ztex_ufm1_15y1-0019-03-12-1: Set frequency from 204,00MHz to 208,00MHz
2013-06-19T16:05:15: bus-0-0: ztex_ufm1_15y1-0019-03-12-1: Set frequency from 208,00MHz to 212,00MHz
2013-06-19T16:05:15: bus-0-0: ztex_ufm1_15y1-0019-03-12-2: Set frequency from 208,00MHz to 212,00MHz
2013-06-19T16:06:30: bus-0-0: ztex_ufm1_15y1-0019-03-12-1: Set frequency from 212,00MHz to 216,00MHz
2013-06-19T16:06:30: bus-0-0: ztex_ufm1_15y1-0019-03-12-2: Set frequency from 212,00MHz to 216,00MHz
2013-06-19T16:07:33: bus-0-0: ztex_ufm1_15y1-0019-03-12-1: f=216,00MHz,  errorRate=0,00%,  maxErrorRate=0,00%,  hashRate=216,0MH/s,  submitted 13 new nonces,  luckFactor=0,89
2013-06-19T16:07:33: bus-0-0: ztex_ufm1_15y1-0019-03-12-2: f=216,00MHz,  errorRate=0,00%,  maxErrorRate=0,00%,  hashRate=216,0MH/s,  submitted 17 new nonces,  luckFactor=1,00
2013-06-19T16:07:33: bus-0-0: ztex_ufm1_15y1-0019-03-12-3: Error: Hash rate drop of 6,0% detect. This may be caused by overheating. FPGA is shut down to prevent damage.: Device disabled since 2013-06-19T16:01:48
2013-06-19T16:07:33: bus-0-0: ztex_ufm1_15y1-0019-03-12-4: f=200,00MHz,  errorRate=0,00%,  maxErrorRate=0,00%,  hashRate=200,0MH/s,  submitted 18 new nonces,  luckFactor=1,20
2013-06-19T16:07:33: bus-0-0: poll loop time: 12ms (USB: 6ms network: 6ms)   getwork time: 38ms  submit time: 71ms
2013-06-19T16:07:33: bus-0-0: Warning: 1 overflows occured. This is usually caused by a slow network connection.
2013-06-19T16:07:33: Total hash rate: 632,0 MH/s
2013-06-19T16:07:33: Total submitted hash rate: 644,0 MH/s
2013-06-19T16:07:33:  --------
2013-06-19T16:07:45: bus-0-0: ztex_ufm1_15y1-0019-03-12-1: Set frequency from 216,00MHz to 220,00MHz
2013-06-19T16:07:45: bus-0-0: ztex_ufm1_15y1-0019-03-12-2: Set frequency from 216,00MHz to 220,00MHz
2013-06-19T16:07:56: bus-0-0: ztex_ufm1_15y1-0019-03-12-2: Set frequency from 220,00MHz to 216,00MHz
2013-06-19T16:09:00: bus-0-0: ztex_ufm1_15y1-0019-03-12-1: Set frequency from 220,00MHz to 224,00MHz
2013-06-19T16:09:09: bus-0-0: ztex_ufm1_15y1-0019-03-12-1: Set frequency from 224,00MHz to 220,00MHz
2013-06-19T16:09:51: bus-0-0: ztex_ufm1_15y1-0019-03-12-1: Set frequency from 220,00MHz to 224,00MHz
2013-06-19T16:09:54: bus-0-0: ztex_ufm1_15y1-0019-03-12-1: Set frequency from 224,00MHz to 220,00MHz
2013-06-19T16:10:00: bus-0-0: ztex_ufm1_15y1-0019-03-12-1: Set frequency from 220,00MHz to 216,00MHz
2013-06-19T16:11:11: New block detected by block monitor
2013-06-19T16:12:33: bus-0-0: ztex_ufm1_15y1-0019-03-12-1: f=216,00MHz,  errorRate=0,03%,  maxErrorRate=0,69%,  hashRate=215,9MH/s,  submitted 14 new nonces,  luckFactor=0,91
2013-06-19T16:12:33: bus-0-0: ztex_ufm1_15y1-0019-03-12-2: f=216,00MHz,  errorRate=0,29%,  maxErrorRate=1,01%,  hashRate=215,4MH/s,  submitted 17 new nonces,  luckFactor=1,06
2013-06-19T16:12:33: bus-0-0: ztex_ufm1_15y1-0019-03-12-3: Error: Hash rate drop of 6,0% detect. This may be caused by overheating. FPGA is shut down to prevent damage.: Device disabled since 2013-06-19T16:01:48
2013-06-19T16:12:33: bus-0-0: ztex_ufm1_15y1-0019-03-12-4: f=200,00MHz,  errorRate=0,00%,  maxErrorRate=0,00%,  hashRate=200,0MH/s,  submitted 17 new nonces,  luckFactor=1,21
2013-06-19T16:12:33: bus-0-0: poll loop time: 12ms (USB: 6ms network: 6ms)   getwork time: 39ms  submit time: 74ms
2013-06-19T16:12:33: Total hash rate: 631,3 MH/s
2013-06-19T16:12:33: Total submitted hash rate: 663,6 MH/s
2013-06-19T16:12:33:  --------






Quote
I would only repair it if it was produced by me. Please contact me via http://www.ztex.de/contact.e.html for verification details.

Since your boards don't feature large USB rack connectors, I would argue it is a clone Wink

Do you have any ideas what I could do to check without repairs?
Turbor
Legendary
*
Offline Offline

Activity: 1008


BitMinter


View Profile WWW
June 19, 2013, 05:33:15 PM
 #608

Set -oh to 0.7 or higher in the BTCMiner start code. It will then shut down later. I know that S. does not recommend doing this but since it's a clone you should give it a try.

Once the bad chip fails, hit control C, restart and repeat over and over again. If you are lucky it keeps hanging and will then mine fine at a lower frequency.

Quote
Sounds like cgminer. Try BTCminer for this one board. Gives you more information when the chip goes out.


Here you go:

Code:
2013-06-19T16:01:30:
(Re)Scanning bus ...
2013-06-19T16:01:30: ztex_ufm1_15y1-0019-03-12: New device: bitfile=ztex_ufm1_15y1   f_default=200,00MHz  f_max=248,00MHz  HpC=1.0H
2013-06-19T16:01:30: ztex_ufm1_15y1-0019-03-12: MAC address: 0004a36dd5f2
2013-06-19T16:01:31: ztex_ufm1_15y1-0019-03-12: FPGA 1: configuration time: 313 ms
2013-06-19T16:01:31: ztex_ufm1_15y1-0019-03-12: FPGA 2: configuration time: 313 ms
2013-06-19T16:01:32: ztex_ufm1_15y1-0019-03-12: FPGA 3: configuration time: 312 ms
2013-06-19T16:01:32: ztex_ufm1_15y1-0019-03-12: FPGA 4: configuration time: 313 ms
2013-06-19T16:01:32: ztex_ufm1_15y1-0019-03-12-1: New FPGA
2013-06-19T16:01:32: ztex_ufm1_15y1-0019-03-12-1: Set frequency to 200,00MHz
2013-06-19T16:01:32: Starting mining thread for bus bus-0-0
2013-06-19T16:01:32: bus-0-0: ztex_ufm1_15y1-0019-03-12-1: added
2013-06-19T16:01:32: ztex_ufm1_15y1-0019-03-12-2: New FPGA
2013-06-19T16:01:32: ztex_ufm1_15y1-0019-03-12-2: Set frequency to 200,00MHz
2013-06-19T16:01:32: bus-0-0: ztex_ufm1_15y1-0019-03-12-2: added
2013-06-19T16:01:32: ztex_ufm1_15y1-0019-03-12-3: New FPGA
2013-06-19T16:01:32: ztex_ufm1_15y1-0019-03-12-3: Set frequency to 200,00MHz
2013-06-19T16:01:32: bus-0-0: ztex_ufm1_15y1-0019-03-12-3: added
2013-06-19T16:01:32: ztex_ufm1_15y1-0019-03-12-4: New FPGA
2013-06-19T16:01:32: ztex_ufm1_15y1-0019-03-12-4: Set frequency to 200,00MHz
2013-06-19T16:01:32: bus-0-0: ztex_ufm1_15y1-0019-03-12-4: added
2013-06-19T16:01:32: 1 new devices found.
2013-06-19T16:01:32:
Summary:
2013-06-19T16:01:32:   Bus bus-0-0 : 4 miners
2013-06-19T16:01:32:   Total   : 4 miners

2013-06-19T16:01:32:
Disconnect all devices or enter `q' for exit. Enter `h' for help.

2013-06-19T16:01:33: bus-0-0: ztex_ufm1_15y1-0019-03-12-4: Using LongPolling URL http://api.bitcoin.cz:8401
2013-06-19T16:01:34: bus-0-0: ztex_ufm1_15y1-0019-03-12-3: Set frequency from 200,00MHz to 196,00MHz
2013-06-19T16:01:36: bus-0-0: ztex_ufm1_15y1-0019-03-12-3: Set frequency from 196,00MHz to 200,00MHz
2013-06-19T16:01:39: bus-0-0: ztex_ufm1_15y1-0019-03-12-3: Set frequency from 200,00MHz to 196,00MHz
2013-06-19T16:01:41: bus-0-0: ztex_ufm1_15y1-0019-03-12-3: Set frequency from 196,00MHz to 192,00MHz
2013-06-19T16:01:44: bus-0-0: ztex_ufm1_15y1-0019-03-12-3: Set frequency from 192,00MHz to 196,00MHz
2013-06-19T16:01:46: bus-0-0: ztex_ufm1_15y1-0019-03-12-3: Set frequency from 196,00MHz to 192,00MHz
2013-06-19T16:01:48: bus-0-0: ztex_ufm1_15y1-0019-03-12-3: Set frequency from 192,00MHz to 188,00MHz
2013-06-19T16:01:48: bus-0-0: ztex_ufm1_15y1-0019-03-12-3: Error: Hash rate drop of 6,0% detect. This may be caused by overheating. FPGA is shut down to prevent damage.: Disabling device
2013-06-19T16:02:32: bus-0-0: ztex_ufm1_15y1-0019-03-12-1: f=200,00MHz,  errorRate=0,00%,  maxErrorRate=0,00%,  hashRate=200,0MH/s,  submitted 3 new nonces,  luckFactor=1,08
2013-06-19T16:02:32: bus-0-0: ztex_ufm1_15y1-0019-03-12-2: f=200,00MHz,  errorRate=0,00%,  maxErrorRate=0,00%,  hashRate=200,0MH/s,  submitted 1 new nonces,  luckFactor=0,36
2013-06-19T16:02:32: bus-0-0: ztex_ufm1_15y1-0019-03-12-3: Error: Hash rate drop of 6,0% detect. This may be caused by overheating. FPGA is shut down to prevent damage.: Device disabled since 2013-06-19T16:01:48
2013-06-19T16:02:32: bus-0-0: ztex_ufm1_15y1-0019-03-12-4: f=200,00MHz,  errorRate=0,00%,  maxErrorRate=0,00%,  hashRate=200,0MH/s,  submitted 2 new nonces,  luckFactor=0,72
2013-06-19T16:02:33: bus-0-0: poll loop time: 15ms (USB: 7ms network: 8ms)   getwork time: 44ms  submit time: 103ms
2013-06-19T16:02:33: Total hash rate: 600,0 MH/s
2013-06-19T16:02:33: Total submitted hash rate: 429,4 MH/s
2013-06-19T16:02:33:  --------
2013-06-19T16:02:45: bus-0-0: ztex_ufm1_15y1-0019-03-12-2: Set frequency from 200,00MHz to 204,00MHz
2013-06-19T16:02:45: bus-0-0: ztex_ufm1_15y1-0019-03-12-4: Set frequency from 200,00MHz to 204,00MHz
2013-06-19T16:02:46: bus-0-0: ztex_ufm1_15y1-0019-03-12-1: Set frequency from 200,00MHz to 204,00MHz
2013-06-19T16:02:48: bus-0-0: ztex_ufm1_15y1-0019-03-12-4: Set frequency from 204,00MHz to 200,00MHz
2013-06-19T16:04:00: bus-0-0: ztex_ufm1_15y1-0019-03-12-2: Set frequency from 204,00MHz to 208,00MHz
2013-06-19T16:04:00: bus-0-0: ztex_ufm1_15y1-0019-03-12-1: Set frequency from 204,00MHz to 208,00MHz
2013-06-19T16:05:15: bus-0-0: ztex_ufm1_15y1-0019-03-12-1: Set frequency from 208,00MHz to 212,00MHz
2013-06-19T16:05:15: bus-0-0: ztex_ufm1_15y1-0019-03-12-2: Set frequency from 208,00MHz to 212,00MHz
2013-06-19T16:06:30: bus-0-0: ztex_ufm1_15y1-0019-03-12-1: Set frequency from 212,00MHz to 216,00MHz
2013-06-19T16:06:30: bus-0-0: ztex_ufm1_15y1-0019-03-12-2: Set frequency from 212,00MHz to 216,00MHz
2013-06-19T16:07:33: bus-0-0: ztex_ufm1_15y1-0019-03-12-1: f=216,00MHz,  errorRate=0,00%,  maxErrorRate=0,00%,  hashRate=216,0MH/s,  submitted 13 new nonces,  luckFactor=0,89
2013-06-19T16:07:33: bus-0-0: ztex_ufm1_15y1-0019-03-12-2: f=216,00MHz,  errorRate=0,00%,  maxErrorRate=0,00%,  hashRate=216,0MH/s,  submitted 17 new nonces,  luckFactor=1,00
2013-06-19T16:07:33: bus-0-0: ztex_ufm1_15y1-0019-03-12-3: Error: Hash rate drop of 6,0% detect. This may be caused by overheating. FPGA is shut down to prevent damage.: Device disabled since 2013-06-19T16:01:48
2013-06-19T16:07:33: bus-0-0: ztex_ufm1_15y1-0019-03-12-4: f=200,00MHz,  errorRate=0,00%,  maxErrorRate=0,00%,  hashRate=200,0MH/s,  submitted 18 new nonces,  luckFactor=1,20
2013-06-19T16:07:33: bus-0-0: poll loop time: 12ms (USB: 6ms network: 6ms)   getwork time: 38ms  submit time: 71ms
2013-06-19T16:07:33: bus-0-0: Warning: 1 overflows occured. This is usually caused by a slow network connection.
2013-06-19T16:07:33: Total hash rate: 632,0 MH/s
2013-06-19T16:07:33: Total submitted hash rate: 644,0 MH/s
2013-06-19T16:07:33:  --------
2013-06-19T16:07:45: bus-0-0: ztex_ufm1_15y1-0019-03-12-1: Set frequency from 216,00MHz to 220,00MHz
2013-06-19T16:07:45: bus-0-0: ztex_ufm1_15y1-0019-03-12-2: Set frequency from 216,00MHz to 220,00MHz
2013-06-19T16:07:56: bus-0-0: ztex_ufm1_15y1-0019-03-12-2: Set frequency from 220,00MHz to 216,00MHz
2013-06-19T16:09:00: bus-0-0: ztex_ufm1_15y1-0019-03-12-1: Set frequency from 220,00MHz to 224,00MHz
2013-06-19T16:09:09: bus-0-0: ztex_ufm1_15y1-0019-03-12-1: Set frequency from 224,00MHz to 220,00MHz
2013-06-19T16:09:51: bus-0-0: ztex_ufm1_15y1-0019-03-12-1: Set frequency from 220,00MHz to 224,00MHz
2013-06-19T16:09:54: bus-0-0: ztex_ufm1_15y1-0019-03-12-1: Set frequency from 224,00MHz to 220,00MHz
2013-06-19T16:10:00: bus-0-0: ztex_ufm1_15y1-0019-03-12-1: Set frequency from 220,00MHz to 216,00MHz
2013-06-19T16:11:11: New block detected by block monitor
2013-06-19T16:12:33: bus-0-0: ztex_ufm1_15y1-0019-03-12-1: f=216,00MHz,  errorRate=0,03%,  maxErrorRate=0,69%,  hashRate=215,9MH/s,  submitted 14 new nonces,  luckFactor=0,91
2013-06-19T16:12:33: bus-0-0: ztex_ufm1_15y1-0019-03-12-2: f=216,00MHz,  errorRate=0,29%,  maxErrorRate=1,01%,  hashRate=215,4MH/s,  submitted 17 new nonces,  luckFactor=1,06
2013-06-19T16:12:33: bus-0-0: ztex_ufm1_15y1-0019-03-12-3: Error: Hash rate drop of 6,0% detect. This may be caused by overheating. FPGA is shut down to prevent damage.: Device disabled since 2013-06-19T16:01:48
2013-06-19T16:12:33: bus-0-0: ztex_ufm1_15y1-0019-03-12-4: f=200,00MHz,  errorRate=0,00%,  maxErrorRate=0,00%,  hashRate=200,0MH/s,  submitted 17 new nonces,  luckFactor=1,21
2013-06-19T16:12:33: bus-0-0: poll loop time: 12ms (USB: 6ms network: 6ms)   getwork time: 39ms  submit time: 74ms
2013-06-19T16:12:33: Total hash rate: 631,3 MH/s
2013-06-19T16:12:33: Total submitted hash rate: 663,6 MH/s
2013-06-19T16:12:33:  --------

Schrankwand
Full Member
***
Offline Offline

Activity: 224


View Profile
June 19, 2013, 07:17:59 PM
 #609

Turbor, thanks for the idea. I have done this already with CGminer, since cgminer clocks down continuously, it declares "Dead" only somewhere at below 120mhz usually and shuts it off.
BR0KK
Hero Member
*****
Offline Offline

Activity: 742



View Profile
June 20, 2013, 09:09:31 PM
 #610

Turbor, thanks for the idea. I have done this already with CGminer, since cgminer clocks down continuously, it declares "Dead" only somewhere at below 120mhz usually and shuts it off.

Do not forget to check the heatsink sits correctly and that there is a good connection between the chip and heatsink (thermal paste!). And if you accidentally shorted parts with that paste (if conductive)

Unstable powersupply and cheap hubs do their part too!

Did you reset the board by using JP 1 (hardware reset) and reprogrammed the bitstream again?

Polyatomic
Sr. Member
****
Offline Offline

Activity: 256


View Profile
June 22, 2013, 07:35:04 AM
 #611

For a 1.15y clone , which mining software is recommended to use cgminer or BTCMiner .

[/URL][/img]
Schrankwand
Full Member
***
Offline Offline

Activity: 224


View Profile
June 24, 2013, 11:34:07 AM
 #612

Turbor, thanks for the idea. I have done this already with CGminer, since cgminer clocks down continuously, it declares "Dead" only somewhere at below 120mhz usually and shuts it off.

Do not forget to check the heatsink sits correctly and that there is a good connection between the chip and heatsink (thermal paste!). And if you accidentally shorted parts with that paste (if conductive)

Unstable powersupply and cheap hubs do their part too!

Did you reset the board by using JP 1 (hardware reset) and reprogrammed the bitstream again?

I will take another look when I am home, right now it is hashing "on travel" here.

Asking for JP1, by the way, is another way to spot a clone: JP1 has no connector pins on the clones. Funny. I will short it with a paperclip to reach my goal then. No jumper here Cheesy

I had reprogrammed the Bitstream before using fwloader, but I might try it and do it again after circumventing EEPROM as in the manual. Looking at the heatsinks, I might perform some changes here as well and exchange whatever is in there (looks like Heatpads, ugh...) with some Arctic Cooling mx-2 paste.

But considering that the other chips run nicely, I believe that one of the Chips might have gotten damaged through improper heating. It can happen with these thermal pads.



BR0KK
Hero Member
*****
Offline Offline

Activity: 742



View Profile
June 24, 2013, 04:36:24 PM
 #613

Turbor, thanks for the idea. I have done this already with CGminer, since cgminer clocks down continuously, it declares "Dead" only somewhere at below 120mhz usually and shuts it off.

Do not forget to check the heatsink sits correctly and that there is a good connection between the chip and heatsink (thermal paste!). And if you accidentally shorted parts with that paste (if conductive)

Unstable powersupply and cheap hubs do their part too!

Did you reset the board by using JP 1 (hardware reset) and reprogrammed the bitstream again?

I will take another look when I am home, right now it is hashing "on travel" here.

Asking for JP1, by the way, is another way to spot a clone: JP1 has no connector pins on the clones. Funny. I will short it with a paperclip to reach my goal then. No jumper here Cheesy

I had reprogrammed the Bitstream before using fwloader, but I might try it and do it again after circumventing EEPROM as in the manual. Looking at the heatsinks, I might perform some changes here as well and exchange whatever is in there (looks like Heatpads, ugh...) with some Arctic Cooling mx-2 paste.

But considering that the other chips run nicely, I believe that one of the Chips might have gotten damaged through improper heating. It can happen with these thermal pads.

Yes, heatpads .... Ztex puts a waring leaflet in the packets that says: "Do not use the provided heat pads. USe thermal paste instead!")

ztex
Donator
Sr. Member
*
Offline Offline

Activity: 367

ZTEX FPGA Boards


View Profile WWW
June 25, 2013, 09:38:09 AM
 #614

I can confirm that an FPGA Board with the MAC address "0004a36dd5f2" was not produced by ZTEX.

The FPGA delivers wrong results from start-up. It's no overheating issue (but may be a defect caused by overheating). Probably the only thing you can "repair" by yourself are shortcuts, e.g. caused by electrical conductive thermal grease or metal (solder) remnants.

objectnotfound
Newbie
*
Offline Offline

Activity: 20


View Profile
July 02, 2013, 06:23:39 PM
 #615

I'm having an issue with the FPGA Module 1.15y, getting a no devices found.

I'm running Ubuntu 13.04 off a thumb drive and I've downloaded the SDCC and BTCMiner. I've installed the SDCC and I got the openjdk-7-jre package through apt-get. Last night I was trying to figure it out and I had the LEDs on the board all flashing, but was getting no devices found. Today they aren't flashing, but I'm still getting no devices found when I run

sudo java -cp ZtexBTCMiner-121126.jar BTCMiner -host[hostinfo] -u[userinfo] -p[password]

This is my first experience trying to mine from command line... kudos to you all that know what you're doing, because I feel like I have no idea what's going on.
BR0KK
Hero Member
*****
Offline Offline

Activity: 742



View Profile
July 02, 2013, 09:25:29 PM
 #616

You need libusb to talsk to the boards.

Whats the lsusb printout:
Quote
[minepeon@minepeon ~]$ lsusb
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp. LAN9500 Ethernet 10/100 Adapter / SMSC9512/9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 045: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light
Bus 001 Device 040: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light
Bus 001 Device 084: ID 221a:0100  
Bus 001 Device 096: ID 221a:0100  
Bus 001 Device 095: ID 221a:0100  
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 035: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 046: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 036: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light
Bus 001 Device 037: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light
Bus 001 Device 038: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 061: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 101: ID 221a:0100  <-- Ztex 1.15y
Bus 001 Device 059: ID 221a:0100  
Bus 001 Device 060: ID 221a:0100

try to start BTCMiner with the "-i" option. It asks you for pool, pasword and login (you do not need them) and then it displays all connected boards (if working)

Provide that printout

objectnotfound
Newbie
*
Offline Offline

Activity: 20


View Profile
July 09, 2013, 07:09:06 PM
 #617

Sorry for the delayed response! I didn't see a reply. for some reason.

Here's the printout.

ubuntu@ubuntu:~/Downloads$ lsusb
Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 003: ID 05ac:850b Apple, Inc.
Bus 002 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 001 Device 005: ID 0781:5530 SanDisk Corp. Cruzer
Bus 001 Device 006: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard
Bus 002 Device 003: ID 05ac:8403 Apple, Inc. Internal Memory Card Reader
Bus 002 Device 004: ID 05ac:8242 Apple, Inc. IR Receiver [built-in]
Bus 002 Device 005: ID 046d:c52f Logitech, Inc. Wireless Mouse M305
Bus 001 Device 007: ID 05ac:8215 Apple, Inc. Bluetooth USB Host Controller
Bus 001 Device 010: ID 05ac:0220 Apple, Inc. Aluminum Keyboard (ANSI)

BTCMiner with '-i' produces no connected devices.

Edit: I'm running Ubuntu 13.04 on an iMac, booting and running Linux from a flash drive. I downloaded the .jar from ztex - am I missing something? Should the fans automatically kick on when I plug it in? Should the LEDs flash?
BR0KK
Hero Member
*****
Offline Offline

Activity: 742



View Profile
July 10, 2013, 06:28:42 PM
 #618

The Fans should run and the LEDs should be on (Green). If they are configured they are off.

Did you follow the guide on the Ztex homepage?

Is your hub powered?
Is it a brand or a cheap one? (Same for the Cable)

Did you install the right libusb (cgminer and BTCMiners are different)

objectnotfound
Newbie
*
Offline Offline

Activity: 20


View Profile
July 11, 2013, 06:19:23 PM
 #619

The Fans should run and the LEDs should be on (Green). If they are configured they are off.

Did you follow the guide on the Ztex homepage?

Is your hub powered?
Is it a brand or a cheap one? (Same for the Cable)

Did you install the right libusb (cgminer and BTCMiners are different)

All I really saw on their page (http://www.ztex.de/btcminer/) was "All files required are packed into a single jar archive which can be downloaded from the download section and runs under Linux and Windows," which I downloaded and ran the command they supplied while in the folder. I have the newest Java, but I'm not sure how you 'install' libusb exactly, unless there's more than the apt-get command.

I think the board is faulty though, I couldn't get it to even made the LEDs come on when I plugged it in, and none of the fans kicked on.
BR0KK
Hero Member
*****
Offline Offline

Activity: 742



View Profile
July 11, 2013, 07:12:02 PM
 #620

The Fans should run and the LEDs should be on (Green). If they are configured they are off.

Did you follow the guide on the Ztex homepage?

Is your hub powered?
Is it a brand or a cheap one? (Same for the Cable)

Did you install the right libusb (cgminer and BTCMiners are different)

All I really saw on their page (http://www.ztex.de/btcminer/) was "All files required are packed into a single jar archive which can be downloaded from the download section and runs under Linux and Windows," which I downloaded and ran the command they supplied while in the folder. I have the newest Java, but I'm not sure how you 'install' libusb exactly, unless there's more than the apt-get command.

I think the board is faulty though, I couldn't get it to even made the LEDs come on when I plugged it in, and none of the fans kicked on.


What does the Powersupply sticker say...

To run mine i need 12V 5A at least (laptop grade).


But the printout displays nothing like mine so the board is not recognized..... Could be USB, could be Power issues....


Do you have a computer at your place with a normal atx power supply and a spare 5,25 Molex (or anything else that has yellow and black cables <12V, Neutral>). Then you could provide the board with power over the proprietary connector (mine are black and i think the fake ztex boards do have a green one).

There is a tutorial on the ztex page. 

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!