(Seems the picture was posted on Twitter, withou blurr)
I guess market for lower end VNAs is not very big? If something like this would be priced so that its attractive to "average" Amateur Radio hobbyist, Siglent probably would sell orders of magnitude more....For the typical antenna adjustments the cheap VNAs are enough. I have a miniVNA Tiny and it works really well. If you are doing finer stuff like filters it’s a different matter of course.
Wow, it looks very modern for a thing made in 1970 , or is it a bug in the firmware >:D
Looking at the port labels I am guessing that it will need an external coupler for S11 measurements...?
Looking at the port labels I am guessing that it will need an external coupler for S11 measurements...?
Looking at the port labels I am guessing that it will need an external coupler for S11 measurements...?
Apparently the Chinese know a way to do it without one. But my bet is they have no idea how to do it at all.
Looking at the port labels I am guessing that it will need an external coupler for S11 measurements...?
Ouch, hopefully the labeling is just incorrect, otherwise it is awful lame and better be crazy cheap. Pretty hard to call it a two port analyzer.
Looking at the port labels I am guessing that it will need an external coupler for S11 measurements...?
Apparently the Chinese know a way to do it without one. But my bet is they have no idea how to do it at all.
Looking at the port labels I am guessing that it will need an external coupler for S11 measurements...?
Apparently the Chinese know a way to do it without one. But my bet is they have no idea how to do it at all.
You don't need a system that uses an external coupler to measure S11. The DG8SAQ VNWA is a two port vector network analyzer that will measure S11 up to 1.3GHz and it uses a resistive bridge internally.
The difficult part is the phase of S11 (or indeed of any S-parameter they are measuring) - how do they compare the phase of the reflected signal with that of their source signal?
You don't need 4 or two receivers to measure S21 - one is enough, and also phase can easily be measured with just one receiver if you compare the received phase to the phase at the TG output.That is assuming the DUT doesn't affect the phase and amplitude of the TG. AFAIK most DUTs will affect the amplitude and phase of the TG so you'll need to measure the TG output while it is loaded by the DUT.
I have few more images about it which show the different mode. The unit was not connected to a signal or component. Would you like me to post them?
I have few more images about it which show the different mode. The unit was not connected to a signal or component. Would you like me to post them?Well errrr, like does a bear shite in the woods ? YES !
Could you elaborate how you think the phase is being affected and how is this relevant if you are comparing the phase at the input to the output?
It’s a relative measurement after all.
I'm not sure why you are being so dismissive. This topology definitely works.
Dear DC1MC,
Hope this email find you well!
This is Jie from Siglent, EU Sales.
Thanks for your visiting of our Siglent booth 4-306 at embedded world 2018 exhibition.
Glad to know that you are interested in our spectrum analyzer products.
Siglent products have the high quality test equipment with an excellent price/performance ratio.
For the details of our products, you can directly to visit our websites:
SSA3000X:
http://siglenteu.com/pdxx.aspx?id=1252&T=2&tid=18 (http://siglenteu.com/pdxx.aspx?id=1252&T=2&tid=18)
The new spectrum analyzer with vector network analyzing function is not available now.
If you have any concerns, please feel free to contact with me.
Best Regards,
Jie
EU Sales
AFAIK what makes things extra difficult is the fact that a 50 Ohm directional coupler works well for looking at a '50 Ohm system' but if you are looking at a system with an impedance of 1k Ohm or 1 milli-Ohm then the VSWR will be very far off anyway and thus measurement accuracy and resolution are going to suffer. I have a low frequency VNA (10Hz to 300MHz) and that offers various ways of doing measurements. I think this Siglent VNA will be handy for measuring antenna's and other typical circuits in the 50 Ohm or 75 Ohm realm but it may be less usefull for measuring milli-ohm impedances in circuit board power distribution.I'm not sure why you are being so dismissive. This topology definitely works.
Definitely not being dismissive, although I would've been before the PE42020 came out. What you posted could very well be what they're doing.
But through personal experience I've learned that there are very few free lunches in a VNA block diagram. Spectrum analyzers are downright trivial by comparison.
As you get up into the GHz range, isolation in particular is hard.
As we can't yet get even a Chinese datasheet for these who's to say what impedance corrections will be offered within the UI, lots more info is needed before we can say; it can't do this or it can do that.AFAIK what makes things extra difficult is the fact that a 50 Ohm directional coupler works well for looking at a '50 Ohm system' but if you are looking at a system with an impedance of 1k Ohm or 1 milli-Ohm then the VSWR will be very far off anyway and thus measurement accuracy and resolution are going to suffer. I have a low frequency VNA (10Hz to 300MHz) and that offers various ways of doing measurements. I think this Siglent VNA will be handy for measuring antenna's and other typical circuits in the 50 Ohm or 75 Ohm realm but it may be less usefull for measuring milli-ohm impedances in circuit board power distribution.I'm not sure why you are being so dismissive. This topology definitely works.
Definitely not being dismissive, although I would've been before the PE42020 came out. What you posted could very well be what they're doing.
But through personal experience I've learned that there are very few free lunches in a VNA block diagram. Spectrum analyzers are downright trivial by comparison.
As you get up into the GHz range, isolation in particular is hard.
AFAIK what makes things extra difficult is the fact that a 50 Ohm directional coupler works well for looking at a '50 Ohm system' but if you are looking at a system with an impedance of 1k Ohm or 1 milli-Ohm then the VSWR will be very far off anyway and thus measurement accuracy and resolution are going to suffer. I have a low frequency VNA (10Hz to 300MHz) and that offers various ways of doing measurements. I think this Siglent VNA will be handy for measuring antenna's and other typical circuits in the 50 Ohm or 75 Ohm realm but it may be less usefull for measuring milli-ohm impedances in circuit board power distribution.
1.5Ghz seems rather low for a VNA these days.
Is there a 3.2 and or 6Ghz version as well?
I guess market for lower end VNAs is not very big? If something like this would be priced so that its attractive to "average" Amateur Radio hobbyist, Siglent probably would sell orders of magnitude more....
Looking at the port labels I am guessing that it will need an external coupler for S11 measurements...?
Looking at the port labels I am guessing that it will need an external coupler for S11 measurements...?
So the explicit answer is no – and maybe that’s also one reason why the frequency range is limited to 1.5GHz. It’s pure speculation on my side, but I recon it would be difficult to cover an even wider frequency range with just one coupler or even bridge and for now Siglent sure didn’t want to have to switch between several of them – not to mention the increase in cost.
I guess market for lower end VNAs is not very big? If something like this would be priced so that its attractive to "average" Amateur Radio hobbyist, Siglent probably would sell orders of magnitude more....
We don’t know the price yet, so why starting to complain already?
There are still lots of folks buying the Rigol DSA815-TG, aren’t there? The new Siglent SVA1015X will cover the same frequency range, but with supposedly better specs, e.g. lower resolution bandwidth and lower phase noise. I don’t think the fact that this machine can be easily upgraded to a VNA, Fault locator and Digital Modulation Analyzer makes it less attractive for potential users.
Price will be around 1.5k$ what makes it quite interesting (of course including TG).
1.5Ghz seems rather low for a VNA these days.Not apparently only the 1.5GHz version for western markets and a 1GHz version for Asian markets.
Is there a 3.2 and or 6Ghz version as well?
1.5Ghz seems rather low for a VNA these days.
Is there a 3.2 and or 6Ghz version as well?
The FPC1500 can be upgraded up to 3GHz VNA included1.5Ghz seems rather low for a VNA these days.
Is there a 3.2 and or 6Ghz version as well?
Rohde&Schwarz do not think so.
Just ago launched new FPC1500 Spectrum & VNA base model is 1GHz.
The FPC1500 can be upgraded up to 3GHz VNA included1.5Ghz seems rather low for a VNA these days.
Is there a 3.2 and or 6Ghz version as well?
Rohde&Schwarz do not think so.
Just ago launched new FPC1500 Spectrum & VNA base model is 1GHz.
not looking for debate either :)The FPC1500 can be upgraded up to 3GHz VNA included1.5Ghz seems rather low for a VNA these days.
Is there a 3.2 and or 6Ghz version as well?
Rohde&Schwarz do not think so.
Just ago launched new FPC1500 Spectrum & VNA base model is 1GHz.
Yes of course. As I told BASE model is 1GHz. You buy it and then you buy things what you need. More os less handfull of options. Even VNA is option what need pay separately.
But still base model is 1GHz and my message only purpose was just answer for quy who wonder this Siglent "low" 1.5GHz limit. What is still more than R&S base model of FPC1500.
Not for start debate about R&S features and option. Only for show that even 1GHz comprabale equipment is lauched by A+ grade manufacturer just ago. No one is there to ask if it's a bit low just in the current years. As we can see name is important.
;) !
1.5Ghz seems rather low for a VNA these days.
Is there a 3.2 and or 6Ghz version as well?
Rohde&Schwarz do not think so.
Just ago launched new FPC1500 Spectrum & VNA base model is 1GHz.
Estimated price around 1500$
Correct.Estimated price around 1500$
hmm i have to preorder one, if the price is real. From what i see, SSA1015X is at 9980 RMB (1400EUR) and SVA1015X at 36780 RMB (4800EUR) -> http://www.siglent.com/spectrum_analyzer/SVA1000X (http://www.siglent.com/spectrum_analyzer/SVA1000X)
Actually a bit better than SSA3021X........SVA1015X US$ 1395 c/w TG plus other options.Correct.Estimated price around 1500$
hmm i have to preorder one, if the price is real. From what i see, SSA1015X is at 9980 RMB (1400EUR) and SVA1015X at 36780 RMB (4800EUR) -> http://www.siglent.com/spectrum_analyzer/SVA1000X (http://www.siglent.com/spectrum_analyzer/SVA1000X)
China price for SSA3021X is the same. ;)
I would be interested to know how much the SVA1000X differs from the SSA3000X *HARDWARE WISE*.
Is it really a new hardware or could everything VNA related (in theory) been implemented by software?
Regards,
Vitor
An informal poll:
If you are an SSA3000X owner, would you rather have purchased this if it were also available at the time of your purchase?
Yep - would upgrade if they had a 3GHz version. Hopefully that will follow.An informal poll:
If you are an SSA3000X owner, would you rather have purchased this if it were also available at the time of your purchase?
Possibly, although I would miss the up to 3Ghz range.
SVA1015X is the top model in this series in which there is also a China market only model SSA1010X-C of 1 GHz capability.Yep - would upgrade if they had a 3GHz version. Hopefully that will follow.An informal poll:
If you are an SSA3000X owner, would you rather have purchased this if it were also available at the time of your purchase?
Possibly, although I would miss the up to 3Ghz range.
Guess that as soon as siglent offer free vna (and others) options for free...I doubt very much they will !
Does the VNA option include the calibration KIT?Apparently not. They're separate items in my price list.
Siglent offers a set as calibration kit, from the data sheet:
"The F503ME mechanical calibration kit contains precision 50 Ω, phase-matched, type-N standards, used to calibrate Siglent vector & spectrum analyzers. Standards include a fixed 50 Ω termination, an open load, a short load, and a through adaptor.
The F503ME performance specifications are very similar to the Keysight 85032B mechanical calibration kit and it can be used as a replacement of 85032B."
Sorry if it is a dumb question... to analyze RF devices with non N connectors like SMA, is it required to have SMA calibration kit? Is it possible to enter user defined / custom calibration kit parameters into the SVA1015X?Seems so.
6. Modify Cal kit (not available)Seems to me that Siglent released an unfinished firmware with the SVA1015X. Waiting for a full review and teardown.
Use user defined calibration kit
U-Boot 2014.07-svn32893 (Apr 27 2018 - 17:38:15)
Board: Xilinx Zynq
I2C: ready
DRAM: ECC disabled 128 MiB
NAND: 256 MiB
MMC: zynq_sdhci: 0
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
int board_late_init(void)+++++
buzzer_off---------------
buzzer_on---------------
buzzer_off---------------
int board_late_init(void)-----
Net: Gem.e000b000
Hit any key to stop autoboot: 0
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
USB1: ULPI request timed out
zynq ULPI viewport init failed
lowlevel init failed
scanning usb for storage devices... 0 Storage Device(s) found
Copying Linux from USB to RAM...
** Bad device usb 0 **
** Bad device usb 0 **
Copying Linux from NAND flash to RAM...
NAND read: device 0 offset 0x780000, size 0x400000
4194304 bytes read: OK
NAND read: device 0 offset 0xb80000, size 0x80000
524288 bytes read: OK
## Booting kernel from Legacy Image at 02080000 ...
Image Name: Linux-3.19.1-omg-xilinx-svn32835
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3016264 Bytes = 2.9 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Flattened Device Tree blob at 02000000
Booting using the fdt blob at 0x2000000
EHCI failed to shut down host controller.
Loading Kernel Image ... OK
Loading Device Tree to 06d0e000, end 06d14ec2 ... OK
Starting kernel ...
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 3.19.1-omg-xilinx-svn32835 (david@david-virtual-machine) (gcc version 4.7.2 (Sourcery CodeBench Lite 2012.09-104) ) #13 SMP PREEMPT Sat May 5 08:53:46 CST 2018
[ 0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine model: Zynq Zed Development Board
[ 0.000000] cma: Reserved 16 MiB at 0x09000000
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] PERCPU: Embedded 9 pages/cpu @48e92000 s8128 r8192 d20544 u36864
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 40640
[ 0.000000] Kernel command line: console=ttyPS0,115200 root=/dev/mtdblock5 rootfstype=cramfs init=/linuxrc earlyprintk uboot_version=2
[ 0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Memory: 139680K/163840K available (3872K kernel code, 213K rwdata, 1568K rodata, 196K init, 216K bss, 7776K reserved, 16384K cma-reserved, 0K highmem)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
[ 0.000000] vmalloc : 0x4a800000 - 0xff000000 (2888 MB)
[ 0.000000] lowmem : 0x40000000 - 0x4a000000 ( 160 MB)
[ 0.000000] pkmap : 0x3fe00000 - 0x40000000 ( 2 MB)
[ 0.000000] modules : 0x3f000000 - 0x3fe00000 ( 14 MB)
[ 0.000000] .text : 0x40008000 - 0x40558638 (5442 kB)
[ 0.000000] .init : 0x40559000 - 0x4058a000 ( 196 kB)
[ 0.000000] .data : 0x4058a000 - 0x405bf6e0 ( 214 kB)
[ 0.000000] .bss : 0x405bf6e0 - 0x405f5954 ( 217 kB)
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
[ 0.000000] L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
[ 0.000000] L2C-310 erratum 769419 enabled
[ 0.000000] L2C-310 enabling early BRESP for Cortex-A9
[ 0.000000] L2C-310 full line of zeros enabled for Cortex-A9
[ 0.000000] L2C-310 ID prefetch enabled, offset 1 lines
[ 0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled
[ 0.000000] L2C-310 cache controller enabled, 8 ways, 512 kB
[ 0.000000] L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
[ 0.000000] slcr mapped to 4a804000
[ 0.000000] zynq_clock_init: clkc starts at 4a804100
[ 0.000000] Zynq clock init
[ 0.000010] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 3298534883328ns
[ 0.000128] timer #0 at 4a806000, irq=17
[ 0.000481] Console: colour dummy device 80x30
[ 0.000500] Calibrating delay loop... 1332.01 BogoMIPS (lpj=6660096)
[ 0.090269] pid_max: default: 32768 minimum: 301
[ 0.090420] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.090437] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.091053] CPU: Testing write buffer coherency: ok
[ 0.091241] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.091313] Setting up static identity map for 0x3a6188 - 0x3a61e0
[ 0.240257] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.240332] Brought up 2 CPUs
[ 0.240352] SMP: Total of 2 processors activated (2664.03 BogoMIPS).
[ 0.240361] CPU: All CPU(s) started in SVC mode.
[ 0.240860] devtmpfs: initialized
[ 0.241562] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[ 0.247087] NET: Registered protocol family 16
[ 0.249034] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.271072] cpuidle: using governor ladder
[ 0.301037] cpuidle: using governor menu
[ 0.309296] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[ 0.309311] hw-breakpoint: maximum watchpoint size is 4 bytes.
[ 0.309443] zynq-ocm f800c000.ocmc: ZYNQ OCM pool: 256 KiB @ 0x4a880000
[ 0.320059] vgaarb: loaded
[ 0.320491] SCSI subsystem initialized
[ 0.320904] usbcore: registered new interface driver usbfs
[ 0.320996] usbcore: registered new interface driver hub
[ 0.321126] usbcore: registered new device driver usb
[ 0.321276] phy0 supply vcc not found, using dummy regulator
[ 0.321372] phy1 supply vcc not found, using dummy regulator
[ 0.321496] --------------usb_udc_init ------
[ 0.321762] pps_core: LinuxPPS API ver. 1 registered
[ 0.321775] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti[member=183778]linux[/member].it>
[ 0.321826] PTP clock support registered
[ 0.321975] EDAC MC: Ver: 3.0.0
[ 0.323433] Switched to clocksource arm_global_timer
[ 0.335124] NET: Registered protocol family 2
[ 0.335898] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.335939] TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
[ 0.335990] TCP: Hash tables configured (established 2048 bind 2048)
[ 0.336037] TCP: reno registered
[ 0.336055] UDP hash table entries: 256 (order: 1, 8192 bytes)
[ 0.336085] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[ 0.336282] NET: Registered protocol family 1
[ 0.336591] RPC: Registered named UNIX socket transport module.
[ 0.336604] RPC: Registered udp transport module.
[ 0.336613] RPC: Registered tcp transport module.
[ 0.336621] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.336970] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
[ 0.338305] futex hash table entries: 512 (order: 3, 32768 bytes)
[ 0.339882] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[ 0.340843] io scheduler noop registered
[ 0.340862] io scheduler deadline registered
[ 0.340915] io scheduler cfq registered (default)
[ 0.342896] dma-pl330 f8003000.dmac: Loaded driver for PL330 DMAC-241330
[ 0.342918] dma-pl330 f8003000.dmac: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[ 0.343367] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 145, base_baud = 2500000) is a xuartps
[ 0.917584] console [ttyPS0] enabled
[ 0.921720] xdevcfg f8007000.devcfg: ioremap 0xf8007000 to 4a878000
[ 0.928486] [drm] Initialized drm 1.1.0 20060810
[ 0.940739] brd: module loaded
[ 0.947628] loop: module loaded
[ 0.956223] libphy: MACB_mii_bus: probed
[ 1.033564] macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 149 (00:0a:35:00:01:22)
[ 1.043462] macb e000b000.ethernet eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:1e, irq=-1)
[ 1.055011] i2c /dev entries driver
[ 1.060195] rtc-ds1307 0-0068: rtc core: registered ds1340 as rtc0
[ 1.066640] cdns-i2c e0004000.i2c: 400 kHz mmio e0004000 irq 143
[ 1.073933] zynq-edac f8006000.memory-controller: ecc not enabled
[ 1.080149] Xilinx Zynq CpuIdle Driver started
[ 1.085215] ledtrig-cpu: registered to indicate activity on CPUs
[ 1.092190] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[ 1.098498] nand: Micron MT29F2G08ABAEAWP
[ 1.102478] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 1.110070] nand: WARNING: pl353-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
[ 1.121573] Bad block table found at page 131008, version 0x01
[ 1.127844] Bad block table found at page 130944, version 0x01
[ 1.133967] 11 ofpart partitions found on MTD device pl353-nand
[ 1.139815] Creating 11 MTD partitions on "pl353-nand":
[ 1.145071] 0x000000000000-0x000000780000 : "fsbl"
[ 1.150867] 0x000000780000-0x000000b80000 : "kerneldata"
[ 1.157124] 0x000000b80000-0x000000c00000 : "device-tree"
[ 1.163411] 0x000000c00000-0x000001100000 : "Manufacturedata"
[ 1.170098] 0x000001100000-0x000001600000 : "reserved1"
[ 1.176294] 0x000001600000-0x000003e00000 : "rootfs"
[ 1.182152] 0x000003e00000-0x000004800000 : "firmdata0"
[ 1.188269] 0x000004800000-0x000006c00000 : "siglent"
[ 1.194289] 0x000006c00000-0x00000d000000 : "datafs"
[ 1.200256] 0x00000d000000-0x00000da00000 : "log"
[ 1.205905] 0x00000da00000-0x000010000000 : "upgrade_cramdisk"
[ 1.214709] TCP: cubic registered
[ 1.217961] NET: Registered protocol family 17
[ 1.222628] Registering SWP/SWPB emulation handler
[ 1.229223] rtc-ds1307 0-0068: setting system clock to 2018-06-30 16:36:51 UTC (1530376611)
[ 1.242527] cramfs_fill_nand blocks is 320-----------------------
[ 1.242527]
[ 1.242527]
[ 1.242527]
[ 1.255562] VFS: Mounted root (cramfs filesystem) readonly on device 31:5.
[ 1.262413] devtmpfs: mounted
[ 1.265628] Freeing unused kernel memory: 196K (40559000 - 4058a000)
Starting rcS...
[ 1.539847] UBI-1: ubi_attach_mtd_dev:attaching mtd7 to ubi1
[ 1.687520] UBI-1: scan_all:scanning is finished
[ 1.698499] UBI-1 warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 3, need 40
[ 1.709601] UBI-1: ubi_attach_mtd_dev:attached mtd7 (name "siglent", size 36 MiB)
[ 1.717060] UBI-1: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 1.725645] UBI-1: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 1.734168] UBI-1: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[ 1.742853] UBI-1: ubi_attach_mtd_dev:good PEBs: 288, bad PEBs: 0, corrupted PEBs: 0
[ 1.750624] UBI-1: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[ 1.759575] UBI-1: ubi_attach_mtd_dev:max/mean erase counter: 2/0, WL threshold: 4096, image sequence number: 900188599
[ 1.770360] UBI-1: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 288, PEBs reserved for bad PEB handling: 3
[ 1.781249] UBI-1: ubi_thread:background thread "ubi_bgt1d" started, PID 574
[ 1.783663] UBI-2: ubi_attach_mtd_dev:attaching mtd6 to ubi2
[ 1.827744] UBI-2: scan_all:scanning is finished
[ 1.838539] UBI-2 warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 9, need 40
[ 1.849552] UBI-2: ubi_attach_mtd_dev:attached mtd6 (name "firmdata0", size 10 MiB)
[ 1.857174] UBI-2: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 1.865775] UBI-2: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 1.874299] UBI-2: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[ 1.882984] UBI-2: ubi_attach_mtd_dev:good PEBs: 80, bad PEBs: 0, corrupted PEBs: 0
[ 1.890656] UBI-2: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[ 1.899617] UBI-2: ubi_attach_mtd_dev:max/mean erase counter: 2/1, WL threshold: 4096, image sequence number: 1004679339
[ 1.910490] UBI-2: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 80, PEBs reserved for bad PEB handling: 9
[ 1.921298] UBI-2: ubi_thread:background thread "ubi_bgt2d" started, PID 578
[ 1.925091] UBI-3: ubi_attach_mtd_dev:attaching mtd9 to ubi3
[ 1.967761] UBI-3: scan_all:scanning is finished
[ 1.978551] UBI-3 warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 9, need 40
[ 1.989580] UBI-3: ubi_attach_mtd_dev:attached mtd9 (name "log", size 10 MiB)
[ 1.996677] UBI-3: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 2.005277] UBI-3: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 2.013829] UBI-3: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[ 2.022489] UBI-3: ubi_attach_mtd_dev:good PEBs: 80, bad PEBs: 0, corrupted PEBs: 0
[ 2.030160] UBI-3: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[ 2.039119] UBI-3: ubi_attach_mtd_dev:max/mean erase counter: 2/1, WL threshold: 4096, image sequence number: 1800024413
[ 2.050011] UBI-3: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 80, PEBs reserved for bad PEB handling: 9
[ 2.060797] UBI-3: ubi_thread:background thread "ubi_bgt3d" started, PID 582
[ 2.062964] UBI-0: ubi_attach_mtd_dev:attaching mtd8 to ubi0
[ 2.461604] UBI-0: scan_all:scanning is finished
[ 2.473888] UBI-0: ubi_attach_mtd_dev:attached mtd8 (name "datafs", size 100 MiB)
[ 2.481311] UBI-0: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 2.489969] UBI-0: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 2.498464] UBI-0: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[ 2.507164] UBI-0: ubi_attach_mtd_dev:good PEBs: 800, bad PEBs: 0, corrupted PEBs: 0
[ 2.514917] UBI-0: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[ 2.523870] UBI-0: ubi_attach_mtd_dev:max/mean erase counter: 2/1, WL threshold: 4096, image sequence number: 1599474356
[ 2.534743] UBI-0: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 800, PEBs reserved for bad PEB handling: 40
[ 2.545718] UBI-0: ubi_thread:background thread "ubi_bgt0d" started, PID 586
[ 2.559346] UBIFS: background thread "ubifs_bgt1_0" started, PID 589
[ 2.591019] UBIFS: recovery needed
[ 2.613820] UBIFS: recovery completed
[ 2.617495] UBIFS: mounted UBI device 1, volume 0, name "siglent"
[ 2.623551] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 2.632656] UBIFS: FS size: 34410496 bytes (32 MiB, 271 LEBs), journal size 4952064 bytes (4 MiB, 39 LEBs)
[ 2.642328] UBIFS: reserved for root: 0 bytes (0 KiB)
[ 2.647374] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 1B35F70A-67F4-455E-858F-2F422846CECF, small LPT model
[ 2.731478] UBIFS: mounted UBI device 2, volume 0, name "firm0", R/O mode
[ 2.738227] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 2.747357] UBIFS: FS size: 7237632 bytes (6 MiB, 57 LEBs), journal size 1650688 bytes (1 MiB, 13 LEBs)
[ 2.756753] UBIFS: reserved for root: 0 bytes (0 KiB)
[ 2.761783] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 448AD2DE-5809-49DA-B1CD-2C0D40CAB686, small LPT model
[ 2.775686] UBIFS: background thread "ubifs_bgt3_0" started, PID 592
[ 2.807286] UBIFS: recovery needed
[ 2.830050] UBIFS: recovery completed
[ 2.833738] UBIFS: mounted UBI device 3, volume 0, name "log"
[ 2.839410] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 2.848563] UBIFS: FS size: 7237632 bytes (6 MiB, 57 LEBs), journal size 1650688 bytes (1 MiB, 13 LEBs)
[ 2.857950] UBIFS: reserved for root: 0 bytes (0 KiB)
[ 2.862991] UBIFS: media format: w4/r0 (latest is w4/r0), UUID B840F246-98FF-4F06-BE7D-E132F60B19EF, small LPT model
[ 2.876123] UBIFS: background thread "ubifs_bgt0_0" started, PID 594
[ 2.907633] UBIFS: recovery needed
[ 2.994601] UBIFS: recovery completed
[ 2.998279] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[ 3.004238] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 3.013351] UBIFS: FS size: 94597120 bytes (90 MiB, 745 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
[ 3.023015] UBIFS: reserved for root: 0 bytes (0 KiB)
[ 3.028070] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 291F26AC-980A-4DA3-9D84-E1F581557A7E, small LPT model
rm: can't remove '/usr/bin/siglent/usr/mass_storage/U-disk*': No such file or directory
rm: can't remove '/usr/bin/siglent/usr/tmp/*_U-disk*': No such file or directory
[ 4.043780] Unhandled fault: external abort on non-linefetch (0x818) at 0x36fc9380
Bus error
[ 4.070882] irq = 170
[ 4.081429] <<-GTP-INFO->> GTP driver installing...
[ 4.086502] <<-GTP-INFO->> GTP Driver Version: V2.4<2014/11/28>
[ 4.092358] <<-GTP-INFO->> GTP Driver Built[member=136418]22[/member]:06:06, Apr 27 2018
[ 4.098487] <<-GTP-INFO->> GTP I2C Address: 0x14
[ 4.103081] 0-0014 supply vdd_ana not found, using dummy regulator
[ 4.109362] 0-0014 supply vcc_i2c not found, using dummy regulator
[ 4.115606] <<-GTP-INFO->> Guitar reset
[ 4.243928] <<-GTP-INFO->> IC Version: 928_1060
[ 4.254344] <<-GTP-INFO->> X_MAX: 1024, Y_MAX: 600, TRIGGER: 0x00
[ 4.273459] <<-GTP-INFO->> create proc entry gt9xx_config success
[ 4.279740] input: goodix-ts as /devices/virtual/input/input0
[ 4.285735] <<-GTP-INFO->> GTP works in interrupt mode.
[ 4.323262] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 4.334157] ehci-pci: EHCI PCI platform driver
[ 4.381946] e0002000.usb supply vbus not found, using dummy regulator
[ 4.388855] ci_hdrc ci_hdrc.0: EHCI Host Controller
[ 4.393754] ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 1
[ 4.413538] ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00
[ 4.419044] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 4.425829] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 4.432993] usb usb1: Product: EHCI Host Controller
[ 4.437921] usb usb1: Manufacturer: Linux 3.19.1-omg-xilinx-svn32835 ehci_hcd
[ 4.445039] usb usb1: SerialNumber: ci_hdrc.0
[ 4.450186] hub 1-0:1.0: USB hub found
[ 4.453952] hub 1-0:1.0: 1 port detected
[ 4.458822] e0003000.usb supply vbus not found, using dummy regulator
[ 4.518256] usbcore: registered new interface driver usb-storage
[ 4.545611] usbcore: registered new interface driver usbhid
[ 4.551119] usbhid: USB HID core driver
[ 4.561849] mousedev: PS/2 mouse device common for all mice
###### Config vdma3 for wave transform for vnc #######
0x00000000
###### Config vdma3 done
###### Config vdma3 for wave transform for vnc #######
0x00000000
###### Config vdma3 done
ln: /usr/bin/siglent/config/www/web_img/usr: File exists
Starting Lighttpd Web Server: [ 4.930257] random: lighttpd urandom read with 17 bits of entropy available
Initializing framebuffer device /dev/fb0...
xres=1024, yres=600, xresv=1024, yresv=600, xoffs=0, yoffs=0, bpp=16[ 4.982700] input: PolyVision Touch Screen as /devices/virtual/input/input1
Initializing touch device /dev/input/event0 ...
Initializing touch device /dev/input/event0 ...
Reading From :(goodix-ts)
buttonMask: xmin:0
xmax: 1024
ymin:0
ymax: 600
Initializing VNC server:
width: 1024
height: 600
bpp: 16
port: 5900
Initializing server...
30/06/2018 16:36:55 Listening for VNC connections on TCP port 5900
lighttpd.
rcS Complete
(none) login: [ 7.255606] <<-GTP-INFO->> System resume.
[ 7.255617] gpio-963 (GTP INT IRQ): _gpiod_direction_output_raw: tried to set a GPIO tied to an IRQ as output
[ 7.273650] <<-GTP-INFO->> GTP wakeup sleep.
[ 7.273660] gpio-963 (GTP INT IRQ): _gpiod_direction_output_raw: tried to set a GPIO tied to an IRQ as output
rotationAngle: 0 invertx: false inverty: false
rotationAngle: 0 invertx: false inverty: false
[1B][32mInfo: ../../ecomb2.0A/ecomb/main.cpp 50 msg: main start[1B][0m
[1B][32mInfo: ../../ecomb2.0A/ecomb/collectdata/Driver/ZynqDriver/HwAcess/ecomb_hw[ 7.866402] spidev spi1.1: setup: unsupported mode bits e8
access.cpp 68 msg: open(Spi0Dev1Name, O_RDWR) sucess !!! /dev/spidev0.1[1B][0m
[1B][32mInfo: ../../ecomb2.0A/ecomb/collectdata/Driver/ZynqDriver/HwAcess/ecomb_hwaccess.cpp 94 msg: open(Spi1DevName, O_RDWR) sucess !!! /dev/spidev1.1[1B][0m
[1B][32mInfo: ../../ecomb2.0A/ecomb/collectdata/Driver/ZynqDriver/HwAcess/ecomb_hwaccess.cpp 117 msg: open(i2c0DevName, O_RDWR) sucess !!! /dev/i2c-0[1B][0m
Len = Check_WriteFlag(addr) == 7
info[i].keyword == 1015
info[i].license == n27a9nd3d8tembmw
info[i].RemainTime == 0
info[i].keyword == AMK
info[i].license == z23g22puf442pzfx
info[i].RemainTime == 0
info[i].keyword == EMI
info[i].license == gpgwxvg3nssg7pv9
info[i].RemainTime == 0
info[i].keyword == DTF
info[i].license == cum6sna36ijz3e9d
info[i].RemainTime == 0
info[i].keyword == VNA
info[i].license == 622si3crra2in5ny
info[i].RemainTime == 0
info[i].keyword == tTG
info[i].license == akd28gtcs5kfp5mr
info[i].RemainTime == 7650
info[i].keyword == tDMA
info[i].license == 2ba7jn2tz7srx4sk
info[i].RemainTime == 7650
sh: service: not found
udhcpc: started, v1.26.0.git
Setting IP address 0.0.0.0 on eth0
udhcpc: sending discover
udhcpc: sending discover
udhcpc: sending discover
udhcpc: no lease, failing
FpgaBase::get_instance().FpgaWrite(0x124, 0); FpgaBase::get_instance().FpgaWrite(0x124, 0); FpgaBase::get_instance().FpgaWrite(0x124, 0);
Hmc703PLL1Read(0x3, &val) == 0x4b
PLL1_Driver::Inital()!!
[1B][32mInfo: true english[1B][0m
[1B][32mInfo: true[1B][0m
+++++++++AnalyzerWidget::initCollectInfo()
case msgSetFreqAndBw m_normalFreqAndBwInfo.startFreq== 0, m_normalFreqAndBwInfo.stopFreq== 1500000000, m_normalFreqAndBwInfo.span == 1500000000
msgSetFreqAndBw 33333333333333333333
___________________----m_freqCounter.enable == 0
-----------------AnalyzerWidget::initCollectInfo()
[1B][33mWarn: QObject::connect: No such slot AnalyzerWidget::dealDemodModez()[1B][0m
[1B][33mWarn: QObject::connect: No such slot AnalyzerWidget::dealDemodEarphone()[1B][0m
[1B][33mWarn: QObject::connect: No such signal AnalyzerScpi::uiPlotsetMeasBWDispAmpt(double, double)[1B][0m
[1B][32mInfo: __arm__[1B][0m
[1B][32mInfo: ../../ecomb2.0A/ecomb/collectdata/Driver/ZynqDriver/HwAcess/axi_dma_driver.cpp 44 msg: open dev sucess !!! /dev/siglent_axidma[1B][0m[ 23.458073] ######################### usb_gadget_probe_driver 3f085598 ##################
initFFTDetector m_bukectNum == 751
initFFTDetector m_rawDataNum == 4501
initFFTDetector decList.size == 751
initFFTDetector decList.max == 45[ 23.477479] usbtmc_bind+++
00
[1B][32mInfo: ../../ecomb2.0A/ecomb/drivers/GpioIntr/EcombZynq/[ 23.485668] SIGLENT_DEV: SIGLENT_DEV, version: 2007 OCT 06
keyboard.cpp 38 msg: #######Enter KeyBoard[1B][0m
[1B][32mInfo: ../..[ 23.495805] usbtmc_open()++
/ecomb2.0A/ecomb/drivers/GpioIntr/EcombZynq/miscintr.cpp 13 msg:[ 23.503075] dev->usbtmc_cdev_open ret = 0
#######Enter MiscIntr[1B][0m
NormalDetector::SetRawDataInfo m_raw[ 23.512843] ret = 0
DataFreqStart == 0, m_step== 333333.333333,m_rawDataLength== 45[ 23.521170] usbtmc_open--
01
NormalDetector::SetRawDataInfo m_DecList.size() == 751, m_D[ 23.528635] show_send_buffer_size = 61440
ecList[0]== 2, m_DecList[m_DecList.size(0-1)]== 4500
[ 124.515493] random: nonblocking pool is initialized
Copying Linux from USB to RAM...
** Bad device usb 0 **
** Bad device usb 0 **
[ 586.143456] cdns-i2c e0004000.i2c: timeout waiting on completion
[ 586.323466] cdns-i2c e0004000.i2c: timeout waiting on completion
[ 586.503466] cdns-i2c e0004000.i2c: timeout waiting on completion
[ 591.513540] usb 1-1: new low-speed USB device number 2 using ci_hdrc
[ 591.688016] usb 1-1: New USB device found, idVendor=045e, idProduct=0732
[ 591.697386] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 591.704549] usb 1-1: Product: Microsoft® Digital Media oard 3000
[ 591.710579] usb 1-1: Manufacturer: Microsoft
[ 591.735066] input: Microsoft Microsoft® Digital Media oard 3000 as /devices/soc0/amba/e0002000.usb/ci_hdrc.0/usb1/1-1/1-1:1.0/0003:045E:0732.0001/input/input2
[ 591.823781] hid-generic 0003:045E:0732.0001: input: USB HID v1.11 Keyboard [Microsoft Microsoft® Digital Media oard 3000] on usb-ci_hdrc.0-1/input0
[ 591.856938] input: Microsoft Microsoft® Digital Media oard 3000 as /devices/soc0/amba/e0002000.usb/ci_hdrc.0/usb1/1-1/1-1:1.1/0003:045E:0732.0002/input/input3
[ 591.923845] hid-generic 0003:045E:0732.0002: input: USB HID v1.11 Device [Microsoft Microsoft® Digital Media oard 3000] on usb-ci_hdrc.0-1/input1
before sleep 0.1S
sleep 0.5S
shut down
[00]
Umm, it's dumping out license strings... :o
Listening for VNC connections on TCP port 5900Now, that's pretty neat if it actually works!!!
[...]
But anything in the ISM band and 802.11ac WIFI is out. Other applications like RADAR are out, too, but those are not the target segment for this kind of device anyway.
[...]
Let's do a little summary on what kinds of applications this 1.5 GHz VNA would be useable. The ones I can think of at this moment:
- RF wireless remote controls (433 MHz is common)
- FM radio
- Amateur radio
- 27 MHz RC electronics
- GPS (marginally)
- UHF based CCTV cameras
- GSM radios
- RFID
Lots of applications really. But anything in the ISM band and 802.11ac WIFI is out. Other applications like RADAR are out, too, but those are not the target segment for this kind of device anyway.
Maybe others can chime in on what kind of applications this would be good for so that people can make better decisions :)
@ joeqsmith
So does this instrument interest you more that the existing SSA3000X models ?
Very nice, really helpful to see them side by side like that. Did you do a sneaky mirror on the images to make them match?
[...]yet highly surprisingly it's not located directly at the port but behind a switch and an impedance matching network / attenuator. I wonder how good the isolation/directivity characteristics of the circuitry are. If you look at the efforts the "big brands" in their boat anchors took some 25+ years ago to achieve really good directivity (see attached photo of an opened-up coupler of a HP 85046B test set, belonging to a 8753C VNA), it's hard to believe that despite all the advances in microcircuitry, manufacturers were able to shrink an assembly that much without sacrificing some quality/performance... I may be wrong, though ;).
What's also quite peculiar is that apparently Siglent got away with a single receiver channel. In order to get a proper phase relation between the measured signal from the DUT and the output signal provided by the VNA, the VNA would have to make a correlation of a portion of the generator signal to the measurement signal. For that purpose, "classic" VNAs have at least two input channels, one of them labeled "R" for "Reference". Since the SVA1015X clearly has only a single channel (with some switching circuitry albeit), it must manage the comparison between reference and measurement signal via that single channel in a multiplexed manner, making sure that the generator's phase is stable enough while "looking" at the measurement signal that no siginificant phase error is introduced during that timeLooks like the same principle as Henriks's 200€ VNA:
Does the VNA option include the calibration KIT?
In Dave's video at 19:02, there's a close-up of the Port1 interface shown. Since I didn't quite believe that Siglent got along without a directional coupler for their VNA functionality, I dared to have a closer look, see the attached screenshot. There is a tiny multilayer coupler installed (similar to this one https://www.mouser.de/datasheet/2/400/tdk_02022018_HHM22152A2_ver4_1(Oct.2017)-1284660.pdf (https://www.mouser.de/datasheet/2/400/tdk_02022018_HHM22152A2_ver4_1(Oct.2017)-1284660.pdf)
Doesn’t require a full second receiver, all you need is to compare the phase out of the tracking generator to the phase at the input port.
Dave, thanks for the teardown, that was quite interesting.
In Dave's video at 19:02, there's a close-up of the Port1 interface shown. Since I didn't quite believe that Siglent got along without a directional coupler for their VNA functionality, I dared to have a closer look, see the attached screenshot. There is a tiny multilayer coupler installed (similar to this one https://www.mouser.de/datasheet/2/400/tdk_02022018_HHM22152A2_ver4_1(Oct.2017)-1284660.pdf (https://www.mouser.de/datasheet/2/400/tdk_02022018_HHM22152A2_ver4_1(Oct.2017)-1284660.pdf)), yet highly surprisingly it's not located directly at the port but behind a switch and an impedance matching network / attenuator. I wonder how good the isolation/directivity characteristics of the circuitry are. If you look at the efforts the "big brands" in their boat anchors took some 25+ years ago to achieve really good directivity (see attached photo of an opened-up coupler of a HP 85046B test set, belonging to a 8753C VNA), it's hard to believe that despite all the advances in microcircuitry, manufacturers were able to shrink an assembly that much without sacrificing some quality/performance... I may be wrong, though ;).
In contrary to the high bandwidth SSA3000 series, Siglent doesn't use the special Rogers (or equivalent) high frequency PCB material but rather some impedance-controlled FR4.
Yes, in principle you are right. But how does one (the instrument) "know" the phase at the tracking generator output?. After all the mixers, gain blocks and filters, even though in theory it may be possible to calculate it, you can not be sure to even getting close to the accuracy required for a VNA to provide reasonable results. You've just got to take a part of the output signal and analyze it to get the required phase information.I don't know how the Siglent in particular does it.
[...]
As to phase stability, Siglent does not specify it but you can probably measure it yourself and see how much/minute it drifts after a calibration.
It has to be said that the quality of your measurements depends on the quality of your cal kit. You can't measure a return loss of 50dB if your load has a return loss of 40dB! If you do measure 50dB after calibrating with a 40dB load, all you can say is the return loss is 40dB or better, subject to the VNA's measurement uncertainties.
It has to be said that the quality of your measurements depends on the quality of your cal kit. You can't measure a return loss of 50dB if your load has a return loss of 40dB! If you do measure 50dB after calibrating with a 40dB load, all you can say is the return loss is 40dB or better, subject to the VNA's measurement uncertainties.
Actually I think that the "quality of your measurements depends on the quality of the characterisation of your cal kit ".
As long as you have good data for your kit, then theoretically the actual standards themselves don't matter much.
Particularly true now that full S param files can be used on a computer, instead of the C0,C1 etc in approximate curve fitting in the VNA.
You can literally use anything as long as you have an S param file for it.
I'd start with a wider span next time so you can actually see the true resonant frequency. It's always nice to see that "dip" on the screen.Great idea, thanks.
No, the monopole on the hockey stick.
Yeah I know, it's shit.No, the monopole on the hockey stick.
So this one?
(https://www.eevblog.com/forum/index.php?action=dlattach;topic=105612.0;attach=479891;image)
Do you have a better picture of the actual antenna or is it just a piece of metal sticking upright? Where is the coax shield connected?
You can easily convert it to a groundplane antenna by using 3 or 4 equal length wires connected to the coax shield and pointing down like this:
(https://www.handelsondernemingveenstra.nl/4869-large_default/gpa-66-108.jpg)
I still think your SWR sucks…
One more thing: the angle of the radial(s) should be about 45o for an impedance of 50 Ohm.Thanks.
I still think calling it a 'monopole' where your second pole is the ground plane is weird, but anyway…Call it a whip then and what's your advice to improve it's performance ?
Please keep in mind that the link points to a 2.4Ghz antenna, your ground plane needs to be 10 times bigger to be as effective. Also, it radiates slightly upwards and I don't think you want that? A vertical dipole radiates horizontally.
Whoops, I haven't got it shipped yet but I bought a Siglent SSA3021X....SVA1015X is already the top BW model in this range so I'm fairly sure BW can't be improved. Owning both (as demo models) they're aimed at different markets due to their differing capability. If the VNA capabilities are of use and 1.5 GHz is enough to meet your SA BW needs the SVA1015X is the one to go for.
Should I just tell them to ship a Siglent SVA1015X instead? Assuming we get to hack the SVA to expand the frequency range. It seems like a much more complete solution and I could definitely use the VNA options.
Damn!!!!
The most basic antenna is an open dipole, which you can mount horizontal or vertical. Horizontal will give you a radiation pattern like the figure 8, vertical will be a circle.An issue I have is it needs to receive transmissions from ~130o different directions which is why I originally settled on a monopole/whip that don't have the same directivity constraints.
So 2 1/4 wavelength elements mounted on a small isolator, coax conductor to one element and shield to the other. The problem here is to mount it on a pole, you can't tape it to a conducting pole but you should stay clear of conducting materials in the radiating direction for a few wavelengths. If you want to use a vertical dipole on the existing mast I think your best bet would be to put the dipole in a pvc tube and mount that on top of your mast, keeping it at least 20cm away from the top of the mast. The problem here is feeding the coax to the antenna without disturbing the radiation pattern.
So that is why a ground plane antenna is easier, you can simply mount it on top of the mast.
A basic J-Pole antenna might be the ideal choice here. Easy to make and easy to match and it gives a low angle of (omni) radiation.Thanks, yes maybe.
It is about 3/4 wavelength long but you can make one from 300R ribbon feeder (this is the Slim Jim folded dipole version) and hide it inside a hollow plastic tube. So you could replace the hockey stick with a longer plastic tube and put the antenna in the top section and feed the coax up the bottom of the hollow tube.
Note that the J Pole (or the Slim Jim variant) doesn't need a ground plane so this is why it might be a good choice for you here.
@tautech, I am enjoying the discussion about antennas, and I see how it is related to a VNA, but it should be more productive to move it to a new thread and keep this thread exclusively for SVA1015X discussions...I'm kind of a noob with respect to VNAs and before your post was thinking of commenting what a great idea it was for @tautech, on this sales oriented thread (or his knowledgable posters ^-^) to do this little teaching moment of what the VNA can be used for. Maybe over time I will learn enough to think I need to buy one :-+
They are easy to make although many people tend to scrimp on the RF connections and end up with something with (soldered) RF connections that will fall apart over time. Also, it's worth fitting something at the antenna feedpoint to choke RF away from the outer of the coax feedline. If it ends up inside a skinny plastic water pipe then you might as well just make the basic J Pole version as there's little/no performance advantage with the folded (Slim Jim) version. They should both radiate as an omni vertical dipole with no need for a ground plane.Yes and after enlarging the J type pic I see the gap (F) spec is OD so yes it will fit into something smaller.
I guess the alternative would be to attach ground radials to your existing monopole antenna. I don't think there will be much difference in RF performance between any of these options and it really is a case of which version you prefer to build (and look at). However, if you build it well, the J Pole version inside a plastic pipe should be the most weatherproof... but you do have to make solid connections from the coax to the antenna if you want something you can fit and forget for many years.
You should be able to fit it inside a 18mm or 22mm diameter plastic pipe. 32mm is very wide!
@tautech, I am enjoying the discussion about antennas, and I see how it is related to a VNA, but it should be more productive to move it to a new thread and keep this thread exclusively for SVA1015X discussions...Noted.
I'm kind of a noob with respect to VNAs and before your post was thinking of commenting what a great idea it was for @tautech, on this sales oriented thread (or his knowledgable posters ^-^) to do this little teaching moment of what the VNA can be used for. Maybe over time I will learn enough to think I need to buy one :-+:) Yeah it's got a bit out of hand from just a quick attempt to demonstrate how useful these VNA's can be.
Smith Chart looks so cool...Yeah and I'm still learning to use it.
@tautech: please post PICTURES of your SVA1015X unit while you experiment with new antennas and the whole tuning processIt's just a plain ordinary SVA using nothing that any hobbyist doesn't have in their RF box, maybe with the exception of a N-BNC adapter borrowed from my SSA3032X.
I think Tautech exploring the SVA1015X and his antenna is great.:)
As an example of something closer to what you're aiming for with your antenna here are two shots of a 1/4 whip antenna designed for the 70cm(430-450MHz) ham band, displayed in SWR and on a smith chart.
He left here like a dog with two tails. :D
An example which shows early preliminary measurements from a new bare J Pole antenna.
Yeah they're miles off mostly due to basic newbie mistakes that were explored yesterday with hendorog.QuoteAn example which shows early preliminary measurements from a new bare J Pole antenna.
Your early plots don't look right to me so I had a go at making a very basic J-Pole at about 315MHz.
Some progress.QuoteAn example which shows early preliminary measurements from a new bare J Pole antenna.
Your early plots don't look right to me so I had a go at making a very basic J-Pole at about 315MHz.
When someone gets the actual Siglent cal kit it would be nice to see what S21 phase looks like with both the open and short connected after performing a calibration.
When someone gets the actual Siglent cal kit it would be nice to see what S21 phase looks like with both the open and short connected after performing a calibration.
Do you mean S11 phase? The S21 phase won't be measuring anything with an open and/or short connected.
Anyway, that can be done now, without waiting for the official cal kit. This is because the Siglent cal kit characterisation data is already installed in the analyzer. So any open short and load will show exactly the same trace as the official cal kit will - as the data pre-set in the analyser defines 'what they are'.
Anything else that you measure will show a different traces if you cal with different kits. But measuring the parts in the kits themselves will show the same traces as they just reflect the cal data in the analyser.
When someone gets the actual Siglent cal kit it would be nice to see what S21 phase looks like with both the open and short connected after performing a calibration.
Do you mean S11 phase? The S21 phase won't be measuring anything with an open and/or short connected.
Anyway, that can be done now, without waiting for the official cal kit. This is because the Siglent cal kit characterisation data is already installed in the analyzer. So any open short and load will show exactly the same trace as the official cal kit will - as the data pre-set in the analyser defines 'what they are'.
Anything else that you measure will show a different traces if you cal with different kits. But measuring the parts in the kits themselves will show the same traces as they just reflect the cal data in the analyser.
Yes indeed, S11.
New firmware for SVA1015X
V2.1.1.1.12
https://www.siglentamerica.com/download/6912/ (https://www.siglentamerica.com/download/6912/)
38.8 MB
Changelog
2018/8/8
1. Spectrum Analysis mode:Improved the stability of sweep and interface.
2. VNA mode: fasten the VNA sweep speed; expand the minimum span from 10M to 10 kHz.
3. Modulation Analysis mode: add trigger, optimize the modulation analysis algorithm.
4. Add user port number selection for web server.
* Start freq for VNA still seems to be 10MHz minimum. I have tried various things but I don't think that has been resolved with this update.
>Quote from: hendorog on Yesterday at 05:34:39 pm (https://www.eevblog.com/forum/index.php?topic=105612.msg1733372#msg1733372)* Start freq for VNA still seems to be 10MHz minimum. I have tried various things but I don't think that has been resolved with this update.
When tautech posted the changelog for this update he said "expand the minimum span from 10M to 10 kHz", so that is not minimum frequency unfortunately. I wouldn't keep up your hope too high, it is probably a limitation of the hardware.
* Start freq for VNA still seems to be 10MHz minimum. I have tried various things but I don't think that has been resolved with this update.
When tautech posted the changelog for this update he said "expand the minimum span from 10M to 10 kHz", so that is not minimum frequency unfortunately. I wouldn't keep up your hope too high, it is probably a limitation of the hardware.
Successfully updated to the latest firmware using the USB.Hoping for some clarity on the minimum BW later today.
Modulation analysis does indeed to be fixed (or at least vastly improved). The totally wonky demodulated signal display is now fixed (I really should've taken a screen capture before updating - the waveform was clearly messed up in very interesting (and physically impossible) ways). I see the correct demodulated waveform now. And the deviation now appears to be giving the correct result. Woot! That makes my life much easier.
VNA is indeed much faster now. I do find it a little curious though that the span can be reduced to 10kHz despite that it seems the RBW is fixed at 10kHz (maybe I'm wrong and/or it's just a misleading display - if you go to RBW it shows 10kHz greyed-out) .
Then again why would it even be mentioned in the changelog as something Siglent has addressed ?* Start freq for VNA still seems to be 10MHz minimum. I have tried various things but I don't think that has been resolved with this update.
When tautech posted the changelog for this update he said "expand the minimum span from 10M to 10 kHz", so that is not minimum frequency unfortunately. I wouldn't keep up your hope too high, it is probably a limitation of the hardware.
Oh yes you guys are both right. I misread that point in the changelog.
I do hope it isnt a hardware limitation though. I am not sure what the problem is though - as with this architecture any phase sync errors in the plls are cancelled out.
I havent played with the scalar side yet, I will post a pic of it .
I will also have try the easy spectrum software.
Sorry typing this on phone, am replying to nautiboy as well.
Quote from: PA0PBZ on Today at 04:19:57 am (https://www.eevblog.com/forum/index.php?topic=105612.msg1734386#msg1734386)
>Quote from: hendorog on Yesterday at 05:34:39 pm (https://www.eevblog.com/forum/index.php?topic=105612.msg1733372#msg1733372)* Start freq for VNA still seems to be 10MHz minimum. I have tried various things but I don't think that has been resolved with this update.
When tautech posted the changelog for this update he said "expand the minimum span from 10M to 10 kHz", so that is not minimum frequency unfortunately. I wouldn't keep up your hope too high, it is probably a limitation of the hardware.
I think the coupler(s) may be the reason for the low er (10MHz) limit.
I am sort of surprised it works at that frequency.
Looks like a decent SA, but I am not really sure about the VNA part.
It misses the Ham market with its lower frequency limit, and misses the professional market with its upper frequency limit.
Its really over priced. Somewhere between free and $200 for the VNA option would seem about right.
Unless they can surprise us, and get the lower VNA frequency limit down to (say) 1.5MHz. The PCB material really limits the upper end.
Then again why would it even be mentioned in the changelog as something Siglent has addressed ?
I'm hoping that it's just a grammar/translation thing.
Mouse, keyboard and auto power ON demo video from Jason (Siglent USA)
Mouse, keyboard and auto power ON demo video from Jason (Siglent USA)
So boot on power on, keyboard and mouse... What was he demonstrating, a PC? ;)
rf-loop
What you see is a product of fast touchscreen demonstration with NO clear defined intent. (like some old Dave video of fast turning of knobs)
With such a swipe of a finger up and down the display both Ref and Atten levels can be affected and Jason's actions show this well.
But, when a finger is placed on the sweep waveform and raised or lowered with clear intent only the Ref level will change.
hendorog and I have just explored this issue without any attempt to adjust touchscreen properties from factory default.
Until I explore how user touchscreen settings might affect what you see in Jason's video I cannot call it a bug, only fingers working faster than mind.
Not ideal I know for an SA but a wireless mouse and keyboard works just fine with SVA.
I have my SVA back now but lost my SSA to hendorog .......again. :scared:
It looks like all is ok IF left side scale is 1 , -9, -19, -29, -39, -49*, -59, -69, -79, -89, -99
QuoteIt looks like all is ok IF left side scale is 1 , -9, -19, -29, -39, -49*, -59, -69, -79, -89, -99
I am going to go out on a limb here and say that it does show these values after the swipe.
I went back to the video and the 0's are more clearly 0's before the adjustment. After the adjustment they don't look as clear and so that makes me think that they are actually 9's.
Image attached shows two numbers. One from after change on the top, and before change on the bottom.
(These aren't from the same position in the grid, I just grabbed two which looked clear.)
I think top value is -19 and bottom value is -10
Back onto this with the VNA and some quick checks to see where I'm at before any final adjustments.Some progress.QuoteAn example which shows early preliminary measurements from a new bare J Pole antenna.
Your early plots don't look right to me so I had a go at making a very basic J-Pole at about 315MHz.
Using SSA3032X and Siglents RBSSA3X20 reflection bridge just in some effort to get the resonant frequency to close to where it needs to be.
Old whip/monopole.
(https://www.eevblog.com/forum/testgear/siglent-sva1015x-1-5ghz-spectrum-vector-network-analyzer-(coming)/?action=dlattach;attach=485327)
New J-Pole and 3m RG58 feeder.
(https://www.eevblog.com/forum/testgear/siglent-sva1015x-1-5ghz-spectrum-vector-network-analyzer-(coming)/?action=dlattach;attach=485333)
No final tuning from VNA SWR or Smith charts until hendorog is finished with the SVA.
I'm pretty happy with this, what do you RF gurus think ?
200 MHz span on 315 MHz
Running on factory CalI'm pretty happy with this, what do you RF gurus think ?
200 MHz span on 315 MHz
Did you calibrate it?
I'm pretty happy with this, what do you RF gurus think ?
Thanks.I'm pretty happy with this, what do you RF gurus think ?
I'd say well done, next project! :-+
Still pretty close but maybe just a little tweak of the feed point will get the impedance back to 50 ohms.
I don't think you are going to do much better as far as resonance and impedance matching go.hendorog did that for me a week or so back and @~3m above ground this is what he got:
Now you need to move on to modeling the antenna to determine its gain/radiation pattern to ensure that all the energy is going the way you want it to, and not straight up in the air.
Here's some real measurements, TG into input, TG ON, SA mode, direct connection with N-N cable.
(https://www.eevblog.com/forum/testgear/siglent-sva1015x-1-5ghz-spectrum-vector-network-analyzer-(coming)/?action=dlattach;attach=500852)
So it looks like the data sheet is wrong. I thought it might be.
What does the trace look like with the TG turned off?Gotcha, thanks.
In general for SAs, there isn't much point in putting a marker at 0Hz - you'll just get the LO bleed through which will show at an amplitude of its real value plus whatever attenuation is in use. In fact, you don't want to look closer to 0Hz than beyond the skirt of the RBW filter in use.
What does the trace look like with the TG turned off?Gotcha, thanks.
In general for SAs, there isn't much point in putting a marker at 0Hz - you'll just get the LO bleed through which will show at an amplitude of its real value plus whatever attenuation is in use. In fact, you don't want to look closer to 0Hz than beyond the skirt of the RBW filter in use.
As requested:
Same settings as above excepting TG OFF and 0Hz marker removed. Open input.
(https://www.eevblog.com/forum/testgear/siglent-sva1015x-1-5ghz-spectrum-vector-network-analyzer-(coming)/?action=dlattach;attach=502103)
New firmware for SVA1015X
V2.1.1.1.12a
https://www.siglentamerica.com/download/6912/ (https://www.siglentamerica.com/download/6912/)
38.8 MB
Siglent insist the datasheet TG spec of 5 MHz to 1.5 GHz is correct and they add this comment:What does the trace look like with the TG turned off?Gotcha, thanks.
In general for SAs, there isn't much point in putting a marker at 0Hz - you'll just get the LO bleed through which will show at an amplitude of its real value plus whatever attenuation is in use. In fact, you don't want to look closer to 0Hz than beyond the skirt of the RBW filter in use.
As requested:
Same settings as above excepting TG OFF and 0Hz marker removed. Open input.
(https://www.eevblog.com/forum/testgear/siglent-sva1015x-1-5ghz-spectrum-vector-network-analyzer-(coming)/?action=dlattach;attach=502103)
You can get closer to 0Hz with a smaller RBW, but it doesn't look worthwhile for this purpose. TG output seems to be getting down in the noise at around 25kHz.
The contention that the TG spec should be from 500kHz seems right to me.
You could probably use it down to 100kHz or so, but with the TG output at -15dBm and the noise at -50dBm, there's not going to be much dynamic range.
You could probably use it down to 100kHz or so, but with the TG output at -15dBm and the noise at -50dBm, there's not going to be much dynamic range.As above it seems Normalize can compensate right down to ~9 KHz, with provisos of course.
New firmware for SVA1015X
V2.1.1.1.12a
https://www.siglentamerica.com/download/6912/ (https://www.siglentamerica.com/download/6912/)
38.8 MB
Opportunity to change root password in shadow file in rootfs.cramfs in ADS file... what a mess...
But I skip at this time. Password hash is the same as in SSA3000X firmware. So ding1234 it must be.
If the Datasheet is correct, then the User Manual example needs to be corrected.Which it is.
There is a lot misleading advertising around this product it seems.
Its advertised as an SA/VNA from 9kHz to 1.5GHz.
The VNA doesn't go down to anywhere near 9kHz, off by an order of magnitude
and the TG which is really a pretty important component of the SA only goes down to 5MHz.
Except that ... its not a VNA unless you pay 50% more.Mine's fully optioned and it didn't cost a cent. :-X
I was saving my pennies to buy one, but I am becoming less and less enthusiastic.Touch base with the guys in Ohio and see if a demo unit is available.
What do you mean? Siglent is including all options at the base price?QuoteExcept that ... its not a VNA unless you pay 50% more.Mine's fully optioned and it didn't cost a cent. :-X
No.What do you mean? Siglent is including all options at the base price?QuoteExcept that ... its not a VNA unless you pay 50% more.Mine's fully optioned and it didn't cost a cent. :-X
Let me guess... a promotion is coming... :popcorn:No.What do you mean? Siglent is including all options at the base price?QuoteExcept that ... its not a VNA unless you pay 50% more.Mine's fully optioned and it didn't cost a cent. :-X
No further comment ! :-X
Not apparently:Let me guess... a promotion is coming... :popcorn:No.What do you mean? Siglent is including all options at the base price?QuoteExcept that ... its not a VNA unless you pay 50% more.Mine's fully optioned and it didn't cost a cent. :-X
No further comment ! :-X
...From my limited poking around, I think they are going to be in deep trouble if Ding ever decides to leave.
:-DD TK perhaps it's time you ask the audience or phone a friend for this one?
Seriously, I believe that Janekivi's post down the page might shed light on this. Options on many of the Siglent devices are easily liberated through root access. I'm guessing that the SVA1015X is no exception. :)
Errr, no unfortunately not. :(:-DD TK perhaps it's time you ask the audience or phone a friend for this one?
Seriously, I believe that Janekivi's post down the page might shed light on this. Options on many of the Siglent devices are easily liberated through root access. I'm guessing that the SVA1015X is no exception. :)
Working for a reseller, which I think tautech does, I would expect them to have at least one demo/test unit with full options turned on.
So he might also have also mentioned that "his" didn't cost him a penny :-)
Errr, no unfortunately not. :(:-DD TK perhaps it's time you ask the audience or phone a friend for this one?
Seriously, I believe that Janekivi's post down the page might shed light on this. Options on many of the Siglent devices are easily liberated through root access. I'm guessing that the SVA1015X is no exception. :)
Working for a reseller, which I think tautech does, I would expect them to have at least one demo/test unit with full options turned on.
So he might also have also mentioned that "his" didn't cost him a penny :-)
Any options I want from Siglent I must shell out $ but at least I get them under retail.
See post #119.
VNA function has a 10MHz lower limit. Presumably this is due to the chip coupler, but rules out 40m and below for VNA.
First post on eevblog. Hate to start off on a down note but I came into some disposable funds and was looking hard at the SVA1015X when I came across this: https://groups.io/g/svna/message/78 (https://groups.io/g/svna/message/78)Welcome to the forum.QuoteVNA function has a 10MHz lower limit. Presumably this is due to the chip coupler, but rules out 40m and below for VNA.
The SVA1015X datasheet corroborates this: VNA frequency range is 10 MHz~1.5 GHz.
No VNA operation below 10 MHz? I'm sorry but that is a major fail in my book. As a ham and electronics hobbyist I'm looking to characterize filters, baluns, chokes and other devices at HF frequencies below 10 Mhz. I realize that professional engineers today spend most of their time at frequencies several orders of magnitude higher, but even so they still deal with intermediate stages that are below 10 MHz.
Anyhow, that limit wasn't mentioned in Dave's excellent teardown/review and I didn't spot it in this thread so I thought I'd share it.
First post on eevblog. Hate to start off on a down note but I came into some disposable funds and was looking hard at the SVA1015X when I came across this: https://groups.io/g/svna/message/78 (https://groups.io/g/svna/message/78)QuoteVNA function has a 10MHz lower limit. Presumably this is due to the chip coupler, but rules out 40m and below for VNA.
The SVA1015X datasheet corroborates this: VNA frequency range is 10 MHz~1.5 GHz.
No VNA operation below 10 MHz? I'm sorry but that is a major fail in my book. As a ham and electronics hobbyist I'm looking to characterize filters, baluns, chokes and other devices at HF frequencies below 10 Mhz. I realize that professional engineers today spend most of their time at frequencies several orders of magnitude higher, but even so they still deal with intermediate stages that are below 10 MHz.
Anyhow, that limit wasn't mentioned in Dave's excellent teardown/review and I didn't spot it in this thread so I thought I'd share it.
No VNA operation below 10 MHz? I'm sorry but that is a major fail in my book. As a ham and electronics hobbyist I'm looking to characterize filters, baluns, chokes and other devices at HF frequencies below 10 Mhz. I realize that professional engineers today spend most of their time at frequencies several orders of magnitude higher, but even so they still deal with intermediate stages that are below 10 MHz.
This might not be as big of an issue if and when the software is enhanced to support S parameter exporting to a PC. Then an external coupler and a couple of mixers could be used to create a simple transverter to cover that range. Possibly the SVA reference could be used as an LO for the transverter.
The other software enhancement which would make this simpler is an OSL calibration type on port #2 instead of just on port 1.
For the adventurous it could be done without the software enhancements, by feeding the transverter output back into port 1 via a second directional coupler.
I have played with this approach on a different device as a way of converting any spectrum analyzer into a VNA.
The SA input will always have some (unwanted) LO coming out, and so the idea is to take that unwanted LO, convert it in frequency so that it matches the input of the SA, amplify it and then bounce it off a DUT. Then feed it back into the input of the SA again. The downside for an SA is that there is no reference channel, unless a solid state switch is also added. The SVA has the switch and reference channel already.
Not an out of the box solution, but it is possible.
No VNA operation below 10 MHz? I'm sorry but that is a major fail in my book. As a ham and electronics hobbyist I'm looking to characterize filters, baluns, chokes and other devices at HF frequencies below 10 Mhz. I realize that professional engineers today spend most of their time at frequencies several orders of magnitude higher, but even so they still deal with intermediate stages that are below 10 MHz.
To be fair it's difficult to make a coupler that can work all the way from LF to UHF; you basically need a balun that covers that frequency range and preserves balun action.This might not be as big of an issue if and when the software is enhanced to support S parameter exporting to a PC. Then an external coupler and a couple of mixers could be used to create a simple transverter to cover that range. Possibly the SVA reference could be used as an LO for the transverter.
The other software enhancement which would make this simpler is an OSL calibration type on port #2 instead of just on port 1.
For the adventurous it could be done without the software enhancements, by feeding the transverter output back into port 1 via a second directional coupler.
I have played with this approach on a different device as a way of converting any spectrum analyzer into a VNA.
The SA input will always have some (unwanted) LO coming out, and so the idea is to take that unwanted LO, convert it in frequency so that it matches the input of the SA, amplify it and then bounce it off a DUT. Then feed it back into the input of the SA again. The downside for an SA is that there is no reference channel, unless a solid state switch is also added. The SVA has the switch and reference channel already.
Not an out of the box solution, but it is possible.
I wouldn't bother because the accuracy will be spotty at best; keep in mind any phase drift introduced in the signal path will screw up the measurements, which is why in a proper VNA there is always a reference path. In my experience of designing VNAs the reference path must be identical to the reflected path and any mixing stages must be driven from the same LO for both paths (even two LO signals phase locked to the same clock isn't good enough), so having a transverter on the reflected path but not the reference path will really fuck up the measurements.
I don't think it's worth bothering trying to hack this because you can very easily build a much cheaper VNA that will actually be accurate; I can imagine for HF to VHF just some cheap clock gen chips plus a coupler using a cheap surface mount balun, mixers, and a stm32 with audio ADC will do fairly well. Actually that might be a good product idea.
Also I don't think any of the low cost VNAs can do SOL calibration on port 2, because they are all of the T/R type, meaning only port 1 has signal output capability. Designing a full two port VNA (and one with good port-to-port isolation) is HARD; not only do you have to have a port switch with 100dB isolation, you also have think about things like the RF signal leaking into the LO via the receive mixer and then into the other port's receiver mixer (you can't use two different LO synthesizers for the two ports for the aforementioned reasons). And to lay out everything on a board while keeping good isolation between the sig gen and the two ports, between the sig gen and the LO, between the two receivers, while keeping in mind the LO signal has to be routed to the two receivers. Only after almost a year of development did I manage to get all the details right and build a full two-port VNA with reasonable performance.
I don't see too much interest on this forum or any marketing effort (except for Tautech posting a project where He uses it) about this instrument like the Siglent Spectrum Analyzer, DSO, etc. I see a high risk of this instrument being left undeveloped any further by Siglent and even discontinued. Please, anyone with connection to Siglent, correct me if I am wrong.Considering they're only been out for 2 months :-//
Getting a frustrating OZ made ... so old now the trimmer had to go for a swim in IPA before it would behave properly. :phew:
Hi,The data sheet specs are what they are unfortunately but a SVA3kX model is coming.
any update in TG and VNA low frequency ?
After such issues with the VNA and TG low frequencies, I´m asking my self if is better to go for to SSA3021 instead.
I lost the VNA function but the TG is much better.
Any ideas about that ?
Regards
Rodrigo
Hi Taut,I’d be very surprised if the current free TG gets dropped from the SSA models, yes it was a option when they were first released but I strongly suspect due to the popularity of the SSA models it made sense for Siglent to include the most basic option TG free of charge and SVA models come with TG free at release.
probably the SVA3kX will solve all the 1015x issues, but what will be the price?
More then 2k hear in Europe, I presume.
I want to keep the value around 1,5k eur.
Just watch siglent site and the ssa3021 TG promotion finishes 12/2018,so, in few days.
I should to decide between this two models. I have some doubts about it.
Regards
Rodrigo
can someone test the latest firmware (V2.1.1.1.13)?The minimum span only, not sweep was reduced and in the previous 12a version firmware.
https://www.siglenteu.com/wp-content/uploads/dlm_uploads/2018/08/SVA1000X-Firmware-Revise-History.pdf (https://www.siglenteu.com/wp-content/uploads/dlm_uploads/2018/08/SVA1000X-Firmware-Revise-History.pdf)
Is the VNA still going from 10MHz? In the release note they mentioned changes to minimum frequency:
"VNA mode: fasten the VNA sweep speed; expand the minimum span from 10M to 10 kHz"
is there any news about the same ""procedure"" that has been done on the SSA3021X even on this model? there are a lot of cool options but the prices are a bit high for a non-professional userWelcome to the forum.
Is anything known about the new higher frequency VNA that was presented a while back?Nothing more is known other than mentioned in reply 228.....could be months away. :-//
is there any news about the same ""procedure"" that has been done on the SSA3021X even on this model? there are a lot of cool options but the prices are a bit high for a non-professional userWelcome to the forum.
I don’t know any reason why it will be different to SSA models however how I got the options out of SVA was a bit different. :-X
My SSA used the standard procedure.
Hi everyone. I usually lurk here more than post, but I thought I'd share a odd behavior of my SVA1015X that's a bit confusing.I checked this ^ with my SVA1015X and SSA3032X.
I've only recently acquired this unit, and I'm new to spectrum analyzers, so it's very possible this is user error, but I've been looking at reviews of the SSA3021 (as I haven't found too many of the SVA1015X), and those models don't seem to behave this way.
I've noticed that when the tracking generator is ON and NORMALIZE is also on, changing the CT, Start or Stop frequencies seems to cause the SA to rerun the NORMALIZE procedure, effectively cancelling out the current waveform. I am able to consistently reproduce this behavior and I am hoping someone here can clarify where I made a mistake or maybe can confirm the issue.
My setup:
.................
I guess market for lower end VNAs is not very big? If something like this would be priced so that its attractive to "average" Amateur Radio hobbyist, Siglent probably would sell orders of magnitude more....
In my opinion, it is a BUG. It should not re-normalize after you change the CF or Start/Stop frequencies. Anyway, the logical procedure sounds like to first set the CF or Start/Stop frequencies, then normalize, then insert the DUT and measure.
This is what I'd expect too but it's currently not the case so emails have been sent to look at this behavior so to address it or have the unit warn the user.In my opinion, it is a BUG. It should not re-normalize after you change the CF or Start/Stop frequencies. Anyway, the logical procedure sounds like to first set the CF or Start/Stop frequencies, then normalize, then insert the DUT and measure.
It does kind of seem that way. I would expect if you change some settings that change/effect the prior normalization it would just report that it is no longer normalized.
This is what I'd expect too but it's currently not the case so emails have been sent to look at this behavior so to address it or have the unit warn the user.In my opinion, it is a BUG. It should not re-normalize after you change the CF or Start/Stop frequencies. Anyway, the logical procedure sounds like to first set the CF or Start/Stop frequencies, then normalize, then insert the DUT and measure.
It does kind of seem that way. I would expect if you change some settings that change/effect the prior normalization it would just report that it is no longer normalized.
What do other SA's do ?
Based on the appearance of the noise in the screenshots it doesn't look to me to re-run the normalise procedure. If it was the line would be completely flat as tautech mentioned.
In fact it looks to be retaining the normalised data and using it for the reduced span, as the noise in the trace looks very similar to what it was before.
However, for some reason it is moving the trace up by 20dB. It could be that this is the real bug, perhaps something to do with the 20dB reference offset. Try again without that offset perhaps?
On my Signalhound, from memory any change to the sweep params will discard the normalised data. I think the HP 8753 VNA will 'try its best' to keep the calibration if you have interpolation turned on, but I will need to confirm that.
From a user perspective, it would be great if I didn't have to toggle the normalize for small shifts in frequency or span. If I see a part of the screen I'd like to zoom into a bit, having to disconnect the DUT each time would be pretty inefficient as I search for the best CF or span. Is this how it's done with other SA's?
Here's a video I found of a review for the SSA3032X where the author changes the span to zoom in without toggling normalize. Being able to do that would be ideal, in my opinion.
https://www.youtube.com/watch?v=Fn7uaEVeOPk, (https://www.youtube.com/watch?v=Fn7uaEVeOPk,) at 37:00
No issue here, mine works properly and I suspect it's just that rmel didn't mentioned he'd removed the 20 dB attenuation.
However, for some reason it is moving the trace up by 20dB. It could be that this is the real bug, perhaps something to do with the 20dB reference offset.
I created a video of this here:Yes, well you normally wouldn't use a SA like that, instead you'd set some reference level appropriately near mid display.
https://gfycat.com/DimEllipticalAnura (https://gfycat.com/DimEllipticalAnura)
Thanks for the suggestion. I'll take a look at that thread.Yep, well watch it again from 37.20 where Shahriar explains that changing settings will impact the normalization and he recommends once the settings are as you want then to re normalize for accurate results.
Shariar's video, however, is the one I linked above, where he does exactly what I am doing...
Sorry but using two *10 scope probes to "demo measure" with the SVA1015X's VNA function in an unpowered CB radio corpse is, well, a little "unresultful" :palm:
This RF stuff definitely isn't Defpom's business, clicking through the menus isn't what really helps someone seriously interested in a purchase. Regarding things one doesn't feel "at home" with, better do yourself a favor and let others who are more into it do this job.
Watching this clip is a waste of time, and probably producing it was even more so for Defpom. He's got much better reviews in his channel than this one...
Cheers and no offense intended :phew:
I also demonstrate a consistent hard crash mode when the VNA mode is turned on while the preamp is on in the spectrum analyzer mode. This crash requires a power cycling to reset.More so amusing. :)
I hope you find it interesting.
Chris
@graybeard
IIRC it is possible to use custom cal kit in the VNA mode of the SVA - for a competent unix user.
The cal kit definition is stored in a file on the file system, and could be backed up and modified to suit another cal kit.
Also IIRC the definitions are stored in a file as mag/phase data, so any standard which one has measurement data for can be used as a cal standard.
IMHO this is a more comprehensive method than using the traditional Cx/Lx model which is what I think you are proposing. I do agree Siglent should implement custom cal kits in the UI.
Looks like a very big jump in the UI and features!
Is there s-file export yet? Looking at the video it appears to be a csv data dump, but not in a standard s1p format. Is that correct?
Is there a plan to implement Enhanced Response calibration type?
With Enhanced Response calibration and a good attenuator, to improve load match, I believe you can get results almost as good as a full 2 port calibration.
Looks like a very big jump in the UI and features!
Is there s-file export yet? Looking at the video it appears to be a csv data dump, but not in a standard s1p format. Is that correct?
Is there a plan to implement Enhanced Response calibration type?
With Enhanced Response calibration and a good attenuator, to improve load match, I believe you can get results almost as good as a full 2 port calibration.
The data export is only CSV, there is no S1P file generated.
If I wanted a S1P file I would just set up an EXCEL or Libre Office template to do the translation.
Chris
Any chance we will see a 2-port 3GHz version any time soon?No Chinese whispers about the SVA3000X models yet other than the one spotted at Electronica last year.
Update.Any chance we will see a 2-port 3GHz version any time soon?No Chinese whispers about the SVA3000X models yet other than the one spotted at Electronica last year.
Even the beta testers that I chat to haven't seen one yet.
Some months away yet I guess. :(
Here's a snapshot of the Siglent showcase at Electronica 2018.We thought a SVA3032X was coming however recently the Chinese website has been updated to indicate a SVA1032X is actually coming.
The SVA3032X prototype analyzes a 16QAM signal produced by the new SSG3032X-IQE, which in turn is using an SDG6000X with I/Q option as the modulation source.
The display of the SVA3032X has been brought to the big monitor using the internal webserver and a notebook computer hidden under the counter ;)
(https://www.eevblog.com/forum/testgear/new-siglent-products-sds2000x-e-sva3032x-and-a-dc-load/?action=dlattach;attach=579734)
And here's the link to the new SVA1015X firmware.
Version 2.2.1.2.1
No Chinese whispers about the SVA3000X models yet other than the one spotted at Electronica last year.
Even the beta testers that I chat to haven't seen one yet.
Some months away yet I guess. :(
Well yeah that's real interesting as we know from recent info on the Chinese site SVA1032X is not too far away and it seems a 3k series is indeed coming too plus a 7k series. :oNo Chinese whispers about the SVA3000X models yet other than the one spotted at Electronica last year.
Even the beta testers that I chat to haven't seen one yet.
Some months away yet I guess. :(
BTW, no need for whispers.
This latest FW (which is quite different from previous ones) has the explanations inside: :popcorn:
SVA1015X
SVA3032X
SVA7075X :scared:
And 5 other options besides what is currently used:
RTA, RCV, SVA, NA and MA
from recent info on the Chinese site SVA1032X is not too far away
Check the Cn datasheet. ;)from recent info on the Chinese site SVA1032X is not too far away
From what I see in the latest FW, I'll bet that "SVA1032X" is a typo. However it would be great if I'm wrong...
Check the Cn datasheet. ;)
I listed some of the SVA1032X improvements a few posts back.
Check again. ;)Check the Cn datasheet. ;)
I listed some of the SVA1032X improvements a few posts back.
I understand that BUT I stand by my bet.
Hopefully the 3032 is a 1032 disguised but it won't be named 1032...
Check again. ;)
Wonder when they will take another step up and make a full 2 port machine.
hendorog,
Is your guess correct?
(https://pbs.twimg.com/media/Dr-zFNXWoAAUF0d.jpg:large)
Start Frequency in VNA Mode to 100 kHz
Of serious improvement is the reduction of the minimum frequency 10 MHz to 100 KHz in VNA mode. This is a really massive improvement as are some other additions that we've examined in detail over the last couple of weeks.
Thanks Siglent for listening, understanding and implementing.
New firmware for SVA1015X.
Version V2.2.1.2.2
https://www.siglentamerica.com/download/9346/ (https://www.siglentamerica.com/download/9346/)
37MB
Release notes
Notice:
This firmware must be upgraded from V2.1.1.1.12a or later. If your SVA1015X has an earlier version, please update to V2.1.1.1.12a first and then proceed to update to the latest version.
New Functionality:
Add a spectrum view, marker for MA Mode
Add mode couple for center frequency
Add system message
Improvements:
Start Frequency in Harmonic measurement in AMK options to 1 Hz
Start Frequency in VNA Mode to 100 kHz
Optimize .sta file, trace interpolation for VNA Mode
Optimize PSK/QAM clock sync ability for MA Mode
Solved Issues:
Fixed AVG, Math bug for VNA Mode
Fixed Date & Time set bug
Of serious improvement is the reduction of the minimum frequency 10 MHz to 100 KHz in VNA mode. This is a really massive improvement as are some other additions that we've examined in detail over the last couple of weeks.
Thanks Siglent for listening, understanding and implementing.
Ok, i joined up just to ask this. Can anyone confirm that the VNA now goes down to 10khz with the latest .2 firmware? The firmware looks like it was removed from the website, at least the north american website as far as i can find. That is a MAJOR relief for me (amateur radio operator that builds a lot of his own stuff) as i was having to track down something else sub 2k because this one couldn't go that low.
Great! Glad to see that someone has confirmed they grabbed a firmware that allows this. My mistake on the 10Khz, i see now it was 100Khz. Not a big deal as about 3.5Mhz will be the lowest i need in most cases.
Out of curiosity i called the NA office on Ohio to ask about it. The guy i spoke to seemed reserved about discussing the drop in frequency and said that "nothing official has been released" and that he could not speculate on it (nor a speculation on a 1032x). I suspect it was possibly a firmware release that had that feature in it a bit prematurely. I finally found an English copy of the release notes on the non-na website but it did not mention that change/upgrade to the VNA low side. I will see if i can find the Chinese version and see if its in there.
He did mention they did some website changes this past weekend, which may explain the dead firmware link on the NA website.
I'm ready to order at this point, just trying to make sure i can get that firmware version and it actually works.
Now we just needs some hacks for the 1015x :D
Great! Glad to see that someone has confirmed they grabbed a firmware that allows this. My mistake on the 10Khz, i see now it was 100Khz. Not a big deal as about 3.5Mhz will be the lowest i need in most cases.The firmware link was broken after I posted about the upgrade so I have replaced it with a working link to the Ohio webpage. The Release notes posted were copied and pasted directly from the SVA release notes file, they are the official notes !
Out of curiosity i called the NA office on Ohio to ask about it. The guy i spoke to seemed reserved about discussing the drop in frequency and said that "nothing official has been released" and that he could not speculate on it (nor a speculation on a 1032x). I suspect it was possibly a firmware release that had that feature in it a bit prematurely. I finally found an English copy of the release notes on the non-na website but it did not mention that change/upgrade to the VNA low side. I will see if i can find the Chinese version and see if its in there.
He did mention they did some website changes this past weekend, which may explain the dead firmware link on the NA website.
I'm ready to order at this point, just trying to make sure i can get that firmware version and it actually works.
Now we just needs some hacks for the 1015x :D
Improvements:
Start Frequency in Harmonic measurement in AMK options to 1 Hz
Improvements:
Start Frequency in Harmonic measurement in AMK options to 1 Hz
Exactly what does this mean? what is amk?
Yep, and while options for SVA have 120hrs free trial times they do eventually expire.Improvements:
Start Frequency in Harmonic measurement in AMK options to 1 Hz
Exactly what does this mean? what is amk?
Advanced Measurement Kit
I imply that the tracking gen starts at 100KHz, right?
According to the datasheet the tracking generator starts at 100kHz for both the SVA and SSA.Actually not so, we're both wrong.
SVA1015X, all the SA options should also work fine in EasySpectrum but at this time I can't confirm the VNA option does until I get my demo unit back and try it.With the current version 5 of EasySpectrum VNA mode is not available. :(
In a few days I will report on this...............
Is Siglent experiencing issues with the 3.2GHz VNA?Nope, getting one in my next order.
Announcements soon.With release of the 3.2 GHz SVA1032X there is a pricing structure change for it and SVA1015X.
Interesting to see what's Siglent's official word on SVA1015X specs.
When they launched it the lowest frequency (as quoted on the datasheet) was 10 MHz, but now it can be usable (at least for rough "antenna analysis, just show me the VSWR/RL") from 3 - 5 MHz.
I tried it with a 7 MHz loop and the results were certainly useful.
Interesting to see what's Siglent's official word on SVA1015X specs.Officially specs haven't changed.
When they launched it the lowest frequency (as quoted on the datasheet) was 10 MHz, but now it can be usable (at least for rough "antenna analysis, just show me the VSWR/RL") from 3 - 5 MHz.Correct and as a result of SVA1032X development it was decided to lower the SVA1015X VNA BW whereas before anything below 10 MHz was not even available to the user.
Does anyone offer a trade in for a SSA3032X upgrading to a SVA1032X?List it here:
Finally looked at the provided links, and saw that the firmware was for SNA1000X.
I had been using the firmware for SNA1015X (since that is what I have).
..............Please note SVA1015X datasheet specs have not changed and are still listed as 10 MHz in VNA mode and as you say we are now able to use VNA mode below 10 MHz right down to 100 KHz which is outside guaranteed accuracy however other users have reported good results down to 1-3 MHz.
Finally looked at the provided links, and saw that the firmware was for SVA1000X.
I had been using the firmware for SVA1015X (since that is what I have).
Tried the 1000X firmware ... load, re-boot, switch to VNA and lowest frequency is now 100khz!
Slightly annoying that there are two variants on the firmware with the same number that behave differently!
ETA: After a few minutes playing ... I am now MUCH happier with this device. Not covering the lower frequency ham bands was a bit of a pain (but an acceptable one given the other functionality it bought). That niggle has now gone.
I have to say that I am a bit amazed that they get this sort of performance out of those directional couplers though...
..............Please note SVA1015X datasheet specs have not changed and are still listed as 10 MHz in VNA mode and as you say we are now able to use VNA mode below 10 MHz right down to 100 KHz which is outside guaranteed accuracy however other users have reported good results down to 1-3 MHz.
Finally looked at the provided links, and saw that the firmware was for SVA1000X.
I had been using the firmware for SVA1015X (since that is what I have).
Tried the 1000X firmware ... load, re-boot, switch to VNA and lowest frequency is now 100khz!
Slightly annoying that there are two variants on the firmware with the same number that behave differently!
ETA: After a few minutes playing ... I am now MUCH happier with this device. Not covering the lower frequency ham bands was a bit of a pain (but an acceptable one given the other functionality it bought). That niggle has now gone.
I have to say that I am a bit amazed that they get this sort of performance out of those directional couplers though...
With SOL Cal at low frequencies results can be improved further than the factory saved data points.
Yes - you can see how they did this: The signal is very noisy (which is to be expected from those small directional couplers) so they just average multiple measurements. Not ideal, but at least it makes measurements possible. Specs are undoubtedly reduced below 10MHz, but so far, I think good enough for typical HAM use.hendorog and I looked at this when we got the SVA1015X beta FW and were able to get sub 0.1dB accuracy from his and Siglent VNA Cal kits.
Yes - you can see how they did this: The signal is very noisy (which is to be expected from those small directional couplers) so they just average multiple measurements. Not ideal, but at least it makes measurements possible. Specs are undoubtedly reduced below 10MHz, but so far, I think good enough for typical HAM use.hendorog and I looked at this when we got the SVA1015X beta FW and were able to get sub 0.1dB accuracy from his and Siglent VNA Cal kits.
Please tell me why did the instrument displayed what it displayed!Sorry I don't have my SVA units to check your as they are with a beta tester for study of the beta and public release SVA1015X firmware but there are a few members with these units that might give you answers.
Dear RF gurus!
For my hobby project (Zynq FPGA+ AD/DA + synthesizers,mixers, amplifiers, passives,antennas) I would like to buy either a: SVA1032X or a R&S FPC1500
Since my project is quite general I need all the T&M features I can get and these models offer a lot of them. SVA1032X has QAM demodulation feature therefore I tend to put my vote on that one, but I have a serious concern. When Shahriar reviewed the instrument he performed QAM demodulation measurements on a saturated amplifier (see attached picture). To me these results make no sense.
When the amplifier gets saturated the constellation points start to move OUTWARDS instead of INWARDS.
It looks like the I and Q components become larger then what they are during non compression. For me this is counter intuitive. I thought the low energy symbols remain (more or less) intact and the high energy symbols at the perimeter of the constellation diagram can't reach their nominal location so their distance from the origin is smaller then during non-compression.
Please tell me why did the instrument displayed what it displayed!
VNA open short load calibration bug ?Conversation entered via PM's.
Anyone else that has noted this bug 2.2.1.2.2 or am I doing something wrong...
Even if User1 is selected the unit will use info in User2 and vice versa...
/Sam
Just got my SVA1032X and getting familiar with it. I have a few questions and don't know if this thread is the right place but here goes:1) Hope so, yes just checked and Mode is not available in V6. :(
1) Easyspectrum does not give any control over the VNA (at least not by USB). Any future plans to provide this remote function?
2) Is there any way to directly save to a PC screen snapshots in VNA mode? I know I can save png to the SVA1032x internal memory and then copy it to my PC but would be much more functional to control directly to a PC
3) Using Preset and going to VNA the number of data points defaults to 201. This leads to some very choppy Smith chart graphs. To get a really smooth Smith plot you need 500-700 data points. Whats the downside to always using more data points routinely?
4) I have seen screen shots of the SVA1015x serial number and it begins with SVA, I was curious of the significance, if any, of my SVA1032x serial number starting with SSA3?
thanks in advance
Jerry NY2KW
As to my perhaps unusual serial number,Can't check with the factory until they come back from break next week.
Do you have full VNA functionality and all Mode access via the webserver ?
You may already be aware but using external software is the best way to get full control over the cal - and the models used for the standards.
QuoteYou may already be aware but using external software is the best way to get full control over the cal - and the models used for the standards.
Thanks, Not familiar with Python but I do some C programming so open to learning Python basics. I downloaded latest Windows Python then Anaconda and then installed the scikit rf module. I went through the early examples including the plots - very cool! It says scikit rf only supports a few VNA s as virtual instruments. Next steps for me is to learn how to set up my calibrations and load SVA1032X data for manipulations in scikit rf. Too bad there isn't a scikit rf GUI interface to simply things... I rather be using the SVA1032x than getting on the scikit rf learning curve.
Jerry NY2KW
Will this VNA do amplitude sweeps?
I scanned through your code. Looks like fun. What is the file format for your standards that you are reading in? For example, the file "data/ideals/KirkbySN0092" ?
I see there is a VI file that Siglent provides. I know even less about Labview, etc but wounder if the Siglent VI file could be easily modified for use in scikit-rf?
Jerry
It seems not. We need another member to test.
You tried the connection while the SVA remains in "upgrading..." mode?
Curious, @tautech didn't mention it.Versions for SVA1015X and SVA1032X models, they are each different !
New firmware.
V2.2.1.2.7 2020/05/12
Teaser for you guys with hacked SSA's to SVA's.
Real stock SVA1032X factory cal, open ports and latest FW.
Smith chart scaling.
Teaser for you guys with hacked SSA's to SVA's.
Real stock SVA1032X factory cal, open ports and latest FW.
Smith chart scaling.
Can you go into the cal menu and show a screen with the calibration in off mode? <3
Mode > VNA > Calibration Menu > Correction Off
Mode > VNA > Calibration Menu > Correction Off
That will not remove the factory cal, it only removes a user cal.
Mode > VNA > Calibration Menu > Correction Off
That will not remove the factory cal, it only removes a user cal.
That's the point, does that screen match the prior?
Siglent has some catching up to do.:-//
All SVAs and the nano V2 currently are hampered by the magnetics based coupler. It performs poorly at lower and upper frequency extremes. I'm experimenting with balun-less active reflectometer designs that can potentially give you decent directivity from DC to 6GHz. Siglent has some catching up to do.
Yes the factory cal (and ecal in the nano v2) hides the true directivity of the coupler. If the raw directivity is low, for example at very low frequencies where the balun is ineffective, the software has to subtract all the forward leakage and the result is more noise after calibration. The SVA series are architecturally very similar to the nano v2, which uses the same kind of coupler and the same method of obtaining the reference signal without an actual reference path (by using an RF switch before port 1 to short it out). I believe siglent has a custom ordered balun that can work up to 7.5GHz, but I'd be surprised if they can get 10dB raw directivity at 7GHz from that. I'd like to see the mentioned raw graphs during user cal.
I'm suspecting you can't turn off factory cal because the raw directivity of the coupler isn't very good and they don't want you to see that ;)
I also see significant trace noise around 3GHz, it looks just like the nanovna V2. That is because it doesn't have a simultaneous reference receiver and can not cancel out synthesizer phase noise.
Don't bother comparing the original Nano to this, look at the V2 instead which has far better calibration standards and the VNA itself performs basically the same as the SVA.
All SVAs and the nano V2 currently are hampered by the magnetics based coupler. It performs poorly at lower and upper frequency extremes. I'm experimenting with balun-less active reflectometer designs that can potentially give you decent directivity from DC to 6GHz. Siglent has some catching up to do.
How to import cal data in s1p format to SVA1050X ?
Or i something disunderstand?
V2.2.1.2.7 2020/05/12
Notice:
This firmware must be upgraded from V2.1.1.1.12a or later. If your SVA1000X has an earlier version, please update to V2.1.1.1.12a first and then proceed to update to the latest version.
New Functionality:
Add Limit mask offset in SA mode
Frequency LOG scale in VNA mode
Add OPEN、SHOT、enhanced response in VNA mode
Add 85033D/E Cal kit in VNA mode
Save/recall .cal file in VNA mode
Port 1 power (TG) adjustable in VNA mode
Zero span in VNA mode
Improvements:
Smooth the glitch in Phase format in VNA mode
Solved Issues:
Fixed AM and FM symbol rate error, Lpf coefficient error, in AMA mode
Fixed Filter bandwidth error in DMA mode
Fixed Freq counter error in SA mode
Fixed Harmonic error in SA mode
Help Display error
Do you think Siglent is planning a patch for the SSA to SVA hack?V2.2.1.2.7 2020/05/12
Notice:
This firmware must be upgraded from V2.1.1.1.12a or later. If your SVA1000X has an earlier version, please update to V2.1.1.1.12a first and then proceed to update to the latest version.
New Functionality:
Add Limit mask offset in SA mode
Frequency LOG scale in VNA mode
Add OPEN、SHOT、enhanced response in VNA mode
Add 85033D/E Cal kit in VNA mode
Save/recall .cal file in VNA mode
Port 1 power (TG) adjustable in VNA mode
Zero span in VNA mode
Improvements:
Smooth the glitch in Phase format in VNA mode
Solved Issues:
Fixed AM and FM symbol rate error, Lpf coefficient error, in AMA mode
Fixed Filter bandwidth error in DMA mode
Fixed Freq counter error in SA mode
Fixed Harmonic error in SA mode
Help Display error
Disappeared...
http://s000.tinyupload.com/index.php?file_id=90679722209028843386 (http://s000.tinyupload.com/index.php?file_id=90679722209028843386)
Do you think Siglent is planning a patch for the SSA to SVA hack?
Disappeared...
http://s000.tinyupload.com/index.php?file_id=90679722209028843386 (http://s000.tinyupload.com/index.php?file_id=90679722209028843386)
Do you think Siglent is planning a patch for the SSA to SVA hack?
Hello,Welcome to the forum.
I'm new on this thread as a user of my VNA from Siglent.
I just bought the SVA1032X and got strange behavior of it. The device shows some noisy signal but does not measure anything or generate a signal on tracking output...
Did anyone experience a similar problem with it? This is the fresh new device, with SW 2.2.1.2.5.
I thought there is a need for some initial password, but after a call to the seller, he confirmed not.
Thanks for any suggestions on that, before launching the official warranty return..
Thanks tautech for the prompt reply.The first screenshot is straight after a Preset which returns factory settings and full span, 10dB/div etc.
The point is that a tracking generator activates in a menu, but nothing is physically existing on the port 1 output. Also, the spectrum analyzer function is not operating - driving port 2 from the external signal source does not change observed background noise. Similarly like shorting ports together.
The Preset button, restart or factory reset from the system menu does not change device behavior.
Tomorrow I will send the unit for seller's inspection if nothing discovered during a day.
The first screen is exactly same as your after Preset.I do, it needs repair or replacement. Contact your supplier.
The second is after TG activation with shorted ports - unfortunately no change in a trace.
I use original cables ordered together with an analyzer - they are fine, just tested on a parallel instrument.
Have no idea.
Notice: This firmware must be upgraded from V2.1.1.1.12a or later. If your SVA1000X has an earlier version, please update to V2.1.1.1.12a first and then proceed to update to the latest version.
New Functionality:
• Update EMI option to a new EMI measurement mode
• Added more VNA calibration kits with N/3.5mm type connectors to 4.5G/9.0GHz
• Added *.CSA file type to store instrument setup and calibration data in one file for easy recall and use of a saved state.
• Update user calibration data format.
CAUTION:
User calibration data taken with previous firmware revisions will no longer be compatible with the instrument after upgrading to V2.8. You will have to store new user calibration files if you update the instrument.
• VNA Port 1 output power and Port2 input Att adjustable
Improvements:
• Improve TG output harmonic performance
• Update Help file
Solved Issues:
• Fix some ADC overload warning
• Fix Ch Power calculation bug in small span
There are new features they left out of the release notes, the best of which is addition of log frequency sweep in VNA mode. I love this feature!
....
New Functionality:
• Add Limit mask offset in SA mode
• Frequency LOG scale in VNA mode
• Add OPEN、 SHOT、 enhanced response in VNA mode
• Add 85033D/E Cal kit in VNA mode
• Save/recall .cal file in VNA mode
• Port 1 power (TG) adjustable in VNA mode
• Zero span in VNA mode
Improvements:
• Smooth the glitch in Phase format in VNA mode
Solved Issues:
• Fixed AM and FM symbol rate error, Lpf coefficient error, in AMA mode
• Fixed Filter bandwidth error in DMA mode
• Fixed Freq counter error in SA mode
• Fixed Harmonic error in SA mode
• Help Display error
I had upgraded my SVA1032x with v2.2.1.2.7 several weeks ago and all seemed fine. Tonight I placed v 2.2.1.2.8 onto the same USB stick (wiped) I always use and the upgrade hourglass has been rotating for more than 15 mins.It should have done its thing by now and as 2.7 was pulled it may have had some bug in it.
Any advice how to proceed?
I had upgraded my SVA1032x with v2.2.1.2.7 several weeks ago and all seemed fine. Tonight I placed v 2.2.1.2.8 onto the same USB stick (wiped) I always use and the upgrade hourglass has been rotating for more than 15 mins.All sorted ? ? ?
Any advice how to proceed?
New Functionality:A new SSAX Plus/SVA and SSAX-R User manual version E02A with chapter 7 for this new EMI mode on P134.
• Update EMI option to a new EMI measurement mode
I needed to have the impedance information from my SVA1032X VNA. Unfortunately, this device does not directly support such a format, so I attempted to connect it over TCP/IP to Matlab.
A vendor would never release a FW that flushed the calibration without the user being able to recalib by himself.Then you obviously never heard of Rigol :)
If not, all equipments around the world would have to be sent to calib...
What I read is that the calib file's format will change.
Then you obviously never heard of Rigol :)
Who knows, if the firmware update to the latest 2.2.1.2.8 version violates the existing calibration certificate? I'm worrying, that this reflash process may irreversibly overwrite some internal calibration data of the unit.The Caution only applies to existing user saved VNA Cal's and has no impact on other functionality.
Is it a safe process from this standpoint?
I found only below remark:
"CAUTION: User calibration data taken with previous firmware revisions will no longer be compatible with the instrument after upgrading to V2.8. You will have to store new user calibration files if you update the instrument", but I believe it is related to the calibration performed during OPEN-SHORT-LOAD, which could be easily repeated in a VNA mode.
What about (possible) accuracy degradation in a spectrum analyzer mode? I assume, there are some manufacturer's correction factors, which typically reduce internal errors (due to linearity, drifts etc.). Are they maintained, discarded, or switched to default ones?
Or maybe there is nothing to worry about?
Did anyone experience any degradation in the accuracy after reflash?Yes, only in VNA mode.
Notice:
This firmware must be upgraded from V2.1.1.1.12a or later. If your SVA1000X has an earlier version, please update to V2.1.1.1.12a first and then proceed to update to the latest version.
New Functionality:
Add user defined VNA calibration kits
Add VNA 0 span calibration
Solved Issues:
Fix avg power bug in EMI Mode
Fix amplitude bug in AMA Mode
Fix peak search bug in SCPI command
New Firmware-Version (V3.2.2.3.2 2020/09/18) is available for SVA3015X, SVA3032X and SVA3075X.Code: [Select]
Notice:
This firmware must be upgraded from V2.1.1.1.12a or later. If your SVA1000X has an earlier version, please update to V2.1.1.1.12a first and then proceed to update to the latest version.
New Functionality:
Add user defined VNA calibration kits
Add VNA 0 span calibration
Solved Issues:
Fix avg power bug in EMI Mode
Fix amplitude bug in AMA Mode
Fix peak search bug in SCPI command
https://int.siglent.com/download/firmwares/?CateIdss=16
That is great news - about the user defined cal kits.;D
That is great news - about the user defined cal kits.;D
Ask and you shall receive ! ;)
:PThat is great news - about the user defined cal kits.;D
Ask and you shall receive ! ;)
In that case I'm asking for the new Landrover Defender next !
Just did the firmware update.
Anyone try the User defined cal loads? The Define Load "Delay Terminal" and "Impedance" are greyed out.
Also when invoking Port Extensions with a RG142 type N 30cm cable "Auto Open Port1" returns "Delay Port1" with numbers like ~18us, and Length Port1 of ~3Km!! Before this firmware update, this provided the correct values in ps and mm!
Best,
Edit: It seems like someone messed up the calculations and is off by 6 orders of magnitude :o
Just did the firmware update.
Anyone try the User defined cal loads? The Define Load "Delay Terminal" and "Impedance" are greyed out.
I did some checking, and I can confirm that the Linux based firmware is actually running; as I can use PuTTY to Telnet into the device over the LAN, and I can now connect using the web browser. but the web browser looks crippled, as there is not much there. I tried the web interface "Firmware Update" button, which loaded the .ADS firmware file, but then immediately say the update has failed.
On a different subject, what types of RF cables are people using to connect to the DUT?Do you wanna stay with N-N type ?
I currently have a very old set of cables made with N male connectors using RG142 coax. They are quite "beat-up" (got them 2nd hand) and would like to replace them.
Is there any recommenced coax cable (sets) that people are using? Or does everybody just make their own?
If you make your own, what type of coax are you using (RG142? double-shielded?)
If this has already been discussed, my apologies.
total 15180
drwxrwxrwx 9 1000 1000 1464 Dec 30 15:40 .
drwxrwxrwx 1 1000 232 3204 Jan 1 1970 ..
-rw------- 1 root root 545 Dec 30 16:43 .ash_history
-rwxrwxrwx 1 root root 15289708 Dec 12 20:03 Aladdin
drwxrwxrwx 8 1000 1000 800 Dec 12 20:04 config
-rwxrwxrwx 1 root root 1078 Dec 12 20:03 config_eth0.sh
drwxrwxrwx 2 1000 1000 1904 Dec 12 20:04 drivers
drwxrwxrwx 6 1000 1000 888 Oct 2 14:19 firmdata0
drwxrwxrwx 2 1000 1000 160 Jan 8 2019 firmdata1
drwxrwxrwx 2 root root 688 Dec 12 20:03 lib
-rwxrwxrwx 1 root root 12068 Oct 4 14:06 lighttpd.conf
drwxrwxrwx 2 1000 1000 232 Jan 8 2019 log
-rwxrwxrwx 1 root root 67085 Oct 4 14:06 php.ini
-rwxrwxrwx 1 root root 2195 Dec 12 20:03 startup_app.sh
-rwxrwxrwx 1 root root 77 Dec 12 20:03 startup_ftp.sh
-rwxrwxrwx 1 root root 482 Dec 12 20:03 startup_vnc.sh
drwxrwxrwx 10 1000 1000 976 Dec 12 20:26 usr
-rwxrwxrwx 1 root root 490 Oct 4 14:06 vdma_vnc.sh
-rwxrwxrwx 1 1000 1000 9520 Apr 17 2018 vnc_test
-rwxrwxrwx 1 root root 29337 Dec 12 20:03 vncserver
-rwxrwxrwx 1 root root 97611 Dec 12 20:03 vsftpd
/usr/bin/siglent/Aladdin &
Filesystem Size Used Available Use% Mounted on
/dev/root 61.7M 61.7M 0 100% /
devtmpfs 68.2M 0 68.2M 0% /dev
none 76.3M 4.0K 76.3M 0% /tmp
ubi1_0 29.7M 21.3M 8.4M 72% /usr/bin/siglent
ubi2_0 5.7M 860.0K 4.9M 15% /usr/bin/siglent/firmdata0
ubi3_0 5.7M 24.0K 5.7M 0% /usr/bin/siglent/log
ubi0_0 82.8M 7.3M 75.4M 9% /usr/bin/siglent/usr
ps -ef | grep Aladdin
956 root 0:00 grep Aladdin
My wild guess:
When you do an upgrade from the USB stick, the .ADS occupies disk space in the USB disk. Then it decompresses to the filesystem upgrade dir.
When you do and upgrade via web, you must download the .ADS to the filesystem spending precious space. When it decompresses, it consumes further space...
I wonder if it is really possible to do any upgrade via web on the current SSAX+ and/or SVAs... :-//
Try to see if you any content in the filesystem's upgrade directory and delete all that content. I would assume it should start at the next reboot...
Nonetheless, I don't fully grasp what this problem could be.
Hi tuburlanut,
yes ist runs:Code: [Select]ps -ef | grep Aladdin
956 root 0:00 grep Aladdin
/usr/bin/siglent/usr/tmp # init log error[File /usr/bin/siglent/usr/tmp/config/log/log4cpp.properties does not exist]
log init finished
[ 7414.066490] spidev spi1.1: setup: unsupported mode bits f8
mac ioctl error
Udisk = U-disk0 not found notes
the u-disk sum = -1 is error
remove udisk /usr/bin/siglent/usr/mass_storage/U-disk0
not erase the udisk = U-disk0
[ 7414.154089] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
挂载U盘 /usr/bin/siglent/usr/mass_storage/U-disk0 device = /dev/sda1
udhcpc: started, v1.26.0.git
Setting IP address 0.0.0.0 on eth0
sh: write error: Device or resource busy
sh: write error: Device or resource busy
udhcpc: sending discover
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
mod_if_exit_handler:signal=6
Clean Up Ready!
Clean Up - dev_thread
Clean Up - dev_interpreter
Clean Up - SCPI
Clean Up - USBTMC
Clean Up - VXI_11
Clean Up - telnet_scpi
Clean Up - socket
Clean Up - GPIB
Clean Up - nsp adapter
Clean Up Over!
udhcpc: sending select for 192.168.42.76
[ 7414.253652] <<-GTP-INFO->> System resume.
[ 7414.253664] gpio-963 (GTP INT IRQ): _gpiod_direction_output_raw: tried to set a GPIO tied to an IRQ as output
[ 7414.273275] <<-GTP-INFO->> GTP wakeup sleep.
[ 7414.273285] gpio-963 (GTP INT IRQ): _gpiod_direction_output_raw: tried to set a GPIO tied to an IRQ as output
udhcpc: sending select for 192.168.42.76
udhcpc: sending select for 192.168.42.76
udhcpc: lease of 192.168.42.76 obtained, lease time 864000
Setting IP address 192.168.42.76 on eth0
Deleting routers
route: SIOCDELRT: No such process
Adding router 192.168.42.1
Recreating /usr/bin/siglent/usr/etc/resolv.conf
Adding DNS server 192.168.42.1
chmod -R 777 /usr/bin/siglent/usr/usr/upgrade/*
sync
mount -o sync,rw,remount /usr/bin/siglent/
sync
rm /usr/bin/siglent/usr/usr/upgrade/*.zip
rm /usr/bin/siglent/usr/usr/upgrade/*.ADS
rm /usr/bin/siglent/usr/*.zip
rm /usr/bin/siglent/usr/*.ADS
sync
the folder /usr/bin/siglent/usr/usr/upgrade/ isn't existing. Maybe, that's the problem?
I can create it, but than it is still empty. Should the .ADS file be located there?
I wonder if something wasn't copied across during the upgrade because of space filling up. Which you won't see now as any temporary files may have been removed when rebooted.
I would suggest running the upgrade (again) from a USB drive, but I have no idea how to do that from the internal serial port. @tv84 ??
/usr/bin/siglent # find / -name "*.ADS"
/usr/bin/siglent/usr/mass_storage/U-disk0/SVA1032X_V3.2.2.3.2.ADS
/usr/bin/siglent/usr/mass_storage/U-disk0/SVA1032X_backup.ADS
/usr/bin/siglent/usr/mass_storage/U-disk0/SVA1032X_V2.2.1.2.8.ADS
/usr/bin/siglent/usr/mass_storage/U-disk0/._SVA1032X_V2.2.1.2.8.ADS
/usr/bin/siglent/usr/mass_storage/U-disk0/SSA3000X_Plus_telnet.ADS
/usr/bin/siglent/usr/mass_storage/U-disk0/._SSA3000X_Plus_telnet.ADS
/usr/bin/siglent/usr/mass_storage/U-disk0/SVA1032X_telnet.ADS
/usr/bin/siglent/usr/mass_storage/U-disk0/._SVA1032X_telnet.ADS
/usr/bin/siglent/usr/mass_storage/U-disk0/._SVA1032X_backup.ADS
/usr/bin/siglent/usr/mass_storage/U-disk0/SVA1032X_V3.2.2.3.3R1.ADS
ps -ef | grep Aladdin
1022 root 0:15 /usr/bin/siglent/Aladdin
1095 root 0:00 grep Aladdin
I manually startet Aladdin. Now it's inside the process list:Code: [Select]ps -ef | grep Aladdin
1022 root 0:15 /usr/bin/siglent/Aladdin
1095 root 0:00 grep Aladdin
But there the device still stucks inside the siglent boot screen.
I manually startet Aladdin. Now it's inside the process list:Code: [Select]ps -ef | grep Aladdin
1022 root 0:15 /usr/bin/siglent/Aladdin
1095 root 0:00 grep Aladdin
But there the device still stucks inside the siglent boot screen.
I believe you have access to the internal serial port?
If you capture the output from that, as a normal boot, without the USB drive plugged in, then someone may be able to spot why Aladdin is not starting on normal boot. (Attach as a text file will be best)
% grep corrupted iTerm2\ Session\ 30.\ Dec\ 2020\ at\ 6_04_21\ PM.txt
[ 1.748128] UBI-1: ubi_attach_mtd_dev:good PEBs: 288, bad PEBs: 0, corrupted PEBs: 0
[ 1.888495] UBI-2: ubi_attach_mtd_dev:good PEBs: 80, bad PEBs: 0, corrupted PEBs: 0
[ 2.034812] UBI-3: ubi_attach_mtd_dev:good PEBs: 80, bad PEBs: 0, corrupted PEBs: 0
[ 2.520557] UBI-0: ubi_attach_mtd_dev:good PEBs: 800, bad PEBs: 0, corrupted PEBs: 0
*** glibc detected *** /usr/bin/siglent/Aladdin: free(): corrupted unsorted chunks: 0x*** glibc detected *** 00ed0a80/usr/bin/siglent/Aladdin ***
: free(): corrupted unsorted chunks: 0x00ed08d8 ***
*** glibc detected *** /usr/bin/siglent/Aladdin: free(): corrupted unsorted chunks: 0x00fa7ce8 ***
*** glibc detected *** /usr/bin/siglent/Aladdin: free(): corrupted unsorted chunks: 0x00ed0730 ***
*** glibc detected *** /usr/bin/siglent/Aladdin: free(): corrupted unsorted chunks: 0x00ed0588 ***
/usr/bin/siglent/Aladdin: free(): corrupted unsorted chunks: 0x00ed0338 ***
*** glibc detected *** /usr/bin/siglent/Aladdin: free(): corrupted unsorted chunks: 0x00ed01d0 ***
*** glibc detected *** /usr/bin/siglent/Aladdin: free(): corrupted unsorted chunks: 0x00ed0028 ***
*** glibc detected *** /usr/bin/siglent/Aladdin: free(): corrupted unsorted chunks: 0x00ecfe80 ***
*** glibc detected *** /usr/bin/siglent/Aladdin: free(): corrupted unsorted chunks: 0x00ecfcd8 ***
*** glibc detected *** /usr/bin/siglent/Aladdin: free(): corrupted unsorted chunks: 0x00ecf920 ***
*** glibc detected *** /usr/bin/siglent/Aladdin: free(): corrupted unsorted chunks: 0x00ecf6f8 ***
359b2000-359b6000 r-xp 000030/12/2020 15:49:14 /lib/libc.so.6(+0x*** glibc detected *** 636e8/usr/bin/siglent/Aladdin): [0xfree(): corrupted unsorted chunks35a226e8: 0x]
*** glibc detected *** /usr/bin/siglent/Aladdin: free(): corrupted unsorted chunks: 0x00ecf458 ***
*** glibc detected *** /usr/bin/siglent/Aladdin: free(): corrupted unsorted chunks: 0x/lib/libc.so.600ecf360/lib/libc.so.6((exitgsignal+0x+0x143c))[0x[0x359f1270359ebfc8]
[ 1.748054] UBI-1: ubi_attach_mtd_dev:good PEBs: 288, bad PEBs: 0, corrupted PEBs: 0
[ 1.888402] UBI-2: ubi_attach_mtd_dev:good PEBs: 80, bad PEBs: 0, corrupted PEBs: 0
[ 2.034702] UBI-3: ubi_attach_mtd_dev:good PEBs: 80, bad PEBs: 0, corrupted PEBs: 0
[ 2.520337] UBI-0: ubi_attach_mtd_dev:good PEBs: 800, bad PEBs: 0, corrupted PEBs: 0
*** glibc detected *** /usr/bin/siglent/Aladdin: corrupted double-linked list: 0x00ef2188 ***
[ 1.748233] UBI-1: ubi_attach_mtd_dev:good PEBs: 288, bad PEBs: 0, corrupted PEBs: 0
[ 1.888603] UBI-2: ubi_attach_mtd_dev:good PEBs: 80, bad PEBs: 0, corrupted PEBs: 0
[ 2.028302] UBI-3: ubi_attach_mtd_dev:good PEBs: 80, bad PEBs: 0, corrupted PEBs: 0
[ 2.514028] UBI-0: ubi_attach_mtd_dev:good PEBs: 800, bad PEBs: 0, corrupted PEBs: 0
Here (http://s000.tinyupload.com/index.php?file_id=62179222259034130417) is the zip with the .ADS contents.
I suggest you do the following:
chmod -R 777 /usr/bin/siglent/usr/usr/upgrade/*
mount -o sync,rw,remount /usr/bin/siglent/
mount -o sync,rw,remount /usr/bin/siglent/firmdata0
sync
Unzip the .ZIP into:
/usr/bin/siglent/usr/usr/upgrade/
Sync.
Then manually launch:
/usr/bin/siglent/usr/usr/upgrade/upgrade.sh
I'm pretty sure the brick was not a fault of the user, but rather a poor implementation of the web update on behalf of Siglent.Possibly and maybe I should've checked that when updating my SVA1032X to V3.2.2.3.3R1 last evening just before Kibabalu found himself in a pickle. Thanks again for helping him out chaps.
So got my SDR Kits Rosenberger "Calkit" i know it's a generic one but original ones are to expensive for "Hobby use" :-(
And i think they are decent enough for my useage (hopefully)..
Now my problem is, how can i get the Calkit Parametes inside my SVA1032x? I saw user calkit buttons but the Parameters were unclear for me.
Or should i telnet in and refine / manipulate one of the saved "original" Calkits with my parameters?
Here are the calkit parameters:
https://www.sdr-kits.net/documents/Rosenberger_Female_Cal_Standards_rev5.pdf (https://www.sdr-kits.net/documents/Rosenberger_Female_Cal_Standards_rev5.pdf)
Can somebody elp me to verify which parameter inside the pdf is the correct parameter for the SVA user calkit (C1,C2,C3...)?
Hm and now?
What can i do? How can i use the provided cal parameters?
Or simply unuseable?
I'm pretty sure the brick was not a fault of the user, but rather a poor implementation of the web update on behalf of Siglent.
@Kibabalu: I would like to know what exactly happend and what you did? Did you just select "online FW update"? Did you have a USB disk inserted? Did you remove it after first reboot?
Try a Chrome browser.
1. download the FW on my machine (iMac)
2. selecting the online FW update offered from the web Front end inside the browser (Safari)
3. choosing the downloaded FW file (iMac)
1. download the FW on my machine (iMac)
2. selecting the online FW update offered from the web Front end inside the browser (Safari)
3. choosing the downloaded FW file (iMac)
Maybe it's me but I definitely didn't understand this part.
Nonetheless, maybe the online web update still points to a lower FW version which is not compatible with the new FW 3.x and that's the cause of the brick...
If the procedure of online web update is getting a file into the USB disk to flash later, then it's pratically the same as downloading it first into the USB stick and doing a local update. UNLESS the file is different or corrupted.
Thus, it's not really an online firmware upgrade. It's more a web based front end controlled FW update process.
Thus, it's not really an online firmware upgrade. It's more a web based front end controlled FW update process.
:palm:
OK, then you did nothing wrong! BTW, download again the .ADS via that method BUT don't flash it and compare with the latest .ADS that we get from the web (in the PC). Or tell me the CRC32.
Had too many :popcorn: to check and as it's early 2021 now will rollback FW and try the web FW update tomorrow to see if I can brick mine also. >:D
Watch this space. ;)
Those kiwis always like to go ahead of us!!! :D
Happy New Year!
The "online" update is a missleading name. What I understood is that you open the webpage of the SSA/SVA and select FW upgrade. This opens a file dialog pointing to your computer where you can select the ADS file. It is then transferred to the SSA/SVA and installed.Correct, it works just like that.
I think the problem is that this only works if a USB disk is attached to the SSA/SVA to store and extract the ADS file. Otherwise, it will be stored in the same folder, which is not mounted to the USB device! Apart from the lack of free memory space, because the device is not syncing this data, after a reboot it will be lost. Which is why the bricked device was complaining about the missing U-Disk0 device.You don't however you can browse to a USB stick and select the ADS update file from there if you wish.
This is a serious bug! Why would you do an "online" update, if you have to insert a USB disk? Why not insert the USB disk with the ADF already copied onto it?
your testing scenario was upgrading from Firmware V3.2.2.3.2 to V3.2.2.3.3R1 using the web gui and everything went fine ?Yes.
Then maybe in my case I didn't wait long enough before I tried another reboot and interrupted the copying process or I just had "bad luck".This ^
Yes, I was aware of this. But it took that long, at least in my feeling, that I suspected some issue.Yes the auto reboot seems to take longer to happen if using the webserver to update, however it does work even though it seems like a freeze.
In future I will try to school myself in patience 😉
********** Zynq-7000 SoC Boot Header **********
00000000 - ARM Vector Table: 8 x EAFFFFFE
00000020 - Width Detection: AA995566
00000024 - Header Signature: XLNX
00000028 - Key Source: 00000000 - Not Encrypted
0000002C - Version: 01010000 (0x01010000)
00000030 - FSBL Image Offset: 00001700
00000034 - FSBL Image Length: 00014010
00000038 - FSBL Load Address (RAM): 00000000
0000003C - FSBL Exec Address (RAM): 00000000
00000040 - Total FSBL Length: 00014010
00000044 - QSPI Configuration: 00000001 (0x00000001)
00000048 - Boot Header Checksum: FC16C520 CHKSUM OK
0000004C - User Defined: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
00000098 - Image Header Table Offset: 000008C0
0000009C - Partit. Header Table Offset: 00000C80
********** Zynq-7000 SoC Device Register Initialization Table **********
000000A0 - Register Initialization Pairs [000000A0-0000089F]
********** Zynq-7000 SoC Device Image Header Table **********
000008C0 - Version: 01020000 (0x01020000)
000008C4 - # Image Headers: 00000003
000008C8 - 1st Partition Header Offset: 00000C80
000008CC - 1st Image Header Offset: 00000900
000008D0 - Header Auth Certif Offset: 00000000
000008D4 - Reserved: FFFFFFFF
********** Zynq-7000 SoC Device Image Headers **********
Partitio Reserved Length Name
00000900 - 00000C80 00000000 00000001 fsbl.elf
00000940 - 00000CC0 00000000 00000001 fpga_top_sva3000x.bit
00000980 - 00000D00 00000000 00000001 u-boot.elf
********** Zynq-7000 SoC Device Partition Headers **********
EncryLen UnencLen TotalLen DestLoad DestExec ImgOffst AttrBits Sections Checksm ImHdOffs AuthOffs HdChkSum
00000C80 - 00014010 00014010 00014010 00000000 00000000 00001700 00000010 00000001 00000000 00000900 00000000 FFFF07E2 CHKSUM OK
00000CC0 - 003DBB00 003DBB00 003DBB00 00000000 00000000 00080000 00000020 00000001 00000000 00000940 00000000 FFCFB14E CHKSUM OK
00000D00 - 0006E860 0006E860 0006E860 04000000 04000000 00580000 00000010 00000001 00000000 00000980 00000000 F7E4CF46 CHKSUM OK
Hmmmm :-//
Since updating to V3.2.2.4.0, I can't use the old telnet ADS files to get back in and re-enable telnet in the startup script? This worked fine on the last update to R1.
Have they removed / moved the telnet binary?
7777777777777777777777777
Archive: /usr/bin/siglent/usr/usr/upgrade/config.zip
creating: add/
creating: add/help/
creating: add/help/sva1000x/
creating: add/help/sva1000x/cn/
inflating: add/help/sva1000x/cn/image001.png
inflating: add/help/sva1000x/cn/image002.png
inflating: add/help/sva1000x/cn/image003.png
inflating: add/help/sva1000x/cn/image004.png
inflating: add/help/sva1000x/cn/image005.jpg
inflating: add/help/sva1000x/cn/image006.jpg
inflating: add/help/sva1000x/cn/image007.jpg
inflating: add/help/sva1000x/cn/image008.jpg
inflating: add/help/sva1000x/cn/image009.png
inflating: add/help/sva1000x/cn/image010.png
inflating: add/help/sva1000x/cn/image011.png
inflating: add/help/sva1000x/cn/image012.png
inflating: add/help/sva1000x/cn/image013.png
inflating: add/help/sva1000x/cn/image014.png
inflating: add/help/sva1000x/cn/image015.jpg
inflating: add/help/sva1000x/cn/image016.png
inflating: add/help/sva1000x/cn/image017.jpg
inflating: add/help/sva1000x/cn/image018.png
inflating: add/help/sva1000x/cn/image019.png
inflating: add/help/sva1000x/cn/image020.jpg
inflating: add/help/sva1000x/cn/image021.jpg
inflating: add/help/sva1000x/cn/image022.png
inflating: add/help/sva1000x/cn/image023.png
inflating: add/help/sva1000x/cn/image024.png
inflating: add/help/sva1000x/cn/image025.png
inflating: add/help/sva1000x/cn/image026.jpg
inflating: add/help/sva1000x/cn/image027.jpg
inflating: add/help/sva1000x/cn/image028.jpg
inflating: add/help/sva1000x/cn/image029.jpg
inflating: add/help/sva1000x/cn/image030.jpg
inflating: add/help/sva1000x/cn/image031.jpg
inflating: add/help/sva1000x/cn/image032.jpg
inflating: add/help/sva1000x/cn/image033.png
inflating: add/help/sva1000x/cn/image034.jpg
inflating: add/help/sva1000x/cn/image035.png
inflating: add/help/sva1000x/cn/image036.png
inflating: add/help/sva1000x/cn/image037.png
inflating: add/help/sva1000x/cn/image038.jpg
inflating: add/help/sva1000x/cn/image039.jpg
inflating: add/help/sva1000x/cn/image040.png
inflating: add/help/sva1000x/cn/image041.png
inflating: add/help/sva1000x/cn/image042.jpg
inflating: add/help/sva1000x/cn/image043.png
inflating: add/help/sva1000x/cn/image044.jpg
inflating: add/help/sva1000x/cn/image045.png
inflating: add/help/sva1000x/cn/image046.png
inflating: add/help/sva1000x/cn/image047.jpg
inflating: add/help/sva1000x/cn/image048.jpg
inflating: add/help/sva1000x/cn/image049.jpg
inflating: add/help/sva1000x/cn/image050.jpg
inflating: add/help/sva1000x/cn/image051.jpg
inflating: add/help/sva1000x/cn/image052.jpg
inflating: add/help/sva1000x/cn/image053.jpg
inflating: add/help/sva1000x/cn/image054.png
inflating: add/help/sva1000x/cn/image055.jpg
inflating: add/help/sva1000x/cn/image056.jpg
inflating: add/help/sva1000x/cn/image057.jpg
inflating: add/help/sva1000x/cn/image058.jpg
inflating: add/help/sva1000x/cn/image059.jpg
inflating: add/help/sva1000x/cn/image060.jpg
inflating: add/help/sva1000x/cn/image061.png
inflating: add/help/sva1000x/cn/image062.png
inflating: add/help/sva1000x/cn/image063.jpg
inflating: add/help/sva1000x/cn/image064.jpg
inflating: add/help/sva1000x/cn/image065.jpg
inflating: add/help/sva1000x/cn/image066.png
inflating: add/help/sva1000x/cn/image067.jpg
inflating: add/help/sva1000x/cn/image068.jpg
inflating: add/help/sva1000x/cn/image069.png
inflating: add/help/sva1000x/cn/image070.png
inflating: add/help/sva1000x/cn/image071.png
inflating: add/help/sva1000x/cn/image072.png
inflating: add/help/sva1000x/cn/image073.jpg
inflating: add/help/sva1000x/cn/image074.png
inflating: add/help/sva1000x/cn/image075.png
inflating: add/help/sva1000x/cn/image076.png
inflating: add/help/sva1000x/cn/image077.png
inflating: add/help/sva1000x/cn/image078.png
inflating: add/help/sva1000x/cn/image079.png
inflating: add/help/sva1000x/cn/image080.png
inflating: add/help/sva1000x/cn/image081.png
inflating: add/help/sva1000x/cn/image082.png
inflating: add/help/sva1000x/cn/image083.png
inflating: add/help/sva1000x/cn/image084.png
inflating: add/help/sva1000x/cn/image085.png
inflating: add/help/sva1000x/cn/image086.jpg
inflating: add/help/sva1000x/cn/image087.jpg
inflating: add/help/sva1000x/cn/image088.png
inflating: add/help/sva1000x/cn/image089.jpg
inflating: add/help/sva1000x/cn/image090.png
inflating: add/help/sva1000x/cn/image091.jpg
inflating: add/help/sva1000x/cn/image092.png
inflating: add/help/sva1000x/cn/image093.png
inflating: add/help/sva1000x/cn/image094.jpg
inflating: add/help/sva1000x/cn/image095.png
inflating: add/help/sva1000x/cn/image096.jpg
inflating: add/help/sva1000x/cn/image097.jpg
inflating: add/help/sva1000x/cn/image098.jpg
inflating: add/help/sva1000x/cn/image099.jpg
inflating: add/help/sva1000x/cn/image100.jpg
inflating: add/help/sva1000x/cn/image101.jpg
inflating: add/help/sva1000x/cn/image102.png
inflating: add/help/sva1000x/cn/image103.png
inflating: add/help/sva1000x/cn/image104.jpg
inflating: add/help/sva1000x/cn/image105.jpg
inflating: add/help/sva1000x/cn/image106.jpg
inflating: add/help/sva1000x/cn/image107.png
inflating: add/help/sva1000x/cn/image108.png
inflating: add/help/sva1000x/cn/image109.png
inflating: add/help/sva1000x/cn/image110.jpg
inflating: add/help/sva1000x/cn/image111.png
creating: add/help/sva1000x/en/
inflating: add/help/sva1000x/en/image001.png
inflating: add/help/sva1000x/en/image002.png
inflating: add/help/sva1000x/en/image003.png
inflating: add/help/sva1000x/en/image004.png
inflating: add/help/sva1000x/en/image005.jpg
inflating: add/help/sva1000x/en/image006.png
inflating: add/help/sva1000x/en/image007.png
inflating: add/help/sva1000x/en/image008.png
inflating: add/help/sva1000x/en/image009.png
inflating: add/help/sva1000x/en/image010.png
inflating: add/help/sva1000x/en/image011.png
inflating: add/help/sva1000x/en/image012.png
inflating: add/help/sva1000x/en/image013.png
inflating: add/help/sva1000x/en/image014.png
inflating: add/help/sva1000x/en/image015.png
inflating: add/help/sva1000x/en/image016.jpg
inflating: add/help/sva1000x/en/image017.jpg
inflating: add/help/sva1000x/en/image018.png
inflating: add/help/sva1000x/en/image019.png
inflating: add/help/sva1000x/en/image020.png
inflating: add/help/sva1000x/en/image021.png
inflating: add/help/sva1000x/en/image022.png
inflating: add/help/sva1000x/en/image023.png
inflating: add/help/sva1000x/en/image024.jpg
inflating: add/help/sva1000x/en/image025.png
inflating: add/help/sva1000x/en/image026.jpg
inflating: add/help/sva1000x/en/image027.png
inflating: add/help/sva1000x/en/image028.jpg
inflating: add/help/sva1000x/en/image029.png
inflating: add/help/sva1000x/en/image030.jpg
inflating: add/help/sva1000x/en/image031.jpg
inflating: add/help/sva1000x/en/image032.jpg
inflating: add/help/sva1000x/en/image033.png
inflating: add/help/sva1000x/en/image034.png
inflating: add/help/sva1000x/en/image035.jpg
inflating: add/help/sva1000x/en/image036.png
inflating: add/help/sva1000x/en/image037.png
inflating: add/help/sva1000x/en/image038.png
inflating: add/help/sva1000x/en/image039.jpg
inflating: add/help/sva1000x/en/image040.jpg
inflating: add/help/sva1000x/en/image041.jpg
inflating: add/help/sva1000x/en/image042.jpg
inflating: add/help/sva1000x/en/image043.jpg
inflating: add/help/sva1000x/en/image044.jpg
inflating: add/help/sva1000x/en/image045.jpg
inflating: add/help/sva1000x/en/image046.png
inflating: add/help/sva1000x/en/image047.jpg
inflating: add/help/sva1000x/en/image048.jpg
inflating: add/help/sva1000x/en/image049.png
inflating: add/help/sva1000x/en/image050.png
inflating: add/help/sva1000x/en/image051.jpg
inflating: add/help/sva1000x/en/image052.jpg
inflating: add/help/sva1000x/en/image053.jpg
inflating: add/help/sva1000x/en/image054.jpg
inflating: add/help/sva1000x/en/image055.jpg
inflating: add/help/sva1000x/en/image056.jpg
inflating: add/help/sva1000x/en/image057.jpg
inflating: add/help/sva1000x/en/image058.jpg
inflating: add/help/sva1000x/en/image059.jpg
inflating: add/help/sva1000x/en/image060.jpg
inflating: add/help/sva1000x/en/image061.png
inflating: add/help/sva1000x/en/image062.jpg
inflating: add/help/sva1000x/en/image063.jpg
inflating: add/help/sva1000x/en/image064.jpg
inflating: add/help/sva1000x/en/image065.jpg
inflating: add/help/sva1000x/en/image066.png
inflating: add/help/sva1000x/en/image067.png
inflating: add/help/sva1000x/en/image068.png
inflating: add/help/sva1000x/en/image069.png
inflating: add/help/sva1000x/en/image070.png
inflating: add/help/sva1000x/en/image071.jpg
inflating: add/help/sva1000x/en/image072.jpg
inflating: add/help/sva1000x/en/image073.png
inflating: add/help/sva1000x/en/image074.jpg
inflating: add/help/sva1000x/en/image075.jpg
inflating: add/help/sva1000x/en/image076.png
inflating: add/help/sva1000x/en/image077.png
inflating: add/help/sva1000x/en/image078.png
inflating: add/help/sva1000x/en/image079.png
inflating: add/help/sva1000x/en/image080.png
inflating: add/help/sva1000x/en/image081.png
inflating: add/help/sva1000x/en/image082.png
inflating: add/help/sva1000x/en/image083.png
inflating: add/help/sva1000x/en/image084.png
inflating: add/help/sva1000x/en/image085.png
inflating: add/help/sva1000x/en/image086.png
inflating: add/help/sva1000x/en/image087.png
inflating: add/help/sva1000x/en/image088.png
inflating: add/help/sva1000x/en/image089.png
inflating: add/help/sva1000x/en/image090.jpg
inflating: add/help/sva1000x/en/image091.png
inflating: add/help/sva1000x/en/image092.png
inflating: add/help/sva1000x/en/image093.jpg
inflating: add/help/sva1000x/en/image094.jpg
inflating: add/help/sva1000x/en/image095.png
inflating: add/help/sva1000x/en/image096.png
inflating: add/help/sva1000x/en/image097.png
inflating: add/help/sva1000x/en/image098.png
inflating: add/help/sva1000x/en/image099.png
inflating: add/help/sva1000x/en/image100.png
inflating: add/help/sva1000x/en/image101.png
inflating: add/help/sva1000x/en/image102.jpg
inflating: add/help/sva1000x/en/image103.jpg
inflating: add/help/sva1000x/en/image104.jpg
inflating: add/help/sva1000x/en/image105.jpg
inflating: add/help/sva1000x/en/image106.jpg
inflating: add/help/sva1000x/en/image107.jpg
inflating: add/help/sva1000x/en/image108.png
inflating: add/help/sva1000x/en/image109.png
inflating: add/help/sva1000x/en/image110.jpg
inflating: add/help/sva1000x/en/image111.jpg
inflating: add/help/sva1000x/en/image112.jpg
inflating: add/help/sva1000x/en/image113.png
inflating: add/help/sva1000x/en/image114.png
inflating: add/help/sva1000x/en/image115.png
inflating: add/help/sva1000x/en/image116.jpg
inflating: add/help/sva1000x/en/image117.png
inflating: add/help/sva1000x/en/image118.jpg
inflating: add/help/sva1000x_manual_cn.xml
inflating: add/help/sva1000x_manual_en.xml
creating: add/Limits/
creating: add/Limits/EN/
creating: add/Limits/EN/55011/
inflating: add/Limits/EN/55011/EN 55011, Cond, Class A, Group 1, GT 20kVA, Average.lim
inflating: add/Limits/EN/55011/EN 55011, Cond, Class A, Group 1, GT 20kVA, Quasi-P.lim
inflating: add/Limits/EN/55011/EN 55011, Cond, Class A, Group 1, LTE 20kVA, Average.lim
inflating: add/Limits/EN/55011/EN 55011, Cond, Class A, Group 1, LTE 20kVA, Quasi-P.lim
inflating: add/Limits/EN/55011/EN 55011, Cond, Class A, Group 2, GT 75kVA, Average.lim
inflating: add/Limits/EN/55011/EN 55011, Cond, Class A, Group 2, GT 75kVA, Quasi-P.lim
inflating: add/Limits/EN/55011/EN 55011, Cond, Class A, Group 2, LTE 75kVA, Average.lim
inflating: add/Limits/EN/55011/EN 55011, Cond, Class A, Group 2, LTE 75kVA, Quasi-P.lim
inflating: add/Limits/EN/55011/EN 55011, Cond, Class B, Group 1, Average.lim
inflating: add/Limits/EN/55011/EN 55011, Cond, Class B, Group 1, Quasi-Peak.lim
inflating: add/Limits/EN/55011/EN 55011, Cond, Class B, Group 2, Average.lim
inflating: add/Limits/EN/55011/EN 55011, Cond, Class B, Group 2, Quasi-Peak.lim
inflating: add/Limits/EN/55011/EN 55011, Cond, Ind Cooking, 100V No Gnd, Average.lim
inflating: add/Limits/EN/55011/EN 55011, Cond, Ind Cooking, 100V No Gnd, Quasi-Peak.lim
inflating: add/Limits/EN/55011/EN 55011, Cond, Ind Cooking, Average.lim
inflating: add/Limits/EN/55011/EN 55011, Cond, Ind Cooking, Quasi-Peak.lim
inflating: add/Limits/EN/55011/EN 55011, Rad, Class A, EDM + Arc Welding.lim
inflating: add/Limits/EN/55011/EN 55011, Rad, Class A, Group 1, GT 20kVA.lim
inflating: add/Limits/EN/55011/EN 55011, Rad, Class A, Group 1, LTE 20kVA, Quasi-P (10m).lim
inflating: add/Limits/EN/55011/EN 55011, Rad, Class A, Group 1, LTE 20kVA, Quasi-P (30m).lim
inflating: add/Limits/EN/55011/EN 55011, Rad, Class A, Group 1, LTE 20kVA, Quasi-P (3m).lim
inflating: add/Limits/EN/55011/EN 55011, Rad, Class A, Group 2 (10m).lim
inflating: add/Limits/EN/55011/EN 55011, Rad, Class A, Group 2 (30m).lim
inflating: add/Limits/EN/55011/EN 55011, Rad, Class A, Group 2, MagField (10m).lim
inflating: add/Limits/EN/55011/EN 55011, Rad, Class A, Group 2, MagField (30m).lim
inflating: add/Limits/EN/55011/EN 55011, Rad, Class B, Group 1.lim
inflating: add/Limits/EN/55011/EN 55011, Rad, Class B, Group 2, Average (10m).lim
inflating: add/Limits/EN/55011/EN 55011, Rad, Class B, Group 2, MagField (3m).lim
inflating: add/Limits/EN/55011/EN 55011, Rad, Class B, Group 2, Quasi-Peak (10m).lim
inflating: add/Limits/EN/55011/EN 55011, Rad, Commercial Ind Cooking, MagField.lim
inflating: add/Limits/EN/55011/EN 55011, Rad, Domestic Ind Cooking, MagField, Horiz.lim
inflating: add/Limits/EN/55011/EN 55011, Rad, Domestic Ind Cooking, MagField, Vert.lim
creating: add/Limits/EN/55012/
inflating: add/Limits/EN/55012/EN 55012, Rad, Average (10m).lim
inflating: add/Limits/EN/55012/EN 55012, Rad, Average (3m).lim
inflating: add/Limits/EN/55012/EN 55012, Rad, Peak, 120kHz RBW (10m).lim
inflating: add/Limits/EN/55012/EN 55012, Rad, Peak, 120kHz RBW (3m).lim
inflating: add/Limits/EN/55012/EN 55012, Rad, Peak, 1MHz RBW (10m).lim
inflating: add/Limits/EN/55012/EN 55012, Rad, Peak, 1MHz RBW (3m).lim
inflating: add/Limits/EN/55012/EN 55012, Rad, Quasi-Peak, 120kHz RBW (10m).lim
inflating: add/Limits/EN/55012/EN 55012, Rad, Quasi-Peak, 120kHz RBW (3m).lim
creating: add/Limits/EN/55013/
inflating: add/Limits/EN/55013/EN 55013, Conducted, Average.lim
inflating: add/Limits/EN/55013/EN 55013, Conducted, Quasi-Peak.lim
inflating: add/Limits/EN/55013/EN 55013, Disturbance, Average.lim
inflating: add/Limits/EN/55013/EN 55013, Disturbance, Quasi-Peak.lim
inflating: add/Limits/EN/55013/EN 55013, Rad, FM Sound, Rx+PCTuner - Harm.lim
inflating: add/Limits/EN/55013/EN 55013, Rad, FM Sound, Rx+PCTuner - LO.lim
inflating: add/Limits/EN/55013/EN 55013, Rad, FM Sound, Rx+PCTuner - Other.lim
inflating: add/Limits/EN/55013/EN 55013, Rad, Indoor Sat TV+Sd Rx,IR Rmt+Headphone.lim
inflating: add/Limits/EN/55013/EN 55013, Rad, Sat Rx Outdoor Unit - EquivRadPW.lim
inflating: add/Limits/EN/55013/EN 55013, Rad, Sat Rx Outdoor Unit - LO.lim
inflating: add/Limits/EN/55013/EN 55013, Rad, Sat TV+Sd Rx, TunerUnit - LO+Harm.lim
inflating: add/Limits/EN/55013/EN 55013, Rad, TV, VidRec, PCTuner - Harm.lim
inflating: add/Limits/EN/55013/EN 55013, Rad, TV, VidRec, PCTuner - LO.lim
inflating: add/Limits/EN/55013/EN 55013, Rad, TV, VidRec, PCTuner - Other.lim
creating: add/Limits/EN/55014/
inflating: add/Limits/EN/55014/EN 55014, Cond, Household, Average.lim
inflating: add/Limits/EN/55014/EN 55014, Cond, Household, Quasi-Peak.lim
inflating: add/Limits/EN/55014/EN 55014, Cond, Motors 700to1000W, Average.lim
inflating: add/Limits/EN/55014/EN 55014, Cond, Motors 700to1000W, Quasi-Peak.lim
inflating: add/Limits/EN/55014/EN 55014, Cond, Motors GT 1000W, Average.lim
inflating: add/Limits/EN/55014/EN 55014, Cond, Motors GT 1000W, Quasi-Peak.lim
inflating: add/Limits/EN/55014/EN 55014, Cond, Motors LT 700W, Average.lim
inflating: add/Limits/EN/55014/EN 55014, Cond, Motors LT 700W, Quasi-Peak.lim
inflating: add/Limits/EN/55014/EN 55014, Rad, FAR.lim
inflating: add/Limits/EN/55014/EN 55014, Rad, Mains, Household, Average.lim
inflating: add/Limits/EN/55014/EN 55014, Rad, Mains, Household, Quasi-Peak.lim
inflating: add/Limits/EN/55014/EN 55014, Rad, Mains, Motors 700to1000W, Average.lim
inflating: add/Limits/EN/55014/EN 55014, Rad, Mains, Motors 700to1000W, Quasi-Peak.lim
inflating: add/Limits/EN/55014/EN 55014, Rad, Mains, Motors GT 1000W, Average.lim
inflating: add/Limits/EN/55014/EN 55014, Rad, Mains, Motors GT 1000W, Quasi-Peak.lim
inflating: add/Limits/EN/55014/EN 55014, Rad, Mains, Motors LT 700W, Average.lim
inflating: add/Limits/EN/55014/EN 55014, Rad, Mains, Motors LT 700W, Quasi-Peak.lim
inflating: add/Limits/EN/55014/EN 55014, Rad, OATS or SAC.lim
inflating: add/Limits/EN/55014/EN 55014, Rad, TEM.lim
creating: add/Limits/EN/55015/
inflating: add/Limits/EN/55015/EN 55015, Cond, Control, Average.lim
inflating: add/Limits/EN/55015/EN 55015, Cond, Control, Quasi-Peak.lim
inflating: add/Limits/EN/55015/EN 55015, Cond, Load, Average.lim
inflating: add/Limits/EN/55015/EN 55015, Cond, Load, Quasi-Peak.lim
inflating: add/Limits/EN/55015/EN 55015, Cond, Mains, Average.lim
inflating: add/Limits/EN/55015/EN 55015, Cond, Mains, Quasi-Peak.lim
inflating: add/Limits/EN/55015/EN 55015, Rad, 30-300MHz (10m).lim
inflating: add/Limits/EN/55015/EN 55015, Rad, 9kHz-30MHz, Loop=2m.lim
inflating: add/Limits/EN/55015/EN 55015, Rad, 9kHz-30MHz, Loop=3m.lim
inflating: add/Limits/EN/55015/EN 55015, Rad, 9kHz-30MHz, Loop=4m.lim
creating: add/Limits/EN/55022/
inflating: add/Limits/EN/55022/EN 55022, Cond, Class A, Average.lim
inflating: add/Limits/EN/55022/EN 55022, Cond, Class A, Quasi-Peak.lim
inflating: add/Limits/EN/55022/EN 55022, Cond, Class A, Telecom, Current, Ave.lim
inflating: add/Limits/EN/55022/EN 55022, Cond, Class A, Telecom, Current, QP.lim
inflating: add/Limits/EN/55022/EN 55022, Cond, Class A, Telecom, Voltage, Ave.lim
inflating: add/Limits/EN/55022/EN 55022, Cond, Class A, Telecom, Voltage, QP.lim
inflating: add/Limits/EN/55022/EN 55022, Cond, Class B, Average.lim
inflating: add/Limits/EN/55022/EN 55022, Cond, Class B, Quasi-Peak.lim
inflating: add/Limits/EN/55022/EN 55022, Cond, Class B, Telecom, Current, Ave.lim
inflating: add/Limits/EN/55022/EN 55022, Cond, Class B, Telecom, Current, QP.lim
inflating: add/Limits/EN/55022/EN 55022, Cond, Class B, Telecom, Voltage, Ave.lim
inflating: add/Limits/EN/55022/EN 55022, Cond, Class B, Telecom, Voltage, QP.lim
inflating: add/Limits/EN/55022/EN 55022, Rad, Class A, 1 to 6GHz, Average (3m).lim
inflating: add/Limits/EN/55022/EN 55022, Rad, Class A, 1 to 6GHz, Peak (3m).lim
inflating: add/Limits/EN/55022/EN 55022, Rad, Class A, 30MHz to 1GHz (10m).lim
inflating: add/Limits/EN/55022/EN 55022, Rad, Class A, 30MHz to 1GHz (3m).lim
inflating: add/Limits/EN/55022/EN 55022, Rad, Class B, 1 to 6GHz, Average (3m).lim
inflating: add/Limits/EN/55022/EN 55022, Rad, Class B, 1 to 6GHz, Peak (3m).lim
inflating: add/Limits/EN/55022/EN 55022, Rad, Class B, 30MHz to 1GHz (10m).lim
inflating: add/Limits/EN/55022/EN 55022, Rad, Class B, 30MHz to 1GHz (3m).lim
creating: add/Limits/EN/55032/
inflating: add/Limits/EN/55032/EN 55032, Cond, Class A, AMN, 0.15-30MHz, AVG.lim
inflating: add/Limits/EN/55032/EN 55032, Cond, Class A, AMN, 0.15-30MHz, Quasi-P.lim
inflating: add/Limits/EN/55032/EN 55032, Cond, Class B, AMN, 0.15-30MHz, AVG.lim
inflating: add/Limits/EN/55032/EN 55032, Cond, Class B, AMN, 0.15-30MHz, Quasi-P.lim
inflating: add/Limits/EN/55032/EN 55032, Rad, Class A, FAR, 30MHz-1GHz, Quasi-P (10m).lim
inflating: add/Limits/EN/55032/EN 55032, Rad, Class A, FAR, 30MHz-1GHz, Quasi-P (3m).lim
inflating: add/Limits/EN/55032/EN 55032, Rad, Class A, FSOATS, 1-6GHz, AVG (3m).lim
inflating: add/Limits/EN/55032/EN 55032, Rad, Class A, FSOATS, 1-6GHz, Peak (3m).lim
inflating: add/Limits/EN/55032/EN 55032, Rad, Class A, OATS, 30MHz-1GHz, Quasi-P (10m).lim
inflating: add/Limits/EN/55032/EN 55032, Rad, Class A, OATS, 30MHz-1GHz, Quasi-P (3m).lim
inflating: add/Limits/EN/55032/EN 55032, Rad, Class B, FAR, 30MHz-1GHz, Quasi-P (10m).lim
inflating: add/Limits/EN/55032/EN 55032, Rad, Class B, FAR, 30MHz-1GHz, Quasi-P (3m).lim
inflating: add/Limits/EN/55032/EN 55032, Rad, Class B, FM receiver, FAR, 30MHz-1GHz, Quasi-P (10m).lim
inflating: add/Limits/EN/55032/EN 55032, Rad, Class B, FM receiver, FAR, 30MHz-1GHz, Quasi-P (3m).lim
inflating: add/Limits/EN/55032/EN 55032, Rad, Class B, FM receiver, OATS, 30MHz-1GHz, Quasi-P (10m).lim
inflating: add/Limits/EN/55032/EN 55032, Rad, Class B, FM receiver, OATS, 30MHz-1GHz, Quasi-P (3m).lim
inflating: add/Limits/EN/55032/EN 55032, Rad, Class B, FSOATS, 1-6GHz, AVG (3m).lim
inflating: add/Limits/EN/55032/EN 55032, Rad, Class B, FSOATS, 1-6GHz, Peak (3m).lim
inflating: add/Limits/EN/55032/EN 55032, Rad, Class B, OATS, 30MHz-1GHz, Quasi-P (10m).lim
inflating: add/Limits/EN/55032/EN 55032, Rad, Class B, OATS, 30MHz-1GHz, Quasi-P (3m).lim
creating: add/Limits/FCC/
inflating: add/Limits/FCC/FCC Part 15, Cond, Class A, Average.lim
inflating: add/Limits/FCC/FCC Part 15, Cond, Class A, Quasi-Peak.lim
inflating: add/Limits/FCC/FCC Part 15, Cond, Class B, Average.lim
inflating: add/Limits/FCC/FCC Part 15, Cond, Class B, Quasi-Peak.lim
inflating: add/Limits/FCC/FCC Part 15, Rad, Class A (10m).lim
inflating: add/Limits/FCC/FCC Part 15, Rad, Class B (3m).lim
creating: add/Limits/GB9254/
inflating: add/Limits/GB9254/GB9254, Cond, Class A, Average.lim
inflating: add/Limits/GB9254/GB9254, Cond, Class A, Quasi-Peak.lim
inflating: add/Limits/GB9254/GB9254, Cond, Class A, Telecom, Current, Ave.lim
inflating: add/Limits/GB9254/GB9254, Cond, Class A, Telecom, Current, QP.lim
inflating: add/Limits/GB9254/GB9254, Cond, Class A, Telecom, Voltage, Ave.lim
inflating: add/Limits/GB9254/GB9254, Cond, Class A, Telecom, Voltage, QP.lim
inflating: add/Limits/GB9254/GB9254, Cond, Class B, Average.lim
inflating: add/Limits/GB9254/GB9254, Cond, Class B, Quasi-Peak.lim
inflating: add/Limits/GB9254/GB9254, Cond, Class B, Telecom, Current, Ave.lim
inflating: add/Limits/GB9254/GB9254, Cond, Class B, Telecom, Current, QP.lim
inflating: add/Limits/GB9254/GB9254, Cond, Class B, Telecom, Voltage, Ave.lim
inflating: add/Limits/GB9254/GB9254, Cond, Class B, Telecom, Voltage, QP.lim
inflating: add/Limits/GB9254/GB9254, Rad, Class A, 1 to 6GHz, Average (3m).lim
inflating: add/Limits/GB9254/GB9254, Rad, Class A, 1 to 6GHz, Peak (3m).lim
inflating: add/Limits/GB9254/GB9254, Rad, Class A, 30MHz to 1GHz (10m).lim
inflating: add/Limits/GB9254/GB9254, Rad, Class A, 30MHz to 1GHz (3m).lim
inflating: add/Limits/GB9254/GB9254, Rad, Class B, 1 to 6GHz, Average (3m).lim
inflating: add/Limits/GB9254/GB9254, Rad, Class B, 1 to 6GHz, Peak (3m).lim
inflating: add/Limits/GB9254/GB9254, Rad, Class B, 30MHz to 1GHz (10m).lim
inflating: add/Limits/GB9254/GB9254, Rad, Class B, 30MHz to 1GHz (3m).lim
inflating: add/log4cpp.properties
inflating: add/NSP_config_upgrade_info.xml
creating: app/
inflating: app/Aladdin
inflating: app/config_eth0.sh
inflating: app/startup_app.sh
inflating: app/startup_ftp.sh
inflating: app/upgrade_app1.sh
inflating: app/vsftpd
creating: drivers/
inflating: drivers/g_usbtmc.ko
creating: plat/
creating: plat/32/
creating: plat/32/boot/
inflating: plat/32/boot/BOOT.bin
creating: plat/32/devicetree/
creating: plat/32/fpga/
inflating: plat/32/fpga/fpga_top.bit
inflating: plat/32/fpga/load_fpga.sh
inflating: plat/32/fpga/plat
inflating: plat/32/fpga/vdma_menu.sh
inflating: plat/32/fpga/vdma_wave.sh
inflating: plat/32/upgrade_dtb.sh
inflating: plat/32/upgrade_fpga.sh
inflating: plat/32/upgrade_uboot.sh
inflating: plat/32/upgrade_vnc1.sh
creating: plat/32/vnc/
inflating: plat/32/vnc/vdma_vnc.sh
inflating: plat/32/vnc/vncserver.conf
creating: sys/
inflating: sys/uImage
creating: vnc/
creating: vnc/lib/
inflating: vnc/lib/brusvxi11.so
inflating: vnc/lib/ext_device_driver.so
inflating: vnc/lib/libEasyLib.so
inflating: vnc/lib/libvncclient.so
inflating: vnc/lib/libvncclient.so.1
inflating: vnc/lib/libvncserver.so
inflating: vnc/lib/libvncserver.so.1
inflating: vnc/lighttpd.conf
inflating: vnc/php.ini
inflating: vnc/startup_vnc.sh
inflating: vnc/vdma_vnc.sh
inflating: vnc/vncserver
creating: vnc/www/
creating: vnc/www/attchment/
creating: vnc/www/css/
creating: vnc/www/css/device/
inflating: vnc/www/css/device/device_control.css
inflating: vnc/www/css/device/main.css
inflating: vnc/www/css/login.css
inflating: vnc/www/css/welcome.css
inflating: vnc/www/deviceupdate.php
inflating: vnc/www/device_read_write.php
creating: vnc/www/fonts/
inflating: vnc/www/fonts/fontawesome-webfont.eot
inflating: vnc/www/fonts/fontawesome-webfont.svg
inflating: vnc/www/fonts/fontawesome-webfont.ttf
inflating: vnc/www/fonts/fontawesome-webfont.woff
inflating: vnc/www/fonts/fontawesome-webfont.woff2
inflating: vnc/www/fonts/FontAwesome.otf
creating: vnc/www/img/
inflating: vnc/www/img/about.png
inflating: vnc/www/img/Home1.png
inflating: vnc/www/img/Home2.png
inflating: vnc/www/img/ic_login.png
inflating: vnc/www/img/ic_password.png
inflating: vnc/www/img/ic_user.png
inflating: vnc/www/img/Intrument1.png
inflating: vnc/www/img/Intrument2.png
inflating: vnc/www/img/LAN1.png
inflating: vnc/www/img/LAN2.png
inflating: vnc/www/img/logo.png
inflating: vnc/www/img/oem_logo.png
inflating: vnc/www/img/SCPI1.png
inflating: vnc/www/img/SCPI2.png
inflating: vnc/www/index.php
creating: vnc/www/Instrument/
creating: vnc/www/Instrument/novnc/
inflating: vnc/www/Instrument/novnc/favicon.ico
creating: vnc/www/Instrument/novnc/images/
inflating: vnc/www/Instrument/novnc/images/alt.png
inflating: vnc/www/Instrument/novnc/images/clipboard.png
inflating: vnc/www/Instrument/novnc/images/connect.png
inflating: vnc/www/Instrument/novnc/images/ctrl.png
inflating: vnc/www/Instrument/novnc/images/ctrlaltdel.png
inflating: vnc/www/Instrument/novnc/images/disconnect.png
inflating: vnc/www/Instrument/novnc/images/drag.png
inflating: vnc/www/Instrument/novnc/images/esc.png
inflating: vnc/www/Instrument/novnc/images/expand.gif
inflating: vnc/www/Instrument/novnc/images/favicon.ico
inflating: vnc/www/Instrument/novnc/images/favicon.png
inflating: vnc/www/Instrument/novnc/images/full_screen.png
inflating: vnc/www/Instrument/novnc/images/hide.gif
inflating: vnc/www/Instrument/novnc/images/keyboard.png
inflating: vnc/www/Instrument/novnc/images/left.png
inflating: vnc/www/Instrument/novnc/images/mouse_left.png
inflating: vnc/www/Instrument/novnc/images/mouse_middle.png
inflating: vnc/www/Instrument/novnc/images/mouse_none.png
inflating: vnc/www/Instrument/novnc/images/mouse_right.png
inflating: vnc/www/Instrument/novnc/images/new-down-24.png
inflating: vnc/www/Instrument/novnc/images/new-left-24.png
inflating: vnc/www/Instrument/novnc/images/new-right-24.png
inflating: vnc/www/Instrument/novnc/images/new-up-24.png
inflating: vnc/www/Instrument/novnc/images/power.png
inflating: vnc/www/Instrument/novnc/images/press_new.png
inflating: vnc/www/Instrument/novnc/images/right.png
inflating: vnc/www/Instrument/novnc/images/r_left-16.png
inflating: vnc/www/Instrument/novnc/images/r_right-16.png
inflating: vnc/www/Instrument/novnc/images/screen_320x460.png
inflating: vnc/www/Instrument/novnc/images/screen_57x57.png
inflating: vnc/www/Instrument/novnc/images/screen_700x700.png
inflating: vnc/www/Instrument/novnc/images/settings.png
inflating: vnc/www/Instrument/novnc/images/showextrakeys.png
inflating: vnc/www/Instrument/novnc/images/stop.png
inflating: vnc/www/Instrument/novnc/images/tab.png
creating: vnc/www/Instrument/novnc/include/
inflating: vnc/www/Instrument/novnc/include/base.css
inflating: vnc/www/Instrument/novnc/include/base64.js
inflating: vnc/www/Instrument/novnc/include/base_mobile.css
inflating: vnc/www/Instrument/novnc/include/base_novnc.css
inflating: vnc/www/Instrument/novnc/include/black.css
inflating: vnc/www/Instrument/novnc/include/blue.css
creating: vnc/www/Instrument/novnc/include/chrome-app/
inflating: vnc/www/Instrument/novnc/include/chrome-app/tcp-client.js
inflating: vnc/www/Instrument/novnc/include/des.js
inflating: vnc/www/Instrument/novnc/include/display.js
inflating: vnc/www/Instrument/novnc/include/input.js
inflating: vnc/www/Instrument/novnc/include/jsunzip.js
inflating: vnc/www/Instrument/novnc/include/keyboard.js
inflating: vnc/www/Instrument/novnc/include/keysym.js
inflating: vnc/www/Instrument/novnc/include/keysymdef.js
inflating: vnc/www/Instrument/novnc/include/logo.js
inflating: vnc/www/Instrument/novnc/include/Orbitron700.ttf
inflating: vnc/www/Instrument/novnc/include/Orbitron700.woff
inflating: vnc/www/Instrument/novnc/include/playback.js
inflating: vnc/www/Instrument/novnc/include/rfb.js
inflating: vnc/www/Instrument/novnc/include/ui.js
inflating: vnc/www/Instrument/novnc/include/util.js
creating: vnc/www/Instrument/novnc/include/web-socket-js/
inflating: vnc/www/Instrument/novnc/include/web-socket-js/README.txt
inflating: vnc/www/Instrument/novnc/include/web-socket-js/swfobject.js
inflating: vnc/www/Instrument/novnc/include/web-socket-js/WebSocketMain.swf
inflating: vnc/www/Instrument/novnc/include/web-socket-js/web_socket.js
inflating: vnc/www/Instrument/novnc/include/websock.js
inflating: vnc/www/Instrument/novnc/include/webutil.js
inflating: vnc/www/Instrument/novnc/LICENSE.txt
inflating: vnc/www/Instrument/novnc/README.md
inflating: vnc/www/Instrument/novnc/vnc.html
inflating: vnc/www/Instrument/novnc/vnc_auto.html
inflating: vnc/www/Instrument/novnc/vnc_auto.php
inflating: vnc/www/Instrument/novnc/vnc_auto_mobile.php
creating: vnc/www/js/
inflating: vnc/www/js/cycle.js
creating: vnc/www/js/device/
inflating: vnc/www/js/device/t_table.js
inflating: vnc/www/js/home_info.js
inflating: vnc/www/js/iscroll.js
inflating: vnc/www/js/jquery.cookie.js
inflating: vnc/www/js/jquery.fileupload.js
inflating: vnc/www/js/jquery.iframe-transport.js
inflating: vnc/www/js/jquery.min.js
inflating: vnc/www/js/jquery.pagination.js
inflating: vnc/www/js/jquery.transit.min.js
inflating: vnc/www/js/jquery.wordexport.js
creating: vnc/www/js/JSON-js-master/
inflating: vnc/www/js/JSON-js-master/cycle.js
inflating: vnc/www/js/JSON-js-master/json2.js
inflating: vnc/www/js/JSON-js-master/json_parse.js
inflating: vnc/www/js/JSON-js-master/json_parse_state.js
inflating: vnc/www/js/JSON-js-master/README
inflating: vnc/www/js/json2.js
inflating: vnc/www/js/json_parse.js
inflating: vnc/www/js/json_parse_state.js
inflating: vnc/www/js/lan_config.js
inflating: vnc/www/js/log_in.js
inflating: vnc/www/js/main.js
inflating: vnc/www/js/mcplib.js
inflating: vnc/www/js/npm.js
inflating: vnc/www/js/TweenMax.min.js
creating: vnc/www/js/vendor/
inflating: vnc/www/js/vendor/jquery.ui.widget.js
inflating: vnc/www/js/xhtml
inflating: vnc/www/js/xhtml1-transitional.dtd
inflating: vnc/www/lan.php
inflating: vnc/www/lan_setting.php
creating: vnc/www/log/
inflating: vnc/www/log/lighttpd_error.log
inflating: vnc/www/login.php
inflating: vnc/www/logout.php
inflating: vnc/www/SCPI_control.php
creating: vnc/www/src/
inflating: vnc/www/src/IDN.php
inflating: vnc/www/src/index.html
inflating: vnc/www/vncserver.conf
inflating: vnc/www/welcome.php
inflating: upgrade.sh
inflating: upgrade_add.sh
inflating: upgrade_app.sh
inflating: upgrade_drivers.sh
inflating: upgrade_plat.sh
inflating: upgrade_sys.sh
inflating: upgrade_vnc.sh
update.sh starting ...
current version:
[ 995.736436] UBIFS: background thread "ubifs_bgt2_0" started, PID 1337
rm: can't remove '/usr/bin/siglent/usr/usr/upgrade/*.ADS': No such file or directory
rm: can't remove '/usr/bin/siglent/usr/*.zip': No such file or directory
rm: can't remove '/usr/bin/siglent/usr/*.ADS': No such file or directory
rm: can't remove '/tmp/*.zip': No such file or directory
rm: can't remove '/tmp/*.ADS': No such file or directory
upgrade_app: starting
cp -rpf /usr/bin/siglent/usr/usr/upgrade/app/startup_app.sh /usr/bin/siglent/
cp -rpf /usr/bin/siglent/usr/usr/upgrade/app/upgrade_app1.sh /usr/bin/siglent/usr/backup/
upgrade_app: ending
upgrade_add: upgrade /usr/bin/siglent/usr/usr/upgrade/add/NSP_config_upgrade_info.xml
upgrade_add: upgrade /usr/bin/siglent/usr/usr/upgrade/add/log4cpp.properties
upgrade_add: upgrade /usr/bin/siglent/usr/usr/upgrade/add/help
upgrade_add: upgrade /usr/bin/siglent/usr/usr/upgrade/add/Limits
upgrade_add: rm /usr/bin/siglent/usr/usr/upgrade/add -rf
upgrade_add: ending
upgrade_drivers: starting
cp -rpf /usr/bin/siglent/usr/usr/upgrade/drivers/* /usr/bin/siglent/drivers/
upgrade_app: ending
upgrade_vnc: starting
-rpf /usr/bin/siglent/usr/usr/upgrade/vnc/startup_vnc.sh /usr/bin/siglent/
-rpf /usr/bin/siglent/usr/usr/upgrade/vnc/vncserver /usr/bin/siglent/
-rpf /usr/bin/siglent/usr/usr/upgrade/vnc/lighttpd.conf /usr/bin/siglent/
-rpf /usr/bin/siglent/usr/usr/upgrade/vnc/php.ini /usr/bin/siglent/
-rpf /usr/bin/siglent/usr/usr/upgrade/vnc/lib /usr/bin/siglent/
rm /usr/bin/siglent/config/www/ -rf
cp -rpf /usr/bin/siglent/usr/usr/upgrade/vnc/www/ /usr/bin/siglent/config/
mv: can't rename '/usr/bin/siglent/config/www/php.ini': No such file or directory
mv: can't rename '/usr/bin/siglent/config/www/lighttpd.conf': No such file or directory
rm: invalid option -- 'p'
BusyBox v1.26.0.git (2016-12-08 18:50:51 CST) multi-call binary.
Usage: rm [-irf] FILE...
Remove (unlink) FILEs
-i Always prompt before removing
-f Never prompt
-R,-r Recurse
rm /usr/bin/siglent/usr/usr/upgrade/vnc -rf
upgrade_vnc: ending
upgrade_sys: starting
/usr/bin/siglent/usr/usr/upgrade/sys/uImage upgrade starting
upgrade /usr/bin/siglent/usr/usr/upgrade/sys/uImage
Erasing 128 Kibyte @ 3e0000 -- 100 % complete
Writing at 0x00000000
Writing at 0x00020000
Writing at 0x00040000
Writing at 0x00060000
Writing at 0x00080000
Writing at 0x000a0000
Writing at 0x000c0000
Writing at 0x000e0000
Writing at 0x00100000
Writing at 0x00120000
Writing at 0x00140000
Writing at 0x00160000
Writing at 0x00180000
Writing at 0x001a0000
Writing at 0x001c0000
Writing at 0x001e0000
Writing at 0x00200000
Writing at 0x00220000
Writing at 0x00240000
Writing at 0x00260000
Writing at 0x00280000
Writing at 0x002a0000
Writing at 0x002c0000
Writing at 0x002e0000
/usr/bin/siglent/usr/usr/upgrade/sys/uImage upgrade ending
upgrade_uimage /usr/bin/siglent/usr/usr/upgrade/sys/uImage
upgrade_sys: /usr/bin/siglent/usr/usr/upgrade/sys/rootfs.cramfs is not exist
upgrade_sys: ending
upgrade_plat.sh: starting
upgrade_vnc1: ending
cp -rpf ./vnc/vdma_vnc.sh /usr/bin/siglent/
cp -rpf ./vnc/vncserver.conf /usr/bin/siglent/config/www/
upgrade_vnc1: ending
upgrade_fpga: starting
cp -rpf ./fpga/*.sh /usr/bin/siglent/config/fpga/
cp -rpf ./fpga/plat /usr/bin/siglent/config/fpga/
cp -rpf ./fpga/plat /usr/bin/siglent/firmdata0/
cp ./fpga/fpga_top.bit /usr/bin/siglent/config/fpga/fpga_top.bit
upgrade_fpga: ending
upgrade_dtb: starting
upgrade_app: there is no *.dtb to upgrade
upgrade_dtb: ending
upgrade_uboot.sh: starting
./boot/BOOT.bin upgrade starting
upgrade ./boot/BOOT.bin
Erasing 128 Kibyte @ 760000 -- 100 % complete
Writing at 0x00000000
Writing at 0x00020000
Writing at 0x00040000
Writing at 0x00060000
Writing at 0x00080000
Writing at 0x000a0000
Writing at 0x000c0000
Writing at 0x000e0000
Writing at 0x00100000
Writing at 0x00120000
Writing at 0x00140000
Writing at 0x00160000
Writing at 0x00180000
Writing at 0x001a0000
Writing at 0x001c0000
Writing at 0x001e0000
Writing at 0x00200000
Writing at 0x00220000
Writing at 0x00240000
Writing at 0x00260000
Writing at 0x00280000
Writing at 0x002a0000
Writing at 0x002c0000
Writing at 0x002e0000
Writing at 0x00300000
Writing at 0x00320000
Writing at 0x00340000
Writing at 0x00360000
Writing at 0x00380000
Writing at 0x003a0000
Writing at 0x003c0000
Writing at 0x003e0000
Writing at 0x00400000
Writing at 0x00420000
Writing at 0x00440000
Writing at 0x00460000
Writing at 0x00480000
Writing at 0x004a0000
Writing at 0x004c0000
Writing at 0x004e0000
Writing at 0x00500000
Writing at 0x00520000
Writing at 0x00540000
Writing at 0x00560000
Writing at 0x00580000
Writing at 0x005a0000
Writing at 0x005c0000
Writing at 0x005e0000
./boot/BOOT.bin upgrade ending
upgrade_uboot.sh: ending
upgrade_plat.sh: ending
[ 1021.122455] reboot: Restarting system
U-Boot 2014.07-svn118162 (Sep 03 2020 - 12:37:11)
Board: Xilinx Zynq
I2C: ready
DRAM: ECC disabled 128 MiB
NAND: 256 MiB
MMC: zynq_sdhci: 0
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
int board_late_init(void)+++++
buzzer_off---------------
buzzer_on---------------
buzzer_off---------------
int board_late_init(void)-----
Net: Gem.e000b000
Hit any key to stop autoboot: 0
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
USB1: ULPI request timed out
zynq ULPI viewport init failed
lowlevel init failed
scanning usb for storage devices... 1 Storage Device(s) found
Copying Linux from USB to RAM...
reading boot_uImage
** Unable to read file boot_uImage **
reading sva1000x_udiskEnv.txt
** Unable to read file sva1000x_udiskEnv.txt **
Copying Linux from NAND flash to RAM...
NAND read: device 0 offset 0x780000, size 0x400000
4194304 bytes read: OK
NAND read: device 0 offset 0xb80000, size 0x80000
524288 bytes read: OK
## Booting kernel from Legacy Image at 02080000 ...
Image Name: Linux-3.19.2-omg-xilinx-svn35686
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3121840 Bytes = 3 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Flattened Device Tree blob at 02000000
Booting using the fdt blob at 0x2000000
EHCI failed to shut down host controller.
Loading Kernel Image ... OK
Loading Device Tree to 06d0d000, end 06d13db2 ... OK
Starting kernel ...
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 3.19.2-omg-xilinx-svn35686 (ding@ding-T5810) (gcc version 4.6.1 (Sourcery CodeBench Lite 2011.09-50) ) #11 SMP PREEMPT Fri Jan 4 15:28:26 CST 2019
[ 0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine model: Zynq Zed Development Board
[ 0.000000] cma: Reserved 16 MiB at 0x09000000
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] PERCPU: Embedded 9 pages/cpu @48e92000 s8128 r8192 d20544 u36864
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 40640
[ 0.000000] Kernel command line: console=ttyPS0,115200 root=/dev/mtdblock5 rootfstype=cramfs init=/linuxrc earlyprintk uboot_version=3
[ 0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Memory: 139704K/163840K available (3835K kernel code, 213K rwdata, 1580K rodata, 196K init, 216K bss, 7752K reserved, 16384K cma-reserved, 0K highmem)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
[ 0.000000] vmalloc : 0x4a800000 - 0xff000000 (2888 MB)
[ 0.000000] lowmem : 0x40000000 - 0x4a000000 ( 160 MB)
[ 0.000000] pkmap : 0x3fe00000 - 0x40000000 ( 2 MB)
[ 0.000000] modules : 0x3f000000 - 0x3fe00000 ( 14 MB)
[ 0.000000] .text : 0x40008000 - 0x40552200 (5417 kB)
[ 0.000000] .init : 0x40553000 - 0x40584000 ( 196 kB)
[ 0.000000] .data : 0x40584000 - 0x405b96a0 ( 214 kB)
[ 0.000000] .bss : 0x405b96a0 - 0x405ef914 ( 217 kB)
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
[ 0.000000] L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
[ 0.000000] L2C-310 erratum 769419 enabled
[ 0.000000] L2C-310 enabling early BRESP for Cortex-A9
[ 0.000000] L2C-310 full line of zeros enabled for Cortex-A9
[ 0.000000] L2C-310 ID prefetch enabled, offset 1 lines
[ 0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled
[ 0.000000] L2C-310 cache controller enabled, 8 ways, 512 kB
[ 0.000000] L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
[ 0.000000] slcr mapped to 4a804000
[ 0.000000] zynq_clock_init: clkc starts at 4a804100
[ 0.000000] Zynq clock init
[ 0.000010] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 3298534883328ns
[ 0.000128] timer #0 at 4a806000, irq=17
[ 0.000479] Console: colour dummy device 80x30
[ 0.000498] Calibrating delay loop... 1332.01 BogoMIPS (lpj=6660096)
[ 0.090271] pid_max: default: 32768 minimum: 301
[ 0.090420] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.090436] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.091064] CPU: Testing write buffer coherency: ok
[ 0.091263] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.091331] Setting up static identity map for 0x39c880 - 0x39c8d8
[ 0.240259] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.240337] Brought up 2 CPUs
[ 0.240356] SMP: Total of 2 processors activated (2664.03 BogoMIPS).
[ 0.240365] CPU: All CPU(s) started in SVC mode.
[ 0.240860] devtmpfs: initialized
[ 0.241578] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[ 0.247188] NET: Registered protocol family 16
[ 0.249136] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.271082] cpuidle: using governor ladder
[ 0.301045] cpuidle: using governor menu
[ 0.309122] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[ 0.309139] hw-breakpoint: maximum watchpoint size is 4 bytes.
[ 0.309269] zynq-ocm f800c000.ocmc: ZYNQ OCM pool: 256 KiB @ 0x4a880000
[ 0.319863] vgaarb: loaded
[ 0.320351] SCSI subsystem initialized
[ 0.320750] usbcore: registered new interface driver usbfs
[ 0.320838] usbcore: registered new interface driver hub
[ 0.320938] usbcore: registered new device driver usb
[ 0.321086] phy0 supply vcc not found, using dummy regulator
[ 0.321195] phy1 supply vcc not found, using dummy regulator
[ 0.321302] --------------usb_udc_init ------
[ 0.321561] pps_core: LinuxPPS API ver. 1 registered
[ 0.321574] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.321624] PTP clock support registered
[ 0.321895] EDAC MC: Ver: 3.0.0
[ 0.323332] Switched to clocksource arm_global_timer
[ 0.335260] NET: Registered protocol family 2
[ 0.336012] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.336063] TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
[ 0.336120] TCP: Hash tables configured (established 2048 bind 2048)
[ 0.336165] TCP: reno registered
[ 0.336182] UDP hash table entries: 256 (order: 1, 8192 bytes)
[ 0.336215] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[ 0.336417] NET: Registered protocol family 1
[ 0.336783] RPC: Registered named UNIX socket transport module.
[ 0.336796] RPC: Registered udp transport module.
[ 0.336805] RPC: Registered tcp transport module.
[ 0.336813] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.337186] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
[ 0.338536] futex hash table entries: 512 (order: 3, 32768 bytes)
[ 0.340151] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[ 0.341179] io scheduler noop registered
[ 0.341200] io scheduler deadline registered
[ 0.341258] io scheduler cfq registered (default)
[ 0.343379] dma-pl330 f8003000.dmac: Loaded driver for PL330 DMAC-241330
[ 0.343399] dma-pl330 f8003000.dmac: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[ 0.343869] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 145, base_baud = 2500000) is a xuartps
[ 0.917206] console [ttyPS0] enabled
[ 0.921351] xdevcfg f8007000.devcfg: ioremap 0xf8007000 to 4a878000
[ 0.928113] [drm] Initialized drm 1.1.0 20060810
[ 0.940616] brd: module loaded
[ 0.947608] loop: module loaded
[ 0.956819] libphy: MACB_mii_bus: probed
[ 1.033452] macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 149 (00:0a:35:00:01:23)
[ 1.043352] macb e000b000.ethernet eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:1e, irq=-1)
[ 1.054887] i2c /dev entries driver
[ 1.060188] rtc-ds1307 0-0068: rtc core: registered ds1340 as rtc0
[ 1.066631] cdns-i2c e0004000.i2c: 400 kHz mmio e0004000 irq 143
[ 1.073893] zynq-edac f8006000.memory-controller: ecc not enabled
[ 1.080108] Xilinx Zynq CpuIdle Driver started
[ 1.085189] ledtrig-cpu: registered to indicate activity on CPUs
[ 1.092203] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[ 1.098515] nand: Micron MT29F2G08ABAEAWP
[ 1.102493] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 1.110086] nand: WARNING: pl353-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
[ 1.121596] Bad block table found at page 131008, version 0x01
[ 1.127871] Bad block table found at page 130944, version 0x01
[ 1.134010] 12 ofpart partitions found on MTD device pl353-nand
[ 1.139857] Creating 12 MTD partitions on "pl353-nand":
[ 1.145114] 0x000000000000-0x000000780000 : "fsbl"
[ 1.150932] 0x000000780000-0x000000b80000 : "kerneldata"
[ 1.157209] 0x000000b80000-0x000000c00000 : "device-tree"
[ 1.163553] 0x000000c00000-0x000001100000 : "Manufacturedata"
[ 1.170248] 0x000001100000-0x000001600000 : "reserved1"
[ 1.176450] 0x000001600000-0x000003e00000 : "rootfs"
[ 1.182318] 0x000003e00000-0x000004800000 : "firmdata0"
[ 1.188487] 0x000004800000-0x000006c00000 : "siglent"
[ 1.194536] 0x000006c00000-0x00000d000000 : "datafs"
[ 1.200540] 0x00000d000000-0x00000da00000 : "log"
[ 1.206236] 0x00000da00000-0x00000f800000 : "upgrade_cramdisk"
[ 1.213038] 0x00000f800000-0x000010000000 : "reserved2"
[ 1.221121] TCP: cubic registered
[ 1.224613] NET: Registered protocol family 17
[ 1.229238] Registering SWP/SWPB emulation handler
[ 1.235909] rtc-ds1307 0-0068: setting system clock to 2021-01-25 02:28:45 UTC (1611541725)
[ 1.249348] cramfs_fill_nand blocks is 320-----------------------
[ 1.249348]
[ 1.249348]
[ 1.249348]
[ 1.262390] VFS: Mounted root (cramfs filesystem) readonly on device 31:5.
[ 1.269286] devtmpfs: mounted
[ 1.272427] Freeing unused kernel memory: 196K (40553000 - 40584000)
Starting rcS...
[ 1.545467] UBI-1: ubi_attach_mtd_dev:attaching mtd7 to ubi1
[ 1.693853] UBI-1: scan_all:scanning is finished
[ 1.704846] UBI-1 warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 3, need 40
[ 1.716002] UBI-1: ubi_attach_mtd_dev:attached mtd7 (name "siglent", size 36 MiB)
[ 1.723466] UBI-1: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 1.732032] UBI-1: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 1.740576] UBI-1: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[ 1.749274] UBI-1: ubi_attach_mtd_dev:good PEBs: 288, bad PEBs: 0, corrupted PEBs: 0
[ 1.757027] UBI-1: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[ 1.765979] UBI-1: ubi_attach_mtd_dev:max/mean erase counter: 17/8, WL threshold: 4096, image sequence number: 1299742721
[ 1.776939] UBI-1: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 288, PEBs reserved for bad PEB handling: 3
[ 1.787829] UBI-1: ubi_thread:background thread "ubi_bgt1d" started, PID 582
[ 1.790223] UBI-2: ubi_attach_mtd_dev:attaching mtd6 to ubi2
[ 1.834489] UBI-2: scan_all:scanning is finished
[ 1.845288] UBI-2 warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 9, need 40
[ 1.856295] UBI-2: ubi_attach_mtd_dev:attached mtd6 (name "firmdata0", size 10 MiB)
[ 1.863916] UBI-2: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 1.872502] UBI-2: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 1.881044] UBI-2: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[ 1.889744] UBI-2: ubi_attach_mtd_dev:good PEBs: 80, bad PEBs: 0, corrupted PEBs: 0
[ 1.897398] UBI-2: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[ 1.906360] UBI-2: ubi_attach_mtd_dev:max/mean erase counter: 87/43, WL threshold: 4096, image sequence number: 2009223325
[ 1.917408] UBI-2: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 80, PEBs reserved for bad PEB handling: 9
[ 1.928216] UBI-2: ubi_thread:background thread "ubi_bgt2d" started, PID 586
[ 1.934978] UBI-3: ubi_attach_mtd_dev:attaching mtd9 to ubi3
[ 1.974879] UBI-3: scan_all:scanning is finished
[ 1.985661] UBI-3 warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 9, need 40
[ 1.996668] UBI-3: ubi_attach_mtd_dev:attached mtd9 (name "log", size 10 MiB)
[ 2.003765] UBI-3: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 2.012346] UBI-3: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 2.020887] UBI-3: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[ 2.029583] UBI-3: ubi_attach_mtd_dev:good PEBs: 80, bad PEBs: 0, corrupted PEBs: 0
[ 2.037262] UBI-3: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[ 2.046250] UBI-3: ubi_attach_mtd_dev:max/mean erase counter: 8/4, WL threshold: 4096, image sequence number: 1866265482
[ 2.057098] UBI-3: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 80, PEBs reserved for bad PEB handling: 9
[ 2.067882] UBI-3: ubi_thread:background thread "ubi_bgt3d" started, PID 590
[ 2.070055] UBI-0: ubi_attach_mtd_dev:attaching mtd8 to ubi0
[ 2.470806] UBI-0: scan_all:scanning is finished
[ 2.483096] UBI-0: ubi_attach_mtd_dev:attached mtd8 (name "datafs", size 100 MiB)
[ 2.490537] UBI-0: ubi_attach_mtd_dev:PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 2.499140] UBI-0: ubi_attach_mtd_dev:min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 2.507666] UBI-0: ubi_attach_mtd_dev:VID header offset: 2048 (aligned 2048), data offset: 4096
[ 2.516372] UBI-0: ubi_attach_mtd_dev:good PEBs: 800, bad PEBs: 0, corrupted PEBs: 0
[ 2.524109] UBI-0: ubi_attach_mtd_dev:user volume: 1, internal volumes: 1, max. volumes count: 128
[ 2.533060] UBI-0: ubi_attach_mtd_dev:max/mean erase counter: 13/7, WL threshold: 4096, image sequence number: 626955013
[ 2.543946] UBI-0: ubi_attach_mtd_dev:available PEBs: 0, total reserved PEBs: 800, PEBs reserved for bad PEB handling: 40
[ 2.554922] UBI-0: ubi_thread:background thread "ubi_bgt0d" started, PID 594
[ 2.574878] UBIFS: background thread "ubifs_bgt1_0" started, PID 597
[ 2.606420] UBIFS: recovery needed
[ 2.746423] UBIFS: recovery completed
[ 2.750095] UBIFS: mounted UBI device 1, volume 0, name "siglent"
[ 2.756147] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 2.765267] UBIFS: FS size: 34410496 bytes (32 MiB, 271 LEBs), journal size 4952064 bytes (4 MiB, 39 LEBs)
[ 2.774927] UBIFS: reserved for root: 0 bytes (0 KiB)
[ 2.779960] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 0327D069-3DA9-4070-95A1-3E1D117AABDE, small LPT model
[ 2.824779] UBIFS: recovery needed
[ 2.868505] UBIFS: recovery deferred
[ 2.872087] UBIFS: mounted UBI device 2, volume 0, name "firm0", R/O mode
[ 2.878830] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 2.887957] UBIFS: FS size: 7237632 bytes (6 MiB, 57 LEBs), journal size 1650688 bytes (1 MiB, 13 LEBs)
[ 2.897346] UBIFS: reserved for root: 0 bytes (0 KiB)
[ 2.902385] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 68D1D634-0B41-44C3-8EE7-5B148BE8F0D7, small LPT model
[ 2.916088] UBIFS: background thread "ubifs_bgt3_0" started, PID 600
[ 2.947719] UBIFS: recovery needed
[ 2.970471] UBIFS: recovery completed
[ 2.974165] UBIFS: mounted UBI device 3, volume 0, name "log"
[ 2.979839] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 2.988991] UBIFS: FS size: 7237632 bytes (6 MiB, 57 LEBs), journal size 1650688 bytes (1 MiB, 13 LEBs)
[ 2.998380] UBIFS: reserved for root: 0 bytes (0 KiB)
[ 3.003430] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 35E3C92F-68EC-461E-A46E-9F549FBFB3F1, small LPT model
[ 3.016864] UBIFS: background thread "ubifs_bgt0_0" started, PID 602
[ 3.048336] UBIFS: recovery needed
[ 3.125471] UBIFS: recovery completed
[ 3.129147] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[ 3.135109] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 3.144233] UBIFS: FS size: 94597120 bytes (90 MiB, 745 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
[ 3.153883] UBIFS: reserved for root: 0 bytes (0 KiB)
[ 3.158923] UBIFS: media format: w4/r0 (latest is w4/r0), UUID AB78C81C-0D18-4506-91AE-D6D46AF0DBD0, small LPT model
[ 5.601129] Unhandled fault: external abort on non-linefetch (0x818) at 0x36f1c380
Bus error
[ 5.628773] irq = 170
[ 5.640179] <<-GTP-INFO->> GTP driver installing...
[ 5.645226] <<-GTP-INFO->> GTP Driver Version: V2.4<2014/11/28>
[ 5.651076] <<-GTP-INFO->> GTP Driver Built@22:06:06, Apr 27 2018
[ 5.657201] <<-GTP-INFO->> GTP I2C Address: 0x14
[ 5.661800] 0-0014 supply vdd_ana not found, using dummy regulator
[ 5.668136] 0-0014 supply vcc_i2c not found, using dummy regulator
[ 5.674307] <<-GTP-INFO->> Guitar reset
[ 5.803831] <<-GTP-INFO->> IC Version: 928_1060
[ 5.814504] <<-GTP-INFO->> X_MAX: 1024, Y_MAX: 600, TRIGGER: 0x00
[ 5.833351] <<-GTP-INFO->> create proc entry gt9xx_config success
[ 5.839632] input: goodix-ts as /devices/virtual/input/input0
[ 5.845620] <<-GTP-INFO->> GTP works in interrupt mode.
[ 5.861240] gpib_usb_init
[ 5.864015] usbcore: registered new interface driver usb-gpib
startup_app.sh start++++++++++
rm -f /usr/bin/siglent/usr/*.ADS
upgrade_app1: starting
-rpf /usr/bin/siglent/usr/usr/upgrade/app/* /usr/bin/siglent/
upgrade_app1: ending
/usr/bin/siglent/usr/backup/upgrade_app1.sh
rm /usr/bin/siglent/usr/backup/upgrade_app1.sh -rf
rm /usr/bin/siglent/usr/usr/upgrade/* -[ 10.470122] UBIFS: background thread "ubifs_bgt1_0" stops
rf
startup_app.sh end++++++++++
[ 11.580464] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 11.592180] ehci-pci: EHCI PCI platform driver
[ 11.634512] e0002000.usb supply vbus not found, using dummy regulator
[ 11.641398] ci_hdrc ci_hdrc.0: EHCI Host Controller
[ 11.646505] ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 1
[ 11.673372] ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00
[ 11.678901] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 11.685713] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 11.692896] usb usb1: Product: EHCI Host Controller
[ 11.697778] usb usb1: Manufacturer: Linux 3.19.2-omg-xilinx-svn35686 ehci_hcd
[ 11.704917] usb usb1: SerialNumber: ci_hdrc.0
[ 11.710067] hub 1-0:1.0: USB hub found
[ 11.713832] hub 1-0:1.0: 1 port detected
[ 11.719484] e0003000.usb supply vbus not found, using dummy regulator
[ 11.782258] usbcore: registered new interface driver usb-storage
[ 11.813185] usbcore: registered new interface driver usbhid
[ 11.818839] usbhid: USB HID core driver
[ 11.828922] mousedev: PS/2 mouse device common for all mice
[ 12.033456] usb 1-1: new high-speed USB device number 2 using ci_hdrc
[ 12.040055] macb e000b000.ethernet eth0: link up (100/Full)
[ 12.209127] usb 1-1: New USB device found, idVendor=154b, idProduct=00ee
[ 12.215816] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 12.222927] usb 1-1: Product: USB 2.0 FD
[ 12.226843] usb 1-1: Manufacturer: PNY
[ 12.230558] usb 1-1: SerialNumber: No!
[ 12.236388] usb-storage 1-1:1.0: USB Mass Storage device detected
[ 12.245830] scsi host0: usb-storage 1-1:1.0
[ 13.247158] random: Aladdin urandom read with 21 bits of entropy available
log init finished
[ 13.407710] spidev spi1.1: setup: unsupported mode bits 50
set_output_level ===============10.000000
set_output_level ===============10.000000
[ 13.509200] UBIFS: completing deferred recovery
[ 13.538289] UBIFS: deferred recovery completed
[ 13.543169] UBIFS: background thread "ubifs_bgt2_0" started, PID 773
route: SIOCDELRT: No such process
system cmd error!WEXITSTATUS(result) = 1
route del default: Success
[ 13.600205] UBIFS: background thread "ubifs_bgt2_0" stops
[ 13.624381] UBIFS: background thread "ubifs_bgt2_0" started, PID 785
[ 13.667743] UBIFS: background thread "ubifs_bgt2_0" stops
[ 13.682381] UBIFS: background thread "ubifs_bgt2_0" started, PID 795
[ 13.700014] UBIFS: background thread "ubifs_bgt2_0" stops
[ 13.715190] UBIFS: background thread "ubifs_bgt2_0" started, PID 800
[ 14.143379] UBIFS: background thread "ubifs_bgt2_0" stops
[ 14.159201] UBIFS: background thread "ubifs_bgt2_0" started, PID 812
[ 14.178515] UBIFS: background thread "ubifs_bgt2_0" stops
[ 14.194933] UBIFS: background thread "ubifs_bgt2_0" started, PID 817
[ 14.219471] UBIFS: background thread "ubifs_bgt2_0" stops
[ 14.241242] UBIFS: background thread "ubifs_bgt2_0" started, PID 822
[ 14.261210] UBIFS: background thread "ubifs_bgt2_0" stops
[ 14.648871] <<-GTP-INFO->> System resume.
[ 14.648882] gpio-963 (GTP INT IRQ): _gpiod_direction_output_raw: tried to set a GPIO tied to an IRQ as output
[ 14.663516] <<-GTP-INFO->> GTP wakeup sleep.
[ 14.663525] gpio-963 (GTP INT IRQ): _gpiod_direction_output_raw: tried to set a GPIO tied to an IRQ as output
[ 14.852156] UBIFS: background thread "ubifs_bgt2_0" started, PID 827
[ 14.886746] UBIFS: background thread "ubifs_bgt2_0" stops
[ 14.921098] UBIFS: background thread "ubifs_bgt2_0" started, PID 832
[ 14.936315] UBIFS: background thread "ubifs_bgt2_0" stops
rotationAngle: 0 invertx: false inverty: false
rotationAngle: 0 invertx: false inverty: false
[ 15.455346] scsi 0:0:0:0: Direct-Access PNY USB 2.0 FD PMAP PQ: 0 ANSI: 6
[ 15.464911] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 15.470572] sd 0:0:0:0: [sda] 30294016 512-byte logical blocks: (15.5 GB/14.4 GiB)
[ 15.480642] sd 0:0:0:0: [sda] Write Protect is off
[ 15.487130] sd 0:0:0:0: [sda] No Caching mode page found
[ 15.492371] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 15.510395] sda: sda1
insert~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[ 15.521404] sd 0:0:0:0: [sda] Attached SCSI removable disk
devName ==sda
devName ==sda1
sda1
sleep time == 0
[ 15.548167] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
/usr/bin/siglent/usr/tmp/sda1_U-disk0
device:IVISoftwareModuleName:: node error!device:ManufacturerDescription:: node error!found the dir = /usr/bin/siglent/usr/mass_storage/U-disk0
[ 17.045293] UBIFS: background thread "ubifs_bgt2_0" started, PID 857
[ 17.070323] UBIFS: background thread "ubifs_bgt2_0" stops
0x00000000
0x00000000
Initializing framebuffer device /dev/fb0...
xres=1024, yres=600, xre[ 21.994683] input: PolyVision Touch Screen as /devices/virtual/input/input1
sv=1024, yresv=600, xoffs=0, yoffs=0, bpp=16
Initializing touch device /dev/input/event0 ...
Reading From :(goodix-ts)
buttonMask: xmin:0
xmax: 1024
ymin:0
ymax: 600
Initializing VNC server:
width: 1024
height: 600
bpp: 16
port: 5900
Initializing server...
25/01/2021 02:29:06 Listening for VNC connections on TCP port 5900
rcS Complete
(none) login:
usbtmc_para = insmod /usr/bin/siglent/drivers/g_usbtmc.ko idVendor=0xf4ec idProduct=0x1301 iManufacturer=Siglent iProduct=SVA1032X iSerialNum=No!
insmod: can't insert '/usr/bin/siglent/drivers/libcomposite.ko': File exists
insmod: can't read '/usr/bin/siglent/drivers/udc-xilinx.ko': No such file or directory
system cmd error!WEXITSTATUS(result) = 1
insmod /usr/bin/siglent/drivers/libcomposite.ko;insmod /usr/bin/siglent/drivers/udc-xilinx.ko;: No such file or directory
[ 30.526827] ######################### usb_gadget_probe_driver 3f09d738 ##################
[ 30.535106] usbtmc_bind+++
[ 30.539994] SIGLENT_DEV: SIGLENT_DEV, version: 2007 OCT 06
[ 30.546478] usbtmc_open()++
[ 30.549212] dev->usbtmc_cdev_open ret = 0
[ 30.553232] ret = 0
[ 30.555355] usbtmc_open--
[ 30.558067] show_send_buffer_size = 61440
Definitely not working with the telnet script from 31st May 2020.
In fact, even weirder, trying to run the script, it times out after 60 seconds. I've never had that before, used to be able to run it for as long you wished.
Upgrade log
reading sva1000x_udiskEnv.txt
** Unable to read file sva1000x_udiskEnv.txt **
Definitely not working with the telnet script from 31st May 2020.
In fact, even weirder, trying to run the script, it times out after 60 seconds. I've never had that before, used to be able to run it for as long you wished.
EDIT: Tried 2 other USB sticks to make sure, and also the SSA version, same result.
Some other Siglent equipments also do that. One needs to make the script stay awake a bit longer... :) (I didn't do that in these cases, but I could if now it's needed)
Upgrade log
Have you noticed this?Code: [Select]reading sva1000x_udiskEnv.txt
** Unable to read file sva1000x_udiskEnv.txt **
It checks the USB disk for a env file when booting... ::)
Machine model: Zynq Zed Development Board
:popcorn:
Where can i find the latest working NAND Backup script for the SVA1032?
Will do a backup before i update it...
Unfortunally this script isn't working on my SVA1032.
It's doing something but relatively short (30s or so) then its rebooting but nothing is on the USB thumbdrive
Unfortunally this script isn't working on my SVA1032.
It's doing something but relatively short (30s or so) then its rebooting but nothing is on the USB thumbdrive
Please try this one.
It kills the Aladdin process, before starting telnet.
Regards,
Vitor
Or this one.
Port 10101.
Best if you just use the Cal kit you have and do the calibration and save it with a name that suits you.
Some tips in the Help file:
VNA>Meas setup>Calibration
Process is:
Select VNA mode.
Enter Calibration.
Select Cal kit>Next
Select User 1 or 2 and follow calibration steps.
Enter File menu.
Set to browse file.
Change View and Save type to Cal.
Press Save on the front panel and use the keypad to name your Calibration.
Example attached.
In use, Correction = ON
Can someone test this telnet script on SVA1032X with latest FW?
Port is 10101.
Yes , it works !!! :D
What is most interesting is that now (with V3.2.2.4.0 FW), all the models SVA1015X, SVA1032X, SVA1075X have the same ProductID = 11410 !!! ::)Check datasheets first. ;)
Does that mean we can upgrade them all to 7.5GHz?!? (Who wants to try?)
What is most interesting is that now (with V3.2.2.4.0 FW), all the models SVA1015X, SVA1032X, SVA1075X have the same ProductID = 11410 !!! ::)
Does that mean we can upgrade them all to 7.5GHz?!? (Who wants to try?)
Does it mean they will differentiate them through other means?!?
What is most interesting is that now (with V3.2.2.4.0 FW), all the models SVA1015X, SVA1032X, SVA1075X have the same ProductID = 11410 !!! ::)Nah, I am sure they have different components, not just the RF circuitry. I think someone did a teardown of the SVA1032X comparing it to the SVA1015X?
Does that mean we can upgrade them all to 7.5GHz?!? (Who wants to try?)
Does it mean they will differentiate them through other means?!?
Yep, 3 models in the SVA range each with different specs and even different instrument weights.What is most interesting is that now (with V3.2.2.4.0 FW), all the models SVA1015X, SVA1032X, SVA1075X have the same ProductID = 11410 !!! ::)Nah, I am sure they have different components, not just the RF circuitry. I think someone did a teardown of the SVA1032X comparing it to the SVA1015X?
Does that mean we can upgrade them all to 7.5GHz?!? (Who wants to try?)
Does it mean they will differentiate them through other means?!?
Unless they release a new unified hw revision to simplify the supply chain? But I doubt it.
While flashing one to another may be possible it certainly won't meet datasheet spec.
Ony issue I can see is that there seems to be no spectrum display in RTSA mode? That said it might be operator error. Other modes are working fine.
I am deciding between a SSA3021X+ and SVA1015X, and note that from my distributor they are within 100 dollars of each other right now. So the obvious choice is the SVA1015X. Is there any reason to even consider the SSA then? I will be playing around with it in telnet, features and 3G.1.5 GHz models are a different HW platform and therefore have some different specs.
I am coming from an SSA3021X (non +), and a sdrkits VNA. I could consolidate to the one device.
Thanks for the heads up Tautech. I must need to find a better set of pages to look at, because SiglentNA lists tracking generator as standard for the SVA. :-//SSA3015X Plus and SVA1015X have a different TG spec to all other models...did you not see that ?
I only see that the SSA has a better DANL.
I am deciding between a SSA3021X+ and SVA1015X
I am deciding between a SSA3021X+ and SVA1015X
That's a no-brainer: get the SSA.
Hello,
at our company, we're going to purchase one of the here discussed SSA or SVA.
We're looking at both SSA3075X-R and SVA1075X, what do you suggest?
We will mainly work on 5.8GHz digital radios and some VNA in PCB traces and antennas.
The choice is very hard, and we're not sure we need realtime (but I have some applications for it in my mind too...).
Cheers!
Hello,
at our company, we're going to purchase one of the here discussed SSA or SVA.
We're looking at both SSA3075X-R and SVA1075X, what do you suggest?
We will mainly work on 5.8GHz digital radios and some VNA in PCB traces and antennas.
The choice is very hard, and we're not sure we need realtime (but I have some applications for it in my mind too...).
Cheers!
Sorry for the captain obvious: The only thing I can think of is to consider if you might want to use the real time bandwidth available on the XR
- i.e. if your 5.8GHz digital radios are hopping around then you will be able to see that on the XR but not on the SVA.
Real SVA1032X fully optioned.....
Sweep Time and IFBW are greyed out when in VNA mode.
Hi Guys, ok so i done the simple test of opening the Unit to check cables :phew:, they are all there, and its looking sweet in there! :-DD:clap:
Ok, here is the test with Emo's basic suggestion for testing and comparison to Tautech.
put on my adapter, then ran OPEN, SHORT and thn put a 50.1Ohm BNC load and ran all 3 reference calibrations.
Here is are the results. I think they look ok now.
What do you guys think of these now? Tautech, Emo, i think this is what it should resemble. Thoughts?
And yes Bicurico, i will definetely make or buy some cal kit when i am ready so i can properly mesure my antennas and all. But for now, its a start so i can learn. Thank you for your great help!
Thanks guys!
Marty
Is it me, or are the LeCroy VNAs rebadged Siglents? Any product differences other than the name on the badge?Yep it seems they are however only the 1.5 and 3.2 GHz models.
E.g., https://teledynelecroy.com/vector-network-analyzer/
Hello,Welcome to the forum.
I have a SVA1015X in version 2.2.1.2.5 that I cannot update (it stays with message Upgrading now, please wait... for hours)
telnet works. Could someone help me about what I can do please ?
Thank you.
Hi Tautech,Which version are you attempting to install ?
I managed to power off this way but I tried 10 times to update without success. Do you have an idea please ?
Thank you for your help.
I tried the last, 2.2.1.2.5 and 2.2.1.2.8 without success.You must install V2.1.1.1.13 before installing later versions.
But it's in 2.2.1.2.5OK then try V3.2.2.3.3R1 as one of fixes is: Fix upgrade failure issue
I tried this version without success.
But it's in 2.2.1.2.5OK then try V3.2.2.3.3R1 as one of fixes is: Fix upgrade failure issue
https://int.siglent.com/upload_file/zip/firmware/Spectrum_analyzer/SVA1015X_V3.2.2.3.3R1_EN.zip
I tried this version without success.OK we need know more.
Hello Tautech,PM sent.
It's not the original, I updated it with the hack tutorial.
My stick is 16 GB and FAT32 formatted (but the first that I used to this update was less than 8 GB)
I can see the file and select it but it never ends.
Do you have a 2.5 or later version of ecomb on you machine ? If yes could you send me it ?
If you have telnet could you give me the result of commands "mount" and df -Th ?
Thank you for your help.
All SVA1015 FW versions expect a Product ID 11402.As I understand facotl's unit is a factory SVA1015X with only options hacked but yes there maybe has been a mistake made but FW has been updated successfully before. We will get a solution soon from the factory to fix it.
If the upgrade fails, it might be because you changed the Product ID to a different number.
Note that the SVA1015 uses a different FW than the SVA1032 model. If you followed the hack, you probably entered a new Product ID matching the SVA1032 (Product ID 11403) instead of the SVA1015.
That might be the reason.
Regards,
Vitor
As I understand facotl's unit is a factory SVA1015X with only options hacked but yes there maybe has been a mistake made but FW has been updated successfully before. We will get a solution soon from the factory to fix it.
Hello all,Welcome to the forum.
new to eevblog and have got an SVA1032x, would like to know if you have an bluetooth-dongle with keyboard or mouse in use ? I have attached a picture from the review from Shahriar where he uses a mouse.
I have a bluetooth keyboard and a dongle from Delock but can´t get it to work. I think there must be a dongle with native drivers for the SVA ?
Any advice is welcome, the keyboard would be helpful for file input.
Thank you !
If it's the same as with the SDS200X+ oscilloscopes, which I suspect: Wireless input devices will work because they identify as HID. Bluetooth devices will not work because you can't get them to pair and the software doesn't handle Bluetooth.Thanks and I'll take the BT mouse and keyboard compatibility issue to Siglent.
Gentlemen, I've been studying this string and as I understand it, I can connect internally to my SVA1015x and make some options permanent? I would connect internally to the uart in the unit with some sort of serial port adapter to (?) to modify or change the .ads file if my unit is running the current firmware?Welcome to the forum.
I have lots of time left on the original options grant and am currently learning the unit. I bought this to avoid carrying my 60 pound VNA and 40 pound SA to a remote site. I learned too late that my purchase wasn't as smart as to purchase a SSA3000+ series but afraid I would brick it. Somewhat confused but still studying the posts...
Thanks!
I am doing some measurements with an upgraded SSA3012X Plus in VNA mode.
...
BW and sweep time are always grayed, both from the VNA stimulus page and pressing the BW/sweep buttons.
The manual refers to those commands as normally usable, only saying that the default BW is 10 kHz. |O
I have normally used BW and sweep time settings on other VNAs (hp and Copper Mountain tech) for this purpose, when measuring devices like resonators or long lines.
Don't be as it's quite acceptable here.I am doing some measurements with an upgraded SSA3012X Plus in VNA mode.
...
BW and sweep time are always grayed, both from the VNA stimulus page and pressing the BW/sweep buttons.
The manual refers to those commands as normally usable, only saying that the default BW is 10 kHz. |O
I have normally used BW and sweep time settings on other VNAs (hp and Copper Mountain tech) for this purpose, when measuring devices like resonators or long lines.
:palm: sorry quoting myself...
I am wondering if someone in Siglent acknowledged the issue, I'd like to be sure that it gets fixed soon. Having fixed BW and sweep time in VNA mode is tremendously limiting, causing wrong measurements on e.g. high-Q resonators like xtals and long lines.Yes this is an issue we have recently explored in some depth with the SSA/SVA product manager and for now SA rather than VNA mode is better for this where you have more control over BW and Sweep times.
Roberto
Is it normal to get an ADC overload warning in VNA mode with default settings and nothing connected?No.
Default after pressing the Preset button is S11 with tracking gen set to -5 dBm. And that's fresh out of the box without doing a port calibration yet.
The warning goes away when dialing down the tracking generator to -7 dBm or less.
Is it normal to get an ADC overload warning in VNA mode with default settings and nothing connected?No.
Default after pressing the Preset button is S11 with tracking gen set to -5 dBm. And that's fresh out of the box without doing a port calibration yet.
The warning goes away when dialing down the tracking generator to -7 dBm or less.
On my SVA1032X the VNA default settings are Tracking Generator -5dBm, Attenuator is grayed-out but shows +15dB so there should not be any overload.
Maybe not. Is yours an ex SSA unit of factory SVA ?Is it normal to get an ADC overload warning in VNA mode with default settings and nothing connected?No.
Default after pressing the Preset button is S11 with tracking gen set to -5 dBm. And that's fresh out of the box without doing a port calibration yet.
The warning goes away when dialing down the tracking generator to -7 dBm or less.On my SVA1032X the VNA default settings are Tracking Generator -5dBm, Attenuator is grayed-out but shows +15dB so there should not be any overload.
So it looks like my unit is broken out of the box? :'(
Maybe not. Is yours an ex SSA unit of factory SVA ?Not hacked (yet). Luckily I got the real thing as I was worried about support in case something goes wrong with the VNA side. :phew: It's already on its way back. I contacted Siglent NA and they also thought that port 1 of the unit is defective.
Hacked units can produce weird results until a VNA Cal is done.
You could try a rough bush Cal with SOL's any Port 1 Short, Port 1 Open and a 51R Load to see if that settles it down.
Post some screenshots.
Sorry, tautech, just not seeing it. Software communications not my strong suit, maybe I'm just too inexperienced. Most of what I see are the SSA hacks. Don't see the SVA hacks. Any hints?AFAIK as Linux is not a world I dabble in, SSA option enable procedures work for SVA.
Any way to override / change the defaults?System>Pwr On/Preset>Factory Reset
Besides TG level I'd like my cal plane to be the default.
TIA
Partial joy:
TG now OK at -20, S21 still -5 with ADC error.
Can set to -20 and all well till next power cycle or reset.
FWIW FW - V3.2.2.4.0r1Should be V3.2.2.4.0R2
FWIW FW - V3.2.2.4.0r1
Should be V3.2.2.4.0R2Now confused: Says 0R2 is for 15 not 32. Upgraded with latest 32 update.
https://int.siglent.com/download/firmwares/?CateIdss=16
Use Save to grab USB screenshots and post them here paying particular attention to have appropriate menus displayed so we can see your settings and replicate them if necessary.OK - any particular screens?
Thanks!OK sorry, missed what model you had. :-[FWIW FW - V3.2.2.4.0r1Should be V3.2.2.4.0R2Now confused: Says 0R2 is for 15 not 32. Upgraded with latest 32 update.
https://int.siglent.com/download/firmwares/?CateIdss=16
15 R2 update specifically mentions 15 and 75 - not 32.
Totally depends on the info you are trying to show us.Use Save to grab USB screenshots and post them here paying particular attention to have appropriate menus displayed so we can see your settings and replicate them if necessary.OK - any particular screens?
Is Siglent planning on adding basic expected VNA features to the upcoming firmware releases?
In particular, without the ability to export touchstone files or set the VNA sweep time, the SVA1032X is little more than a toy.
I don't understand how such basic features can be missing. Its almost as if the firmware developers have never used a real VNA. :palm:
AFAIK, VNA sweep time can be set in the upcoming firmware releases.
Hi
I used the SVA1032X Plus in VNA mode to determine return loss of a 2.4Ghz sector antenna. Wanting to home in on the area between 2.4 and 2.5Ghz I set the lower and upper frequencies accordingly.
A previous VNA then would have me perform SOLT calibration for this range. When trying to do this on the SVA1032X Plus it always resets the lower to 100khz and upper to 3.2Ghz with 751 points.
edited to remove typo
I don't normally use the touch screen much (don't like fingermarks!) .........You'll find a mouse is quite useful with these instruments. ;)
I have a question (possible bug I found?) about the EMI software package.
I am taking EMI measurements through a 10dB attenuator. Based on the manual I need to set the "Ref Offset" value in the Amplitude menu to match the external attenuator.
When in normal spectrum analyzer setting the "Ref Offset" value does shift the amplitude of the plot by the correct amount. If I enter 10dB the entire curve shifts up by 10dB on the scale.
However, when in the EMI mode setting the "Ref Offset" value shifts everything, including the scale and the limit mask. This means that all the readings and the limit mask for checking EMI emissions levels is incorrect if there is any external attenuator that is corrected via the "Ref Offset" value.
Am I misunderstanding something? The behavior seems to be correct for just spectrum analyzer mode. I looked through all the options specific to the EMI mode and I do not see any alternative way to set a ref offset value. The limit masks can be shifted up or down, but that still means that all the amplitude values are incorrect with an external attenuator.
The behaviour is just the same - when you press calibrate, calibrate, 1-port the frequency range always resets to 100khz to 3.2Ghz.
I have a SVA1032X, born SVA1032X, with SW 3.2.2.4.0 20201220-1 and in this unit the freq does not change
Am I correct in assuming that in such case, after the user calibration (OSLT) has been successfully performed, the status in the upper left of the screen would have to change to Cor (=calibrated)?
Now it shows --- regardless of what I do.
According to the user manual on page 76:
3.5.6 Calibration
Set calibration related items. The calibration status is displayed in the upper left corner of the screen.
The calibration status and display are as follows:
No calibration data --- (displayed in gray)
Calibrated Cor (displayed in blue)
Correction Off Off (displayed in gray)
Need to re-calibrate C? (displayed in blue)
Wow Thanks ! - I guess it was kind of obvious but yes, plugging in a mouse really makes a difference - recommended ! :-+
There are still unresolved issues around VNA calibration and saving of calibration.
One has been referred to already by Ghislain
Am I correct in assuming that in such case, after the user calibration (OSLT) has been successfully performed, the status in the upper left of the screen would have to change to Cor (=calibrated)?
Now it shows --- regardless of what I do.
According to the user manual on page 76:
3.5.6 Calibration
Set calibration related items. The calibration status is displayed in the upper left corner of the screen.
The calibration status and display are as follows:
No calibration data --- (displayed in gray)
Calibrated Cor (displayed in blue)
Correction Off Off (displayed in gray)
Need to re-calibrate C? (displayed in blue)
I experience the same - the unit seems to be calibrated (I know this becuase I am calibrating with a known dodgy load and it accounts for it perfectly). But it is disconcerting to see that the status is ---
I did find that if I do 1-port Cal followed by just an "Open" Cal the status changes to "Cor" and the 1-port cal is not lost. So there is another good work around.
It begs the question: What is the point of having a menu option just for "Open" calibration and another for "Short" Calibration when there is none for "Load" Calibration ? I mean if you want to do a calibration you either select "1-port" or "Through" which include all elements.
OK, next problem. When you Save the calibration to a file, switch the instrument off, switch on again, it has lost the calibration. Aha - but you saved it to a file ? Load the file and, yes you guessed it, you have still not got your calibration back. The only answer is to repeat the calibration.
Now this is not a huge problem because I think you probably need to calibrate at every use anyway - especially if you've had the instrument off and come back for another session. But you are supposed to be able to do this and it makes me queasy that if some of these small items don't work, what is there that also doesn't work and that might give you really dodgy results when you don't realise it?
After having read everything I can find, I am now starting to think that this might all be down to the unit being an "upgraded" SSA. Perhaps the firmware is trying to deal with a use case that it wasn't written for - like maybe there isn't a proper factory VNA calibration file and it is getting into a twist as it tries to combine a non-existent file with a user cal file.
I did have a look at the logs and thought I may have the answer but there are log entries to say successful factory vector calibration applied, so it probably isn't that after all. But perhaps something similar that I haven't thought of ?
Regards
Eloso
Also - check you are on the latest firmware?The trick is to change the Save type to a Cal file type so it gets stored internally and is accessible to load again.
I am not able to replicate the Save/Load cal issue either.
Thanks everyone.
Yes I am on latest firmware. 3.2.2.4.0.r2 is displayed on the System Screen.
And sorry but no, the answer is not to change the file type to CAL. I have already done this as a matter of course.
Interestingly, loading a saved CAL file does make a difference - ever so slight difference to the display. But it is a long way from being what it should be. I am using a very good 50 ohm load and a fairly dodgy one, in order to give me a reliable baseline and test subject.
I have heard two folk say now that this behaviour is not apparent on their instruments. I am wondering if there is an issue relating to it being an upgraded machine rather than a native born one. It would be really helpful if folk can state if their machine was purchased as an SVA1032X or was transformed into one.
I had no problem with the upgrade and Linux has been part of my career for a long time. I have checked several times and looked at several different (but more or less the same of course) descriptions of the upgrade process so am as confident as it is possible to be that the upgrade went according to plan and should be just like everyone else's. I'm experienced enough also to know that this may not be the case of course and I may have made a mistake.
Cheers
Eloso
There's no improvement over the OSL cal. I tried that as well. :(
Hi everyone,
I bought an SVA1032X as my first VNA. I have a concern about it though. After a fresh calibration using the "enhanced response" cal, looking into the instrument and measuring the S11 it doesn't seem to be very well matched. Any chance anyone else can confirm this with their unit? The VNAs I've used at work don't have this kind of response so I'm curious as to why mine looks like this.
Hi everyone,
I bought an SVA1032X as my first VNA. I have a concern about it though. After a fresh calibration using the "enhanced response" cal, looking into the instrument and measuring the S11 it doesn't seem to be very well matched. Any chance anyone else can confirm this with their unit? The VNAs I've used at work don't have this kind of response so I'm curious as to why mine looks like this.
I am not a sva1032x owner but the graph seems credible. It represents the s11 of port 2 (which is usually not very efficient in terms of vswr) seen through a transmission line less than a meter long.
It was a nice thought but perhaps we are barking up the wrong tree. Unless there are factory calibration files elsewhere. Rather than comparing file lists from an SSA with a genuine SVA can we compare filelists from a genuine SVA with my upgraded version ? I can do this if someone can provide a full treelist of files from a genuine SVA.
Anyone have pictures of the SVA1032x apart? I just noticed the VNA port on mine is slightly loose and I need to know how to disassemble it to get them tightened. Normally, I'd just tear into it, but I got as far as cutting the warranty seal and realized its a bit too expensive to tear apart before seeing if anyone has advice on the topic. Anyone do this before?The only images I’ve seen are here on the blog and it seems there’s just 2 fixings in the N type socket. :--
Anyone have pictures of the SVA1032x apart?
I don't understand how they could become loose.I believe it is my fault. When I ordered it, I immediately went on RFParts and got some nice port savers for it (that added some torque sticking out an inch and a half) and then I mistakenly ordered RG-142 instead of RG-400 for my test cables, which are stiffer than most test cables. I am sure I have applied a bit more stress on the ports than I should have. It is just the tiniest amount of play, barely noticeable. There will be some lock-tite going on those screws and the two they omitted will also go in to make it 4 fasteners total.
There maybe additional fixing with the shield fasteners but not sure. Let us know what you find.I have not tore into it yet, but I just found Dave's video which covers the disassembly a bit more than signal path did. It looks like the other two holes do get used with the shielding.
how can i find the U-disk0/ source and the firmdata0/calib directory, i can't locate it in the sub directories:
Do you wanna stay with N-N type ?
Siglents 6 GHz rated N type cables are reasonably priced:
https://siglentna.com/product/cable-male-n-to-male-n-0-7-m-length/ (https://siglentna.com/product/cable-male-n-to-male-n-0-7-m-length/)
They also do N-SMA cables for the same cost:
https://siglentna.com/product/cable-male-n-to-male-sma-0-7-m-length/ (https://siglentna.com/product/cable-male-n-to-male-sma-0-7-m-length/)
Unless you wanna go right OTT and get their new 18 GHz cables :scared:
Also, I feel like I'll have to get a calibration kit to get any meaning result. The crap I have from NanoVNA, is, well, crap ...F603ME is what I ended up getting as certainly you mostly want to work with SMA however you can cobble together workable Cal standards that will give reasonable results however you must have a known Cal to start with and only quite reasonable Cal kits with give good results over the entire frequency sweep.
I am thinking of the Siglent F603ME (most of the interfaces I deal with will be SMA based, so I'm thinking that would be the best choice.
Or am I wrong ? Should I get the N-Style ?
Is it ok to ask here if anybody knows of the cheapest source for these kits ?
rudi
F603ME is what I ended up getting as certainly you mostly want to work with SMA however you can cobble together workable Cal standards that will give reasonable results however you must have a known Cal to start with and only quite reasonable Cal kits with give good results over the entire frequency sweep.
You also need decide it you will work with N-SMA adapters so to minimize the wear on the N type inputs and if you do and so use plain SMA cables the ongoing costs and those of getting set up is reduced although if you need predicable accuracy down in the tenths of dB you have to shell out for good cabling.....but will you use it often is what I've asked myself so have a selection of lower and higher cost cabling and adapters now.
Some previous forum posts on these matters:
https://www.eevblog.com/forum/testgear/siglent-sva1015x-1-5ghz-spectrum-vector-network-analyzer-(coming)/msg3089298/#msg3089298 (https://www.eevblog.com/forum/testgear/siglent-sva1015x-1-5ghz-spectrum-vector-network-analyzer-(coming)/msg3089298/#msg3089298)
https://www.eevblog.com/forum/rf-microwave/diy-short-open-and-load-for-vna-calibration/ (https://www.eevblog.com/forum/rf-microwave/diy-short-open-and-load-for-vna-calibration/)
Hi everyone,
I bought an SVA1032X as my first VNA. I have a concern about it though. After a fresh calibration using the "enhanced response" cal, looking into the instrument and measuring the S11 it doesn't seem to be very well matched. Any chance anyone else can confirm this with their unit? The VNAs I've used at work don't have this kind of response so I'm curious as to why mine looks like this.
First picture (Attachment Link) is what I'm concerned about, second picture (Attachment Link) is the test setup.
Thanks!
LOL Rudi, be careful of the rabbit hole you are now peering into ! ;D
(https://www.eevblog.com/forum/testgear/test-equipment-anonymous-(tea)-group-therapy-thread/?action=dlattach;attach=641927;image)
As some example:
https://siglentna.com/product/nm-smam-cable100cm18-ghz/ (https://siglentna.com/product/nm-smam-cable100cm18-ghz/)
These are very nice cables and they'd want to be for the price however they are made by Rosenberger for Siglent.
I am seriously interested in purchasing a SVA1032X.Only that it's just a single port VNA therefore measurements are limited to S11 and S21 types as all stimulus comes from Port 1 (TG) yet for antenna (S11) and one directional tests of filters etc (S21)) it's still very useful.
Is there any owner, based on his experience with the instrument, able to briefly present the pros and cons of the spectrum analyzer and the VNA section respectively?
It may be that this is not the most suitable thread but... is there anyone who can tell me if for the SVA1032X it is possible to set the SW options in lifetime mode?
The SVA1032X has a considerable cost and before proceeding with its purchase I need to be sure if the various SW options (the cost of which is prohibitive for my possibilities...) can be permanently enabled.
Thanks in advance to those who want to help me.
It may be that this is not the most suitable thread but... is there anyone who can tell me if for the SVA1032X it is possible to set the SW options in lifetime mode?It is possible to start the journey to the full SVA1032X from the cheaper SSA3021X-plus
The SVA1032X has a considerable cost and before proceeding with its purchase I need to be sure if the various SW options (the cost of which is prohibitive for my possibilities...) can be permanently enabled.
Thanks in advance to those who want to help me.
It may be that this is not the most suitable thread but... is there anyone who can tell me if for the SVA1032X it is possible to set the SW options in lifetime mode?It is possible to start the journey to the full SVA1032X from the cheaper SSA3021X-plus
The SVA1032X has a considerable cost and before proceeding with its purchase I need to be sure if the various SW options (the cost of which is prohibitive for my possibilities...) can be permanently enabled.
Thanks in advance to those who want to help me.
Full information on how to cross-flash the SSA3021X-plus to SVA1032X somewhere on this thread: https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/ (https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/)It may be that this is not the most suitable thread but... is there anyone who can tell me if for the SVA1032X it is possible to set the SW options in lifetime mode?It is possible to start the journey to the full SVA1032X from the cheaper SSA3021X-plus
The SVA1032X has a considerable cost and before proceeding with its purchase I need to be sure if the various SW options (the cost of which is prohibitive for my possibilities...) can be permanently enabled.
Thanks in advance to those who want to help me.
Thanks a lot for the suggestion!!! Before purchasing I'll investigate a bit regardig this much less expensive option.
Anyway, regarding this possibility that I'll now explore in detail thanks to your suggestion, I have the doubt that the frequency expansion operated in the transition between 2.1 GHz and 3.2 GHz results in an uncalibrated spectrum analyzer in the 2.1 - 3.2 GHz range and this would be a not negligible inconvenience for this type of measuring instruments! (calibration of a Spectrum Analyzer is usually a very expensive service...)
I am seriously interested in purchasing a SVA1032X.Only that it's just a single port VNA therefore measurements are limited to S11 and S21 types as all stimulus comes from Port 1 (TG) yet for antenna (S11) and one directional tests of filters etc (S21)) it's still very useful.
Is there any owner, based on his experience with the instrument, able to briefly present the pros and cons of the spectrum analyzer and the VNA section respectively?
For DUT's that need testing/measuring in both directions they must be flipped to poke them from either end.
I have a SVA1032X which used to be an SSA3021X Plus and I'm seeing some strange issues with the VNA calibration. It seems that when I do a calibration, using either the Open, Short, or Enhanced Response calibration modes, things work OK and I get a "Cor" message to indicate things are calibrated. The issue comes up when I use either the 1-Port or Response Through calibration modes. Whenever I enter them, the start and stop frequencies always get reset to 100kHz-3.2Ghz. I can change them when in cal mode by clicking on them under the graph, but either way, when the cal completes, I never get the "Cor" message at the top indicating things are calibrated. Nor do I get a "*" next to the calibration option in the calibrate menu. Instead it always shows "---" at the top. Things seem like they might be calibrated, so I'm not sure if this is just a bug. Can someone with a real SVA1032X check if this happens there also?See here for clues to managing various Cals:
The 2nd thing, I'm wondering about is the the cal kit selection. I have the F603FE kit from Siglent and select that from the menu when doing cals, but I noticed that there isn't a CSV file for it in the vnacalkitdata directory even though it's showing up in the menu. Does anyone know if that is an issue or how the CSV is used?
/usr/bin/siglent/usr/vnacalikitdata
Are you saying that saving and loading a CAL file will produce a CSV file? The files in the vnacalkitdata directory seem to be installed from the factory for only certain mechanical cal kits.
I'm referring to the CSV files not the CAL files. The CSV files are located in the directory structure atCal kit files will be individual characterizations of each model of the listed Cal kits.Code: [Select]/usr/bin/siglent/usr/vnacalikitdata
Are you saying that saving and loading a CAL file will produce a CSV file? The files in the vnacalkitdata directory seem to be installed from the factory for only certain mechanical cal kits.
I have a SVA1032X which used to be an SSA3021X Plus and I'm seeing some strange issues with the VNA calibration. It seems that when I do a calibration, using either the Open, Short, or Enhanced Response calibration modes, things work OK and I get a "Cor" message to indicate things are calibrated. The issue comes up when I use either the 1-Port or Response Through calibration modes. Whenever I enter them, the start and stop frequencies always get reset to 100kHz-3.2Ghz. I can change them when in cal mode by clicking on them under the graph, but either way, when the cal completes, I never get the "Cor" message at the top indicating things are calibrated. Nor do I get a "*" next to the calibration option in the calibrate menu. Instead it always shows "---" at the top. Things seem like they might be calibrated, so I'm not sure if this is just a bug. Can someone with a real SVA1032X check if this happens there also?I have one. I always use the 1-port cal and I just tried the Response Through cal. The frequency settings follow into both calibration screens and it also shows CAL at the top after leaving the cal screens.
The strange thing is that the cal kit CSV files in that folder are only for a subset of the calkit options you can pick from the menus. Makes me wonder if I pick the F603FE and the CSV file does not exist, then what is actually happening?A wee look at this beta FW and Cals.
I don't suppose you can tell us if the new beta has fixes for the weird cal issues I mentioned above when selecting 1-port or through calibration, etc.? :-+ :popcorn:
A wee look at this beta FW and Cals.
Some screenshots below with what might be the new max points. :)
Going through the Cal process for which I used 1 Port Cal as this is mostly what I use and for this a F603FE at the end of a cheap 150mm SMA cable on a N-SMA adapter on Port 1.
Captures for Short and Open were done in the Sort and Open cal and went through them again in the 1 Port Cal where Load is also used but at each step each Cal is Applied however you only see the full result after Load is done.
Marker @ 3.2 GHz added FYI.
Full BW sweeps were quite fast previously however with 10k points they're ~4.5s now.
10pm here now but wet day coming tomorrow so will roll back FW then and offer some examples of the same sort of Cal with this SVA1032. Might do some examples of how to Save a Cal for recall also.....A wee look at this beta FW and Cals.
Some screenshots below with what might be the new max points. :)
Going through the Cal process for which I used 1 Port Cal as this is mostly what I use and for this a F603FE at the end of a cheap 150mm SMA cable on a N-SMA adapter on Port 1.
Captures for Short and Open were done in the Sort and Open cal and went through them again in the 1 Port Cal where Load is also used but at each step each Cal is Applied however you only see the full result after Load is done.
Marker @ 3.2 GHz added FYI.
Full BW sweeps were quite fast previously however with 10k points they're ~4.5s now.
I can't wait for the official release !!!
rudi
I have a SVA1032X which used to be an SSA3021X Plus and I'm seeing some strange issues with the VNA calibration. It seems that when I do a calibration, using either the Open, Short, or Enhanced Response calibration modes, things work OK and I get a "Cor" message to indicate things are calibrated. The issue comes up when I use either the 1-Port or Response Through calibration modes. Whenever I enter them, the start and stop frequencies always get reset to 100kHz-3.2Ghz. I can change them when in cal mode by clicking on them under the graph, but either way, when the cal completes, I never get the "Cor" message at the top indicating things are calibrated. Nor do I get a "*" next to the calibration option in the calibrate menu. Instead it always shows "---" at the top. Things seem like they might be calibrated, so I'm not sure if this is just a bug. Can someone with a real SVA1032X check if this happens there also?I have one. I always use the 1-port cal and I just tried the Response Through cal. The frequency settings follow into both calibration screens and it also shows CAL at the top after leaving the cal screens.
I have a SVA1032X which used to be an SSA3021X Plus and I'm seeing some strange issues with the VNA calibration. It seems that when I do a calibration, using either the Open, Short, or Enhanced Response calibration modes, things work OK and I get a "Cor" message to indicate things are calibrated. The issue comes up when I use either the 1-Port or Response Through calibration modes. Whenever I enter them, the start and stop frequencies always get reset to 100kHz-3.2Ghz. I can change them when in cal mode by clicking on them under the graph, but either way, when the cal completes, I never get the "Cor" message at the top indicating things are calibrated. Nor do I get a "*" next to the calibration option in the calibrate menu. Instead it always shows "---" at the top. Things seem like they might be calibrated, so I'm not sure if this is just a bug. Can someone with a real SVA1032X check if this happens there also?
Might do some examples of how to Save a Cal for recall also.....Sorry guys found some bugs in Enhanced Response calibration with the beta FW. :(
I have a SVA1032X which used to be an SSA3021X Plus and I'm seeing some strange issues with the VNA calibration. It seems that when I do a calibration, using either the Open, Short, or Enhanced Response calibration modes, things work OK and I get a "Cor" message to indicate things are calibrated. The issue comes up when I use either the 1-Port or Response Through calibration modes. Whenever I enter them, the start and stop frequencies always get reset to 100kHz-3.2Ghz. I can change them when in cal mode by clicking on them under the graph, but either way, when the cal completes, I never get the "Cor" message at the top indicating things are calibrated. Nor do I get a "*" next to the calibration option in the calibrate menu. Instead it always shows "---" at the top. Things seem like they might be calibrated, so I'm not sure if this is just a bug. Can someone with a real SVA1032X check if this happens there also?
My converted SSA3021X Plus works ok with the calibration steps you have highlighted for both "1-Port" and "Response Through". The "Cor" indication appears when calibration is applied, and the frequency remains at whatever I had previously selected.
Steve, I suspect you are missing a small but very important step. ;)
Work through 1 Port Cal as you have then re-enter the Calibration menu and select Correction = ON.
Screenshots below just taken show first what a Load looks like with Correction not applied and then applied.
No and why would one undertake a calibration process with correction ON ? Dunno if it makes a difference or not. it just seems logical to disable corrections. Anyways I'm working with a V5 beta and just got an update that's apparently soon to be released so I need get all my checks done with it today.Steve, I suspect you are missing a small but very important step. ;)
Work through 1 Port Cal as you have then re-enter the Calibration menu and select Correction = ON.
Screenshots below just taken show first what a Load looks like with Correction not applied and then applied.
This is interesting... By default my Correction is on, so I never touched it. I will have to try switching it OFF before doing the cal and then switching it back ON after to see if that makes a difference. I'll try this out tonight.
Is your Correction defaulting to OFF?
Can you post a picture of your screen? It looks you are missing a cable because I had the same problem but then my Smith diagram screen was al over the placeEven a genuine SVA1032X can display garbage if you have the wrong Cal applied and some are quite delightful patterns too !
No and why would one undertake a calibration process with correction ON ? Dunno if it makes a difference or not. it just seems logical to disable corrections. Anyways I'm working with a V5 beta and just got an update that's apparently soon to be released so I need get all my checks done with it today.Steve, I suspect you are missing a small but very important step. ;)
Work through 1 Port Cal as you have then re-enter the Calibration menu and select Correction = ON.
Screenshots below just taken show first what a Load looks like with Correction not applied and then applied.
This is interesting... By default my Correction is on, so I never touched it. I will have to try switching it OFF before doing the cal and then switching it back ON after to see if that makes a difference. I'll try this out tonight.
Is your Correction defaulting to OFF?
Can you post a picture of your screen? It looks you are missing a cable because I had the same problem but then my Smith diagram screen was al over the place
Hi Eloso.Been balls out today and there's still a few hrs to go ! :scared:
Thanks for your comments! I'm wondering if someone can figure out the mystery of what's missing from the converted one since the hardware should be the same. Maybe the upcoming firmware will magically fix things ;D
Hi Eloso.Been balls out today and there's still a few hrs to go ! :scared:
Thanks for your comments! I'm wondering if someone can figure out the mystery of what's missing from the converted one since the hardware should be the same. Maybe the upcoming firmware will magically fix things ;D
Installed new FW but work/business has got in the way of doing any more.
Hopefully I'll get back to it this evening ...........
Smith charts look mint :-+Hi Eloso.Been balls out today and there's still a few hrs to go ! :scared:
Thanks for your comments! I'm wondering if someone can figure out the mystery of what's missing from the converted one since the hardware should be the same. Maybe the upcoming firmware will magically fix things ;D
Installed new FW but work/business has got in the way of doing any more.
Hopefully I'll get back to it this evening ...........
I understand, and thanks again for helping out with this! :)
(Note: I've also added some pictures in the post above... Image upload wasn't working for me earlier for some reason.)
I've attached some pictures showing the results after a 1-port cal in both log mag and smith charts. Do these show any noticeable issues?
I've attached some pictures showing the results after a 1-port cal in both log mag and smith charts. Do these show any noticeable issues?
I wonder if you are masking the same mistake I was after cross flashing.
Port 1 if the TG port on the SSA, and Port 2 is the RF Port.
When doing calibration, you need to use Port 1 (TG Source).
I'll do some test on my SSA3032X+ converted to SVA1032 later on today
and will post some pics too.
rudi
.... The other is that until someone steps forward with a cross flashed SVA1032X to say that theirs works ok, it is clear that the behaviour of Cross Flashed SVAs is different to that of natural born ones (easy test - do a 1-port CAL, if the "Cor" label comes up at the end then it is behaving itself, if only -- or OFF comes up at the end of the CAL routine then it is behaving like the badly behaved cross flashed unit that Steve and I have been describing.).
Test | Expected Result | Actual Result in Factory Mode | Actual Result after reapplying original S/N |
Carry out 1 Port Calibration 1Mhz – 500Mhz | Should operate over SPAN requested. On completion it should show “Cor”. On completion a Smith chart with a 50ohm load on Port 1 should result in a small spot in the middle of the chart | As soon as Calibration routine is entered, frequency SPAN annoyingly changes to 100kHz – 3.2Ghz. Can be changed back only with mouse pointer on screen. On completion there is no “Cor”, just “—“. But note that results on the Smith chart appear to show a calibrated status | No problem – does exactly as requested |
Power cycle machine after One Port Cal | Machine should come up into VNA mode with appropriate settings and with “Cor” highlighted to show status is calibrated | Problem. Switches on into SA mode. Putting into VNA mode there is only “—“ where there should be “Cor” | No problem – does exactly as requested |
Change Frequency Span after Calibration | Calibration status should change from "Cor" to “C?” | Problem because calibration status is never shown as “Cor” in the first place. | No problem – does exactly as requested |
Save Calibration File | Should create file. | Creates a file. | Creates a file. |
Load Calibration file after having made changes to frequency span. | Should show C? until frequency span is adjusted to be the same as when the calibration file was created | Problem. Calibration status shows “—“ all the time. i.e. loading a calibration file never appears to work as far as the "Cor" indicator is concerned | No problem – does exactly as requested |
For reference, here are some tests made by an anonymous member:
Some more tests have been carried out which show that in Factory Mode the VNA exhibits quirks surrounding one port calibration function. There are work arounds and the author has continued to use the VNA for hobby S11 measurement. The key is in being methodical and checking the calibration status frequently by means of looking at a range of loads on the Smith Chart.
But having reapplied the serial number the VNA appears to work impeccably.
...
Sum up:
1) Factory mode: implies not having a serial number, by editing/removing/deleting the respective XML file
2) With factory mode, all options are active
3) It has been found out that factory mode has bad/weird behaviour regarding VNA calibration/measurements
4) Enabling/restoring the serial number will deactivate factory mode and options need to have valid license again ("key") - cross graders will have no option at all
5) Owners of an SSA3021X+ can do the cross-grade to a SVA1032 but have to live with the mentioned issues in VNA mode if they use the factory mode to get all options activated
6) There is no public keygen
I believe there is a way:What post explains how to copy those files? I've never had mine connected to the computer or done any telnet stuff.
1. We need someone with a genuine SVA1032X, to share the following files:
/usr/bin/siglent/firmdata0/NSP_system_info.xml
/usr/bin/siglent/firmdata0/NSP_sn_bandwidth.xml
/usr/bin/siglent/firmdata0/nsp_data_b1
2. Once we have those files, we should be able to change the S/N and (if needed) regenerate the licenses ...
Anybody wants to try ?
We can do it in private ...
Thanks,
rudi
I believe there is a way:What post explains how to copy those files? I've never had mine connected to the computer or done any telnet stuff.
1. We need someone with a genuine SVA1032X, to share the following files:
/usr/bin/siglent/firmdata0/NSP_system_info.xml
/usr/bin/siglent/firmdata0/NSP_sn_bandwidth.xml
/usr/bin/siglent/firmdata0/nsp_data_b1
2. Once we have those files, we should be able to change the S/N and (if needed) regenerate the licenses ...
Anybody wants to try ?
We can do it in private ...
Thanks,
rudi
I'll receive a genuine SVA1032X shortly.
I know that the various SW options can be permanently enabled. Where can I find a trace of the procedure for doing this?
Given what has been reported in previous posts, does this in any way compromise the functionality of the analyzer?
Thanks everyone!
The public keygen doesn't work for SSA or SVA.
So I think the public keygen DOES work.
So, at present, it seems to me that there is no way to permanently enable the software options. Correct?Not correct, read for example here: https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg3180754/#msg3180754 (https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg3180754/#msg3180754)
If you want to take it further from here, to have the correct Serial number, you'll also need a way to generate the correct license info for your specific device's Serial + Host ID.
This can be done with some help from the forum, but the procedure is not public yet. ;)
Hi guys,New FW for SVA/SSA-X-R is under construction and we're still sorting a few issues with it.
my unit shows exactly 100% same issue on 1-PORT calibration procedure as described by steve1515 and eloso.
If you have a look at the review of SVA1032X by The Signal Path (https://youtu.be/ToVJTKCyIU8) you can see at 33:30 of the video that his unit shows the same issue of missing calibration status "---" on left top of his screen.
So, it seems to be definitely a buggy issue of the FW in the pro-mode.
TauTech:
Is there any chance that Siglent could fix that in an update?
Why have your Smith plots for OPEN and SHORT a long "line" response and not a "spot" response as should be? You get clean spot result instead when using the calibration menu SHORT or OPEN. |O
Thanks!
TauTech:
Is there any chance that Siglent could fix that in an update?
Why have your Smith plots for OPEN and SHORT a long "line" response and not a "spot" response as should be? You get clean spot result instead when using the calibration menu SHORT or OPEN. |O
Thanks!
So, it seems to be definitely a buggy issue of the FW in pro-mode.
Great! Would be perfect if this issue will be solved with next FW update.
My question refers to screenhots in #688 of tautech.
I know that "arcs" occure due to capacitance and inductance effects of physical connections.
However, when doing same calibration in simple "OPEN" and "SHORT" mode instead of "1-PORT" mode I get perfect nice spots.
So, it seems to be definitely a buggy issue of the FW in pro-mode.
I wouldn't call it a "bug"... You're outside the envelope.
Hi guys,New FW for SVA/SSA-X-R is under construction and we're still sorting a few issues with it.
my unit shows exactly 100% same issue on 1-PORT calibration procedure as described by steve1515 and eloso.
If you have a look at the review of SVA1032X by The Signal Path (https://youtu.be/ToVJTKCyIU8) you can see at 33:30 of the video that his unit shows the same issue of missing calibration status "---" on left top of his screen.
So, it seems to be definitely a buggy issue of the FW in the pro-mode.
TauTech:
Is there any chance that Siglent could fix that in an update?
Why have your Smith plots for OPEN and SHORT a long "line" response and not a "spot" response as should be? You get clean spot result instead when using the calibration menu SHORT or OPEN. |O
Thanks!
Did the product ID change in this update? If not, couldn't you just use the same telnet ADS file and update the startup script to re-enable telnet again?I was thinking the same... but I'm not sure.
;D ;D upgrade 3.2.2.4->3.2.2.5 done, all hacks still working!!!
Now VNA number of points is up to 10001, that's wonderful! Unfortunately SA number of points is still not changeable and fixed to 751.
telnet is reenabled successfully with script SVA1000X_telnet_11410, followed by the usual editing to activate it on boot.
:SYSTem:TIME
:SYSTem:TIME?
:SYSTem:DATE
:SYSTem:DATE?
:SYSTem:PRESet
:SYSTem:FDEFault
REBOOT
:SYSTem:PRESet:TYPE
:SYSTem:PRESet:TYPE?
:SYSTem:PON:TYPE
:SYSTem:PON:TYPE?
:SYSTem:COMMunicate:LAN:TYPE
:SYSTem:COMMunicate:LAN:TYPE?
:SYSTem:COMMunicate:LAN:IPADdress
:SYSTem:COMMunicate:LAN:IPADdress?
:SYSTem:COMMunicate:LAN:SMASk
:SYSTem:COMMunicate:LAN:SMASk?
:SYSTem:COMMunicate:LAN:GATeway
:SYSTem:COMMunicate:LAN:GATeway?
:SYSTem:COMMunicate:LAN:MAC
:SYSTem:COMMunicate:LAN:MAC?
:SYSTem:COMMunicate:LAN:HOSTname
:SYSTem:COMMunicate:LAN:HOSTname?
NET_BRIDGE_ADDR?
SRLN
SRLN?
SGLT-UPGRADE
SGLT-UPGRADE_CFG
SGLT-UPGRADE_PATH
SGLT-UPGRADE_CFG_PATH
SGLT-TEST-VAST-DATA
SGLT-TEST-VAST-DATA?
SCDP
IDN-SGLT-PRI?
LOAD:CALI:FILE?
CHIP
CHIP?
DMESg?
SVNALL?
$$SY_FP
MMEMory:UPLoad?
LICENSE
LICENSE?
LICENSE_KEY
LICENSE_PR?
LICENSE_ID?
INNEr:PRODuction:MODE
SYSTem:FileSystem:Type?
BOARDTEST?
WEB:PSW
WEB:PSW?
FACTORYDATA
FACTORYDATA?
:DISPlay:WINDow#:TRACe#:Y[:SCALe]:RLEVel
:DISPlay:WINDow#:TRACe#:Y[:SCALe]:RLEVel?
:DISPlay:FSCan:VIEW#:WINDow#:TRACe:Y[:SCALe]:RLEVel
:DISPlay:FSCan:VIEW#:WINDow#:TRACe:Y[:SCALe]:RLEVel?
:DISPlay:WINDow#:TRACe#:Y[:SCALe]:PDIVision
:DISPlay:WINDow#:TRACe#:Y[:SCALe]:PDIVision?
:DISPlay:FSCan:VIEW#:WINDow#:TRACe:Y[:SCALe]:PDIVision
:DISPlay:FSCan:VIEW#:WINDow#:TRACe:Y[:SCALe]:PDIVision?
:DISPlay:WINDow#:TRACe#:Y[:SCALe]:RPOSition
:DISPlay:WINDow#:TRACe#:Y[:SCALe]:RPOSition?
[:SENSe]:POWer[:RF]:ATTenuation
[:SENSe]:POWer[:RF]:ATTenuation?
[:SENSe]:POWer[:RF]:ATTenuation:AUTO
[:SENSe]:POWer[:RF]:ATTenuation:AUTO?
:DISPlay:WINDow:TRACe:Y[:SCALe]:RLEVel:OFFSet
:DISPlay:WINDow:TRACe:Y[:SCALe]:RLEVel:OFFSet?
:DISPlay:FSCan:VIEW:WINDow:TRACe:Y[:SCALe]:RLEVel:OFFSet
:DISPlay:FSCan:VIEW:WINDow:TRACe:Y[:SCALe]:RLEVel:OFFSet?
[:SENSe]:POWer[:RF]:GAIN[:STATe]
[:SENSe]:POWer[:RF]:GAIN[:STATe]?
:DISPlay:WINDow:TRACe:Y[:SCALe]:SPACing
:DISPlay:WINDow:TRACe:Y[:SCALe]:SPACing?
:UNIT:POWer
:UNIT:POWer?
[:SENSe]:CORRection:IMPedance[:INPut][:MAGNitude]
[:SENSe]:CORRection:IMPedance[:INPut][:MAGNitude]?
[:SENSe]:CORRection:OFF
[:SENSe]:CORRection:CSET#:OFF
[:SENSe]:CORRection:CSET:ALL[:STATe]
[:SENSe]:CORRection:CSET:ALL[:STATe]?
[:SENSe]:CORRection:CSET#[:STATe]
[:SENSe]:CORRection:CSET#[:STATe]?
[:SENSe]:CORRection:CSET#:DATA
[:SENSe]:CORRection:CSET#:DATA?
[:SENSe]:CORRection:CSET#:ADD
[:SENSe]:CORRection:CSET#:DELete
[:SENSe]:CORRection:CSET#:ALL:DELete
:DISPlay:WINDow#:TRACe#:Y[:SCALe]:AUTO
:TRACe#:Y[:SCALe]:RLEVel
:TRACe#:Y[:SCALe]:RLEVel?
:TRACe#:Y[:SCALe]:PDIVision
:TRACe#:Y[:SCALe]:PDIVision?
:TRACe#[:Y]:AUToscale
[:SENSe#]:BWIDth[:RESolution]
[:SENSe#]:BWIDth[:RESolution]?
[:SENSe]:BWIDth:VIDeo
[:SENSe]:BWIDth:VIDeo?
[:SENSe]:BWIDth[:RESolution]:AUTO
[:SENSe]:BWIDth[:RESolution]:AUTO?
[:SENSe]:BWIDth:VIDeo:AUTO
[:SENSe]:BWIDth:VIDeo:AUTO?
[:SENSe]:BWIDth:VIDeo:RATio
[:SENSe]:BWIDth:VIDeo:RATio?
[:SENSe]:BWIDth:VIDeo:RATio:CONfig?
[:SENSe#]:BANDwidth[:RESolution]
[:SENSe#]:BANDwidth[:RESolution]?
[:SENSe]:BANDwidth:VIDeo
[:SENSe]:BANDwidth:VIDeo?
[:SENSe]:BANDwidth[:RESolution]:AUTO
[:SENSe]:BANDwidth[:RESolution]:AUTO?
[:SENSe]:BANDwidth:VIDeo:AUTO
[:SENSe]:BANDwidth:VIDeo:AUTO?
[:SENSe]:BANDwidth:VIDeo:RATio
[:SENSe]:BANDwidth:VIDeo:RATio?
[:SENSe]:BANDwidth:VIDeo:RATio:CONfig?
[:SENSe]:AVERage:TYPE
[:SENSe]:AVERage:TYPE?
[:SENSe]:FILTer:TYPE
[:SENSe]:FILTer:TYPE?
[:SENSe]:BWIDth:SHAPe
[:SENSe]:BWIDth:SHAPe?
[:SENSe]:DDEMod:FFT:WINDow:TYPE
[:SENSe]:DDEMod:FFT:WINDow:TYPE?
[:SENSe]:FSCan:SCAN:BWIDth[:RESolution]
[:SENSe]:FSCan:SCAN:BWIDth[:RESolution]?
[:SENSe]:FSCan:SCAN:BWIDth[:RESolution]:AUTO
[:SENSe]:FSCan:SCAN:BWIDth[:RESolution]:AUTO?
[:SENSe]:DEMod
[:SENSe]:DEMod?
[:SENSe]:DEMod:TIME
[:SENSe]:DEMod:TIME?
[:SENSe]:DEMod:VOLume
[:SENSe]:DEMod:VOLume?
[:SENSe]:DEMod:EPHone
[:SENSe]:DEMod:EPHone?
[:SENSe#]:FREQuency:STARt
[:SENSe#]:FREQuency:STARt?
[:SENSe#]:FREQuency:CENTer
[:SENSe#]:FREQuency:CENTer?
[:SENSe#]:FREQuency:STOP
[:SENSe#]:FREQuency:STOP?
[:SENSe#]:FREQuency:SPAN
[:SENSe#]:FREQuency:SPAN?
[:SENSe]:FREQuency:CENTer:STEP[:INCRement]
[:SENSe]:FREQuency:CENTer:STEP[:INCRement]?
[:SENSe]:FREQuency:CENTer:STEP:AUTO
[:SENSe]:FREQuency:CENTer:STEP:AUTO?
:CALCulate:MARKer:TRCKing[:STATe]
:CALCulate:MARKer:TRCKing[:STATe]?
[:SENSe]:FREQuency:SPAN:FULL
[:SENSe]:FREQuency:SPAN:ZERO
[:SENSe]:FREQuency:SPAN:HALF
[:SENSe]:FREQuency:SPAN:DOUBle
[:SENSe]:FREQuency:SPAN:PREVious
[:SENSe]:FREQuency:CENTer:SET:STEP
[:SENSe]:FREQuency:OFFSet
[:SENSe]:FREQuency:OFFSet?
:DISPlay:WINDow:TRACe:X[:SCALe]:SPACing
:DISPlay:WINDow:TRACe:X[:SCALe]:SPACing?
[:SENSe]:FREQuency:TUNE:IMMediate
[:SENSe#]:FREQuency:DATA?
[:SENSe]:FSCan:RANGe
[:SENSe]:FREQuency:MIDSpan
[:SENSe]:FREQuency:MIDSpan?
:INNer:SET:MODE:REMOte
:INNer:VERS:MATCh:ID?
:INNer:ALL:DP:DATA?
:INNer:ALL:EMI:DATA?
:INNer:AMPT:PARM?
:INNer:AMPT:CORR:PARM?
:INNer:FREQuency:PARM?
:INNer:BW:PARM?
:INNer:ALL:TRACE:PARM?
:INNer:PEAK:PARM?
:INNer:SWEEP:PARM?
:INNer:TRIG:PARM?
:INNer:LIMit:PARM?
:INNer:TG:PARM?
:INNer:MEAS:PARM?
:INNer:MODE:PARM?
:INNer:MARKer#:PARM?
:INNer:LOAD:FILE
:INNer:EXPort?
DEBug:HWACcess:FPGA
DEBug:HWACcess:FPGA?
DEBug:HWACcess:CPLD
DEBug:HWACcess:CPLD?
DEBug:HWACcess:PLL1
DEBug:HWACcess:PLL1?
DEBug:HWACcess:PLL2
DEBug:HWACcess:PLL2?
DEBug:HWACcess:FILTer:RF
DEBug:HWACcess:TG
DEBug:HWACcess:TG?
DEBug:HWACcess:ATT:TG
DEBug:HWACcess:ATT:TG?
DEBug:HWACcess:TEST:SWITch
DEBug:HWACcess:PLL3
DEBug:HWACcess:PLL3?
DEBug:HWACcess:RTFPga
DEBug:HWACcess:RTFPga?
DEBug:HWACcess:REFPLL
DEBug:HWACcess:REFPLL?
DEBug:HWACcess:ADC
DEBug:HWACcess:ADC?
DEBug:HWACcess:VGA
DEBug:HWACcess:VGA?
DEBug:HWACcess:LOAD:RTFPGA
DEBug:HWACcess:INIT:PLL
DEBug:HWACcess:DAC
DEBug:HWACcess:DAC?
DEBug:HWACcess:IFDAc
DEBug:HWACcess:IFDAc?
DEV:INNersorce
DEBug:TEMPrt:BOARd?
DEBug:TEMPrt:ZCPU?
DEBug:ERASe:CALibration:DATA
DEBug:FACTory:MODE
DEBug:IF:FILTer
:TEMPreature:COMP:VALue?
:DEBug:INNersorce:DEFault:VALue?
:BOARdtest:FPGA:VERSion?
:BOARdtest:RTSA:FPGA:VERSion?
:BOARdtest:CPLD:VERSion?
:BOARdtest:PCBid:VERSion?
:BOARdtest:FPGA:RW?
:BOARdtest:DDR3:TEST?
:BOARdtest:FLASh:TEST?
:BOARdtest:LAN:TEST?
:BOARdtest:USBHost:TEST?
:BOARdtest:PLL40lock:TEST?
:BOARdtest:EXTTrig:TEST?
:BOARdtest:EXTRefsource:TEST?
DEBug:FLASh:DATA
DEBug:FLASh:DATA?
DEBug:ERASe:FLASh:SECTor
DEBug:ERASe:FLASh:BULK
DEBug:S11:CALFile:SYNC:TO:FLASh
:CALCulate:LLINe#:STATe
:CALCulate:LLINe#:STATe?
:CALCulate:FSCan:LLINe#:DISPlay
:CALCulate:FSCan:LLINe#:DISPlay?
:CALCulate:FSCan:LLINe#:MARGin
:CALCulate:FSCan:LLINe#:MARGin?
:CALCulate:FSCan:LLINe#:MARGin:STATe
:CALCulate:FSCan:LLINe#:MARGin:STATe?
:CALCulate:FSCan:LLINe#:TRACe
:CALCulate:FSCan:LLINe#:TRACe?
:CALCulate:LLINe#:TYPE
:CALCulate:LLINe#:TYPE?
:CALCulate:LLINe#:MODE
:CALCulate:LLINe#:MODE?
:CALCulate:FSCan:LLINe#:MODE
:CALCulate:FSCan:LLINe#:MODE?
:CALCulate:LLINe#:Y
:CALCulate:LLINe#:Y?
:CALCulate:FSCan:LLINe#:Y
:CALCulate:FSCan:LLINe#:Y?
:CALCulate:LLINe#:DATA
:CALCulate:LLINe#:DATA?
:CALCulate:FSCan:LLINe#:DATA
:CALCulate:FSCan:LLINe#:DATA?
:CALCulate:LLINe#:OFFSet:X
:CALCulate:LLINe#:OFFSet:X?
:CALCulate:LLINe#:OFFSet:Y
:CALCulate:LLINe#:OFFSet:Y?
:CALCulate:LLINe#:ADD
:CALCulate:LLINe#:DELete
:CALCulate:LLINe#:ALL:DELete
:CALCulate:LLINe:TEST:STARt
:CALCulate:LLINe:TEST:STOP
:CALCulate:LLINe:TEST:STATe?
CALCulate:LLINe:TEST
:CALCulate:LLINe:TEST?
:CALCulate:LLINe:FAIL?
:CALCulate:FSCan:LLINe:FAIL?
:CALCulate:LLINe:CONTrol:DOMain
:CALCulate:LLINe:CONTrol:DOMain?
:CALCulate:LLINe:CONTrol:BEEP
:CALCulate:LLINe:CONTrol:BEEP?
:CALCulate:LLINe:FAIL:STOP
:CALCulate:LLINe:FAIL:STOP?
:CALCulate:LLINe#:CONTrol:INTerpolate
:CALCulate:LLINe#:CONTrol:INTerpolate?
:CALCulate:FSCan:LLINe#:CONTrol:INTerpolate
:CALCulate:FSCan:LLINe#:CONTrol:INTerpolate?
[:SENSe]:DDEMod:RAWiq:COLLect
[:SENSe]:DDEMod:RAWiqdata?
[:SENSe]:MA:SAMPle:MAX?
[:SENSe]:MA:RAWiq:COLLect
[:SENSe]:MA:RAWiqdata?
[:SENSe]:MA:PARSe:RATE?
[:SENSe]:MA:PARSe:SIZE?
[:SENSe]:MA:BUFFer:SIZE?
:CALCulate:MARKer:TABLe[:STATe]
:CALCulate:MARKer:TABLe[:STATe]?
:CALCulate[:SELected]:MARKer:AOFF
:CALCulate#:MARKer#:STATe
:CALCulate#:MARKer#:STATe?
:CALCulate:IFBW:INDEx?
:CALCulate:EQLPf:INDEx?
:CALCulate:MARKer#:MODE
:CALCulate:MARKer#:MODE?
:CALCulate:FSCan:MARKer#:MODE
:CALCulate:FSCan:MARKer#:MODE?
:CALCulate:MARKer#:TRACe
:CALCulate:MARKer#:TRACe?
:CALCulate:FSCan:MARKer#:TRACe
:CALCulate:FSCan:MARKer#:TRACe?
:CALCulate:MARKer#:REFerence
:CALCulate:MARKer#:REFerence?
:CALCulate:FSCan:MARKer#:REFerence
:CALCulate:FSCan:MARKer#:REFerence?
:CALCulate:MARKer#:RELative:TO:MARKer
:CALCulate:MARKer#:RELative:TO:MARKer?
:CALCulate:MARKer#:X:READout
:CALCulate:MARKer#:X:READout?
:CALCulate:MARKer#:FUNCtion
:CALCulate:MARKer#:FUNCtion?
:CALCulate:MARKer#:BANDwidth:NDB
:CALCulate:MARKer#:BANDwidth:NDB?
:CALCulate:MARKer#:BWIDth:NDB
:CALCulate:MARKer#:BWIDth:NDB?
:CALCulate:MARKer#:BANDwidth:RESult?
:CALCulate:MARKer#:BANDwidth:RLEFt?
:CALCulate:MARKer#:BANDwidth:RRIGht?
:CALCulate:MARKer#:BWIDth:RESult?
:CALCulate:MARKer#:BWIDth:RLEFt?
:CALCulate:MARKer#:BWIDth:RRIGht?
:CALCulate:MARKer#:FCOunt[:STATe]
:CALCulate:MARKer#:FCOunt[:STATe]?
:CALCulate:MARKer#:FCOunt:X?
:CALCulate#:MARKer#:X
:CALCulate#:MARKer#:X?
:CALCulate#:FSCan:MARKer#:X
:CALCulate#:FSCan:MARKer#:X?
:CALCulate:MARKer#:X:POSition
:CALCulate:MARKer#:X:POSition?
:CALCulate#:MARKer#:Y
:CALCulate#:MARKer#:Y?
:CALCulate#:FSCan:MARKer#:Y?
:CALCulate:MARKer#[:SET]:CENTer
:CALCulate:MARKer#[:SET]:STEP
:CALCulate:MARKer#[:SET]:STARt
:CALCulate:MARKer#[:SET]:STOP
:CALCulate:MARKer#[:SET]:RLEVel
:CALCulate:MARKer#[:SET]:DELTa:SPAN
:CALCulate:MARKer#[:SET]:DELTa:CENTer
:CALCulate#[:SELected]:MARKer:COUPle
:CALCulate#[:SELected]:MARKer:COUPle?
:CALCulate#[:SELected]:MARKer:DISCrete
:CALCulate#[:SELected]:MARKer:DISCrete?
:CALCulate#[:SELected]:MARKer:REFerence[:STATe]
:CALCulate#[:SELected]:MARKer:REFerence[:STATe]?
:TRACe#:MARKer#:X
:TRACe#:MARKer#:X?
:TRACe#:MARKer#:Y?
:TRACe#:MARKer#:REFerence
:TRACe#:MARKer#:REFerence?
:TRACe:MARKer:COUPle
:TRACe:MARKer:COUPle?
:TRACe#:MARKer#:TYPE
:TRACe#:MARKer#:TYPE?
:TRACe#:MARKer#:ENABle
:TRACe#:MARKer#:ENABle?
:CALCulate:FSCan:MARKer#[:SET]:SLISt
:CALCulate:FSCan:MARKer#[:SET]:METer
:CALCulate:FSCan:MARKer#:TO:METer
INSTrument:MEASure
INSTrument:MEASure?
:DISPlay:VIEW[:SELect]
:DISPlay:VIEW[:SELect]?
[:SENSe]:MEASure:REFLction#:RETUrnloss?
[:SENSe]:MEASure:REFLction#:COEFficient?
[:SENSe]:MEASure:REFLction#:VSWR?
[:SENSe]:CHPower:FREQuency:CENTer
[:SENSe]:CHPower:FREQuency:CENTer?
[:SENSe]:CHPower:BWIDth:INTegration
[:SENSe]:CHPower:BWIDth:INTegration?
[:SENSe]:CHPower:BANDwidth:INTegration
[:SENSe]:CHPower:BANDwidth:INTegration?
[:SENSe]:CHPower:FREQuency:SPAN
[:SENSe]:CHPower:FREQuency:SPAN?
[:SENSe]:CHPower:FREQuency:SPAN:POWer
:MEASure:CHPower?
:MEASure:CHPower:CHPower?
:MEASure:CHPower:DENSity?
[:SENSe]:ACPRatio:BANDwidth:INTegration
[:SENSe]:ACPRatio:BWIDth:INTegration
[:SENSe]:ACPRatio:BANDwidth:INTegration?
[:SENSe]:ACPRatio:BWIDth:INTegration?
[:SENSe]:ACPRatio:OFFSet[:FREQuency]
[:SENSe]:ACPRatio:OFFSet[:FREQuency]?
[:SENSe]:ACPRatio:OFFSet:BANDwidth[:INTegration]
[:SENSe]:ACPRatio:OFFSet:BWIDth[:INTegration]
[:SENSe]:ACPRatio:OFFSet:BANDwidth[:INTegration]?
[:SENSe]:ACPRatio:OFFSet:BWIDth[:INTegration]?
:MEASure:ACPRatio:MAIN?
:MEASure:ACPRatio:LOWer:POWer?
:MEASure:ACPRatio:LOWer?
:MEASure:ACPRatio:UPPer:POWer?
:MEASure:ACPRatio:UPPer?
[:SENSe]:OBWidth:METHod
[:SENSe]:OBWidth:METHod?
[:SENSe]:OBWidth:PERCent
[:SENSe]:OBWidth:PERCent?
[:SENSe]:OBWidth:XDB
[:SENSe]:OBWidth:XDB?
:MEASure:OBWidth?
:FETCh:OBWidth?
:MEASure:OBWidth:OBWidth?
:FETCh:OBWidth:OBWidth?
:MEASure:OBWidth:CENTroid?
:FETCh:OBWidth:CENTroid?
:MEASure:OBWidth:OBWidth:FERRor?
:FETCh:OBWidth:OBWidth:FERRor?
:FETCh:TPOWer?
:MEASure:TPOWer?
[:SENSe]:TPOWer:FREQuency:CENTer
[:SENSe]:TPOWer:FREQuency:CENTer?
[:SENSe]:TPOWer:LLIMit
[:SENSe]:TPOWer:LLIMit?
[:SENSe]:TPOWer:RLIMit
[:SENSe]:TPOWer:RLIMit?
:MEASure:TOI?
:MEASure:TOI:IP3?
[:SENSe]:SPECtrogram:STATe
[:SENSe]:SPECtrogram:STATe?
[:SENSe]:SPECtrogram:RESTart
[:SENSe]:HARMonics:FREQuency:FUNDamental
[:SENSe]:HARMonics:FREQuency:FUNDamental?
[:SENSe]:HARMonics:FREQuency:FUNDamental:AUTO
[:SENSe]:HARMonics:FREQuency:FUNDamental:AUTO?
[:SENSe]:HARMonics:FREQuency:STEP[:INCRement]
[:SENSe]:HARMonics:FREQuency:STEP[:INCRement]?
[:SENSe]:HARMonics:FREQuency:STEP[:INCRement]:AUTO
[:SENSe]:HARMonics:FREQuency:STEP[:INCRement]:AUTO?
[:SENSe]:HARMonics:NUMBer
[:SENSe]:HARMonics:NUMBer?
:FETCh:HARMonics:AMPLitude:ALL?
:MEASure:HARMonics:AMPLitude:ALL?
:FETCh:HARMonics:AMPLitude?
:MEASure:HARMonics:AMPLitude?
:FETCh:HARMonics:FREQuency:ALL?
:MEASure:HARMonics:FREQuency:ALL?
:FETCh:HARMonics:FREQuency?
:MEASure:HARMonics:FREQuency?
[:SENSe]:CNRatio:BANDwidth:INTegration
[:SENSe]:CNRatio:BANDwidth:INTegration?
[:SENSe]:CNRatio:BANDwidth:NOISe
[:SENSe]:CNRatio:BANDwidth:NOISe?
[:SENSe]:CNRatio:OFFSet
[:SENSe]:CNRatio:OFFSet?
:MEASure:CNRatio?
:MEASure:CNRatio:CARRier?
:MEASure:CNRatio:NOISe?
[:SENSe]:HARMonics:SELect
[:SENSe]:HARMonics:SELect?
:CALCulate#:PARameter#:DEFine
:CALCulate#:PARameter#:DEFine?
:CALCulate#[:SELected]:FORMat
:CALCulate#[:SELected]:FORMat?
[:SENSe#]:CORRection:EXTension[:STATe]
[:SENSe#]:CORRection:EXTension[:STATe]?
[:SENSe#]:CORRection:EXTension:PORT#:TIME
[:SENSe#]:CORRection:EXTension:PORT#:TIME?
[:SENSe#]:CORRection:RVELocity:COAX
[:SENSe#]:CORRection:RVELocity:COAX?
[:SENSe#]:CORRection:EXTension:AUTO:PORT
[:SENSe#]:CORRection:COLLect[:ACQuire]:LOAD
[:SENSe#]:CORRection:COLLect[:ACQuire]:OPEN
[:SENSe#]:CORRection:COLLect[:ACQuire]:SHORt
[:SENSe#]:CORRection:COLLect[:ACQuire]:THRU
[:SENSe#]:CORRection:COLLect:CKIT:LABel
[:SENSe#]:CORRection:COLLect:CKIT:LABel?
[:SENSe#]:CORRection:COLLect:CKIT:LABel:CATalog?
[:SENSe#]:CORRection:COLLect:CKIT:GENDer
[:SENSe#]:CORRection:COLLect:CKIT:GENDer?
[:SENSe#]:CORRection:COLLect:METHod[:RESPonse]:THRU
[:SENSe#]:CORRection:COLLect:METHod:SOLT1
[:SENSe#]:CORRection:COLLect:METHod:TYPE?
[:SENSe#]:CORRection:COLLect:CLEar
[:SENSe#]:CORRection:COLLect:SAVE
CALCulate:TRANsform:DISTance:STARt
CALCulate:TRANsform:DISTance:STARt?
CALCulate:TRANsform:DISTance:STOP
CALCulate:TRANsform:DISTance:STOP?
CALCulate:TRANsform:DISTance:UNIT
CALCulate:TRANsform:DISTance:UNIT?
CALCulate:TRANsform:DISTance:WINDow
CALCulate:TRANsform:DISTance:WINDow?
[:SENSe]:CORRection:LOSS:COAX
[:SENSe]:CORRection:LOSS:COAX?
[:SENSe]:DDEMod[:FORMat]:RLENgth
[:SENSe]:DDEMod[:FORMat]:RLENgth?
[:SENSe]:DDEMod[:FORMat]:SRATe
[:SENSe]:DDEMod[:FORMat]:SRATe?
[:SENSe]:DDEMod:MODulation
[:SENSe]:DDEMod:MODulation?
[:SENSe]:ADEMod:STYLe
[:SENSe]:ADEMod:STYLe?
[:SENSe]:DDEMod:FILTer[:MEASurement]
[:SENSe]:DDEMod:FILTer[:MEASurement]?
[:SENSe]:DDEMod:FILTer:ABT
[:SENSe]:DDEMod:FILTer:ABT?
[:SENSe]:DDEMod:FILTer:REFerence
[:SENSe]:DDEMod:FILTer:REFerence?
[:SENSe]:DDEMod:FILTer:RLENgth
[:SENSe]:DDEMod:FILTer:RLENgth?
[:SENSe]:STATistic:STATe
[:SENSe]:STATistic:STATe?
[:SENSe]:DDEMod[:FORMat]:SYMBol:POINts
[:SENSe]:DDEMod[:FORMat]:SYMBol:POINts?
:READ:DDEMod?
:READ:ADEMod?
:DISPlay:VIEW:DENSity:PERSistence
:DISPlay:VIEW:DENSity:PERSistence?
[:SENSe]:CAT:RST
[:SENSe]:CAT:FREFlect:TYPE
[:SENSe]:CAT:FREFlect:TYPE?
[:SENSe]:CAT:FREFlect:OPEN
[:SENSe]:CAT:FREFlect:SHORt
[:SENSe]:CAT:FREFlect:LOAD
:DISPlay:VIEW:DENSity:PERSistence:INFinite
:DISPlay:VIEW:DENSity:PERSistence:INFinite?
:DISPlay:VIEW:SPECtrogram:TRACe:SELection
:DISPlay:VIEW:SPECtrogram:TRACe:SELection?
:DISPlay:VIEW:SPECtrogram:TRACe:STARt
:DISPlay:VIEW:SPECtrogram:TRACe:STARt?
:DISPlay:VIEW:SPECtrogram:TRACe:NUMber
:DISPlay:VIEW:SPECtrogram:TRACe:NUMber?
:CALCulate:RESTart
[:SENSe]:DDEMod:EVM:RMS?
[:SENSe]:DDEMod:EVM:PK?
[:SENSe]:DDEMod:ASK:ERR?
[:SENSe]:DDEMod:ASK:DEPTh?
[:SENSe]:DDEMod:FSK:ERR?
[:SENSe]:DDEMod:FSK:DEVI?
TEST
[:SENSe]:FSCan:SEQuence
[:SENSe]:FSCan:SEQuence?
[:SENSe]:FSCan:SCAN#:POINts?
[:SENSe]:FSCan:SCAN#:TIME
[:SENSe]:FSCan:SCAN#:TIME?
:DISPlay:METer#[:STATe]
:DISPlay:METer#[:STATe]?
[:SENSe]:METer#:DETector:DWELl
[:SENSe]:METer#:DETector:DWELl?
[:SENSe]:METer#:DETector
[:SENSe]:METer#:DETector?
:CALCulate:METer#:LIMit[:DATA]
:CALCulate:METer#:LIMit[:DATA]?
:CALCulate:METer#:LIMit:STATe
:CALCulate:METer#:LIMit:STATe?
:CALCulate:METer#:LIMit:ULLine
:CALCulate:SLISt:MARK:SIGNal
:CALCulate:SLISt:MARK:CLEar:SIGNal
:CALCulate:SLISt:MARK:ALL
:CALCulate:SLISt:MARK:CLEar:ALL
:CALCulate:SLISt:DELete:SIGNal
:CALCulate:SLISt:DELete:ALL
:CALCulate:SLISt:SORT:TYPE
:CALCulate:SLISt:SORT:ORDer
:CALCulate:SLISt:SORT:ORDer?
:CALCulate:METer:POWer[:CURRent]?
[:SENSe]:METer:PHOLd:RESet
:SEQ:RUN?
:READ:DDEMod:BIT?
CALCulate:MARKer#:MAXimum
CALCulate:MARKer#:MINimize
CALCulate:FSCan:MARKer#:MAXimum
CALCulate1:MARKer#:MAXimum
CALCulate1:MARKer#:MINimize
CALCulate:MARKer#:MAXimum[:SET]:CENTer
CALCulate:MARKer#:MAXimum:NEXT
CALCulate:MARKer#:MAXimum:LEFT
CALCulate:FSCan:MARKer#:MAXimum:LEFT
CALCulate:MARKer#:MAXimum:RIGHt
CALCulate:FSCan:MARKer#:MAXimum:RIGHt
CALCulate:MARKer#:PTPeak
CALCulate:MARKer#:CPSearch[:STATe]
CALCulate:MARKer#:CPSearch[:STATe]?
CALCulate:MARKer#:CPEak[:STATe]
CALCulate:MARKer#:CPEak[:STATe]?
CALCulate:MARKer#:CVSearch[:STATe]
CALCulate:MARKer#:CVSearch[:STATe]?
CALCulate:MARKer:PEAK:TABLe[:STATe]
CALCulate:MARKer:PEAK:TABLe[:STATe]?
CALCulate:PEAK:TABLe?
CALCulate:MARKer:PEAK:EXCursion
CALCulate:MARKer:PEAK:EXCursion?
CALCulate:MARKer:PEAK:THReshold
CALCulate:MARKer:PEAK:THReshold?
CALCulate:MARKer:PEAK:SEARch:MODE
CALCulate:MARKer:PEAK:SEARch:MODE?
CALCulate:MARKer:PEAK:SORT
CALCulate:MARKer:PEAK:SORT?
[:SENSe]:SWEep:TIME
[:SENSe]:SWEep:TIME?
[:SENSe]:SWEep:TIME:AUTO
[:SENSe]:SWEep:TIME:AUTO?
[:SENSe]:ACQuisition:TIME
[:SENSe]:ACQuisition:TIME?
[:SENSe]:ACQuisition:TIME:AUTO
[:SENSe]:ACQuisition:TIME:AUTO?
[:SENSe]:SWEep:SPEed
[:SENSe]:SWEep:SPEed?
:INITiate#:CONTinuous
:INITiate#:CONTinuous?
:INITiate#[:IMMediate]
:INITiate#:RESTart
[:SENSe]:FSCan:SCAN:ABORt
[:SENSe]:SWEep:MODE
[:SENSe]:SWEep:MODE?
[:SENSe]:SWEep:COUNt
[:SENSe]:SWEep:COUNt?
[:SENSe]:FSCan:SCAN#:PRBW
[:SENSe]:FSCan:SCAN#:PRBW?
[:SENSe]:FSCan:SCAN#:PRBW:AUTO
[:SENSe]:FSCan:SCAN#:PRBW:AUTO?
[:SENSe]:QPD:DWELl:TIME
[:SENSe]:QPD:DWELl:TIME?
[:SENSe#]:SWEep:POINts
[:SENSe#]:SWEep:POINts?
:INITiate:PAUSe
:INITiate:RESume
ABORt
*OPC
*OPC?
*WAI
*TRG
*IDN?
DEBTTT
DEBug:CALibration:MODE
[:SENSe]:CALibration:STATe
*RST
:SYSTem:CLEAr
:SYSTem:RESTart
:SYSTem:POWer:OFF
SCOPeid?
DISconnectDEVice
:SYSTem:CONFigure:SYSTem?
HCOPy:SDUMp:DATA?
:KEY:CONTrol
:MMEMory:PATH
:MMEMory:STORe
:MMEMory:LOAD
:MMEMory:DELete
:SYSTem:LKEY
:SYSTem:LKEY?
:SYSTem:LKEY:DELete
:SYSTem:OPTions?
:SYSTem:LKEY:TIME:RESet
:SYSTem:MODE:FACTory?
:SYSTem:LANGuage
:SYSTem:LANGuage?
:SYSTem:COMMunicate:LAN:CONFig:APPLy
:INSTrument[:SELect]
:INSTrument[:SELect]?
DEBug:CALibration:FILe:SAVe
DEBug:SWEEp:STOP
DEBug:SWEEp:RESTart
:DISPlay:WINDow:TRACe:Y:DLINe:STATe
:DISPlay:WINDow:TRACe:Y:DLINe:STATe?
:DISPlay:WINDow:TRACe:Y:DLINe
:DISPlay:WINDow:TRACe:Y:DLINe?
:DISPlay:WINDow:TRACe:GRATicule:GRID:BRIGhtness
:DISPlay:WINDow:TRACe:GRATicule:GRID:BRIGhtness?
:SYSTem:PRESet:USER#:SAVE
:SYSTem:PRESet:USER#:LOAD
[:SENSe]:EXTReference:AUTO
[:SENSe]:EXTReference:AUTO?
:DISPlay:WINDow:SELect
:DISPlay:WINDow:SELect?
:DEV:SVA?
*OPT?
INST:CAT?
:SYSTem:INFO:VERSion?
:RELease:VERSion?
:SYSTem:OVERload:TIME?
:OUTPut[:STATe]
:OUTPut[:STATe]?
:SOURce#:POWer[:LEVel][:IMMediate][:AMPLitude]
:SOURce#:POWer[:LEVel][:IMMediate][:AMPLitude]?
:SOURce:CORRection:OFFSet
:SOURce:CORRection:OFFSet?
:CALCulate:NTData[:STATe]
:CALCulate:NTData[:STATe]?
:DISPlay:WINDow:TRACe:Y[:SCALe]:NRLevel
:DISPlay:WINDow:TRACe:Y[:SCALe]:NRLevel?
:DISPlay:WINDow:TRACe:Y[:SCALe]:NRPosition
:DISPlay:WINDow:TRACe:Y[:SCALe]:NRPosition?
:DISPlay:WINDow:NTTRace[:STATe]
:DISPlay:WINDow:NTTRace[:STATe]?
:TRACe#:MODE
:TRACe#:MODE?
:TRACe#:FSCan:TYPE
:TRACe#:FSCan:TYPE?
[:SENSe]:AVERage:TRACe#:COUNt
[:SENSe]:AVERage:TRACe#:COUNt?
[:SENSe]:AVERage:TRACe#:CLEar
[:SENSe]:DETector:TRACe#[:FUNCtion]
[:SENSe]:DETector:TRACe#[:FUNCtion]?
[:SENSe]:FSCan:DETector:TRACe#
[:SENSe]:FSCan:DETector:TRACe#?
[:SENSe]:DETector:TRACe:PVTime
[:SENSe]:DETector:TRACe:PVTime?
[:SENSe]:DETector:TRACe:SPECtrogram
[:SENSe]:DETector:TRACe:SPECtrogram?
[:SENSe]:AVERage:TRACe#?
:CALCulate#[:SELected]:MATH:FUNCtion
:CALCulate#[:SELected]:MATH:FUNCtion?
:TRACe:MATH:TYPE
:TRACe:MATH:TYPE?
:TRACe:MATH:Z
:TRACe:MATH:X
:TRACe:MATH:Y
:TRACe:MATH:Z?
:TRACe:MATH:X?
:TRACe:MATH:Y?
:TRACe:MATH:OFFSet
:TRACe:MATH:OFFSet?
:TRACe#[:DATA]?
:TRACe:REF[:DATA]?
:TRACe#:FSCan[:DATA]?
:TRACe:ADC[:DATA]?
:TRACe[:DATA]:SPECtrum?
:TRACe[:DATA]:PVT?
:FORMat[:TRACe][:DATA]
:FORMat[:TRACe][:DATA]?
:CALCulate#:PARameter:COUNt
:CALCulate#:PARameter:COUNt?
:CALCulate#:PARameter#:SELect
:TRACe:SELect?
:CALCulate#[:SELected]:MATH:MEMorize
[:SENSe#]:AVERage:TRACe#:STATe
[:SENSe#]:AVERage:TRACe#:STATe?
:DISPlay:WINDow#:TRACe#:STATe
:DISPlay:WINDow#:TRACe#:STATe?
:DISPlay:WINDow#:TRACe#:MEMory[:STATe]
:DISPlay:WINDow#:TRACe#:MEMory[:STATe]?
:CALCulate#[:SELected]:DATA:FDATa
:CALCulate#[:SELected]:DATA:FDATa?
:CALCulate#[:SELected]:DATA:FMEMory
:CALCulate#[:SELected]:DATA:FMEMory?
[:SENSe#]:AVERage:COUNt
[:SENSe#]:AVERage:COUNt?
[:SENSe#]:AVERage[:STATe]
[:SENSe#]:AVERage[:STATe]?
:TRACe#:HOLD
:TRACe#:HOLD?
:TRACe#:DATA:NAME
:TRACe#:DATA:NAME?
:TRACe#:FORMat[:Y]
:TRACe#:FORMat[:Y]?
:DISPlay:LAYout
:TRACe:DEMod:EYE:LENGth
:TRACe:DEMod:EYE:LENGth?
:TRACe:DEMod:TABLe:FORMat
:TRACe:DEMod:TABLe:FORMat?
:TRACe:COPY
:TRACe:COPY:REF
:TRIGger[:SEQuence]:SOURce
:TRIGger[:SEQuence]:SOURce?
:TRIGger[:SEQuence]:VIDeo:LEVel
:TRIGger[:SEQuence]:VIDeo:LEVel?
:TRIGger[:SEQuence]:RFBurst:SLOPe
:TRIGger[:SEQuence]:RFBurst:SLOPe?
:TRIGger[:SEQuence]:RF:LEVel
:TRIGger[:SEQuence]:RF:LEVel?
:TRIGger[:SEQuence]:LEVel:LEVel
:TRIGger[:SEQuence]:LEVel:LEVel?
:TRIGger[:SEQuence]:LEVel:DELay
:TRIGger[:SEQuence]:LEVel:DELay?
:TRIGger[:SEQuence]:EXTernal:SLOPe
:TRIGger[:SEQuence]:EXTernal:SLOPe?
:TRIGger[:SEQuence]:EXTernal:DELay
:TRIGger[:SEQuence]:EXTernal:DELay?
TRIGger[:SEQuence]:FMT:MASK:BUILd
:TRIGger[:SEQuence]:FMT:TCRiteria
:TRIGger[:SEQuence]:FMT:TCRiteria?
:TRIGger[:SEQuence]:FMT:STATe
:TRIGger[:SEQuence]:FMT:STATe?
:TRIGger[:SEQuence]:FMT:ACTion
:TRIGger[:SEQuence]:FMT:ACTion?
:TRIGger[:SEQuence]:FMT:TRACe
:TRIGger[:SEQuence]:FMT:TRACe?
:TRIGger[:SEQuence]:FMT:MASK:DELete:ALL
DEBug:S11:CALibration:STATe
Hi,
what I found out for a unit in Pro mode (SVA3021x+) regarding VNA calibration & firmware 3.2.2.5.0.r8.
1) 1-port cal - does not really work suffiently.
2) Enhanced response calibration is working quite well. It does not change the start & stop frequencies, nor the number of points. After a performed calibration it is saving the data internally, Calibration on/off is only working from the enhanced response menu. This is true for a cold boot, too. Only downside you need to memorize the number of points you performed for the calibration. As soon as you apply the "right" number of points, start & stop freq., the calibration is used and showing "COR" in the upper left corner.
3) you can save calibration data as ".CAL" for example on the internal flash. When you load the data, you only need to apply points, start & stop - and again the "COR" shows up. (note them in the file name!)
4) For me it seems all preset and user Calibration Standards are not working. Port extension is not saved, either.
indeed - changing a value of the user cal does the trick. Even with firmware 3.2.2.5.0.r8
Another short question. As I put my DIY GPSDO with OCXO (I love acronyms) circuit board into live today.You don't.
When comparing the warm Siglent SSA/SVA 1032x + with the homebrew GPSDO & very old DIY DCF 77 controlled oscillators with 10Mhz output, I see that the Siglent is of +2.15 hz - not a big deal, but .... :)
Anybody else checked the Offset of the internal 10 Mhz ? How to enter the offset permanentely other than every time after a cold boot under Frequency/ Freq Offset ?
thanks & best regards,
Juergen
Hi everyone. Sorry if there is this information somewhere within the topic, I was not able to find it. I'm considering buying SVA1032x for LNA design. The amplifiers will be high gain and low power so I need to have control over TG power in VNA mode. I figured out that this option was enabled with the firmware update 05/2020, but I was not able to find the specs on how much TG can be attenuated. Can somebody make a check?
I encountered my first serious issue with my SVA1032x. I am not sure if I had too many calibrations saved, but for whatever reason, none of my calibrations were working and a few times the unit would power up and the spectrum analyzer had no reading. It wasn't until I did a factory reset that it started working properly again. I usually unplug it every time I am done with it because our power company has had numerous power surges. I hope I don't have issues when the memory battery goes dead...Did Factory Reset retain your Cal files ? IIRC they should still be in the internal memory.
Hi all,Certainly and you can also activate a total of 4 traces showing Log Mag, SWR, Smith and Phase.
I'm considering a SVA1032X but I'd like to get an impedance vs freq plot log/log similar to the example below. Is that possible with this? Is it available with other instruments?
Tx
Ken
I'm considering a SVA1032X but I'd like to get an impedance vs freq plot log/log similar to the example below. Is that possible with this?
Did Factory Reset retain your Cal files ? IIRC they should still be in the internal memory.Now I am second guessing myself. I cannot remember if I hit "Factory Reset" or "Reset & Clear". Whatever I hit cleared all of my saved calibrations. I had dozens for various cables, connectors and frequency spans. All gone. I will have to periodically save them to USB as I create them.
Can you still load them ?
And FW version please.
Yes I had that problem with saved Cals too after upgrading FW versions and I see you are still on V4.0.Did Factory Reset retain your Cal files ? IIRC they should still be in the internal memory.Now I am second guessing myself. I cannot remember if I hit "Factory Reset" or "Reset & Clear". Whatever I hit cleared all of my saved calibrations. I had dozens for various cables, connectors and frequency spans. All gone. I will have to periodically save them to USB as I create them.
Can you still load them ?
And FW version please.
Hi,
I'm considering getting an SSA30xxX Plus to hack to an SVA. Are the SSA 3015X+ and SSA3021X+ the same HW, do they both hack to an SVA3032? Where is the dividing line in the HW?
So the 3015 is it's own thing, but I think there is another line then that is above the 3032.
So the 3015 is it's own thing, but I think there is another line then that is above the 3032. But I think those are out of reach for me, sounds like the 3021 is my starting point.It is.
I'm considering a SVA1032X but I'd like to get an impedance vs freq plot log/log similar to the example below. Is that possible with this? Is it available with other instruments?
When it works, it is great. When it plays up, I am pulling my hair out.Please don't think I'm taking the piss but a good USA friend with new SNA5014A had similar problems until he got on top of connector cleanliness as outlined in this Siglent video:
The response at the low freq end of the SVA devices was poor, and so you could just be seeing the low freq 'tail' of the smith chart jumping around.
You have already noted it is fine above 2.5MHz. Below that it will bounce around on the Smith chart. So start the sweep at 2.5Mhz and see what happens.
This spec was improved in the newer units, but I don't believe it is great. I don't have one to try and replicate.
Other points:
You need to simplify things and start from a known base. This is troubleshooting 101.
Switch to LogMag images only for now, it is much easier to look at and interpret.
Factory reset is not the same as turning it off and on. You really need to factory reset before reporting a fault so that others can replicate the issue.
You're testing active devices, so perhaps you reduced the TG output level? This could be making the S11 low freq response worse.
It is hard work to follow your pictures, there is too much going on, too many traces.
Your DUT's are too complex. If you want to demonstrate a fault with the unit then test something simple with a known response - like an attenuator or a load.
The marker colours are not matching either - which appears to be a screenshot bug worth reporting.
Have you checked to see if you are using the latest firmware?
Also, I have a set of new N-SMA adapters which I think I got from MiniCircuits which look clean and perfect but cause problems. But agree, not likely a problem at 1MHz.
Factory reset. One trace per picture. Start with the simplest calibration possible and then measure some VERY simple device.
Simple device would be an attenuator if you have one, or a load.
Ideally make a video showing these steps, if it shows an issue then stick it up on Youtube for us to review. Then if we can't solve it we can send it direct to the Siglent engineers.
You may well be correct and the device could well be faulty.
But you could also be suffering from confirmation bias caused to the frustration of having so many problems.
Ok I watched the video more closely.
The first time you did the 1 port cal you used the 50 ohm load for the short and the load.
Short/Load:
https://youtu.be/t-wb9Cz4c1s?t=181
The second time you did it correctly.
That is why it worked the second time and not the first.
I would return the second unit and ask for a full refund.
I would then buy the SSA3021X+ and read this thread from the beginning.
If the second unit is still working weird with black screens and strange behaviour, you are certainly entitled to just send it back for a full refund. No point trying this and that, doing a factory reset, etc. This device should work fine out of the box.
Ok I watched the video more closely.
The first time you did the 1 port cal you used the 50 ohm load for the short and the load.
Short/Load:
https://youtu.be/t-wb9Cz4c1s?t=181
The second time you did it correctly.
That is why it worked the second time and not the first.
The hint was that you can hack a SSA3021X+ (the plus model) into a SVA1032.
It will cost you little more money than the SVA1015X. I guess this model is not sold much anymore...
QuoteOk I watched the video more closely.
The first time you did the 1 port cal you used the 50 ohm load for the short and the load.
Short/Load:
https://youtu.be/t-wb9Cz4c1s?t=181
The second time you did it correctly.
That is why it worked the second time and not the first.
you are wrong I am afraid. Please watch 55s. At 1:00 I transferred the load from NanoVNA to Siglent VNA. At 1.25s I incorrectly said it is registered open, it should be short. Also you ignore all evidence presented to you . There are lots of noisy traces flying across the Smith chart. You are wrong to assume the load is longer than others. My load is quite short.
You try to tell me I cannot tell what is a 50 ohm load? Come on. I have both long and short 50 ohm loads. Anyone who has used a VNA would notice that the traces should not fly across the screen like that without or with calibration.
I dont want to spend another minute thinking about it or try to argue about it.
ust a note of encouragement. Like you, I have a few Siglent bits of kit - A scope, the SVA3021X (started life as the SSA model), a SDM3055M and a power supply. All from Telonic.
In all cases, happy as larry :) apart from the Bench DMM. That was a bit of a saga - I bought the 3045X then sent it back because of the relay design fault in order to exchange for a 3055 (all mentioned elsewhere) which when it arrived had a marginal kind of fault - one of the 4mm sockets was a bit rough and the probes didn't feel quite right when pushing into that one. All of this kit cost much hard earned cash of course and although I got a gentle comment back saying that the probes went in ok and there wasn't much wrong, as far as I was concerned it wasn't a £10 meter from Aliexpress, and I expected better. These instruments will last me a long time (and I will be buying more stuff from that supplier) and I like to feel good about this kind of purchase, not feel a pang of regret every time I switch it on. So to their credit, the supplier sent me a new 3055 and now all is well.
If your VNA isn't right I am sure you are doing the right thing in rejecting it whether you decide to get another one or not. I am sure Telonic will do the right thing (do let us know either way - its good to reward good businesses and personal recommendations on these forums do help them I am sure). Eventually you will have the kit that you want and all the hassles of backwards and forwards / phone calls, emails and videos will be just a memory !).
Regards
Eloso
p.s. if you didn't buy it as a commercial customer, then don't forget there are distance selling regulations in the UK that allow you to return goods within a certain time period without actually needing to prove them faulty. I can't remember the exact laws now - they changed a little while back but a quick google will come up with it. I am sure Telonic will be helpful though in any case.
I think your N-type to SMA adapter that you are using on the SVA is worn out.
I have the same issues with the SVA1032.
The smith chart is very noisy and short/load/open are not described as points in the log smith chart view.
I use a professional calibration kit.
Another thing, when i want to specify my cal-kit under user cal. I cannot enter the specific details of the load ( it is grayed out as being exactly 50 ohm, which is not ). All other can be specified.
Does anyone has a clue?
Evert
Also, in this video at the 2 minute mark, you see how the load temporarily made contact then dropped out again when you were attaching it? There you go right there, shot. You essentially did the load calibration with an open :) GET NEW ADAPTERS!!!!!
Just entertain me and try a different adapter, what do you have to lose?
or a bad connection, yes, that is normal. With the tech returning it to you stating that it was fine, with the obvious bad connection in your video, and with me showing how to replicate your results by simulating a bad connection, and you still think that $1 connector is good... I have no further comment either ~ except one. I'm sorry to hear you had such trouble and I hope that you eventually find a good VNA that works for you.
If it like a patient told his doctor he has persistent headache on and off randomly, it could be a migraine, tension headache, gluacoma, sinusitis, Covid, brain tumour....Right, but before going in for a chemotherapy or a brain transplant, you first look at your caffeine intake, pop an aspirin, check for TMJ or ear infections and see if the thyroid glands are swollen. I was suggesting trying a different adapter, you opted for the transplant...
I was suggesting trying a different adapter, you opted for the transplant...
@regenfreak,
You did the only sensible thing you could have done in this circumstance. @antenna is right in a way but he's forgetting the other ten SMA connections and their five patch cables inside the SVA as pictured here:
https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg3088340/#msg3088340 (https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg3088340/#msg3088340)
When I saw your plots, it put me in mind of techneut's experience after cross-flashing his SSA to an SVA, hence my guessing from the symptoms you'd described that the fault was very likely one of these internal connections (a loose or damaged connector or faulty patch cable).
Regardless of the actual cause, the problem was obviously a fault within the SVA itself (the black screen events were enough cause in themselves to justify a return).
Telonic, when convinced that you have reasonable cause to reject the goods as faulty, will respond to such requests without undue delay, even when it means they have to bear the cost of collect and return. TBH, I was wondering just when you were going to request a return with full refund, hence my "vote of thanks" when you finally did so :).
That could mean we could upgrade the new SVA1015 to higher BW... ::)Don't be so hasty as we need check this out first.
The most recent Data Sheet (DS0701X_E05B) for the SVA1000 series specifies that the SVA1015X now has the same VNA and Tracking Generator specifications as the SVA1032X and the SVA1075X, i.e. 100KHz low frequency limit. A query to Siglent engineering responded that the DS0701X_E05B data sheet is correct.We should have a 1.5 GHz model next week and in our PD checks will have a quick look at VNA stimulus frequency limits....
Can anyone confirm from your SVA1015X that these new limits are actually correct? These are key parameters for a buying decision.
Thanks!
Don't be so hasty as we need check this out first.
Yes datasheet says VNA stimulus now = higher BW models but there are also other error in the datasheet in spec for all models.
Yep, of course and it's very likely the inbuilt bridge was swapped out however if you hunt through the datasheet there are still a # of differences to the 3.2 GHz model including weight = lesser HW. ;)Don't be so hasty as we need check this out first.
Yes datasheet says VNA stimulus now = higher BW models but there are also other error in the datasheet in spec for all models.
No hastiness here, just thinking out loud.
Nonetheless, I remember who has indicated in the past the low freq. distinction as a sign that the HW should be different. ;)
Fresh arrival.Yep, of course and it's very likely the inbuilt bridge was swapped out however if you hunt through the datasheet there are still a # of differences to the 3.2 GHz model including weight = lesser HW. ;)Don't be so hasty as we need check this out first.
Yes datasheet says VNA stimulus now = higher BW models but there are also other error in the datasheet in spec for all models.
No hastiness here, just thinking out loud.
Nonetheless, I remember who has indicated in the past the low freq. distinction as a sign that the HW should be different. ;)
But when the # of VNA data points are wrong by an order of magnitude it screams someone is not doing their job ! :horse:
The only way to use all of the provided params is to export the sweep data to a PC and do the calibration there.
I was using my SVA1032X and found when I turn on min/max or averaging traces there is no way to "reset" the traces which makes it hard to connect probe and then start the min/max, has anyone else seen this, am I missing something?
Additionally I found that there is no way to freeze screen, ie stop. For example I am probing with min/max on and then need to release the probe and save waveform, but it does not appear I can do this. Anyone have suggestions on how to stop and freeze the system?
I am also looking at trying to do impedance measurements with the SVA, it looks like it should be possible and was wondering if anyone has done this and might have a python scripts for such a feature?
Thanks
I was using my SVA1032X and found when I turn on min/max or averaging traces there is no way to "reset" the traces which makes it hard to connect probe and then start the min/max, has anyone else seen this, am I missing something?You're overlooking the type of trace required/selected for each task and the type of detection required.
Additionally I found that there is no way to freeze screen, ie stop. For example I am probing with min/max on and then need to release the probe and save waveform, but it does not appear I can do this. Anyone have suggestions on how to stop and freeze the system?In the Trace menu use the View option that ceases the sweep and freezes the trace, permanently until you select one of the other Trace options or reclick on the type you were using to start the sweep again.
I wanted to measure the impedance of piezo probe. So I setup the VNA on S11, Smith chart R+jX, and got the enclosed smith chart.
The SVA1015X or alike
Please in VNA mode, is it possible to change the IF Bandwidth?
I searched the thread concerning IF bandwidth but could not find anything (strangely)
It is a SSA3021X plus hack/upgrade and I did calibrate with short/open/50 Ohm load. I also tested the VNA with 100 ohm and 50 ohm resistors to make sure the impedance was reasonable.
I actually got the magnitude and phase graphed, for the VNA
One of the things with the piezo is looking for the resonate frequency, which is typically the point where the phase is closest to zero. In the O-scope version this matches what I was expecting and is at ~8.25Mhz, while the VNA shows to be at 8.5Mhz which is a significant difference. A second issue I wonder about is that from what I have read the resonance frequency should have the lowest impedance, which does not match the data.The external capacitive loading lowers the resonance frequency. In the case of the VNA it is compensated by the calibration, so there is no excess capacitance if you calibrated on the DUT plane. In the case of the scope you may have a few 10s to 100 pF of additional shunt capacitance.
Are you using the same start/stop frequencies and number of points? If these are different it only makes sense that the saved file won't open.Can your older SSA3kX save and recall a TRC (Trace) file ? That's the only issue this end.
I don't own this device, so I can't test, but my own software uses a similar feature with this exact limitation
Regards,
Vitor
Fresh arrival.Yep, of course and it's very likely the inbuilt bridge was swapped out however if you hunt through the datasheet there are still a # of differences to the 3.2 GHz model including weight = lesser HW. ;)Don't be so hasty as we need check this out first.
Yes datasheet says VNA stimulus now = higher BW models but there are also other error in the datasheet in spec for all models.
No hastiness here, just thinking out loud.
Nonetheless, I remember who has indicated in the past the low freq. distinction as a sign that the HW should be different. ;)
But when the # of VNA data points are wrong by an order of magnitude it screams someone is not doing their job ! :horse:
100 KHz is certainly the minimum stimulus frequency that can be set.
Still waiting for official confirmation......
Quick question if I may,
Since I use my now liberated SVA1032X only for hobby purposes I'm not in the market for a professional mechanical calibration kit but for something slightly nicer then the average AliExpress stuff. I found a fairly economical mechanical calibration kit, made of Rosenberg SMA parts, on SDR-kits.net
The kit comes with calibration instructions from Kurt Poulsen OZ7OU, are made with the best intentions but not the easiest to understand for me.
The idea is to enter the female cal kit parameters under Calibration>cal Kit>User1 and the male cal kit parameters under User2
I can enter the "define open" delay of 42.3ps and no need to change C0, C1, C2 or C3 so that's all ok. But when I try to enter the "define Load" parameters the delay and Terminal Impedance fields are greyed out and there are no fields for C0, C1, etc, while the kit comes with a measured terminal impedance and the instructions to define CII as 5pf.
Any idea how I can enter the calibration parameters?
Link to the instructions: https://www.sdr-kits.net/documents/Rosenberger_Female_Cal_Standards_rev5.pdf (https://www.sdr-kits.net/documents/Rosenberger_Female_Cal_Standards_rev5.pdf)
Can this hack be used on the SSA3015x plus ? I was told the hardware is exact, is this true?Same as what ? Same as SVA1015X, I believe so.
Andrew
I'm having a terrible time interfacing with the SVA1032X over USB. It is quite frustrating as I have some testing I'd really like to automate. I'm using python and the python-usbtmc package.After a bit of a hunt I can find no mention of Python commands or their USB driver as suitable to use with these instruments.
Please take VNA discussion to the correct threads. :horse:
Are you able to find out what ECal models the SVA1000X supports with the latest firmware V3.2.2.6.0R7 ?Show me the menu....screenshot not a photo please.
Are you able to find out what ECal models the SVA1000X supports with the latest firmware V3.2.2.6.0R7 ?Show me the menu....screenshot not a photo please.
Currently there are no ECal kits available from Siglent however when I had a SNA5000A several from other brands were supported.
https://siglentna.com/products/accessories/vna-calibration-kits/
How does the FFT on something like a sds1200X-E, compare to an entry level dedicated SA , for sub-200MHz ?The obvious differences are:
You must have something wrong. 26 seconds here for 3.2.2.6.0R7Unfortunate since there's not much to mess up during the upgrade process...
Look here https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg4294279/#msg4294279 (https://www.eevblog.com/forum/testgear/siglent-ssa3000x-spectrum-analyzers/msg4294279/#msg4294279) and a few messages previous.
The jist was to goto menu button System/Power On Preset and set 'Power on and 'Preset' to Def and if that doesn't work press the 'Reset & Clear' and if that doesn't 'Factory Reset' and after that it's hack time.
Unit won't respond to PWR + PresetSorry my short hand for entering buttons is lacking. I don't think there are any 2 simultaneous button presses on this machine.
I don't know what button(s) "Reset & Clear" are.
I tried the link you added, factory reset over SCPI doesn't even work :-- (EDIT: I do appreciate the help though!)
32 seconds here after upgrade.
I remember posts mentioning problematic system response due to very large log files clogging the file system, caused by some missing configuration causing error logs at each boot. If I remember well, it was due to the default VNA calibration files missing. Those logs could be deleted.
Search here or in the SSA thread.
I don't think you'll solve by downgrading FW.
Turns out that Siglent enabled the menu option (in "MODE") from some SVA firmware version. When you try to use it you obtain frozen displays. So it seems to work!Ony issue I can see is that there seems to be no spectrum display in RTSA mode? That said it might be operator error. Other modes are working fine.
RTSA is not a SVA option. You see it because you "hacked" it.
I get a reading, very unstable of no better than 20db return loss. On the smith chart I can't get a nice neat spot on the centre line - it is all over the place.
I wonder if anyone else has experienced this or has some suggestions ?
*** SIGLENT FEATURE REQUEST ***
The new SVA1032X firmware upgrade 3.2.2.6.0R7 upgrade works, BUT...
:-- The field "IF bandwidth" for the VNA is still grayed at 10 kHz and this seriously limits the performance of the instrument.
So, please, if somebody here can contact Siglent, ask them to change this! Even the NanoVNA can configure lower BWs, improving the measurement noise and hence the dynamic range.
Based on the hardware performance in SA mode, the instrument should be able to reach 100 or better 10 Hz BW.
The DANL is specified in the data sheet with -156 dBm/Hz. At 10kHz ENBW, this should result in a noise floor of -116 dBm. Is that so bad?
OTOH, the DANL of the NanoVNA is certainly worse, so a narrower RBW is needed to compensate. However, this does not come for free, but it comes at the cost of a slow sweep.
DANL is specific to the SA mode. In VNA it is much worse: preamp is missing and the bridge introduces a loss in S11 mode.
In VNA it is much worse: preamp is missing and the bridge introduces a loss in S11 mode.Show us this with a load and Mag Loss trace.
In VNA it is much worse: preamp is missing and the bridge introduces a loss in S11 mode.Show us this with a load and Mag Loss trace.
:popcorn:
0dB stimulus should return a ~0dB trace.
Member RoV has no issue with S21 measurements, a through measurement and only makes comment on S11 measurement, a reflection measurement.In VNA it is much worse: preamp is missing and the bridge introduces a loss in S11 mode.Show us this with a load and Mag Loss trace.
:popcorn:
0dB stimulus should return a ~0dB trace.
The question is, what's the S21 noise floor when you measure S21 of a "zero-gain DUT" using a stimulus of (say) 0dBm?
(an example of a zero gain DUT is if you terminate port 1 and port 2 with 50R each)
[ And (any) bridge or directional coupler certainly does introduce some additional dynamic range loss for S11 readings, since only a fraction of the signal is coupled to the receiver. ]
Member RoV has no issue with S21 measurements, a through measurement and only makes comment on S11 measurement, a reflection measurement.
I asked for a loaded Mag Loss trace which will show if there is a problem or not.
Understood however I have never used such practices for S11 antenna measurements of which I have done many.Member RoV has no issue with S21 measurements, a through measurement and only makes comment on S11 measurement, a reflection measurement.
I asked for a loaded Mag Loss trace which will show if there is a problem or not.
I mentioned S11 because it tends to be more noisy due to the additional loss introduced by the internal bridge. S21 doesn't use the bridge, because the analyzer is a T/R, not a full 2-port, so in S21 mode is equivalent to the SA in tracking mode (however, in VNA mode it misses the BW setting respect to SA mode).
If you measure a load you will find S11=0 with some noise. If you look at it in Log Mag mode, you'll see a noise level around -something (perhaps -50 dB?). Decreasing the BW, this would improve.
This is particularly critical if some device is inserted. For example, when measuring an external antenna impedance, in order to avoid the risk of damaging the VNA due to external signals, I prefer to insert a limiter in series to the port (full limit @5-10 dBm), followed by a 10 dB attenuator . Then I calibrate AFTER those devices. In this way the VNA port is very well protected, but >20 dB attenuation are added to the measurements (the chain limiter+attenuator is passed twice, first by the test signal and then by the reflected one), so traces tend to be very noisy (even during calibration) unless BW is kept small. This procedure worked very well with an old hp 8714ES, but doesn't with the SVA1032X.
Average safe reverse power Total : 30 dBm (1 W)
Maximum safe reverse level Voltage: ±50 VDC
How any ordinary antenna we might sweep might exceed these levels is unclear. :-//
Average safe reverse power Total : 30 dBm (1 W)
Maximum safe reverse level Voltage: ±50 VDC
How any ordinary antenna we might sweep might exceed these levels is unclear. :-//
Antenna measurement was just an example.
I don't think the 30 dBm rating applies to port 1. It does, for a brief time and -I believe- with at least 20 dB internal attenuation inserted, for port 2 (SA port).
RTFM/datasheet.Average safe reverse power Total : 30 dBm (1 W)
Maximum safe reverse level Voltage: ±50 VDC
How any ordinary antenna we might sweep might exceed these levels is unclear. :-//
Antenna measurement was just an example.
I don't think the 30 dBm rating applies to port 1.
It does, for a brief time and -I believe- with at least 20 dB internal attenuation inserted, for port 2 (SA port).Port 2 (RF In) has more defined specs as expected and in SA and adjustable attenuation: 0 ~ 50 dB
When having longer antennas, eg. 40+ meter you get to certain times quite impressives levels. Especially when ROV is starting to transmit nearby - or somebody else e.g. in a car.From the User manual preface:
To that comes - and that is more important for magnitudes - a static charging of the Antenna and coax cable to several hundreds of Volts, which generates enormous HF-Spikes when the max Voltage of the insulation at a certain point in the structure is reached and an arc will occur.
This is not hypothetical - it's a matter of fact. I had a ground plane Antenna, which was not having an inductor to ground on the roof - for 2m only - I measured nearly a 1000v during a rain shower with an electron tube multimeter (ancient) .
I have seen cases where the input and power transistors of transceivers were killed by the peaks produced by static arcs.
From the User manual preface:
Electrostatic Prevention
Operate the instrument in an electrostatic discharge protective area environment to avoid damages
induced by static discharge. Always ground both the internal and external conductors of the cable to
release static before connecting.
Antenna static problems are nothing new and no different to what my pop faced with his end fed 30m SW antenna 75 years ago well before I was even a twinkle in his eye.From the User manual preface:
Electrostatic Prevention
Operate the instrument in an electrostatic discharge protective area environment to avoid damages
induced by static discharge. Always ground both the internal and external conductors of the cable to
release static before connecting.
but one time grounding does not help if the capacitors (coax line) are re-charged. I would never use port 1 or 2 of the VNA without external protection with an Antenna mounted outside.
Understood however I have never used such practices for S11 antenna measurements of which I have done many.
Hi...Compare specs carefully against SVA1032X. ;)
I am still missing a spectrum analyzer for home, but I also want to be able to measure the overtagunsfunktion of filters, so I will probably need the combi device from siglent:
https://www.batronix.com/versand/spektrumanalysator/Siglent-SVA1015X-VNA.html (https://www.batronix.com/versand/spektrumanalysator/Siglent-SVA1015X-VNA.html)
Are there any reservations about this device ?
I had skimmed the manual earlier, the VNA section.
If I have interpreted correctly, the start frequency is at 10Mhz ?
That would be high, if one wants to represent e.g. the transmission line of a 10Mhz filter.
And now ?SA mode also.
Thanks a lot for the information, will try this when coming home:)
After this, is it possible to update the FW in the future, and still keep the options?
Best regards
Robert
Now i have permanent on all the options that was on trial, but in the keygen there is a lot more options generated. Can i use the other ones on my SVA1015x as well, or is it just AMK,EMI,TG;DMA,AMA,DTF,VNA?Only official license types are supported.
So are these models over 5yr's old?Roughly 5 with SVA1015X the first of the later HW with touch/mouse capable displays.
Since they've had new scopes lately, are there any plans for updated VNA's ? I wish there were models closer to the sds2000x+ series prices, or 1000x-e prices. Even if they are only 500MHz BW, that's plenty for all kinds of uses. And a lot more people could afford them.SVA1015X is the cheapest (ready to go) with SA/VNA capability for a little more than SDS2104X Plus cost.
Does anyone with an SVA1015X have input N-type connectors that become quite hot to the touch after about 30-45 minutes?Yes, I have that too. But a lot of measurement devices seem to get warm in order to maintain a stable temperature, so I wouldn't worry about it. Just a weird spot to get warm.
I recently received a liberated SSA3021X+
Does anyone with an SVA1015X have input N-type connectors that become quite hot to the touch after about 30-45 minutes?Yes, I have that too. But a lot of measurement devices seem to get warm in order to maintain a stable temperature, so I wouldn't worry about it. Just a weird spot to get warm.
I have a genuine SVA1032x and I have not noticed any part of it warm up, not even a little. I've had mine open to tighten the connector screws (for some reason they got loose) and I can tell you that aluminum is heavy. With that in mind, I have 20w transmitters with much less mass in the heat sync that barely gets noticeably warm, so I ask, what inside a RECEIVER needs to get that hot??? I would be concerned enough to find out what is generating the heat.
Hello everyone,Not having much luck are you ?
I recently received a liberated SSA3021X+, now I'm using it to get into the world of RF.
Agreed. And using a thermocouple or other sensor physically attached to the object is highly recommended as a thermal camera will only be accurate on matte black surfaces.I have a genuine SVA1032x and I have not noticed any part of it warm up, not even a little. I've had mine open to tighten the connector screws (for some reason they got loose) and I can tell you that aluminum is heavy. With that in mind, I have 20w transmitters with much less mass in the heat sync that barely gets noticeably warm, so I ask, what inside a RECEIVER needs to get that hot??? I would be concerned enough to find out what is generating the heat.
I wouldn't.
Both you, Spacehen and Self Bias discuss this "temperature" without stating any temperature measured by thermometer.
"Measuring" temperature by touching it with a hand is highly subjective and two different people will have wildly different perception what "really warm is".
Not to mention that a room all this is happening in can vary by 10 °C and nobody takes that into account.
To many people pain threshold for touching hot objects is mere 50°C, and some will report 40-45°C as very hot. Some will go into 60°C sauna and say "it is warm but it's OK"...
So before getting all crazy about it, a measurement should be done. If connectors are at 70°C than something is wrong...
Grr...So you snatched it from under my nose. ;)
Your screenshots mean nothing as sweeps are not seen as Ref levels and Scale are not applicable to the signals used. Turn the measurement table Off so Sweep and Span settings are visible and just use Markers and their values displayed on the screen.
Press Preset (check is is set to Factory Default) and show us some aweeps with the trace visible.
Then I would like to see the Mode menu if all the SVA options are actually available.
Does the System info display a SN# and model ?
Both you, Spacehen and Self Bias discuss this "temperature" without stating any temperature measured by thermometer.
Good. :phew:Then I would like to see the Mode menu if all the SVA options are actually available.
Does the System info display a SN# and model ?
I could take a screenshot, but I already checked that: It has a SN# and all options are permanently active.
Then just a screenshot with the Mode menu showing please., there you go:
So, I tried a few things.Thanks.
All normal. But switching to Harmonics instantly yields the same problem:
(https://www.eevblog.com/forum/testgear/siglent-sva1015x-1-5ghz-spectrum-vector-network-analyzer-(coming)/?action=dlattach;attach=2013938;image)
With Harmonics it seems the sweep is mostly above the current Reference level so wind it up some to see the whole trace.That will not help sadly; the measured value is always above the reference level. Even with the reference set to +30 dBm, it will then read +36 to +38.
Harmonics tests works as expected.
Not tested.Harmonics tests works as expected.
So you don't get unreasonably high values in Harmonics measurement when setting the RBW < 30 Hz or the detector to anything but Pos Peak?
Show us some detailed results displaying your findings.
Ok, analyzer behavior is a bit weird, but does it make any sense to measure harmonics with 10 Hz RBW?
I tried with mine several times, at several different frequency ranges, and although it would often let me enter whatever RBW I wanted, occasionally it would tell me RBW out of range and stop me when inputting anything under 30Hz. I think the bug is that it don't always stop you from entering it.
Did you verify that the tracking generator was off? With it turned on, RBW will always be limited to 30 Hz.Yes, it was off. I was using an external sig gen.
I wouldn't consider an SVA1032x the go-to tool for repairing something sophisticated enough to need to see a harmonic down in the natural weeds, so whats the point here?
The reason is that Siglent is not completely honest about the phase noise in its specifications. They state a phase noise of -98dBc at 1 GHz. My device just manages that, but the rest of the spectrum is much worse. Look at the attached screenshot.
Yes indeed, your phase noise is better.What is Samp detection in your screenshots ? Never used it :-//
Now you have an SSA3021X+ and I'm not sure if it has the same hardware as an SVA1032X.Instead be sure it does.
What is Samp detection in your screenshots ? Never used it :-//It is very common to use sample detection in noise measurements. I believe this is even 'a must' by convention.
Yet you still compared apples with oranges. :-//What is Samp detection in your screenshots ? Never used it :-//It is very common to use sample detection in noise measurements. I believe this is even 'a must' by convention.
I just forgot about it during the 2nd measurement.
Yet you still compared apples with oranges. :-//
Of course the FPL1007 is more expensive but don't forget that my SSA3032X-R has the same hardware as the 3075X-R. Then you no longer talk about entry-level models. Especially not if you buy a few expensive options.
Let's consider for a moment the consequences of bad phase noise.Is there a reason you use a different RBW when comparing the R&S to the Siglent?
Is there a reason you use a different RBW when comparing the R&S to the Siglent?
There is some extra noise going on at the left few divisions of the display. Is this still not fixed?
Yet you still compared apples with oranges. :-//
That's quite a bold statement, so to say.
But I have done a new measurement for you in which you will see that the noise values with the sample detector are better than with a peak measurement. The choice of the detector is therefore important.
In my post where I used a peak measurement (by mistake) I actually put the SSA3032X-R at a disadvantage and yet it was even better than the SVA1032X.
There is some extra noise going on at the left few divisions of the display. Is this still not fixed?
Of course the FPL1007 is more expensive but don't forget that my SSA3032X-R has the same hardware as the 3075X-R. Then you no longer talk about entry-level models. Especially not if you buy a few expensive options.
While we are comparing numbers, let's put thing in perspective...
Even SSA3075X-R is still half the price of FPL1007... And that is for FPL1007 base price without any options, that are, by the way, even more expensive on R&S. For instance: 40 MHz BW realtime option on R&S cost 4000 € alone! While it is actually free on SSA3075X-R now...
For 4000€ (only for realtime option on R&S) you can buy ALL the options for SSA3075X-R, that includes a set of nearfield EMC probes...
So my comment on this is : " 2-3x times more expensive R&S SA actually has slightly better performance than SSA3075X-R?
Really? Well it effing better have better performance for the price you pay for it..."
It is still a Chinese company whose name is suspiciously similar to Agilent and they do their best to copy expensive Western items. There are so many examples that show that Siglent is far from having things in order. You notice it in the documentation and you notice it in the errors in the firmware.
In general, it looks like the -R may be either a superior design or given more attention, possibly a few better components.It's not quite that simple.
In general, it looks like the -R may be either a superior design or given more attention, possibly a few better components.It's not quite that simple.
X-R models certainly use different HW to most SSA/SVA models but not all.
We can clearly see evidence of this in SSA+, SVA and SSA X-R datasheets.
With some study we can identify 3 HW versions that cover all models from 1.5 - 7.5 GHz.
Currently only have my SNA5004A 4.5 GHz unit to test.....In general, it looks like the -R may be either a superior design or given more attention, possibly a few better components.It's not quite that simple.
X-R models certainly use different HW to most SSA/SVA models but not all.
We can clearly see evidence of this in SSA+, SVA and SSA X-R datasheets.
With some study we can identify 3 HW versions that cover all models from 1.5 - 7.5 GHz.
I'm sure you're right but what I'm really after is visibility to how well it calibrates and how stable that calibration is. In spite of videos and web reviews, there isn't much at the VNA end and nothing at the cal end. A few more looks at how well it behaves up to 7+ GHz would also be helpful.
Hey, you could be an industry leader. Just get Siglent to support you and your US and worldwide counterparts with a virtual try out online. You select the instrument which is then connected to a matrix of sources, loads, reflectances, etc. Our internet bandwidths are high enough to support that fairly well today.Similar has been asked for before as we have used other equipment via the inbuilt webserver of a beta tester in Oregon.
This is OT from the phase noise but I guess this is a MT (multi topic) thread :)
In the process of downsizing and eliminating several higher end gear, I'm headed toward either an SVA1075X or possibly a -R of the SSA series. One thing I have not seen on this blog, flog me if wrong, is the SOLT performance of these units. In general, it looks like the -R may be either a superior design or given more attention, possibly a few better components.
Can you post an image of your SOLT cal with the load performed last, in LOG form. How stable is it over an hour or two (assuming analyzer has been warmed for an hour)?
Higher end VNAs are fairly rock solid. The early FieldFox wanders like crazy. I'm scared sh-less over the four leaf clovers out of the Siglents Smith chart prior to cal. I am seeing better than -60dB on the bench VNA and the FF.
I would like to think that Siglent's converters and dynamic range are good enough to get down there but have seen NO plots of such.
Thanks IM3 ! That's exactly what I was looking for. I'm not asking you to run it again, but have you noticed that it remains stable for some time?
Yes, -50dB is a decent number, especially if it's repeatable and stable. For small chip and pcb antenna work, the final result is usually well above -30dB and can be a lot worse but acceptable.
My other units are PNA and early FieldFox, both of which may be gone with retirement downsizing. They are about 20dB (at 10kHz IFBW) lower but the FieldFox drifts a bit, while the PNA is rock solid (should be at 55lbs / 25kg). The difference must be in the directional couplers.
And of course, this is where Siglent's 38dB to 40dB corrected directivity comes from.
I've recently been lurking the blog doing my due diligence in search for a viable SA/ VNA for amateur radio use, and use as a hobbyist. I was about to pull the trigger on a SVA1015X when IM3's post came up. I would like to mention that I do appreciate the level of expertise in this forum.
I had considered the SSA3032X-R, but do I really need a RTSA, probably not. Is it a a really cool function, yes it is! Looking at the data provided by IM3 the 3032X-R is back in the radar.
I'd hate to invest the extra capital just for the RTSA feature if all of the other performance characteristics are relatively similar between the SVA1015X, and the SSA3032X-R.
From the most recent information in the thread, I want to verify by consensus that the SSA3032X-R does indeed have better phase noise characteristics and better HW than the SVA-1015X?
Thank you for the consideration of my question.
I've recently been lurking the blog doing my due diligence in search for a viable SA/ VNA for amateur radio use, and use as a hobbyist. I was about to pull the trigger on a SVA1015X when IM3's post came up. I would like to mention that I do appreciate the level of expertise in this forum.
I had considered the SSA3032X-R, but do I really need a RTSA, probably not. Is it a a really cool function, yes it is! Looking at the data provided by IM3 the 3032X-R is back in the radar.
I'd hate to invest the extra capital just for the RTSA feature if all of the other performance characteristics are relatively similar between the SVA1015X, and the SSA3032X-R.
From the most recent information in the thread, I want to verify by consensus that the SSA3032X-R does indeed have better phase noise characteristics and better HW than the SVA-1015X?
Thank you for the consideration of my question.
As always a lot of things depends on budget, so I can't help with that, but I can explain how I came to my choice.
For now there are 2 main RF designs of interest within the Siglent spectrum analyzers. (The 3rd choice is the 5000 series and too expensive)
The better RF design of the 2 can be recognized in the documentation by a DNAL of -165 dBm.
The simpler RF designs have a more worse DNAL value. More like -156 dBm and -161dBm.
I think all beter ones are the SVA1075X, SSA3075X-PLUS, SSA3032X-R, SSA3050X-R, SSA3075X-R.
Now what I had already described in an earlier post is that the simpler RF design of my SVA1032X has led to poor phase noise in a large part of the spectrum. In any case, worse than -98dBc that Siglent specifies at 1GHz.
The better RF design doesn't have that problem and have the same phase noise across the entire spectrum.
To see how physically different the designs are, I advise you to view 2 links.
For the more simple RF design, watch a video from EEVBlog here:
https://www.youtube.com/watch?v=HxBcQDooAYs (https://www.youtube.com/watch?v=HxBcQDooAYs)
Click here for a look at the better RF design. (Scroll to reply 53 & 54)
https://www.eevblog.com/forum/testgear/siglent-ssa3000x-r-57-5ghz-real-time-spectrum-analyzer/?all (https://www.eevblog.com/forum/testgear/siglent-ssa3000x-r-57-5ghz-real-time-spectrum-analyzer/?all)
As far as I know the only photos on the internet of this version. (Thanks to TV84 on this blog)
How I made a choice which analyzer to buy:
Of the SVA series, only the SVA1075X is suitable, but then you pay €9200.
Of the SSA X-PLUS series, only the SSA3075X-PLUS is suitable, but then you pay €7875. But it has no VNA function. I thought that could be upgraded, but it would require some tinkering.
The SSA3032X-R is the cheapest of the SSA X-R series and costs €4830, but you can expand it to 7.5 GHz for free, including all options with the key generator that you can download here.
http://tpcg.io/_SV2SRE (http://tpcg.io/_SV2SRE) (Many thanks to the guys who made this script)
In my opinion, the SSA3032X-R is the device that gives you the most for the least money.
And real time is nice to have, really.
My SVA1032X : Firmware_V3.2.2.6.0R7 original Version with all Options
yellow: 10MHz, blue: 200MHz, red: 500MHZ, green: 1GHz
(Attachment Link)
Discovered the following two items I wanted to leave somewhere regarding usage.https://www.eevblog.com/forum/testgear/siglent-sna5000x-two-and-four-port-vnas-coming/ (https://www.eevblog.com/forum/testgear/siglent-sna5000x-two-and-four-port-vnas-coming/)
1. the SVA now supports saving in SNP, or S parameter format. It saves as S1P. This is very handy for bringing the VNA sweep of a network to an external program for massaging. This is not in Siglent docs nor in firmware revision guide.
With a quality cable attached and calibrated to the end, attached a small antenna eval board for a response plot, with or without markers. When saved as STA or CAL, neither one could load back the working state and screen appearance.
2. Enter the CSA save format. This is not in Siglent docs nor firmware revision guide. CSA saves calibration AND state combined. When you load a CSA file, you will return to where you left off, with cal in place, entire setup in place including markers, etc.
Also, if you find something that is not in Siglent docs, look at their manual for their higher end model, the SNA5032A.
If there is a thread dedicated to usage, please move this there.
Nice looking units.Totally next level and some.
And they do either directly load or import Agilent/Keysight cal kit files. With full editing and custom kits. The basics of this should have been carried into the SVA.Reasonably sure they do but need get mine out to confirm ....when I get a chance, please bare with me....
On a converted SVA1032X, MARKER FUNCTION does not exist in Windows remote control mode.Not sure I see what you do. :-//
If you establish markers for bandwidth of an antenna for instance, they will be visible on the remote screen, as will MARKER FN but as soon as you leave that soft menu, you can't get back to it.
Thank you to anyone who can verify and turn it in.
Siglent released a new firmware version
Version SVA1000X Firmware_V3.2.2.6.2R5 (Release Date 06.28.24 ).
Siglent released a new firmware version - did someone apply this version to an upgraded SSA? Any issues ?
Version SVA1000X Firmware_V3.2.2.6.2R5 (Release Date 06.28.24 ).
merci
Siglent released a new firmware version - did someone apply this version to an upgraded SSA? Any issues ?
Version SVA1000X Firmware_V3.2.2.6.2R5 (Release Date 06.28.24 ).
merci
I applied it just now, seems to work fine.
As I mentioned in the SSA3000x/plus ThreadAll/any boot settings are from flash memory.
What worries me a little is this function:
"Save the configuration every 60 seconds, and load it when Power On is turned Last".
Why does it have to be saved every 60 seconds?
My fear is that if it is saved in flash, the memory cycles can be greatly reduced.
Flash memories also have a limited number of writes.
I once had a similar problem with a router that was constantly writing to the flash
and then stopped working after half a year.
After that, the option was removed from the firmware because there were too many failures.
Has Siglent provide any further information about what this is all about?
All/any boot settings are from flash memory.
Not that I know exactly but I strongly suspect the FW settings save changes are to reduce/minimize flash memory wear, however this is not an ongoing problem as I have yet to encounter it with any of the SVA/SSA models.
Maybe I misunderstood you, but I don't see that saving every 60 seconds reduces/minimizes writing to the flash memory.I'll see what I can find out.....if not immediately, in a few weeks when I visit HQ.
Quite the opposite.
I'm also interested to know more about the issue with writing to the flash every 60 seconds. This doesn't seem like a good idea.Let's revisit the FW release notes:
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.