Release Notes 2015.2

From RadiWiki
Jump to: navigation, search

Introduction

We are proud to deliver you Version 2015.2 of our RadiMation® EMC Test software. This 2015.2 version is the result of several major improvements that we have done. This release is completely based on the Microsoft .NET development framework, which ensures that we can fully support future operating systems.

We include several improvements and new functionalities in version 2015.2, the most important improvements are:

  • Automated pulsed immunity EFT Burst testing
  • Automated pulsed immunity Surge pulse testing
  • Attachments on the EUT window
  • Several user interface and usability improvements.
  • Report generator fixes.

We trust that we have incorporated these new feature in such a way that it is useful for several customers that have been requesting these functionalities.

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 2015.2 since version 2014.3.

RadiMation version 2015.2.5

  • #470: No buttons present for often used operations
  • #510: No overview of of used equipment at start of a test
  • #940: Predefine which graphs should be shown on the screen
  • #3826: Show during measurement option in the graph line configuration window
  • #4162: automatically add and show the configured and selected ad channels in the graph window during an RI measurement
  • #4613: Calibration expire window should be a MDI client window
  • #4641: Switching between graph and table should rename graph button to table info
  • #5125: Closed loop measurements
  • #5527: Label of Show details button should become Hide details when details are shown
  • #5576: Driver: R&S OSP130 with option B102
  • #5607: Add "Save Calibration As..." possibility
  • #5661: Add Frequency range panel for Bonn BLWA drivers
  • #5678: Enhanced status window description of vertical and horizontal is not directly clear
  • #5985: ESR7 replies with error about AC_DC coupling on Channel2
  • #6020: Show all activated AD-channels by default in the graph during a test
  • #6027: Perform final measurements in EMI receiver mode with the Agilent MXE N9038A EMI receiver
  • #6036: Ability to enter manual information at each disturbance frequency
  • #6090: Start/stop time test fileds are not retained from 2014.2.12 to 2015.1.7
  • #6123: RadiMation is not responding when Amplifier Control window is enabled
  • #6251: R&S ESR7 specific System Error: -222 Data out of Range DISP:TRAC:Y:RLEV:0.0103DBM
  • #6270: Raise an error when R&S NRP-Z55 power sensor is disconnected during test
  • #6296: Device stream in the device driver system for http protocol using get and post
  • #6297: Driver: USB-xSPDT-A18 series switch matrix
  • #6299: R&S FSP30 spectrum analyser option for FFT filters
  • #6302: Driver: Tektronix RSA5100-series
  • #6312: Timeout in communication with R&S ESPI after QP measurement
  • #6321: Clear the input buffer of a configurable device driver directly after the connection is established
  • #6322: Not possible to specify the Escape character in the configurable device driver
  • #6323: Configurable switch matrix device driver sends the 'Turntable Changed' command before the turntable starts moving
  • #6337: Turning off Pre-amplifier option (INP:GAIN:STAT OFF) without this option being available is raising an error for the R&S FSV
  • #6340: No Unit is shown for test level
  • #6343: Ability to disable determination of the dynamic range during the Attenuation / Gain system calibration
  • #6345: Carrier Level command of the Configurable Signal generator is not transmitted if no Carrier On command is specified
  • #6349: Driver Switch matrix ICS 4864
  • #6354: QP Detector Measuretime of ESL6 is set to 10 ms
  • #6360: Driver: Tektronix 2001 for fixed voltage test
  • #6361: Ability to zoom in the frequency graph during the prescan phase of a MB Emission test
  • #6362: Frequency of the graph in the report is different
  • #6364: Too few spaces in the name of the graphline in a report generator code causes that the graph is not include in the report
  • #6389: Update the Configurable Switch Matrix wiki knowledgebase page
  • #6394: NI DAQ USB 6218 AD Converter default input min and max
  • #6395: NI DAQ USB 6218 AD Converter channels 9-16 can't be used
  • #6397: How to dirrectly reference from the Main Template to a Keyword for a certain test
  • #6398: Driver: Tektronix TDS2024C Oscilloscope
  • #6399: Driver: Tektronix AFG3252 Signal Generator
  • #6400: Driver: IFI ST181-10 Amplifier
  • #6403: Ability to use the FSV-3 Analyser controlled as powermeter in zero span mode
  • #6405: ARFI7000 is not reading probe values
  • #6410: Driver: ETS-Lindgren 8000-053 amplifier
  • #6411: Driver: ETS-Lindgren 8000-034 amplifier
  • #6412: Raise an error when R&S NRP-Z55 is disconnected during a test
  • #6418: R&S FSV 40 Error -222: Data out of range DISP:TRAC:Y:RLEV -10 DBM
  • #6426: Configurable Switch Matrix isn't correctly saving settings when user configured commands of During and/or After Test are cleared
  • #6428: Device driver Check is erasing the selected correction file(s) in the device configuration screen
  • #6432: Device drivers that are using GPIBRS232 should be converted to panels
  • #6436: Selection of a correction file in a device driver configuration is not working
  • #6438: Default frequency range of the EMCO / ETS-Lindgren antenna 3117
  • #6439: Driver: All ETS-Lindgren 8000-series amplifiers
  • #6442: What does the NRP settling time does?
  • #6448: Correct frequency range of the ETS-Lindgren 8000-034 amplifier
  • #6451: Frequency up / down for UFA calculation is not working
  • #6453: Uniform Field Area (UFA) calculation should trigger a default auto-layout when calibrations are added or removed
  • #6454: Not possible to use CAL files for the UFA when it contains different test distance
  • #6455: Warnings related to wxEXPAND are shown when a wxWidgets dialog is shown
  • #6459: ETS-Lindgren 8000-053 Device Not Connected
  • #6462: How to set the RBW when the R&S FSP 40 is used as powermeter?
  • #6465: Driver: ETS-Lindgren Antenna series
  • #6467: Driver: R&S FSIQ 7
  • #6471: 'Decrement' should be the default value for the PowerStep setting of the Amplifier Linearity test
  • #6472: Settings that are normally protected for the administrator, can be changed when the dongle is not present
  • #6474: After zooming in a graph the graph axis is no longer linked to center and span
  • #6476: Save the configured Auto-Layout settings for the Uniform Field Area (UFA) calculation config
  • #6477: Insert Row in a Correction file is not working if no row is present
  • #6478: A new correction file should have 1 row by default
  • #6479: A new row should be added to a correction file when the 'TAB' key is pressed in the last cell
  • #6487: Driver: EUT Controller: Generic TCP/IP Status interface
  • #6488: Python program to test/verify the Generic TCP/IP Status inteface
  • #6491: Driver: Frankonia EMCL-20
  • #6493: GPIB address of Frankonia FC06 cannot be changed
  • #6504: Project: Remember which graphs should be shown
  • #6505: Propose best implementation to remember graphs to be shown
  • #6527: Ability to specify a frequency depending RBW for the R&S ESI Powermeter
  • #6536: Unit-test for the C++ CenterSpanStartStopFrequency class
  • #6537: In the testsite window, 'save as ...' should show the original name + ' - Copy' as the new suggested name
  • #6571: Remove Row of a correction file selects the first row if the last row was selected
  • #6572: Show a message with the used coupling value for the virtual coupler
  • #6577: Project: Telefication: Substitution measurement investigation
  • #6580: Showing the configuration window of R&S NRVS AD-Convertor crashes
  • #6586: ETS-Lindgren HI-4422 VI_ERROR_INV_PARAMETER: Invalid Parameter error
  • #6609: Update the splash screen logo of ETS to DARE!! Instruments
  • #6620: Driver: Frankonia ALX-4000E / AXL-80
  • #6624: Driver: Frankonia FLG-70C / FLH-200B1
  • #6627: Make StandardPreAmplifer device drivers Configurable
  • #6657: grid color always black
  • #6664: Driver: R&S ESRP7 as powermeter
  • #6717: Zero button should be shown for the FieldSensor Virtual Instrument
  • #6726: How do I configure the RPR3006W power meter for remote control?
  • #6735: Also show a magnifier button after the selection of the CONFDVDR directory
  • #6796: Report generator code to retrieve the 'Device driver versions'
  • #6847: General working and use of Main and test specific template with the Report Generator

RadiMation version 2015.2.4

  • #476: The CI configuration window is to small by default
  • #2216: ESD has strange behavior when pre defined report generation is enabled
  • #4498: Measuring settings Lines/Neutral with LISN
  • #4607: Customize graphs not working
  • #5322: Signal Generator setting the frequency raised an error
  • #5954: R&S ESL 6 Scanning Receiver Specific System Error -222 Data out of range SCAN1:TIME 1 MS
  • #6152: Incorrect behaviour of Save button after RE test
  • #6251: R&S ESR7 specific System Error: -222 Data out of Range DISP:TRAC:Y:RLEV:0.0103DBM
  • #6287: Driver: R&S ESL6 as Sensor power meter
  • #6301: Preamplifier setting is not visible anymore in the CE MB TSF window
  • #6303: HP 34401A message There is no Device Stream Configuration
  • #6303: List of performed tests is not updated in the report generator, when a test is finished
  • #6308: COM port setting is not remembered in the RadiMate IV device driver
  • #6314: Is it possible to use mutlimeters or oscilloscopes for conducted immunity tests
  • #6372: Can I take an existing graph / plot and generate an excel file with the frequency and amplitude data?
  • #6647: RadiSense 6 fieldprobe connected by Radicentre 1 is raising an error
  • #6793: How can the settings of an oscilloscope for the the Voltage measurement during a Conducted Immunity be set?

RadiMation version 2015.2.3

  • #1864: Move during measurement checkbox is shown in unlogical state if multiple bands are selected.
  • #5320: Folder name is changed to New Directory again
  • #5744: After adding a TSF directory it doesn't show the renamed directory name directly
  • #5894: DARE Homepage menu item name and link is incorrect
  • #5898: Graph items and restore factory default are disabled for the Chart settings
  • #5947: Modulation of Marconi 2024 Signal generator is never turned off during CI test
  • #6202: Show the DeviceStream configuration of a device driver in a panel below a combobox
  • #6243: Communication issue with a RadiSense IV connected by CTR1
  • #6250: Advanced configuration dropdown boxes are not visible for the RadiSense IV driver
  • #6286: Report generation doesn't replace all the codes
  • #6289: CompleteBuild.py is not triggering a rebuild
  • #6309: How to configure test setup files when using a low resolution?

RadiMation version 2015.2.2

  • #703: Calibration Types
  • #1922: No compression information in table form when performing a Compression test.
  • #1923: No color difference in graph at Compression test
  • #2288: Automated test for EFT
  • #2289: Automated test for Surge
  • #3812: EFT and Surge do not have seperate positive and negative pulse levels
  • #5269: Frequency is not set during harmonic measurement
  • #5285: Harmonics measurement (amplifier cal) is not working
  • #5574: Harmonics measurement could be optimistic
  • #5614: It is possible to start a test without an EUT opened
  • #5737: EFT test duration field is required
  • #5902: Not possible to remove test specific report generator template from items in the report generator settings list
  • #5903: List sorting settings of the Report Generator Settings are not retained
  • #6100: Device driver: Teseq NSG3040
  • #6122: Common buttons on the Multiband status test window should be enabled
  • #6129: Device driver: emtest EFT 500M
  • #6132: Sequence number in PI MB EFT test is not updated
  • #6137: Update list of available EFT-line couplings
  • #6138: Update list of available Surge line couplings
  • #6139: Driver: Haefely PEFT-Junior
  • #6140: Selected Cable in EFT & Surge MB test is retained after it doesn't exists anymore
  • #6141: Driver: GPIB support for emtest UCS500N
  • #6144: Update the progress column of the EFT and Surge tests
  • #6145: Implement the test repeat count for EFT and Surge tests
  • #6146: Is Random Surge angle working correctly?
  • #6148: Creating a new EFT MB TSF shows an empty screen
  • #6164: Enable Amplifier harmonics and gain for all users with the Immunity module
  • #6179: Units are not correctly shown initially in the BandsGrid control
  • #6180: Only the duplicates bands should be selected after duplication in the BandsGrid control
  • #6181: Up and down buttons of the BandsGrid control are flickering during changes
  • #6182: Up and Down buttons in the BandsGrid control are swapped
  • #6192: Move the 'Change' button of the units to the bottom right of the units

RadiMation version 2015.2.1

  • #4354: Test data graph has become black
  • #4398: Graphs (auto) scaling is not functioning as expected
  • #4811: When start frequency is unchanged it's causing frequency range errors
  • #5001: Allow to insert attachments in an EUT file
  • #5002: Possibility to directly attach generated report to the EUT file
  • #5524: File is probably corrupt, or it is created with a newer version of the software
  • #5682: Tolerances of AD Channel are shifted after report generation
  • #6015: Is it possible to perform the power delivery test on another frequency

RadiMation version 2015.1.12

  • #3821: Test equipment not correctly changed in radiated immunity multiband
  • #5250: Change format of graph export per default
  • #5402: Driver: AR 20ST1G18 Amplifier
  • #5595: Driver R&S Vector Signal Generator SMBV100A
  • #5596: Driver: AR 50ST1G18 amplifier
  • #5670: How to integrate probe calibration values into RadiMation
  • #5871: Metrohm Antenna Tower device driver
  • #5892: Turning on modulation of R&S SME is having a hardware delay
  • #6033: Extend driver for Agilent 34401A Multimeter (AD Converter) with VISA communication
  • #6063: HP 4417A Power meter issue
  • #6136: Driver Frankonia controller Model FC-06
  • #6200: The AD Channel configuration window is not responsive when it is shown the first time
  • #6202: Show the DeviceStream configuration of a device driver in a panel below a combobox
  • #6208: Driver: IFR2398 Spectrum Analyser
  • #6209: Configuration National Instruments AD converter for channel 9 and higher
  • #6211: HI 6105 Device Driver Function Not Implemented
  • #6212: HI 6105 wxDynamicLibrary already loaded error
  • #6213: HI 6105 always tries to switch to local
  • #6214: Driver Prana DP600 amplifier
  • #6221: Driver Anritsu Spectrum Master MS2713E as field sensor for 2000-1791-R antenna
  • #6222: How can we change the speed of the Maturo turntable
  • #6224: Extend driver for Agilent 34401A AD Converter with VISA communication
  • #6225: Driver Manual Controlled AD Converter
  • #6226: No values for National Instruments AD converter channel 9 and higher
  • #6232: How to measure the Frequency and duty cycle with Oscilloscope or AD Converter
  • #6234: Directly raise an error when device is disconnected
  • #6249: Wrong AD Channel is selected for RadiSense probe
  • #6272: Driver of Keysight Technologies N9038A is checking for the 'Agilent Technologies' *IDN? response

RadiMation version 2015.1.11

  • #1491: The directory selection is not showing the directory
  • #2697: Possibility to use units during editing of correction files
  • #5683: Driver EPI1001A CTR plugin card
  • #5947: Modulation of Marconi 2024 Signal generator is never turned off during CI test
  • #5971: Driver: Fluke45 as multimeter
  • #6098: Logarithmic step frequency for R&S ESPC Receiver
  • #6151: Advantest R4131D No match was found in the specified regular expression errors
  • #6161: Graph Customization Configuration button Restore factory default is always disabled
  • #6166: Verification TESEQ drivers
  • #6169: RPR device driver is crashing RadiMation
  • #6173: First sweeps Advantest TR4172 are jittering, causing wrong measurement results

RadiMation version 2015.1.10

  • #3503: The configurable signal generator does not allow the setting of the external modulation settings
  • #4410: Changed modulation settings are not applied
  • #4831: Not possible to see actual values in table mode
  • #5467: Hide all table information is not working
  • #5782: ESRP raises an error for an unknown header: INP:GAIN:LNA:STAT OFF
  • #5796: Setting the frequency is showing rounding issues
  • #5915: Driver: Keithley Arbitary Generator 3390 as modulation source
  • #5947: Modulation of Marconi 2024 Signal generator is never turned off during CI test
  • #5960: Pulse modulation settings in the singleband fixed power manual mode window are not forwarded to the signal generator device driver
  • #6054: Cross thread operation detected error
  • #6057: Keyword ||RADIMATION VERSION|| is exporting 201x,x instead of 201x.x.x
  • #6061: Can not save LLF anymore after making changes
  • #6065: Multiband PM Modulation Configuration setting is not retained
  • #6066: Windows Universal Naming Convention (UNC) is causing error "Access to the path.. is denied." when creating a new TSF directory
  • #6078: Opening a test in a newer version overwrite test data used RadiMation version
  • #6085: Support 2 Hz AM modulation in RadiGen
  • #6095: Driver Bonn BTA 0122-3000
  • #6099: RadiCentre is still in remote after deinitialisation
  • #6102: Overshoot detection of the EMCO1060 is not working
  • #6103: Suggested product id number for instrument descriptor of NRP power meters is wrong
  • #6107: R&S BBA100 RF path is not being switched between bands
  • #6111: R&S AFG device check seems to be always successful
  • #6112: R&S BBA100 RF option to always keep amplifier on
  • #6113: External Modulation Source settings are lost
  • #6114: Configurable Signal Generator Modulation settings are not retained
  • #6115: Enable wxWS_EX_VALIDATE_RECURSIVELY for all device drivers
  • #6116: Move during measurement should not be visible in an immunity multiband test
  • #6120: Configurable Modulation Source carrier level is not send
  • #6171: CARAD EUT Controller driver settings are not retained

RadiMation version 2015.1.9

  • #4140: Problem with ESL6 and conducted emission LISN test
  • #5140: Current Status windows without a description is shown
  • #5230: Not possible to delete measurement data from the EUT
  • #5325: R&S ESIB26 Analyser not all bytes are writen (..) within the timeout period
  • #5526: Implement Word Wrap for error code descriptions
  • #5889: CDN test according EN61000-4-6
  • #5891: Driver National Instruments AD converter (NI USB 6218 BNC)
  • #5929: Monitoring input channel setup is not using the correct default device driver setting
  • #5943: AR No Listeners are detected on the GPIB bus and the KRE matrixes is alway switching to position 2
  • #6060: Quasi peak measurement of Advantest TR4172 sometimes has a difference
  • #6067: Agilent N9038A MXE is not using Discrete Scan Type
  • #6072: Driver Narda SRM3006
  • #6082: Typo in the description "successfull"
  • #6083: Adding beeb as before or after action is directly showing a warning
  • #6084: Driver AR 100S1G6 amplifier
  • #6091: How to manually operate an Antenna Tower and Turn Table
  • #6097: How to perform a CE measurement with a voltage probe (PMM SHC-1-1000)

RadiMation version 2015.1.8

  • #5052: Reference level is changed during measurement, generating an IF overload
  • #5385: Power delivery test stops with “Power went to high -4dBm Signal Power"
  • #5829: Frequencies labels are not correctly updated in a Mutiband TSF
  • #5950: Driver Amplifier Bonn BSA 0106
  • #5976: Saving a Pause Test is generating several 'file corrupt' problems
  • #5983: Driver for obsolete field probe PMM8052
  • #5998: What means: 'before', 'during' and 'after' on the EUT Monitoring channel
  • #6002: Do not change the reference level. Leave it fixed on the selected level
  • #6030: AR FP 3000A Field sensor is not connected
  • #6034: New EUT Monitoring channel configuration is not working in Singleband immunity
  • #6035: Values specified in the Min and Max of AD Input Range are lost
  • #6037: Driver National Instruments Switch (NI USB 6218 BNC)
  • #6038: Driver HP 83650A Signal generator
  • #6039: Driver FSP 40 as powermeter
  • #6040: Driver CBL 6112C
  • #6043: Units configuration is not applied to test
  • #6045: Auto save function after completion of (Multiband) tests is polluting the EUT
  • #6051: Possibility to send switch command before power on for the Configurable Amplifier device driver
  • #6052: Configurable amplifier device driver is sending the standby command at start of test and operate command after the test
  • #6056: Monitoring input channels from channel 33 and higher are not working
  • #6079: Problems with Software Protection Key dongle
  • #6089: No graph or table information is exported in manual mode test data
  • #6092: Different antenna polarization errors during UFA calculation

RadiMation version 2015.1.7

  • #2140: Ampersand in name of test-site is shown as underscore on information window
  • #5634: R&S ESPI 7 specific system error SWE:SPAC LIN
  • #5856: Auto move of antenna tower is harmfull for hardware
  • #5904: Keyword TEST TIME is exporting wrong data and shows TEST START TIME
  • #5906: Spurious emissions with high values are detected during noise floor measurement
  • #5910: Sunol SC110V customer specific Antenna Tower driver
  • #5917: Final peak measurement with ESR 7 blocks the software
  • #5925: Configurable Signal Generator is missing the Remote Control checkbox
  • #5939: Strange measurements with the R&S ESVS20 Test Receiver
  • #5940: HP 33120 signal generator raises error 1 -113
  • #5946: Driver AR 40S4G18M4 Amplifier
  • #5961: A 1 hour multiband immunity test causes an algorithmic calculation error
  • #5964: R&S ESR7 Specific System Error -141 Invalid character data SWE:SPAC APUL
  • #5970: RSS1006A no connection after changing COM port
  • #5980: The entry "Configurable EUT Controller" is in the driver list of Switch Matrix and not in the list of "EUT Controllers"
  • #5986: Frequency up/down is not working in multiband immunity manual mode
  • #5987: Driver Milmega AS0827-55 amplifier for IEC61000-4-3
  • #6014: Power delivery test is not succesfull at 550 MHz
  • #6044: How can I get more precision from the data of a calibration file?
  • #6074: Forward power measurements values are showing dips

RadiMation version 2015.1.6

  • #4598: Driver PMM9010F
  • #4947: Diagram description in dBuA/m with Magnetic field setting
  • #5155: Driver PMM9010F
  • #5369: RadiMation crashes when SRQ line is busy
  • #5594: Driver Agilent Power Meters U2000H, U2000B and U2002A
  • #5641: Signal power went to high errors with Gigatronic 8542C powermeter
  • #5645: Peak measurements give different results
  • #5841: MXE receiver N9038 is not starting performing the measurement
  • #5843: First point of forward powermeter (Advantest analyser) measurement is wrong
  • #5844: Advantest analyser as powermeter is not automatically switching the attenuator
  • #5847: RadiField field verification
  • #5883: ESL 6 quasi-peak measurement gets stuck
  • #5907: Error detected during the start of the sweep with PMM 9010 F
  • #5919: Unexpected power readings with RPR3006W Powermeter
  • #5932: RIGOL DSA 815 AVG and QP measurements are showing differences compared to manual measurements
  • #5933: Regulation in the Multiband Immunity test is not increasing the power to satisfy both Testlevels
  • #5937: Driver: Rigol DSG3060
  • #5945: RIGOL DSA 815 timeout and query interrupted
  • #5948: When opening test data a Run-time error '91' Object variable or With block variable not set is shown
  • #5949: Driver AR Field Analyser 7006 read out
  • #5951: RadiMation crash during startup
  • #5955: Drivers AR DC2500AM1, DC7128A, DC7420M1, DC7530 and DC 7620
  • #5957: Driver AR 40T26G40A
  • #5958: Drivers Antennas ATEK30MM1, ATL80M1G, ATH18G27, ATH26G40
  • #5965: What is the difference between the average value and the measurement value of the used field probe?
  • #5966: Why is the setting of the frequency range missing in the driver window?
  • #5972: When is the CAL calibration file needed to be used
  • #5979: What is the External Dwell Time and how is it working?

RadiMation version 2015.1.5

  • #3864: Init of the multiband test is not using the amplifier driver of the amplifier manager
  • #5590: Include option to download latest drivers.exe in RadiMation setup program
  • #5602: Include option to overrule drivers.exe included in RadiMation setup program
  • #5826: Error 76: Could not find a part of the path (..)
  • #5828: Opening a TSF file from a sequence is suddenly changing focus at the sequence window again
  • #5830: Test file is corrupted after opening and saving
  • #5831: Unexpected forward- and sensor power measurements during calibration
  • #5896: Showing graph and table information is making the performed test extremely slow
  • #5909: Configuration of Narrow band / broad band detection according to standards has disappeared
  • #5922: Update Copyright information of device drivers setup
  • #5928: Current Closed loop method is not correctly controlling/reading the sensor power meter
  • #5931: Data files of a RI Multiband test are corrupted after editing the note
  • #5959: Driver: Narda PMM EP408 Field probe

RadiMation version 2015.1.4

  • #2249: Not possible to set limit line from 500 Hz to 900 Hz
  • #4019: Unexpected CIC errors
  • #4733: No trace of the measurement data visible
  • #4748: QP measurements seems to be wrong
  • #5406: Peaks are detected outside the graph trace
  • #5563: Continuously measuring envelope power of the RadiPower results in memory problems
  • #5684: Unexpected high noise floor with CXA 9000A
  • #5818: Driver for R&S ESPC not working anymore after updating drivers.exe
  • #5821: VI Powermeter: Burst Graph doesn't show the graph by default
  • #5823: Driver: Teseq NSG 4070 as Amplifier and Powermeters
  • #5826: Error 76: Could not find a part of the path (..)
  • #5827: TSF files can't be deleted, delete and Ok buttons are always disabled
  • #5837: How can the field sensor be corrected by a RadiMation file?
  • #5846: R&S ESRP error Data out of range during time setting
  • #5848: Does the modulation needs to be turned off and on during each frequency step?
  • #5849: How can a customized warning message be shown?
  • #5857: GPIB Hibernated NI Drivers error required PC restart and loss of data
  • #5860: Frequency range of Agilent N5171B Signal Generator
  • #5862: How to add the correction for the emission antenna VW TL81000?
  • #5868: RadiMation is crashing when device is not connected

RadiMation version 2015.1.3

  • #5642: Driver Teseq NSG 4070 as Signal Generator
  • #5736: No trace data obtained from measurements with FSV13
  • #5739: Cursor information is no longer shown
  • #5778: Rigol spectrum analyser as powermeter is using pre-amp
  • #5780: Control of the Maturo antenna tower is not working if it is controlled with a LAN-to-GPIB convertor
  • #5790: Final measurement of QP detector on R&S ESI always returns 0 dBuV
  • #5797: R&S SME03 Specific system errors Level over range and ALC failure
  • #5800: Windows XP is not supported anymore
  • #5801: Detection if zeroing of RadiSense4 probe is finished takes a long time
  • #5803: Controls of the VI Powermeter are not reenabled if the auto-trigger is disabled during the re-trigger wait time
  • #5805: Old test results cannot be loaded in 2015.1.2
  • #5816: Rigol spectrum analyser pre-amp settings can't be controlled

RadiMation version 2015.1.2

  • #5787: Selection of another TSF folder doesn't update the list of TSF's in that folder
  • #5791: Uniform Field Area Calculation is not working for Constant Power method calibration files

RadiMation version 2015.1.1

  • #5775: Driver R&S switch matrix for amplifier BBA100 interlocks

RadiMation version 2014.3.8

  • #5773: Amplifier that is already in OPERATE can result in an endless test initialization
  • #5774: Antenna tower reports the error: Field probe is still busy with zeroing the field probe
  • #5776: Several improvements to the Antenna Diagram module
  • #5777: ETS-Lindgren 7006-001: antenna tower: device-id 1A/1B is not selectable

RadiMation version 2014.3.7

  • #669: Implement Advanced IO
  • #1475: Specification of the AD-Channel measurement is too complicated
  • #1529: Use multiple AD-Convertor device drivers simultaneously
  • #3339: Possibility to include several AD Converters
  • #5640: Missing whitespaces when (German) date is inserted in report
  • #5751: RadiSwitch is not working anymore
  • #5769: TEST DATE keyword not available for RE

RadiMation version 2014.3.6

  • #5691: Measurement differences during validation of Radiated Emission
  • #5724: Error message during deinitialization of RadiSwitch card: Could not create RS232RunTimeData
  • #5755: Error Comport could not be accessed RSW No RS232RunTimeData object could be created

RadiMation version 2014.3.3

  • #1527: Test results should be saved during test
  • #2535: Dutch Lineair should be changed to english Linear
  • #3083: Tests should save the data during the test, so no a lot of data is lost due to a crash
  • #3351: Test-number shown in Graph
  • #5707: AAA amplifier module can't be updated

RadiMation version 2014.3.2

  • #929: Simplify the loading of the calibration files for the 16 point calibration
  • #3742: continuing a calibration after error
  • #4692: Errors in calibration file, give problems during 16 point verification
  • #4773: Default calculation method for the 16 point
  • #4774: In an uniform field area calculation with 9 calibration files, the points should be shown in a 3 x 3 grid
  • #5289: Implement unlimited Uniform Field Area calculation

RadiMation version 2014.3.1

  • #2425: Changing a device driver configuration is not stored if the CONFDVDR directory is read-only, but also no warning
  • #4457: Prevent that a new device driver can be created when the CONFDVDR directory is read-only
  • #4458: Show a clear message that states that the CONFDVDR directory is readonly, when the 'Advanced' button is pressed
  • #4751: RG: report output location is not retained
  • #5088: Warning to show in new device driver that it still should be configured
  • #5471: Multiband test level and Inputs grid controls customizations are not retained
  • #5498: Include test settings are not retained
  • #5544: ASCII export functionality is not available
  • #5551: Only include Sentinel USB drivers in SETUP.EXE instead of Protection drivers
  • #5555: Change the SQLite COM object to a .NET interface
  • #5675: Opening probe data is generating error Arithmetic operation resulted in an overflow

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.