Pages:
Author

Topic: GekkoScience has a new stickminer that does 300+GH - page 44. (Read 22568 times)

hero member
Activity: 882
Merit: 5834
not your keys, not your coins!
One could de-solder it, test it, & determine it' value.
So if it screwed up it could be replaced.
PITA for sure, but . . .

BTW, not surprised to hear that it sometimes de-solders itself. There's a reason that on the 17 series hash boards Bitmain puts heatsinks on both sides of the pcb. High power consumption SMDs regularly thermally sink thru their power connections on the underside of the chip.

I have another stick which is fine; so I might actually do this, not sure yet whether to take that risk. I still hope for a response from GekkoScience team. Not sure why not to release this info since it's so trivial to RE.
newbie
Activity: 6
Merit: 0
Sure looks like a power supply decoupling cap to me since there is a polarity mark on the largest component on the backside of the hash chip PCB (2 pin component).
Right - makes sense, thanks guys! I just assumed diode since it has the distinct polarity mark which diodes also have. But it seems a cap makes more sense in this part of the circuit.
I'm surprised your works without the cap in place, @Biffa! Then I'll see if I can get it working simply without that.

Would still be great to hear what component this is (specifications) so it can be replaced if it is missing or blows / melts like in that case.

One could de-solder it, test it, & determine it' value.
So if it screwed up it could be replaced.
PITA for sure, but . . .

BTW, not surprised to hear that it sometimes de-solders itself. There's a reason that on the 17 series hash boards Bitmain puts heatsinks on both sides of the pcb. High power consumption SMDs regularly thermally sink thru their power connections on the underside of the chip.
hero member
Activity: 882
Merit: 5834
not your keys, not your coins!
Sure looks like a power supply decoupling cap to me since there is a polarity mark on the largest component on the backside of the hash chip PCB (2 pin component).
Right - makes sense, thanks guys! I just assumed diode since it has the distinct polarity mark which diodes also have. But it seems a cap makes more sense in this part of the circuit.
I'm surprised your works without the cap in place, @Biffa! Then I'll see if I can get it working simply without that.

Would still be great to hear what component this is (specifications) so it can be replaced if it is missing or blows / melts like in that case.
newbie
Activity: 6
Merit: 0
Cgminer does have provisions for temp monitoring, fan control, shut down, etc. but -- there needs to be a temp monitor of some sort to feed that info into cgminer and none of the Compacs have that. You could always look for RasPi projects that deal with temp control, mount a temp sensor to the heatsink and use it to simply switch off power to the sticks.

Stavroski, NotFuzzyWarm's solution is without a doubt the simplest way to garner temp monitoring.
In theory, if one could breakout pins 21-24 on the BM1397 hash chip one could garner a finer measurement of what one might call TJunc.

Please reference attached image: https://www.zeusbtc.com/Upload/image/202108/16280626681136747.JPG

Having said that I have no clue whether that is an analog or digital signals.
But it appears that Bitmain included temperature sensing into the chip/die.

Further, Bitmain uses the Ti TMP451AIDQFR temperature sensor on their 17 series hash boards to measure board temperature. Which are currently unavailable from any supplier anywhere in the USA (But may be found on eBay or Aliexpress). The data sheet may be found here: https://www.ti.com/lit/ds/symlink/tmp451.pdf?ts=1641066272554&ref_url=https%253A%252F%252Fwww.google.com%252F

This uses a simple 2 wire serial interface which on the Pi is easy to interface with. Soooo, if one epoxy'ed one to the heatsink . . . .

Hope this helps & provides some possibilities.

Pup




1397 and 1398 mostly look to be pin-compatible, but the documentation I have says they're not entirely so. 1398 operates on a much different V/I which makes it fairly non-suitable for single-chip operations. I've looked into it, and the main regulator engineering would be difficult and probably pretty inefficient. A series string like we did for the R606 would be a lot easier to manage. In any case, a direct chip swap from 1397 won't work.

Kinda' what I figured I hear. Butcha' don't know till you ask.

That accounts for what Bitmain calls "voltage domains" when troubleshooting hash chip chains on their boards.
And I can see the board engineering constraints on trying to maintain packaging on your USB Compac form factor.
But if one was willing to deviate from that form factor a tad .  .  .

Anyway, assuming one could supply the appropriate V/I to the chip do you believe Kano's 1397 driver would communicate w/ a 1398?
Is that something you've played with?

On a different note, I found these breakout PCB's for 1397/1398 prototyping & bought 5 of them (& D/L'ed the gerber files): https://www.pcbway.com/project/shareproject/Socket_BM1397.html
Figured I solder them up so I could socket them into a larger board to ring out the signals (multi channel o-scope) & test w/ Kano's driver merged into cgminer for testing/tweaking.

Was also thinking that if I swapped out the USB A for a USB C connector and fed it 20V @ 3A per USB C 3.2 / 3.1 specs it might make the main LDO engineering simpler to implement w/ "off the shelf" components. That also would decrease the current handling on a USB connector.

W/ a USB C 3.2 connector an APW 9 (14.5V-21V @ 170+ A or equivalent) could be used to supply trons to the USB power bus in a USB hub versus being limited to the 5V @ 3A USB A standard.

Curious to hear your thoughts.

Pup



Does anyone know the model number and / or parameters of the diode that is directly behind the mining chip (like on the opposite side of the PCB)?
I recently got my hands on a Compac F where that diode is missing. Would be sick to get it working!
Sidehack will have to chime in to confirm but I believe it is a capacitor -- not a diode. Somewhere further back in the thread there is talk about measuring the Vcore across it and it was referred to as a cap..

Sure looks like a power supply decoupling cap to me since there is a polarity mark on the largest component on the backside of the hash chip PCB (2 pin component).

[moderator's note: consecutive posts merged]
legendary
Activity: 3234
Merit: 1220
Does anyone know the model number and / or parameters of the diode that is directly behind the mining chip (like on the opposite side of the PCB)?
I recently got my hands on a Compac F where that diode is missing. Would be sick to get it working!
Sidehack will have to chime in to confirm but I believe it is a capacitor -- not a diode. Somewhere further back in the thread there is talk about measuring the Vcore across it and it was referred to as a cap..

Mine melted off when I first got one. Sidehack assured me its not a vital component and mine has been hashing away fine ever since.
legendary
Activity: 3822
Merit: 2703
Evil beware: We have waffles!
Does anyone know the model number and / or parameters of the diode that is directly behind the mining chip (like on the opposite side of the PCB)?
I recently got my hands on a Compac F where that diode is missing. Would be sick to get it working!
Sidehack will have to chime in to confirm but I believe it is a capacitor -- not a diode. Somewhere further back in the thread there is talk about measuring the Vcore across it and it was referred to as a cap..
hero member
Activity: 882
Merit: 5834
not your keys, not your coins!
Does anyone know the model number and / or parameters of the diode that is directly behind the mining chip (like on the opposite side of the PCB)?
I recently got my hands on a Compac F where that diode is missing. Would be sick to get it working!
newbie
Activity: 15
Merit: 1
Cgminer does have provisions for temp monitoring, fan control, shut down, etc. but -- there needs to be a temp monitor of some sort to feed that info into cgminer and none of the Compacs have that. You could always look for RasPi projects that deal with temp control, mount a temp sensor to the heatsink and use it to simply switch off power to the sticks.

Thanks - this is the info' I was after. Now I know the Compacs dont have any sort of temp sensing I will look into an external sensor from the Pi.

Thanks
Stav
legendary
Activity: 3822
Merit: 2703
Evil beware: We have waffles!
Cgminer does have provisions for temp monitoring, fan control, shut down, etc. but -- there needs to be a temp monitor of some sort to feed that info into cgminer and none of the Compacs have that. You could always look for RasPi projects that deal with temp control, mount a temp sensor to the heatsink and use it to simply switch off power to the sticks.
newbie
Activity: 15
Merit: 1
Hi all,

Does anyone know if there is a way to monitor the temp of the CompacF to prevent issues if the stick gets too hot, etc? Is there anything within CGMiner or on the board itself that looks at temps? I dont want my fan to fail and then the thing overheat and die when I am not in its vicinity. I want to be able to monitor the temp of the stick and write a script to shut CGMiner down if something goes wrong.

Thanks
Stav
legendary
Activity: 3374
Merit: 1859
Curmudgeonly hardware guy
1397 and 1398 mostly look to be pin-compatible, but the documentation I have says they're not entirely so. 1398 operates on a much different V/I which makes it fairly non-suitable for single-chip operations. I've looked into it, and the main regulator engineering would be difficult and probably pretty inefficient. A series string like we did for the R606 would be a lot easier to manage. In any case, a direct chip swap from 1397 won't work.
newbie
Activity: 6
Merit: 0
Quote
If one replaced the 1397 w/ a 1398 on the Compac F would your driver for CGminer work?
They appear pin compatible. Or are the comms too different?
I highly doubt a simple 'drop-in' replacement is possible. Looking at older chips data sheets it is obvious that Bitmain plays around with different timing specs for the internal circuits - none of them are the same. Since BM no longer releases the data sheets Sidehack had to manually debug the signals/commands and timing for the 1397 and then supplied that info to Kano to work into the driver.

Hey NotfuzzyWarm,

Long time no talk, the old, now defunct, PlanetCrypto here (forgot password & lost email account when we shut it down 5+ years ago).

Kinda' assumed there was a LOT of reverse engineering going on between the 2.
And likely only those 2, outta' the community, coulda' figured it out, given BM's tight lipped agenda & complete absence of documentation. (They don't even teach theory of operation to their repair techs in their school).

Currently running some 17's & 19's, have a hot air rework station & test gear to fix'em when they break & have a small inventory of BIN 1 1397's & 1398's (& have a source for more). Mostly retired & was looking for a winter project to play w/ on these long cold MN nights. Upgrading an F seemed like a nice challenge. I know w/ esoteric cooling the 1397's can be pushed to 900+ Mhz w/ CoreV tweaks. The 1398's w/ the same heat dissipation & tweaks, in theory, should be able to exceed 1TH/s each.

Back in the day, we did some prototyping w/ 2 phase immersion cooling w/ Novec engineered fluids. So was thinking 'bout building some small immersion tanks to handle the heat. Like we did w/ S3 boards: https://www.youtube.com/watch?v=fStHV_Q-x7s

Anyway, thanks for the response & be safe out there.
Pup
hero member
Activity: 2534
Merit: 623

Yes, I am using this:
Quote
sudo ./cgminer -o stratum+tcp://us-east.stratum.slushpool.com:3333  -u xxx.xxx -p xxxx --gekko-compacf-freq 200  --gekko-compacf-detect --suggest-d
iff 256

Read PAGE 4 of the thread. Try adding the “tune2” and “mine2” arguments. Also what hub are you using?

Thank you.  Yes, I had just created a conf file based on page 4 of this thread, with all the same settings [except pool, user and pass].
My USB hub is an Anker powered hub, but I will try an different one - power could be the problem

Yea that is most definitely the problem. I last used an anker hub for the original Compacs. They didnt like it so got the gekko hub. That seems to be the only one robust enough for the Ferraris.
legendary
Activity: 2746
Merit: 1181
sidehack, I never got the stick you promised me, what's up?
legendary
Activity: 3822
Merit: 2703
Evil beware: We have waffles!
Quote
If one replaced the 1397 w/ a 1398 on the Compac F would your driver for CGminer work?
They appear pin compatible. Or are the comms too different?
I highly doubt a simple 'drop-in' replacement is possible. Looking at older chips data sheets it is obvious that Bitmain plays around with different timing specs for the internal circuits - none of them are the same. Since BM no longer releases the data sheets Sidehack had to manually debug the signals/commands and timing for the 1397 and then supplied that info to Kano to work into the driver.
newbie
Activity: 6
Merit: 0
For linux I compile and build it on Ubuntu.
While that doesn't really matter too much, ubuntu is very simple to install.

Hi, oh smarter one than I,

If one replaced the 1397 w/ a 1398 on the Compac F would your driver for CGminer work?
They appear pin compatible. Or are the comms too different?

Just curious & thinking outside the box, a little.

Pup
newbie
Activity: 3
Merit: 0

Yes, I am using this:
Quote
sudo ./cgminer -o stratum+tcp://us-east.stratum.slushpool.com:3333  -u xxx.xxx -p xxxx --gekko-compacf-freq 200  --gekko-compacf-detect --suggest-d
iff 256

Read PAGE 4 of the thread. Try adding the “tune2” and “mine2” arguments. Also what hub are you using?

Thank you.  Yes, I had just created a conf file based on page 4 of this thread, with all the same settings [except pool, user and pass].
My USB hub is an Anker powered hub, but I will try an different one - power could be the problem
hero member
Activity: 2534
Merit: 623

Yes, I am using this:
Quote
sudo ./cgminer -o stratum+tcp://us-east.stratum.slushpool.com:3333  -u xxx.xxx -p xxxx --gekko-compacf-freq 200  --gekko-compacf-detect --suggest-d
iff 256

Read PAGE 4 of the thread. Try adding the “tune2” and “mine2” arguments. Also what hub are you using?
newbie
Activity: 3
Merit: 0
What am I doing wrong?

I compiled cgminer from github/kanoi and it runs, however, all it seems to do is plateau adjusts and lowers the target frequency by 5MHz each time.
Sample output:

Quote
cgminer version 4.12.0 - Started: [2021-12-29 19:48:50.879]
--------------------------------------------------------------------------------
 (5s):0.000 (1m):0.000 (5m):0.000 (15m):0.000 (avg):0.000h/s
 A:8  R:8192  HW:0  WU:0.0/m
 Connected to sha256.pool.xxxx.com diff 8 with stratum as user xxxxx
 Block: 6e7f308f...  Diff:92.4K  Started: [19:55:26.956]  Best share: 0
--------------------------------------------------------------------------------
 SB management [P]ool management Settings [D]isplay options [Q]uit
 0: GSF 10050211: BM1397:01  80.00MHz T:80  P:0   (160:80)  |  0.0% WU:  0% |  0
.000 /  0.000h/s WU:0.0/m-------------------------------------------------------
 [2021-12-29 19:58:53.824] 0: GSF 0 - set ticket to 0x00/1 work 1/1.0
 [2021-12-29 19:58:54.028] 0: GSF 0 - setting bauddiv : 00 61 (ftdi/2)
 [2021-12-29 19:58:54.157] 0: GSF 0 - set ticket to 0xe0/8 work 8/8.0
 [2021-12-29 19:59:04.471] Stratum from pool 0 requested work restart
 [2021-12-29 19:59:13.792] Stratum from pool 0 requested work restart
 [2021-12-29 19:59:31.410] 0: GSF 0 - plateau adjust: target frequency 85.00MHz
-> 80.00MHz
 [2021-12-29 19:59:32.686] 0: GSF 0 - CompacF Bitcoin Miner (10050211)
 [2021-12-29 19:59:33.657] Stratum from pool 0 requested work restart
 [2021-12-29 19:59:34.405] 0: GSF 0 - set ticket to 0x00/1 work 1/1.0
 [2021-12-29 19:59:34.609] 0: GSF 0 - setting bauddiv : 00 61 (ftdi/2)
 [2021-12-29 19:59:34.740] 0: GSF 0 - set ticket to 0xe0/8 work 8/8.0
 [2021-12-29 19:59:53.317] Stratum from pool 0 requested work restart

Any help, please?

Can you share more details of the code you input to start the cgminer?

Yes, I am using this:
Quote
sudo ./cgminer -o stratum+tcp://us-east.stratum.slushpool.com:3333  -u xxx.xxx -p xxxx --gekko-compacf-freq 200  --gekko-compacf-detect --suggest-d
iff 256
newbie
Activity: 3
Merit: 0
I gotcha. no worries. Im def not complaining. These Ferraris are awesome!

Since i got the Gekko hub I ramped them up (incrementally) to 550mhz.  3 were getting about 360ghs, and 1 was at 340.  Which is still amazing.

and I did dial back the volt screw. but then it only got up to 520mhz.  so i turned back up a bit, but not as much as I had before.  its back to 550mhz,  and 340ghs.  So it's all good.

If only I could find more gekko hubs, Id buy some more. There is a guy in Germany selling 2 hubs on Ebay for like 1500 Euros ($1700) +$160 shipping.  I offered him $500, and he told me to go F myself  ¯\_ (ツ)_/¯   hopefully there in stock again soon.


I have the same issue with 1 of my stick too, but I couldnt find out which stick it was.  I got 8 of them, runnin on the bitcoinmerch hub.

I thought it was the inconsistentcy of power distribution when all 4 sticks are plugged in to each of the hubs. 

I run all of them at 400Mhz averaging around 250Ghs, but 1 always come down to around 115 MHz / 120GHs

Been looking for the Gekkoscience hubs on ebay as well, but havnt seen the German " Go F yourself" guy.. i hope you didnt take his suggestion Smiley 

Code:
 (5s):1.878T (1m):2.002T (5m):1.978T (15m):1.955T (avg):1.950Th/s
 A:80339912  R:66985  HW:69440  WU:27243.6/m
 Connected to sg.stratum.slushpool.com diff 2.1K with stratum as user CryptoApeKing.workerName
 Block: 8d9ef614...  Diff:24.3T  Started: [00:59:19.435]  Best share: 312M
--------------------------------------------------------------------------------   
[U]SB management [P]ool management [S]ettings [D]isplay options [Q]uit
 0: GSF 10050171: BM1397:01+ 400.00MHz T:400 P:400 (32:16)  |  100% WU:100% | 253.4G / 261.8Gh/s WU:3657.8/m
 1: GSF 10050134: BM1397:01+ 400.00MHz T:400 P:400 (32:16)  |  100% WU:100% | 289.1G / 264.3Gh/s WU:3692.8/m
 2: GSF 10050173: BM1397:01+ 400.00MHz T:400 P:400 (32:16)  |  100% WU:100% | 261.1G / 248.9Gh/s WU:3477.8/m
 3: GSF 10050074: BM1397:01+ 400.00MHz T:400 P:400 (32:16)  |  100% WU:100% | 252.3G / 262.3Gh/s WU:3664.9/m
 4: GSF 10050167: BM1397:01+ 400.00MHz T:400 P:400 (32:16)  |  100% WU:100% | 260.8G / 257.8Gh/s WU:3602.0/m
 5: GSF 10050208: BM1397:01+ 300.00MHz T:115 P:249 (42:21)  | 95.4% WU:^82% | 150.7G / 128.4Gh/s WU:1793.1/m
 6: GSF 10050179: BM1397:01+ 400.00MHz T:400 P:400 (32:16)  |  100% WU:100% | 245.6G / 260.9Gh/s WU:3644.8/m
 7: GSF 10050103: BM1397:01+ 400.00MHz T:400 P:400 (32:16)  |  100% WU:100% | 210.3G / 265.6Gh/s WU:3710.3/m






What am I doing wrong?

I compiled cgminer from github/kanoi and it runs, however, all it seems to do is plateau adjusts and lowers the target frequency by 5MHz each time.
Sample output:

Quote
cgminer version 4.12.0 - Started: [2021-12-29 19:48:50.879]
--------------------------------------------------------------------------------
 (5s):0.000 (1m):0.000 (5m):0.000 (15m):0.000 (avg):0.000h/s
 A:8  R:8192  HW:0  WU:0.0/m
 Connected to sha256.pool.xxxx.com diff 8 with stratum as user xxxxx
 Block: 6e7f308f...  Diff:92.4K  Started: [19:55:26.956]  Best share: 0
--------------------------------------------------------------------------------
 SB management [P]ool management Settings [D]isplay options [Q]uit
 0: GSF 10050211: BM1397:01  80.00MHz T:80  P:0   (160:80)  |  0.0% WU:  0% |  0
.000 /  0.000h/s WU:0.0/m-------------------------------------------------------
 [2021-12-29 19:58:53.824] 0: GSF 0 - set ticket to 0x00/1 work 1/1.0
 [2021-12-29 19:58:54.028] 0: GSF 0 - setting bauddiv : 00 61 (ftdi/2)
 [2021-12-29 19:58:54.157] 0: GSF 0 - set ticket to 0xe0/8 work 8/8.0
 [2021-12-29 19:59:04.471] Stratum from pool 0 requested work restart
 [2021-12-29 19:59:13.792] Stratum from pool 0 requested work restart
 [2021-12-29 19:59:31.410] 0: GSF 0 - plateau adjust: target frequency 85.00MHz
-> 80.00MHz
 [2021-12-29 19:59:32.686] 0: GSF 0 - CompacF Bitcoin Miner (10050211)
 [2021-12-29 19:59:33.657] Stratum from pool 0 requested work restart
 [2021-12-29 19:59:34.405] 0: GSF 0 - set ticket to 0x00/1 work 1/1.0
 [2021-12-29 19:59:34.609] 0: GSF 0 - setting bauddiv : 00 61 (ftdi/2)
 [2021-12-29 19:59:34.740] 0: GSF 0 - set ticket to 0xe0/8 work 8/8.0
 [2021-12-29 19:59:53.317] Stratum from pool 0 requested work restart

Any help, please?

Can you share more details of the code you input to start the cgminer?

[moderator's note: consecutive posts merged]
Pages:
Jump to: