Author Topic: Siglent SVA1015X 1.5GHz Spectrum & Vector Network Analyzer  (Read 30527 times)

0 Members and 1 Guest are viewing this topic.

Online tautech

  • Super Contributor
  • ***
  • Posts: 15356
  • Country: nz
  • Taupaki Technologies Ltd. NZ Siglent Distributor
    • Taupaki Technologies Ltd.
Re: Siglent SVA1015X 1.5GHz Spectrum & Vector Network Analyzer (Coming)
« Reply #75 on: June 29, 2018, 12:35:57 am »
Does the VNA option include the calibration KIT?
Apparently not. They're separate items in my price list.
Avid Rabid Hobbyist
 

Offline simone.pignatti

  • Frequent Contributor
  • **
  • Posts: 313
  • Country: it
Re: Siglent SVA1015X 1.5GHz Spectrum & Vector Network Analyzer (Coming)
« Reply #76 on: June 29, 2018, 05:54:32 am »
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."
Technical Support
 

Offline hendorog

  • Super Contributor
  • ***
  • Posts: 1368
  • Country: nz
Re: Siglent SVA1015X 1.5GHz Spectrum & Vector Network Analyzer (Coming)
« Reply #77 on: June 29, 2018, 06:00:18 am »
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."

I think that it probably means:  "...can be used as a replacement of 85032B up to 1.5 GHz..."


 

Online TheSteve

  • Supporter
  • ****
  • Posts: 2923
  • Country: ca
  • GHz
Re: Siglent SVA1015X 1.5GHz Spectrum & Vector Network Analyzer (Coming)
« Reply #78 on: June 29, 2018, 06:00:25 am »
The Keysight 85032B is rated to 6 GHz though, so how is a 3.5 GHz kit a replacement for it?
VE7FM
 

Offline TK

  • Super Contributor
  • ***
  • Posts: 1069
  • Country: us
  • I am a Systems Analyst who plays with Electronics
Re: Siglent SVA1015X 1.5GHz Spectrum & Vector Network Analyzer (Coming)
« Reply #79 on: June 29, 2018, 06:06:52 am »
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?
 

Online tautech

  • Super Contributor
  • ***
  • Posts: 15356
  • Country: nz
  • Taupaki Technologies Ltd. NZ Siglent Distributor
    • Taupaki Technologies Ltd.
Re: Siglent SVA1015X 1.5GHz Spectrum & Vector Network Analyzer (Coming)
« Reply #80 on: June 29, 2018, 07:48:05 am »
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.
From the manual:
https://www.siglentamerica.com/wp-content/uploads/dlm_uploads/2018/06/SVA1000X_UserManual_UM0701X_E01A.pdf

In SA mode:
2.6.4.6 Calibration
Set calibration related items. There are three calibration states, factory calibration, user
calibration, and no calibration. The user calibration status is displayed in green font at the top
left corner of the screen. Enter the sub-menu; you can make the appropriate choice.
1. Calibration
Calibrating with the specified mechanical calibration requires three loads: open, short, and
match. Calibration data is saved as user calibration data.
2. Ecal
Use the optional SIGLENT electronic calibration unit for calibration. Calibration data is saved
as user calibration data.
3. Cal kit
Specifies the calibration kit used for mechanical calibration.
4. Clear
Clear user calibration data.

In VNA mode:
2.6.5.5 Calibration
Set calibration related items. This function is only available when the measurement item is S11.
There are three calibration states, factory calibration, user calibration, and no calibration. The
user calibration status is displayed in green font at the top left corner of the screen. Enter the
sub-menu; you can make the appropriate choice.
1. 1-Port Cal
Calibrating with the specified mechanical calibration requires three loads: open, short, and
match. Calibration data is saved as user calibration data.
2. Response (Through)
When operating, connect the port 1 and port 2 of the analyzer with an optional Through
Adapter. The normalization operation moves the measurement reference plane to both ends of
the Through Adapter. This function is only available when the measurement item is S21. Enter
the normalized submenu to make the appropriate selection.
3. Ecal (not available)
Use the optional SIGLENT electronic calibration kit for calibration. Calibration data is saved as
user calibration data.
4. Clear
Clear user calibration data.
5. Cal kit
Specifies the calibration kit used for mechanical calibration.
 F503ME:Type-N 50Ω 3 GHz Cal Kit (Siglent)
 85032F:Type-N 50Ω 9 GHz Cal Kit (KeySight)
6. Modify Cal kit (not available)
Use user defined calibration kit

« Last Edit: June 29, 2018, 08:06:34 am by tautech »
Avid Rabid Hobbyist
 

Online PA0PBZ

  • Super Contributor
  • ***
  • Posts: 3986
  • Country: nl
Re: Siglent SVA1015X 1.5GHz Spectrum & Vector Network Analyzer (Coming)
« Reply #81 on: June 29, 2018, 07:57:45 am »
Looks to me that this is only to tell the SA what calibration set to use: Factory, User or None. I don't think you can enter individual parameters.
Keyboard error: Press F1 to continue.
 

Offline TK

  • Super Contributor
  • ***
  • Posts: 1069
  • Country: us
  • I am a Systems Analyst who plays with Electronics
Re: Siglent SVA1015X 1.5GHz Spectrum & Vector Network Analyzer (Coming)
« Reply #82 on: June 29, 2018, 12:40:20 pm »
6. Modify Cal kit (not available)
Use user defined calibration kit
Seems to me that Siglent released an unfinished firmware with the SVA1015X. Waiting for a full review and teardown.
 

Online EEVblog

  • Administrator
  • *****
  • Posts: 29250
  • Country: au
    • EEVblog
Re: Siglent SVA1015X 1.5GHz Spectrum & Vector Network Analyzer
« Reply #83 on: June 30, 2018, 08:39:02 am »
Serial U-Boot output:

Code: [Select]
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
« Last Edit: June 30, 2018, 08:56:09 am by EEVblog »
 
The following users thanked this post: klaus11

Online PA0PBZ

  • Super Contributor
  • ***
  • Posts: 3986
  • Country: nl
Re: Siglent SVA1015X 1.5GHz Spectrum & Vector Network Analyzer
« Reply #84 on: June 30, 2018, 08:42:47 am »
Quote
Copying Linux from USB to RAM...
** Bad device usb 0 **
** Bad device usb 0 **

 >:D

It can boot from USB...
Keyboard error: Press F1 to continue.
 

Offline hendorog

  • Super Contributor
  • ***
  • Posts: 1368
  • Country: nz
Re: Siglent SVA1015X 1.5GHz Spectrum & Vector Network Analyzer
« Reply #85 on: June 30, 2018, 08:47:22 am »
Listening for VNC connections on TCP port 5900

 

Online EEVblog

  • Administrator
  • *****
  • Posts: 29250
  • Country: au
    • EEVblog
Re: Siglent SVA1015X 1.5GHz Spectrum & Vector Network Analyzer
« Reply #86 on: June 30, 2018, 08:48:12 am »
Plug in a keyboard and you get

Code: [Select]
[  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

Shutdown is just:

Code: [Select]
before sleep 0.1S
sleep 0.5S
shut down 
[00]
 
The following users thanked this post: klaus11

Online EEVblog

  • Administrator
  • *****
  • Posts: 29250
  • Country: au
    • EEVblog
Re: Siglent SVA1015X 1.5GHz Spectrum & Vector Network Analyzer
« Reply #87 on: June 30, 2018, 08:53:29 am »
Umm, it's dumping out license strings...  :o
 

Online PA0PBZ

  • Super Contributor
  • ***
  • Posts: 3986
  • Country: nl
Re: Siglent SVA1015X 1.5GHz Spectrum & Vector Network Analyzer
« Reply #88 on: June 30, 2018, 09:03:45 am »
Umm, it's dumping out license strings...  :o

Probably only working with the right serial # anyway.
Keyboard error: Press F1 to continue.
 

Offline bson

  • Supporter
  • ****
  • Posts: 1540
  • Country: us
Re: Siglent SVA1015X 1.5GHz Spectrum & Vector Network Analyzer
« Reply #89 on: July 01, 2018, 12:57:03 pm »
Listening for VNC connections on TCP port 5900
Now, that's pretty neat if it actually works!!!
 

Offline taydin

  • Frequent Contributor
  • **
  • Posts: 380
  • Country: tr
Re: Siglent SVA1015X 1.5GHz Spectrum & Vector Network Analyzer
« Reply #90 on: July 01, 2018, 05:15:25 pm »
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 :)
Real programmers use machine code!

My hobby projects http://mekatronik.org/forum
 

Offline joeqsmith

  • Super Contributor
  • ***
  • Posts: 5562
  • Country: us
Re: Siglent SVA1015X 1.5GHz Spectrum & Vector Network Analyzer
« Reply #91 on: July 01, 2018, 05:35:06 pm »
First I've seen this thread.  Watched their video from 4 days ago.   Nice looking unit.   Maybe I can replace my old HP8754A.   
How electrically robust is your meter?? https://www.youtube.com/channel/UCsK99WXk9VhcghnAauTBsbg
 

Offline Neganur

  • Supporter
  • ****
  • Posts: 1114
  • Country: fi
Re: Siglent SVA1015X 1.5GHz Spectrum & Vector Network Analyzer
« Reply #92 on: July 01, 2018, 08:00:11 pm »
[...]
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 it's easier to day that anything that exceeds its bandwidth is out... there are quite a few ISM bands below 1500 MHz.
Lots of M2M (machine to machine, do I dare say IoT) uses the 865MHz/915MHz band for example, I'd imagine the VNA is sufficient for antenna measurements.
 

Offline joeqsmith

  • Super Contributor
  • ***
  • Posts: 5562
  • Country: us
Re: Siglent SVA1015X 1.5GHz Spectrum & Vector Network Analyzer
« Reply #93 on: July 01, 2018, 08:02:41 pm »
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 :)

Just a few home projects I have shown on this site where I would have used it:

I am currently working on an active HV wideband differential probe that I could use it on. 

Designing custom made wideband HV single ended passive probes.
Redesigning the UNI-T UT210E current probe to increase it's bandwidth from 3KHz to 100KHz.
Designing your own HV differential probe.
Redesigning the Tektronix P6042 to increase it's bandwidth from 50MHz to about 100MHz. 

Looks like they support National Instruments, a must have.   
How electrically robust is your meter?? https://www.youtube.com/channel/UCsK99WXk9VhcghnAauTBsbg
 

Online tautech

  • Super Contributor
  • ***
  • Posts: 15356
  • Country: nz
  • Taupaki Technologies Ltd. NZ Siglent Distributor
    • Taupaki Technologies Ltd.
Re: Siglent SVA1015X 1.5GHz Spectrum & Vector Network Analyzer
« Reply #94 on: July 01, 2018, 08:30:58 pm »
@ joeqsmith
So does this instrument interest you more that the existing SSA3000X models ?
Avid Rabid Hobbyist
 

Offline joeqsmith

  • Super Contributor
  • ***
  • Posts: 5562
  • Country: us
Re: Siglent SVA1015X 1.5GHz Spectrum & Vector Network Analyzer
« Reply #95 on: July 01, 2018, 10:32:26 pm »
@ joeqsmith
So does this instrument interest you more that the existing SSA3000X models ?

Yes. 

I've thought about getting an 8753 but they are getting fairly old now themselves.  Then finding all the parts to put one together.  I looked at Copper Mountain a couple years ago.    With the help of Labview, the 8754A still does the basics for my higher frequency projects.   
How electrically robust is your meter?? https://www.youtube.com/channel/UCsK99WXk9VhcghnAauTBsbg
 
The following users thanked this post: tautech

Online tautech

  • Super Contributor
  • ***
  • Posts: 15356
  • Country: nz
  • Taupaki Technologies Ltd. NZ Siglent Distributor
    • Taupaki Technologies Ltd.
Re: Siglent SVA1015X 1.5GHz Spectrum & Vector Network Analyzer
« Reply #96 on: July 01, 2018, 10:45:18 pm »
Thanks Joe, nice looking bits of old HP.  :)
Member hendorog who's much better at this RF stuff than I will get the SVA I have coming for some tests and comparison against a HPAK VNA he has, so watch for his findings in the next week or so.
Avid Rabid Hobbyist
 

Online EEVblog

  • Administrator
  • *****
  • Posts: 29250
  • Country: au
    • EEVblog
Re: Siglent SVA1015X 1.5GHz Spectrum & Vector Network Analyzer
« Reply #97 on: July 02, 2018, 09:30:45 am »
Was playing with it today shooting a teardown video. Seemingly fairly basic VNA capability compared with the USB ones with all their bells and whistles, but probably going to very usable for lots of apps. Shame that everything is optional extra though. Even the cal kit is like $360 or something.
 

Online EEVblog

  • Administrator
  • *****
  • Posts: 29250
  • Country: au
    • EEVblog
Re: Siglent SVA1015X 1.5GHz Spectrum & Vector Network Analyzer
« Reply #98 on: July 04, 2018, 06:21:29 am »
In the middle of the teardown video, not there yet, but thought I'd post a preliminary teardown block comparison with the SSA3000
Not seeing much in the way of VNA hardware yet. Seems to be a lower frequency implementation of the SSA3000 as you'd expect, with IF ADC in the RF block this time instead of external.



 
The following users thanked this post: hendorog, klaus11

Online EEVblog

  • Administrator
  • *****
  • Posts: 29250
  • Country: au
    • EEVblog
Re: Siglent SVA1015X 1.5GHz Spectrum & Vector Network Analyzer
« Reply #99 on: July 04, 2018, 06:38:47 am »
And the tracking gen comparison

 
The following users thanked this post: thm_w, electricForce, hendorog, klaus11


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf