Search content
Sort by
Showing 20 of 85 results by canford
Приветствую вас, криптовалютчики, майнеры и арбитражники!
Мой партнер, программист Hektur хотел заняться майнингом вместе со своим другом. Пока рассматривали варианты, Hektur решил создать сервис, который позволил бы выводить деньги с нескольких бирж одновременно и получать при этом максимальный доход. Суть да дело, в итоге друг моего партнера передумал. Этот же друг был главным спонсором мероприятия, а партнер, не имея достаточного количества
денег, решил не майнить.
уффф, как все запутано, но дальше будет проще)
А арбитражный советник тем не менее остался. Помимо своей главной функции вывода криптовалют с максимальным доходом, сервис ещё и дает рекомендации по арбитражной торговле между биржами. Грех было бросать такое начинание!
Поэтому Hektur решил не запускать работу. К работе над сервисом присоединился я, вместе мы добавили ему функциональности. Затем появились и спонсоры.
Просим вас потестировать сервис, и, если что-то неясно - задать вопросы. На другом форуме тоже есть ветка посвященная проекту. Там мы уже наладили диалог с пользователями они спрашивают, мы отвечаем
Также, я подготовил небольшое описание, чтобы вы смогли быстро разобраться с информацией.
Арбитражный советник «Торговые рекомендации»
Вывод криптосредств с максимальным доходом, рекомендации по арбитражной торговле между биржами
Преимущества
· Анализирует 15 бирж: Bitfinex, Kraken, Bittrex, HitBTC, Exmo, Poloniex, Liqui, GDAX, xBTCe, Binance, BitStamp, itBit, ANX, OKCoin, BTCC,
· Анализирует валюты: USD EUR BTC BCH LTC ETH ETC XMR ZEC.
· Возможность отключать для конкретных бирж фиатные валюты (если вы не прошли авторизацию или подтверждение личности).
· При просчете наиболее выгодных сделок анализирует цепочку глубиной до 10 сделок ежеминутно.
· Позволяет указать стартовую точку (конкретная биржа, конкретная валюта, биржа+валюта, на которой у вас есть баланс) и конечную точку.
· Возможность вывода совокупной информации со всех интересующих бирж и лучшей цены в ячейке
· В секунду анализируется 18,7 триллионов маршрутов.
Возможности
Открытие личных кабинетов (регистрация без верификации почтового адреса) с возможностью редактирования списка бирж, указания личных комиссий на биржах и включения/отключения фиатных валют для каждой биржи. Все настройки индивидуальны.
Наличие уведомлений (алертов) при появлении маршрутов с интересующими параметрами: биржи, валюты, желаемый мин. профит и ширина арбитражного окна (точность определения длительности по времени 12%).
Скоро появится Возможности
Возможность получать уведомления на email и google cloud message.
Вывод информации о стаканах сделок.
Вывод информации о максимальной сумме арбитражного маршрута
Доступ к получению маршрутов по rest-api.
Подписка на котировки и стаканы сделок с помощью web-sockets (и возможно по tcp)
Добавление информации по тех. анализу (важно для инвесторов на долгосрочной основе).
Исторические графики (с выводом по лучшей цене и конкретной бирже). Возможность добавления техиндикаторов на график, добавление уведомлений по событиям и сохранение настроек с тех. индикаторами.
Торговые сигналы и уведомления о пересечении указанной отметки
Возможность работы на 15-ти + биржах из сервиса.
Важно: Это безопасно: в API ключах, предоставляемых биржей, вы можете поставить запрет на вывод средств. Также сервис хранит ваши данные только имея на это ваше согласие.
Торговля на 15-ти биржах из одного интерфейса, выставление приказов из графиков, отображение баланса на графиках и в интерфейсе.
Торговля из терминала
Плюшки, которые можно получить уже сейчас написав на info@trd.ai:
1. Резервирование мощностей. Для поддержавших проект выставлен наибольший приоритет для расчета маршрутов.
2. Дана возможность отдельно выводить исключительно внутрибиржевые сделки - внутри одной биржи (у обычных пользователей выводится только топ-10 по прибыльности в соответствии с заданными настройками).
3. При поиске наиболее прибыльных сделок учитываются абсолютно все маршруты (стандартные пользователи ограничены: в начальной точке и конечной точке нужно конкретизировать либо биржу, либо валюту.
4. Возможность увеличения глубины поиска до 10 сделок.
5. Снято ограничение на циклические сделки особенно удобно при совершении сделок внутри биржи, когда через 2-3 валютных пары можно оборачивать средства несколько кругов подряд для извлечения прибыли.
6. Возможность фильтров внутрибиржевых арбитражей, выбора нескольких точек начала
7. Выбор нескольких точек старта и конца, выбор фильтра внутрибиржевых арбитражей
Таблица комиссий
Смотрите видео https://www.youtube.com/watch?v=pNhx715vOOk&feature=youtu.be
Приглашаю вас регистрироваться на trd.ai
Если есть вопросы пишите в теме, буду рад ответить.
Мой партнер, программист Hektur хотел заняться майнингом вместе со своим другом. Пока рассматривали варианты, Hektur решил создать сервис, который позволил бы выводить деньги с нескольких бирж одновременно и получать при этом максимальный доход. Суть да дело, в итоге друг моего партнера передумал. Этот же друг был главным спонсором мероприятия, а партнер, не имея достаточного количества
денег, решил не майнить.
уффф, как все запутано, но дальше будет проще)
А арбитражный советник тем не менее остался. Помимо своей главной функции вывода криптовалют с максимальным доходом, сервис ещё и дает рекомендации по арбитражной торговле между биржами. Грех было бросать такое начинание!
Поэтому Hektur решил не запускать работу. К работе над сервисом присоединился я, вместе мы добавили ему функциональности. Затем появились и спонсоры.
Просим вас потестировать сервис, и, если что-то неясно - задать вопросы. На другом форуме тоже есть ветка посвященная проекту. Там мы уже наладили диалог с пользователями они спрашивают, мы отвечаем
Также, я подготовил небольшое описание, чтобы вы смогли быстро разобраться с информацией.
Арбитражный советник «Торговые рекомендации»
Вывод криптосредств с максимальным доходом, рекомендации по арбитражной торговле между биржами
Преимущества
· Анализирует 15 бирж: Bitfinex, Kraken, Bittrex, HitBTC, Exmo, Poloniex, Liqui, GDAX, xBTCe, Binance, BitStamp, itBit, ANX, OKCoin, BTCC,
· Анализирует валюты: USD EUR BTC BCH LTC ETH ETC XMR ZEC.
· Возможность отключать для конкретных бирж фиатные валюты (если вы не прошли авторизацию или подтверждение личности).
· При просчете наиболее выгодных сделок анализирует цепочку глубиной до 10 сделок ежеминутно.
· Позволяет указать стартовую точку (конкретная биржа, конкретная валюта, биржа+валюта, на которой у вас есть баланс) и конечную точку.
· Возможность вывода совокупной информации со всех интересующих бирж и лучшей цены в ячейке
· В секунду анализируется 18,7 триллионов маршрутов.
Возможности
Открытие личных кабинетов (регистрация без верификации почтового адреса) с возможностью редактирования списка бирж, указания личных комиссий на биржах и включения/отключения фиатных валют для каждой биржи. Все настройки индивидуальны.
Наличие уведомлений (алертов) при появлении маршрутов с интересующими параметрами: биржи, валюты, желаемый мин. профит и ширина арбитражного окна (точность определения длительности по времени 12%).
Скоро появится Возможности
Возможность получать уведомления на email и google cloud message.
Вывод информации о стаканах сделок.
Вывод информации о максимальной сумме арбитражного маршрута
Доступ к получению маршрутов по rest-api.
Подписка на котировки и стаканы сделок с помощью web-sockets (и возможно по tcp)
Добавление информации по тех. анализу (важно для инвесторов на долгосрочной основе).
Исторические графики (с выводом по лучшей цене и конкретной бирже). Возможность добавления техиндикаторов на график, добавление уведомлений по событиям и сохранение настроек с тех. индикаторами.
Торговые сигналы и уведомления о пересечении указанной отметки
Возможность работы на 15-ти + биржах из сервиса.
Важно: Это безопасно: в API ключах, предоставляемых биржей, вы можете поставить запрет на вывод средств. Также сервис хранит ваши данные только имея на это ваше согласие.
Торговля на 15-ти биржах из одного интерфейса, выставление приказов из графиков, отображение баланса на графиках и в интерфейсе.
Торговля из терминала
Плюшки, которые можно получить уже сейчас написав на info@trd.ai:
1. Резервирование мощностей. Для поддержавших проект выставлен наибольший приоритет для расчета маршрутов.
2. Дана возможность отдельно выводить исключительно внутрибиржевые сделки - внутри одной биржи (у обычных пользователей выводится только топ-10 по прибыльности в соответствии с заданными настройками).
3. При поиске наиболее прибыльных сделок учитываются абсолютно все маршруты (стандартные пользователи ограничены: в начальной точке и конечной точке нужно конкретизировать либо биржу, либо валюту.
4. Возможность увеличения глубины поиска до 10 сделок.
5. Снято ограничение на циклические сделки особенно удобно при совершении сделок внутри биржи, когда через 2-3 валютных пары можно оборачивать средства несколько кругов подряд для извлечения прибыли.
6. Возможность фильтров внутрибиржевых арбитражей, выбора нескольких точек начала
7. Выбор нескольких точек старта и конца, выбор фильтра внутрибиржевых арбитражей
Таблица комиссий
Смотрите видео https://www.youtube.com/watch?v=pNhx715vOOk&feature=youtu.be
Приглашаю вас регистрироваться на trd.ai
Если есть вопросы пишите в теме, буду рад ответить.
Re: [14000Th] Eligius: 0% Fee BTC, 105% PPS NMC, No registration, CPPSRB
Eligius is handing out work and operating fine, all that is missing is a miner dashboard. Right now for me: connected, diff 4.1K, work being accepted as normal.
No one is getting paid!! What do you mean fine??I have been mining with Eligius for three and a half years. In that time, payments have frequently been delayed due to one hiccup or another, but I have tracked every detail in a spreadsheet, and Wizkid has made it right EVERY SINGLE TIME. Each time, there are a bunch of panicked posts about how the pool is defrauding people, and every time it has amounted to nothing. So yes, it is possible that something has happened to Wizkid and this time is different, but I see no reason to lose faith in somebody who has been consistently loyal and service oriented while operating a mining pool with NO FEES.
Re: [14000Th] Eligius: 0% Fee BTC, 105% PPS NMC, No registration, CPPSRB
Thanks wk. Sorry you get besieged every time the queue gets long. I'm still mining with Eligius, even though with my electric rate it doesn't make financial sense. But I like supporting bitcoin, and I like supporting Eligius, so what the heck.
Re: Spondoolies-Tech released a new miner SP45 NEWTON (ignore this)
Scam is back up at http://spondoolies-tech.co/.
Re: [10000Th] Eligius: 0% Fee BTC, 105% PPS NMC, No registration, CPPSRB
Mining has been a pretty terrible investment, IMO, for a while now. There is pretty much no hardware released in the past year or more that is expected to ever even break even.
I've been mining for 15 months now, with a variety of equipment, currently 7 TH/s. From a fiat perspective, at today's bitcoin prices, the total return on investment (equipment + expenses) has been -50%. As in, if I'd put the fiat cash under a mattress and bought bitcoin with it today, I'd have twice as much bitcoin as I was able to mine. But hindsight is always 20:20, it could have worked out just as easily the other way around. I'm just going to hold and wait and see what happens. I have a hard time making any argument in support of purchasing mining equipment right now, but clearly with the newly skyrocketing difficulty others are drawing different conclusions.
All three OC experiments failed. Both of the other units I tried 250/0750 with looked fantastic for the first hour, then slid into slow decline without any symptoms other than declining hashrate. They bottomed out at about 430 after 12 hours. Reverting to stock and taking a break!
I am not by any means disputing your results as that would be futile, however if I may point out my experience with S3's, it is very rare that you find any two units hashing the same, even when using similar freq & voltage settings, PSU and connected to the same pool.
In your case however, that you have experienced the same wall of performance after the first hour, and that happening on most of your units, leads me to believe the issue must be local to your setup.
My first instinct was a heat / temperature problem, however, you seem to discount this as a possibility, and that the units run as normal on stock frequencies seems to justify that. I am not completely sold though since I have never run an S3 variant at temps as high as yours. Before the season change and my moving my rigs outside, I had them all running the fans at full pelt, aka blue wire hack, which kept the temps low, and now that the seasons have changed and my rigs reside in the garden, my temps are a lot lower.
My second guess is how you are powering your rigs. Though you appear to have the right PSU's, this may be a cause if you have them all plugged into the same extension lead. They may not trip your circuit, but they will compete for power, especially if you are running them off a 110v circuit.
If you choose to attempt the OC again, I wish you luck, but I think in your instance I have given as much help as I possibly can, bearing in mind I am neither an engineer nor an electrician.
Thanks for trying to help! I am both an engineer and an electrician. I do not think I have power issues, as all 6 units are running from Corsair 750 or 800W supplies, with all four PCI-E connectors well seated. Three power supplies are on one 20A 120V circuit, and three are on another. So there is plenty of spare power.
I think what is happening is a slow overheating. Interestingly, the S3s do not appear to respond by increasing the fan speeds, instead the hash rate goes down as we have discussed. All six units are in a well ventilated space that stays around 18C. The S3s report temps around 39-42C, so not very high.
If I find the time, I may try redoing the paste and/or maxing the fan speeds to see if that helps. I will also keep an eye out for any S3 firmware updates that fix something. For now, I have concluded that my six units are not overclockable other than the slight bump I get from setting the frequencies to 225/231/243/237/225/237 for the six.
Very frustrating to see such promising hashrate increases in the first hour, but then nothing sustainable. But overall I am impressed with the units, they are all working to spec and running just fine.
It took longer, but 250/0750 also a dead end. Over 500 first hour, then down. After 3h down to 485 average, 458 last hour on the pool. All "o" on the chips and only 1 HW. Dropping to 243/0750 for the next run.
243/0750 also a dead end, dropped to 4h running average of 471, with last hour on the pool at 449. Trying 237/0750.
I also started playing with the slowest of the others (225 for 453, no voltage change). Trying 250/0750, and so far 2 hours in it is rock solid at the expected 504. Not going to count those chickens, will see what it looks like tomorrow.
237 was repeated "x" from chips over four reboots, so bailed. 231 was 428 over an hour at the pool, also bailed. That unit just doesn't want to OC. Reverted to 225/no-volt.
Other unit, however, continues to hum along at 504 after 5h. I do not understand these things.
I noticed that repeated x's clear when you restart cgminer e.g via the System Start Up tab (which also happens when you Save & Apply settings) - just saying so you can reduce your restart / reboot cycle length.
Been said a lot of times. S3's are the same, but different ..... most of the S3 variants in my stable run best at different settings, and those with the same settings, on the same pool, over the same connection produce differing results! So there goes.
All three OC experiments failed. Both of the other units I tried 250/0750 with looked fantastic for the first hour, then slid into slow decline without any symptoms other than declining hashrate. They bottomed out at about 430 after 12 hours. Reverting to stock and taking a break!
It took longer, but 250/0750 also a dead end. Over 500 first hour, then down. After 3h down to 485 average, 458 last hour on the pool. All "o" on the chips and only 1 HW. Dropping to 243/0750 for the next run.
243/0750 also a dead end, dropped to 4h running average of 471, with last hour on the pool at 449. Trying 237/0750.
I also started playing with the slowest of the others (225 for 453, no voltage change). Trying 250/0750, and so far 2 hours in it is rock solid at the expected 504. Not going to count those chickens, will see what it looks like tomorrow.
237 was repeated "x" from chips over four reboots, so bailed. 231 was 428 over an hour at the pool, also bailed. That unit just doesn't want to OC. Reverted to 225/no-volt.
Other unit, however, continues to hum along at 504 after 5h. I do not understand these things.
It took longer, but 250/0750 also a dead end. Over 500 first hour, then down. After 3h down to 485 average, 458 last hour on the pool. All "o" on the chips and only 1 HW. Dropping to 243/0750 for the next run.
243/0750 also a dead end, dropped to 4h running average of 471, with last hour on the pool at 449. Trying 237/0750.
I also started playing with the slowest of the others (225 for 453, no voltage change). Trying 250/0750, and so far 2 hours in it is rock solid at the expected 504. Not going to count those chickens, will see what it looks like tomorrow.
My procedure lately is to put in freq/volt, save & apply, power cycle, then system/reboot. I added on the last step after just a power cycle would result in bad stats in Miner Status.
I used to have that issue (and always had to do an SSH reboot after a power cycle). Of late, though, it seems to have been fixed .... all I did once is before I rebooted via SSH, I first went into the System -> Start Up tab and stopped cgminer, then entered reboot in the SSH window. Now the stats are OK after a brutal power cycle .... (but I was called names when I mentioned the stats problem on this forum!)
It doesn't happen every time, but a significant % of power cycles result in Miner Status using the previous elapsed time, so everything gets pushed lower. A warm reboot always results in the correct outcome. This is a funny hobby to have, these things have minds of their own.
It took longer, but 250/0750 also a dead end. Over 500 first hour, then down. After 3h down to 485 average, 458 last hour on the pool. All "o" on the chips and only 1 HW. Dropping to 243/0750 for the next run.
On the one test unit, I will now try 250/0750, hardware reset then software reset. Will see what happens! One thing I am wondering is if we are triggering an internal chip overheat of some kind, that throttles it back but doesn't report a bunch of failures. So we try to push them harder, and they actually go slower. But I'm just guessing at this point.
Its your rig, but I'd try 275/0800 first. Simply enter the voltage, save and apply then do a power cycle.
On pushing them harder if they are going to throttle back without showing any outward sign ..... that is the question.
Sorry, missed this post. I will try 275/0800 after we see what happens with 250/0750. My procedure lately is to put in freq/volt, save & apply, power cycle, then system/reboot. I added on the last step after just a power cycle would result in bad stats in Miner Status. Have you tried OC on an S3+ with factory thermal paste? The six I am working with are untouched. So if it is a chip-level thermal problem that is not reported to the sw, then I guess that could explain the difference here.
.... But I would also expect the symptoms you describe with an overheat, and I'm not seeing them. No increasing temps, no "x"s on the chips, HW errors still negligible. Fan speeds are dropping, now 1800-1900, down from 2200-2300. So the unit is getting cooler as it slows down. .... ...
There, my friend, is the sign you are looking for!
Fan speeds dropping ... unit is getting cooler
That means there are some chips that have gone offline! EDIT: Either that, or the chips are not getting work ..... now you see how that the queue argument was formented in my mind?
Does it? Why are all chips still reporting "o" and not "-" or "x"? That is why I'm wondering about the internal throttling. There should be plenty of work, I have tried leaving queue at default as well as deleting queue parameter completely. I have not tried --queue 1024 yet though. But I saw the same result with two different pools and with and without deletion of the parameter.
New test run started: 1024 firmware, 250/0750, queue left at stock, cgminer left at stock. Only change to stock is the additional options in cgminer.lua, which do not change the 250 values.
And yes, that is more like a death spiral, too damn right! I'd have expected it to be flashing x's all over + an increase in HW errors at this point, but then again the new binaries support that --bitmain-hwerror option (or such like) that I have never gotten my head around! I think its that time to try the 0800 setting .... I am convinced it is a heat problem your rigs are encountering due to its consistency in drop-off, so reducing the voltage may help (but may need a power cycle, infact I'd say do one even though I do all my tests initially without one).
OK, I'm going to call it a death spiral now. 98 minutes into the run, 15m hashrate of 375 at the pool, miner reports average dropped to 495. All chips still "o", temps 41/41, and a total of 5 HW errors. But I would also expect the symptoms you describe with an overheat, and I'm not seeing them. No increasing temps, no "x"s on the chips, HW errors still negligible. Fan speeds are dropping, now 1800-1900, down from 2200-2300. So the unit is getting cooler as it slows down. I saw the same behavior on all six units, so we are missing something here.
On the one test unit, I will now try 250/0750, hardware reset then software reset. Will see what happens! One thing I am wondering is if we are triggering an internal chip overheat of some kind, that throttles it back but doesn't report a bunch of failures. So we try to push them harder, and they actually go slower. But I'm just guessing at this point.
4. If you've recently started the rig, could you post the cgminer startup string (usually logged in system log ...?)?
From the process tab:
cgminer --bitmain-options 115200:32:8:14:275:0a82 -o stratum+tcp://us1.ghash.io:3333 -O USER.WORKER:Any -o stratum+tcp://stratum.mining.eligius.st:3334 -O ADDR_WORKER:Any -o stratum+tcp://mint.bitminter.com:3333 -O USER_WORKER:PASS --bitmain-nobeeper --api-listen --api-network --bitmain-checkn2diff --bitmain-hwerror --version-file /usr/bin/compile_time --lowmem
From the process tab:
cgminer --bitmain-options 115200:32:8:14:275:0a82 -o stratum+tcp://us1.ghash.io:3333 -O USER.WORKER:Any -o stratum+tcp://stratum.mining.eligius.st:3334 -O ADDR_WORKER:Any -o stratum+tcp://mint.bitminter.com:3333 -O USER_WORKER:PASS --bitmain-nobeeper --api-listen --api-network --bitmain-checkn2diff --bitmain-hwerror --version-file /usr/bin/compile_time --lowmem
I remember reading somewhere that it is not a good idea to run without a queue, rather have a reduced one to the 2048 one that ships. I run mine with --queue 1024, so you could possibly try --queue 512 if you are averse to having a long one. (I am not conversant with the why's of this, so please don't ask!)
Here's where that came from, ckolivas's recommendation when he released the S3 binary I am currently using on the OC unit:
Here's an updated S3 binary.
http://ck.kolivas.org/apps/cgminer/antminer/s3/4.6.1-141020/cgminer
Recommended if you're mining on p2pool for the default binary actually discards stale shares which you should never do, especially on p2pool. Also includes changes to queuing and memory usage that were necessary on S4 but probably only of minor benefit here. Recommend you edit the cgminer startup script to remove the --queue value entirely, and add --lowmem. Performance should be pretty much unchanged.
http://ck.kolivas.org/apps/cgminer/antminer/s3/4.6.1-141020/cgminer
Recommended if you're mining on p2pool for the default binary actually discards stale shares which you should never do, especially on p2pool. Also includes changes to queuing and memory usage that were necessary on S4 but probably only of minor benefit here. Recommend you edit the cgminer startup script to remove the --queue value entirely, and add --lowmem. Performance should be pretty much unchanged.
Death spiral on the OC unit definitive now, average down to 523 GH/s. All chips good with "o", still just the 3 HW errors, temps 42/38. This would bother me less if I had some explanation for what is happening.
2. What is the HW %
0 (zero). Last try it got a an occasional HW error, but they were minor. One of the six units got a bogged down in HW errors, but then performed well when I dropped the frequency to 268.
0 (zero). Last try it got a an occasional HW error, but they were minor. One of the six units got a bogged down in HW errors, but then performed well when I dropped the frequency to 268.
I assume that when your avg hash-rate falls you restart(ed) immediately, so seeing you have no HW errors, could you let it run for at least an hour after that and see whether you get any HW errors and / or x's on the chips?
I also noticed that the 5s hash-rate flactuates whenever a new block is started / a block is about to end, but soon builds up, so that may be something you have to bear in mind (assuming your hash-rate recovers!).
Unit hashrate dropping sharply now after the 1 hour run, average down to 533. HW errors now 3 for 0.0093%.
If hashrate keeps falling, I will report the numbers and try again with 0800.
I'm only going to try this with the one unit, the improvement was so dramatic the last time that when it was solid for an hour, I upgraded all 6. But I have yet to have an OC last more than 90 minutes or so.
Did you try 275/0800 before 275/0815?
Not this time, just went with 0815. 1 hour in now, showing average 539 GH/s. You can see the slowdown starting though, average is decreasing, and temps now 42/38. I am consistently getting 1 hour of improved performance, then the slowdown starts. I am using the 1024 firmware, the only change on top of that is adding the new frequencies into cgminer.lua. All six units stable again at the lower frequencies with no voltage setting.
Trying again on one unit, this time with ckolivas's S3 cgminer 4.6.1 build, also deleting --queue and adding --lowmem. I can't think of anything else to try. The S3's are in a ventilated space, so the ambient temperature over the three hour period is constant. Why would I get great results for 1+ hours, but poor results over 3 hours?
Possibly easier to simply post a shot of your web UI, but I'll ask just in case:
1. What temps do you have on that rig?
Right now showing 43 & 42 25 minutes in (and reporting 538 GH/s avg), it don't think it got above 44 the last time I tried it. Ambient temp in the room 18C.
2. What is the HW %
0 (zero). Last try it got a an occasional HW error, but they were minor. One of the six units got a bogged down in HW errors, but then performed well when I dropped the frequency to 268.
3. What freq are you running at?
275/0815 target, last night's test I ran five that way, then the one I dropped to 268/0815.
4. If you've recently started the rig, could you post the cgminer startup string (usually logged in system log ...?)?
From the process tab:
cgminer --bitmain-options 115200:32:8:14:275:0a82 -o stratum+tcp://us1.ghash.io:3333 -O USER.WORKER:Any -o stratum+tcp://stratum.mining.eligius.st:3334 -O ADDR_WORKER:Any -o stratum+tcp://mint.bitminter.com:3333 -O USER_WORKER:PASS --bitmain-nobeeper --api-listen --api-network --bitmain-checkn2diff --bitmain-hwerror --version-file /usr/bin/compile_time --lowmem
5. Finally, could you also post the freq setting line that you are running from the cgminer.lua file?
pb:value("14:275:0a82", translate("275M"))
[/quote]
Thanks for the help! Answers above in bold.
I continue to find this extremely frustrating. I am running 6 S3+ units, each supplied by a 750-800W power supply with a single 12V rail and all four PCI-E connectors connected. I tried the 275/0815 settings, and exactly the same thing happened as the last time. Hour 1: fantastic, all units over 500 GH/s, holy crap why did I not do this earlier. Hour 2: OK, but hashrates down both as reported by units and at the pool. Hour 3: terrible, all hashrates reported by units and by pool way below stock results. So I have yet again reverted everything to 225/231/243/237/225/237 with voltage left blank.
I do not understand the mechanism here. If it is heat, why does it take 2 hours to show up? With the OC settings, all chips show up as "o" and working. But the hashrate results speak for themselves. But why the very prominent jump in hashrate for the first hour, but then utter crap out in hour 3? Can anybody explain this?
I do not understand the mechanism here. If it is heat, why does it take 2 hours to show up? With the OC settings, all chips show up as "o" and working. But the hashrate results speak for themselves. But why the very prominent jump in hashrate for the first hour, but then utter crap out in hour 3? Can anybody explain this?
Which firmware are you using?
I am using the 1024 firmware, the only change on top of that is adding the new frequencies into cgminer.lua. All six units stable again at the lower frequencies with no voltage setting.
Trying again on one unit, this time with ckolivas's S3 cgminer 4.6.1 build, also deleting --queue and adding --lowmem. I can't think of anything else to try. The S3's are in a ventilated space, so the ambient temperature over the three hour period is constant. Why would I get great results for 1+ hours, but poor results over 3 hours?