So with the oncoming ASIC tsunami, which coins should be the best bet for small miners with USB miners and Jally

Can you be so kind to please post the code to the modified firmware, since I want  to test my Jally at speeds "9" and using all engines.

Is there no way BFL can pull up its socks and increase production rates?

Hold on cowboy,

let's get an open-source, crowd sourced, asic developed instead, and convince intel or glofo to manufacture it for us. I donot see any other means to stop the AM tsunami.

I would get a voltmeter and check the psu voltage output.

So does the average hashrate reported by cgminer considers hw error or do we have to account for hw errors by some other method?

I bought my AVR DRAGON from Newark. Very reliable and fast shipping. $50 + tax + $5 shipping.

http://www.newark.com/atmel/atavrdragon/in-ckt-debug-prog-jtag-spi-for/dp/68T2063?Ntt=avr+dragon

+1

okay, corrected. It's from BFL for USD 308

Just wanted to see if it would make sense to order that Jally from BFL website for USD 308 soon.

Ordered the 25 GH/s Bitcoin Miner BF0025G for    $1,283.00, since it probably will use the same board(s) as the Jalapeño, and a bunch of Jallys did ship a while back.

great thanks! used the python api-example.py code.

 python api-example.py stats

{u'STATUS': [{u'STATUS': u'S'    u'Msg': u'CGMiner stats'        u'Code': 70     u'When': 1372553376     u'Description': u'cgminer 3.3.1'}]      u'STATS': [{u'Temp2 Max Time': 1372553345       u'Temp1 Max': 33.0      u'Min': 99999999.0       u'Que Watermark': 32    u'Driver': 2    u'Firmware': u'1.2.5'   u'Flush ID': 0  u'Scan Sleep': 891      u'Results Sleep': 100   u'Que Full': 36         u'Overheat': False      u'Work Queued': 37      u'Max': 0.0      u'Result ID': 251       u'Vmain': 12.398        u'USB Pipe': u'0'       u'Elapsed': 204         u'Vcc1': 3.846  u'Vcc2': 0.993  u'Flushed': False       u'Chips': u'(null)'     u'Wait': 0.0    u'Que Low': 8   u'STATS': 0      u'Calls': 0     u'Que Size': 40         u'Work Complete': 420   u'Temp1 Max Time': 1372553224   u'ID': u'BAJ0'  u'Work ms': 954         u'Temp2 Max': 45.0      u'Temp2': 42.81         u'Temp1': 32.41         u'GetInfo': u'DEVICE: BitFORCE SC0x0aFIRMWARE: 1.2.50x0aIAR Executed: NO0x0aCHIP PARALLELIZATION: YES @ 20x0aQUEUE DEPTH:400x0aPROCESSOR 3: 15 engines @ 319 MHz -- MAP: FFFE0x0aPROCESSOR 7: 13 engines @ 326 MHz -- MAP: F5FE0x0aTHEORETICAL MAX: 9023 MH/s0x0aENGINES: 280x0aFREQUENCY: 291 MHz0x0aXLINK MODE: MASTER0x0aCRITICAL TEMPERATURE: 00x0aXLINK PRESENT: NO0x0aOK0x0a0x00'}  {u'Temp2 Max Time': 1372553347  u'Temp1 Max': 31.0      u'Min': 99999999.0      u'Que Watermark': 32     u'Driver': 2    u'Firmware': u'1.2.5'   u'Flush ID': 0  u'Scan Sleep': 913      u'Results Sleep': 100   u'Que Full': 36         u'Overheat': False      u'Work Queued': 37      u'Max': 0.0     u'Result ID': 249        u'Vmain': 12.097        u'USB Pipe': u'0'       u'Elapsed': 204         u'Vcc1': 3.404  u'Vcc2': 0.987  u'Flushed': False       u'Chips': u'(null)'     u'Wait': 0.0    u'Que Low': 8   u'STATS': 1     u'Calls': 0      u'Que Size': 40         u'Work Complete': 372   u'Temp1 Max Time': 1372553328   u'ID': u'BAJ1'  u'Work ms': 954         u'Temp2 Max': 43.0      u'Temp2': 40.98         u'Temp1': 30.11         u'GetInfo': u'DEVICE: BitFORCE SC0x0aFIRMWARE: 1.2.50x0aIAR Executed: NO0x0aCHIP PARALLELIZATION: YES @ 20x0aQUEUE DEPTH:400x0aPROCESSOR 3: 13 engines @ 286 MHz -- MAP: FFE60x0aPROCESSOR 7: 15 engines @ 284 MHz -- MAP: FFFE0x0aTHEORETICAL MAX: 7978 MH/s0x0aENGINES: 280x0aFREQUENCY: 291 MHz0x0aXLINK MODE: MASTER0x0aCRITICAL TEMPERATURE: 00x0aXLINK PRESENT: NO0x0aOK0x0a0x00'}  {u'Min': 99999999.0     u'Work Roll Time': 0    u'Work Can Roll': False         u'Work Diff': 10.0       u'Net Bytes Recv': 17219        u'Times Recv': 271      u'Times Sent': 263      u'Max': 0.0     u'Elapsed': 204         u'Pool Min': 99999999.0         u'Min Diff': 1.0        u'Work Had Expire': False       u'Wait': 0.0     u'STATS': 2     u'Calls': 0     u'Bytes Sent': 30881    u'Pool Max': 0.0        u'Max Diff': 11.0       u'ID': u'POOL0'         u'Work Had Roll Time': False    u'Pool Calls': 0        u'Net Bytes Sent': 31610        u'Pool Av': 0.0  u'Bytes Recv': 17219    u'Max Diff Count': 443  u'Pool Attempts': 0     u'Pool Wait': 0.0       u'Min Diff Count': 219}         {u'Min': 99999999.0     u'Work Roll Time': 0    u'Work Can Roll': False         u'Work Diff': 1.0        u'Net Bytes Recv': 124376       u'Times Recv': 2        u'Times Sent': 2        u'Max': 0.0     u'Elapsed': 204         u'Pool Min': 99999999.0         u'Min Diff': 1.0        u'Work Had Expire': False        u'Wait': 0.0    u'STATS': 3     u'Calls': 0     u'Bytes Sent': 232      u'Pool Max': 0.0        u'Max Diff': 1.0        u'ID': u'POOL1'         u'Work Had Roll Time': False    u'Pool Calls': 0        u'Net Bytes Sent': 1236  u'Pool Av': 0.0         u'Bytes Recv': 123936   u'Max Diff Count': 1    u'Pool Attempts': 0     u'Pool Wait': 0.0       u'Min Diff Count': 1}   {u'Min': 99999999.0     u'Work Roll Time': 0    u'Work Can Roll': False u'Work Diff': 1.0        u'Net Bytes Recv': 1989         u'Times Recv': 3        u'Times Sent': 3        u'Max': 0.0     u'Elapsed': 204         u'Pool Min': 99999999.0         u'Min Diff': 1.0        u'Work Had Expire': False        u'Wait': 0.0    u'STATS': 4     u'Calls': 0     u'Bytes Sent': 464      u'Pool Max': 0.0        u'Max Diff': 1.0        u'ID': u'POOL2'         u'Work Had Roll Time': False    u'Pool Calls': 0        u'Net Bytes Sent': 1348  u'Pool Av': 0.0         u'Bytes Recv': 692      u'Max Diff Count': 1    u'Pool Attempts': 0     u'Pool Wait': 0.0       u'Min Diff Count': 1}]  u'id': 1}

Okay so i guess  i need to compile the sample api code. thanks

Then how can I get the API info? Can it be done with a browser URL? Thanks

Just tweaked the firmware. changes ln 101 in std_defs.h


New Speeds  

Before Jalapeno 0: 8.6GH/s : After Jalapeno 0: 9.2GH/s
Before Jalapeno 1: 7.7GH/s : After Jalapeno 1: 7.9GH/s

Btw the correct terminology for the required driver is Torx T9 

How can I get the stats of engines? I would want to know that. Thnks

those are just for use during flashing. It will kill the Jally for sure if used as a replacement after flashing.  

Just tweaked the firmware. changes ln 101 in std_defs.h


New Speeds  

Before Jalapeno 0: 8.6GH/s : After Jalapeno 0: 9.2GH/s
Before Jalapeno 1: 7.7GH/s : After Jalapeno 1: 7.9GH/s

Before Jalapeno 0: 6.2GH/s : After Jalapeno 0: 8.6GH/s
Before Jalapeno 1: 5.5GH/s : After Jalapeno 1: 7.7GH/s

Setup for flashing Rev 2 Jalapeno with all aluminum heatsink.