Maury MTune v2.0 Release Notes

The function getSparHarmonics() was only returning the s-paramters of the fundamental frequency.

Updated the TunXtIp, and TunXtUsb drivers to support the MT977AL, MT978AL, and MT979AL tuners.

Updated the PNAX driver to support magor firmware versions 14 and later.

In the Tuner Characterization Software (TCS), the “In-Situ System Cal” menu item now has updated wizard pages. The original wizard pages for reading the VNA calibrations are restored

In the Tuner Characterization Software (TCS), the “In-Situ System Cal” menu item now has updated wizard pages.

The reading of VNA calibrations are now all on one wizard page, and can the calibrations can be done and read in any order.

The setup page for the Adaptive Modeling method of tuner characterization has been updated with a simpler user interface, like the same dialog in the tuner characterization wizard.

Added MT981HL13, MT981HL14, MT981HL15, XT981HL13, XT981HL14, and XT981HL15 to the TunLxiIp, TunLxiUsb, TunXtIp, and TunXtUsb drivers

The API routine CalcGamma() returned incorrect results if harmonic tuning using a multiplexer was used.

The Tuning GUI (turned on with the setGuiState() API function), Control tab, was modified to show the Reference Z0, and the target gamma values are now based on that Reference Z0 instead of always 50 Ohms. This applies to the Tuning GUI only, not other API functions.

Added XT981ML01 to the tuner drivers TunXtIp, TunXtUsb, TunLxiIp, and TunLxiUsb.

The Tun1020C driver was updated to work with other non-Maury devices that use the same FTDI chip.

The VnaPnax driver was modified to work with the new Keysight ENA network analyzers.

A VnaPnax_VISA driver was added to control the PNA/ENA network analyzers using the VISA interface.

The PNA-X application using Maury tuners for noise parameter measurements, would give an error moving the tuner with certain tuner models.

With some combinations of multi-carriage tuners, the software would not tune to the desired impedances

The tuner drivers TunXtIp, TunXtUsb, TunLxiIp, and TunLxiUsb were all updated to work with either LXI or XT tuners.

The scan for tuners function in TunXtIp.exe was updated to avoid timeouts if the scan took longer than 10 seconds.

If the carriage order was set to “Carriage 1 Away from DUT” while the tuner model was a multi-carriage tuner, and then the model was changed to a 1-carriage tuner, tuning would produce an error message and stop.

In the tuner properties dialog, if the tuner model was changed, the properties were not immediately updated to reflect the new model selection

If In a swept adaptive tuner characterization, the frequency range crossed the crossover frequency of the tuner, the first point in frequencies above the crossover frequency would be recorded with the wrong position.

The scan for tuners function in TunXtUsb.exe was updated to include the specified Fmin and Fmax in the return strings.

In the Tuner Characterization Software (TCS), the “Calibrate->Combine Tuner Files” menu item will now allow multiple (more than two) files to be combined at once.

In TCS, a new menu item “Combine Version 5 C1,C2 tuner files" has been added to the Calibrate menu. This takes the carriage 1 and carriage 2 tuner files from TCS version 5 (part of MTune version 1) to be combined for use in TCS version 6 (part of MTune version 2).

Additional bugs in the Swept Adaptive tuner characterization point selection were fixed.

Nfm_897x.exe: modified the on-line check to recognize new models numbers that start with “”897”

Vna_CM.exe: fixed bug where sometimes a non-uniform frequency list was read incorrectly.

The Swept Adaptive tuner characterization did not measure any points if the entire frequency range was higher than the tuner crossover frequency.

Version 2 uses the new tuning object from ATS version 6.0 or later.

A multi-carriage tuner is now treated as a single tuner

The third parameter of the existing CreatePort() API function, tuningMode, is used slightly differently, since the new tuning object no longer has a tuning mode. However, it does have options for multiplexed harmonic tuning and prematching when multiple tuners or carriages are used. The following convention is adopted to be as close to backwards compatible as possible.

tuningMode = 1: This sets the option to use a multiplexer for harmonic tuning. However, this is only valid if all tuners on that port are single carriage tuners.

tuningMode = 2: This sets the option for the carriage closest to the DUT to be a prematch tuner for the fundamental frequency. This is only valid if there are at least two carriages on that port, allowing one to be a prematch, and the other(s) for general tuning. If there are three or more carriages, then the second and on carriages will be used for cascaded harmonic tuning after the fundamental prematch is set.

getCarriageInfo() – gets the number of carriages and the number of motors per carriage on a specified tuner.

getCarriageOrder() – gets the order or orientation of the tuner. The convention is the same as with setCarriageOrder().

getGammaHarmonics – gets the magnitude and phase of the current reflection coefficient vs. harmonics.

getSparHarmonics – gets the magnitude and phase of the current s-parameters vs. harmonics.

getTunerInfo() – gets information about tuner frequency ranges, number of motors, and motor ranges

getTunerPortVersion() – gets the version strings of the supporting TunerPort DLL and DriverManager DLL

setCarriageOrder() – sets the order or orientation of the tuner. Order=0 means carriage 1 is toward the DUT; Order=1 means carriage 1 is away from the DUT. This has no effect unless the tuner has multiple carriages.