beautypg.com

Determining the file size of the stored weld data – Dr. Livingstone, I Presume WELDWISE 2400 User Manual

Page 151

background image

0614-INS-400 Rev. D

11-5

Determining the file size of the stored weld data


The following can be used as an aide to determine how quickly the welddata.mdb database will fill up
with weld data. This database can hold up to 1 gigabyte (minus some overhead) of weld data. Each
weld data record is approximately 280 bytes in size. This means that 125,000 weld records would be
approximately 35Mbytes in size.

For a review of the different data modes, please refer to the General Setup section of Chapter 6, WMS
Reference Guide. Depending on the weld data mode settings it is possible to collect data for each half
cycle, segment or weld. It is even possible to shut off data collection altogether.

The number of records collected for a single weld is dependent on the data modes. The most data is
collected when all three modes are set to ‘ALL’. Typically only weld summary data is collected unless
there is a special need to record the more detailed halfcycle data (Example: when trouble-shooting a
weld process).


Records per weld (1 binary select) = halfcycles + segments + weld summary (for 1 weld)

Records per process cycle = Records per weld (weld 1) + Records per weld (weld 2) + etc.

Database size per process cycle (bytes) =

(Records per process cycle) X 280 bytes each

Total Database size per day = Database size per process cycle X process cycles per day


The following example calculates the size based on the worst-case setting only to demonstrate how to
account for all of the different record types. When calculating the number of records recorded per
weld, do not forget to include the number of halfcycles in all of the segments, including the PRE and
POST.

Example: A WeldWise 2400 monitors 2 welds during one process cycle. Both welds have a PRE and
POST of 10 and welds of length 16 halfcycles and 20 halfcycles respectively. There are 5000 process
cycles per day. Assume 3 segments (PRE, WELD, POST), collecting all of the halfcycle, segment and
weld summary data.


Records per weld #1 = (36 halfcycles(total from all segments) + 3 segments + 1 weld summary) = 40


Records per weld #2 = (40 halfcycles + 3 segments + 1 weld summary) = 44

Database size per process = 84 records X 280 bytes = 23520 bytes

Total database size per day = 23520 bytes X 5000 process cycles per day = 117,600,000 bytes

117,600,000 bytes = > 117.6 Mbytes


Note: When only weld summary data records are collected, this calculation gives 2.8 Mbytes per day.
This is a more typical value for a data collection in a production environment.