GSE Scale Systems - 215
Chapter 20 Database (OPTION) Technical Reference Manual
However, if some of the database memory has been
allocated to general usage (normally to allow larger
macros) then the amount shown at P60010 will be
reduced by 8192 (8K). Refer to parameter P65010 for
more information on this item.
P60011 dbAvl 24242 This value indicates the
remaining amount of RAM available for creating more
rows. When this value becomes relatively small, then the
database is coming close to running out of room for more
records. When this parameter is selected, it may take a
while for the unit to add up all of the unused memory.
While the unit is calculating, the display will show
"Look-ing.."
P60012 dbUse 14 This number indicates the
amount of database memory actually used by the
databases, for both recording the setup and storing
records. When this value is added to the "dbAvl" value,
the result should equal the value for P60010.
P60013 BlkSz 16384 The Block Size parameter
displays the size of the largest contiguous block of
memory available for use by the database feature. This
parameter will be seldom used. However when either
multiple databases of various sizes are used or if rows are
updated and / or deleted quite often, the available
memory can become quite fragmented. So, if a situation
arises where the total amount of available memory, as
indicated by P60011, is sufficient to create a row and yet
the "OutOF Memry" error message results, then the
maximum block size parameter can be checked to
determine if there is enough memory available in one
contiguous block to perform the operation. If there is not
enough contiguous memory available, the only remedy is
to compact the stored rows. This can only be
accomplished by downloading all of the stored database
records and the database setup to a computer and default
the database using parameter P65010. Then reload the
setup and the database records using the "Up-load"
command.
P60014 dbase Error The results of the last
database operation can be checked with this parameter.
Each database operation sets a code indicating the results
of the operation. The corresponding error message is
displayed at this parameter.
The next 16 database information modes display the
number of records (rows) created in databases which
have been setup. If a database has not been setup, then
the parameter for the number of rows within that
database is skipped.
Specifically, P60021 will display the number of rows
currently stored within database 1, P60022 for database
2, etc... with P60036 indicating the current number of
rows stored in database 16.
20.15 DEFAULTING THE ENTIRE
DATABASE
P65010 can be used to completely clear out the
DATABASE data and setup. However, the deletion is
not final until you exit the setup mode and all changes
are saved.
Press <ENTER> to simply default the database setups.
Whether or not any database memory is allocated to
general usage is not affected. However if it is desired to
allocate some of the database memory for general use,
press <2> <ENTER>. This will reduce the total amount
of database memory by 8K bytes. To reverse this and
keep all the database module's memory allocated to
databases, press <1> <ENTER>.
Allocating database memory to general usage can be
used to allow variably sized setup modes (such as custom
transmit setup and macro setup) to increase when they
would otherwise be limited by the occurence of the "Out
Of RAM" error message. If this is done, the only
limitation on the amount of information entered into
these setup modes is the amount of available EEPROM
memory.
20.16 MEMORY CONSUMPTION
When a database RAM module is completely blank,
P60012 will indicate that 14 bytes are in use. This
amount is due to the initialization of the module to make
it usable for database operations.
The amount of memory required to create each record
(row) in a database is dependent on the database's
definition. To determine the amount of memory required
per record, use the following procedure.
a. Each row requires 6 bytes for internal purposes.
b. Each column uses four bytes.
c. Alpha-numeric data may require additional
memory, depending upon the size of the data.
Thus the amount of memory required per row
will depend on the actual length of the ID data
being stored. Refer to the following notes:
SECTION - 20.14
To Next Page
Loading...