What This Guide Covers
This technical note helps you understand the data structure from your scale, balance, meter, or other serial/Ethernet-connected device. Once you understand your data structure, you can use WinWedge’s simple menus to configure data parsing, filtering, and formatting—no programming required. WinWedge then sends the formatted data to your chosen application like Excel or web forms.
Why Understanding Data Structure Matters
Before configuring WinWedge to parse and filter data from your device, you must understand:
-
- What data your device transmits
-
- Which parts of the data are important to you
-
- How to identify data records and fields within those records
-
- Which fields to keep and which to ignore
How to Analyze Your Device’s Data Output with WinWedge
Go to Port>Analyze dialog box. Observe the live data that your device transmits in the “Input” box. Most devices need you to hit the PRINT button on the device or send a command to them to get then to send data. See tech note no_data_appears_in_the_analyze_window. Understanding WinWedge’s Data Processing Approach WinWedge treats each input from your device as a data record containing one or more data fields. You need to identify:-
- How to separate one record from the next
- How to separate individual fields within each record
- Which fields are important for your application
-
- Go to Define menu
- Select “Input Data Record Structure”
-
- Start Of Record Event – What signals the beginning of a data record. Often the first Character received, the first numeric character or a special character.
- End Of Record Event – What signals the end of a data record. Often a <CR> (carriage return) or <CR><LF> or a time delay.
- Record Structure – How fields are organized (single field, multiple delimited fields, or fixed-length fields). If Delimited fields then what is the delimiter character
Real Data Structure Examples
Example 1: Simple Data (such as a scale or meter) Device Output: 110,250,801<Cr><Lf> Data Analysis:-
- Three numeric fields separated by commas
-
- Record ends with carriage return and line feed <Cr><Lf>
-
- Start Of Record Event: “Any Character Received”
- End Of Record Event: “Carriage Return or CrLf Received”
- Record Structure: “Multiple Delimited Data Fields” (3 fields, comma delimited)
-
- Records have different numbers of fields
-
- Uses both commas and asterisks as separators
-
- Configure WinWedge to translate all asterisks (*) to commas (,)
- Result becomes: Sample#1,,213,,32,,,,23,,<Cr><Lf>
- Count maximum fields across all records (13 fields in this example)
- Configure for “Multiple Delimited Data Fields” with 13 maximum fields
-
- In the above example, if instead of translating asterisks to commas, translate both commas and asterisks to spaces.
- Choose space character as your delimiter:
-
- Start Of Record Event: “Numeric Character Received”
-
- End Of Record Event: “Carriage Return or CrLf Received”
-
- 4 fields/record. Delimiter is space character
-
- Result: Only lines with numeric data are processed (header and separator lines ignored)
-
- Start Of Record Event: “Numeric Character Received”
-
- End Of Record Event: “Special Character Received” (dash character)*
-
- Use Pre-Input Translation to convert line breaks to spaces
-
- Result: All 16 numbers become fields in a single record
How WinWedge Processes Your Data
WinWedge follows this sequence:-
- Waits for your defined “Start Of Record Event”
- Captures characters until “End Of Record Event” occurs
- Parses the data according to your Record Structure definition
- Applies any filters, math functions, or formatting you’ve configured
- Sends each processed field to your target application with defined separators
-
- Captures data from your scale, balance, gage, meter, sensor or other device
-
- Parses and filters the data according to your specifications
-
- Formats the output for your chosen destination (Excel, web forms, databases, etc.)
-
- Handles the data transfer without requiring programming or manual intervention