Posted at November 24, 2024 by PCI-DB Team
Install Driver AutomaticallyDevice Name | GeoVision GV-FER3402 IP Camera Firmware 3.00 |
---|---|
Category | Network Ip Surveillance Baby Camera |
Manufacturer | GeoVision |
File Size | 37.9 MB |
Supported OS | OS Independent |
Symptom 1
When upgrading GV-IP Camera directly from firmware V1.06 or earlier to firmware V1.09 or later, the upgrade cannot be completed successfully.
1. Upgrade the camera to firmware V1.08 using the latest GV-IP Device Utility.
2. Upgrade the camera again to the latest firmware version.
Important: Firmware V2.01 is only applicable to GV-IP Camera (except GV-FE420 / 421 / 520 / 521 and GV-FER521) and firmware V2.02 is only applicable to GV-FE420 / 421 / 520 / 521 and GV-FER521. Upgrading your camera with incompatible firmware can limit the access to live view and Web interface (see Symptoms 2 and 3).
If you have upgraded your GV-IP Camera (except GV-Fisheye Camera) to firmware V2.02, you may not be able to connect to live view and/or receive an error message when trying to log in the Web interface:
The error occurs because firmware V2.02 is only applicable to GV-FE420 / 421 / 520 / 521 and GV-FER521. To solve this problem, downgrade the camera to firmware V2.01 using GV-IP Device Utility V8.5.6 or later.
If you have upgraded your GV-Fisheye Camera to firmware V2.01, you may not be able to connect to live view and/or upgrade the camera.
These problems occur because firmware V2.01 is not applicable to GV-FE420 / 421 / 520 / 521 and GV-FER521. To solve this problem, follow the steps below to upgrade the camera to firmware V2.02.
1. Load the camera with this temporary firmware using GV-IP Device Utility
2. Proceed to upgrade the camera to firmware V2.02 using GV-IP Device Utility.
Firmware upgrade fails when you upgrade your GV-Fisheye Camera from firmware earlier than V2.02 to firmware V2.03 or later.
Note: When firmware upgrade is unsuccessful, rebooting the camera will restore the camera back to normal operation.
To solve this problem, follow the steps below.
1. First upgrade the GV-Fisheye Camera to firmware V2.02 using GV-IP Device Utility.
2. Proceed to upgrade the GV-Fisheye Camera to the latest firmware version.
New:
- Support for the following models:
GV-BX2510-E and GV-BX5310-E
GV-VD2500
P-Iris for GV-BX1500-3V / 2500-3V / 3400-3V / 5300-6V
- Support for Preset Set and Preset Go functions for models equipped with motorized varifocal lens
- Support for recording to GV-NAS Systems, provided that the camera adhere to the following settings:
VBR is set to "Good"
Maximal Bit Rate is set to “6” Mbit or lower for 1.3 MP models, and “8” Mbit or lower for 2 MP, 3 MP, 4 MP, and 5 MP models
- Support for motion and audio settings using CGI SDK command
- Support for a new DDNS server "gvdip.com"
- Support for dual streams in GeoVision Fisheye Cameras
- Support for the following functions through ONVIF
WDR, BLC
Device searching
PTZ control (of GV-PTZ Series and models equipped with motorized varifocal lens)
- Support for ONVIF test tool version 14.06
- Support for new image orientation options, "Rotate 90" and "Rotate 270"
- Support for H.264 video codec CABAC encoding
- Support for text overlay by on-screen display which are viewable through GeoVision software or third-party software through ONVIF and RTSP connection
- Support for continuously sending of captured images to the FTP server
- Support for UMTS protocol (3G Modem)
- Possible disruption of file time for files recorded during DST periods
- SSLv3 flaw in OpenSSL library
- Interruption of file backup from GV-Backup Center when the backup is carried out to the next day or next month
- Issue of live view closing when the resolution is set to 448 x 252 and a region for Privacy Mask (under ROI Settings, for GV-IP Cameras connected to third-party software through ONVIF/RTSP) touches the edge of the live view
- Distorted image size when PIP is enabled in full screen
- Issue of frame skipping when any of the following scenarios occur:
files are being recycled on the inserted memory card during motion events motions are triggered immediately after post-alarm recording ends
- Possible live view lag for:
GV-IP Cameras that are set to 1920 x 1080, dual streams
4 M GV-Fisheye Cameras
- Interruption of recording when the GV-IP Camera time is 2000/01/01, monitoring is enabled and the Synchronized with Network Time Server is activated
- Network interruption when the camera is connected to the network through PPPoE and that the camera’s date and time have been configured to synchronize automatically with a Network Time Server
- Firmware upgrade which can now prevent hardware failure when the upgrade fails
- Import setting of GV-IP Device Utility where settings can be imported without changing the device name
- Frame rate options which are changed from 8 options ("2", "3", "5", "6", "10", "15", "20", and "30") to 15 or 30 options ("1" to "15" or "to "30")
- Default maximum frame rate for VBR which is now changed to 12 Mbit for all 3 M, 4 M, and 5 M models
- Tampering Alarm function where the Alarm for Dark Images option is now enabled by default when the Tampering Alarm function is enabled
- D/N mode settings which now also includes "Auto" and "B/W" options when the Super Low Lux is set to "Auto" (for GV-MFD1501 Series / 2501 Series and GV-MDR1500 Series only)
- Denoise functionality for levels 2 to 10
- FTP settings where the user can select between the active or the passive mode
- Web interface language setting where the language options are now shown in its corresponding language instead of English
- Wordings for the Slovakian version of the Web interface
Updating to a newer firmware version than the one already installed on your network camera can improve the device’s overall performance and stability, resolve various issues, and add support for newly developed features or enhance existing ones.
On the other hand, downgrading the camera’s firmware can recover its functionality in the unlikely event the currently installed version is faulty, or the device’s performance dropped after an upgrade. However, bear in mind that applying an earlier build might not always be possible.
Changing the camera’s firmware must be performed when the new release resolves an issue that your device has encountered or adds a new feature (or enhances an existing one) that could prove useful to you.
As for the installation method, the steps vary depending on the model you own, but basically, you must connect your camera via an Ethernet cable (username and password required), and use the downloadable file in the Firmware Update section to upgrade your device. Make sure you do not interrupt the installation process.
However, make sure you carefully read and understand the installation steps so that you don’t end up with a broken device. This process isn’t intended to be destructive, but still, it’s best to save all configurations before applying a different firmware.
That being said, if you consider that this firmware improves your device in any way, then hit the download button and get the desired version; if not, check our website as often as possible so that you don’t miss the update that will boost your camera’s performance.
It is highly recommended to always use the most recent driver version available.
Try to set a system restore point before installing a device driver. This will help if you installed an incorrect or mismatched driver. Problems can arise when your hardware device is too old or not supported any longer.
Device Type: Network Ip Surveillance Baby Camera File Size: 37.9 MB OS Independent
Install DriverDevice Type: Network Ip Surveillance Baby Camera File Size: 37.9 MB OS Independent
Install DriverDevice Type: Network Ip Surveillance Baby Camera File Size: 37.9 MB OS Independent
Install DriverDevice Type: Network Ip Surveillance Baby Camera File Size: 37.9 MB OS Independent
Install DriverDevice Type: Network Ip Surveillance Baby Camera File Size: 37.9 MB OS Independent
Install DriverDevice Type: Network Ip Surveillance Baby Camera File Size: 37.9 MB OS Independent
Install DriverDevice Type: Network Ip Surveillance Baby Camera File Size: 37.9 MB OS Independent
Install DriverDevice Type: Network Ip Surveillance Baby Camera File Size: 37.9 MB OS Independent
Install DriverDevice Type: Network Ip Surveillance Baby Camera File Size: 37.9 MB OS Independent
Install DriverDevice Type: Network Ip Surveillance Baby Camera File Size: 37.9 MB OS Independent
Install DriverFind Missing Drivers
Recent Devices
Recent Drivers
© 2024 PCI-DB.com - PCI Database Replacement. All rights reserved.