Brand New Current Profiler "WriteConfig" issue

Up to Software

Brand New Current Profiler "WriteConfig" issue

Posted by Tom Foulds at May 05. 2010

Hello,

I have just received two brand new Aquadopp Current Profilers, but am having some configuration issues with one of them.

 

I do have two identical profilers here and have successfully set up one which has been sent off and deployed.  I have been trying to set up the other on using the same computer and communication cables.  I have also tried to communicate with the profiler on battery and also with an external power source.

I am able to communicate to the profiler, but the “WriteConfig” is failing causing the error.  I was successful in updating the firmware to 3.32 and I am using the latest version of the AquaPro software version 1.34.

Again I am able to connect from both “Communication>Connect” and from “Communication>Terminal Emulater” then hitting “Send Break” which tells me the firmware currently installed (3.32).

I can also use “Deployment>Planning>Load From Instrument” and get the current settings, but if I make a change and hit “Upload” I get an error which reads as follows;

“Command Failed! (WriteConfig)  Acknowledge not received. The configuration may be invalid.  Please check your configuration parameters.  This could also be due to a low RTC battery condition.  Please recharge for 12 hours”

I hit “OK” and subsequent error message reads “Unable to write configuration”.

Despite the error message I am sure my configuration parameters are fine because I used the same ones on the other profiler with no issues, I am also sure that the battery is fully charged, because I swapped it with the other meter which had no issues with the same battery, and I also get the same error message when using an external power supply.

I did check that the appropriate power was getting to the circuit board, but did not go any further as I have no drawings to reference.

 

Any help would be greatly appreciated.

 

Re: Brand New Current Profiler "WriteConfig" issue

Posted by Øistein Hurum at May 06. 2010

Hello Tom,

This very likely is due to a low RTC battery condition. Please note that the RTC battery is the real-time clock backup battery and not the main battery. Recharging for 12 hours should fix this.

Best regards,
Oistein

 

 

Powered by Ploneboard
Document Actions
Log in


Forgot your password?
New user?