Posted at November 17, 2024 by PCI-DB Team
Install Driver AutomaticallyDevice Name | AXIS P5414-E Network Camera Firmware 5.90.1 |
---|---|
Category | Network Ip Surveillance Baby Camera |
Manufacturer | Axis |
File Size | 51.3 MB |
Supported OS | OS Independent |
- Firmware 5.60 extends the ACAP SDK which gives new possibilities to develop ACAPs. It is also possible to enable multiple ACAP applications to run simultaneously.
- Extended SNMP with AXIS Video MIB (Management Information Base). Enables notification of a number of possible disruptions in Axis Products e.g. fan failure, temperature limits, storage disruptions, tampering, video/audio connectors disconnect, via SNMP traps. Available traps depend on the Axis product.
- Auto-format an SD card to a specified file system upon insertion. This will allow easy installation of a new SD card that will be formatted automatically to a preselected file system, mounted and then recording will be resumed.
- Edge Storage recording makes it possible to indicate e.g. on the Live View, that an edge storage recording is ongoing. This allows the operator to be notified if a recording is ongoing or not.
- The Live View page is updated with responsive design and scales with different screen resolutions and browser window sizes. This will allow the user to see the complete page without the need to scroll.
- For all megapixel products, a new default viewing profile for HDTV resolution has been added. This viewing profile is visible in the Live View and is beneficial for demonstration purposes.
- The Export Video Clip capability enables the export of recordings directly from the camera to a PC or a smartphone. Select a portion of an Edge Storage recording from your camera and export as a playable video file to a client. The exported recording will be one playable Matroska file.
- SSH command line interface to the products that may be used for specific support and maintenance activities was introduced in 5.50. SSH is now the only supported protocol to establish a connection and telnet is not supported. SSH is not enabled by default but can be activated by an API.
- Secure FTP (SFTP) is now supported for a more secure file transfer method.
- Edge Storage robustness is improved with features to detect and repair faults due to unexpected loss of storage media.
- Storage limit offers a possibility to control how much storage space may be used for recordings. This is available via VAPIX.
- Axis network cameras now support NAS drives over 2TB.
- Storage manager now collects information about SD card usage.
- EIS improved handling of the motion when pan/tilt.
- Available ONVIF Media Profiles are now presented and configurable using the product Web GUI.
- With SD card Encryption it is now possible to enable encryption of the SD card to protect your data. This encryption is transparent to users and VMS solutions making it possible to activate without adaptations. This feature is presented and configurable both in the Web GUI and via VAPIX.
- Improved start-up time.
- Edge storage recording robustness is improved with an automatic database repair feature.
- SNMP MIB r/w OID values are saved after reboot.
- Video overlay text size can now be set for each individual stream profile.
- Select "Use Temporary Mode" if during ftp upload temporary files are required.
- ONVIF users are now handled when PTZ Control Queue is enabled.
- Removed LLDP-MED logs containing spam.
- Improved robustness for Axis ACAPs.
- Improved handling of frequent I/O triggering.
- When DST is enabled, export recordings can now be done via web interface.
- Reduced audio noise levels from internal microphone.
- Passwords can now contain "#".
- PullMessages now follow the ONVIF specification 9.1.2.
- Users with admin permissions can edit ACAP configuration settings.
- Manual triggers for all enabled View Areas are shown.
- It is now possible to select starting point when playing back a recording while using multicast and H.264.
- To increase robustness, a retry of 10 seconds is added for an action rule. If action fails it will retry until it succeeds or until the rule is no longer active.
- Improved synchronization between sound and video when having low fps and long GOV length.
The firmware can be upgraded using AXIS Camera Management, HTTP or FTP.
1. Download and install AXIS Camera Management on your computer.
2. Download the upgrade file to a directory that is accessible from your local computer if the upgrade file is not to be downloaded via Internet connection from the Axis Support pages.
3. Run AXIS Camera Management. All the Axis devices found on the local subnet (or on subnets with routers that support multicasting) are shown
in the list.
4. Select the devices that you want to upgrade with new firmware (you can
even select different models) and click the Upgrade icon.
Note: A dialog will open if some of the devices can not be configured, e.g. if the devices are not accessible.
5. The Upgrade Firmware dialog shows a list of camera models.
6. Click to locate the new firmware versions stored on your hard drive, select among already downloaded files or select to download official firmware file from Axis Support Pages (marked with Download). This needs to be done for each Axis network camera or video encoder model.
7. Click OK to start upgrading the devices.
1. Download the upgrade file to a directory that is accessible from your
local computer.
2. Go to the product's start page (e.g. http://192.168.0.90).
3. Click the Setup link and log in as "root" (or any other user with Administrator privileges). You must be logged in as an Administrator to
upgrade the unit.
4. Click System Options in the menu to the left.
5. Click Maintenance.
6. Click the Browse button in the Upgrade Server section.
7. Select the upgrade file you downloaded (and maybe decompressed) from our site. This file is typically named after the product and Firmware version.
8. Click the Open button.
9. Click the Upgrade button in the Upgrade Server section.
10. Wait for the flash load to complete, which may take 1-10 minutes. The upgrade procedure is in four steps:
- Step 1, Shut down: Running applications are shut down and active connections are terminated.
- Step 2, Uploading firmware: The old firmware will be erased and the new firmware will be saved. During this step, the Power LED will blink green/amber. After a while the progress of the upgrade will be displayed in the Web browser.
- Step 3, Reboot: The system restarts automatically.
- Step 4, Reconfiguration:The new firmware settings are configured to match the previous settings.The Status LED will be amber during this step.
11. After the upgrade has completed, the unit will automatically initiate the
system, during which the Status LED blinks amber. When initiation is complete and the system is ready for use, the Status LED will be green.
1. You must be at the command prompt and in the directory that contains the upgrade file. Example: C:\Axis\Product\Firmware
2. From the command prompt, open an FTP connection to the unit you wish to upgrade. (Do not use a Windows based FTP-program to do this, use only
command line FTP programs!)
3. Log in as root. You must be logged in as the root user to upgrade the unit.
4. Change to binary transfer mode by typing bin and press enter.
5. Type hash and press enter. (This will allow you to see how the upgrade
progresses)
6. Type the command put XXX.bin flash where XXX.bin is the name of the upgrade file you downloaded (and maybe decompressed) from our site. This file is typically named after the product and Firmware version.
7. Wait for the flash load to complete, which may take 1-10 minutes. The
upgrade procedure is in four steps:
- Step 1, Shut down: Running applications are shut down and active connections are terminated.
- Step 2, Uploading firmware: The old firmware will be erased and the new firmware will be saved. During this step, the Power LED will blink green/amber. After a while the progress of the upgrade will be displayed in the command prompt.
- Step 3, Reboot: The FTP session terminates and the system restarts automatically.
- Step 4, Reconfiguration: The new firmware settings are configured to match the previous settings. The Status LED will be amber during this step.
8. After the upgrade has completed, the unit will automatically initiate the system, during which the Status LED blinks amber. When initiation is complete and the system is ready for use, the Status LED will be green.
The device can alternatively be installed using the ARP and Ping commands.
1. Acquire an unused IP address for the camera. This IP address must be on the same subnet as your computer.
2. Locate the serial number (S/N) on the camera’s rear label.
3. From a computer on your network, open a Command Prompt (in Windows: from the Start menu, select Run... and type cmd in the field. Click OK).
4. As appropriate for your operating system, enter the following commands:
Windows syntax: Windows example:
arp -s <IP Address> <Serial Number>
ping -l 408 -t <IP Address>
UNIX/Linux/Mac syntax: UNIX/Linux/Mac example:
arp -s <IP Address> <Serial Number> temp
ping -s 408 <IP Address>
5. Check that the network cable is connected. Start/restart the camera by disconnecting and reconnecting the power cable.
6. Close the Command prompt when you see ‘Reply from 192.168.0.125: ...’
7. The IP address has been set when the Power indicator is permanently lit and the Network indicator flashes intermittently.
8. Start your browser, enter the IP address of the camera in the Location/Address field and press Enter on your keyboard.
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: 50.4 MB OS Independent
Install DriverDevice Type: Network Ip Surveillance Baby Camera File Size: 50.2 MB OS Independent
Install DriverDevice Type: Network Ip Surveillance Baby Camera File Size: 47.3 MB OS Independent
Install DriverDevice Type: Network Ip Surveillance Baby Camera File Size: 51.3 MB OS Independent
Install DriverDevice Type: Network Ip Surveillance Baby Camera File Size: 45.9 MB OS Independent
Install DriverDevice Type: Network Ip Surveillance Baby Camera File Size: 49.3 MB OS Independent
Install DriverDevice Type: Network Ip Surveillance Baby Camera File Size: 49.5 MB OS Independent
Install DriverDevice Type: Network Ip Surveillance Baby Camera File Size: 49.9 MB OS Independent
Install DriverDevice Type: Network Ip Surveillance Baby Camera File Size: 51.3 MB OS Independent
Install DriverDevice Type: Network Ip Surveillance Baby Camera File Size: 45.9 MB OS Independent
Install DriverFind Missing Drivers
Recent Devices
Recent Drivers
© 2024 PCI-DB.com - PCI Database Replacement. All rights reserved.