Saving Data On The Device; Creating User Data Entries - Matrix Vision mvBlueFOX3 Technical Manual

264

20.8 Saving data on the device

Note
As described in Storing and restoring settings (p. 82), it is also possible to save the settings as an
XML file on the host system.
bilities of the different driver versions in the mvIMPACT Acquire SDK manuals and the according set-
ting classes: https://www.matrix-vision.com/manuals/SDK_CPP/classmvIMPACT_1_
1acquire_1_1FunctionInterface.html
There are several use cases concerning device memory:

20.8.1 Creating user data entries

20.8.1.1 Basics about user data
It is possible to save arbitrary user specific data on the hardware's non-volatile memory. The amount of possible
entries depends on the length of the individual entries as well as the size of the devices non-volatile memory
reserved for storing:
• mvBlueFOX,
• mvBlueFOX-M,
• mvBlueFOX-MLC,
• mvBlueFOX3, and
• mvBlueCOUGAR-X
currently offer 512 bytes of user accessible non-volatile memory of which 12 bytes are needed to store header
information leaving 500 bytes for user specific data.
One entry will currently consume:
1 + <length_of_name (up to 255 chars)> + 2 + <length_of_data (up to 65535 bytes)> + 1 (access mode) bytes
as well as an optional:
1 + <length_of_password> bytes per entry
It is possible to save either String or Binary data in the data property of each entry. When storing binary data
please note, that this data internally will be stored in
time the binary data size.
The UserData can be accessed and created using wxPropView (p. 74) (the device has to be closed). In the section
"UserData" you will find the entries and following methods:
• "CreateUserDataEntry"
•
"DeleteUserDataEntry"
• "WriteDataToHardware"
You can find further information about for example the XML compati-
(C++)
if a password has been defined
format thus the amount of memory required is 4/3
Base64
for this particular entry
MATRIX VISION GmbH
CONTENTS