the
by
andilo
—
last modified
May 17, 2006 10:03 PM
(I´m sorry - this thread belongs to the one before...)
Hi Sven,
there is something wrong with the new software version. The Vector is not responding to changes in any parameter (sampling frequency, coordinate system,....).
It seems that the instrument is ignoring the new configuration file completely.
Maybe the checksum is wrong?
Andreas
Hi Sven,
there is something wrong with the new software version. The Vector is not responding to changes in any parameter (sampling frequency, coordinate system,....).
It seems that the instrument is ignoring the new configuration file completely.
Maybe the checksum is wrong?
Andreas
Current state:
Being created
Hi Andreas,
Can you verify that you are running software version 1.28beta4 (Help->About)?
You can use the command GC to read back the configuration to verify that it has been stored in the instrument.
We have tested the software and did not see any problems. As this may have some general interest, here is an example on how this can be tested:
- option -cu on the command line
- set the appropriate configuration parameters and save the deployment as setup.dep
- copy the uploaded file (cc.pcf) to the same folder as setup.dep (the file simply contains the two characters CC)
- from a command prompt, copy /b cc.pcf + setup.pcf test.pdc This adds the command CC to the configuration structure.
- then use the terminal emulator of the Vector software, check the box for binary mode and use the command file button to upload the file test.pdc. Make sure you receive acknowledge (06 06)
- enable logging, send the GA command and start a measurement with the ST command. Stop logging and convert the logged data.
We verified that the sampling rate changed from 64Hz to 8Hz and that there were fast analogue data present for both configurations.
Best regards,
Sven
Can you verify that you are running software version 1.28beta4 (Help->About)?
You can use the command GC to read back the configuration to verify that it has been stored in the instrument.
We have tested the software and did not see any problems. As this may have some general interest, here is an example on how this can be tested:
- option -cu on the command line
- set the appropriate configuration parameters and save the deployment as setup.dep
- copy the uploaded file (cc.pcf) to the same folder as setup.dep (the file simply contains the two characters CC)
- from a command prompt, copy /b cc.pcf + setup.pcf test.pdc This adds the command CC to the configuration structure.
- then use the terminal emulator of the Vector software, check the box for binary mode and use the command file button to upload the file test.pdc. Make sure you receive acknowledge (06 06)
- enable logging, send the GA command and start a measurement with the ST command. Stop logging and convert the logged data.
We verified that the sampling rate changed from 64Hz to 8Hz and that there were fast analogue data present for both configurations.
Best regards,
Sven
Current state:
Being created
Hi Sven,
Sorry, I had another problem here with my own software on friday. Now, using software version 1.28beta4, the analog inputs and the sampling frequency etc. are set up properly. Thank you!
However, the nominal velocity range is set to 7 m/s (0.3 m/s in the setup file) and the salinity is reported as N/A in the header file (0 ppt in the setup file).
Could you please check if the Vector software is setting those paramters in the *.pcf file?
best regards,
Andreas
Sorry, I had another problem here with my own software on friday. Now, using software version 1.28beta4, the analog inputs and the sampling frequency etc. are set up properly. Thank you!
However, the nominal velocity range is set to 7 m/s (0.3 m/s in the setup file) and the salinity is reported as N/A in the header file (0 ppt in the setup file).
Could you please check if the Vector software is setting those paramters in the *.pcf file?
best regards,
Andreas
Current state:
Being created
Hi Andreas,
I have checked and the values for velocity range and salinity are set correctly in the .pcf files. Good to hear that it works now.
Best regards,
Sven
I have checked and the values for velocity range and salinity are set correctly in the .pcf files. Good to hear that it works now.
Best regards,
Sven
Current state:
Being created
Hi Sven,
I think there still is a problem with some parameters. You can try the following:
Use the Vector software (1.28beta4) to configure the instrument (choose a velocity range of e.g. 0.3 m/s).
Then start data collection and stop it after some time. If you now read the configuration from the instrument, the velocity range is set to 7 m/s.
I face the same problem when sending a binary configuration file and reading the user setup afterwards. A similar problem is salinity.
cheers,
Andreas
I think there still is a problem with some parameters. You can try the following:
Use the Vector software (1.28beta4) to configure the instrument (choose a velocity range of e.g. 0.3 m/s).
Then start data collection and stop it after some time. If you now read the configuration from the instrument, the velocity range is set to 7 m/s.
I face the same problem when sending a binary configuration file and reading the user setup afterwards. A similar problem is salinity.
cheers,
Andreas
Current state:
Being created
Hi Andreas,
It is still just a software problem (that we should fix at some point), the actual velocity range is defined by the parameters System38 and System39 which do change in the various .pcf-files.
Cheers,
Sven
It is still just a software problem (that we should fix at some point), the actual velocity range is defined by the parameters System38 and System39 which do change in the various .pcf-files.
Cheers,
Sven
Current state:
Being created
Hi Sven,
what does this mean - are the paramters set correctly in the *pcf file and hence in the instrument? Or is the range really set to 7 m/s?
regards,
Andreas
what does this mean - are the paramters set correctly in the *pcf file and hence in the instrument? Or is the range really set to 7 m/s?
regards,
Andreas
Current state:
Being created
Powered by
Ploneboard

