Release Notes 2024.1

From RadiWiki
Jump to navigation Jump to search

Introduction[edit]

We are proud to deliver you Version 2024.1 of our RadiMation® EMC Test software. This 2024.1 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[edit]

Backup[edit]

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[edit]

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[edit]

Installing software updates[edit]

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[edit]

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[edit]

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[edit]

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[edit]

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[edit]

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[edit]

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[edit]

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[edit]

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

RadiMation version 2024.1.6[edit]

  • #13074: Improve resolution calculation for the AFJ FFT3110 receiver
  • #14151: Improve multiple dongle management in RadiMation
  • #14258: Audivo Pecos 7.1 support
  • #14459: Add pulsed immunity sequence overview keyword to export sequence configuration to a table
  • #14695: Driver: Audivo Pecos 7.1
  • #14750: Improve detection of RadiMation license keys
  • #14868: Calibration file name creator now also has a test level description option
  • #14490: A report generator keyword which can output a test overview of an EUT in table format
  • #15058: CI calibrations use the same report functionality as the RI calibration document
  • #15063: Attenuation system test can now generate reports after the test is already performed
  • #15065: correctionfile copy-paste unit tests should not use the actual clipboard
  • #15085: Add pulsed immunity sequence overview report generator keyword
  • #15123: Update of RadiField firmware prevents bricking of the plugin card
  • #15132: License key is sometimes detected as Essential even though it is a Pro license
  • #15133: Software protection key error without valid license

RadiMation version 2024.1.5[edit]

  • #11944: Correctly maximize the PI ESD configuration window
  • #13818: Driver: Milmega AS0860-030D
  • #14537: Take additional 10% of the sweeptime for the rigol RSA
  • #14750: Improve detection of RadiMation license keys
  • #14873: Driver: Vectawave VBA230-25 amplifier
  • #14940: Do not re-enable the timer to measure inputs when an error occured.
  • #14960:How to use SQL queries to insert customized tables in reports
  • #14964: Add preamp status command to the PMM 9000 driver
  • #14966: Multiband testing datapoint are filterable under unexpected setting combinations
  • #14974: Prana N-DT310/220 amplifier can be controlled over ethernet
  • #14975: Control of Prana N-DT310/220 amplifier is now using RFON/RFOFF command set
  • #14976: Prana Ampliers can now be controlled by RS232 and USB port
  • #14978: Default socket port of an ethernet controlled Prana amplifier is set to be 23
  • #14979: Improved retrieval of actual status of ethernet controlled Prana amplifiers
  • #14980: Improved Ethernet communication with Prana amplifiers
  • #14988: Improved RS232 communication with the Prana amplifiers, resolving 'unknown system errors'
  • #14490: A report generator keyword which can output a test overview of an EUT in table format
  • #14999: Prevent inclusion of unexpected graphlines when a trailing seperator is added to the keyword
  • #15000: RS3018U Wait for laser to start when the device is reset.
  • #15022: Integration NI USB-6525 in RadiMation
  • #15024: Add range selection for the DT 310/220 amplifier
  • #15066: Do not show 1 Hz for generic messages in the event log
  • #15084: AutoDetectNewDriverWatcher does not report every created driver
  • #15093: Driver: Frankonia FPD-REM
  • #15105: Driver: Schwarzbeck CDN M5PE 32 A
  • #15107: Driver: RadiSense RSS2018S
  • #15114: RadiMation free cannot measure above 10 GHz in free mode
  • #15122: Improved handling of temporary files on the network

RadiMation version 2024.1.4[edit]

  • #14576: Communication improvements with the Boonton 4220(A) power meters
  • #14904: 10 second timeout is prevented when Maturo FCU clamp mover starts moving
  • #14944: Improvements to starting virtual instruments tests
  • #14951: Detection of available axes on a Maturo FCU controller is improved
  • #14952: measurement issue by using ESR 26 Spectrum analyzer input 1
  • #14956: Fix loading calibration files created in 2024.1.2
  • #14959: Detection of the state of the preamplifier of the PMM9010 is improved
  • #14965: Value of retrieved preamplifier gain is shown correctly in RadiLog
  • #14967: Application Note 159: How to create nicely formatted tables in a report

RadiMation version 2024.1.3[edit]

  • #12772: Application note 147: MIL-STD RE101
  • #13138: Objects used together must be created from the same factory instance
  • #13425: Fix error: Objects used together must be created from the same factory instance
  • #13651: Fix update of plugin card is not working correctly in a multislot RadiCentre
  • #13758: The progress of the software update of a Raditeq device is only running once from 0 % to 100 %
  • #13759: The dialog cannot be closed as long as the software update of a Raditeq device is busy
  • #13760: At the end of the software update of Raditeq device a messagebox is shown
  • #13761: During the software update of a Raditeq device a message is shown that the update is busy
  • #13984: Fix error Objects used together must be created from the same factory instance
  • #13998: Fix error objects used together must be created from the same factory instance
  • #14365: Loading previous Reverberation calibration files shows all the information again
  • #14483: 'Suggest an improvement' redirects to the RadiMation download page
  • #14498: Antenna distance exported from Multiband Calibration matches with the antenna distance used during the test
  • #14507: UFA calculation stores logarithmic step frequency into resulting CAL file
  • #14567: Add reseller ASTAT
  • #14589: Keysight E4446A factory preset type is set during the initialisation
  • #14617: Terminator is correctly skipped in binary response of Narda PMM600
  • #14620: CI system calibration does not allow to set a constant current with decimals e.g. 7.5 mA
  • #14632: Fix hiding controls on the virtual instrument window
  • #14633: Fix display of controls on Virtual instrument window
  • #14636: Fix auto triggering of RSS3018U is not performed
  • #14653: FSV40 correctly set the center frequency in final measurement mode
  • #14677: Driver: ETS-Lindgren HI-6023
  • #14678: Add reseller Comtest SRL
  • #14679: Check for system errors in NRT power meter driver
  • #14694: Log the new operation mode when it is changed
  • #14716: Software update can be be performed on Raditeq RadiSense Ultra
  • #14731: Add reseller Netscope RM
  • #14760: Fix Logging when directory configuration does not match CONFDVDR directory configuration
  • #14764: Update packages
  • #14768: Updates to assembly info
  • #14769: Fix amplifier initialisation display mismatch
  • #14772: Fix freezing when closing MB with open event window
  • #14773: Improve PMM9010 communication by clear communication buffers around commands
  • #14805: SRM3006 Correctly handle '\r' characters and use ';' as termination only
  • #14826: Fix object used together must be created from the same factory instance
  • #14855: A saved reverberation calibration file is not triggering a file corrupted error anymore
  • #14872: Do not show the stirrer in the signal generator list
  • #14884: More retries added to handle sudden disconnects and timeouts for Maturo FCU
  • #14890: Prevented deadlock in pulsed immunity multiband EFT test
  • #14899: Support for windows 10 enterprise LTSC 2019 x64 17763
  • #14917: Drivers added for Raditeq RadiPol RPL3001L, RPL3001H and RPL3001R
  • #14928: Resolved a problem that < 1 ms differences between different timing loops are present

RadiMation version 2024.1.2[edit]

  • #8756: Virtual Instrument amplifier window. Triangle button is not drawing a triangle
  • #12693: A correction file that is opened by a restricted engineer can still be modified by using TAB
  • #13711: Fix for error 'Error: Objects used together must be created from the same factory instance. (Exception from HRESULT: 0x88990012)'
  • #13819: Added EN61000-4-20:2022 UFA Calculation and TEM mode verification
  • #13826: Update to DevExpress 23.2.3
  • #13873: Driver: EMCO 5390 XYZ Positioner
  • #13916: 2 or more calibration files can be opened at the same time again
  • #13921: Show the default button in the Raditeq skin more distinctive
  • #13967: Keysight N9038A: Alignment status is not checked during test
  • #14150: Simplify selection of the type of the RadiCentre when a RadiCentre Ultra 8 is controlled
  • #14283: On/Off buttons should not behave as toggle buttons
  • #14315: Textboxes in word templates disappear
  • #14323: Driver: Rohde & Schwarz SMB100M
  • #14331: A readonly TSF file can still be saved by selecting 'Are you sure to replace it?'
  • #14354: Objects used together must be created from the same factory instance. (Exception from HRESULT: 0x88990012)
  • #14411: RadiCentre selection is always set to 'RadiCentre Ultra'
  • #14413: Raise warning when main template is used as test specific template
  • #14419: Returned value of SwitchHoldContinuousOff is always ignored
  • #14437: Error while measuring with R&S FPC1500
  • #14438: Objects used together must be created from the same factory instance
  • #14438: Objects used together must be created from the same factory instance
  • #14443: For RadiCentre devices when directly connected to the pc it is not possible to change the baudrate
  • #14443: Allow baudrate change for RadiCentre1 devices connected by RS232
  • #14444: No response from directly connected RadiPower
  • #14446: Error while clicking table
  • #14451: Fixed firmware check for the RPR2006C
  • #14453: Improve battery check speed for raditower
  • #14470: Error opening EUT calibration test graph "attenuation"
  • #14472: Implemented a check if the Maturo FCU is enabled and referenced
  • #14516: AR75S1G6C was not going to operate
  • #14518: No stirrer driver in test site in normal RI MB closed loop test
  • #14520: Amplifier not powering on
  • #14523: Allow internal and external AM sine and square wave modulation for the R&S SMF100A generator
  • #14547: Copying a limit line file table does not consider the unit when pasted into another limit line file
  • #14552: Not possible to copy and paste the address information
  • #14554: Driver does not read power anymore during zero operation.
  • #14564: Objects used together must be created from the same factory instance. (Exception from HRESULT: 0x88990012)
  • #14568: Objects used together must be created from the same factory instance. (Exception from HRESULT: 0x88990012)
  • #14583: RadiSense Ultra: Add hidden advanced ability to skip range selection
  • #14583: RadiSense Ultra should wait until probe is active after laser is activated
  • #14584: Agilent ESG-D (E4431B) is automatically switching int/ext reference.
  • #14590: Allow pasting correction data in units different from the receiving correction file

RadiMation version 2024.1.1[edit]

  • #12009: Support 64 bit time stamps
  • #14039: Switching band in a RI MB test using a stepper with a frequency list can be slow
  • #14134: Add antenna efficiency setting to all antenna device drives.
  • #14163: Objects used together must be created from the same factory instance. (Exception from HRESULT: 0x88990012)
  • #14269: Controls on reverberation calibration configuration window are incorrectly aligned
  • #14270: Description on the reverberation calibration configuration window is unexpected.
  • #14271: Add validator if 'allowed deviation' is selected
  • #14272: Add validator if at least one field probe input is selected
  • #14273: Add a validator if at least one testlevel is selected
  • #14274: Positioning of the field probe cannot be changed in the change order
  • #14278: 'Save Calibration As' dialog is shown if reverberation calibration takes longer than 5 minutes
  • #14281: Overflow is prevented when searching very large arrays
  • #14292: Allignment of radiated immunity related test configurations forms
  • #14320: Remove PropertyChanged events in settingbase class

Known Problems[edit]

R&S spectrum analysers/receivers communication problems[edit]

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[edit]

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[edit]

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.