JVC GZMC500US - Everio Camcorder - 1.33 MP, Service Manual, Page: 12 / 44

1-12 (No.YF100)
2.4.5.4 Operation failures caused by main unit failures
2.4.5.3 Judging from the separation of the main unit and MD, the
operation failure is more likely to be caused by the main unit fail-
ure. 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.
2.4.5.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.
2.4.5.5.1 Microdrive hardware failure
Although no failure was found in the MD appearance at the time
of the separation of 2.4.5.1, actually there is considerable dam-
age disabling the operation. In this case, "Shipping Damage"
(damage caused by the transportation) is displayed as a result of
HiTest 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 unrealis-
tic. A failure cause by the user handling is more likely considered.
Recovery method
Asking a data recovery company (a data salvage company)
seems the only way.
Even if the MD is not recognized a drive, a transmission may be
possible with the MD (light hardware failure). In this case, system
recovery software such as Norton Utilities in Norton System-
Works 2005 (NOTE1 ) may help drive recognition.
Once the drive recognition is recovered, the record may be re-
covered by the method mentioned in 2.4.5.5.2 Microdrive soft-
ware failure. However, if it is a hardware failure, banning the use
of the MD is strongly recommended.
2.4.5.5.2 Microdrive software failure
Most of the software failures are caused by the unrecognizable
MD after user's editing works such as formatting and adding/ de-
leting files or maintenance works such as defragmentation and
check disk done with a device other than the main unit.
Basically, do not recover user data. If recovery is needed in
certain cases, recovery can be done by using recovery software,
which can recover MPEG2 data, such as Final Data 3.0
Premium. It enables the drive recognition and the data reading.
Once the data is recovered, follow the below procedure.
Go to
2.4.5.5
Go to
2.4.5.4
2.4.5.3
Check the emergency
record of the main unit
Troubles?
YES
Any record?
MD Diagnosis
Perform the HitTEST
Perform the HitTEST again
Can the recorde
data be recognized with
other devices?
NO
Perform the DDD Clean Disk Format the MD with the main unit
Perform the DDD Clean Disk
Format the MD with the main unit
YES
Troubles?
YES
MD failure
NO
NO
Perform a detailed operation
check by using the user MD
Troubles?
NO
YES
NO
End
Main unit failure
Check the files recorded with the PC by connecting the MD to the USB adaptor.
YES
Perform an operation check on
all items including MD and SD
Either the bad data file or the
damaged MD causes the disabled
read/ write is not yet determined
at this point.
The failure is resolved by
performing the formatting
and the Clean Disk.
Although main unit failure is generally
speculated, the cause of the failure is
not determined whether the main unit/
MD at this point
2.4.5.4
Check the MD socket
of the main unit.
Troubles in both
SD and CF?
NO
YES
Troubles?
Main unit
diagnosis
An operation check
with other MD
NO
Troubles
only in CF?
NO
Troubles?
YES
End
Main unit failure
Perform an operation check with CF and SD.
Use SD with theoretical value of 10MB/s or more.
Use CF with 40x high speed or more.
For details, refer to 5.
The Combinations of media and the main unit
Carry out the servic
YES
An operation check
with CF and SD
YES
Main unit failure
NO
Main unit failure
Check bend or break
in the socket pin(s).
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
2.4.5.5
Troubles?
NO
Recoverability
diagnosis
An operation check
with other MD
Main unit failure
Perform
the HitTEST
Troubles?
YES
MD Hardware failure
NO
YES
MD software failure
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.
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.