|
|
|
Kto jest w sklepie?
Sklep przegląda 5987 gości |
|
Kategorie
|
|
Informacje
|
|
Polecamy
|
|
|
 |
|
|
Dla tego produktu nie napisano jeszcze recenzji!
 ;
jedyne do czego mogę mieć zastrzeżenie to jakość zdjęć zawartych w przesłanej instrukcji serwisowej ponieważ są fatalnej jakości, praktycznie nieczytelne. tak poza tym jestem zadowolony to jest to czego szukałem.
 ;
Wszystko w porządku.
Instrukcja czytelna i kompletna.
Dziękuję.
all right!
thank you.
;
Bardzo dobra instrukcja. Zawiera wszystko co potrzeba, polecam!
;
Instrukcja jest OK. Schematy czytelne, opisane niektóre procedury.
;
Instrukcja bardzo czytelna. zawiera co potrzeba. Polecam
When it is submerged, the white Water Exposure Seal turns to red. As the center part of the seal turns to pink, the color seen from the hole is pink. The 1mm hole diameter prevents the seal from getting affected by wet hands under normal conditions. It is not affected by the humidity of normal storage or operational conditions.
2.1.4.4
Normal condition
Main unit diagnosis An operation check with other MD Perform an operation check with CF and SD. Use SD with 40x high speed or more. or more. Use CF with theoretical value of 10MB/s For details, refer to 5. The Combinations of media and the main unit Troubles?
Water Exposure Seal display is appeared (changes from white to red)
Displays of Water Exposure Seal
NO
YES
6mm 1mm
1.5mm
2mm 4mm
1.5mm
Air is taken into inside the Microdrive from this hole through special filter for ventilation. DO NOT SEAL THIS HOLE is displayed.
An operation check with CF and SD
Main unit failure
Troubles in both SD and CF?
YES
Check bend or break in the socket pin(s).
NO
Troubles only in CF?
Location of a Water Exposure Seal (inside) Reverse side of the Microdrive
YES
Check the MD socket of the main unit.
Main unit operation failures caused by the main unit/ Microdrive failures. 2.1.4.2 There is a possibility of a Microdrive being damaged even though there is no notable failure in appearance. Main unit failures also result in abnormal operation in a Microdrive. Identifying the causes of the failures in the main unit is explained in this section. In the diagram, MD stands for a Microdrive, CG for a compact flash card, and SD for a SD card.
2.1.4.3
NO Main unit failure
Troubles?
NO Main unit failure
YES
The user MD/ FC may bend the main unit socket pin(s). Using defective MD/ FC results in repeated failures, as they bend the main unit connector every time they are used. User MD/ CF should be checked when abnormal main unit socket is found. Ask how many MDs/ CFs the user has, then check all user MDs/ CFs. Check the connector part of the main unit housing and user MD/ CF
Carry out the servic
End
2.1.4.3
MD Diagnosis Backup by connecting to the PC via USB or PCMCIA adapter Backup the record of the user MD
2.1.4.5 Disabled read/ write with other devices When read/ write cannot be done with the main unit, the main unit failure is considered in most cases. Recognition failure caused by the main unit writing bad data can be considered. The causes of read/ write failures are as listed below. (1) Damaged mechanism parts or electric parts inside the MD. (Hardware failure) (2) Damaged information in the MD. (Software failure) In the case (1), it seems very difficult to recover, but there is a possibility of recovery in the case (2) by using commercial software. The following procedure shows how to figure out whether the damage is in the hardware or in the software, and whether it is recoverable or not.
Can it be back upped?
NO
Read/ write by other devices is impossible
YES
Perform the DDD Full Check
Go to
2.1.4.5
Either the bad data file or the damaged MD causes the disabled read/ write is not yet determined at this point.
Troubles?
NO
Check the emergency record of the main unit
YES
Any record? Format the MD with the main unit
YES
2.1.4.5
Go to 2.1.4.4
Recoverability diagnosis An operation check with other MD Troubles? Perform the DDD Full Check A failure caused by the user handling is considered, and no more recovery is expected. Please explain the user that it is a MD failure.
NO
Format the MD with the main unit Although main unit failure is generally speculated, the cause of the failure is
Perform the DDD Clean Disk
Troubles?
NO
MD software failure
Perform the DDD Full Check
Perform the DDD Clean Disk
not determined whether the main unit/ MD at this point
YES
YES MD Hardware failure
The main unit operation failure may be caused by an unrecognizable MD after user's editing works such as formatting and adding/ deleting files or maintenance works such as defragmentation and check disk done with a device other than the main unit.
NO
Return the user backup data. Return the user backup data Perform an operation check on all items including MD and SD
Main unit failure
Troubles?
NO
Perform a detailed operation check by using the user MD The failure is resolved by performing the formatting and the Clean Disk.
YES
Troubles?
NO
YES MD failure Main unit failure End
2.1.4.4
Operation failures caused by main unit failures
2.1.4.3 Judging from the separation of the main unit and MD, the operation failure is more likely to be caused by the main unit failure. However, the main unit failure has not been determined yet, as there is a possibility of the user MD failure causing the main unit damage. The following procedure shows how to determine the main unit failure. 1-8 (No.YF058)
2.1.4.5.1 Microdrive hardware failure Although no failure was found in the MD appearance at the time of the separation of 2.1.4.1, actually there is considerable damage disabling the operation. In this case, "Shipping Damage" (damage caused by the transportation) is displayed as a result of DDD diagnosis. Surely, a possibility of the products damaged on route from the production plants to the shops and then to the consumers cannot be denied. However, MDs are stored in protection cases or in main units and the transportation shock that damages only the MDs is unrealistic. A failure cause by the user handling is more likely considered.
|
|
|
> |
|
