Siglent SVA1015X and SVA1032X 1.5, 3.2GHz Spectrum & Vector Network Analyzers

[Johnny B Good]

 I'm guessing it's more likely that this data, along with other setup data, is stored in sram ready to be copied at an instant's notice into the flash when the soft power button is pressed to initiate the shutdown process controlled by the OS. It may be being saved to sram every 60 seconds but this only gets written to the flash on each soft power-down cycle.

 Of course there's always the alternative strategy of triggering a short  (10 to 30ms?) write to flash cycle when the PSU PG signal is negated by the loss of mains supply utilising the few hundred milliseconds worth of reserve power remaining in the HT smoothing caps to complete such a short write cycle to guard against even this most extreme of shutdown scenarios.

[pagrei]

Does any one have a vna factory cal file from a genuine SVA1000X they can share?

I’d like to have a go at understanding the internal file format…

[pagrei]

Specifically, I am after the following files:

/usr/bin/siglent/usr/config/usr_vna_o_calib_log.bin
/usr/bin/siglent/usr/config/usr_vna_s_calib_log.bin
/usr/bin/siglent/usr/config/usr_vna_calib_log.bin
/usr/bin/siglent/usr/config/usr_vna_ref_log.bin
/usr/bin/siglent/usr/config/enh_rsp_calib_log.bin
/usr/bin/siglent/usr/config/usr_vna_e_calib_log.bin
/usr/bin/siglent/usr/config/usr_vna_e_ref_log.bin
/usr/bin/siglent/usr/config/usr_vna_o_calib.bin
/usr/bin/siglent/usr/config/usr_vna_s_calib.bin
/usr/bin/siglent/usr/config/usr_vna_calib.bin
/usr/bin/siglent/usr/config/usr_vna_ref.bin
/usr/bin/siglent/usr/config/enh_rsp_calib.bin
/usr/bin/siglent/usr/config/usr_vna_e_calib.bin
/usr/bin/siglent/usr/config/usr_vna_e_ref.bin

[CoolNamesAllTaken]

After upgrading my SVA1032X to firmware version 3.2.2.6.2R5.r19, I seem to no longer be able to save .CAL files, to the local file system nor to an external USB drive. Has anyone else experienced this issue? Any attempts to save .CAL or .CSA result in a "MSG: Save file failed!" warning. It seems that I can still save CSVs and other file types.

For what it's worth, the calibration does seem to stick between reboots after it's done, but it's weird to not be able to save it to a separate file.

[NY2KW]

If you can give me some basic instruction how to download those files, I can try.

Jerry

[pagrei]

Hi Jerry,

Thanks for the offer.  I’m waiting to see if another option “pans out”.  If not, I’ll post some instructions to extract the calibration data to a USB stick.

Pa

[pagrei]

Hi Tautech,

Did you get any feedback from Siglent regarding the write to NAND every 60 seconds in the latest firmware?

In particular, does it only occur if you don’t select boot to default?

[IM3]

Yes, I share the same concerns.

This is preventing me from proceeding with the update. I know that the hardware does have flash memory with a write limit of 100,000 cycles.

It would be great if Siglent acknowledged the concerns of technical users and provided an explanation that inspires confidence.

I have an SSA3075X-R, and this 60-second save feature has been implemented there as well.

[TERRA Operative]

Wow, that's theoretically only 28 hours of runtime needed to start having issues of worn memory.....

[IM3]

The calculation is a bit different: 100,000 flashes / (24 x 60 minutes) = 69 days. 

It would be quite strange for Siglent to flash data every minute, so I hope it was just poorly phrased in the firmware notes.

However, the only reason to save data every minute would be for power-down purposes, which must be done in non-volatile memory, such as flash.

I recently photographed a flash memory chip in an SDS5000X. This flash was located near the processor. You can assume that this type of flash is used in all Siglent devices.

[spacehen]

After upgrading my SVA1032X to firmware version 3.2.2.6.2R5.r19, I seem to no longer be able to save .CAL files, to the local file system nor to an external USB drive. Has anyone else experienced this issue? Any attempts to save .CAL or .CSA result in a "MSG: Save file failed!" warning. It seems that I can still save CSVs and other file types.

For what it's worth, the calibration does seem to stick between reboots after it's done, but it's weird to not be able to save it to a separate file.

Saving a calibration file works fine on my unit with the latest firmware.