Um, Kano has many times made a point of saying that your code (and only your code) does not infringe in the slightest and for that reason has allowed it to be used since day-1 of him starting the solo mining site. Once there was finally proof that your code actually correctly finds & reports block finds he also now allows it on the main pool.

Or just google 'fan simulator circuit' or 'fake fan signal' to get prints or information about it. One nice discussion is here

The resistance that the pot is set to is pretty meaningless without knowing what the rest of the spoofer circuit is using. The pot is part of a timing circuit and without knowing what that circuit is...

What you need to measure is the duty cycle and frequency of the pulse train being sent. Best way is with either a multi-meter that has those functions, use an oscilloscope, or -- measure the average DC voltage you see between the yellow tach wire and the black wire (common). You can assume that 100% = 12v. That will at least let you calculate the duty cycle different fans speeds give but you still need to find out the baseline frequency, as I mentioned before, 1kHz is common.

Fans and fan emulators do not use resistance (ohms) for control. The are changing the duty cycle of a pulse train to report and set speed. I believe most use 1kHz with a 10% = slow speed to 100% = full speed duty cycle.

Kano and/or Sidehack would have to chime in to confirm, but I think yer main problem in communicating is the lack of a driver that speaks the chips language. The driver is a chip makers Secret Sauce. I do know that Bitmains S9 source code *is* on the internet somewhere so hopefully it would have the driver code as well. Drivers for the early sticks that Sidehack produced were all using drivers and code that Bitmain (eventually) released and was reused by -vh for early Compaq's.

Kano wrote the driver for Sidehack's Compaq'F' (S17 chip) after Sidehack was able to trace/figure out the signaling going on in a working S17 and then refreshed -vh's earlier code as part of the Compaq'F' work and cgminer update to include all the drivers.

Just how are you interfacing with it? trying a simple JTAG serial connection into some IDE?

The last fully open source firmware for Antminers was done by Kano for their S1-S3 Antminers. AFAIK he has it in his git along with the latest cgminer code he did for the CompacF. After that BM hacked & slashed their version of his code into what is used in all of their miners since.

The source code for a S9 *is* out there but...

Someone been living under a rock?
Many existing threads about their different miners in the Hardware area, just use 'Avalon' or 'Canaan' as a search term. Various models were the A6, A721, A741, A821, A841, A941 (their only clunker but the 1st 10nm miner to market beating Bitmain by 3 months). Starting with the A10xx they followed MicroBt & Bitmain and changed to using built-in PSU to raise efficiency. For a very long time their Avalon 841 has been the most durable miner ever made.

You should also know that when running older Compacs along with the 'F', those older ones should be ran under a separate instance of cgminer because of radical differences in performance between them and the 'F'. Can still all be on one hub, just need the different instance of cgminer for all of them to be happy.

Yer 1st Merit given for updating us with your status.
Way too many folks find a solution and then never let us know their problem was solved...

As Kano said, even the big pools lose orphan races. If your connection to the network is even just 2x slower than theirs one has just increased the odds against getting a block before someone else does.

Yes there is a *chance* that if against already incredible odds one *does* find a block when solo mining to their own node, personally I'd be heartbroken to soon after see that another miner with better connections to the BTC network beat me in the race for my block to be the one that is 1st to be confirmed & built upon...

Bump.

Um, look at the home page... (sorry -ck but this needs to be replied to properly...) Sure looks like contact info to me

A) Kano pool is ran by Kano and NOT -ck who runs solo.ckpool!
Yes, in the beginning Kano and -ck worked together on cgminer and the ckpool code and then started & ran the now defunct ckpool but they parted company long long ago in 2014.

B) The Kano pool thread is disused because very few folks have issues that need to be reported there and most now use Disccord. If you repost there (pool thread) and you will get better response.

That said, have you changed the miner firmware being used? Most of the aftermarket firmwares violate the cgminer GPL so they are automatically banned from Kano's pool. The one exception is Braiins, they are allowed because it is clean code that is not based on cgminer. Considering that Kano is the 'other' main developer of cgminer he rightfully takes great umbrage towards those who refuse to publish their code modifications like the GPL requires them to to.

edit: BTW, KanoPool accepts connections from *anywhere* on the planet with no restrictions (aside from the 3rd party firmware thing).

Folks, I hope you have paid attention to Canaan's Terms page, specifically the part about Warranty repairs:Because Canaan no longer uses Authorized Distributors that applies to ALL companies that are acting as resellers or unofficial distributors of their mining equipment.

The 'Block Found' flag is a part of the near universally used cgminer API that Kano wrote. Now as to how much of that API is recognized by the software that the Apollo uses (not cgminer nor directly based on it) is another story. One would would think that an equivalent command exists  for it...

Odds are -ck deleted it from his pool thread because:
a) your post had nothing to do with the solo pool itself that he runs and -ck really wants to have nothing more to do with supporting the publicly available ckpool code. Hell, last year ck was considering closing the solo pool... It took some fools folks donating to him to pay for the servers that made him keep it open. Turns out it was good that he took them up on the offer considering he made a nice bit of coin off of his 2% cut of the several blocks the folks in the pool found since then... As he posted in the pool thread the other day it was more than enough to pay for the next year of running the pool

b) Since he locked the ckpool software thread (and his git for it) long ago you should have opened a new topic in the Mining Software area - not the pools area.

That said, the ckpool software is not something that you just download, install, and run. There's good reason that the folks behind Laurentia pool paid -ck a hefty consultant fee to set it up for their project.

There are a lot of tweaks (settings) that the operator must do to even be able to run it some of which are not pre-coded - you have to know how/what to edit and/or add code to suit your needs. Um, things like having the block payout automatically sent to the main recipient be it a solo miner or a pool wallet for distribution to the pool members + a % of total rewards that you set to the pool operator wallet. That starts the history of newly generated coins with a perfectly clear record of where the new coins came from and were they were 1st sent to start their life as part of the BTC blockchain.
BTW: that initial identification of the 'parents' the coins went to is an entirely different thing vs the diversion of hash rate that several hacked miner firmwares use to enforce the fee for using their hacked (which by being closed source, violates the cgminer GPL) firmware.

Odds are the various readme files cover the bulk of you have to do.

I do hope that you were saying that as an exaggerated point... Miner chips simply cannot match the revenue generated that Foundries make by producing cutting/bleeding edge chips for just about everything NOT related to mining.

As I've often said before, the only reason that TSMC, Global, UMC and Samsung Foundries produced advanced-node miner chips so cheaply was to use them to fine tune their low nm node chip production processes. Miner chips are dirt-simple and very forgiving of production faults making them a perfect process refinement testbed. Once those processes were nailed down and had yields good enough for their main customers to run full speed with their very much more complex and non-fault tolerant chip designs- which produce immense profits for the Foundries - the advanced equipment availability needed for mining chip production was slashed and chip prices for the remaining allocation raised. Foundries know their cash-cow markets very well and making mining chips ain't one of them.

Again, Canaan is NOT new.
They produced the 1st ASIC chip back in late 2012 and released the 1st ASIC-based miner in 2013
IMHO Canaan generally produces the best miners. While their Avalon miners may not be quite as efficient as Bitmain's Ants are, the Avalons' are far far more reliable.

heh...
In other words a modern version of the 'lugable' 1st mobile(ish) PC
https://en.wikipedia.org/wiki/Osborne_1

That's too high. Look at your other sticks and for a start, set the pot on problem one to the same angle.
Looking at the pot like a clock, the default is for the flat to be *just* past being in line with the long edge of the stick - call it 15-16 minute position. What you describe I would call the 30 min mark.
I run mine with it set to 20-25 min mark and the stick is quite happy at 500MHz pulling 2.8A.