GekkoScience Terminus R808 Miner Official Support Thread - page 15.

419mining

copper member

Activity: 190

Merit: 111

https://www.419mining.com

Quote from: sidehack on March 03, 2018, 12:37:22 PM

Are you sure the reset line stays pulled high? If the controller sees a problem it pulls reset low for one second, then high for two seconds, then rechecks, so if the problem persists the reset line cycles low and back to high every 3 seconds.

yes, I let it sit for a while, it has a VERY minor fluctuation 1.409 to 1.410 volts but it never drops.

while writing this, it just kicked off a single cycle of work then failed again.

Quote

[2018-03-03 13:00:31.406] GSE 402: Terminus BM1384 Bitcoin Miner (10030050)
[2018-03-03 13:00:31.408] GSE 402 TX: 84:00:00:11
[2018-03-03 13:00:31.411] GSE 402 TX: 84:00:00:11
[2018-03-03 13:00:31.612] GSE 402: found 0 chip(s)
[2018-03-03 13:00:31.612] Hotplug: GekkoScience added GSE 402
[2018-03-03 13:00:31.613] GSE 402 failure, disabling!
[2018-03-03 13:00:31.613] GSE 402: setting frequency to 100.00MHz
[2018-03-03 13:00:31.615] GSE 402 TX: 82:07:83:1C
[2018-03-03 13:00:31.617] GSE 402 TX: 84:00:04:00
[2018-03-03 13:00:35.705] Testing pool stratum+tcp://pool.ckpool.org:3333
[2018-03-03 13:00:36.981] GSE 403: Terminus BM1384 Bitcoin Miner (10030050)
[2018-03-03 13:00:36.982] GSE 403 TX: 84:00:00:11
[2018-03-03 13:00:36.984] GSE 403 TX: 84:00:00:11
[2018-03-03 13:00:37.186] GSE 403: found 0 chip(s)
[2018-03-03 13:00:37.186] Hotplug: GekkoScience added GSE 403
[2018-03-03 13:00:37.186] GSE 403 failure, disabling!
[2018-03-03 13:00:37.186] GSE 403: setting frequency to 100.00MHz
[2018-03-03 13:00:37.188] GSE 403 TX: 82:07:83:1C
[2018-03-03 13:00:37.190] GSE 403 TX: 84:00:04:00
[2018-03-03 13:00:40.706] Testing pool stratum+tcp://pool.ckpool.org:3333
[2018-03-03 13:00:42.649] GSE 404: Terminus BM1384 Bitcoin Miner (10030050)
[2018-03-03 13:00:42.650] GSE 404 TX: 84:00:00:11
[2018-03-03 13:00:42.652] GSE 404 TX: 84:00:00:11
[2018-03-03 13:00:42.861] Hotplug: GekkoScience added GSE 404
[2018-03-03 13:00:42.863] GSE 404 TX: 84:00:00:11
[2018-03-03 13:00:42.870] GSE 404 RX: 13:82:90:FF:0F
[2018-03-03 13:00:42.870] GSE 404 RX: 13:82:90:BF:12
[2018-03-03 13:00:42.870] GSE 404 RX: 13:82:90:FF:0F
[2018-03-03 13:00:42.870] GSE 404 RX: 13:82:90:FF:0F
[2018-03-03 13:00:42.870] GSE 404 RX: 13:82:90:FF:0F
[2018-03-03 13:00:42.870] GSE 404 RX: 13:82:90:FF:0F
[2018-03-03 13:00:42.870] GSE 404 RX: 13:82:90:FF:0F
[2018-03-03 13:00:42.870] GSE 404 RX: 13:82:90:FF:0F
[2018-03-03 13:00:42.972] GSE 404: found 8 chip(s)
[2018-03-03 13:00:43.088] GSE 404: setting frequency to 81.25MHz
[2018-03-03 13:00:43.090] GSE 404 TX: 82:06:03:18
[2018-03-03 13:00:43.092] GSE 404 TX: 84:00:04:00
[2018-03-03 13:00:43.093] GSE 404: sending chain inactive for 8 chip(s)
[2018-03-03 13:00:43.094] GSE 404 TX: 85:00:00:0F
[2018-03-03 13:00:43.096] GSE 404 TX: 01:00:00:19
[2018-03-03 13:00:43.098] GSE 404 TX: 01:20:00:01
[2018-03-03 13:00:43.098] GSE 404 RX: 80:0C:00:03:00
[2018-03-03 13:00:43.098] GSE 404: chip reported frequency of 81.25MHz
[2018-03-03 13:00:43.098] GSE 404 RX: 80:0C:00:03:00
[2018-03-03 13:00:43.098] GSE 404: chip reported frequency of 81.25MHz
[2018-03-03 13:00:43.098] GSE 404 RX: 80:0C:00:03:00
[2018-03-03 13:00:43.098] GSE 404: chip reported frequency of 81.25MHz
[2018-03-03 13:00:43.098] GSE 404 RX: 80:0C:00:03:00
[2018-03-03 13:00:43.098] GSE 404: chip reported frequency of 81.25MHz
[2018-03-03 13:00:43.098] GSE 404 RX: 80:0C:00:03:00
[2018-03-03 13:00:43.098] GSE 404: chip reported frequency of 81.25MHz
[2018-03-03 13:00:43.099] GSE 404 RX: 80:0C:00:03:00
[2018-03-03 13:00:43.099] GSE 404: chip reported frequency of 81.25MHz
[2018-03-03 13:00:43.099] GSE 404 RX: 80:0C:00:03:00
[2018-03-03 13:00:43.099] GSE 404: chip reported frequency of 81.25MHz
[2018-03-03 13:00:43.099] GSE 404 RX: 80:0C:00:03:00
[2018-03-03 13:00:43.099] GSE 404: chip reported frequency of 81.25MHz
[2018-03-03 13:00:43.100] GSE 404 TX: 01:40:00:0C
[2018-03-03 13:00:43.103] GSE 404 TX: 01:60:00:14
[2018-03-03 13:00:43.105] GSE 404 TX: 01:80:00:16
[2018-03-03 13:00:43.107] GSE 404 TX: 01:A0:00:0E
[2018-03-03 13:00:43.109] GSE 404 TX: 01:C0:00:03
[2018-03-03 13:00:43.111] GSE 404 TX: 01:E0:00:1B
[2018-03-03 13:00:43.112] GSE 404: open cores @ 81.25MHz
[2018-03-03 13:00:45.329] GSE 404: start work @ 81.25MHz
[2018-03-03 13:00:45.706] Testing pool stratum+tcp://pool.ckpool.org:3333
[2018-03-03 13:00:50.348] GSE 404 TX: 84:00:04:00
[2018-03-03 13:00:50.707] Testing pool stratum+tcp://pool.ckpool.org:3333
[2018-03-03 13:00:55.420] GSE 404 TX: 84:00:04:00
[2018-03-03 13:00:55.707] Testing pool stratum+tcp://pool.ckpool.org:3333
[2018-03-03 13:00:55.763] Work update message received
[2018-03-03 13:01:00.428] GSE 404 TX: 84:00:04:00
[2018-03-03 13:01:00.707] Testing pool stratum+tcp://pool.ckpool.org:3333
[2018-03-03 13:01:14.751] Testing pool stratum+tcp://pool.ckpool.org:3333
[2018-03-03 13:01:19.752] Testing pool stratum+tcp://pool.ckpool.org:3333
[2018-03-03 13:01:19.821] GSE 404 TX: 84:00:04:00 R:0 HW:0 WU:0.0/m
[2018-03-03 13:01:24.752] Testing pool stratum+tcp://pool.ckpool.org:3333
[2018-03-03 13:01:24.847] GSE 404 TX: 84:00:04:00
[2018-03-03 13:01:26.755] Work update message received
[2018-03-03 13:01:29.753] Testing pool stratum+tcp://pool.ckpool.org:3333
[2018-03-03 13:01:29.881] GSE 404 TX: 84:00:04:00 R:0 HW:0 WU:0.0/m
[2018-03-03 13:01:34.753] Testing pool stratum+tcp://pool.ckpool.org:3333
[2018-03-03 13:01:34.895] GSE 404 TX: 84:00:04:00
[2018-03-03 13:01:39.753] Testing pool stratum+tcp://pool.ckpool.org:3333
[2018-03-03 13:01:39.966] GSE 404 TX: 84:00:04:00 R:0 HW:0 WU:0.0/m
[2018-03-03 13:01:44.754] Testing pool stratum+tcp://pool.ckpool.org:3333
[2018-03-03 13:01:45.026] GSE 404 TX: 84:00:04:00
[2018-03-03 13:01:49.754] Testing pool stratum+tcp://pool.ckpool.org:3333
[2018-03-03 13:01:50.031] GSE 404 TX: 84:00:04:00 R:0 HW:0 WU:0.0/m
[2018-03-03 13:01:54.755] Testing pool stratum+tcp://pool.ckpool.org:3333
[2018-03-03 13:01:55.046] GSE 404 TX: 84:00:04:00
[2018-03-03 13:01:58.772] Work update message received

im going to build a quick jumper connector so i can watch the voltage for an extended period so i can catch it again when it starts responding(without having to hold the meter leads to the 2 pins by hand).

sidehack

legendary

Activity: 3374

Merit: 1859

Curmudgeonly hardware guy

Hm. If the clock line isn't getting to the first node, it won't get propagated all the way down. If that's the case, the string would still settle to balanced voltage even with a high reset line, in which case the reset controller won't see the issue and won't try to cycle another reset, and since the chips aren't getting a clock line they're not operating so any IO commands will fall on deaf ears.

Are you sure the reset line stays pulled high? If the controller sees a problem it pulls reset low for one second, then high for two seconds, then rechecks, so if the problem persists the reset line cycles low and back to high every 3 seconds.

Also, "setting frequency to 100MHz" is default behavior for a "failure, disabling" event. You'll see the same thing if you unplug a running miner.

419mining

copper member

Activity: 190

Merit: 111

https://www.419mining.com

just had a failure.
interesting its not respecting the --gekko-start-freq 80 command.
@Sidehack, I checked the reset header, its still showing 1.4v event though it says 0 chips.

Quote

[2018-03-03 12:05:27.645] GSE 0: Terminus BM1384 Bitcoin Miner (10030050)
[2018-03-03 12:05:27.647] GSE 0 TX: 84:00:00:11
[2018-03-03 12:05:27.649] GSE 0 TX: 84:00:00:11
[2018-03-03 12:05:27.853] GSE 0: found 0 chip(s)
[2018-03-03 12:05:27.853] Probing for an alive pool
[2018-03-03 12:05:27.855] GSE 0 failure, disabling!
[2018-03-03 12:05:27.855] Testing pool stratum+tcp://pool.ckpool.org:3333
[2018-03-03 12:05:27.855] GSE 0: setting frequency to 100.00MHz
[2018-03-03 12:05:27.857] GSE 0 TX: 82:07:83:1C
[2018-03-03 12:05:27.859] GSE 0 TX: 84:00:04:00
[2018-03-03 12:05:27.993] Pool 0 difficulty changed to 4000
[2018-03-03 12:05:28.045] Pool 0 message: Authorised, welcome to ckpool.org 1DtRzACnDAr2SPXMyAp3pLMfREPch3PbhA!
[2018-03-03 12:05:28.045] Stratum authorisation success for pool 0
[2018-03-03 12:05:28.047] Pool 0 stratum+tcp://pool.ckpool.org:3333 alive
[2018-03-03 12:05:28.102] Pool 0 difficulty changed to 32
[2018-03-03 12:05:28.102] Network diff set to 3.01T
[2018-03-03 12:05:28.103] New block: 00000000000000000000e499bf7fa30e87a9d2542885276cb80fb2fdeab1ffdb... diff 3.01T
[2018-03-03 12:05:28.855] Testing pool stratum+tcp://pool.ckpool.org:3333
[2018-03-03 12:05:28.855] Work update message received
[2018-03-03 12:05:32.857] Work update message received
[2018-03-03 12:05:33.856] Testing pool stratum+tcp://pool.ckpool.org:3333
[2018-03-03 12:05:34.115] GSE 1: Terminus BM1384 Bitcoin Miner (10030050)
[2018-03-03 12:05:34.116] GSE 1 TX: 84:00:00:11
[2018-03-03 12:05:34.120] GSE 1 TX: 84:00:00:11
[2018-03-03 12:05:34.321] GSE 1: found 0 chip(s)
[2018-03-03 12:05:34.322] Hotplug: GekkoScience added GSE 1
[2018-03-03 12:05:34.323] GSE 1 failure, disabling!
[2018-03-03 12:05:34.323] GSE 1: setting frequency to 100.00MHz
[2018-03-03 12:05:34.325] GSE 1 TX: 82:07:83:1C
[2018-03-03 12:05:34.326] GSE 1 TX: 84:00:04:00
[2018-03-03 12:05:38.857] Testing pool stratum+tcp://pool.ckpool.org:3333
[2018-03-03 12:05:39.688] GSE 2: Terminus BM1384 Bitcoin Miner (10030050)
[2018-03-03 12:05:39.689] GSE 2 TX: 84:00:00:11
[2018-03-03 12:05:39.694] GSE 2 TX: 84:00:00:11
[2018-03-03 12:05:39.897] GSE 2: found 0 chip(s)
[2018-03-03 12:05:39.897] Hotplug: GekkoScience added GSE 2
[2018-03-03 12:05:39.900] GSE 2 failure, disabling!
[2018-03-03 12:05:39.900] GSE 2: setting frequency to 100.00MHz
[2018-03-03 12:05:39.901] GSE 2 TX: 82:07:83:1C
[2018-03-03 12:05:39.902] GSE 2 TX: 84:00:04:00
[2018-03-03 12:05:43.857] Testing pool stratum+tcp://pool.ckpool.org:3333
[2018-03-03 12:05:45.262] GSE 3: Terminus BM1384 Bitcoin Miner (10030050)
[2018-03-03 12:05:45.264] GSE 3 TX: 84:00:00:11
[2018-03-03 12:05:45.267] GSE 3 TX: 84:00:00:11
[2018-03-03 12:05:45.468] GSE 3: found 0 chip(s)

vh

hero member

Activity: 699

Merit: 666

Quote from: 419mining on March 03, 2018, 08:49:01 AM

Hey VH, I saw some wierdness with one of my units yesterday during testing. It spun up great on the first try and was chugging along at 150Mhz. I closed and restarted cgminer and the damn thing just crapped out. It was weird because the only change was restarting cgminer.
It ran through hundreds of re-enumerations until it randomly just started working again. Any idea on what I can give you for diganostics? I've already talked with sidehack about it and know what he needs the next time it happens.

"When it drops out, check the voltage across the two pins on the reset header. If it's flatlined at zero volts, that indicates an issue with the temperature sensor. The onboard controller won't enable the mining chips without valid temperature data. If it cycles between zero and around 1.4 volts, there's an issue with the chips and the string isn't turning on right."

...

its been running strong since (~11 hours now) but I want to make sure you have everything you need for diagnostics.

that's perfect, thanks.

just a couple of notes...

first: look for any "frequency changed" messages in the log. it's also a sign that the temperature sensor kicked in a few time before the pc restarted.
second: if it is a cooldown issue, you can pass in a --hotplug 30 so that cgminer give it a longer break before trying to start it back up.

sidehack

legendary

Activity: 3374

Merit: 1859

Curmudgeonly hardware guy

Moonie -when you say the white LED is blinking, is it flashing on about a 3-second cycle?

419mining

copper member

Activity: 190

Merit: 111

https://www.419mining.com

Hey VH, I saw some wierdness with one of my units yesterday during testing. It spun up great on the first try and was chugging along at 150Mhz. I closed and restarted cgminer and the damn thing just crapped out. It was weird because the only change was restarting cgminer.
It ran through hundreds of re-enumerations until it randomly just started working again. Any idea on what I can give you for diganostics? I've already talked with sidehack about it and know what he needs the next time it happens.

"When it drops out, check the voltage across the two pins on the reset header. If it's flatlined at zero volts, that indicates an issue with the temperature sensor. The onboard controller won't enable the mining chips without valid temperature data. If it cycles between zero and around 1.4 volts, there's an issue with the chips and the string isn't turning on right."

Quote

[2018-03-02 18:41:45.728] Started cgminer 4.10.0
[2018-03-02 18:41:46.048] GSE 0: Terminus BM1384 Bitcoin Miner (10030050)
[2018-03-02 18:41:46.050] GSE 0 TX: 84:00:00:11
[2018-03-02 18:41:46.052] GSE 0 TX: 84:00:00:11
[2018-03-02 18:41:46.457] GSE 0: found 0 chip(s)
[2018-03-02 18:41:46.457] Probing for an alive pool
[2018-03-02 18:41:46.457] Testing pool stratum+tcp://pool.ckpool.org:3333
[2018-03-02 18:41:46.457] GSE 0 failure, disabling!
[2018-03-02 18:41:46.462] GSE 0: setting frequency to 100.00MHz
[2018-03-02 18:41:46.464] GSE 0 TX: 82:07:83:1C
[2018-03-02 18:41:46.465] GSE 0 TX: 84:00:04:00
[2018-03-02 18:41:46.728] Pool 0 difficulty changed to 4000
[2018-03-02 18:41:46.775] Pool 0 message: Authorised, welcome to ckpool.org 1DtRzACnDAr2SPXMyAp3pLMfREPch3PbhA!
[2018-03-02 18:41:46.775] Stratum authorisation success for pool 0
[2018-03-02 18:41:46.775] Pool 0 stratum+tcp://pool.ckpool.org:3333 alive
[2018-03-02 18:41:46.828] Pool 0 difficulty changed to 32
[2018-03-02 18:41:46.828] Network diff set to 3.01T
[2018-03-02 18:41:46.828] New block: 0000000000000000002915f5244780934423a32d8f97d795a1606d964586849a... diff 3.01T
[2018-03-02 18:41:47.458] Testing pool stratum+tcp://pool.ckpool.org:3333
[2018-03-02 18:41:47.458] Work update message received
[2018-03-02 18:41:49.459] (5s):0.000 (1m):0.000 (5m):0.000 (15m):0.000 (avg):0.000h/s
[2018-03-02 18:41:52.458] Testing pool stratum+tcp://pool.ckpool.org:3333
[2018-03-02 18:41:52.768] GSE 1: Terminus BM1384 Bitcoin Miner (10030050)
[2018-03-02 18:41:52.771] GSE 1 TX: 84:00:00:11
[2018-03-02 18:41:52.773] GSE 1 TX: 84:00:00:11
[2018-03-02 18:41:53.176] GSE 1: found 0 chip(s)
...
restart pc
...
change usb ports
...
reset Terminus power
...
restart cgminer
...
[2018-03-02 20:35:33.093] Testing pool stratum+tcp://pool.ckpool.org:3333
[2018-03-02 20:35:37.086] GSE 29: Terminus BM1384 Bitcoin Miner (10030050)
[2018-03-02 20:35:37.088] GSE 29 TX: 84:00:00:11
[2018-03-02 20:35:37.091] GSE 29 TX: 84:00:00:11
[2018-03-02 20:35:37.495] GSE 29: found 0 chip(s)
[2018-03-02 20:35:37.497] Hotplug: GekkoScience added GSE 29
[2018-03-02 20:35:37.499] GSE 29 failure, disabling!
[2018-03-02 20:35:37.500] GSE 29: setting frequency to 100.00MHz
[2018-03-02 20:35:37.504] GSE 29 TX: 82:07:83:1C
[2018-03-02 20:35:37.505] GSE 29 TX: 84:00:04:00
[2018-03-02 20:35:38.094] Testing pool stratum+tcp://pool.ckpool.org:3333
[2018-03-02 20:35:42.867] GSE 30: Terminus BM1384 Bitcoin Miner (10030050)
[2018-03-02 20:35:42.868] GSE 30 TX: 84:00:00:11
[2018-03-02 20:35:42.873] GSE 30 TX: 84:00:00:11
[2018-03-02 20:35:43.081] Hotplug: GekkoScience added GSE 30
[2018-03-02 20:35:43.089] GSE 30 TX: 84:00:00:11
[2018-03-02 20:35:43.094] Testing pool stratum+tcp://pool.ckpool.org:3333
[2018-03-02 20:35:43.094] GSE 30 RX: 13:82:90:FF:0F
[2018-03-02 20:35:43.095] GSE 30 RX: 13:82:90:FF:0F
[2018-03-02 20:35:43.096] GSE 30 RX: 13:82:90:FF:0F
[2018-03-02 20:35:43.097] GSE 30 RX: 13:82:90:FF:0F
[2018-03-02 20:35:43.097] GSE 30 RX: 13:82:90:FF:0F
[2018-03-02 20:35:43.098] GSE 30 RX: 13:82:90:FF:0F
[2018-03-02 20:35:43.099] GSE 30 RX: 13:82:90:FF:0F
[2018-03-02 20:35:43.100] GSE 30 RX: 13:82:90:FF:0F
[2018-03-02 20:35:43.203] GSE 30: found 8 chip(s)
[2018-03-02 20:35:43.311] GSE 30: setting frequency to 81.25MHz
[2018-03-02 20:35:43.312] GSE 30 TX: 82:06:03:18
[2018-03-02 20:35:43.316] GSE 30 TX: 84:00:04:00
[2018-03-02 20:35:43.317] GSE 30: sending chain inactive for 8 chip(s)
[2018-03-02 20:35:43.319] GSE 30 TX: 85:00:00:0F
[2018-03-02 20:35:43.322] GSE 30 TX: 01:00:00:19
[2018-03-02 20:35:43.322] GSE 30 RX: 80:0C:00:03:00
[2018-03-02 20:35:43.323] GSE 30: chip reported frequency of 81.25MHz
[2018-03-02 20:35:43.324] GSE 30 TX: 01:20:00:01
[2018-03-02 20:35:43.325] GSE 30 RX: 80:0C:00:03:00
[2018-03-02 20:35:43.327] GSE 30: chip reported frequency of 81.25MHz
[2018-03-02 20:35:43.327] GSE 30 RX: 80:0C:00:03:00
[2018-03-02 20:35:43.328] GSE 30: chip reported frequency of 81.25MHz
[2018-03-02 20:35:43.329] GSE 30 RX: 80:0C:00:03:00
[2018-03-02 20:35:43.329] GSE 30 TX: 01:40:00:0C
[2018-03-02 20:35:43.330] GSE 30: chip reported frequency of 81.25MHz
[2018-03-02 20:35:43.334] GSE 30 TX: 01:60:00:14
[2018-03-02 20:35:43.334] GSE 30 RX: 80:0C:00:03:00
[2018-03-02 20:35:43.336] GSE 30: chip reported frequency of 81.25MHz
[2018-03-02 20:35:43.337] GSE 30 RX: 80:0C:00:03:00
[2018-03-02 20:35:43.338] GSE 30: chip reported frequency of 81.25MHz
[2018-03-02 20:35:43.338] GSE 30 RX: 80:0C:00:03:00
[2018-03-02 20:35:43.339] GSE 30 TX: 01:80:00:16
[2018-03-02 20:35:43.339] GSE 30: chip reported frequency of 81.25MHz
[2018-03-02 20:35:43.340] GSE 30 RX: 80:0C:00:03:00
[2018-03-02 20:35:43.341] GSE 30: chip reported frequency of 81.25MHz
[2018-03-02 20:35:43.343] GSE 30 TX: 01:A0:00:0E
[2018-03-02 20:35:43.350] GSE 30 TX: 01:C0:00:03
[2018-03-02 20:35:43.352] GSE 30 TX: 01:E0:00:1B
[2018-03-02 20:35:43.354] GSE 30: open cores @ 81.25MHz
[2018-03-02 20:35:45.099] Work update message received
[2018-03-02 20:35:45.643] GSE 30: start work @ 81.25MHz
[2018-03-02 20:35:45.888] GSE 30 RX: C5:38:04:81:84
[2018-03-02 20:35:45.889] GSE 30: Device reported nonce: c5380481 @ 04

its been running strong since (~11 hours now) but I want to make sure you have everything you need for diagnostics.

419mining

copper member

Activity: 190

Merit: 111

https://www.419mining.com

Sorry I've been busy and It old but still important

Quote from: philipma1957 on February 24, 2018, 10:21:59 AM

Quote from: 419mining on February 24, 2018, 10:14:15 AM

So based on that, a standard LED strip light power pack should work. something like this? http://amzn.to/2FsOMP1

that is junk I will get you a better link

this will do 3 units

https://www.trcelectronics.com/ecomm/pdf/hrp200.pdf
https://www.trcelectronics.com/View/Mean-Well/HRP-200-12.shtml

88% efficient

use with these as they are 22 ga not 24 or 26 just cut off the end that does not fit.

https://www.ebay.com/itm/10-Pack-of-36-22AWG-DC-Power-Cable-Male-to-Male-5-5mm-X-2-1mm-Barrel-Plugs/192150513189?

better yet buy these

https://www.ebay.com/itm/5-5mm-x-2-5mm-5-5-2-5-DC-Power-Barrel-Jack-Screw-terminal-Pack-of-2/381843414717?

https://www.ebay.com/itm/50-Speaker-Wire-18-AWG-Ga-Gauge-High-Quality-Car-or-Home-Audio-Guage/361647935149?

and cut to length

3 rigs per psu 88% efficient

Can you tell me why you think this unit is junk? and/or provide a link to a single unit PSU? I actually run my personal rigs on 92% efficient HP1200 w/Gekko break out boards but I need a PSU for single unit sales.

itzmoonie

newbie

Activity: 2

Merit: 0

Hello all! So I just received my 2 terminus today and one of them is working fine while the other ran for about 5 minutes and has now gone into a permanent ZOMBIE state.

I am running them on a os x machine plugged directly into their own USB ports. I am running the latest version of cgminer from vthoang/cgminer. I also tried running the zombied one on my pi machine but still no luck. Below is a snippet of the log file:

Code:

cgminer version 4.10.0 - Started: [2018-03-02 16:37:18.250]
--------------------------------------------------------------------------------
(5s):63.62G (1m):65.78G (5m):67.01G (15m):59.15G (avg):66.11Gh/s
A:27508 R:0 HW:0 WU:924.0/m
Connected to blah
Block: 3469a8d1... Diff:30.4M Started: [17:08:57.491] Best share: 5.35K
--------------------------------------------------------------------------------
[U]SB management [P]ool management [S]ettings [D]isplay options [Q]uit
1: GSE 10030045: BM1384:8 150.00MHz HW:0 | 73.27G / 66.14Gh/s WU:924.0/m
0: GSE 10030044: | ZOMBIE
--------------------------------------------------------------------------------
[2018-03-02 17:05:08.443] GSE 76: Terminus BM1384 Bitcoin Miner (10030044)
[2018-03-02 17:05:08.865] Hotplug: GekkoScience added GSE 76
[2018-03-02 17:05:14.099] GSE 77: Terminus BM1384 Bitcoin Miner (10030044)
[2018-03-02 17:05:14.521] Hotplug: GekkoScience added GSE 77
[2018-03-02 17:05:19.761] GSE 78: Terminus BM1384 Bitcoin Miner (10030044)
[2018-03-02 17:05:20.183] Hotplug: GekkoScience added GSE 78
[2018-03-02 17:05:25.423] GSE 79: Terminus BM1384 Bitcoin Miner (10030044)
[2018-03-02 17:05:25.840] Hotplug: GekkoScience added GSE 79
[2018-03-02 17:05:31.075] GSE 80: Terminus BM1384 Bitcoin Miner (10030044)
[2018-03-02 17:05:31.495] Hotplug: GekkoScience added GSE 80

Also, what is funny is that the one that works never goes over 150MHz even if I try and force it on the command line. But at least it is running I guess...

I noticed that the white LED lights on the ZOMBIED one are blinking while the one that works just the blue LED light is on when they are not connected or mining. So what should I do at this point? Want me to send the ZOMBIED one back to you sidehack?

Thanks!

vh

hero member

Activity: 699

Merit: 666

the "pause" is the last line of the bat file.

it's there to stop the batch cmd prompt from closing out in case you decide to add additional parameters in and introduce an typing error.

plugging in the second device causing the first one to fail is odd since there should be no real activity at all going to it with the --usb :1 setting.

start up miner1.bat, then plug in one miner. wait until avg 66GH/s, then plug in the second miner. if it breaks, stop cgminer and unplug all.
start up miner1.bat, then plug in one miner. wait until avg 66GH/s, then plug in the second miner into "other" usb port. if it breaks. stop.

if still breaking, repeat with a different unit for the second miner in the case above.

if it miner1.bat doesn't show errors after plugging in the second device, start up miner2.bat.

minerbobbert

member

Activity: 177

Merit: 10

Quote

plugged into a second free port on your laptop or onto a hub?

That's after plugging into a second port. I'm avoiding hubs for now as you suggested.

And I didn't make different .bat files, I just tried bringing up the same one twice. I'll check that next.

What does the "usb pause" code for? Do I need to bring up each instance of cgminer first and then activate the miners?

vh

hero member

Activity: 699

Merit: 666

Quote from: minerbobbert on March 01, 2018, 08:40:44 PM

Making a separate post for a second (?) problem. If I have one miner running and plug a second one in, the following log error pops up:

plugged into a second free port on your laptop or onto a hub?

Quote from: minerbobbert on March 01, 2018, 08:35:12 PM

For reference sake, my bat file is:

cgminer -o stratum+tcp://pool.ckpool.org:3333 -u me -p x --suggest-diff 40 --gekko-start-freq 100 --gekko-step-freq 25 --gekko-step-delay 15 --gekko-terminus-freq 200 2>logfile.txt --usb :1

miner1.bat

Code:

cgminer.exe -o stratum+tcp://pool.ckpool.org:3333 -u 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr -p x --usb :1 2>logfile_miner1.txt
pause

miner2.bat

Code:

cgminer.exe -o stratum+tcp://pool.ckpool.org:3333 -u 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr -p x --usb :1 2>logfile_miner2.txt
pause

miner3.bat

Code:

cgminer.exe -o stratum+tcp://solo.ckpool.org:3333 -u 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr -p x --usb :1 2>logfile_miner3.txt
pause

sidehack

legendary

Activity: 3374

Merit: 1859

Curmudgeonly hardware guy

I'm going to bet your first issue is an error opening the logfile. Make a second copy of the batch file, point it at a different text file and see if it works.

The second issue, that's VH's neighborhood for sure.

minerbobbert

member

Activity: 177

Merit: 10

Making a separate post for a second (?) problem. If I have one miner running and plug a second one in, the following log error pops up:

[2018-03-01 10:56:17.609] Started cgminer 4.10.0
[2018-03-01 10:56:19.531] GSE 0: Terminus BM1384 Bitcoin Miner (10030013)
[2018-03-01 10:56:19.750] Probing for an alive pool
[2018-03-01 10:56:19.859] GSE 0: found 8 chip(s)
[2018-03-01 10:56:19.968] GSE 0: setting frequency to 100.00MHz
[2018-03-01 10:56:20.031] GSE 0: open cores @ 100.00MHz
[2018-03-01 10:56:20.093] Pool 0 difficulty changed to 4000
[2018-03-01 10:56:20.156] Pool 0 message: Authorised, welcome to ckpool.org 15rN7atb8w7avfQH7PUjh6zEmForXvDr2x!
[2018-03-01 10:56:20.218] Pool 0 difficulty changed to 40
[2018-03-01 10:56:20.218] Network diff set to 3.01T
[2018-03-01 10:56:21.781] GSE 0: start work @ 100.00MHz
[2018-03-01 10:56:36.796] GSE 0: setting frequency to 125.00MHz
[2018-03-01 10:56:41.296] Rejected 0211dddc Diff 124/40 GSE 0 (Above target)
[2018-03-01 10:56:47.468] Rejected 011da736 Diff 229/40 GSE 0 (Above target)
[2018-03-01 10:56:51.875] GSE 0: setting frequency to 150.00MHz
[2018-03-01 10:56:54.843] Rejected 016214fc Diff 185/40 GSE 0 (Above target)
[2018-03-01 10:56:58.093] Rejected 03908434 Diff 72/40 GSE 0 (Above target)
[2018-03-01 10:57:00.750] Rejected 046ca895 Diff 58/40 GSE 0 (Above target)
[2018-03-01 10:57:05.234] Rejected 05363b43 Diff 49/40 GSE 0 (Above target)
[2018-03-01 10:57:05.437] Rejected 04e43f7d Diff 52/40 GSE 0 (Above target)
[2018-03-01 10:57:06.937] GSE 0: setting frequency to 175.00MHz
[2018-03-01 10:57:09.234] Rejected 03419efe Diff 79/40 GSE 0 (Above target)
[2018-03-01 10:57:13.937] Accepted 032f31a9 Diff 80/40 GSE 0
[2018-03-01 10:57:16.093] Accepted 032aeca4 Diff 81/40 GSE 0
[2018-03-01 10:57:20.609] Accepted 029646fc Diff 99/40 GSE 0
[2018-03-01 10:57:22.000] GSE 0: setting frequency to 200.00MHz
... lots of hashing...
I plug in the new miner and:
[2018-03-01 18:37:33.921] Accepted 61dba76b Diff 670/48 GSE 0
[2018-03-01 18:37:40.484] Accepted 02b3d528 Diff 95/48 GSE 0
[2018-03-01 18:37:42.546] Accepted 032b3d34 Diff 81/48 GSE 0
[2018-03-01 18:37:48.203] Accepted 0112fef6 Diff 238/48 GSE 0
[2018-03-01 18:37:53.687] GSE 0 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
[2018-03-01 18:37:53.937] GSE 0 attempted reset got err:(0) LIBUSB_SUCCESS / LIBUSB_TRANSFER_COMPLETED
[2018-03-01 18:37:54.968] GSE 0 SendWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT
[2018-03-01 18:37:54.968] GSE 0: usb failure (-7)
[2018-03-01 18:37:54.968] GSE 0 failure, disabling!
[2018-03-01 18:37:54.968] GSE 0: setting frequency to 100.00MHz
[2018-03-01 18:37:56.015] GSE 0 RequestResults usb write err:(-7) LIBUSB_ERROR_TIMEOUT
[2018-03-01 18:37:56.015] GSE 0 attempted reset got err:(0) LIBUSB_SUCCESS / LIBUSB_TRANSFER_COMPLETED
[2018-03-01 18:38:09.562] WTF WRLOCK ERROR ON LOCK! errno=0 in usbutils.c usb_cleanup():3884
[2018-03-01 18:38:09.562] Shutdown signal received.

minerbobbert

member

Activity: 177

Merit: 10

Quote

open up a command prompt.
navigate to the folder that you unzipped (d5fba8e) to.
run "cgminer.exe -o stratum+tcp://pool.ckpool.org:3333 -u 1BURGERAXHH6Yi6LRybRJK7ybEm5m5HwTr -p x --usb :1"

I am running my cgminer off a bat file I created. I cannot run it off of a command prompt because I am complete idiot with computers so when I open the cmd prompt, I can't find the folder even when I type it in exactly as it appears in explorer. Will this work off of a .bat file?

For reference sake, my bat file is:

cgminer -o stratum+tcp://pool.ckpool.org:3333 -u me -p x --suggest-diff 40 --gekko-start-freq 100 --gekko-step-freq 25 --gekko-step-delay 15 --gekko-terminus-freq 200 2>logfile.txt --usb :1

Quote

wait to see if miner can reach 66Gh/s...

I can reach this. With the settings above I average 84-88ghash.

However, if I try to open a second .bat prompt a new window pops up and immediately closes. This happens before I can read any text on the window and because the first miner is chugging along, I can't grab a log file because none are created.

vh

hero member

Activity: 699

Merit: 666

Quote from: jdesarro on February 28, 2018, 11:38:38 PM

...

As for s/w, those look like checksums you are passing, those would be just for the compiled Win executables? I cloned/flagged/made tonight, no obvious change, if there is a log I can pull please advise.

Thanks again.

Those are the git commit id in the folder name to track the downloaded build.

Separate out the Terminus and run it in verbose mode (--verbose).
When it goes into that "failure, disabling" cycle there may be additional messages to grab, but it will be a little noisy until then.

kipper01

full member

Activity: 214

Merit: 100

1KippERXwH1PdBxKNt1ksgqh89WBv6CtWQ

Quote from: sidehack on February 28, 2018, 11:56:44 PM

Well, it's recognizing 8 chips. That's the first hurdle. Not really sure what's going wrong next, except maybe the core voltage is cranked way down for some reason and the string drops out as soon as it lights up and then gets re-set and redetected.

Although, looks like it did run for about ten minutes before bailing out the first time, and then it started cycling. I've seen similar behavior on one or two during final testing, but I haven't torn into them to track down the cause.

I have 2 devices that are having issues. I will look at them more this weekend when I have more time but one essentially does not work at all and I will be interested what the log says. The other appears to run for around an hour than stops. Like I said I'll get specifics this weekend. The other ones seem to be running fine on Windows using PCIe connection.

sidehack

legendary

Activity: 3374

Merit: 1859

Curmudgeonly hardware guy

Well, it's recognizing 8 chips. That's the first hurdle. Not really sure what's going wrong next, except maybe the core voltage is cranked way down for some reason and the string drops out as soon as it lights up and then gets re-set and redetected.

Although, looks like it did run for about ten minutes before bailing out the first time, and then it started cycling. I've seen similar behavior on one or two during final testing, but I haven't torn into them to track down the cause.

jdesarro

newbie

Activity: 4

Merit: 0

Quote from: sidehack on February 27, 2018, 11:35:16 PM

Ooh handy, error codes. Gonna have to update my testing station.

Yes, voltages across the different nodes would be handy. Maybe on the reset pin also.

Wait, you're looking at the chips? You pulled off the heatsink?

When it re-enumerates, does it tell you how many chips are detected? VH, I don't know if updated version of your software mention how many chips are detected (the old version on my bench computer does) but that's useful diagnostic info.

https://imgur.com/TvmQX6R

These looked like the components with the test points on the 2PAC, I had them as the ASICs, but of course they are just caps, maybe high filters for the supply to the ASICs? Anyway, no, I did not pull off the heat sink, I will gladly measure across these caps, or the nodes you mentioned, any other test points and report back.

Each enumeration identifies the correct number of chips per device, including the Terminus resets after it fails and restarts.

[2018-02-28 20:39:03.907] GSC 0: Compac BM1384 Bitcoin Miner (10002069)
[2018-02-28 20:39:04.040] GSD 0: 2Pac BM1384 Bitcoin Miner (10021345)
[2018-02-28 20:39:04.182] GSE 0: Terminus BM1384 Bitcoin Miner (10030035)
[2018-02-28 20:39:04.495] GSC 0: found 1 chip(s)
[2018-02-28 20:39:04.613] GSC 0: setting frequency to 150.00MHz
[2018-02-28 20:39:04.621] GSC 0: open cores @ 150.00MHz
[2018-02-28 20:39:04.703] GSD 0: found 2 chip(s)
[2018-02-28 20:39:04.808] Probing for an alive pool
[2018-02-28 20:39:04.821] GSD 0: setting frequency to 100.00MHz
[2018-02-28 20:39:04.830] GSD 0: open cores @ 100.00MHz
[2018-02-28 20:39:04.916] GSE 0: found 8 chip(s)
[2018-02-28 20:39:05.030] GSE 0: setting frequency to 100.00MHz
[2018-02-28 20:39:05.052] GSE 0: open cores @ 100.00MHz
...
[2018-02-28 20:50:34.456] GSE 0 failure, disabling!
[2018-02-28 20:50:34.456] GSE 0: setting frequency to 100.00MHz
[2018-02-28 20:50:38.258] GSE 1: Terminus BM1384 Bitcoin Miner (10030035)
[2018-02-28 20:50:38.469] Hotplug: GekkoScience added GSE 1
[2018-02-28 20:50:38.577] GSE 1: found 8 chip(s)
[2018-02-28 20:50:38.693] GSE 1: setting frequency to 100.00MHz
[2018-02-28 20:50:38.715] GSE 1: open cores @ 100.00MHz
[2018-02-28 20:50:39.185] GSE 1 failure, disabling!
[2018-02-28 20:50:43.788] GSE 2: Terminus BM1384 Bitcoin Miner (10030035)
[2018-02-28 20:50:43.998] Hotplug: GekkoScience added GSE 2
[2018-02-28 20:50:44.106] GSE 2: found 8 chip(s)
[2018-02-28 20:50:44.220] GSE 2: setting frequency to 100.00MHz
[2018-02-28 20:50:44.242] GSE 2: open cores @ 100.00MHz
[2018-02-28 20:50:45.487] GSE 2 failure, disabling!

From this same run, I did catch another error message after reset 26:
[2018-02-28 20:54:44.957] GSE 26 failure, disabling!
[2018-02-28 20:54:45.120] GekkoScience detect (3:76) failed to initialise (incorrect device?), resetting
[2018-02-28 20:54:45.120] failed usb_init

As for s/w, those look like checksums you are passing, those would be just for the compiled Win executables? I cloned/flagged/made tonight, no obvious change, if there is a log I can pull please advise.

Thanks again.

goose1072

full member

Activity: 235

Merit: 100

Quote from: sidehack on February 28, 2018, 01:50:04 AM

The set of 6 pins is a PIC programming header. The offshoot pin with a jumper sends power to the PIC. This controller handles temperature monitoring, fan speed and string lockup resetting. The two pins are connected to GND and Reset, so tying them together will force a reset of the chip string.

Package coming your way.

Thank you

sidehack

legendary

Activity: 3374

Merit: 1859

Curmudgeonly hardware guy

The set of 6 pins is a PIC programming header. The offshoot pin with a jumper sends power to the PIC. This controller handles temperature monitoring, fan speed and string lockup resetting. The two pins are connected to GND and Reset, so tying them together will force a reset of the chip string.

Topic: GekkoScience Terminus R808 Miner Official Support Thread - page 15. (Read 16917 times)