Simple Data Logger just became significantly more powerful (and useful): You can now modify the regular expression used to match and capture data. Example: capture and record the net weight sent by a scale and ignore all other data.
Our free software 232key enables you to easily transfer the weight from your scale or balance to any application running on your PC (as simulated keystrokes). It contains a list of compatible devices that we are constantly expanding.
However, we cannot possibly test every scale or balance on the market. Using a practical example, this blog post will show you how to determine whether your balance is compatible with our software.
As of version 2018.1.0, the following requirements can be found on our 232key homepage (under “limitations”):
- Data sent by your device has to be in ASCII format.
- Your device has to send each line of data only once, not continuously (by pressing a key on the device or automatically).
These requirements may change in future version. We recommend that you always consult our 232key.com website first.
Step 1: Prerequisites
Scale or balance
You’ll need your scale, of course. For this example we used an Excell FD130 scale which we found among our samples:
At the time of the writing of this post, this scale did not have a predefined device profile in 232key.
It’s a good idea to try to find or download the user manual for your scale. As you’ll see below, you’ll most likely need it.
Your scale must be equipped with an interface which can be connected to a COM port on your PC (or appears as a COM port when connected). The FD130 has a DB25F port:
Cables and converters
We used a straight (1:1) DB25M to DE9F RS-232 cable with an FTDI US232R-10 converter plugged into a USB port on our PC:
Your scale will probably require a different cable. If you’re lucky, the user manual contains further information. We’ll address the topic of finding the right serial cable in an upcoming post (it can be quite complicated).
Serial terminal program
Step 2: Transfer the weight to a terminal program
Before using an unlisted device with 232key, it’s a good idea to get it to work with a terminal program. Just like 232key, a terminal program requires that you make a few settings before connecting to your scale:
- COM port
- Baud rate
- Data bits
- Stop bits
- Flow control (handshaking)
Only one COM port was shown on PC (created when the FTDI converter was plugged in). If you have the choice between multiple ports, consult the Windows Device Manager to determine the correct one.
We found the following interface parameters in the user manual of our FD130 scale:
- 1200, 2400, 4800 or 9600 baud (no default value was specified)
- 8 data bits
- 1 stop bit
- No parity
- No flow control
To determine the correct baud rate, we accessed the scale’s RS-232 configuration (we couldn’t have done this without the user manual):
After all settings were made, we pressed the “Connect” button in HTerm and immediately saw a lot of data coming from the scale:
The data contained a stability and net weight indication, a polarity sign, the weight and the unit, then a carriage return and finally a line feed character:
Setting “Newline at” to “LF” in HTerm made things a bit clearer:
Concerning the requirements mentioned above, we confirmed that the data was sent in ASCII format. However, the scale was continuously sending 4 values per second, which is not suitable for use with 232key as all these values would be typed (you could, however, use it with our Simple Data Logger application).
We again consulted the manual and found that the setting could be changed from “rnP 2 – continuous transmission” to “rnP 4 – press the ⏎ key to transmit”. As the description says, in this mode the user has to press the ⏎ key on the scale to send the weight to the connected PC (once).
Another mode suitable for use with 232key was “rnP 1 – stable transmission”. In this mode, the scale sent each (stable) weight once. This is often referred to as “auto print on stability”.
Your scale may or may not have several different transmission modes. Please refer to your manual for further information. Unfortunately, there are some scales which only support continuous transmission and are therefore not suitable for use with 232key (at this time).
No output at all
Unfortunately, there can be many reasons. Please read our extensive troubleshooting section on 232key.com.
No readable output
If the output in the terminal program contains no human readable data, you’ll have to fix this before trying to use the scale with 232key. As an example, setting the baud rate in HTerm to a wrong value (e.g. 4800) resulted in the following output (with “Show errors” selected):
If you’ve confirmed that all interface parameters in HTerm match those of your scale and still can’t read the output, the scale might not be sending data using the ASCII format. If no ASCII mode is available, it cannot be used with 232key.
Other values than the weight
Instead of sending only the weight as shown on the display, some scales send a lot of data to the connected PC. Below you can see the output when we set our scale to a ticket format meant to be used with a printer (“rnP 6”):
If the data sent by your scale contains numbers other than the weight, they will also be captured and typed by 232key. This is usually not what you want.
There are two ways you can try to fix this:
- Configure the scale. Refer to the manual to find out if it’s possible to change the output format to a more simple one that sends only the weight.
- If the line with the weight can be reliably identified (because it starts with or contains certain characters), you can use a custom regular expression in 232key Plus to capture the weight and ignore all other numbers.
Step 3: Use the scale with 232key
As we were able to read the output in HTerm and had fixed the continuous transmission issue, we proceeded to configure 232key for use with our Excell FD130 scale:We selected “generic measuring instrument” as the device and set the COM port and all interface parameters to the same values as in HTerm. As the terminator, we selected “LF”, the last character in each line of data sent by the scale (as seen above).
In the output tab, we instructed 232key to send an enter key after typing the weight (this is of course up to you and your application).
We then pressed the start button and switched to Word for testing purposes. By pressing the ⏎ key on the scale, the weight was typed by 232key:
Received data and captured/typed values could also be seen in the event log in 232key:
Further information and support
Please visit 232key.com to download our free software for scales and balances. Our website also contains an extensive documentation, FAQ and troubleshooting section.
Should you have any questions, please post them in our support forum. However, please keep in mind that the problem is not caused by 232key if you cannot see readable output in a terminal software.
We regularly publish blog posts with application examples. You can find all 232key posts here.
If a virtual keyboard wedge software like 232key is not what you need, please have a look at our other software. For data logging applications where you want to log the weight, time and date to a file, we recommend using Simple Data Logger.
Our software 232key was originally designed to make it as easy as possible to capture the weight sent by a scale or balance (and then transmit it to another application as simulated keystrokes). As most weighing instruments also include the unit and possibly other characters, 232key assumes that the first (decimal) number it encounters is the weight. If you also want to capture the date and time sent from a scale, this can lead to unwanted results.
Capturing the net weight
Let’s look at a simple example first. Below you’ll see the data received from an Ohaus Scout STX scale configured to transmit only the net weight (as it appears in the event log in 232key):
Net: 302.4 g ? N<13><10>
The blue characters were captured by 232key using the “Ohaus” device profile. In this example, 232key managed to successfully capture the weight.
Capturing the net and tare weight
If we set the scale to send both the net and tare weight, the event log shows that 232key still captures both values:
Net: 302.4 g ? N<13><10> Tare: 7.9 g T<13><10>
To have them appear in separate columns in spreadsheet applications like Excel, OpenOffice Calc or Google Sheets, we can go the output tab and modify the end with settings as shown below:
Alternating the “TAB” with the “Enter” key every 2 value will produce the desired result (shown in Google Sheets):
Capturing date and time
Things get significantly more complicated if we configure the scale to also send the date and time. The event log now looks as follows:
11/17/2017 15:04:21<13><10> Net: 302.4 g N<13><10> Tare: 7.9 g T<13><10>
Using its default strategy of capturing the first number in each line, 232key only captures “11” and ignores the rest of the combined date/time line (as the backslash cannot be a part of a decimal number).
We can try to fix this by going to the device tab and setting the device to “Barcode alphanumeric extended” (available in the Plus version). This device appears in italics, which means that it is a “text” device instead of a “numeric” device. Note: Do not click the set defaults button after making this change.
As the scale is now sending three lines of data, we should also enter the number “3” in the end with settings in the output tab:
If we press the print button on the scale again, the event log will show that all data has been captured by 232key:
11/17/2017 15:09:51<13><10> Net: 302.2 g N<13><10> Tare: 7.9 g T<13><10>
The output in Google Sheets looks as follows:
If we simply wanted to record all data sent from the scale, this would be fine. However, it is not ideal for further processing for two reasons:
- Date and time appear together in one column.
- The measurement values are not recognized as numbers because the cells contain additional text.
232key does currently not support extracting multiple values from one line of data, so there’s nothing we can do about the first issue. Unfortunately, our Ohaus Scout STX scale cannot send the date and time in separate lines.
The second issue can be fixed using custom regular expressions. To do this, go to the device tab, click on the customize button and replace the existing regular expression with the following one:
Note: This regular expressions assumes the scale is using the 24 hour time format.
The event log and the output in the spreadsheet now look as follows:
15:38:40 11/17/2017 15:39:01<13><10> 15:38:40 Net: 302.2 g N<13><10> 15:38:40 Tare: 7.9 g T<13><10>
The cells containing the net and tare weights are recognized as numbers and can be used for further calculations.
If we just wanted to capture the time (and maybe add a “date” column manually), we could use the following regular expression:
- The regular expressions above have been customized to work with the Ohaus Scout STX scale (configured to send the date, time and weight). They might not work with other scales and balances.
- As we’re now using a “text” device, the computation and rounding settings in the process tab have been disabled (you can’t round non-numeric characters).
- The option to change the decimal separator from a dot to a comma is also no longer available (and our custom regular expression does not capture decimal numbers using a comma as the separator).
- For data logging purposes, consider using our new Simple Data Logger software instead of 232key. It has the ability to add the date and time to each weight. The CSV files it produces can be easily opened in Excel and other spreadsheet apps.