Release Notes 2022.3

Introduction

We are proud to deliver you Version 2022.3 of our RadiMation^® EMC Test software. This 2022.3 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 2022.3 since version 2022.2

RadiMation version 2022.3.9

• #13750: Order of the columns in the detected peak table is not maintained
• #13757: Field strength graphs are sometimes shown without the correction data
• #13773: Field strength graph is not shown correctly, seems like field probe correction is not applied
• #13787: S-Parameter test form does not show the Raditeq Q-logo

RadiMation version 2022.3.8

• #13201: Device driver: Keithley 2700
• #13242: Teseq PMU 6006 gets error during testing
• #13486: Communication issues with rotational probe positioner
• #13514: Antenna tower is moved when the amplifier linearity test is started
• #13518: Field Sensor measurement result was 0 V/m.
• #13533: FPC Fix incorrect measurements when measuring parallel detectors during the final measurements
• #13537: Radimation data storage error during test
• #13566: RadiSense 10 returns 0.0 V/m on all axis
• #13568: Which RBW is really active during the sweeps
• #13569: SAC10 - Radimation 2022.2.3 Error message at startup "Acces to the path 'C:\TSFDIR.INI' is denied."
• #13573: TDEMI G supports multiple input ports
• #13622: Object reference error when closing emission test

RadiMation version 2022.3.7

• #5616: Changing RGN output is not correctly updating frequency range
• #9965: Closing Powersensor mini-circuits PWR-SEN-6GHS panel from 'Devices' crashes Radimation
• #10330: Controlling the Mini-circuits PWR-SEN-6GHS from different threads causes crashes
• #13270: Driver: Specialized device driver for the Fluke 8845A
• #13307: Driver: Extending the RadiPower 4000 series driver to 4 kHz with additional filters
• #13340: Mini-circuits power meter PWR-SEN-6LRMS does not work
• #13387: Printing a test result, results in a word error, file not found.
• #13391: Changing the polarization of the Frankonia FC06.1 results in an error -101
• #13395: Implement blocking print call
• #13417: Configuring the Customer Database returns "This is not a valid Device Driver"
• #13423: Error after disabling graph lines in an immunity graph
• #13424: ESRP keeps max hold on screen on the device while frequency was changed
• #13430: Data lost from perfomed tests (Conducted emissions) in February
• #13431: Improve *IDN? check of RadiField 1000-series
• #13438: No error description available when device not found
• #13440: Cannot find devices using Auto detection
• #13442: Rhode&Schwarz BBA100 Interlock
• #13445: Wrong current measurement with 34465A multimeter
• #13452: Rigol RSA3030E-TG firmware not supported.
• #13453: Label impedance has caption: Caption, in S22 result.
• #13454: R&S FPC1500 Average measurement does not work.
• #13465: Span error in GTEM Single band test with Rigol DSA832
• #13466: EMPower 7002-008 reports it can be used from 9 kHz
• #13468: Keysight IO Suite reports that a VXI-11 communication is a TCPIP stream, causing errors when setting VI_ATTR_TCPIP_KEEPALIVE
• #13469: The file property information of VISA32.DLL should be logged in RadiLog
• #13471: graph scaling persistable error on start up of RadiMation
• #13476: R&S FPC1500 Decvice check fails on drivers 2023.03.08.1406
• #13479: R&S FPC1500 Take sweeps after final measurement is done on wrong frequency span on analyzer
• #13480: Error when disabling all graphs
• #13488: Timeout errors GPIB: EABO
• #13490: Overshoot of polarisation change of the Frankonia FC06.1 is not corrected
• #13494: Changing note content created at a different moment will result in saving an additional newline character
• #13495: Correctly load the user correction into the RadiSense 10 probe
• #13496: SMB100B driver accepts 4 kHz FM DEV, but warning messages are presented on the screen of the device.
• #13530: RadiSense 4 returns 0.0 V/m on all axis

RadiMation version 2022.3.6

• #13353: Automatic ticket creator e-mails are not send or are received delayed
• #13365: Remove version from resource XML tag in wxWidgets XRC files to prevent warnings on start up
• #13367: Error without description VISA: --> Timeout expired before operation completed
• #13371: RI Test stops initialization at amplifier initialization.
• #13374: Changing the configuration directory does not result in restarting RadiMation
• #13379: Possibility to ignore UNCAL error ESPI3
• #13380: Text in textbox is not replaced in word report
• #13381: When using the report generator code InsertFile an extra new line is added after the inserted content
• #13382: WPF8 + SMP2 probe does time out when requesting field
• #13405: Report generator attempted divide by zero
• #13429: R&S BBA150 Amplifier system (3 stages within 80-6000 MHz)
• #13446: Changing measurement parameters used by the analyser as power meter drivers
• #13447: Could not find visa32.dll
• #13460: Problem with Rigol DSA832
• #13362: DSA832 Error about span
• #13484: Field strenght polar plot does not dynamically scale as expected
• #13485: Add AR 75A220M3 amplifier driver
• #13486: Add AR 200W1000M3A amplifier driver
• #13491: No trace visible in Radiated Emission. (using the HP 8542E)

RadiMation version 2022.3.5

• #11073: Wrong display of "Field 11 V/m AM" for Horizontal RI Test
• #11642: Calibration file of horizontal is also used for vertical polarization of the second band
• #11895: Calculated field calibration file of the first band is used in the calculations of the other configured bands
• #12480: RI multiband measurements (V+H) - Deviation in calculated test level
• #13258: Configuring a multiband test with multiple bands testing on different polarisations result in incorrect measurement results
• #13260: Report generator error 'System.OutOfMemoryException'
• #13308: Relay Unit SC1000 not switching
• #13330: Communication error with LSProbe 2.0
• #13335: Report generator does not replace expected keywords compared to previous versions.
• #13338: The axis of the Lumiloop LSProbe 2.0 are reported in a different order
• #13342: HI 6153 raises error 3
• #13344: Raditeq driver shows ETS identifier in settings.
• #13345: Driver: Keysight U2021XA
• #13348: Driver: ETS 7002-008.
• #13352: RadiMation does not use the correct RBW when performing the final measurement.
• #13355: Rename reseller Nortelco to Adeptor AS
• #13359: Error no average probe is selected
• #13361: Word report: correctly handle text in bullits and headers
• #13363: Report generator does not insert data of a valid keyword when table data is inserted into another table
• #13386: Error while reading binary data from Rigol DSA815.
• #13412: RI multiband .Cal file File does not exist error loading an existing file.
• #13416: Report generator does not insert expected data.
• #13420: End Frequency is too high for the selected equipment
• #13439: Auto detection of Radi-products does not seem to work as expected

RadiMation version 2022.3.4

• #13331: Opening radiated immunity tests shows the peak table tab while no peaks are detected
• #13321: Report generator outputs table data with a precision of 13 digits
• #13316: Init on AR75A400 amplifier hangs.
• #13315: RTO1024 Data out of range error channel 2
• #13313: Incorrect data transfer for HP 8564EC analyser
• #13290: Increase the size of the correction file selection control to be able to show 5 correction entries
• #13171: Play a tone during the dwelltime

RadiMation version 2022.3.3

• #13332: communication error R&S ESR and radimation
• #13287: Report generator outputs table data with a precision of 13 digits
• #13253: No RadiWiki page is available for the error message of a RadiCentre
• #13234: Rohde & Schwarz ESR: data out of range settings the measurement time
• #13192: Auto detection of cards in an ETS-Lindgren EMCenter is not working
• #13189: INNCO CO3000 starts rotation to a random angle during the initialisation
• #10997: Include description of all the tabs of the configuration dialog of the RadiPower on the RadiWiki website
• #5934: 2 graph buttons on the Triplate Information window are not working
• #5025: RDM1004B (RadiCentre) probably an unknown RadiMation Error

RadiMation version 2022.3.2

• #13223: Adding a row in correction file does not show the new row
• #13010: Driver: COM-POWER AMTTC300 (turntable)
• #12947: RadiMation slows down the PC after updating

RadiMation version 2022.3.1

• #13320: Graph of amplifier compression is not scaled correctly
• #13221: Kan COM-object van het type System.__ComObject niet converteren naar interfacetype DevExpress.Utils.DirectXPaint.ID2D1DeviceContext.
• #13207: mutex error
• #13183: Improve label layout in antenna scan
• #13148: Update DevExpress to 22.1.6
• #13099: Update nuget packages
• #13073: Update DevExpress to 22.1.5
• #12972: Test status of a Conducted emission test is not set to Fail if one or more peaks are failing
• #12909: Generation of report is too slow
• #12649: Possibility to use logarithmic scaling on the Y axis needed for DO-160
• #12279: Limit line with gaps
• #11644: Update Crypto++ to 8.7.0
• #11355: Make it possible to not detect peaks between limit line gaps
• #10772: Treshold is evaluated with the unmodulated signal.
• #4430: Possibility adding 'don't care' ranges in LLF
• #4253: Easy implementing several limit lines CISPR25

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.