I'm a Batch 3 Sierra customer and the email I received only said "we anticipate shipping by March 31st."  I talked to Chris on the phone and he suggested (no confirmation, he doesn't know for sure) that Ciarra might be producing in batches, and then re-tooling for other customers and then back to HashFast orders.  That would explain the erratic deliveries.

On the IceDrill thread it seems they've received 169THs(?) out of 253TH/s...their order was smaller than originally desired because they didn't raise enough BTC for the full 500TH/s... check the thread to be sure.

I'm still looking for where they said everything through Batch 4 will be shipped by March 31st... maybe Facebook

Can someone treat me like an idiot and tell me exactly where I enter --hfa-hash-clock 600?

Im using CGminer 4.1

I've managed to get 4 Sierra's hashing from one PC, adding more Sierra's just causes it to crash. Is this normal?

Hi JD, thanks for the reply.

I downloaded CGminer 4.1 to windows 7 - inside the zip is CGminer.exe which I run from a batch file along the lines of

@echo on
cgminer.exe -o pooldetails:3333 -u myusername -p mypassword

I've tried adding in the '--hfa-hash-clock 600' on the above string and it causes CGminer to load and immediately quit.

Obviously I'm a moron for not knowing this stuff so really do appreciate the help.

Thanks, just crashes CGminer when I do that.

So after a little over 24hrs I've learned a little and been angry a lot.

Of the 9 Sierra's 2 are useless. 1 fails to power up although did power for a short time today, on connecting it to CGminer it immediately gave an error along the lines of 'Main Board 12V error' and crashed CGminer.

The other problem Sierra was running fine but now does nothing but crash CGminer with Libusb errors.

I've had a few hours of easy running with the other 7 machines but now im having to restart every 20 mins or so.

Whilst the .4 firmware may solve some of this, there appears to be no support for windows users with the instructions only talking about Unix or babyjet users flashing their cards.

Losing the will to live here. Having gone through the ballache of installing Ubuntu in order to update the firmware, in trying to update all I get back is this

('confirm is ', False)
('FIRMWARE_DIR is ', '.')
UC_HFU_FILE at './uc3.cropped.hfu'.
READSERIAL found at 'x86_64/readserial'.
HFUPDATE found at 'x86_64/hfupdate'.
ENTERLOADER found at 'x86_64/enterloader'.

HashFast Firmware Updater

Reading serial number from module.
x86_64/readserial: symbol lookup error: x86_64/readserial: undefined symbol: libusb_strerror
Entering Boot Loader...
x86_64/enterloader: symbol lookup error: x86_64/enterloader: undefined symbol: libusb_strerror
Traceback (most recent call last):
  File "./field_firmware_update.py", line 184, in <module>
    firmware_updater()
  File "./field_firmware_update.py", line 143, in firmware_updater
    enterloader()
  File "./field_firmware_update.py", line 62, in enterloader
    subprocess.check_call([ENTERLOADER])
  File "/usr/lib/python2.7/subprocess.py", line 511, in check_call
    raise CalledProcessError(retcode, cmd)
CalledProcessError: Command '['x86_64/enterloader']' returned non-zero exit status 127
Command '['x86_64/enterloader']' returned non-zero exit status 127
Firmware Update had an error.  Please retry or report to HashFast Support.

Same response for a machine that works and the machine that has the LIBUSB error.

So now what?

Hey Thanks CK... I'll see about updating my Ubuntu tomorrow and see if I have any joy there.

Do you think the firmware will resolve the machine with the LIBSUB error?

shouldn't hf test the devices before shipping? the fault rate seems so high! and I wonder how long the RMA takes?

Well so far 6 emails across 48 hrs to HF and not one reply so RMA is looking like taking a while.

Phoning tech support just gets a 'We're not able to take your call right now'