Release Notes 2023.2

Introduction

We are proud to deliver you Version 2023.2 of our RadiMation^® EMC Test software. This 2023.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 radimation-support@raditeq.com.

Installation

Backup

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.

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 2023.2 since version 2023.1

RadiMation version 2023.2.6

• #12424: INNCO CO3000 firmware vesion 1.03.09 has problem with retrieving polarisation
• #13474: Drivers added for the EMI mode of the Rigol RSA3000-series and RSA3000E-series
• #13630: Added Possibility to configure the preselector of the TDEMI series
• #13811: Improved retrying to resolve Error 130 when controlling RadiPol antenna tower
• #13883: Fixes related to loading the advanced settings
• #13967: Enable alignment warnings for the N9038A
• #14112: N9010B Wrong RBW in Final Peak Measurement
• #14112: N9010B Wrong RBW in Final Peak Measurement
• #14146: Rigol analyzer returns unexpected results during BCI Calibration
• #14219: Rigol RSA-series analysers: Socket based communication on port 5555 now possible
• #14220: Possible to control Rigol RSA3030E on LAN port 5555
• #14221: *OPC? is also included in the RadiLog when TCPIP device stream is used
• #14241: RE TDEMI buffers a sweep taken before the pre-amp is state is changed
• #14257: Driver: AMP 2104
• #14264: Firmware version check for Rigol RSA3000E series is now checking on firmware version 00.01.04
• #14295: Unit not changing to dBuA from mA in CS114
• #14297: Gauss Instruments TDEMI controlled in spectrogram mode uses actually taken number of sweeps for second detector
• #14299: Fieldfox N9912A Check correct option values
• #14310: Driver Wavecontrol SMP 3
• #14313: Limit line must be enabled for the measured detector type
• #14316: Correct default TCP/IP port number is selected again when it is removed from the Ethernet address configuration
• #14316: Set the default port in the TCPIP communication string if it is removed during configuration
• #14317: More securely pass variables to multithreaded combine of correction files
• #14322: Extend configurable amplifier drivers to perform an additional optional read
• #14326: Changed description of the graph division settings frame
• #14329: Changing the 'max measure' in the powermeter settings is not possible using the keyboard
• #14341: Driver for adjustment of RadiField amplifier input attenuator
• #14342: Driver for advanced measurement values of RadiSense Ultra
• #14350: Keysight N9000: Fix Wrong RBW during final measurement
• #14357: Do not start the RadiField gain adjustment while this is already started
• #14370: Improved auto detection of actual terminator used by Raditeq devices
• #14376: SMF100A carrier is limited to minimum level
• #14376: SMF100A carrier is now limited to the minimal possible level
• #14377: Driver: R&S EPL
• #14379: Support the RS OSP B103 module
• #14382: Revert change which sends an unsupported command to the SMB100B related to setting the minimal carrierlevel
• #14399: Keysight N9000: Meter average detector is set in receiver mode
• #14409:Error in Av measurement during CE
• #14415: R&S ESRP: Correctly select the fixed attenuation value when the same as the auto attenuation value
• #14420: Increase the power measurement observation time of RadiPower when measuring AM modulation
• #14421: Requesting the average trace in the pre-scan results in unexpected data returned
• #14423: Rigol RSA3030E-TG is used in GPSA mode instead of EMI mode
• #14432: Improved initialisation time of a USB connected RadiPower RPR2006P
• #14433: Siglent generator time out problem when sending the OPT command
• #14448: Baudrate of RadiPower RPR2006 is not set again if it is already using that baudrate
• #:14471: Device driver message boxes should show the brand and description
• #14484: Power Meter Boonton 4220A not recognized
• #14491: Firmware update of RadiPower 4000 series does not raise an 'ERROR 1' anymore
• #14492: RadiPower driver waits until unit has finished restart after a firmware update
• #14493: Corrected typing error 'faling' to 'falling'
• #14509: Checking for updates raises a 'server cannot be found' error
• #14539: R&S SMC100A is always set to 0 dBm
• #14546: Error when controlling a R&S NRP connected to a R&S SMB100A
• #14550: Update version number checks in driver for RadiSense Ultra
• #14559: Low and High range selection for the Radisense 3018U
• #14560: TSF is not blank anymore after click cancel in sequence window
• #14585: Driver: Ceyear 1465-series and 1466-series signal generators
• #14586: Two dongles are now correctly supported
• #14596: RepGen: Possibility to reapply the table styles to a table
• #14603: Raditeq RadiSense RSS3018U: The range selection is by default hidden
• #14605: OSP B103 module does not remember selected state
• #14607: Generating a report using the RADICLI.EXE is only possible when the desktop client is running
• #14611: ESU40 Receiver does not return data when measuring bands with a 0 Hz span
• #14613: RadiSense 3018U: Do not request device specific inputs related to the laser temperature and current
• #14615: Radimation Closed after choosing multiple Files in EUT-Attachments Tab

RadiMation version 2023.2.5

• #13291: Read all trace data when multiple detectors are active for a TDEMI
• #13512: Error of invalid process is not shown anymore after SHIFT+Advanced click
• #13536: Radimation 2022.3.6 crashs after each test when using two dongles.
• #13764: SG386 pulse modulation
• #13813: RadiMation hangs at the end of the test when multiple dongles are connected to the PC
• #13920: Driver request: Stanford Research SG386 RF Signal Generator
• #14005: Rigol RSA series: Additional sweep is taken after QP detector is activated to allow to level to correct amplitude
• #14010: Problem with RadiMation and the polarisation of the Frankonia FC06
• #14064: Rigol RSA series: Additional sweep is taken after QP detector is activated to allow to level to correct amplitude
• #14111: Driver: ETS-Lindgren EMSense 7007-203
• #14117: Apply cable correction to the magnetic field calibration
• #14121: Driver: A-info DS-3100
• #14122: Driver: A-Info LB-OH-650-10-C-SF
• #14123: Driver: A-Info LB-2080-SF
• #14124: Driver: Aeroflex 2025
• #14125: Driver: Agilent Technologies 83731A
• #14126: Driver: A-Info 62EWGS-A1
• #14127: Driver: A-Info 90EWG3.5-T02-A1
• #14128: Driver: EMC Partner ESD3000
• #14130: Driver: Tekbox current probes
• #14131: Driver: Tekbox Bulk current injection devices
• #14133: MCU antenna tower position progress calculation issue
• #14136: Driver: Injection device: Schloeder EMCL-20 and Schloeder EMCL-35
• #14148: High attenuation required for measuring the fundamental results in upper harmonics being measured in the noise.
• #14149: Adjust drivers to use the correct name for A-INFO
• #14154: Rigol DSA832: Additional sweep is taken after QP detector is activated to allow to level to correct amplitude
• #14156: Can HTTP communication be used to retireve information from JSON
• #14160: Rigol DSG3065B does not support SYST:ERR?
• #14161: Textronix AFG3251C reports event messages as errors
• #14166: HI-6105 cannot save settings when pressing the OK button
• #14176: CWS500 as receiver does not work
• #14177: Object reference error opening Graph Export window
• #14186: Error when using RS PRO analyzer as power meter
• #14194: Data returned from Tektronix TDS oscilloscopes are calculated using 10 vertical divisions
• #14194: Improved selection of to be transferred waveform from older Tektronix TDS oscilloscopes
• #14195: Driver: RadiSense RSS2010M
• #14199: HP E4419A cannot be found because the identification string cannot be changed
• #14201: EMSense 7007-203 drivers
• #14218: Wrong settings are sent to the VDI device
• #14223: HP E4419A dual power meter error during zero operation
• #14224: Process (PID number) not found after closing Notepad
• #14225: Frankonia FC06.1 wait after height change to finish INIT procedure
• #14226: Manual EFT configuration does not indicate the unit in which configured values are expressed
• #14229: Driver: Tekbox TBMA4
• #14230: Driver: Tekbox TBL 5032-3
• #14232: Driver: Kalmus 320 FC
• #14233: Driver: Kalmus 711-FC-CE
• #14234: Driver: Teseq T800
• #14235: Driver: FCC-801-M2-50A
• #14236: Driver: FCC-801-M3-16A
• #14237: Driver: FCC-801-M5-16A
• #14238: Driver: EM Test ESD 30
• #14243: Driver: Prana N-MT500DC
• #14245: Magnetic field test according ISO 11452-8 time outs when using the Configurable multimeter driver
• #14251: Adjusted start frequency to 9 kHz of Raditeq GTM0250A, GTM0500A and GTM1000A
• #14255: Powermeter Fail
• #14256: Regulation of initial step of a non linear amplifier is now using the configured default gain
• #14259: HP4418 added option to enable the step detector and send the sense speed
• #14261: Raise error if the selected filter setting is not allowed for current RadiPower firmware
• #14262: Driver: Hameg 8135
• #14263: R&S SMH Allow configuring of 10kHz-2GHz range
• #14265: Standard socket port of the Rigol RSA-series is port 5555
• #14267: Fix Strange layout of stirrer configuration panel
• #14268: Select tuned mode as the default stirrer type
• #14275: Driver: Boonton 4220 powermeter
• #14287: Driver: IFI T188-50
• #14288: Driver: Klein+Hummel SA602 amplifier
• #14289: Driver: OPHIR RF 5041

RadiMation version 2023.2.4

• #5383: Implement 'Ignore height change' settings for the NCD AT
• #6879: Maturo MCU cannot ignore height change
• #9153: Average too high in Final Measurement sweep
• #9332: Final Measurement - average
• #12081: Average of phase is not correctly calculated when Phase is crossing 180 degrees
• #12150: AD-Convertor device driver as a Decorator around a spectrum analyser driver to measure AM/FM/Pulse-modulation
• #12236: Driver: Rigol RSA5065 to use multiple traces in EMI mode
• #12482: Support tracking generator on Rigol RSA5065
• #12797: Driver: Rigol RSA5065 EMI-Mode
• #12799: Rigol RSA5065 Tracking generator
• #13049: Driver: Siglent SVA1032X
• #13402: Measurement using Cispr AVG detector in the EMI-Mode of the Rigol RSA5065N
• #13602: I/O Error with Rigol RSA5065
• #13688: It takes long to open emission data files
• #13749: Report generator deletes grid found in template file when generating report
• #13772: Driver: Agilent 34410A
• #13844: Driver: Spectrum analyser driver for multimeter in CWS500N3
• #13857: Qpeak not visible in peak table after making adjustments to the peak table.
• #13883: Unexpected oscilloscope behavior in CS101 test
• #13987: Re-implement MCU antenna tower limits as pure software limits,
• #13924: The name or number of the point in the UFA calculation cannot be modified
• #13932: Differences in generated reports
• #13939: Include more logging during start of RadiMation to identify what causes startup time
• #13956: The last used graph exporter type should be remembered
• #13983: Environmental information is inserted as boolean value in RI printout reports
• #14000: Rigol RSA5065 Communication Error
• #14017: Driver: KRE 4000 extend with ethernet control
• #14031: RadiSense has invalid user calibration table.
• #14038: Implemented a change to not reduced the sweep time when the average or rms detector is activated for r&s esu based drivers like the esw
• #14041: It is not possible anymore to use a key on the keyboard to select an entry from a dropdown list
• #14053: RSA5065(EMI mode): RBW cannot be set to 9 kHz, changes back to 1 MHz
• #14054: AR FM5004 Driver issue with channel selection
• #14055: conducted emission in RSA5065 EMI mode
• #14058: RE MB QP missing in the table
• #14063: FA 7006 Issue with termination characters on legacy commands
• #14076: Hide the "Move antenna height" and Move distance" setting from the change order
• #14080: Driver: Siglent SSG5060X
• #14081: Radiated Immunity MB test is corrupt in 2023.2.3
• #14082: Plugin cards are not auto detected in RadiCentre Ultra 8
• #14085: Add Advanced option:"Emission.Multiband.Sequence.AllowPeakReview"
• #14086: Driver PMM 6630 does not handle *** correctly
• #14092: Improvement Amplifier linearity, remove 10dB Limit?
• #14095: Driver: ETS-Lingren 3166 & 3167 TEM Horn antennas
• #14097: Multiband GTEM not possible to configure the antenna distance
• #14099: Emission test using Rigol RSA5065 - Analyzer Reference Level not as defined
• #14100: RadiCentre returns VI_INP_PROT error when the expected response size is less than the actual response size
• #14102: Averaging of phase
• #14113: ESD Keywords are not working
• #14114: Repetition rate has no unit in report in EFT Report.
• #14116: More antenna steps in MB GTEM test results in unexpected results
• #14119: Turn table min/max positions are incorrect
• #14175: Antenna with Power Meter as "Field Probe"
• #14206: Change LumiLoop 2.0 calibration mode to put back the original settings after the test.
• #14207: Electrical Field could not be regulated to the desired test-level
• #14210: Improved auto attenuator selection on R&S ESW input 2 with pulse limiter
• #14211: DSG3065B raises error when am modulation is used above 3.6 GHz
• #14242: Time out error controlling the U2009A power meter
• #14249: EUT Controller TESTINFO doesn't work
• #14277: Error setting the sweep time while using the CAV detector

RadiMation version 2023.2.3

• #12894: OPC Driver does not work
• #13901: ESIB 7 error
• #13913: Extend Bonn amplifier driver to reset water cooling interlock error at retry
• #13925: The start position should be allowed to be higher than the end position of the X-orientation of the probe positioner
• #13926: The start position should be allowed to be higher than the end position of the Y-orientation of the probe positioner
• #13938: Change the x-position and the y-position generator to behave as an uni-directional generator by default
• #13951: Extend manual or add application note regarding usage of axis specific correction factors of field probes
• #13955: Add 4 steps as a default possible options for the XY positioner step count
• #13957: ESR TD driver has a resolution configuration which is not expected
• #13965: UFA Calculation not possible due to unspecified tolerance in calibration files - Field closed loop method
• #13966: Maturo NCD turntable time expired before operation completed
• #13978: Multiband: UFA calibration seems to regulate to an average field greater than the specified tolerance
• #13996: index outside the bounds
• #14011: Maturo NCD Turntable: Timeout expired before operation completed.
• #14012: EMPower 7002-009 010 option 010 not detected
• #14016: Extend the Maturo NCD Antenna tower to send the height with fractions.
• #14023: R&S ESRP3 Analyser has a default port of 7895 this should be 5025
• #14026: Amplifier Research FL 7006: Not all bytes are written to the GPIB-Board within the timeout period (GPIB: EABO)
• #14029: EN61000-4-3:2020 Constant Power method is interpreted as being constant field method in the UFA configuration dialog
• #14033: Driver: Raditeq GTEM RGT0250A, RGT0500A, RGT1100A
• #14049: Configurable Power meter clear input buffers before getpower.
• #14052: RSA5065(GPSA mode) is not switching to EMI mode for the final detector measurement
• #14067: Support RF mixer in front of Keysight N9020B MXA
• #14145: RadiMation cannot connect to the R&S NRP powermeters anymore

RadiMation version 2023.2.2

• #13849: Manual XY Positioner does not show message when first position is X=0, Y=0
• #13851: The tab order of the X/Y positioner settings of the field distribution is very unlogical
• #13584: The virtual X/Y-positioner has advanced configuration settings which is unlogical
• #13858: Setting start-x and end-x in Field Distribution configuration is not possible
• #13877: NGS3040 set default port configuration to 1025
• #13934: CTR1009B USB drivers

RadiMation version 2023.2.1

• #9240: Negative combobox values with unit distance (grootheid) are getting different smaller units (eenheden)
• #9241: Spin control of ctlsetting xy positioner comboboxes only checks closest allowed value when the unit is not centimeters
• #9243: BusyStatusBar of the xy positioner progression status displays the distances with the wrong units as extension
• #9832: Driver Maturo FPP2.3 Biaxial Positioner
• #12157: EN 61000-4-3:2020 is not mentioned in the UFA calculation window
• #13408: XY positioner parameters are reset during configuration
• #13411: The continue settings for the XY positioner only shows a selection for the X position
• #13502: Restrict usage of XY positioner using RadiMation Essential license
• #13503: Change the order of the XY positioner configuration controls
• #13504: Possibility to enter the positioner distances with millimeter accuracy
• #13505: Set the correct values for the XY positioner in the advanced settings
• #13506: Show and use the X position setting in the change order
• #13507: Show and use the Y position setting in the change order
• #13508: Separation of command generators, applicable settings and driver interfaces for the X- and Y-axis movement of a field probe positioner device driver
• #13510: Add switch matrix events related to the Y positioning of the field probe positioner
• #13511: Add switch matrix events related to the X positioning of the field probe positioner
• #13513: Show the antenna and antenna tower controls when the field distribution location type is selected
• #13631: Add a stop button for the manual mode XY- Positioner
• #13632: Parallel control of current, voltage, switch matrix and eut controller
• #13634: UFA calibration export tool
• #13736: EN 61000-4-3:2020 is not mentioned in the UFA calculation window
• #13741: IEC 61000-4-3:2020 specifies that the amplifier is linear if the 5.1 dB step results in a 3.1 to 7.1 dB change
• #13791: Calculate average and float unit test fails in VS 2022
• #13805: Calibration export tool file validators, keeps detecting already deleted cal files

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.