Rohde & Schwarz R&S SMA100A - Page 11

R&S SMA100A Information on the Current Version and History
Release Notes for Firmware 1171.5360.52 11
● ILS-Loc/ILS-Gs Modulation (R&S® SMA-K25): The parameters are sorted in a
different order for improved usability.
● DME Modulation (R&S® SMA-K26): The parameters are sorted in a different order
for improved usability.
● DME Modulation (R&S® SMA-K26): Channel Suffix enhanced with ICAO channels.
● Phase settings: The resolution for delta phase changed to 0.01 deg
● Improved stability and performance of USBTMC
● Directory /var/user, that is intended for user data storage, is no longer used by any
instrument files. Former instrument directories like “Lists” may be removed if
appropriate.
● Support of wildcards ‘*’ and ‘?’ in mass memory system MMEM
● Remote control emulation Aeroflex 202x: Added suffix 2 as an alias for suffix 1 in
AM, FM and PM subsystem
● Remote control emulation Aeroflex 203x/204x: Added subsystem SWEEP
● Remote control emulation Agilent E44xx/N51xx: Added file selection for the
variants “file@msus”, “msus:file” and “absolute path to file” to the MMEM/MEM
subsystem. Valid data for msus are “UFLT” and “LIST”.
● Remote control emulation Agilent E44xx/N51xx: Added subsystem LIST and
SWEEP
Fixed Issues
● VOR Modulation (R&S® SMA-K25): Missing SCPI
command :SOURce:VOR:FREQuency:STEP to set the Carrier Freq Knob Step to
Defined.
● All Sweeps: In mode Single with shape Triangle, the R&S® SMA100A ignores
Execute Single commands while the sweep is running
● All Sweeps: In mode Extern Single with shape Triangle, the R&S® SMA100A
jumps back to the beginning and stops (like reset) on external trigger signals
applied during the triangle return slope.
● Listmode: In mode Single, the R&S® SMA100A ignores Execute Single commands
while the listmode is running
● viClear() over USBTMC blocks further communication
● Communication break, after applying viClear() to USBTMC interface
● *CLS did not clear error queue
● Some message boxes did not accept ENTER/x1
● NRP-Z Power Viewer indicator could not be configured to display peak values
● Socket connection might lose data packages send in a fast sequence
● Several issues around the data/time dialog