sending a configuration file to the vector
by
andilo
—
last modified
Jan 16, 2006 03:56 PM
Hi,
I´m trying to operate a vector on a controller. Everything works fine, so far (I can send softbreakes, start and stop data collection, read the configuration, and record the data over the serial port), but for some reason I´m not able to send a binary configuration file to the instrument.
I generated the *.pcf configuration file using the vector software (with the command line option -cu). The resulting file is 784 bytes long.
And then I tried to send this file to the vector using the CC command (in command mode), but this does not work (the vector is responding with negative acknowledges (NackNack) after each word sent out.
I have tried to do the same thing using the terminal mode in the vector software: I have inserted a CC at the beginning of the of the configuration file and have sent it to the instrument with the send command file button - with the same result.
Is there something special about the vector? Do I have to swap high and low bytes within the binary file?
In the vector software I can choose two different baudrates - the normal baudrate and the recorder/configuration baud rate. Are the configuration data following the CC command supposed to be sent with the second baud rate?
How do I check or change the configuration/recorder baud rate? Is this done automatically by setting the baud rate in the software and going to "stop data collection"? I have tried this too with no results.
thank you and best regards,
Andreas
I´m trying to operate a vector on a controller. Everything works fine, so far (I can send softbreakes, start and stop data collection, read the configuration, and record the data over the serial port), but for some reason I´m not able to send a binary configuration file to the instrument.
I generated the *.pcf configuration file using the vector software (with the command line option -cu). The resulting file is 784 bytes long.
And then I tried to send this file to the vector using the CC command (in command mode), but this does not work (the vector is responding with negative acknowledges (NackNack) after each word sent out.
I have tried to do the same thing using the terminal mode in the vector software: I have inserted a CC at the beginning of the of the configuration file and have sent it to the instrument with the send command file button - with the same result.
Is there something special about the vector? Do I have to swap high and low bytes within the binary file?
In the vector software I can choose two different baudrates - the normal baudrate and the recorder/configuration baud rate. Are the configuration data following the CC command supposed to be sent with the second baud rate?
How do I check or change the configuration/recorder baud rate? Is this done automatically by setting the baud rate in the software and going to "stop data collection"? I have tried this too with no results.
thank you and best regards,
Andreas
Current state:
Being created
Hi Andreas,
What kind of software version do you use?
The resulting .pcf file should be 512 bytes long. I have tested this using version 1.27 and got a 512 bytes long file as expected. The latest software version can be downloaded using the Software&Firmware link on our support page. Follow the registration procedure if you are not already registered.
To test this with the terminal emulator the next step is to append the command CC at the start of the .pcf file (using a binary editor) like you have done. The resulting 514 bytes long file can then be sent to the Vector by using the command file button. Make sure that you have checked for binary mode when doing this, if not the software will interpret the command file as text.
The configuration data is sent with the regular baud rate. The term configuration baud rate was somewhat misleading so it has been changed to upgrade baud rate since it is only used for firmware upgrades. The baud rate switching is done automatically in the software when you start a firmware upgrade or a recorder data download.
Best regards,
Sven
What kind of software version do you use?
The resulting .pcf file should be 512 bytes long. I have tested this using version 1.27 and got a 512 bytes long file as expected. The latest software version can be downloaded using the Software&Firmware link on our support page. Follow the registration procedure if you are not already registered.
To test this with the terminal emulator the next step is to append the command CC at the start of the .pcf file (using a binary editor) like you have done. The resulting 514 bytes long file can then be sent to the Vector by using the command file button. Make sure that you have checked for binary mode when doing this, if not the software will interpret the command file as text.
The configuration data is sent with the regular baud rate. The term configuration baud rate was somewhat misleading so it has been changed to upgrade baud rate since it is only used for firmware upgrades. The baud rate switching is done automatically in the software when you start a firmware upgrade or a recorder data download.
Best regards,
Sven
Current state:
Being created
Hi Sven,
thanks! It works now with version 1.27. I used version 1.25 before and it seems that this caused the problem. I also noticed that regular deployment files created with version 1.25 are not comparible with version 1.27.
Thank you also for your reply to the question ragarding the hard break for an NDP.
best regards,
Andreas
thanks! It works now with version 1.27. I used version 1.25 before and it seems that this caused the problem. I also noticed that regular deployment files created with version 1.25 are not comparible with version 1.27.
Thank you also for your reply to the question ragarding the hard break for an NDP.
best regards,
Andreas
Current state:
Being created
Powered by
Ploneboard

