BTW, anyone has done a calibration/adjustment on SDG2042X?
Run the internal self cal and enjoy your 40 120 MHz AWG.
Do you experience any improvement after doing the "self cal"?
The service manual says that one should only run self-cal after having done a calibration of the internal feedback channel. But that latter calibration requires Python scripts which, I believe, are unavailable to end users. So, can we run a meaningful calibration?
BTW, anyone has done a calibration/adjustment on SDG2042X?
Run the internal self cal and enjoy your 40 120 MHz AWG.
Do you experience any improvement after doing the "self cal"?
If the AWG meets the Accuracy and Output Flatness specs listed under Output Characteristics on P8 of the datasheet I leave it alone.
https://int.siglent.com/products-document/5.html?DId=25/
Just a note to say, took delivery of an SDG2042X, *cough* followed everything in John95's 14-step process *cough* and all worked very well. This was done on FW: 2.01.01.23R8 factory supplied version.
Then verified the performance with a scope = 120MHz goodness.
Then today I did a plain old regular firmware upgade to 2.01.01.35R3B2 and all went smoothly + 120MHz performance still remains.
Posting should anyone find this useful if, like me thought there was a chance of going from a liberated 23R8 to 35R3B2 would reverse the mod... it doesn't appear to.
All the best,
Dan
I had the same experience as you as mentioned in the
hack thread. However I found that the peak-to-peak voltage decreases with frequency, soon after 40 MHz.
I've found a bug in FM modulation. With an external 10MHz reference clock, 10MHz output signal, FM frequency of 10mHz, triangle modulation waveform and a frequency deviation of 5mHz the output signal will slowly (a few ns per hours) phase shift in respect to the external reference.
Hi guys
I have SDG2042x hacked to SDG2122x, firmware: 2.01.01.35R3B2, hardware 02-02-00-40-00.
Does your SDG2000x copy have the front panel knob working intermittently? I spin for a few seconds and it's ok, then it stops working for a second. The knob doesn't respond at all when turning faster. If this is a software error, it definitely needs to be corrected.
Hi so I just upgraded my spd3303x-e with the FW I found on page 9 from tv84
https://www.eevblog.com/forum/testgear/siglent-ads-firmware-file-format/200/In 2 weeks I'm getting the SDG2042X. What page should I go to, for the main procedure people have been using, so I can study up ?
As for really learning how this stuff works, and getting into hardware hacking, (I have a BusPirate on the way), what should I do, learn python or some C language ?
I'm buying 1 of these in 15 days if people go to work in Ontario
I can't wait, then I'll try and upgrade it. I could just afford the 2082, but thank Siglent for making either near my budget.
It seems that with the last firmware update I applied, the undocumented LXI SCDP (screendump) command stopped working. Can anyone else confirm? I know this used to work because I have lots of screendumps from my SDG2000X. I use the same program to do screen capture from all of my Siglent devices.
It's not documented in
https://siglentna.com/wp-content/uploads/dlm_uploads/2019/12/SDG_Programming-Guide_PG02-E04A.pdfCan someone confirm whether this was explicitly removed? There's nothing in the release notes about it.
I‘m new in the SDG2xxx owners club for a week . After dealing for month with the weaknesses of
the cheap (but for the money not that bad) Feeltec 6900 I decided to stop all efforts for further improvements
and ordered a SDG2042x with Welectron in Germany.
It came with the latest firmware and with a little service and a prepared thumb drive it improved itself into
a SDG2122x
It‘s worth mentioning that the telnet access with Putty didn‘d work but with Debian in the new Windows Linux system environment.
It‘s childish but the first thing I tried was to set up my own FM station(for some minutes).
Searching for a empty frequency around 100 MHz, deviation of 75kHz and modulation extern by my iPod
with „Stairway to heaven“. Antenna 75 cm wire. And it works! That was a thing I wanna do for 50 years
Don‘t bash me for that but it was a thing that has to be done....
Great experiment!
This made me think of the Mr. Microphone toy that was sold in the US back in the Eighties
It‘s childish but the first thing I tried was to set up my own FM station(for some minutes).
Searching for a empty frequency around 100 MHz, deviation of 75kHz and modulation extern by my iPod
with „Stairway to heaven“. Antenna 75 cm wire. And it works! That was a thing I wanna do for 50 years
Shit! Much smaller and so much cheaper than the SDG
And battery powered as well
Thanks for this funny commercial! But I think you got it
Waynes World, Waynes world, party time excellent!!!
I like this movie! Especially the Bohemian Rhapsody performance
And this:
I've found a bug in FM modulation. With an external 10MHz reference clock, 10MHz output signal, FM frequency of 10mHz, triangle modulation waveform and a frequency deviation of 5mHz the output signal will slowly (a few ns per hours) phase shift in respect to the external reference.
I recently got a Siglent 2042X (I'm using it to test a Time Interval Counter that I'm building), and I noticed that the 1Hz output isn't exactly 1Hz (referenced to the 10MHz clock output). I don't have my notes handy, but it was off a few tenths of a uHz (micro Hertz). The minimum frequency steps seemed to come in two sizes, one 2x the other. The frequency generated was always within the specified 1uHz, but wasn't exact.
This is the behavior I would expect from a binary DDS (Direct Digital Synthesis) / NCO (Numerically Controlled Oscillator), where no matter how large the numerator, the power-of-two denominator doesn't allow certain ratios to be generated. It's not a problem or a bug, since the unit does meet its specs, but it is interesting to note. It's also nice to see that the 10ns resolution of my Time Interval Counter lets me quickly measure these frequency relationships -- with a typical gated frequency counter I would have had to wait about twelve days for even a clue that the frequencies weren't exact.
External 10Mhz reference
My SDG2042X doesn't seem to remember the External setting for the reference Clock upon power-on. Is there a way to make it stick between reboots? Works fine otherwise, detecting signal presence/loss but it's rather annoying when it pukes out its own clock on the line.
Running latest firmware ver.
External 10Mhz reference
My SDG2042X doesn't seem to remember the External setting for the reference Clock upon power-on. Is there a way to make it stick between reboots? Works fine otherwise, detecting signal presence/loss but it's rather annoying when it pukes out its own clock on the line.
Running latest firmware ver.
Check the last firmware release notes and ensure you meet the conditions for external 10 MHz reference.
https://siglentna.com/wp-content/uploads/dlm_uploads/2019/12/SDG2000X-Firmware-Revise-History-Update-Instructions.pdfThese are for version 2.01.01.35R3B1:
5. Added an icon to indicate clock source is internal or external.
Internal: (icon) External: (icon)
External and the clock is lost: (icon)
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.Also, check you have the Power ON setting to Last (used settings).
I recently got a Siglent 2042X (I'm using it to test a Time Interval Counter that I'm building), and I noticed that the 1Hz output isn't exactly 1Hz....
Another manifestation of that: set channel 1 to 1.000000 Hz, and channel 2 to 10.0000 Mhz, then measure their ratio. It reads exactly 9 999 999:1 on my HP 53131A counter, rather than the ideal 10 000 000:1. (Test done with an SDG1062X).
Again, each channel is within spec. But this experiments highlights a side effect of "1 uHz" accuracy when generating two signals with a frequency ratio > 10
6 -- and it did have me chasing a phantom "bug" in a phase detector design before realizing what was going on :-)
I recently got a Siglent 2042X (I'm using it to test a Time Interval Counter that I'm building), and I noticed that the 1Hz output isn't exactly 1Hz....
Another manifestation of that: set channel 1 to 1.000000 Hz, and channel 2 to 10.0000 Mhz, then measure their ratio. It reads exactly 9 999 999:1 on my HP 53131A counter, rather than the ideal 10 000 000:1. (Test done with an SDG1062X).
Again, each channel is within spec. But this experiments highlights a side effect of "1 uHz" accuracy when generating two signals with a frequency ratio > 106 -- and it did have me chasing a phantom "bug" in a phase detector design before realizing what was going on :-)
I fell into the exact same trap. I was trying to qualify a time interval counter and wondered why there was a 90° phase shift every second. I went through the code at least a dozen times, checked for numerical stability, changed the whole integer math to "double" only to realize eventually that it was the generator that was acting up.
Same crap with SDG6000. Tested other generators that I've got; Rigol DG4000 is doing it correctly, same with MSO2000S integrated generator (though phase alignment isn't working accurately). DG800/900 is failing all the way, no stable phase coupling possible in current firmware version above frequency ratios of 1:3
(at lest at low frequencies), continuous drift observable. Could it be that difficult to get the math right??
I recently got a Siglent 2042X (I'm using it to test a Time Interval Counter that I'm building), and I noticed that the 1Hz output isn't exactly 1Hz....
Another manifestation of that: set channel 1 to 1.000000 Hz, and channel 2 to 10.0000 Mhz, then measure their ratio. It reads exactly 9 999 999:1 on my HP 53131A counter, rather than the ideal 10 000 000:1. (Test done with an SDG1062X).
Again, each channel is within spec. But this experiments highlights a side effect of "1 uHz" accuracy when generating two signals with a frequency ratio > 106 -- and it did have me chasing a phantom "bug" in a phase detector design before realizing what was going on :-)
I fell into the exact same trap. I was trying to qualify a time interval counter and wondered why there was a 90° phase shift every second. I went through the code at least a dozen times, checked for numerical stability, changed the whole integer math to "double" only to realize eventually that it was the generator that was acting up.
The only reason that I located this "bug" is that I had already been using a mash-up three-output clock generator for testing my Time Interval Counter design. My little clock gen uses the Silicon Labs Si5351 (on a breakout board) and an Adafruit "Trinket M0" controller, all stuffed into an Altoids tin and USB powered. The clocks are all locked to a common reference xtal, and extremely programmable with fractional PLL feedback dividers and fractional output dividers. The frequency accuracy isn't great, but the ratios are spot-on. I've also tested my design with the 10MHz and 1Hz outputs of a Trimble "Thunderbolt" GPDSO, so I knew what I was seeing was due to the Siglent, and not my design.
" Also, check you have the Power ON setting to Last (used settings). "
That was the trick! Thanks!