ztex_ufm1_15d3-04A32E1A99: Error: String index out of range: 4: Disabling device
I noticed this error when I briefly tried running with EMC. I didn't have time to fully test it out, but I just thought I didn't have the pool info correct. Any thoughts?
EDIT: This appears to be fixed with the latest 120208 release.
I had a chance to test the cluster yesterday, and I just want to summarize my experience with ztex. I hope I am not stating what everybody already knows:
Currently, with the 120208 release, I am able to run my 20-board test cluster with d1, d3, and d3a. I have been testing with deepbit for the last week or so, and the rate has been very stable at around 4GH/S. It will range between 3900 to 4100, but for the most part it is around 4,000 to 4,050 (60 min average per deepbit). Most of the boards are running at 200 to 208 MHz. Power, measured with a power meter at the outlet is 245 watts (APC BR1500, Corsair Ax1200 gold, core i7 2600k, 4gig ram, 32G SSD, win 7 64, jre64).
2012-02-09T23:31:04: bus-0-0: ztex_ufm1_15d3-2012-L1-A1: f=204.00MHz, errorRate=0.41%, maxErrorRate=1.86%, hashRate=203.2MH/s, submitted 16 new nonces, luckFactor=0.96
2012-02-09T23:31:04: bus-0-0: ztex_ufm1_15d3-2012-L1-A2: f=200.00MHz, errorRate=0.00%, maxErrorRate=0.31%, hashRate=200.0MH/s, submitted 11 new nonces, luckFactor=1.02
2012-02-09T23:31:04: bus-0-0: ztex_ufm1_15d3-2012-L1-A3: f=200.00MHz, errorRate=0.00%, maxErrorRate=0.25%, hashRate=200.0MH/s, submitted 14 new nonces, luckFactor=1.02
2012-02-09T23:31:04: bus-0-0: ztex_ufm1_15d3-2012-L1-A4: f=200.00MHz, errorRate=0.00%, maxErrorRate=1.05%, hashRate=200.0MH/s, submitted 11 new nonces, luckFactor=0.99
2012-02-09T23:31:04: bus-0-0: ztex_ufm1_15d3-2012-L1-B1: f=208.00MHz, errorRate=0.07%, maxErrorRate=0.67%, hashRate=207.8MH/s, submitted 12 new nonces, luckFactor=1.00
2012-02-09T23:31:04: bus-0-0: ztex_ufm1_15d3-2012-L1-B2: f=208.00MHz, errorRate=1.23%, maxErrorRate=1.94%, hashRate=205.4MH/s, submitted 8 new nonces, luckFactor=0.96
2012-02-09T23:31:04: bus-0-0: ztex_ufm1_15d3-2012-L1-B3: f=200.00MHz, errorRate=0.04%, maxErrorRate=0.50%, hashRate=199.9MH/s, submitted 18 new nonces, luckFactor=1.06
2012-02-09T23:31:04: bus-0-0: ztex_ufm1_15d3-2012-L1-B4: f=204.00MHz, errorRate=0.12%, maxErrorRate=1.33%, hashRate=203.7MH/s, submitted 12 new nonces, luckFactor=0.92
2012-02-09T23:31:04: bus-0-0: ztex_ufm1_15d3-2012-L1-B5: f=204.00MHz, errorRate=0.04%, maxErrorRate=1.20%, hashRate=203.9MH/s, submitted 17 new nonces, luckFactor=1.04
2012-02-09T23:31:04: bus-0-0: ztex_ufm1_15d3-2012-L1-B6: f=200.00MHz, errorRate=0.27%, maxErrorRate=0.54%, hashRate=199.5MH/s, submitted 17 new nonces, luckFactor=1.03
2012-02-09T23:31:04: bus-0-1: ztex_ufm1_15d3-2012-L1-A0: f=204.00MHz, errorRate=0.00%, maxErrorRate=0.54%, hashRate=204.0MH/s, submitted 19 new nonces, luckFactor=1.04
2012-02-09T23:31:04: bus-0-1: ztex_ufm1_15d3-2012-L1-A5: f=200.00MHz, errorRate=0.30%, maxErrorRate=1.48%, hashRate=199.4MH/s, submitted 13 new nonces, luckFactor=0.96
2012-02-09T23:31:04: bus-0-1: ztex_ufm1_15d3-2012-L1-A6: f=200.00MHz, errorRate=0.00%, maxErrorRate=0.64%, hashRate=200.0MH/s, submitted 10 new nonces, luckFactor=0.96
2012-02-09T23:31:04: bus-0-1: ztex_ufm1_15d3-2012-L1-A7: f=204.00MHz, errorRate=1.86%, maxErrorRate=2.95%, hashRate=200.2MH/s, submitted 20 new nonces, luckFactor=1.07
2012-02-09T23:31:04: bus-0-1: ztex_ufm1_15d3-2012-L1-A8: f=204.00MHz, errorRate=0.00%, maxErrorRate=0.28%, hashRate=204.0MH/s, submitted 16 new nonces, luckFactor=0.99
2012-02-09T23:31:04: bus-0-1: ztex_ufm1_15d3-2012-L1-A9: f=204.00MHz, errorRate=0.00%, maxErrorRate=0.32%, hashRate=204.0MH/s, submitted 12 new nonces, luckFactor=1.00
2012-02-09T23:31:04: bus-0-1: ztex_ufm1_15d3-2012-L1-B0: f=204.00MHz, errorRate=0.29%, maxErrorRate=1.46%, hashRate=203.4MH/s, submitted 11 new nonces, luckFactor=0.97
2012-02-09T23:31:04: bus-0-1: ztex_ufm1_15d3-2012-L1-B7: f=204.00MHz, errorRate=0.00%, maxErrorRate=0.32%, hashRate=204.0MH/s, submitted 13 new nonces, luckFactor=1.05
2012-02-09T23:31:04: bus-0-1: ztex_ufm1_15d3-2012-L1-B8: f=204.00MHz, errorRate=0.00%, maxErrorRate=0.58%, hashRate=204.0MH/s, submitted 13 new nonces, luckFactor=1.14
2012-02-09T23:31:04: bus-0-1: ztex_ufm1_15d3-2012-L1-B9: f=200.00MHz, errorRate=0.45%, maxErrorRate=1.45%, hashRate=199.1MH/s, submitted 18 new nonces, luckFactor=1.08
2012-02-09T23:31:04: bus-0-0: poll loop time: 74ms (USB: 2ms network: 72ms) getwork time: 189ms submit time: 197ms
2012-02-09T23:31:04: bus-0-1: poll loop time: 75ms (USB: 2ms network: 73ms) getwork time: 187ms submit time: 194ms
2012-02-09T23:31:04: Total hash rate: 4045.6 MH/s
2012-02-09T23:31:04: Total submitted hash rate: 4076.4 MH/s
-Boards were shipped the day after payment. Shipping took 4 days from Germany to California, including 2 days at customs.
-The boards were well packaged.
-Assembly of the heatsink was straight forward (I used arctic silver for the thermal paste instead of the included stock paste)
-The power supply is probably the most involved part of the assembly. We decided to solder the wires and the connectors (anal retentiveness acting up) after initially using the terminals per ztex guide, which also works.
There was a bug in the firmware programming code which is now fixed. I think swapping out the pentium g620 for a core i72600k also helped. The programming for 20 boards used up to 4 threads so I would recommend anyone running large clusters to use a cpu capable of handling a few threads. It will run on the g620 without errors, but it maxes the cpu. EDIT: it maxes the g620 during the initial programming (uses 4 threads on the 2600k). During actual mining, the software barely uses the cpu and a g620 is more than sufficient. /EDIT
2nd EDIT: As of the newly release 120208.jar, programming does not utilize much cpu at all. So a pentium g620 or a similar sempron should have no problem running a good-size cluster.
-Ambient temperature is about 75 degree F (sorry it is California) and heatsink temperature is around 85 F measured with a probe.
-Mining has been very stable on deepbit, which is key for me. Plan now is to try the other pools. Is P2Pool running fine now?
Overall, I am very impressed with ztex's professional work and his boards. He has been very responsive and I am definitely looking to purchase more boards from him. Sorry to take up this space on the forum post, but I just thought I'd leave a good word for ztex and his work.