Release Notes 2022.2

From RadiWiki
Jump to: navigation, search


We are proud to deliver you Version 2022.2 of our RadiMation® EMC Test software. This 2022.2 version is the result of several major improvements that we have done.

This letter contains all the information that is needed before your system is upgraded. If you have any additional questions or remarks please let us know through your reseller, or contact



When RadiMation® files are opened, changed and saved in a newer version of RadiMation®, it is possible that it will saved in a newer file format, which cannot be opened anymore in an older version of RadiMation®. To prevent that changed TSF, LLF, COR, SEQ or EUT files cannot be opened anymore in an older RadiMation® version, we strongly recommend to make a backup. Before you install the latest version of RadiMation®, please make sure to saveguard all your critical data.

Make a back up of (at least) the following files:

  • Correction files
  • TSF files
  • Sequence files
  • Limit Line files
  • Device driver configuration files

Multi version installation

It is possible to install different RadiMation® versions on the same PC.

This functionality can be used to verify the correct functioning of the RadiMation® software before it is used for EMC testing. Simply put, the functioning of the new version can be checked by comparing it with the older version. This verification can for example be required by internal quality assurance standards. During this verification process, the installation of the older RadiMation® version can still be used for all EMC tests.

Be advised that:

  • It is not possible to run two (or more) different versions at the same time without risking a software crash. Close other instances of RadiMation® before starting another version!
  • Raditeq cannot be held accountable if information is lost because two different versions of RadiMation® are used at the same time.
  • The user needs to have the rights as described in User rights and installation.


Installing software updates

Software updates can be distributed on CD or downloaded from the RadiMation® Download page.

To install the RadiMation® update from a CD, please execute the ‘SETUP.EXE’ startup program. The setup program will install the new RadiMation® version at the same location as the previous version, but in a separate installation folder. This will allow you to use the previously installed RadiMation® version, as well as the new one.

The setup program will detect that a previous version of RadiMation® has already been installed on your PC. A back up of this older version will automatically be copied to the backup directory. All the settings of the older version will also be used for the newly installed RadiMation®. If any problems should occur with the new software, the older version can be recovered.

Installing from a network directory

If the already installed RadiMation® version was installed from a network directory, the new setup file can be copied to the <Setup> sub-directory of the <NetworkDir>.

The new RadiMation® version can then be installed on each computer from this directory.

Updating device drivers

After the new RadiMation® version is installed, we strongly recommend that you install the latest device drivers as well. These device drivers can be installed by starting the ‘DRIVERS.EXE’ program that is located on the delivered CD.

The ‘DRIVERS.EXE’ program will detect the different RadiMation® versions installed on your PC. A dialog will start, asking you to select the RadiMation® version that needs updated device drivers. Select the latest version of RadiMation® that was just installed.

You have successfully obtained the latest released version of RadiMation® when both the software and device drivers have been updated.

Verification and Validation

Every new RadiMation® version is tested extensively before it is released. Raditeq validates these new versions on three ‘levels’. The fourth level of the validation is to be done by the end-user.

This quality management system follows the ISO/IEC 17025 standard (“General requirements for the competence of testing and calibration laboratories”).

1) Automatic knob pushing program

The ‘automatic knob pushing program’ simulates an end-user and is run on each RadiMation® version. The program performs all the actions that a user could do, such as entering information, executing tests, reviewing test results and generating reports.

Performing the first validation level is a responsibility of Raditeq.

2) Validation and usage in a test lab

Once the new RadiMation® version has passed the first validation level, it progresses to the second validation level performed by Raditeq.

During this validation the RadiMation® software is installed in a real test lab, to perform measurements on a 'known' EUT. These results are then compared to manual measurements to verify the quality of the software. The results are also compared with the measurement results of previous software versions.

Performing the second validation level is a responsibility of Raditeq.

3) Validation and usage in a test house

When the new RadiMation® version has passed the second validation level, it progresses to the third validation level performed by Kiwa Dare Services.

This validation level consists of two stages. In the first stage the software is used to perform measurements on a 'known' EUT. These results are then compared to manual measurements to verify the quality of the software. When the new software version has passed the first stage, it progresses to the second stage where it is installed and used by Kiwa Dare Services for at least two weeks. Any issues that are reported during this period, will be investigated and resolved. An updated version of RadiMation® is created if needed.

Performing the third validation level is a responsibility of Kiwa Dare Services.

When this validation is succesful, the RadiMation® version will be officially released, and will become available for all end-users.

4) Validation by end-users

Once the new RadiMation® version has passed the third validation level, it progresses to the fourth (and last) validation level, which should be performed by the end-users of RadiMation®.

When end-users receives a new RadiMation® version they should perform a validation of the software in their own test setup. The parts that should be validated by the end-user are:

  • Correct control of the used measurement equipment
  • Validation of the software according to internal quality standards
  • Possible verification and comparison of measurements on a 'known' EUT

We strongly advise to only start to use RadiMation® after this validation is performed.

Performing the fourth validation level is a responsibility of the end-user.

Solved items

See below the list of all the issues that have been solved in RadiMation® version 2022.2 since version 2022.1

RadiMation version 2022.2.7

  • #13643: Name of new sub-folder in TSF selection window is lost

RadiMation version 2022.2.6

  • #13409: Add reseller MDL Technologies
  • #13430: Data lost from perfomed tests (Conducted emissions) in February
  • #13471: graph scaling persistable error on start up of RadiMation

RadiMation version 2022.2.5

  • #4902: Device driver of RadiSense should raise a specific error during the Check if the laser is not activated
  • #5723: LOCAL command is send to RadiSense 4 with direct to PC communication
  • #11717: EC_OperationTimeOut and EC_RADIPOL_WARNING_BATTERY_LOW use wrong constants
  • #11736: Improve Logging of the RadiPower Set<-->ModulationConfiguration() functions
  • #13169: Rohde & Schwarz ESRP 7: VI_ERROR_TMO: A timeout occurred
  • #13210: AR 200S1G4 & AR 200S1G6 Interlock state is not detected
  • #13271: clsSettingCalculatedFieldParameters::CompareTo is incorrectly implemented
  • #13282: Correction file for Reflection Factor for antenna is not described in manual
  • #13295: Order: Quatest 2 - Quality Assurance and Testing Center 2
  • #13306: RTE1024 setting a negative start frequency results in data out of range error
  • #13328: Configured power for the minimal stepdown performance in SB is limited to 0.1 db
  • #13358: Index out of range when populating the combobox for the AD-Converter selection of the monitoring input window

RadiMation version 2022.2.4

  • #6725: Default configuration of the RPR powermeters
  • #6783: RadiField Polarization driver should have 'ignore height change' checkbox disabled
  • #7358: Strange dBm formatting is included in RadiGen error message
  • #10178: Application note 121: Using a RPR powermeter stand-alone with RadiMation® free version
  • #10263: Questions doing IEC 61000-4-3 with a RadiCentre CTR1009B that has 4 RSW1921N modules
  • #10287: FieldProbe RSS1004A: Not able to set filter
  • #12876: Device driver: Bonn amplifer - bonn 0830-250/100/60D - 3 bands
  • #13087: Changing the individual directory configurations does not result in remembering the new directory.
  • #13106: USB Dongle not detected
  • #13119: ESD: Test passed icon is set to fail while the test has been passed
  • #13121: The duplicate button on the sequence overview cannot be used when selecting multiple TSF files.
  • #13134: Report generator, expected harmonics and compression data is not exported after upgrading to a newer version.
  • #13137: The note button of a graph in the RI Fixed power result window is not working.
  • #13139: Directory is not stored after changing it in the configuration.
  • #13156: mk-messtechnik motion detection doesn't detect all alarms correctly
  • #13173: Turning modulation off for a RadiGen only turns gated pulse modulation off, but leaves pulse modulation on
  • #13184: Monitoring input channel Setup error.
  • #13194: Which receiver settings are used when measureing the voltage in CI MB using spectrum analyzer
  • #13197: Latest firmware version of RadiSense plugin in RadiCentre is not correctly detected
  • #13199: AR250W1000B Interlock not detected
  • #13208: SURGE: Deleting a sequence from the sequence list results in the order of the sequences being changed.
  • #13219: ESW44 initialization error
  • #13220: No measurement during antenna movement when an INNCO CO3000 antenna tower is used
  • #13225: No polarization control on Frankonia FC05 possible
  • #13227: -200 execution error when selecting a new LISN line after the analyzer has been reset due to loading a new test site with another "instance" of the analyzer driver
  • #13237: Fluke 8845A performs measurements in auto ranging mode
  • #13245: Include predefined sizes of several horn antennas
  • #13246: Driver: ETS-Lindgren probe polariser
  • #13247: Add reseller: Nanjing Rongxiang Testing Equipment Ltd.
  • #13263: Configuration Directory cannot be changed
  • #13265: Configuration Directory of RadiMation cannot be changed
  • #13268: Signal Generator error

RadiMation version 2022.2.3

  • #12600: Frankonia FC06.1 Antenna mast 1 polarization change still has problem in changing polarization
  • #12928: Test equipment Monitoring tab Add/Edit/Delete buttons are not correctly placed
  • #12933: Pressing cancel on the advanced option password prompt results in an invalid password error
  • #13004: Check version number of LAN controlled RadiCentre
  • #13011: Driver: COM-POWER ARI-6000-100
  • #13012: Driver: COM-POWER ARI-1000-200
  • #13013: Driver: COM-POWER ACS-250-100W
  • #13014: Driver: SIGLENT SSG3021X
  • #13015: Driver: Anritsu 68369A
  • #13016: Driver: COM-POWER LI-3P-232
  • #13017: Driver: COM-POWER AC-220
  • #13018: Driver: COM-POWER AB-900A
  • #13019: Driver: COM-POWER AL-100A
  • #13020: Driver: COM-POWER CLA-150A
  • #13021: Driver: COM-POWER PAM-103
  • #13022: Driver: COM-POWER PAM-103
  • #13035: Resolve compile errors of device drivers when using C++17 compiler settings
  • #13036: VisaBase::GetUsedVISACommunication returns another response than expected when VXI-11 is used
  • #13059: The control of the Frankonia FC06.1 controller is not working
  • #13085: Configuration dialog of R&S NRT powermeter driver raises a wxWidgets Debug Alert
  • #13104: How to export standards data in the report generator.
  • #13107: Controlling the Schwarzbeck TK9420 LISN raises an 'Unknown SetValueID'
  • #13222: EUT file doesn't show the list of performed tests
  • #13224: New Driver for Bonn BLWA 0830-250/100/30D doesn't work
  • #13244: Auto detect does not find Keysight MXE N9038B
  • #13254: Test data is not exported when using a WHERE clause in SQL report generator keywords

RadiMation version 2022.2.2

  • #4601: Report, view and compare improvements for CAL files
  • #5742: Determination of % out of 6dB error after UFA calculation
  • #5936: Possibility to generate a report of a calibration with Report Generator
  • #8586: Milmega 80RF1000-175 amplifier is not switching.
  • #9626: Driver: ETS-Lindgren 2090
  • #12686: Wrong test level if order is tick checkbox/change testlevel.
  • #12765: Extend Uniform Field Area (UFA) calculation to include statistical information
  • #12767: Calculate statistical information of UFA calculation.
  • #12769: Show the result of statistical information of the UFA calculation on the UFA result window.
  • #12770: Include report generator codes to include Statistical information in the report
  • #12771: Update standard printout of UFA calculation to includes the calculated statistical information:
  • #12861: Milmega 80RF1000 does not switch.
  • #12957: The Note and Units buttons are not shown on the UFA result window.
  • #12988: The maximum tolerance of the UFA calculation is not shown if it is all below the accepted tolerance
  • #12989: Wrong unit is shown at maximum deviation frequency on printout of uniform field area calculation.
  • #12996: Reading a binary block buffer results in a time out when using VISA Socket communication
  • #12999: N9322C Fails
  • #13000: N9322C Fails
  • #13002: Remove code related to HP3478A from Fluke 8840 driver
  • #13003: Show the number of device drivers on the RadiWiki website
  • #13092: Can the QP detector value be shown in the peak table if the QP detector has been used in the measurement?
  • #13094: Columns hidden from the detected peak table are still shown in the report

RadiMation version 2022.2.1

  • #512: Ability of auto detection of all connected equipment
  • #4517: Auto detect connected Radi-xxx equipment
  • #5750: Improve the printout template of UFA calculation
  • #6170: Add support for IEC 61000-4-16: conducted immunity: common mode disturbances in the frequency range 0 Hz to 150 kHz
  • #6769: Improve detection of Radi-products
  • #12766: Add report button to the calibration result window
  • #12768: Add configuration options for the statistical information to the UFA calculation configuration dialog
  • #12816: Attenuation gain system calibration does not report the calibration level when opening the .CAL file
  • #12920: Switch to new text generation engine.
  • #12948: The dropdown list with pre-filled tolerances is unlogical
  • #12949: The red maximum error line in the UFA graph should be using the value as specified for the accepted tolerance
  • #12950: Accepted extended tolerance should not be smaller than accepted tolerance
  • #12951: Also include an 'Extended maximum error' graph to the UFA calculation graph
  • #12952: Selected template and report filename are not remembered after report is generated for UFA
  • #12954: A default filename and location for the report of a calibration file is not provided if the TSF file of the UFA calculation was not saved
  • #12955: Unclear what the numbers on the UFA calculation result are indicating
  • #12956: The maximum deviation of the UFA calculation is shown with too many digits
  • #12958: Optimized UFA calculation drops unexpected points

Known Problems

R&S spectrum analysers/receivers communication problems

It has been detected that on very fast PC’s, the communication with modern Rohde & Schwarz spectrum analyser/receivers can be corrupted. These problems are related to the speed of the PC and the used GPIB bus. The R&S receivers that are related to this problem are: ESI/ESIB/ESPI/ESCI/FSE/ESU.

We strongly advise that you slow down the GPIB communication speed between the PC and R&S receivers. Follow these steps to do so:

  1. Open the configuration window of RadiMation®
  2. Select the Device Drivers tab
  3. Select Receivers/Spectrum Analysers
  4. Select the R&S receiver
  5. Press Edit to open the device driver configuration window
  6. Press the Advanced button
    • The GPIB configuration dialog of the R&S device driver will be shown
  7. Activate the Show advanced Settings checkbox
    • The GPIB Configuration dialog will show a Wait time box
  8. Specify 3000 us in the Wait time box
  9. Close all windows, and repeat these steps for each and every R&S receiver.

Configuring the R&S device drivers in this way will slow down the GPIB bus, by ensuring that at least 3 milliseconds delay are included between each GPIB call to the R&S devices

Previous RadiMation® version raises a run-time error

If the latest RadiMation® version and an older RadiMation® version are installed on the same PC, it can happen that the older RadiMation® version raises an error during the start of RadiMation.

This error is raised because a file that is shared by both versions is written in a newer file format that cannot be read anymore by older software. The solution for this problem is to remove the file: C:\Program Files\DARE Development\RadiMation\Confdvdr\CUSTOMIZ.DAT. The CUSTOMIZ.DAT file is used to remember customizations of the colour of the graphs, so removing the file will not influence the measurements. However the graph colours will probably be changed to the defaults as specified by RadiMation®.

Windows 8, Windows 7, XP, Vista and older are not supported

Due to the fact that Microsoft has ended their support for these versions we are also forced to stop the support of RadiMation® running on these operating systems. This means that we do not test if RadiMation® is working correctly on these operating systems. However it could be that RadiMation® is still working correctly. We strongly suggest upgrading your operating system to Windows 10 (21H2). Both the 32-bit and the 64-bit versions of the Microsoft Windows Operating system are supported.