Aquadopp (2MHz) Config Errors (possible RTC clock fault?)

Hi there,

We are having some problems getting our AquaDopps (x2) ready for deployment.  I suspect some kind of internal fault, but I'm not sure what, if anything I can do to work around this.  

The problem began last week when I was getting 'WriteConfig' errors when trying to setup a deployment.  The error message I was getting is attached (first_error.jpg).  This persisted across two versions of Aquapro (v1.35 / v1.34), two PCs (one XP, the other Win7), two firmware revisions (one device had v 3.31 and the other, v3.32), and with / without the main battery connected (obviously connected to the DC supply under the latter scenario).  Further, a third Aquadopp, with an 'older' hardware revision and running 1.x firmware is communicating fine under these scenarios - which leads me to believe the fault is with the units themselves.  

This morning (with nothing left to try) I updated the firmware on one of the Aquadopps to v3.37 (the most recent version) and now get a different (but related) sequence of error messages - see attached (new_error_sequence.jpg).  

This appears to be a developing problem in our units.  This was flagged in 2009 by one of our senior PhD students in this forum post.  In this instance charging the unit for 12 hours appears to have solved the problem however at the moment this does not appear to be working (the units have been on DC supply for 20+ hours now to no effect).  

I get a result from a break command, but nothing from RC or BV commands.  To that end, the problem appears to be very similar to the fault described in this forum thread - in which the solution appears to be to return the unit for repair.  

They units were both purchased at the same time and they have both failed at the same time.  

Is there something we can do to get out deployment underway?  Or must we return these units to Nortek for repair?

Any response very much appreciated,

Dan

The aforementioned second screen shot...

Previously Daniel Pritchard wrote:

see attached (new_error_sequence.jpg).  

Dear Daniel,

I guess you already have received a work around from our UK office.

Midlife boards shipped before October 1st 2009 have the possibility of getting this error. The chance of getting it is low, about one of every 300 instruments have had this error.

Please contact us at inquiry@nortek.no for futher instructions if your instrument get this error.

Best regards

Jonas Røstad

Hi Jonas,

Yes.  Thank you.  To confirm, the work around provided (via the UK office) worked perfectly on both of our devices and they are now communicating fine.

Certainly I would agree.  If anyone else see this error in the future - contact Nortek straight away.  The solution is easy enough to implement, but certainly it is something worth discussing with the experts on a case-by-case basis.  

Thanks again,

Dan