I just sent BTC for 32 chips.
Thanks!
Chad
Topic: Liquid Synergy Designs Inc. -ASIC mining hardware - page 167. (Read 423299 times)
just paid for my boards 
Your order # is: 100000110.
Your order # is: 100000110.
I'm still in the market for one fully assembled miner from batch 1-4. I'd be willing to pay a premium of 1-2BTC, depending on batch, over Steamboat's price. If the miner is the only one in your order, we can just change the shipping address with Steamboat. If it's part of a multi-miner order, PM me and we can work something out -- maybe escrow the transaction or something. Send me a PM if you're interested, please!
TLDR; Batch3 have nothing to do with chips sales, so no worries.
Thx for clearing that up
Quick question are batches 1-5 considered Avalon Batch #3 i.e. the one everyone is getting all riled up about?
No... Avalon batch 3 is Bitsyncom's third batch of fully assembled miners which became pre-orderable on March 25th. People have their panties in a bunch because the pricing was based on a timeline with an expected ROI... basically 100BTC for an 85GH/s model and 75BTC for a 67GH/s model, with delivery on May 5th. At that time it was expected the ROI for breakeven would take 30 days. It is now close to 2 months after with still no delivery and folks are speculating that because of the initial high BTC price and the late delivery, these machines will never be able to recoup their cost. Also there was some drama that the batch 2 machines (an earlier miner pre-order batch) were being delivered with an eligius address matching a whale which was clocking in at 3.5TH and folks were speculating that Avalon was delaying shipment to farm on eligius with these machines. Chips are going to be start delivery early in July... before B3 is shipped/completed even though chip sales started after B3.
TLDR; Batch3 have nothing to do with chips sales, so no worries.
Thank You Steamboat Received e-mail on my order YEAH!
Received e-mail on my order YEAH!
Quick question are batches 1-5 considered Avalon Batch #3 i.e. the one everyone is getting all riled up about?
Overclocked or not, I just want to be hashing as soon as possible.
Depending on what ends up happening, I'd like to have overclock capabilities. If Rev2 doesn't come out in time (once the chips arrive) it'd be nice to have the option of only populating the board with 14 chips to accommodate some head room. steamboat; do you have plans for this contingency?
Steamboat posted his plan for overclocking in page 51 of this thread, post #1014. Not a lot of details yet, but certainly sounds like he'll be taking care of this.
I think this is based on BKKCoins changing his design. In the event he doesn't change designs for Rev1, the option for oc would be to under populate.
That was my understanding of the situation. BKK's latest comments are that to fully overclock requires: a) a new board revision (which has not been done or started) and b) some different components.
Did steamboat's post #1014 mean that the board he is building will be BKK's rev1 design but with a higher wattage regulator to enable overclocking, and if so will this be enough to match the full rev2 board or just a smallish bump.
Steamboat if you have time could you clarify what you're planning in post #1014 and what that most likely enables? I'm just trying to align this with the K16 thread.
Thanks!
I would love if steamboat takes BKK's advice and plans for the rev2 design as well, would love the extra hash rates
2 x Full Assembly w/ Testing ordered (#74).
In for 448 chips, tx id: fdfcf608aed55660d5966f9460cd82e62f2d8e77d68240d0814bfdddebd3713c
Thanks again!
Thanks again!
2x "full assembly + testing" purchased, order number 100000101. Site worked no prob
Depending on what ends up happening, I'd like to have overclock capabilities. If Rev2 doesn't come out in time (once the chips arrive) it'd be nice to have the option of only populating the board with 14 chips to accommodate some head room. steamboat; do you have plans for this contingency?
Steamboat posted his plan for overclocking in page 51 of this thread, post #1014. Not a lot of details yet, but certainly sounds like he'll be taking care of this.
I think this is based on BKKCoins changing his design. In the event he doesn't change designs for Rev1, the option for oc would be to under populate.
That was my understanding of the situation. BKK's latest comments are that to fully overclock requires: a) a new board revision (which has not been done or started) and b) some different components.
Did steamboat's post #1014 mean that the board he is building will be BKK's rev1 design but with a higher wattage regulator to enable overclocking, and if so will this be enough to match the full rev2 board or just a smallish bump.
Steamboat if you have time could you clarify what you're planning in post #1014 and what that most likely enables? I'm just trying to align this with the K16 thread.
Thanks!
edit: fixed.
50 chips purchased.
50 chips purchased.
Depending on what ends up happening, I'd like to have overclock capabilities. If Rev2 doesn't come out in time (once the chips arrive) it'd be nice to have the option of only populating the board with 14 chips to accommodate some head room. steamboat; do you have plans for this contingency?
Steamboat posted his plan for overclocking in page 51 of this thread, post #1014. Not a lot of details yet, but certainly sounds like he'll be taking care of this.
I think this is based on BKKCoins changing his design. In the event he doesn't change designs for Rev1, the option for oc would be to under populate.
Depending on what ends up happening, I'd like to have overclock capabilities. If Rev2 doesn't come out in time (once the chips arrive) it'd be nice to have the option of only populating the board with 14 chips to accommodate some head room. steamboat; do you have plans for this contingency?
Steamboat posted his plan for overclocking in page 51 of this thread, post #1014. Not a lot of details yet, but certainly sounds like he'll be taking care of this.
He said: " The Klondike is being verified for overclock ability, and several possible solutions have been suggested to increase it's potential. Each of the options does increase the cost of the board slightly, either from higher rated components or additional board size, or both. Some of them are minor, some are not. This additional cost will not be passed on to the end user. The base board design has been tested by several different sources and has passed, and the majority of the parts will stay the same. Lead time can be affected, and will increase the cost of PCB manufacture to ensure delivery before Batch 1. This cost will not be passed on to the end user.
The BOM has changed multiple times already. Sometimes due to scarcity, sometimes due to redesign. "
Depending on what ends up happening, I'd like to have overclock capabilities. If Rev2 doesn't come out in time (once the chips arrive) it'd be nice to have the option of only populating the board with 14 chips to accommodate some head room. steamboat; do you have plans for this contingency?
You have the burnin option for overclocking, board pics are up, its looking nice. https://bitcointalksearch.org/topic/m.2592961
Here is the latest from Bkk on the K16 overclocking issue
I am a bit stuck on what is best to do now. It seems 20-30% overclocking is quite reasonable for these chips. Even 20% is a significant bump that greatly increases the K16's ROI with 5.414 GH/s vs. 4.512GH/s.
So now I'm trying to figure out which option is best, any thoughts would be appreciated.
Option 1) Buy assembly as-is, receive 4.5GH/s boards and maybe tweak a bit if possible later
Option 2) Take chips only, find alternative assembly using Bkk's rev 2 board
Option 3) Have steamboat populate my K16's with only 13 or 14 chips per board to enable power overhead (not sure if this is even a possibility)
My current opinion / standing on the over-clocking power issues is that I'll get the current version working fully and then do a version 2 board that uses the IR3847 buck reg chip instead. The circuit is almost identical and just has some position/orientation changes. The sourcing may be more difficult but it's still the better choice for boosting the on-board power without too much redesign. Most of the parts are value changes to similar parts. I think the main issue will be the Cyntec 0.215 uH inductor (PCDC1008-R215EMO) and for those looking at sourcing and supply I'd start digging into how to get test samples and place larger orders of that part. It doesn't seem to be commonly available at Mouser/Digikey et al.
Just some forward looking comments at this point.
On the K1 it's possible to replace the 6502A with the 6503A and use a powered hub to get up to 3A of juice for the ASIC over-clocking. It's almost the same price anyway but would require a small bump in inductor choice.
Just some forward looking comments at this point.
On the K1 it's possible to replace the 6502A with the 6503A and use a powered hub to get up to 3A of juice for the ASIC over-clocking. It's almost the same price anyway but would require a small bump in inductor choice.
I am a bit stuck on what is best to do now. It seems 20-30% overclocking is quite reasonable for these chips. Even 20% is a significant bump that greatly increases the K16's ROI with 5.414 GH/s vs. 4.512GH/s.
So now I'm trying to figure out which option is best, any thoughts would be appreciated.
Option 1) Buy assembly as-is, receive 4.5GH/s boards and maybe tweak a bit if possible later
Option 2) Take chips only, find alternative assembly using Bkk's rev 2 board
Option 3) Have steamboat populate my K16's with only 13 or 14 chips per board to enable power overhead (not sure if this is even a possibility)
avalon chips are out of order...so does the order still apply?
They have always been "out of stock". The 10 week lead time means they are being manufactured before Avalon ships them out. The order still applies
True, they have always been "out of stock" since there IS a lead time. However, as far as I can recall, there used to be a "Buy" button on that page that allowed you to "pre-order". chips. That isn't there any longer.
Thanks for the clarification
Jump to: