My understanding is that:
Rev.F hardware is hardware version “05-xx-xx-xx-xx”
(A-0, B-1, C-2, D-3, E-4, F-5, ...)
My understanding is that:
Rev.F hardware is hardware version “05-xx-xx-xx-xx”
(A-0, B-1, C-2, D-3, E-4, F-5, ...)
Ok, if this is confirmed, mine instrument is a "Rev.C" HW : "
02-07-00-40-00"
So i'm out this release, a pity because the feature to use the second channel as modulation source it would have been very useful for me.
Ok, if this is confirmed, mine instrument is a "Rev.C" HW : "02-07-00-40-00"
So i'm out this release, a pity because the feature to use the second channel as modulation source it would have been very useful for me.
Why? It says it's compatible with hardware rev. F and you can't downgrade with that rev. F. It doesn't say it's incompatible with other hardware revs.
As I've said
here the FW can be flashed in any HW version because it contains a package for the different HW's.
Don't know if that new capability is only present with the new MCU.
Also, can't understand how a FW that was packaged in August 31st takes 4 months to release publicly...
Why? It says it's compatible with hardware rev. F and you can't downgrade with that rev. F. It doesn't say it's incompatible with other hardware revs.
How do you read this statement ?
-snip
Release notes
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
I read "Compatible with Rev.F hardware", in my book is equal to "not compatible with HW Revisions different from F".
Now the subsequent question : where the **** or what the **** is the HW Rev. ?
System info reports a sequence of 5 numbers, no letters ...
I flashed the new firmware to my improved SDG2042x and managed to then go back to the previous version without apparent issue.
I have hw: 02-01-00-40-00 and went from 2.01.01.35R3B2 to 2.01.01.37.R3 and back to 2.01.01.35R3B2.
It seemed to go both ways no issue - screenshots attached.
(edit - second pic didn't take)
I flashed the new firmware to my improved SDG2042x and managed to then go back to the previous version without apparent issue.
I have hw: 02-01-00-40-00 and went from 2.01.01.35R3B2 to 2.01.01.37.R3 and back to 2.01.01.35R3B2.
It seemed to go both ways no issue - screenshots attached.
(edit - second pic didn't take)
So the mystery deepens
Sorry if I appear a dumb, but ... the modulation defect is for all HW versions or what ...
New firmware for SDG2000X models, as reported by NoisyBoy in this thread:
https://www.eevblog.com/forum/testgear/siglent-sdg2000x-firmware-hardware-software-versions/
Version: V2.01.01.37R3
39MB
https://int.siglent.com/upload_file/zip/firmware/Signal_generator/SDG2000X_V2.01.01.37R3_EN.zip
Release notes (edited)
Also 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
Supported trig dual channel separated when use manual trigger.
Supported using another channel as the modulation source
Supported setting the output frequency after the completion of sweep
Counter add fast measurement mode
Changed the square waveform data used in square FM modulation
Some clarification arrived from Tech support.
All HW versions accept this new V2.01.01.37R3 firmware and it is only Rev.F hardware; if the hardware version is “05-xx-xx-xx-xx”, it will not support to roll back previous firmware version.
So V2.01.01.37R3 can be installed into
any SDG2000X instrument.
I flashed the new firmware to my improved SDG2042x and managed to then go back to the previous version without apparent issue.
I have hw: 02-01-00-40-00 and went from 2.01.01.35R3B2 to 2.01.01.37.R3 and back to 2.01.01.35R3B2.
It seemed to go both ways no issue - screenshots attached.
(edit - second pic didn't take)
So the mystery deepens
Sorry if I appear a dumb, but ... the modulation defect is for all HW versions or what ...
It is not clear if it exists at all. The person in question has a bit of trouble communicating details and while there is certainly something going on, it is not clear to me what is wrong.
https://www.eevblog.com/forum/testgear/siglent-sdg2000x-firmware-hardware-software-versions/msg4574527/#msg4574527Look at my post later for 6000 and 7000 AWGs... They look better than that Keysight.
There is also post from Mike from his 2000 that looks a lot like mine.
So I'm not sure...
My HW version is 02-01-00-40-00, but the new firmware is not installed. The process starts: "10%-20%-90%" and right after that "Update failed" message.
I tried from different flash drives and copying the firmware to the internal memory - the result is invariably the same. What could be the problem?
upd: I solved the problem by resetting all the settings to default. After that, the firmware installed normally.
My HW version is also 02-01-00-40-00.
I try to reset all settings to default but the new firmware fails to install.
Can you please detail how you reset all settings?
Utils-System-Default. Then immediately launch the firmware update from the flash drive.
The SDG2000X is generally very capricious when updating firmware, and in the past often refused to accept new firmware. In all other cases, it works flawlessly.
Latest firmware for SDG2000X has the following updates:
Release notes
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
Supported trig dual channel separated when use manual trigger.
Supported using another channel as the modulation source
Supported setting the output frequency after the completion of sweep
Counter add fast measurement mode
Changed the square waveform data used in square FM modulation
Has anyone tried the Counter add fast measurement mode ? What does it do?
A real shame they didn't add more digits to frequency setting...
Roger
I just applied the last firmware and now my SDG2042X's encoder response has deeply improved
I just applied the last firmware and now my SDG2042X's encoder response has deeply improved
That's great to hear. I thought it was a hardware problem (i.e crappy encoder).
I have an sdg1032x and the encoder really bugs me. Hopefully, they'll release an update for the sdg1000x seriers too.
A real shame they didn't add more digits to frequency setting...
Roger
Looks like they did add a couple of digits to Frequency ...
(edit: not sure why the pic is upside down - try again)
Anyone notice the small change in display font ?
Not sure what that's about.
@tautech
Maybe the font is smaller to accommodate more digits as @djadeski noted? I have to find where this was causing a problem for
me, but looks like its better.
The SCPI command 'MODE INDEPENDENT' and 'MODE PHASE-LOCKED' seem to work now. Don't know if I checked it for 35R3B2.
Haven't played with the modulation yet.
Anyone notice the small change in display font ?
Not sure what that's about.
I can confirm, the new font would be nice but size it's too small...
@tautech
Maybe the font is smaller to accommodate more digits as @djadeski noted? I have to find where this was causing a problem for
me, but looks like its better.
One can only hope! However, if the surplus characters, "itude", are dropped, this leaves sufficient space to accommodate the full complement of 14 digits to show the frequency to the claimed 1uHz resolution right up to 100MHz without the need to reduce the font size, just like my cheap FeelTech FY6600-60M 'toy' function generator does (only meaningful of course when modded with an OXCO that can be locked to a high grade external reference
).
Anyone notice the small change in display font ?
Not sure what that's about.
Yes the font size is reduced and there is lots of space on the screen for a bigger font. Hard to read especially digits like 3. As a distributor you have contacts at Siglent tech support. Could you ask them to increase font size back to what it used to be? Should be an easy fix.
Thanks - Roger
I also confirm that the font has been reduced and is quite a bit harder to read. I am going back to the previous 35R3B2 and will wait for a new update.
Latest firmware for SDG2000X has the following updates:
Release notes
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
Supported trig dual channel separated when use manual trigger.
Supported using another channel as the modulation source
Supported setting the output frequency after the completion of sweep
Counter add fast measurement mode
Changed the square waveform data used in square FM modulation
Has anyone tried the Counter add fast measurement mode ? What does it do?
A real shame they didn't add more digits to frequency setting...
Roger
I’ve found that this firmware update improves the frequency counter’s measurement update speed at the cost of making the counter unusable. I’ll explain.
The upside: The frequency counter now has two settings: “slow” and “fast”. The “slow” setting updates the counter’s screen at about 1 Hz, and the “fast” setting updates at around 4 Hz. This is a definite improvement over the previous, non-configurable update speed of about 0.5 Hz.
The downside: This firmware update has introduced a bug in which the longer the counter is both enabled and actively displayed on the screen, the less responsive the device’s user interface becomes (in terms of the latency between a key press and its effect). Eventually, the device becomes completely unresponsive and requires its power to be cycled in order to restore responsiveness. The degradation in responsiveness is directly proportional to the counter’s update speed setting—setting the counter to “fast” will degrade responsiveness faster than setting the counter to “slow”, to the point where one can observe key press latency increasing with each passing second.
This bug makes the frequency counter feature of this device nearly useless. Note that I have a “liberated” SDG2042X with Rev. C hardware (hardware version 02-02-00-40-00). Has anyone else encountered this pathological behavior?
Side note: the new ability to use the other channel as a modulation source is glorious! (Or, at least, appears to be so during my limited testing so far.)
I’ve found that this firmware update improves the frequency counter’s measurement update speed at the cost of making the counter unusable. I’ll explain.
The upside: The frequency counter now has two settings: “slow” and “fast”. The “slow” setting updates the counter’s screen at about 1 Hz, and the “fast” setting updates at around 4 Hz. This is a definite improvement over the previous, non-configurable update speed of about 0.5 Hz.
The downside: This firmware update has introduced a bug in which the longer the counter is both enabled and actively displayed on the screen, the less responsive the device’s user interface becomes (in terms of the latency between a key press and its effect). Eventually, the device becomes completely unresponsive and requires its power to be cycled in order to restore responsiveness. The degradation in responsiveness is directly proportional to the counter’s update speed setting—setting the counter to “fast” will degrade responsiveness faster than setting the counter to “slow”, to the point where one can observe key press latency increasing with each passing second.
This bug makes the frequency counter feature of this device nearly useless. Note that I have a “liberated” SDG2042X with Rev. C hardware (hardware version 02-02-00-40-00). Has anyone else encountered this pathological behavior?
Side note: the new ability to use the other channel as a modulation source is glorious! (Or, at least, appears to be so during my limited testing so far.)
I'm having exactly the same issue and I was wondering if nobody else had experienced this problem with the latest firmware. When using the frequency counter, first the device starts to feel unresponsive/laggy and at the end the user interface freezes... My hardware is 02-01-00-40-00.
I contacted with support a couple of days ago and they asked me to send my device as it might be a faulty device, but I pointed out that if I downgrade the firmware to previous version everything worked fine, so it should be a software problem. Hopefully they are trying the reproduce the issue with the latest firmware version and fix it on a future firmware. I will send them your post also for reference.