 Show Posts
|
|
Pages: « 1 [2] 3 4 5 »
|
|
Hi Fuse,
something is not working well with tagmining pool. The payouts are to late and the chart shows even no payouts. Since July 16 I don't mine on the pool. Last payout was on July 22. Don't know the value of the payout was ok or not. My address is TB4VdPAVp8Tg47wFn7kyF1kNBt1N2YgM1R
I hope you can fix the pool soon.
Thank you
|
|
|
|
|
Hi presstab,
while I like your explorer page, the "Annulized Stake Rate" chart is quite misleading. The chart assumes an average stake rate of 200%. But that is not the case. The average stake rate is currently less than 60% only.
Calculation:
current supply: 583,306,124 HYP
blocks/year: 960 * 365 = 350,400
Assuming each block gets the max 1000 HYP, we will mine 350,400,000 HYP per year.
100 * 350,400,000 HYP / 583,306,124 HYP = 60,07%
Not each block will mine 1000 HYP, so the real percentage is even lower.
While the supply is increasing and the yield is fixed, the percentage will go down a bit each day.
It would be great, if you may present a chart with such data.
Thanks
|
|
|
|
Hm. Clocking down to 250 did not work, two sets of power supplies dropped off. Switching voltages didn't help either, below a specific clock speed (275) dies will fall off line.
Which makes *no* sense, but seems to fit a pattern: Titans have a sweet spot where they are stable in a voltage/frequency level. Run them there, things are good. Run them other places and the power supplies destabilize.
They start to behave like that, when they get older. Maybe it helps to replace the 5 ceramic capacitors at the input of the power supply. These capacitors are dedicated to reduce interferences triggered by the ASIC power consumption changes. With a 300 MHz oscilloscope that should be visible. Did you found out the capacity of those 5 capacitors? In one of your previous posts, you wrote something about 25 uF. Are all 5 identical with 25 uF ? |
|
|
|
.... but a/c vs miners (with help from summer heat) always win....so yeah i may have to shut down on the really hot days me thinks (my units are 17 months old now)
anyway my arrangement works..if it stops working I have 2 more windows I can put 2 more fans up ..1 push and one shutter fan it out
This way of cooling may be useful for you and others. I have separated a small area with a window inside. The miner fans get fresh air from outside and blow the warm air into the room. No extra fans required. another window is open to let the warm air out. The advantage is, that no preheated air went into the miner again. Even the room where the warm air went into is much cooler now.  [img=http://s30.postimg.org/4zyesd47h/IMG_7002.jpg] |
|
|
|
Disappeared DCDC on advanced pageI have noticed, a DCDC converter is not listed on the advanced web page if the DCDC PMbus of the missing device does not answer. /home/pi/knc-asic/waas/waas -g all-asic-inforeports i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98 In that case a power cycle is required to get the DCDC working again. This may be a reason for a hanging DCDC: On specification page 5: Each DCDC converter shall be connected to External CIN = 470 μF/10 mΩ, COUT = 470 μF/10 mΩ. See Operating Information section for selection of capacitor types.
Operating instructions are on Page 41: A minimum capacitance of 300 μF with low ESR is
recommended. ..... For high-performance/transient applications or
wherever the input source performance is degraded, additional
low ESR ceramic type capacitors at the input is recommended. The ceramic capacitors are on the board, near to each DCDC converter as recommended. But instead of having a capacitor for each DCDC converter, they have inserted a single capacitor with higher capacity for all DCDC together. But the way from the capacitor to the DCDC converter creates additional inductance. While the capacitor is getting older, the stable frequency is changing. That may be a reason for these islands of stability on Titans for some frequency ranges. The Ericson DCDC specification is available for download at http://archive.ericsson.net/service/internet/picov/get?DocNo=28701-EN/LZT146435&Lang=EN&HighestFree=Y
|
|
|
|
Anyone having problem with the KNC Neptune Web interface?
I cant access the first site, and not the "advanced settings" either. The neptune does not work, but I can browse the other menues.
I am willing to pay for someone to help me with this one.
Try to install the original image on another SD card. Image and instructions: http://www.kncminer.com/support/neptune-setup-and-firmware |
|
|
|
POLL:
Based off of ... I believe lightfoot's recommendation ...
For my next release, who would find a "cable / connector life saver" option valuable?
Basically it would be an algorithm to guestimate how much power is being drawn through each PSU cable assuming the Y connector & 2 PSU cables are present, per cube.
The algo would then take into account current draw per DCDC & overall watts & possibly even temps guestimated by the cube and then drop the clocks down until the power usage would be below 140-150w per cable coming off the cube.
This would of course make the Titan slower but far less risk of burning cables.
I really dont know how valuable such an option will ultimately be, because I know most miners just want to push these things as hard as they will go and when stuff does burn up, just replace and move on.
So, may be a lot of work for nothing really. But its an interesting idea =P
I have noticed that when multiple dies fail at the same time that this is a great signal that there is a power problem. I have alarms set when mh/s drops below a certain level I can manually monitor the advanced page. On the last alarm 2 dies failed at the same time, on the same cube and your firmware soft restarted them. A few hours later the whole cube failed because the psu shutdown so I checked the cube and discovered the fried pcie connector. And this PCIE was seriously burnt, there wasn't much left of it, the male/female were melted/fused together, I needed pliers to separate them. In this case restarting the dies earlier certainly didn't help. So maybe some logic that when 2 or more dies fail at the same time just shut the whole cube down till it is cold started or rebooted. I don't know if or how often this would generate false alarms, but I've never noticed 2 dies failing at the same time except in this instance. Unless that exact situation can be reproduced more than a few times .... it could have been just coincidence at this point =( Even then, 2 dies could go down around the same time and there not be any power issue at all. Ive witnessed it several times on my Titan. But, a definite pattern of many different miners would have to prove this is the case before coding this into the firmware. It is possible to measure this. Usually we have an input of 12.0 V. If the connector starts to be fried the resistor of the connector is increasing. Thats why the connector is getting hot while a high current went trough. At the DCDC regulator the input voltage will get lower. When the voltage is lower, the dies are failing more often. The DCDC regulator provides the input voltage VIN as well. VIN is currently not used by the firmware. But it is already coded in libpmbus.c Have a look into function test_ericsson pmbus_read_vin(i2c_bus, ERICSSON_I2C_WORKAROUND_DELAY_us); may be used in waas.c |
|
|
|
Hi, I bought a used Titan which had a donated/pre-paid 99e version installed. Is it possible to get an update to the latest version? Is it possible to disable the energy saving feature? According to the description, you found an important bug in the original KNC code: Noticed in rare cases dies are configured with positive voltage – wrote correction code for this. Maybe that bug leads to dies with 0.8V idle issue. May you explain a bit more about the bug please. In which situations it occurs, what did you improve? I tried to find the source code of your version 1.0.0, but found the readme and license only on github. Where can I find the latest source code? Thanks Joerg |
|
|
|
|
These nodes are currently working:
addnode=198.205.118.181:38003
addnode=85.24.169.215:54460
addnode=108.61.10.90:49551
addnode=84.85.59.189:36002
addnode=204.11.237.233:57893
addnode=54.223.76.165:34838
addnode=162.255.117.105:63612
addnode=158.69.27.82:48974
addnode=54.252.51.245:63331
addnode=98.115.147.74:34335
addnode=88.127.17.14:50057
addnode=178.197.237.53:17378
addnode=85.25.44.119:41120
addnode=209.188.18.188:59635
addnode=213.239.202.92:60135
addnode=148.251.19.213:63668
addnode=94.137.49.90:16383
addnode=82.170.116.109:52616
|
|
|
|
|
My API access is still working.
|
|
|
|
The only STR pool I know is hash-to-coins.comBut STR is down for maintenance since Mar 27, 2015 at 22:20 I guess they are waiting for Cryptsy  |
|
|
|
Im receiving reports of some deposits not posting. Is there a block explorer or working pool with chain statistics?
I see there is a new repository. I may have reverted to an older client during recent infrastructure changes as I show the older repo reflected in our database. I havent synced with the new client again yet but im assuming the broadcast checkpointing is active after the latest commit? That would explain the stall in our chain after it successfully synced for some time. I should have starcoin restored in the next few days.
It looks like there is neither an explorer nor any pool remaining. But it would be great if you could get the wallet running again on Cryptsy. Here is some blockinfo, so you can be sure to take the right blockchain. A single peer has left for me: 21:11:28
getpeerinfo
21:11:28
[
{
"addr" : "71.175.81.45:18216",
"services" : "00000001",
"lastsend" : 1428174676,
"lastrecv" : 1428174681,
"conntime" : 1427917242,
"version" : 60007,
"subver" : "/StarCoin:1.7.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 2061518,
"banscore" : 0
}
]
Here is some info about a block which was found today. Using commands getblockhash and getblock you may check for the block. And others may confirm as well to work on the same chain.
21:19:06
getblockhash 2071865
21:19:06
000000023eb8a066a45ec8a1229869ba26d696daeeba723cc7eb52987738f1ad
21:20:09

getblock 000000023eb8a066a45ec8a1229869ba26d696daeeba723cc7eb52987738f1ad
21:20:10
{
"hash" : "000000023eb8a066a45ec8a1229869ba26d696daeeba723cc7eb52987738f1ad",
"confirmations" : 137,
"size" : 267,
"height" : 2071865,
"version" : 4,
"merkleroot" : "0510eeec17ed467d67e8efabb88e193c255de9728a15e41483de3ee2d6eda6c9",
"mint" : 50.00000000,
"time" : 1428171861,
"nonce" : 2561578165,
"bits" : "1d03151c",
"difficulty" : 0.32441142,
"previousblockhash" : "00000000ca18c9195edd903d80fa9c803bfd7b2bea6ad7ef7e61296195769385",
"nextblockhash" : "00000001bf1ec57efd1db78292d2119a8bb39a402c182e3db94d1c39fd689ed8",
"flags" : "proof-of-work",
"proofhash" : "000000023eb8a066a45ec8a1229869ba26d696daeeba723cc7eb52987738f1ad",
"entropybit" : 1,
"modifier" : "3333a03ed3cc8134",
"modifierchecksum" : "f72ff73a",
"tx" : [
"0510eeec17ed467d67e8efabb88e193c255de9728a15e41483de3ee2d6eda6c9"
],
"signature" : "304502204dde3a7f0b3a81cb21223d83292fa3ea671c68e9f856e4137e1a46500ebd3164022100f e124a6ddb493254306579efbdda4064379debef233d87a65d68474519ddde8a"
}
I hope that helps. |
|
|
|
Do I need to update something?
My STR coins suddenly did not reach cryptsy. Last successfull deposit transaction was on March 5, 2015.
same with me In the meantime I found the cryptsy wallet status page https://www.cryptsy.com/pages/statusIt looks like cryptsy has lost connection to other up to date nodes. The last received block is quite old. I have opened a support ticket at cryptsy. They are working on that issue... |
|
|
|
|
Do I need to update something?
My STR coins suddenly did not reach cryptsy. Last successfull deposit transaction was on March 5, 2015.
|
|
|
|
Hi,
my wallet v0.9.1.1-PID-beta is out of sync, but I have 7 connections to the network.
Did I miss any update?
What do I need to do?
Thanks
We have an extraordinary long block going on right now. Your wallets will say out of sync until a block is found. Blak Thank you for explanation. Indeed, the wallet is in sync again. |
|
|
|
|
Hi,
my wallet v0.9.1.1-PID-beta is out of sync, but I have 7 connections to the network.
Did I miss any update?
What do I need to do?
Thanks
|
|
|
|
@joef, just solo mine several blocks for v1 coin, and you're ok
don't u see that blockchain simply stopped...
while the wallet is out of sync, solo mine is not possibe :-( |
|
|
|
|
Hi,
my wallet v1.2 is out of sync. I tried to send my coins in the hope that the wallet will sync again.
But until now it does not sync again.
I have 4 active connections and sent 148401 coins.
My wallet connection port is at feler.homelinux.org:21451
Maybe it is possible to stimulate the wallet?
getpeerinfo
[
{
"addr" : "209.188.18.188:21451",
"services" : "00000001",
"lastsend" : 1425168697,
"lastrecv" : 1425168694,
"conntime" : 1425166577,
"version" : 70000,
"subver" : "/MetalMusicCoin:1.2.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 152743,
"banscore" : 0
},
{
"addr" : "199.68.198.33:21451",
"services" : "00000001",
"lastsend" : 1425168698,
"lastrecv" : 1425168758,
"conntime" : 1425166594,
"version" : 70000,
"subver" : "/MetalMusicCoin:1.2.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 152743,
"banscore" : 0
},
{
"addr" : "108.61.10.90:21451",
"services" : "00000001",
"lastsend" : 1425168758,
"lastrecv" : 1425168697,
"conntime" : 1425166594,
"version" : 70000,
"subver" : "/MetalMusicCoin:1.2.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 152743,
"banscore" : 0
}
]
An error was reported as I tried to send all at once. So I created 3 transactions:
[
{
"account" : "",
"address" : "MgJ183ioD37VkBWCtjt83ELVhG1SpLQVik",
"category" : "send",
"amount" : -50000.00000000,
"fee" : -0.58000000,
"confirmations" : 0,
"txid" : "b9493207082b440036531a47959a91c6c96d5a491fc2668fd274bcbd872c407f",
"time" : 1425166810,
"timereceived" : 1425166810
},
{
"account" : "",
"address" : "MgJ183ioD37VkBWCtjt83ELVhG1SpLQVik",
"category" : "send",
"amount" : -50000.00000000,
"fee" : -0.58000000,
"confirmations" : 0,
"txid" : "fd7e57ea539efca83afe70a779641a9baf1039132b2f2c03721bf784d048f185",
"time" : 1425167928,
"timereceived" : 1425167928
},
{
"account" : "",
"address" : "MgJ183ioD37VkBWCtjt83ELVhG1SpLQVik",
"category" : "send",
"amount" : -48401.00000000,
"fee" : -0.56000000,
"confirmations" : 0,
"txid" : "13b3e47fee43e699531e01acd61d4989091de8201cd934ca85a4cfd2410a8d43",
"time" : 1425168403,
"timereceived" : 1425168403
}
]
My new MTLMCv3 address is Me15asoLgExZ3KiMRkUvCNVaRGJ13nezdP
|
|
|
|
OMG whats going on with dnotes mining right now network going down and pools not working help help  under attack or what The network is running, but there might be a problem with the block reward as of the switch at block 525949. Looking into it. There is a bug in the subsidy calculation: int yearsElapsed = nHeight / 525949; int64 nReductionPercentage = pow(0.95,yearsElapsed); nSubsidy = nSubsidy * nReductionPercentage; ==> integer from a value less than 1 is always 0 since block 525949 the value of nReductionPercentage is 0 So there are fees in the block reward only. |
|
|
|
|
