EEVblog Electronics Community Forum
Products => Test Equipment => Topic started by: NoisyBoy on September 11, 2019, 05:51:38 pm
-
I noticed Siglent just released a new firmware update to their website today, there is a significant list of changes with the latest version:
https://siglentna.com/service-and-support/firmware-software/waveform-generators/#sdg2000x-series
1. Changed the amplitude strategy of AM modulation: The carrier stays fixed at the amplitude, regardless of the modulation setting.
2. Increased the upper limit of Harmonics number from 10 to 16.
3. Supported Multi-Device Synchronization.
4. Supported Up followed by Down Sweep mode in Linear sweep (no change for Log sweep).
5. Added an icon to indicate clock source is internal or external.
Internal: External: External and the clock is lost:
6. Changed the clock switch strategy: When the clock source is set to External and no actual external clock signal is being received, the clock source will not switch to Internal automatically but the clock icon will indicate that external clock is lost
7. Supported specifying Arb type by remote control when the modulating waveform is Arb.
8. Optimized the UI of selecting built-in arbs
9. Supported changing the unit of amplitude without any amplitude change by long pressing the "Amplitude" softkey.
10. Added "User" option under "PowerOn Setting".
11. Added "Normal" as a new UI color style.
12. Added memory space information in Store/Recall UI.
13. Optimized response of the universal knob
14. Added indicator for double function of the soft keys =>
15. Removed the warning message when parameter is set to a value beyond the limit
16. Fixed several bugs
a) [2017/04/07-92573] Digit changes when setting delay of Pulse by the knob
b) Amplitude unit “dBm” is not remembered after a reboot
I found item 10 to be very useful, it let you pick whichever profile you want instead of defaulting to Default or Last.
Item 12 gives you an idea of internal storage usage before you run out of space.
Item 14 gives the item selected a much clearer indication.
I drove the unit with a GPSDO, so item 5 and 6 are welcoming additions.
Lastly, update process is painless, it preserves the enhancements you made to the SDG.
There is no updated user manual available yet to reflect these enhancements.
-
Thanks, added to SDG2042X thread.
https://www.eevblog.com/forum/testgear/the-siglent-sdg2042x-thread/msg2681994/#msg2681994 (https://www.eevblog.com/forum/testgear/the-siglent-sdg2042x-thread/msg2681994/#msg2681994)
-
For other SDG2000X owners out there, new firmware is available. It is version 2.01.01.37R3, here are the changes:
1. Compatible with Rev.F hardware; if the hardware version is “05-xx-xx-xx-xx”, it will not support to roll back previous firmware version
2. Supported trig dual channel separated when use manual trigger.
3. Supported using another channel as the modulation source
4. Supported setting the output frequency after the completion of sweep
5. Counter add fast measurement mode
6. Changed the square waveform data used in square FM modulation
I updated my unit, the process is completely trouble free. The tinkering I did to the unit to enhance its capabilities is preserved in the new update.
BTW, thank you Siglent for adding new capabilities to the unit despite it has been around for a number of years now.
-
>> 6. Changed the square waveform data used in square FM modulation
just a warning as FM now :-- :palm: and PM now shitery as it gets :-- :-- :-- :palm:
So be aware in case having “05-xx-xx-xx-xx” HW model
Tested as +510mV & -510mV swing using 10MHz as
- FM 100 / 500Hz & 1Hz ... 100mH deviations
- PM 100 / Hz 0.005°
do you get the same as using SDG6000 model or 7000 model?
as I compared as using an $$$$ Keysight model... as now time to give up with that kind of SDG2K :palm: as complaining since years now
-
Some graphs as from a SSA2K+ and than rollback to any :palm: :palm: FW...
KS as Keysight AWG
SDG as SDH2082x AWG
-
Some graphs as from a SSA2K+ and than rollback to any :palm: :palm: FW...
Send me PM with your email as I believe we can roll it back.
-
Some graphs as from a SSA2K+ and than rollback to any :palm: :palm: FW...
KS as Keysight AWG
SDG as SDH2082x AWG
Oh that looks awful. Is that the new function, using a second channel as modulation source? The unmodulated signal is not quite clean already, but the modulated output is completely unusable.
-
Some graphs as from a SSA2K+ and than rollback to any :palm: :palm: FW...
KS as Keysight AWG
SDG as SDH2082x AWG
Oh that looks awful. Is that the new function, using a second channel as modulation source? The unmodulated signal is not quite clean already, but the modulated output is completely unusable.
I used ordinary source, also checked by Ch2 as equal behavior.... using the Ch2 source: the freq. counts only and must be on so I do not understand as you loose one channel.
Any older FW as 23R7 as 35R3B2 as R37R2 (given from support) as I check shortly is different in FM/PM faults.. :palm: :-- :--
BTW: to get rid of 37R3 (not having 05-xxx HW model) It requires a special recovery FW given from support as using an 4/8G stick :-DD
-
Some graphs as from a SSA2K+ and than rollback to any :palm: :palm: FW...
KS as Keysight AWG
SDG as SDH2082x AWG
Oh that looks awful. Is that the new function, using a second channel as modulation source? The unmodulated signal is not quite clean already, but the modulated output is completely unusable.
I used ordinary source, also checked by Ch2 as equal behavior.... using the Ch2 source: the freq. counts only and must be on so I do not understand as you loose one channel.
Any older FW as 23R7 as 35R3B2 as R37R2 (given from support) as I check shortly is different in FM/PM faults.. :palm: :-- :--
BTW: to get rid of 37R3 (not having 05-xxx HW model) It requires a special recovery FW given from support as using an 4/8G stick :-DD
Sorry, but i still do not understand :
you are getting this malfunction because you upgraded to last FW without having the "Rev.F" HW version or this apply to ALL legit instruments target ?
It still remain to understand where "Rev.F" should be checked, as HW version reported by Sytem Info menu has a numeric only format.
-
Very interesting.
This new SDG2000X_V2.01.01.37R3.ADS package has 2 packages inside:
335x_packet.zip
zynq_packet.zip
update.sh
You can see the update script attached.
So, they changed the MCU in the new HW for the now usual Zynq.
-
-snip
So, they changed the MCU in the new HW for the now usual Zynq.
So now the interiors should be complete different and maybe the Rev.F refers to this last HW release.
-
@ hpw,
That doesn't look good, was it this bad before the FW update?
Your 1st plot without any modulation also looks bad, almost as if there's a hardware problem?
This caused us to quickly do a "sanity" check on our SDG 2000X AWG, this is shown without any modulation. Our's is 02-02-00-40-00 hardware version and FW R3B2 version.
Best,
-
-snip
So, they changed the MCU in the new HW for the now usual Zynq.
So now the interiors should be complete different and maybe the Rev.F refers to this last HW release.
Yeah, the previous hardware was based on a TI AM335x based SoC, going by the boot log posted previously. Plus an additional FPGA. The Zync-7000 in the new hardware is a bit more powerful, with one or two Cortex-A9 cores and it already comes with some FPGA built-in. It's a really nice platform for test instruments, and cheap, now that it has been largely replaced by UltraScale+ devices. Siglent saw an opportunity for cost optimization. Also, TI was notoriously not able to provide chips during Chipageddon, so, they lost a design here.
-
SDG6000X and SDG7000A , 11 MHz at 100Hz modulation and 105mHz(0.105 Hz) depth of FM modulation..
BB60C, 1 Hz RBW/VBW,
When set for single tone, BB60C cannot measure phase noise of either with built in Phase noise measurements because they are both below phase noise floor of instrument
-
Here's basic result with no modulation from our SDG6000X, very similar to result from SDG2000X.
With what 2N3055 has shown and this result, definitely points to something wrong with hpw AWG, either FW and/or Hardware.
Best,
-
Here's basic result with no modulation from our SDG6000X, very similar to result from SDG2000X.
With what 2N3055 has shown and this result, definitely points to something wrong with hpw AWG, either FW and/or Hardware.
Best,
I agree. It is either defective or damaged or Hpw is doing something wrong, which I doubt, because he seems like he knows "the stuff"...
-
Just did firmware upgrade to .37R3 dated 8-31-2022 on SDG2000X and took a quick look at 10MHz output, very clean as shown before.
Best,
-
Just did firmware upgrade to .37R3 dated 8-31-2022 on SDG2000X and took a quick look at 10MHz output, very clean as shown before.
After the FW reset and upgrading again to .37R3 and in addition measure same on different place as may getting 1GHz LAN interference.
The first .37R3 setup (KS or Siglent) was just using same cable & power cable so really same basic setup.
New measurements on different place
1) square 10Mhz looks NOW clean as this gear permits
2) FM modulation:
- Using older FW releases, I had fade out's on low deviation using 100/500Hz FM modulation
- New setup looks now as good.
- Keep in mind 100 & 500 Hz with equal deviations: The side 100/500Hz levels are any different as PM (as equal)
3) PM modulation:
- 100Hz New setup looks now as good.... low deviations hardly to test while may the Siglent SSA is not able as jittery synthesizer & close in PN
- 500Hz New setup looks now (as previous FW releases) as :palm: :palm: as KS engineers did made his home works :-+
End of the story and my conclusions on Siglent & Support are made ...
Cheers
-
Just did firmware upgrade to .37R3 dated 8-31-2022 on SDG2000X and took a quick look at 10MHz output, very clean as shown before.
After the FW reset and upgrading again to .37R3 and in addition measure same on different place as may getting 1GHz LAN interference.
The first .37R3 setup (KS or Siglent) was just using same cable & power cable so really same basic setup.
New measurements on different place
1) square 10Mhz looks NOW clean as this gear permits
2) FM modulation:
- Using older FW releases, I had fade out's on low deviation using 100/500Hz FM modulation
- New setup looks now as good.
- Keep in mind 100 & 500 Hz with equal deviations: The side 100/500Hz levels are any different as PM (as equal)
3) PM modulation:
- 100Hz New setup looks now as good.... low deviations hardly to test while may the Siglent SSA is not able as jittery synthesizer & close in PN
- 500Hz New setup looks now (as previous FW releases) as :palm: :palm: as KS engineers did made his home works :-+
End of the story and my conclusions on Siglent & Support are made ...
Cheers
So after repeated questions to perform reset and again upgrade FW that you ignored and kept repeating Siglent is crap, you finally do it and, lo and behold, your AWG now works as well as Keysight (that is 4x more expensive).
From which you draw an conclusion is that Siglent support is bad.
Good news is it works well now ...
-
FW upgrade for SDG2000X with HW version 02-02-00-40-00 went smoothly. Rotary encoder works slightly better IMO ( :-+), font got slightly different (does not bother me), otherwise all functions work as before.
10MHz signal is clean as shown in posts above with noise level at ~100dB (same before and after FW update).
Previous issue with FM modulation remains - FM modulated output drifts in relation to sync output (tried various FM mod combinations, did not notice a change).
EDIT: added FM modulation drift screen shots (10MHz carrier, 50kHz FM freq with 25kHz modulation). Other FM MOD setups also result in a drift, slower or faster.
-
Hello, I want to update firmware in my SDG2042x (updated to SDG2122) hw ver 02-02-00-40-00 please help me and clarify which version of firmware can I use? currently I have 2.01.01.35R3B2, on website are two newer ... 37R3 and ...37R6 but there are description "compatible with hardware ver.F or G so it is not usable for my device?
Thank you in advance for any feedback
-
Hello, I want to update firmware in my SDG2042x (updated to SDG2122) hw ver 02-02-00-40-00 please help me and clarify which version of firmware can I use? currently I have 2.01.01.35R3B2, on website are two newer ... 37R3 and ...37R6 but there are description "compatible with hardware ver.F or G so it is not usable for my device?
Thank you in advance for any feedback
Install the latest irrespective of your HW version. There is a fix in the latest relevant to all HW versions.
https://int.siglent.com/upload_file/zip/firmware/Signal_generator/SDG2000X_V2.01.01.37R6_EN.zip
-
Yeah, I loved this latest release...
Counter dead after xxx counts as system locked up completely.. so switch off/on button helped O;)
Still a nightmare those Siglent gear.
-
Yeah, I loved this latest release...
Counter dead after xxx counts as system locked up completely.. so switch off/on button helped O;)
Still a nightmare those Siglent gear.
Thanks, that's really helpful....not !
Please write it up in detail here and attach a State file from your AWG.
https://www.eevblog.com/forum/testgear/the-siglent-sdg2042x-thread/ (https://www.eevblog.com/forum/testgear/the-siglent-sdg2042x-thread/)
TIA
-
Yeah, I loved this latest release...
Counter dead after xxx counts as system locked up completely.. so switch off/on button helped O;)
Still a nightmare those Siglent gear.
Thanks, that's really helpful....not !
Please write it up in detail here and attach a State file from your AWG.
https://www.eevblog.com/forum/testgear/the-siglent-sdg2042x-thread/ (https://www.eevblog.com/forum/testgear/the-siglent-sdg2042x-thread/)
TIA
You mean this ?
SDG2042X has open telnet port with no user name or password required.
I just connected with Putty.exe to the network IP address on port 23 and got right in with no request for a user name or password. So, I had a look around to see how the system was configured. No surprise it is Linux based running on an ARM 7 CPU. It was a bit of a surprise to see the log on message say "SDG800 project" which tells me that the SDG2000 FW is based on the SDG800 FW in some way. For everyone's reference below is a log of my poking around cleaned up and organized a little.
And how a man would detect the culprit, as second run went on past the previous hangings...
-
Yeah, I loved this latest release...
Counter dead after xxx counts as system locked up completely.. so switch off/on button helped O;)
Still a nightmare those Siglent gear.
Thanks, that's really helpful....not !
Please write it up in detail here and attach a State file from your AWG.
https://www.eevblog.com/forum/testgear/the-siglent-sdg2042x-thread/ (https://www.eevblog.com/forum/testgear/the-siglent-sdg2042x-thread/)
TIA
As I did some counter measurement on 10MHz again...
1. did hang, as running > 15 Min screen saver ... >> power off > power on cycle to get it back running
2. did change the the screen saver to 1 Minute: also hangs after hangs, sometimes the the screen activation did not runs... so as hooked up
3. disabled screen saver completely, so on magic count 935, device hooked up
Please, Can some one confirm this situation repeated hook up... as let them run without screen saver for hours :phew:
Hp
-
Could check this in the evening with my SDG2122X and Bodnar pulser
-
Hi,
Test it...
Screensaver 1min, 5min no problem.
Screensaver 15min, system hangs, only off/on will help.
Screensaver off, after 1564 counts (fast mode) system hangs, only off/on will help.
Clearly a bug.
Mine:
Firmware 2.01.01.37R2
Hardware 02-02-00-40-00
Martin
Edit:
It seems I don´t have the latest firmware installed - did you have it ?
Interesting: My firmware version seems not to exist in the revision history
@Tautech : Would be good if the systeminfo will display the hardware revision mentioned in the firmware revisions, F...G...etc.
-
Thanks for testing,
I run the latest FW, as posted on previous page with given bug.
So it looks as an old feature O;)
hp
-
Hi,
Test it...
Screensaver 1min, 5min no problem.
Screensaver 15min, system hangs, only off/on will help.
Screensaver off, after 1564 counts (fast mode) system hangs, only off/on will help.
Clearly a bug.
Mine:
Firmware 2.01.01.37R2
Hardware 02-02-00-40-00
Martin
Edit:
It seems I don´t have the latest firmware installed - did you have it ?
Interesting: My firmware version seems not to exist in the revision history
@Tautech : Would be good if the systeminfo will display the hardware revision mentioned in the firmware revisions, F...G...etc.
V2.01.01.37R6 is latest, install it. ;)
From release notes:
1.Compatible with Rev.G hardware
2.Fix the bug that the system does not respond when there is no operation for a long time after the counter is turned on
-
I know the notes, I´ve posted a pic from it.. ;)
But:
I run the latest FW, as posted on previous page with given bug.
Nevertheless I´ll update my gen and then test again.
-
As "V2.01.01.37R6 is latest, install it." did helped to fix the issue!
Hp