Appendix H
93
VIS-CAM Systems
12.4
Troubleshooting:
1
If any errors occur during the firmware upgrade process, document the type of error and redo the
firmware upgrade process WITHOUT REBOOTING THE CAMERA. A CAMERA REBOOT AT THIS TIME COULD
CAUSE CATASTROPHIC FAILURE resulting in the camera having to be returned to JAI for repair.
2
If camera has successfully updated and you are unable to locate the camera with ensetup, follow this
procedure.
12.4.1
Scenario 1: If you can ping the camera
1
Telnet to the camera. Log-in as root, password is JAIPULNiX
2
Type test_bcs –a erase and hit return. This erases APP file from the FlashROM. This process is needed, if
LIB/DRV firmware update fails. If LIB/DRV is corrupt and APP starts, the APP exits abnormally, and the
watchdog timer keeps rebooting the camera.
3
Type reboot and hit return. This reboots the camera.
4
Unzip the firmware ZIP file in your host PC.
5
Telnet to the camera and log-in again.
6
FTP the following 2 files to the camera. (FTP user name = root, password = JAIPULNiX). These 2 files are
common to all EN cameras.
Make sure to change directory to /usr/local/bin (cd /usr/local/bin)
Make sure to set the FTP transfer mode to BINARY mode (bin)
a
.drv file
b
.app file
7
On the telnet screen, command cd /usr/local/bin
8
Start test_bcs firmware upgrade utility
a
test_bcs –l <DRV FILE NAME>.drv
b
test_bcs –a <DRV FILE NAME>.app
Make sure to wait until the flashROM updgrade is complete. You’ll see the progress on the screen.
9
After 2 firmware upgrade is complete, type reboot and hit return. This reboots the camera and the 2
new firmware will be loaded.
10 Start ENSetup, or restart it if it was already running. The software should find the camera now. If not,
please contact JAI for the further troubleshooting.
11 If the ENSetup finds the camera, then follow the regular firmware upgrade using ZIP file to make sure
other firmware is updated. H8 and FPGA files are specific to each camera models, and JAI do not
recommend manual upgrade of these firmware. Instead, let ENSetup software automatically find proper
files. See Section XXXXXX.
12.4.2
Scenario 2: If you can not ping the camera
1
Use RS-232 Serial Debug Cable. 9600bps, 8bit, No Parity, 1 stopbit, No Flow Control
2
Reboot the camera.
3
Log-in as root, password is JAIPULNiX
4
Type test_bcs –a erase and hit return. This erases APP file from the FlashROM. This process is needed, if
LIB/DRV firmware update fails. If LIB/DRV is corrupt and APP starts, the APP exits abnormally, and the
watchdog timer keeps rebooting the camera.
5
Type reboot and hit return. This reboots the camera. Make sure to connect Ethernet cable to the
camera at this point.
6
After the camera is up again, log in as a root.
Summary of Contents for VIS-CAM System
Page 1: ...VIS CAM System Vehicle Imaging Subsystem Document Version 10436 Document P N E...
Page 2: ......
Page 12: ...VIS CAM Systems xii List of Tables...
Page 20: ...VIS CAM Systems 8 Preparing for Installation Figure 5 VIS 300 U S Camera options chart...
Page 21: ...Preparing for Installation 9 VIS CAM Systems Figure 6 VIS 350 U S Camera options chart...
Page 22: ...VIS CAM Systems 10 Preparing for Installation Figure 7 VIS 400 U S Camera options chart...
Page 23: ...Preparing for Installation 11 VIS CAM Systems Figure 8 VIS 500 U S Camera options chart...
Page 24: ...VIS CAM Systems 12 Preparing for Installation Figure 9 VIS 300 European Camera options chart...
Page 25: ...Preparing for Installation 13 VIS CAM Systems Figure 10 VIS 350 European Camera options chart...
Page 26: ...VIS CAM Systems 14 Preparing for Installation Figure 11 VIS 400 European Camera options chart...
Page 27: ...Preparing for Installation 15 VIS CAM Systems Figure 12 VIS 500 European Camera options chart...
Page 92: ...VIS CAM Systems 80 Appendix B Figure 90 Lane controller setup...
Page 100: ...VIS CAM Systems 88 Appendix E Figure 98 Operation configuration of Serial port 1...
Page 110: ......
Page 111: ......