Close

L'équipe Hikvision recueille des fonds pour la neuvième mission annuelle 500 Sécurité 5 / 2K à l'ISC Ouest 2018

avril 23, 2018

Hikvision Mission 500 5k participants

Les employés de Hikvision Amérique du Nord ont participé à la Mission 500 Security 5 / 2K à l'ISC West 2018, amassant des fonds pour fournir de la nourriture, des vêtements et du matériel éducatif aux enfants dans le besoin aux États-Unis.

Un communiqué de presse sur la participation de Hikvision à l'événement a été publié aujourd'hui.

L'équipe Hikvision a recueilli 2 415 $ pour l'organisation à but non lucratif, se classant quatrième dans la compétition de collecte de fonds sur 40 équipes. Hikvision USA Inc. a également commandité la distribution de sacs sur la ligne d'arrivée de la course. Plus d'une douzaine d'employés d'Hikvision ont participé à la course, qui a eu lieu à Sunset Park à Las Vegas lors de la conférence annuelle ISC West.

"Redonner fait partie de la mission de Hikvision. Nos employés sont enthousiastes à l'idée de soutenir une organisation comme Mission 500 et de participer au Security 5 / 2K, un événement amusant qui rassemble l'industrie de la sécurité pour fournir un soutien direct aux enfants pauvres », a déclaré Alex Asnovich, directeur du marketing chez Hikvision Amérique du Nord.

En plus de participer à la troisième édition annuelle de la Classique de hockey de la mission 500 tenue le 15 février 2018 à Toronto, Hikvision et ses employés ont fait don de plus de 5 000 $ à la mission 500 cette année.

Mission 500 a amassé 113 411 $ dans l'événement Security 5 / 2K de cette année.

Nouvelles de l'entreprise

View the most updated version of this document here:

https://techsupportca.freshdesk.com/en/support/solutions/articles/17000113531-i-series-nvr-firmware-upgrade-instructions

The I-series NVR (such as the DS-7716NI-I4) is one of Hikvision's most popular and feature-rich recorders. As such, many firmware revisions have been introduced over the years to continually ensure the product is compatible with the newest technology available. Due to the many revisions, we recommend that the user closely follows the instructions below in order to reduce the amount of time spent as well as the chance of failure.

Database Optimization and Repair

As more affordable IP cameras are introduced over time with greater video resolution and data sizes, more efficient database management also becomes necessary. The introduction of firmware v4.0 brought about a new database architecture in order to be futureproof.

After upgrading to v4.X, the recorder database will need to be converted and optimized. If you are experiencing issues where playback is expected but not found, make sure "Database Repair" is performed as indicated in the procedures and scenarios below.

Preparing the Upgrade

Before proceeding with upgrade, it is recommended that NVR configuration file is exported from the NVR over the network or on to a local USB drive.

Upgrading from v3.4.92 build 170518 or Older

All recorders must reach v3.4.92 before proceeding further. Upgrading from versions before v3.4.92 directly to any version of v4.X will likely cause the recorder to fail.
If the recorder is already at v3.4.92, a full factory default is highly recommended before upgrading to any version of v4.X. There is a high chance of unit failure (requiring RMA) if the unit is not defaulted before upgrade.
After reaching v3.4.92 and performing a full factory default, an upgrade directly to v4.50.00 is acceptable.
After the upgrade is completed and the recorder is reprogrammed, it may be beneficial to perform a Database Repair. For details, refer to the section "Database Optimization and Repair" above.
To verify repair progress, you may refer to the HDD status, or search the recorder log for repair started and stopped entries. Note that while the HDD is repairing, new recordings are still being made, but some existing recordings may not be searchable until repair is complete.
If you continue to observe playback issues after database repair, ensure there are no power, network, or motion detection issues. Should the problem persist, contact technical support.

Upgrading from Any v4.X Build to v4.50.00.

Any v4.X build can be upgraded directly to v4.50.00.
Export configuration is highly recommended before performing the upgrade.
If upgrading from any v4.X version that was not v4.22.005, a Database Repair is recommended. Refer to Step 4 and onwards in the previous section.

Downgrading

Downgrading is not recommended. Due to new features and parameters constantly being added, downgrading may cause the NVR to factory default itself or require a manual default to operate properly.

View the most updated version of this document here:
K-Series DVR upgrade instruction
The Turbo 4 Hybrid DVR K series has multiple models and across different platform and chipset. It also has similar firmware development of other recording product line; DVR K series has also introduced the GUI4.0 to ensure the series to be compatible to the newest technology available. The new database architecture is also brought into the DVR firmware v4.0 to be future proof and for better recording search experience.

Database Optimization and Repair

As more affordable cameras introduced over time with greater video resolution and data sizes, more efficient database management also becomes necessary. The introduction of firmware v4.0 brought about a new database architecture in order to be futureproof.
After upgrading to v4.X, the recorder database will need to be converted and optimize. If you are experiencing issues, where playback is expected but not found, please make sure to perform "Database Rebuild" as indicated in the procedures and scenarios below.

Preparing the Upgrade

Before proceeding with upgrade, it is recommend exporting DVR configuration file from the DVR over the network or on to a local USB drive.

Action after firmware upgraded

1. Upgrade the DVR according to the chart above.

2. Reconfirming Channel's Recording Schedule

- Confirm channel's recording schedule is enable.

- Check if the channel is on correct recording schedule.

3. Double Check Storage Setting

- Make sure all channel are assigned to record on its HDD group when the Storage setting is under Group Mode.

4. Perform Database Rebuild locally.

• Some version above support Database Rebuild via web access - K51 and K72

• Perform Database Rebuild regardless if system is having any database issue symptom.

• Database Rebuild process is average ~30 to 60min per TB. The process may still varies depends recording data.

• After Database Rebuild - Check log to confirm Database Rebuild has went thru properly.

• If Database Rebuild Started and Stopped log has been log only within few minutes. Database rebuild may not has been completed properly. It is strongly recommend performing the Database Rebuild again.

• To check log > System > Log > Information > Database Rebuild Started and Stopped.

• If the log option is not available - access system via SSH can also obtain similar result.

5. Recording Data is still missing after database rebuild process.

If the data has not been recorded or has been overwritten, Database rebuild process is not able retrieve those lost data. Have the system upgraded to the latest available firmware version above to prevent any future data lost is strongly recommended for all application.