Topic: Liquid Synergy Designs Inc. -ASIC mining hardware - page 38. (Read 423279 times)
No one is getting a refund denominated in BTC. This was clear since your order was purchased in USD.
With the power connector on the bottom of the K16 I have to lay the miners I have running on their side. I'm thinking about building a custom shelf for them so I can route power out the bottom. How is everyone else setting up their miners? How are the hosted miners physically configured? And is anyone successfully stacking their miners? Any pictures?
Thanks,
-Jay
Thanks,
-Jay
The boards appear to have mounting holes to accept a right-angle 6-pin PCIe power connector, but my boards at least came with regular connectors.
For mine, I just used extra standoffs to mount the boards far enough apart to stack them and still have room for the power cables to attach. It does make for a tall stack.
I may try to replace the connectors someday.
The "value" of your refund isn't changing, it's the same amount of US Dollars that it always has been.
If that is addressed to me; I meant to say if we were refunded 25% refund of usd value but refunded in bitcoin months ago and kept it, we will had now more in $ value because btc rise.
So waiting for refunds while $ value is rising sucks!
The "value" of your refund isn't changing, it's the same amount of US Dollars that it always has been.
We paid in BTC, not dollars. So we should actually get more back than we paid, in theory.
I would have to agree. In my opinion, because bitcoin in itself has interest, as it constantly rises, our assembly refunds rightfully must be returned to us in the form of which we payed, in bitcoins (in denomination of cost based on the time history for which we payed for them when they were worth $80-$120 ea. per BTC).
Because for a ridiculous example, I payed $560 for Assembly in bitcoins, of which at the time they were worth ~$112 ea., be it that I sent ~5BTC for assembly, if by happenstance in the future a bitcoin increased to an extreme value (which it possibly may) such as $5,000+, that is $25,000 that I could have simply sat on--significantly more than being returned $560 assembly refund based on USD such as, I would get only .112BTC back in this extreme example, when initially it was 5 BTC i sent over (44 times that!)
Prices were quoted in usd. If btc had gone down in value you would be complaining and wanting your refunds in usd. The constructive, useful, interesting posts in this thread and only just enough to keep people here. I'm desperate for the refunds to be paid out so the whining will stop.
This is bullshit!
I demanded my full refunds months ago, when the price of Bitcoin was nearly a third of what is it today.
So either pay up in BTC or using those rates.
Look, it's not bullshit. Steamboat said that Assembly prices were $USD, payable in bitcoin. You paid a USD amount in bitcoin and asking for an equal number of bitcoin (much greater $USD value, which SB paid for components/assembly/shipping costs-these are all paid in USD) is unfair to Steamboat. You knew the risks; Steamboat is human, just like all of us, and doing his best. Patience is a virtue (I'm looking at you cardcomm) and this will be sorted out eventually. I'm not pleased with how things turned out either, but it's an unfortunate reality and we were all informed and took the risks involved.
That two separate issues and company need to operate within the US laws. He need to refund us now, we are lossing in the price value while we waiting for money paid months ago!!!
We paid in BTC, not dollars. So we should actually get more back than we paid, in theory.
I would have to agree. In my opinion, because bitcoin in itself has interest, as it constantly rises, our assembly refunds rightfully must be returned to us in the form of which we payed, in bitcoins (in denomination of cost based on the time history for which we payed for them when they were worth $80-$120 ea. per BTC).
Because for a ridiculous example, I payed $560 for Assembly in bitcoins, of which at the time they were worth ~$112 ea., be it that I sent ~5BTC for assembly, if by happenstance in the future a bitcoin increased to an extreme value (which it possibly may) such as $5,000+, that is $25,000 that I could have simply sat on--significantly more than being returned $560 assembly refund based on USD such as, I would get only .112BTC back in this extreme example, when initially it was 5 BTC i sent over (44 times that!)
Prices were quoted in usd. If btc had gone down in value you would be complaining and wanting your refunds in usd. The constructive, useful, interesting posts in this thread and only just enough to keep people here. I'm desperate for the refunds to be paid out so the whining will stop.
This is bullshit!
I demanded my full refunds months ago, when the price of Bitcoin was nearly a third of what is it today.
So either pay up in BTC or using those rates.
Look, it's not bullshit. Steamboat said that Assembly prices were $USD, payable in bitcoin. You paid a USD amount in bitcoin and asking for an equal number of bitcoin (much greater $USD value, which SB paid for components/assembly/shipping costs-these are all paid in USD) is unfair to Steamboat. You knew the risks; Steamboat is human, just like all of us, and doing his best. Patience is a virtue (I'm looking at you cardcomm) and this will be sorted out eventually. I'm not pleased with how things turned out either, but it's an unfortunate reality and we were all informed and took the risks involved.
We paid in BTC, not dollars. So we should actually get more back than we paid, in theory.
I would have to agree. In my opinion, because bitcoin in itself has interest, as it constantly rises, our assembly refunds rightfully must be returned to us in the form of which we payed, in bitcoins (in denomination of cost based on the time history for which we payed for them when they were worth $80-$120 ea. per BTC).
Because for a ridiculous example, I payed $560 for Assembly in bitcoins, of which at the time they were worth ~$112 ea., be it that I sent ~5BTC for assembly, if by happenstance in the future a bitcoin increased to an extreme value (which it possibly may) such as $5,000+, that is $25,000 that I could have simply sat on--significantly more than being returned $560 assembly refund based on USD such as, I would get only .112BTC back in this extreme example, when initially it was 5 BTC i sent over (44 times that!)
Prices were quoted in usd. If btc had gone down in value you would be complaining and wanting your refunds in usd. The constructive, useful, interesting posts in this thread and only just enough to keep people here. I'm desperate for the refunds to be paid out so the whining will stop.
This is bullshit!
I demanded my full refunds months ago, when the price of Bitcoin was nearly a third of what is it today.
So either pay up in BTC or using those rates.
With the power connector on the bottom of the K16 I have to lay the miners I have running on their side. I'm thinking about building a custom shelf for them so I can route power out the bottom. How is everyone else setting up their miners? How are the hosted miners physically configured? And is anyone successfully stacking their miners? Any pictures?
Thanks,
-Jay
Thanks,
-Jay
We paid in BTC, not dollars. So we should actually get more back than we paid, in theory.
I would have to agree. In my opinion, because bitcoin in itself has interest, as it constantly rises, our assembly refunds rightfully must be returned to us in the form of which we payed, in bitcoins (in denomination of cost based on the time history for which we payed for them when they were worth $80-$120 ea. per BTC).
Because for a ridiculous example, I payed $560 for Assembly in bitcoins, of which at the time they were worth ~$112 ea., be it that I sent ~5BTC for assembly, if by happenstance in the future a bitcoin increased to an extreme value (which it possibly may) such as $5,000+, that is $25,000 that I could have simply sat on--significantly more than being returned $560 assembly refund based on USD such as, I would get only .112BTC back in this extreme example, when initially it was 5 BTC i sent over (44 times that!)
Prices were quoted in usd. If btc had gone down in value you would be complaining and wanting your refunds in usd. The constructive, useful, interesting posts in this thread and only just enough to keep people here. I'm desperate for the refunds to be paid out so the whining will stop.
Like you would get even a CENT back anyway? Yifu should be behind bars, he scammed the whole DIY community.
Yes morris14ccm, Plug it in to the PSU and USB to Computer. Download CGMiner 3.7.0 and run it.
running 360MHz stable
running 360MHz stable
Adding slub to the end of cmdline.txt has my pi back up and running like it's old self again. It's been hashing away without any problems for the last hour or so. I started playing around with the clock settings and 360mhz was the highest value that my K16's would actually hash at. What is weird is that at 360mhz they only hash at about half speed. I get around 2.5 to 2.8 gigahashes at 360mhz. The highest I can go on mine and still have full speed is 352mhz. If I change it to 353mhz the hash rate drops dramatically.
Chad
Since the board uses two groups of 8 chips, and each group has it's own regulator, it is possible that regulator on one side (for one group) cant keep up with the other one - so one side is without power when clocked that high and another one is hashing. That would explain why you get half of the hashrate at higher clocks.
Possible to latch the output of the two regulators together in this case as a work around?
For those who have hot air gun and a fat wire to do it with :-P
I would definitely not advise this, since both regulators can have a slightly different output voltages. And if one is dropping off, the other one would be near its limit too, because they are identical. Anyways, you probably wouldn't get past 375, which is a 400MH/s gain per board. I think that tinkering with it for this low speed gain and with current difficulty is not worth it, especially if it is working stable and without any major problems now.
Good point. How about adding an external 12Amp 1.2v 600Khz switching DC-DC regulator? I see them available on the net for around 8 bucks a pop.
We paid in BTC, not dollars. So we should actually get more back than we paid, in theory.
I would have to agree. In my opinion, because bitcoin in itself has interest, as it constantly rises, our assembly refunds rightfully must be returned to us in the form of which we payed, in bitcoins (in denomination of cost based on the time history for which we payed for them when they were worth $80-$120 ea. per BTC).
Because for a ridiculous example, I payed $560 for Assembly in bitcoins, of which at the time they were worth ~$112 ea., be it that I sent ~5BTC for assembly, if by happenstance in the future a bitcoin increased to an extreme value (which it possibly may) such as $5,000+, that is $25,000 that I could have simply sat on--significantly more than being returned $560 assembly refund based on USD such as, I would get only .112BTC back in this extreme example, when initially it was 5 BTC i sent over (44 times that!)
Prices were quoted in usd. If btc had gone down in value you would be complaining and wanting your refunds in usd. The constructive, useful, interesting posts in this thread and only just enough to keep people here. I'm desperate for the refunds to be paid out so the whining will stop.
So now that the issue is the project development itself, aren't we eligible for a refund?
We bought these miners on the basis that building the miner was an easy step which will be done the next day after delivery.. Well, this is not the case and I do demand a refund, this is the BIGGEST BS in history having to wait for something that's depreciating in value by the minute for that long because the provider isn't capable of building it.
I've had enough of all the "news" which bring no news to me, I don't get how a HW engineer can't pull this shit together, I wonder what he's getting paid for?
We bought these miners on the basis that building the miner was an easy step which will be done the next day after delivery.. Well, this is not the case and I do demand a refund, this is the BIGGEST BS in history having to wait for something that's depreciating in value by the minute for that long because the provider isn't capable of building it.
I've had enough of all the "news" which bring no news to me, I don't get how a HW engineer can't pull this shit together, I wonder what he's getting paid for?
Is anyone sinking the chips or regulators on the back of the board with useful results?
Yes morris14ccm, Plug it in to the PSU and USB to Computer. Download CGMiner 3.7.0 and run it.
running 360MHz stable
running 360MHz stable
Adding slub to the end of cmdline.txt has my pi back up and running like it's old self again. It's been hashing away without any problems for the last hour or so. I started playing around with the clock settings and 360mhz was the highest value that my K16's would actually hash at. What is weird is that at 360mhz they only hash at about half speed. I get around 2.5 to 2.8 gigahashes at 360mhz. The highest I can go on mine and still have full speed is 352mhz. If I change it to 353mhz the hash rate drops dramatically.
Chad
Since the board uses two groups of 8 chips, and each group has it's own regulator, it is possible that regulator on one side (for one group) cant keep up with the other one - so one side is without power when clocked that high and another one is hashing. That would explain why you get half of the hashrate at higher clocks.
Possible to latch the output of the two regulators together in this case as a work around?
For those who have hot air gun and a fat wire to do it with :-P
I would definitely not advise this, since both regulators can have a slightly different output voltages. And if one is dropping off, the other one would be near its limit too, because they are identical. Anyways, you probably wouldn't get past 375, which is a 400MH/s gain per board. I think that tinkering with it for this low speed gain and with current difficulty is not worth it, especially if it is working stable and without any major problems now.
Possible to latch the output of the two regulators together in this case as a work around?
For those who have hot air gun and a fat wire to do it with :-P
For those who have hot air gun and a fat wire to do it with :-P
I wouldn't recommend this. Bridging power supplies like this is a science. In the end this board was a compromise, I think I suggested wire bridges to segment the power supply and headers for off board supplies but this was seen as too esoteric. If anyone does a rev 2 design it would be smart to allow for up to 4 core power supplies.
I just hope to god SB tax declared it as valueless, or very low value, similar to the refund value or something... (ie paperweight of educational value only) or I have to pay another 200 bucks in VAT on import... that's gonna suck balls... I may consider just refusing to collect the shipment and let it return to Steamboat if that is the case...
It arrives tomorrow, so we'll see...
It arrives tomorrow, so we'll see...
Yep, I got fucked. 245 USD in value added tax. I'm not going to collect, so SB probably have to fork out return postage when the miners arrive back in Miami.
Sweet... I paid close to 1500 USD and got nothing to show for.
Steamboat, your goods deprecated close to 90% in value between payment and shipping the miners, why didn't the tax/export form reflect this... I can't take delivery of the miners now. Sorry.
Too bad communication with SB seems impossible. I'm sure this could have been avoided on his end had he shown the current actual value.
Yes morris14ccm, Plug it in to the PSU and USB to Computer. Download CGMiner 3.7.0 and run it.
running 360MHz stable
running 360MHz stable
Adding slub to the end of cmdline.txt has my pi back up and running like it's old self again. It's been hashing away without any problems for the last hour or so. I started playing around with the clock settings and 360mhz was the highest value that my K16's would actually hash at. What is weird is that at 360mhz they only hash at about half speed. I get around 2.5 to 2.8 gigahashes at 360mhz. The highest I can go on mine and still have full speed is 352mhz. If I change it to 353mhz the hash rate drops dramatically.
Chad
Since the board uses two groups of 8 chips, and each group has it's own regulator, it is possible that regulator on one side (for one group) cant keep up with the other one - so one side is without power when clocked that high and another one is hashing. That would explain why you get half of the hashrate at higher clocks.
Possible to latch the output of the two regulators together in this case as a work around?
For those who have hot air gun and a fat wire to do it with :-P
Yes morris14ccm, Plug it in to the PSU and USB to Computer. Download CGMiner 3.7.0 and run it.
running 360MHz stable
running 360MHz stable
Adding slub to the end of cmdline.txt has my pi back up and running like it's old self again. It's been hashing away without any problems for the last hour or so. I started playing around with the clock settings and 360mhz was the highest value that my K16's would actually hash at. What is weird is that at 360mhz they only hash at about half speed. I get around 2.5 to 2.8 gigahashes at 360mhz. The highest I can go on mine and still have full speed is 352mhz. If I change it to 353mhz the hash rate drops dramatically.
Chad
Since the board uses two groups of 8 chips, and each group has it's own regulator, it is possible that regulator on one side (for one group) cant keep up with the other one - so one side is without power when clocked that high and another one is hashing. That would explain why you get half of the hashrate at higher clocks.
Yes morris14ccm, Plug it in to the PSU and USB to Computer. Download CGMiner 3.7.0 and run it.
running 360MHz stable
running 360MHz stable
Adding slub to the end of cmdline.txt has my pi back up and running like it's old self again. It's been hashing away without any problems for the last hour or so. I started playing around with the clock settings and 360mhz was the highest value that my K16's would actually hash at. What is weird is that at 360mhz they only hash at about half speed. I get around 2.5 to 2.8 gigahashes at 360mhz. The highest I can go on mine and still have full speed is 352mhz. If I change it to 353mhz the hash rate drops dramatically.
Chad
Every time you change the value of the clock speed you must reboot the K16's. I'm sure new firmware will fix this minor problem in the near future. jesse11
Yes morris14ccm, Plug it in to the PSU and USB to Computer. Download CGMiner 3.7.0 and run it.
running 360MHz stable
running 360MHz stable
Adding slub to the end of cmdline.txt has my pi back up and running like it's old self again. It's been hashing away without any problems for the last hour or so. I started playing around with the clock settings and 360mhz was the highest value that my K16's would actually hash at. What is weird is that at 360mhz they only hash at about half speed. I get around 2.5 to 2.8 gigahashes at 360mhz. The highest I can go on mine and still have full speed is 352mhz. If I change it to 353mhz the hash rate drops dramatically.
Chad
Jump to: