November 28, 2012 | Cisco Systems | PrecisionHD 4X Camera Connectivity Problems
2
1. Failed Camera Boot Failed Initialization
Customers are reporting the following symptoms on new installs (new out of box), new replacements
out of box), or after rebooting their codec on a previously working installation for certain Precision HD 4X cameras:
1.
Orange LED present on camera at all times.
2.
Green LED present on base of camera.
3.
No PTZ control from any input device (e.g. touchpanel, remote, etc.)
4.
No video on self-view from camera.
5.
The admin CLI command "xstatus camera 1" shows "Connected: False" and no other camera information
is displayed.
xstatus camera 1
*s Camera 1 Connected: False
*s Camera 1 HardwareID: ""
*s Camera 1 Manufacturer: ""
*s Camera 1 Model: ""
*s Camera 1 SoftwareID: ""
*s Camera 1 SerialNumber: ""
*s Camera 1 IpAddress: ""
*s Camera 1 MacAddress: ""
*s Camera 1 Position Pan: 0
*s Camera 1 Position Tilt: 0
*s Camera 1 Position Zoom: 16
*s Camera 1 Position Focus: 4000
*s Camera 1 Capabilities Options: ""
*s Camera 1 Flip: "Off"
** end
OK
6.
Power cycling the camera or codec does not allow codec control of the camera.
Details regarding the above problem are documented in the following bug:
CSCua44699
Camera fails to boot due to checksum validation failure
As a result of the above, the camera cannot be controlled by the codec.
NOTE: The issue described above (failed initialization) is different than the Continuous Reboot issue mentioned
below. When the camera LED is solid orange, the camera in most cases can and should be recovered to working
order by upgrading to TC5.1.5 and using systemtools camerarescue from the CLI (page 4), or using the
(page 7) on the existing TC software version.
Root Cause:
The root cause has been found by our camera team and corrected camera firmware is found in TC4.2.4 and
TC5.1.3 and higher; corrected camera firmware is found in those versions. In summary, a bug was found in our
error correction; the new NAND flash found in recent cameras, being a different technology, is more likely to have
correctable errors, and made the bug much more obvious.
Solution:
