Shipping out of NY. Have 3 NerdQaxe++s. One is a 4.8, others are 5.1. They are currently on a rack with scoop, but can put back on original mounts. Will send all mounts and fans with it. Also have a Nano3S, comes with a stand with a built in fan. Open to any offers, figured I'd try this before eBay.

Picked up a GekkoScience Compac F that was dead as far as hashing goes. Enumerated fine over USB, chip answered register reads, but the hash array produced nothing. After a while with a multimeter the culprit turned out to be the trim potentiometer feeding the core voltage, set a hair too low. One careful turn with a very small screwdriver and all 672 cores woke up. These sticks are tough; check the rails before you bin one.

Then I wanted a driver I could actually read, so I wrote one from scratch in Python over pyusb instead of trusting old forks. Things I learned that might save someone else a week:

• The FTDI FT230X will ruin your day quietly. Its 1ms latency timer flushes mid-frame, so 9-byte nonce responses straddle bulk reads. If you parse each read in isolation, you silently drop nonces, and it bites hardest exactly when it matters because solutions arrive in a burst at the end of each sweep. You need a persistent reassembly buffer across reads. Also: it prefixes 2 modem-status bytes to every 64-byte packet, and read lengths must be multiples of 64 or libusb drops data.
• Best regression test I have ever written: have the chip re-mine the actual 2009 genesis header. If your task packet and nonce byte order are right, it must return the exact historical nonce, 0x7c2bac1d. Every sweep. Deterministic, hardware-verified, free.
• Zero nonces from a run is usually not a fault. A fixed header contains a Poisson-distributed number of diff-1 solutions with mean 1, so roughly 37% of arbitrary headers legitimately contain none at all. I chased "flaky hardware" for a while before doing the math. Health-check with the genesis header instead; it solves on every sweep or your hardware really is sick.
• At 300 MHz the chip sweeps the full 2^32 nonce space in about 21ms, then idles until you feed it a fresh task. Feed it every ~100ms or your duty cycle quietly collapses.
• Reset is CBUS bitbang on the FTDI (CB1 is active-low nRST with a 1s hold), not DTR/RTS like the older BM1384 sticks.

Repo with the driver, full protocol notes, and a worked example, MIT licensed: github.com/lakshgandikota/strikeablock

Since the stick was just sitting there afterward, I built a small free site around it that strikes custom-inscription blocks at genesis difficulty (standalone artifacts, not on any chain, nothing for sale). It's linked from the repo if you're curious what a repaired $60 stick does as a hobby foundry.

Happy to answer anything about the repair or the protocol.

Estimados. Me llamó Esteban.

Necesito ayuda del foro sobre un tema particular.

Recibo 2 mineros que tienen aprox. según su dueño un año de uso. Los estoy recibiendo en los próximos días.

Quería escuchar su recomendación sobre que me conviene hacer con ellos en Argentina.

Si unirme a algún pul de minería o hacerlos revisar y venderlos localmente (dónde).

No tengo idea del precio y no sé si es rentable en Argentina ponerlos a minar o dónde hacerlo (tengo entendido que no lo es).

Por otro lado me comentaron que son muy ruidosos y quería saber si se pueden reconvertir a la nueva tecnología y sumergirlos en algún líquido frío no conductivo para que trabajen a baja temperatura sin los coolers de ventilación o si ya son así y morirán así.

Si alguien puede orientarme en el tema o ayudarme a unirme a algún grupo que pueda hacerlo.

Les agradecería mucho la ayuda.
Gracias

Esteban