Yes, I used 12 gauge...the breaker is double posted...but it says that its internally connected. Did I f-up?
Like so?
Topic: CoinTerra announces its first ASIC - Hash-Rate greater than 500 GH/s - page 33. (Read 231002 times)
February 12, 2014, 05:06:59 PM
Like so?
February 12, 2014, 04:57:11 PM
Yes, I used 12 gauge...the breaker is double posted...but it says that its internally connected. Did I f-up?
February 12, 2014, 04:39:36 PM
BTW - I installed a 70A 120V circuit breaker in my main breaker box and ran two 20A dual-plug outlets. Each miner has each of its PSUs plugged into either outlet so that both miners are sharing both ciruits. Each circuit should be good for 20A * 120V = 2400W.
Pardon? What guage wire did you run? Are you implying that you ran both 'hots' to a single 70A breaker?
February 12, 2014, 04:08:47 PM
I should also point out however, that Peter Kirby (CoinTerra) responded to my texts within a couple minutes and has been very communicative. He has already escalated my case to support and they are addressing the problem in a VERY professional & high priority fashion (in my opinion).
February 12, 2014, 04:00:44 PM
I just got my tracking number for my two miners....should have them up and running tomorrow.
Order #594
Paid on AUG 23rd, 2013
Received tracking on FEB 11th, 2014
Received system on FEB 12th, 2014
average hash rate 1st Miner - 1.6 TH/s
average hash rate 2nd miner - 750 GH/s (only 1 chip operational ATM)
power draw - approx 1900W each, based on readings from my "KILL A WATT"
I'm a bit disappointed that one of the chips in my 2nd box is not running. But Peter responded to my text message immediately and we're troubleshooting the problem at this time.
After two hours...as you can see, one of my miners is only running a single chip
http://i161.photobucket.com/albums/t228/miahallen/TerraMinerIV_01.png
http://i161.photobucket.com/albums/t228/miahallen/TerraMinerIV_02.png
BTW - I installed a 70A 120V circuit breaker in my main breaker box and ran two 20A dual-plug outlets. Each miner has each of its PSUs plugged into either outlet so that both miners are sharing both ciruits. Each circuit should be good for 20A * 120V = 2400W.
February 12, 2014, 03:12:55 PM
The cointerra driver has now been merged into the cgminer git master code, so the lucky few who already have hardware can try it out by running their devices directly with a PC via USB. While there are probably fixes generically in the code from the main cgminer code, it is entirely possible there are still bugs in the driver code that will only show up only with real world testing.
I should add the cointerra device+protocol+driver has the most advanced work model designed for p2pool or similar networking and bitcoin transaction propagation with virtually seamless work restarts for rapid frequent block changes such as those required by p2pool, along with flushing of any queued work on a work template update such as that which occurs regularly with stratum update so it will always be working on the most current work - meaning it is optimised for maximum transmission of transactions, provided the pool is updating its work template frequently with new transactions. Kudos to the cointerra team for adopting everything I recommended in their work transmission/protocol. February 12, 2014, 02:29:12 PM
I just got my tracking number for my two miners....should have them up and running tomorrow.
Order #594
Paid on AUG 23rd, 2013
Received tracking on FEB 11th, 2014
Received system on FEB 12th, 2014
average hash rate 1st Miner - 1.6 TH/s
average hash rate 2nd miner - 750 GH/s (only 1 chip operational ATM)
power draw - approx 1900W each, based on readings from my "KILL A WATT"
I'm a bit disappointed that one of the chips in my 2nd box is not running. But Peter responded to my text message immediately and we're troubleshooting the problem at this time.
February 12, 2014, 01:49:15 PM
anyone outside of US received tracking number yet?
February 12, 2014, 01:27:06 PM
The cointerra driver has now been merged into the cgminer git master code, so the lucky few who already have hardware can try it out by running their devices directly with a PC via USB. While there are probably fixes generically in the code from the main cgminer code, it is entirely possible there are still bugs in the driver code that will only show up only with real world testing.
I should add the cointerra device+protocol+driver has the most advanced work model designed for p2pool or similar networking and bitcoin transaction propagation with virtually seamless work restarts for rapid frequent block changes such as those required by p2pool, along with flushing of any queued work on a work template update such as that which occurs regularly with stratum update so it will always be working on the most current work - meaning it is optimised for maximum transmission of transactions, provided the pool is updating its work template frequently with new transactions. Kudos to the cointerra team for adopting everything I recommended in their work transmission/protocol.testerx -
a few ideas worth trying...
try a few different pools and see if you're still seeing the same issue, eg. eligius, etc. when i looked, the cgminer reported perf was pretty close to the mining pool reported performance on my systems.
also, check you've got the two ac power cables attached to two different circuits in your home. not just two different sockets.. make sure each socket is on a different breaker, to ensure you're getting all the power to the box that it needs (its drawing 2,000 watts which is too much for one single breaker)
and also what happens if you try selecting a slower hashing speed? does it still have a disparity between cgminer reported perf and pool reported perf?
-- Jez
If you are on the same breaker you are using over 80% (83%) which is a HUGE no no, that is granted if you are in the US and on a 20amp breaker (15 amp breaker you'd be done).
February 12, 2014, 01:26:25 PM
FWIW, My unit works fantastically on P2Pool. I appear to get somewhat above the web ui reported rate, and the device has the lowest stale rate I've seen on any hardware device (0.23x of the Avalon batch 1's stale rate, about 0.78x the bitmain antminer S1 which was the prior best I'd seen).
February 12, 2014, 01:19:29 PM
The cointerra driver has now been merged into the cgminer git master code, so the lucky few who already have hardware can try it out by running their devices directly with a PC via USB. While there are probably fixes generically in the code from the main cgminer code, it is entirely possible there are still bugs in the driver code that will only show up only with real world testing.
I should add the cointerra device+protocol+driver has the most advanced work model designed for p2pool or similar networking and bitcoin transaction propagation with virtually seamless work restarts for rapid frequent block changes such as those required by p2pool, along with flushing of any queued work on a work template update such as that which occurs regularly with stratum update so it will always be working on the most current work - meaning it is optimised for maximum transmission of transactions, provided the pool is updating its work template frequently with new transactions. Kudos to the cointerra team for adopting everything I recommended in their work transmission/protocol.testerx -
a few ideas worth trying...
try a few different pools and see if you're still seeing the same issue, eg. eligius, etc. when i looked, the cgminer reported perf was pretty close to the mining pool reported performance on my systems.
also, check you've got the two ac power cables attached to two different circuits in your home. not just two different sockets.. make sure each socket is on a different breaker, to ensure you're getting all the power to the box that it needs (its drawing 2,000 watts which is too much for one single breaker)
and also what happens if you try selecting a slower hashing speed? does it still have a disparity between cgminer reported perf and pool reported perf?
-- Jez
February 12, 2014, 08:54:28 AM
The cointerra driver has now been merged into the cgminer git master code, so the lucky few who already have hardware can try it out by running their devices directly with a PC via USB. While there are probably fixes generically in the code from the main cgminer code, it is entirely possible there are still bugs in the driver code that will only show up only with real world testing.
I should add the cointerra device+protocol+driver has the most advanced work model designed for p2pool or similar networking and bitcoin transaction propagation with virtually seamless work restarts for rapid frequent block changes such as those required by p2pool, along with flushing of any queued work on a work template update such as that which occurs regularly with stratum update so it will always be working on the most current work - meaning it is optimised for maximum transmission of transactions, provided the pool is updating its work template frequently with new transactions. Kudos to the cointerra team for adopting everything I recommended in their work transmission/protocol.gmaxwell mentioned this on irc last night as well, stating that Cointerra handled p2pool terrific.
February 12, 2014, 08:32:01 AM
The cointerra driver has now been merged into the cgminer git master code, so the lucky few who already have hardware can try it out by running their devices directly with a PC via USB. While there are probably fixes generically in the code from the main cgminer code, it is entirely possible there are still bugs in the driver code that will only show up only with real world testing.
I should add the cointerra device+protocol+driver has the most advanced work model designed for p2pool or similar networking and bitcoin transaction propagation with virtually seamless work restarts for rapid frequent block changes such as those required by p2pool, along with flushing of any queued work on a work template update such as that which occurs regularly with stratum update so it will always be working on the most current work - meaning it is optimised for maximum transmission of transactions, provided the pool is updating its work template frequently with new transactions. Kudos to the cointerra team for adopting everything I recommended in their work transmission/protocol.
February 12, 2014, 08:09:26 AM
My early Jan order is still "processing"
February 12, 2014, 05:43:47 AM
Does anybody know what the default IP address is or is this thing supposed to do a DHCP request?!
You can connect directly to the console output of the cointerra via USB to get your IP.
1) Connect a USB cable from your PC/Laptop to the cointerra
2) Download and launch putty
3) Select Serial
4) Enter "COM5" and speed 115200
5) The open
6) Login with user: root, pass: cointerra
7) ifconfig
You might need to look at your device manager to see what COM port the USB cable attaches too.
I changed mine to a static IP.
February 12, 2014, 05:18:51 AM
The cointerra driver has now been merged into the cgminer git master code, so the lucky few who already have hardware can try it out by running their devices directly with a PC via USB. While there are probably fixes generically in the code from the main cgminer code, it is entirely possible there are still bugs in the driver code that will only show up only with real world testing.
I should add the cointerra device+protocol+driver has the most advanced work model designed for p2pool or similar networking and bitcoin transaction propagation with virtually seamless work restarts for rapid frequent block changes such as those required by p2pool, along with flushing of any queued work on a work template update such as that which occurs regularly with stratum update so it will always be working on the most current work - meaning it is optimised for maximum transmission of transactions, provided the pool is updating its work template frequently with new transactions. Kudos to the cointerra team for adopting everything I recommended in their work transmission/protocol. February 12, 2014, 04:40:17 AM
Still on for an update tomorrow? Thanks.
In their austin office this second.
Im now told to go to austin
Sounding good then unless Im missing something. Really looking forward to this appreciate it
in dallace drinking with ct guys.
all is good.
From auctions section looks like the higher ups are in Dallas getting their drink on with Goat. Although earlier in the thread he said they will be in Austin tomorrow. Hopefully someone with pull can answer your question by then.
February 12, 2014, 02:34:13 AM
Cointerra why are you not honoring your hashrate guarantee for Early January customers?
I emailed support and received this response:
I think reasonable people can accept that there were delays and you might be late delivering, but I'd imagine this guarantee caused a lot of people who would not have ordered in the first place to order your equipment. Please explain how March 2nd can possibly work as a guarantee date for "Early January" orders.
I emailed support and received this response:
Quote
Our legal team has determined that the 30 day late delivery agreement does not kick in until March 2nd. Sorry, I know that this is such a hassle.
I think reasonable people can accept that there were delays and you might be late delivering, but I'd imagine this guarantee caused a lot of people who would not have ordered in the first place to order your equipment. Please explain how March 2nd can possibly work as a guarantee date for "Early January" orders.
According to the general sales agreement if they are late you are entitled to request a refund ... they already are letting you request a refund with a January order. So while they may not admit to being late - you are already enjoying all the benefits as if they did.
they had a hashrate guarantee. They said if they were more than 30 days late, they would compensate us.
They're going to be more than 30 days late, but they just recently changed the terms to 45 days because their lawyer said they could.
This isn't about making a return, it's about getting what we paid for, under the terms of the transaction. I am requesting binding arbitration.
February 11, 2014, 11:22:00 PM
Box up and running but it is underperforming badly only doing 1.3 Thash at best....this is a lot more than a 25 percent drop on the performance so I ended up paying 14000 for 1.3thash apparently.
so I ended up paying 14000 for 1.3thash apparently.I don't doubt your report, though I'm curious if you've tried different pools, long polling, solo mining, etc. What's the power draw at the wall? I'm eager to troubleshoot this with you, since you may not be the only one with this problem (I do not yet have one to test with).
February 11, 2014, 11:02:17 PM
Cointerra why are you not honoring your hashrate guarantee for Early January customers?
I emailed support and received this response:
I think reasonable people can accept that there were delays and you might be late delivering, but I'd imagine this guarantee caused a lot of people who would not have ordered in the first place to order your equipment. Please explain how March 2nd can possibly work as a guarantee date for "Early January" orders.
I emailed support and received this response:
Quote
Our legal team has determined that the 30 day late delivery agreement does not kick in until March 2nd. Sorry, I know that this is such a hassle.
I think reasonable people can accept that there were delays and you might be late delivering, but I'd imagine this guarantee caused a lot of people who would not have ordered in the first place to order your equipment. Please explain how March 2nd can possibly work as a guarantee date for "Early January" orders.
According to the general sales agreement if they are late you are entitled to request a refund ... they already are letting you request a refund with a January order. So while they may not admit to being late - you are already enjoying all the benefits as if they did.
"Letting us request a refund" daveepsilon is shilling again. You can demand a refund whenever you want and are legally entitled to it. If you're a small buyer and don't have an 'in' with cointerra I would recommend doing that now, especially with this recent price dip. 1.3 TH/s @2200 WATTS what a fucking joke.
Jump to: