memformat

Usage

>> memformat [ type | newtype | availabletypes ]

Security

Unsafe.

Description

This command reports or sets the format used to store deployment data in memory. The available parameters and their usage are described below.

  • type requests the format of the data presently stored in memory, either for a deployment in progress or for one which has finished. If the memory is completely empty because it has been cleared, the response will be none.

  • newtype [= <type>] requests or sets the format of the data which will be used during a future deployment; the value can not be modified while logging is in progress.
    1. rawbin00
    2. calbin00

  • availabletypes requests a list of the data storage formats available for this logger.

If no argument is given to the command, all arguments are reported. Currently supported types are as follows:

rawbin00
This is the 'Standard' format which contains all sample data and supplementary data in a single data set in binary form.

calbin00
This is the 'EasyParse' format, for which the sample data is stored in its own data set in a uniform and consistent format which is simpler to decode.

 For a full discussion of the data storage formats available, refer to the section Format of Stored Data.

Examples

>> memformat availabletypes
<< memformat availabletypes = rawbin00|calbin00

>> memformat
<< memformat type = rawbin00, newtype = rawbin00, availabletypes = rawbin00|calbin00

>> permit command = memclear
<< permit command = memclear
>> memclear
<< memclear used = 0

>> memformat type
<< memformat type = none

>> memformat newtype = calbin00
<< memformat newtype = calbin00

>> memformat type
<< memformat type = none

Errors

Error E0105 command prohibited while logging 
The data storage format may not be modified while logging is in progress; reading is permitted.

Error E0108 invalid argument to command: '<invalid-argument>' 
The supplied argument was not recognized.