Support Articles — MadgeTech 4

Wind101A – Wind Units Set-Up and Troubleshooting

Posted on

The Wind101A comes programmed with an engineering unit to provide the average wind speed using a 10 second reading rate. If a different reading interval is desired, a different engineering unit must be created to properly scale pulses to wind speed.

Note: these instructions assume that the Comptus anemometer from the Wind101A kit is being used.  If it is any other sensor, the instructions for setting up the unit will be appropriate, but the scaling (gain/offset) will be entirely different, and should be determined based on the sensor manufacturer’s output specifications.

For most users and applications, better results (and certainly better battery life) can be acheived by slowing down the reading interval.  This leads to a better idea of average wind speed rather than just gusts vs. no wind.  For example a 1 minute reading interval is still reasonably granular data, without being quite so noisy, and is much better for battery life.

The larger chart below on the right hand side shows the majority of selectable reading intervals/rates, and the corresponding Gain to use when setting up an engineering unit.

There are two ways to create an engineering unit for Pulse loggers.  The first is based on the older method of doing engineering units, where the “rate” was based on the reading interval.  The second is based on the new functionality of creating an engineering unit that IS a rate, so it will work with any reading interval by recalculating the engineering unit on-the-fly.  The first method is conceptually easier and only creates a single unit, but cannot be used for other reading intervals. The second may create some slight confusion in that rate units will also create multiple additional units for different rates (per second, per minute, per hour, etc.) but is more flexible if different reading intervals will be used.

To create the engineering unit for the previously recorded data:

(Note: These instructions use an assumed 60 second reading interval, but the gain and description for a different reading interval can be used if desired, based on the information in the chart above)

  1. Click the Engineering Units button on the Device toolbar.
  2. Click the Add button, which will results in cleared fields for a new unit.
  3. Name the unit MPH (60s)
  4. Change the Reference unit to Pulses
  5. Leave the Destination unit on (Custom)
  6. Change the Description to MPH (60s)
  7. Change the Label to MPH
  8. Change the Gain to 0.0142361
  9. Click Save
  10. The unit is now in the list of available engineering units.

Entering via this method also calculates the High scale point automatically, to make it the same as the Gain.  The number could have been entered in as a high scale point instead for the same results, as it would have calculated it as the gain.  Since 0 is still 0 both before and after scaling, there is no offset.  This is essentially saying that every pulse is equivalent to 0.0142361 miles per hour, at a sixty second reading interval.

Use this same method to create a different engineering unit different intervals, using the gain information in the chart above. 

The second method is to create a unit that is a rate.

  1. Click the Engineering Units button on the Device toolbar.
  2. Click the Wizard button.  Read the instructions and click Next.
  3. Select No, just create a unit.
  4. Select Pulses, then click Next.
  5. Select My unit is a rate
  6. Name the unit MPH
  7. Change the Pulse interval to Second (minute or hour could also be used, if you selected the corresponding gain from the chart)
  8. Change the Destination Unit to Miles
  9. Change the Unit interval to Hours
  10. Click Next
  11. Click Gain and Offset
  12. Change to Gain to 0.8541667 (the gain for 1 second in the chart below, based on the Pulse interval we selected above)
  13. Click Next and Close.
  14. The unit is now in the list of available engineering units. When selecting the engineering unit in a report, the other rate intervals (per minute, per hour) have also been created automatically and can be selected.

After creating the unit, in an open report right-click on the Y-Axis (unit axis) and select the new engineering unit.

If only a single reading interval, and single engineering unit is to be used, it can also be applied to the logger in the device’s Properties screen, in the Engineering Units tab.

Save and Share Reports

Posted on

The standard method of saving reports is to save to the MadgeTech 4 internal File Database:

  1. Open a dataset as a Graph, Data Table, or Statistics report
  2. Go to File – Save
  3. Select a Report folder or subfolder within the File Database as the save location

To save reports as individual files outside of the software, which can be shared, use the following method:

  1. Originating PC opens a dataset as a Graph, Data Table, or Statistics report
  2. Go to File – Save To – File to save in the MadgeTech File Format (.mtff/.mtffs)
  3. Save the file or send the file as an email attachment
  4. Viewing PC receives the file and saves to PC
  5. In the MadgeTech 4 software, go to File – Open
  6. To save a report, go to File – Save
  7. To save a report and a dataset (raw data) to File Database, go to File – Save To – File Database.  (Saving in this manner saves the original data previously downloaded on a different PC)

To share files in MadgeTech 4 Secure Software, all PC’s require a Secure Software license.  Please contact [email protected] to purchase additional software licenses.

MadgeTech 4 will not open

Posted on


If the software will not open, this may be due to an issue with the specific version of the Microsoft .NET framework on the user’s PC.

When Microsoft released .NET framework 4.5, it had a bug that prevented a lot of software packages—including ours—from running properly.  They have since released 4.5.1, 4.5.2 and other subsequent versions, which work fine with our software. Updating is only required and recommended, if the computer specifically has .NET framework version 4.5.

Go to Control Panel in the Start Menu and select Programs and Features.  Scroll down to the listing for Microsoft .NET Framework and check the full name and the specific version number.  If the installed version is Microsoft .NET Framework 4.5 (actual version in the right-hand column may say 4.5.50709) rather than 4.5.1 or 4.5.2, then that is likely the issue.  Note, the new 4.6.1 and later versions included with Windows 10 should be fine as well.

Microsoft has since patched this version to 4.5.1/4.5.2 as they inadvertently affected many small software companies like us.  .NET 4.5 changed a registry function that doesn’t work with our software or many other packages.

Linked below is the download page from Microsoft for 4.5.2, please download and install this new .NET framework, restart your computer, and then try running the software again.

If this does not solve the problem, please review the article “MadgeTech 4 will not open – DbProviderFactories error”.