Demodulation and decoding is part of digital modulation analysis.
I think, there is no confusion... and nobody judges here if something is wrong or right...
Anyway, the statistic Trace with decoding samples in MA mode is somewhat useless, if no recording and saving is available.
And everybody likes the "pay one get three", right?
Nonsense, show a universal spectrum analyzer even much more expensive which has such a recording option...
In SSA+/SVA you have all the modulation information you need and the filters you need for analysis. One disadvantage is the high CPU load and the GUI response slower with a larger sample buffer - as shown in the video.
You just need to know how to use it - really no decoded data analysis is needed for modulation analysis (these are useful for communication protocol analysis etc.).
The limitation is the number of symbols per second which results from the fact that it is not an RT spectrum analyzer (therefore it has limited bandwidth). Even if it had more bandwidth, you still have a problem with timeslots used on e.g. cellular networks, so this decoded data would be useless. On the other hand, I have shown that the SSA+/SVA can modulation analyze both one UMTS variant and three LTE variants.
If you want to decode data cheaply, I suggest you buy some SDR like USRP. I use my own USRP to decode data on all types of cellular networks. However, the USRP, due to its inferior RF path, is less suitable for modulation analysis.
For consolation, I will add that in the equipment (R&S FSWP) in the pictures (photos of measurements of the amateur DMR repeater made last year) I also do not have such an option (Capability to record decoded data)
All fine my friend, no need to get upset
We are all here to learn from each other... thank you for your lessons
I tried to decode this is what it gives
For 2G we will say that it is OK
For 3G even though the bandwidth is 4 MHz it doesn't seem to decode anything.
mount -o remount,rw /usr/bin/siglent/firmdata0
cd /usr/bin/siglent/firmdata0
mv nsp_data_b1x nsp_data_b1
cd /usr/bin/siglent/usr/backup
mv nsp_data_bx nsp_data_b
sync && reboot
Summarizing the collected information
Script to run:
https://www.online-python.com/PX3v0J8nbs
Is there a way to cross flash a 3000x+ with firmware V3.2.2.5.1R1? I might have jumped the gun a bit by updating all the way to the newest version. If I try to go back to the V3.2.2.5.0 release with the tv84 hex mod, it just says "Update Failed!" after attempting to cross flash.
If he take this options everything is fine.
Is there a way to cross flash a 3000x+ with firmware V3.2.2.5.1R1? I might have jumped the gun a bit by updating all the way to the newest version. If I try to go back to the V3.2.2.5.0 release with the tv84 hex mod, it just says "Update Failed!" after attempting to cross flash.
Are you saying that you did a downgrade to SSAX+ V3.2.2.5.0 and then a crossflash (with the "hex mod") and it failed? If so, that is interesting. If not, first do the downgrade.
You need to check what your current ID is. You can do that using telnet. On the SSA-XP models, there is a SCPI command to activate telnet if I remember correctly. Also, you can edit and change the ID (described in the initial crossgrade instructions).
I guess there is no change from Prod_ID in V3.2.2.5.0 to V3.2.2.5.1R1. Maybe Siglent is stopping people from upgrading by checking FW version...
If I'm in the mood, I'll create a "hex mod" for V3.2.2.5.1R1.
<?xml version="1.0" encoding="UTF-8"?>^M
<nsp_upgrade_info_root>^M
<device>^M
<upgrade_static_id>11411</upgrade_static_id>^M
<upgrade_start_id>11400</upgrade_start_id>^M
<upgrade_end_id>11499</upgrade_end_id>^M
</device>^M
</nsp_upgrade_info_root> ^M
^M
If I'm in the mood, I'll create a "hex mod" for V3.2.2.5.1R1.
<?xml version="1.0" encoding="UTF-8"?>
<nsp_trends_info_root>
<device>
<language>english</language>
<pid>0x1301</pid>
<vid>0xf4ec</vid>
<product_type_1>SVA1032X</product_type_1>
<manufacturer>Siglent</manufacturer>
<Support_Touch_Flag>1</Support_Touch_Flag>
<Support_VXI11_Flag>1</Support_VXI11_Flag>
<file_prefix>CP_</file_prefix>
</device>
</nsp_trends_info_root>
2) edit /usr/bin/siglent/config/NSP_config_upgrade_info.xml to change ProductID:
replace
<upgrade_static_id>11411</upgrade_static_id>
with
<upgrade_static_id>11403</upgrade_static_id>
Wrong move. BTW, move to the hack thread.