Discontinued: Lancelot (Heavy Duty 400 Mega hashes, 2 x FPGA Mining Board)

[blackarrow]

Thanks for the update, blackarrow.  But the fact that your product page still says "In Stock" is blatantly deceptive.

If we put the product out of stock, our website will not take any orders. We've added a note to the product to explain the situation.

Three days ago, I placed an order for an "In Stock" product and was immediately told the item was backordered and I would receive a notification in the next 4-7 days for payment.  I now learn through your post that my order will most likely not be available for an additional 4 weeks.

I understand the manufacturing and supply chain process can be very challenging, but placing an overseas order like this requires a great deal of trust from the customer and when a customer's expectations are manipulated and/or misinformed by the seller - that trust erodes quickly.

Of course, I have not yet made any actual payment, so there is no measurable loss of funds here, but you should know - this sort of practice is disruptive & irritating and furthermore seems unsuitable to the communicative & helpful person that you seem to be.

We've been more than open with everybody here about how the production is going.

We've asked everybody not to pay for the products that are not in stock but we still see unhappy customers like you. I guess you cannot make everybody happy whatever you do.

I'm amazed how some people are so sensitive about such a minor detail but they are pouring money in some companies that have not shipped anything for 1 year (Butterfly Labs).

[1714942185]

1714942185

[1714942185]

1714942185

[1714942185]

1714942185

[blackarrow]

So something like:
--icarus-timing 2.5=100
It will show the MH/s incorrectly, but it will still hash at the highest rate it can.

The random unknown MHz is actually problematic

It looks that v42 firmware is actually faster than 200Mhz firmware, even with the hardware errors that is yielding. The number of packets accepted is higher than a device running at 200Mhz.

I've also looked at ztex and it is producing the same amount of errors so it should be fine.

I think that with v42 firmware Lancelot reaches 500Mega hases. I haven't looked at your code but I think that based on the proof of work you should be able to accurately calculate the speed. You should not rely on how fast the device returns data but on what date it is actually returning.

Regards!

[phm]

On my unit a red HOT LED is on all the time when it's running. Heat sink is cool (not even lukewarm), so I wonder what exactly it means. Does anyone know?

[CrownCloud]

On my unit a red HOT LED is on all the time when it's running. Heat sink is cool (not even lukewarm), so I wonder what exactly it means. Does anyone know?

Check the heat on the underside of the board ? As the heatsink is pretty cool most of the times, its the underside of the board, especially towards the middle of the board (between the 2 Spartan 6 FPGA Chips) which gets pretty warm for me

[FlappySocks]

I think that with v42 firmware Lancelot reaches 500Mega hases.

Should we update the firmware?  Does that require a JTag cable?

[phm]

On my unit a red HOT LED is on all the time when it's running. Heat sink is cool (not even lukewarm), so I wonder what exactly it means. Does anyone know?

Check the heat on the underside of the board ? As the heatsink is pretty cool most of the times, its the underside of the board, especially towards the middle of the board (between the 2 Spartan 6 FPGA Chips) which gets pretty warm for me

Right, it's quite warm, but not burning hot. Do you know what is the temperature value that triggers HOT LED? Shall I worry about my FPGAs dying prematurely?

[kano]

So something like:
--icarus-timing 2.5=100
It will show the MH/s incorrectly, but it will still hash at the highest rate it can.

The random unknown MHz is actually problematic

It looks that v42 firmware is actually faster than 200Mhz firmware, even with the hardware errors that is yielding. The number of packets accepted is higher than a device running at 200Mhz.

I've also looked at ztex and it is producing the same amount of errors so it should be fine.

I think that with v42 firmware Lancelot reaches 500Mega hases. I haven't looked at your code but I think that based on the proof of work you should be able to accurately calculate the speed. You should not rely on how fast the device returns data but on what date it is actually returning.

Regards!

If it's hashing at 500MH/s then use --icarus-timing 2.0=80

The =80 is actually the important number.
(=100 will be OK only up to about 428MH/s)
The Hs nanoseconds number is just used to try to get the display right if you also specify a value with the =

We've done the Blackarrow Lancelot (BLT) code and it works fine.
Also working with AMU (asicminer USB) and of course should work with a normal Lancelot (LLT)
Just need to do the Icarus (ICA) and Cairnsmore1 (CMR) and then it will be done.
They are all in the one driver, so all need to be working before we'll put it in a release
(though you can get it from git as it is now - but you need to know which commits)

e.g. almost 5hour runtime:

Code:

 cgminer version 3.1.1k - Started: [2013-05-20 03:21:21]
--------------------------------------------------------------------------------
 (5s):968.0M (avg):734.7Mh/s | A:2927  R:4  HW:9  U:10.2/m  WU:10.3/m
 ST: 2  SS: 0  NB: 37  LW: 5611  GF: 0  RF: 0
 Connected to au.ozco.in diff 1 with stratum as user
 Block: 011b55e1d73ee2d4...  Diff:11.2M  Started: [08:05:05]  Best share: 25.9K
--------------------------------------------------------------------------------
 [P]ool management [S]ettings [D]isplay options [Q]uit
 BLT 0:                | 398.2M/399.3Mh/s | A:1584 R:0 HW:1 U: 5.54/m
 AMU 0:                | 335.1M/335.5Mh/s | A:1344 R:3 HW:8 U: 4.70/m
--------------------------------------------------------------------------------

[Tranz]

I'm a bit disappointed!  

Thread says "Now Available", Shows in stock on website.  Placed order. Now I get this email...

Dear Customer,

Unfortunately we have sold our current batch of Lancelot boards. As you have placed your order on our website you are on our emailing list. You will receive a reminder for payment when we restock. Our next dispatch date is 10th of June. At the moment we schedule our deliveries for 27th of May and we will let you know if we have enough stock to fit your order into this batch.

Regards,
CardReaderFactory

Edit: I see I am not the only one. Glad it was a weekend and I couldn't pay or I'd be kinda upset and nervous for sending such money to China.

Guess more waiting.....................

[LaserHorse]

I'm amazed how some people are so sensitive about such a minor detail but they are pouring money in some companies that have not shipped anything for 1 year (Butterfly Labs).

Aw c'mon - implying I am one of those people is kind of shitty, no?

I just object to the tactic of luring in customers based on false pretense - I'm not freaking out, and I was trying to respectfully tell you and others that I thought you were better than that.

I suppose it's a seller's market.  Back to the tech …

EDIT: blackarrow explains this is a limitation of their webstore - https://bitcointalk.org/index.php?topic=187549.msg2205714#msg2205714

[FlappySocks]

Aw c'mon - implying I am one of those people is kind of shitty, no?

You dont think your being sensertive?  Read the whole thread.  blackarrow has done a pretty good job considering all the hurdles, and had expressly said dont pay for anything until you get a payment reminder (i.e when a shipping date is known).

[LaserHorse]

You dont think your being sensertive?  Read the whole thread.  blackarrow has done a pretty good job considering all the hurdles, and had expressly said dont pay for anything until you get a payment reminder (i.e when a shipping date is known).

You mean 'too sensitive'?  Well, no.  He stated that they wouldn't get any orders if the actual stock status was clearly represented.  I just disagree with that approach.  My intention was to clarify an inaccuracy and avoid any further unnecessary aggravation.  done.

Lancelot seems like a great product - back to the hashing!

EDIT: blackarrow explains this is a limitation of their webstore below

[blackarrow]

I just object to the tactic of luring in customers based on false pretense - I'm not freaking out, and I was trying to respectfully tell you and others that I thought you were better than that.

We're actually trying to keep everybody informed, and not lure anybody into anything.

"On Stock" on the website is a limitation of the software that we're using for shopping card.
If we put "out of stock" customers cannot place orders and we would have no queue and wouldn't know what parts we need to order in order to clear our queue.

We cannot just buy random quantities of Spartan 6. They are very expensive and having them in stock without being able to sell them would get us bankrupt.

[bitpop]

Black arrow has been very honest and DELIVERED.

[LaserHorse]

I just object to the tactic of luring in customers based on false pretense - I'm not freaking out, and I was trying to respectfully tell you and others that I thought you were better than that.

We're actually trying to keep everybody informed, and not lure anybody into anything.

"On Stock" on the website is a limitation of the software that we're using for shopping card.
If we put "out of stock" customers cannot place orders and we would have no queue and wouldn't know what parts we need to order in order to clear our queue.

We cannot just buy random quantities of Spartan 6. They are very expensive and having them in stock without being able to sell them would get us bankrupt.

Thanks for clarifying - that makes much more sense.  I'll update my previous posts to point to your explanation.

[HTML5 Gordon]

I'm a bit disappointed!  

Thread says "Now Available", Shows in stock on website.  Placed order. Now I get this email...

Dear Customer,

Unfortunately we have sold our current batch of Lancelot boards. As you have placed your order on our website you are on our emailing list. You will receive a reminder for payment when we restock. Our next dispatch date is 10th of June. At the moment we schedule our deliveries for 27th of May and we will let you know if we have enough stock to fit your order into this batch.

Regards,
CardReaderFactory

Edit: I see I am not the only one. Glad it was a weekend and I couldn't pay or I'd be kinda upset and nervous for sending such money to China.

Guess more waiting.....................

blackarrow, I notice in the email above that it gives a dispatch date of June 10th.  Is this correct?  I was under the impression that even purchases that are not bought on the Group Manufacturing deal would not ship until July.  If I placed an additional non-group purchase now, would that one ship in June?

Thanks!

[yantis]

I gave these guys a call and they were very helpful and I would have to say Legit. Enough that I bought 100 units from them.

[tidus_13]

I gave these guys a call and they were very helpful and I would have to say Legit. Enough that I bought 100 units from them.

Wow 100 lancelots , 80 ASICMINER Block Erupter USB.
Any other big ASIC hash power?

[elchorizo]

On my unit a red HOT LED is on all the time when it's running. Heat sink is cool (not even lukewarm), so I wonder what exactly it means. Does anyone know?

2 out of my 10 units do this. It goes on as soon as the unit is powered on and never goes off. The other units (in the same stack, with the same cooling, etc) -- it never goes on. I just ignore it, they haven't had any issues.

[blackarrow]

Do you mean that you will stop taking group orders for the current group on Wednesday? Or that you will stop taking group orders?

The demand for group manufacturing is not big enough to make Xilinx happy to manufacture new batches every week. We will need to make group manufacturing batches slower so we can gather more orders.

[blackarrow]

Should we update the firmware?  Does that require a JTag cable?

You should try it, see if you're happy with the performance. Yes, it requires a Jtag cable. Shall we start selling these too?