Pros and Cons - Automating Firmware Updates

By Ethan Ace, Published Jul 01, 2015, 12:00am EDT (Info+)

Firmware and software updates are one of the most tedious tasks in surveillance, so why not make them easier? While other devices, like PCs, phones, and other consumer electronics have featured automatic updates for years, few manufacturers even automatically check for, let alone perform updates. 

In this note, we look at Avigilon, Axis, Bosch, Exacq and Speco proceses as well as the advantages and disadvantages of automatic updates and easing this process.

**********

***** *** *** ********** ** ******* updates *************:

****** ******** *****

********* ******* ***** ***** *** ******** help ** ****** ******** ****** ***** in ******* *** *********, ** ************* could **** ***** ** ******* ***** ******. Patching ***** ***** ******* ********* ********** by *** ********* *** **** ***** or *********** ******* ****** * ******** event, *** *** ******* ****** ** the ************* *****. **** ** ********** important ** ***** ******** ******* *********.

****** *** ******** ***********

**** ********** ******* *********** * ****** ** ******** ** in *****, ******* *********** ******** *********** and *** ********. * **** ******* of **** *** ** **** *******'* ********* **** *****, ***** ******* ******** *** ***** performance ******* *.** *** *.** *********, seen ****:

******* ******* *****

********** *** ****** ******* ******* *** number ** ******* ******* *** (*********** buggier) ******* ** ********.**** **** ***** on * ****** *******, **** ******* ******** may ***** **** ** ** ** date ********/********, ******** *****.

*************

****** *** *********: ****** ************

******** ******** ******* *** *********, ******* is ***** ** ******* *** *********** of ** ****** ******** * *** integration. ******, ** *** **** ** **** seen ********* *** ***** ** **** happening *********.

*******, **** *** ****** *****+ ***** ** *** **** *** *****, ***** 5-6 ********* *****, ** **** ***** experienced ****** *** *********** *** ** a ******** ******. ** ****, *** opposite *** **** **** ** **** than *** ********, **** *** ********* making **** ********** ***** ** ******** integrations **** ********.

************: ****** *******

********* ******* ********* *** ***** *** **** in ****** *******: ******* ***** ************ unavailable ****** ** ********. ****** ********** ************ *****, ** ***** ** * minute, ****** *** **** **-** ******* to *****. ****** ** **** ***** this *** ** *********** ** **** critical **********, **** * ****** ****** may **** *** ***** ** ******* used ** *** *********** *** ******** infrastructure. ******* ** ****, ****** ******* should ** **** ** ***** *****.

Current ****** *** *** ********

**** ******** *******, **** *********,*********, ***., ************* ***** *******, ***** commercial ******* *** *******. ****** **** are ***, ***** *** **** ************* which ******* ********* ******** ** **** fully ********* *******. 

***** ********* *******: *****

**** *** ********** ** *********** *********, ***** *** ****** **** manual *******, ************* ** *** ********, and ***** ********* ********:

**** *** *****: ****** *****, ********* Update

**** ******** **** ***** *** ****** process *** **** ****** **********. **** in *** ****** ******** ******, * list ** ********* ** *********, **** the ****** ************* ********** *** ******* to *** ** **** ******* **************. The ******* *** ***** ** *******, but ********* ** *** ****** ** a ****.

********: ****** *** *******, ********* ******

******** ******* ************** ***** ** ******** ****** ********, with ** ************ ** *** ******** in *** ****** ** ****** *******. However, **** * *** ******* *** been *********, **-**-**** ******** ******** *** pushed ** *** ********* ******** *******. Note **** ***** ** ** ******* for ******** ******* ************* ***** **** this, *** ******* **** ** ********* manually.

*****: ****** *****, ********* ******

********* ******** ** *****, ***** *** ***** *** *** server ******** ** *** ****** *** of *** ****** ****, ****** ***, and ************* ******** *** ***** ** in **** *** *****. ** ******* user *********** ** ********. 

What ** *** *****?

****** ***** ********** *** *************, ***** do *** *****? *** ********* ******* a *** *****, ***** ** ********? Or ** **** ****** ********** ****** and **** ******* ****** *** ** peak ***********?

Comments (9)

Avatar

Paul Curran

07/01/15 02:04pm

Updating firmware is a good idea, but you are best sandboxing some camera first as a trial. Also factor in you may / will need to update the VMS in some cases. :)

Agree: 1
Disagree
Informative
Unhelpful
Funny

Scott Sheldrake

07/01/15 04:41pm

Typical scenario : Problem with Axis camera and Exacq VMS

Step 1. Call Axis tech support who immediately insists you must upgrade the camera firmware. Upgrading firmware does not solve issue (has it ever?)

Step 2. Hang up with Axis, call Exacq tech support who immediately blames the camera firmware which is newer than what they have tested and officially support.

Step 3. Upgrade Exacq client/server out of sheer frustration. Recording breaks completely, or other problems appear.

Step 4. Submit trouble tickets to everyone.

Step 5. Wait 6 months, other companies submit similar tickets. Both companies fix bugs with updates. Upgrade furiously.

Step 6. Take note of magical combination of working camera firmware and VMS software. NEVER LOSE THIS INFORMATION. HOLD ON TO IT FOR DEAR LIFE.

Agree: 4
Disagree: 1
Informative
Unhelpful
Funny: 4

John Honovich

IPVM | In reply to Scott Sheldrake | 07/01/15 04:43pm

Funny cause it's true....

I think 6 months is an exaggeraton but we have certainly seen that basic pattern, and not unique to Axis / Exacq either.

Agree: 1
Disagree
Informative
Unhelpful
Funny

johan Schorreel

In reply to Scott Sheldrake | 07/02/15 08:07am

Having worked with Exacq for over 3 years, and using almost exclusively Axis I have not had this experience. Yes we have had issues with firmware and yes they were not solved within one week, but there has always been a workaround that 'temporarily' resolved the problem until the proper solution was introduced.

I do understand and sympathize how frustrating it can be, if combinations do not work as they should. This was also a reason why we opted to leave 'other brands' and to go for Axis.

As for the automatics updates : I use a policy where the VMS updates are used in-house after the initial release and only after several weeks we apply them in the field. As for firmware updates for camera's, this is more tricky. New camera's come with new firmware and if they are working reliable, then we would upgrade older versions IF and only IF we have a problem with that camera on a site.

Agree
Disagree
Informative
Unhelpful
Funny

Michael Miller

07/01/15 06:27pm

For most of our large customers the system is off line with no WAN access so automatic updates from the web don't work out so well. Automatic firmware updates on the other hand are a huge time saver.

Agree
Disagree
Informative
Unhelpful
Funny

Glynn Thomas

07/01/15 08:13pm

I have noticed some cameras when firmware update revert to default settings.

Particually annoying as then have to go through the camera settings and readjust

Agree
Disagree
Informative
Unhelpful
Funny

John Honovich

IPVM | In reply to Glynn Thomas | 07/02/15 01:42am

Glynn,

Yikes. I hope that manufacturer sees that as a bug. Who was it? And has it happened more than once?

Agree
Disagree
Informative
Unhelpful
Funny

Irina Manea

07/02/15 06:55am

I consider that software update is a must. However i would have some of the following conditions met:

- posibility of programing this automated update. for example in the morning when there is no activity

- not using the newest software (on version older)

- update only 1/3 of the system. monitor for 1-2 month and than update all

- make sure you can downgrade easily

- save all config from the old setup (cameras and VMS)

Agree
Disagree
Informative
Unhelpful
Funny

Andrew Thomas

07/10/15 02:13pm

When Juniper issued automatic updates to routers in the past, It all but killed Blackberry for several days. A well designed an secure camera network, isolated from internal and external networks should only need firmware updates to address a measurable issue, or to gain a feature, or improve reliability. I do think keeping firmware current is important, but an uncontrolled update makes no sense. Imagine your best client with 100 cameras that factory reset to the same default IP address. Upgrading firmware, software upgrades, feature enhancements, can all be sold as part of a maintenance support plan.

Agree: 1
Disagree
Informative
Unhelpful
Funny
Login to read this IPVM report.
Why do I need to log in?
IPVM conducts reporting, tutorials and software funded by subscriber's payments enabling us to offer the most independent, accurate and in-depth information.
Loading Related Reports