> For the complete documentation index, see [llms.txt](https://wvu-neuromint.gitbook.io/neuromint-resources/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wvu-neuromint.gitbook.io/neuromint-resources/technical-guides/ohaus-ranger-3000-scale.md).

# OHAUS Ranger 3000 Scale

To connect the scale to the computer, you will first need a USB to RS232 serial cable. Currently (8/9/21), we have two such cables in the lab that should be stored with the scale.

![A USB to serial cable](/files/-MggtQsZAeoMCOuycCH1)

The cable mounts to a serial connector on the underside of the scale below the red cover.

Once you have the cable, you will need to download some program to read from the serial cable. This tutorial will cover the use of the program suite Windmill ComDebug.  

{% hint style="info" %}
[Download ComDebug here](https://www.windmill.co.uk/serial.html), then run the setup.exe file after extracting the folder.
{% endhint %}

From here, I will cover the needed steps for the different programs installed as part of ComDebug.

### ComDebug

![The start screen for ComDebug](/files/-MggvjbXr1EX4yEfAYvW)

This program will set up the actual communication through the COM port. To begin, click on the button next to "Create a new Windmill Instrument File". Select "Serial Communications" to get into the "COM Port Settings" window.

![](/files/-Mggz1hrb6YlpED1BFlW)

Here, define the COM Port as whatever the USB to serial cable is assigned to in the Device Manager. The rest of the settings are defined to match the settings of the scale.

To access/change these settings on the scale, follow these steps:

1. With the scale turned on, press and hold the "Menu" button.
2. Keep pressing the "Print" button until "COM" is displayed on the screen, then press "On/Zero".
3. Use the "Print" button to cycle to the various settings, then "On/Zero" to enter the menus.

Page EN-21 in the Ranger 3000 manual covers the COM menu for more detail.

{% hint style="danger" %}
If changing the Baud Rate, you also need to change the properties of the port in the Device Manager. To do so, follow these steps:

1. Right click on the port and select "Properties"
2. Under "Port Settings", change the "Bits per second" property to the Baud Rate you have set
   {% endhint %}

![The settings I have been using to take data from the scale.](/files/-MggwKithY_PiRNlfI5Q)

Once you have changed all of these settings, press "OK" to continue. This will take you to the Main Menu of comDebug. 

![comDebug Main Menu](/files/-Mggz_1vd6xudOktqa7Z)

If at any point you want to edit these settings again, simply press "Edit COM Port Settings".

The following tabs lay out the settings that need to be changed from this menu.

{% tabs %}
{% tab title="Editing data channels" %}
Press "Edit the data channel details" to define what variable(s) you want to store data under. In this case, we will be defining a Weight variable to store the value from the scale. I defined the different parameters as follows:

![Channel details for reading off of the scale](/files/-Mgh-gYX4RC_xY6qdYap)

If there isn't anything in the Msg category yet, don't worry; we'll define that shortly. Once you are done defining the channel, exit out of the window.
{% endtab %}

{% tab title="Editing instrument timings" %}
Press "Edit the Instrument Timings" to define the timings of how the program will get data. I've found that you really only need to change the "Data Persistence Time" to ensure that the program records changes at a decent time scale. 

![Settings to ensure speedy data update](/files/-Mgh12oi1IIwM_g7vf4H)
{% endtab %}

{% tab title="Editing message" %}
Press "Edit Message\_1" to edit the commands that the program sends to the scale. Name the message whatever you want here. First, define the Prompt values as follows:

![Prompt settings for the scale](/files/-Mgh2AN_EYiOgU5RjyrI)

To check if this is working correctly, press "Send" below the Prompt column. You should see a weight reading appear in the Reply column. 

Next, press the "Parse" button to change how the program parses the data for display. These are the settings I have used to parse the weight:

![Reply parser settings for the scale](/files/-Mgh2i0FkU23occ_OCCx)

If you're using other settings, you can check what each step is doing by clicking on the "Step" menu item while highlighting one of the steps. The sections of the reply that are being parsed by that step will highlight in green in the Message Edit window, as below.

![The portions of the reply parsed by Step 1 in the parser menu.](/files/-Mgh3OxkAF8fF_upcYCM)

To define the extracting step, click on the "Extract" menu item. It will then allow you to tie the data channel as the output of the message commands.

Pressing the "Close" button or exiting out of the window will set these settings.
{% endtab %}
{% endtabs %}

Once all of these settings are defined, go back into the "Edit Message" menu to check if everything is working correctly. From this menu, press the "Run" button to open the "Display Screen" menu.

![The Display Screen upon first opening](/files/-Mgh62XM7LFmrh04dOht)

From here, set the "Sample Rate" as the value you set the "Data Persistence Time" value to before (in this case 50 ms = 0.05 s), then press "Start" to start displaying real-time data from the scale.

Once everything is working correctly, go back to the Main Menu and press "Save .IMD File" to save this setup. In the future, you can then open this setup again in ComDebug by selecting "Edit an existing Windmill Instrument File" in the start screen.

### SetupIML

To use the other programs included with ComDebug, you also need to set up a .IML file. ComDebug only sets up a .IMD file. 

When opening SetupIML, choose to "Create new setup" from the menu that opens. Choose whatever name you'd like (I chose RANGER) and press "OK". 

![The main menu of SetupIML](/files/-Mgh8O6fNUzeSvN-2Dmh)

The .IMD setup you configured in ComDebug should show up here. Then, just save the file and exit the application.

### Windmill Logger

The logger allows you to display the readings off the scale in real time through the computer. Upon opening Logger, select "File > Load Hardware Setup". Locate where you saved the .IML file from earlier. The default location should be "C:\Program Files (x86)\Windmill Software\Windmill\SetUps".

Upon opening the hardware file, you will then choose which channels to connect to the logger. Find the channel you defined in ComDebug and move it over to "Connected Channels". You can change the connected channels at any time via the "Inputs" menu item.

![Connecting channels to the Logger](/files/-Mgh9s0SWUtBo8pg5zjr)

From here, the top menu items change the logger in the following ways:

{% tabs %}
{% tab title="Settings" %}
![The settings window of the logger](/files/-MghALhDShlNW8RlBHdo)

The settings window allows you to change the input read time, as well as how it displays the time stamps.
{% endtab %}

{% tab title="File Options" %}
![File options for the logger](/files/-MghAdt_lqrBOiOPA7DR)

The File Options menu allows you to change when/how the logger puts data into files.
{% endtab %}
{% endtabs %}

{% hint style="warning" %}
I haven't gotten the files that the logger saves to actually show up in the Data folder, so I generally just have the logger not save data to a file in the File Options window.
{% endhint %}

### Troubleshooting

#### Can't connect to the COM port when opening program.

This is likely because another one of the Windmill programs is using the COM port. To fix this, close all Windmill programs, including the IML Devices that will only show up on the Taskbar.

![The devices on the taskbar that also need to be closed.](/files/-MghByFvIvzZP0WwPmqp)

### Other Resources

[Ranger 3000 Manual](https://dmx.ohaus.com/WorkArea/showcontent.aspx?id=30234)\
[Capturing Data from an Ohaus Balance](https://www.windmill.co.uk/driver-ohaus.html)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://wvu-neuromint.gitbook.io/neuromint-resources/technical-guides/ohaus-ranger-3000-scale.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.