I've only tested 1 at a time on my Pi, but we're running five per USB bus (10 per machine) on the old Dell 755 testers. If a current model Pi has comparable horsepower to half an office PC from like 2010 you'd be fine. Given a Pi will run something like 12-14 Compac F, 3-4 R909 shouldn't be difficult.

By the way, 1.5TH is the baseline spec. The last batch off testers were running 1.6-1.7TH and still had headroom. Kano and I have both tested units at 2TH and up. Of course the top-end of your units will be dependent on the hardware behaving nicely but I bet you could get 3.6TH just from the R909s.

It's a brand-new product and we busted our butts to get the assembly line up to speed in time for the first batches to be out for Christmas, which is still 19 days off. Reseller stock requests are being filled right now, so they'll be "in stock" with resellers in one to two weeks.

There was a change in the USB connector from the original batch to all successive batches (2022 models). In testing, I've had *fewer* issues with mechanically reliable connections with the new jack than the old one, and if there's an issue in testing it gets replaced. I have no experience with the issues some are seeing, and no solution except using a different meter.

There was a change in the USB connector from the original batch to all successive batches (2022 models). In testing, I've had *fewer* issues with mechanically reliable connections with the new jack than the old one, and if there's an issue in testing it gets replaced. I have no experience with the issues some are seeing, and no solution except using a different meter.

The two are effectively exactly the same but for one difference, a slightly higher pot voltage setting on the newer ones.

With the old hubs port D and 1 is limited to 2A total so I see no reason why port 1 couldn't be used to daisy chain a few hubs together since I certainly wouldn't recommend port 1 for mining with the Compac F's.

If you are using the older version of the hub, use port 1 to daisy chain a few of the hubs together. That seems to have worked for me

It just indicates the performance issue, which process (hashing out) less block header data within the expectation of usb stick's capability. Then, chance to hit a BTC is reduced. (32:16) indicate, it took 32 milliseconds average time to process a header data. (8:16) indicate, it took 8 milliseconds average time for hashing process (sub tasks: check status of usb stick and process, obtain header data, format data, write data to usb stick, etc). Sometime, checking usb status cost time when usb stick does not work well.
 
cgminer is an multiple threads program. More usb sticks are used, more process threads will be created and running there, which compete limited system resources. You can test if a PI 4 computer can handle how many of compacf sticks without impact the performance of whole system to achieve (8:16).

 

^^ Please learn how to use quotes correctly... You've been here long enough to know how to not make the entire post look like a quote.
As for the CPU stuff... unless you are running dozens of sticks from 1 computer a RasPi does just fine.

Thank you for the informations.
I'm adjusting my sticks now, I managed to make them work on the usbs that were disabled before, it was a problem with the current, adjusting with the screw behind the stick was possible to solve the problem.

About the parameter (28:14) I realized that it is related to the mhz, because the higher the frequency, the lower this value is, is this correct?

turn right or clock turning,  increse current => increase frequence, then, increse hashing. But, increase hot?

There is another indicator (7:20) on display screen in cgminer, which rules out the performance of compacF stick miner.
It often change and has more impact on hash rate on this stick miner.
(7 : 20) got more hashrate, faster.
(16: 20) got less hashrate, slower.