CRC-Tests on Kama Connect 2

[hiroshige]

Since some days I am running several experiments regarding CRC errors with IDE-drives connected to the Kama Connect 2. I was using a Hitachi Deskstar 7k160 (HDS72161PLAT80) with 160GB for the tests. The HDD was formatted completely after every run and checked using scandisk and HDTune.

I used a freshly installed Windows XP Professional for the tests, please make sure, that your Windows is not the issue for your CRC-problems!

I used several PCB-revisions, up to know I was testing 5 devices. Until now i can say, that I was not able to produce any CRC errors which means, the Kama Connect is reliable in general.





The pictures show one of the programs I used each taken in one of the evaluation-steps when checking the CRC of files in different sizes with a total amount of 20 GB. The whole process takes about 2 hours for every Kama Connect, you see it is quite a lot of work.

I will inform you about the latest results, until tomorrow evening I will be finished I think.

Comparing ...
Comparing done.
- Status Summary -
- Total Files - Source: 5 (40,00GB) - Target: 5 (40,00GB)
- Excluded Files - Source: 0 (0) - Target: 0 (0)
- Matched Files - Source: 5 (40,00GB) - Target: 5 (40,00GB)
- Single Files - Source: 0 (0) - Target: 0 (0)
- Newer Files - Source: 0 (0) - Target: 0 (0)
- Older Files - Source: 0 (0) - Target: 0 (0)
- Total Subfolders - Source: 0 - Target: 0
- Excluded Subfolders - Source: 0 - Target: 0
- Matched Subfolders - Source: 0 - Target: 0
- Single Subfolders - Source: 0 - Target: 0
Source and Target are identical.

Finished. I was not able to produce any CRC-errors.

Cheers,
Stefan

[rokas]

Hello.

Would be nice to know the exact method(s) you used for this test.

Was there only 1 IDE HDD connected to KC2 and the data was copied to an internal desktop HDD?

If yes, I think this test was not very useful (to me).

My problem occurs if there are 2 HDDs connected - both HDDs to KC2 and copying starts from IDE HDD to SATA HDD.

Also, it would be useful to know the production date of your KC2s and the type of your power adapters.

"Until now i can say, that I was not able to produce any CRC errors which means, the Kama Connect is reliable in general. "

Lucky one. My four KC2s were all fault. (production dates all 2007)

Thanx

[hiroshige]

Please have a look at the HowTo!
http://www.scythe-eu.com/forum/kama-...nnect-2-a.html

I will check how these test behave when copying data from USB to IDE both connected to KC2.

[npn]

Hello.
My CRC transfer problems occurs when I connect only ONE IDE 3.5 HDD (tested with 4 different IDE 3.5 HDDs) to KC2, and size of files was over 300 MB.
I use the same program (ViceVersa Pro) for synchronize my files with CRC verification option activated when I detected this problem.

I was able to "produce" this CRC problem with TWO different Kama Connect 2 devices. I used for testing 6 different IDE 3.5 HDDs, and 3 different PCs.

I have NO problem with power adapter and connection cables.

Both Kama Connect 2 devices (mine and my friend's one) was produced in 2007 (actually, both was bought in the same day)

My device has the following Serial Number:
SCUPS-2000
200708071326

Can you test a KC2 device that was produced in the same month and with same PCB-revision like my devices?

[hiroshige]

Hi npn,

I tested 4 different PCBs from 2007 and 4 from 2008 including 3 brand-new ones from Japan and I never (!) got any CRC-errors with small and large files. Additionally I used 5 different HDDs from 4 different manufacturers, which means: I had quite a lot of work.

It is impossible to test a device from the same month, I only tested one with the same PCB-version and there have been no CRC-errors.

I would suggest you to send your KC2 for RMA if you are not able to establish file-transfers without CRC-errors, but for me it is really strange after my bunch of experiments.

Cheers,
Stefan

@rokas: I just tested 2 PCB-versions using both IDE and SATA connected: no CRC-errors.

edit: I used a freshly installed Windows XP Professional for the tests, please make sure, that your Windows is not the issue for your CRC-problems!

[npn]

I wil contact the official Scythe distributor in Romania (IT Direct) for RMA.... From IT Direct I bought KC2 device last year.

I hope they will test and replace my fault KC2 device....And I will suggest them to send you this device for analysis.

Cheers,
npn

[hiroshige]

Allright, we will do it like this.

[gtissink]

I have now 2 "kama connect 2" devices and 1 of them is working great and the other is working troublesome (CRC-errors)

For testing I used the wires and adapter of the good one on the defective device and still CRC-errors..... replaced only the device and No Errors!!

The good one has a number 2007..... and the other one is 2008....

I will turn in the defective device at the retailer....

[Bantai]

Originally Posted by npn

My device has the following Serial Number:
SCUPS-2000
200708071326

This is mine:

SCUPS-2000
200708070346

Looks like the 20070807 revision is defective.

First thing I noticed after purchase was the power brick making a high pitched noise when KC2 was turned off. The retailer replaced the original power brick with one from another box. The new power brick looks different and is from another brand: Starmen.

I used KC2 with SATA mostly, which works great. However, IDE not so much.

- SATA + IDE DVD burner: burn fails at ~4% - immediate coasters
- IDE DVD burner only: damaged sectors with Nero DiscSpeed ScanDisc - indeed, there are glitches in movies; data may be corrupted
- IDE HDD: CRC errors with ViceVersa, a lot of folder and files are inaccessible or not even shown.

Perhaps if the retailer had replaced the complete package instead of only the power brick, I would have gotten a better working revision.

I will try to get it replaced now. Do I need an RMA?

[hiroshige]

Hello Bantai,

you can't say that the complete batch is defective, but good to know.

If you are from the EU, please send the item directly to us so that we can check and replace it if necessary. The shipment to Hamburg, Germany you have to pay by yourself, we will pay the shipment back to you.

Cheers,
Stefan