Model 574 Programmable Counting System (PCS)
216 - GSE Scale Systems
ID data four characters or less in length requires no
additional memory.
ID data between five and seven charcters in length will
require eight additional bytes of memory to store a
record. This is in addition to the four bytes required as a
minimum for an ID column.
ID data greater than 7 characters in length will require a
number of bytes equal to the length of the ID plus one.
Again, this is in addition to the four bytes required as a
minimum for an ID column. Thus the number of
additional bytes required for an ID which is 13 characters
in length would be: 13 (size) + 1 (extra) = 14 additional
bytes per row.
As an example, for a database which has 3 columns the
minimum amount of memory required per row would be:
6 (overhead)
(3 x 4) = 12 (3 columns x 4 bytes per column)
__
18 bytes per row minimum
If any of the columns were ID types (parameters 21 - 26)
then additional memory may be required per row,
depending on the specific size of the data being stored in
the ID(s), as described above.
The amount of memory required to setup a database is
twelve bytes plus one additional byte per column
defined. Thus a database with three columns uses 12 + 3
= 15 bytes of memory. This small amount of memory
usage is probably insignificant in the overall picture of
total memory usage, but this information is provided for
those applications which require a considerable amount
of memory.
The following is a macro setup that will determine the
exact number of rows that can be created based on the
number of columns set in the database. Setup to allow
easy execution of the macro by naming macro 0 at
parameter P850. Make sure P720 is set to MENU. The
execution of the macro will take a while and the time is
dependant on what size DBase module is installed. After
running the macro, the total number of rows can be
viewed in reg#1 (P91) or P60021.
Macro#0
0;91%C Reset reg# 1
1%T Tag location
Run..ning%I idle
%i id
11%s Select dbase mode
1%e select dbase 1
3%s Make Row
%e enter
%_ IF any DBase error (if out of memory)
DBASEFULL!%S%P 1 second prompt
%N ELSE
1;91%+ increment reg# 1
1%J Jump to TAG 1
%E END IF
The previous macro was tested with a GSE 24K database
module. Two columns were setup in database #1. These
columns were ID#1 and the pieceweight (P34). The total
number of rows allowable in the database was shown in
reg#1 was 1,101. This could be five times this if using a
GSE 120K database module. Total running time of the
macro was approximately 3.5 minutes. The ID was
entered as five characters.
Remember that the number of columns (parameters)
setup in the database structure is proportional to memory
consumption. The more columns used the less number
of rows can be stored.
20.17 DATABASE ERRORS
If an error occurs during the execution of any database
command, then the corresponding error message is
displayed for one second. Refer to table 38 for a listing
of database error codes. Also the error status of the
command is recorded so that a macro can be
programmed to react appropriately if a database error
occurs. However if a macro is performing the recall
operation, then error messages will not be displayed.
Therefore it is the responsibility of person programming
the macro to check for possible errors at the appropriate
times to insure that the operation will occur as expected.
For instance, in some applications it may be desirable to
prompt the scale operator through the necessary steps to
add an item to a database if the item is not found. In
other cases, it may be desirable to request verification of
Note:
The following procedure should be performed by
qualified personnel only!
To Next Page
Loading...