Wine user, read this before running SATSAGEN on macOS/Linux
Latest release:
SATSAGEN v.0.9.2.1 (29 November 2024) File size: 5.867.029 bytes MD5 a23db9faa40e6d5685184a840c162635 SHA1 e565c9d9a88dbb60361eeb26da8a9ef29a82d648 SHA256 7a7f115f9b36b01429365b6a6adb7296f5960b368b31fc4ced76a22ff5992ede SATSAGEN v.0.9.2.1 article (under construction) Highlights - Time Domain (Zero Span) in ZERO-IF and IF demodulation process mode - Support ADF4351 and Si5351 synthesizers via USBDAALBFER interface - Experimental support for USRP B200 - VNA dual-port/dual devices configuration - Configuration diagrams for SNA/VNA settings - Improved simple spectrum analyzer device protocol - Live warning messages on the Status Display - kHz setting on SNA/VNA start/stop frequencies Additions - Added knob to define the range of intervention of the Video FFT trigger in Time Domain, which can be activated with Level R (-) and Level R (+) - Added Trace auto-clear button in the Time Domain tab that allows to select the auto-clear function of the trace if the trigger has not been activated - Added the frequency vs time in Time Domain, selectable from the Time Domain tab. Improvements - Support firmware F5OEO DVB2 0.5.16.2 - Improved Radio tuning knob operation for SSB, added up/down buttons for Radio tuning knob control - Extended the maximum time base of the Time Domain FFT to 5 seconds and extended down to 1uS (100ns per division) - Recalibrated AD8318 and AD8317 tables in curvecorrRX_PLUTOCGT.ini - Recalibrated ADALM_PLUTO RX table in curvecorrRX_PLUTOCGT.ini port 1 for frequencies below 50 MHz - Recalibrated AntSDR e200 UHD RX table in curvecorrRX_PLUTOCGT.ini port 1 for frequencies below 50 MHz - Reference Frequency, XO Correction, and Connection string override parameters become custom per device. - The generator modulation amplitude box becomes Deviation for FMN, FMW, and FSK modulations, in Hz for FMN and kHz for the others - It is possible to set Start and Stop TSA/VNA frequencies even when Start exceeds the set Stop and vice versa. If this condition occurs, Start or Stop are automatically set below or above the minimum possible step. Fixes - Zero Span video trigger does not work on slow events for example 1/s - Version 0.9.1.1 with the Fix "uncertain Zero Span video trigger with waveforms with too steep transition time edges" introduces "shaky" vision for faster events - Wrong display without x-axis subdivision if the Time Domain (Zero Span) starts on spectrum analyzer with zoom activated - Incorrect marker position in Time Domain - Moving markers in the Time Domain can have excessive steps. Now the steps are the X-axis resolution in nanoseconds divided by 100 (or finer divided by 1000 with CTRL pressed and using the mouse wheel to move) - LogDetector incorrectly calculated the maximum value of the scale based on the configured attenuator. For example with a -20dB attenuator and AD8318 log detector the maximum measurable was -10 dBm while it should have been 30 dBm. - Incorrect display in SA at the frequency edges of devices by acting on RBW, span coupled, or changing the Sample limit - SSA devices do not save settings for center frequency, Span, etc… - Incorrect display in SA of minimum frequency of AntSDR e200 UHD device - Radio not correctly tuned to the edges of the spectrum - The Settings window goes into the background if the main window goes out of focus during opening. - The VF size, FFT size, and fast cycle resources are restored if a workload decreases, but the restore load function can interfere with manual settings of those parameters - Prevents that a length change within three characters of the X-axis label of the scope spectrum analyzer changes the justification causing a "dancing" display - FSK modulation is not clean, because it does not maintain the phase when changing the deviation frequency. - Access Violation during Power Off after connecting to a serial device with an incorrect model. - Non-USBDAALBFER serial ports may remain open after scanning available devices - Cannot insert markers with SSA because Radio is enabled in a previous session started with SDR. - Cannot run TSA in harmonics using RTL, SDRPlay, or Airspy devices with TX devices enabled in harmonics. - The description of the previously connected device is used to connect to a device of a different model. For example, you connected to a Pluto, then disconnected the device and changed the model, for example to USRP B210. - In TSA2CH mode the TX reference frequency correction acts on both RX channels and can give the low signal warning, now it acts only on the first channel - In TSA2CH mode the TX device does not transmit as a generator - In TSA2CH mode if a single channel device without DDS FPGA (for example not Pluto) is used as TX, it does not transmit in TSA
If you like SATSAGEN, you can donate to support and incentives for developing new versions:
https://paypal.me/FERRARIS944
Thank you!