Products > Test Equipment

The Siglent SDG2042X Thread

<< < (371/372) > >>

tautech:
Thanks David.
Will forward to Siglent HQ for their investigations.

DavidPlatt:
Thanks, much appreciated!

Please also suggest to them that they check the behavior of the GUI, when the modulation settings are being changed via SCPI.  On a couple of occasions, I switched the modulation source to ARB via SCPI, read back the status and confirmed that it had been set, but when I pressed MOD on the front panel, the status display was inconsistent.  When I went down through the menus it didn't reflect the status being read back by C1:MDWV?.  If I recall correctly, the first-level display showed that the modulation was via ARB, but when I dived into the ARB menu to look to see which modulation waveform was being used, none of the choices were highlighted!

It looks as if updating the modulation state via SCPI doesn't always set all of the internal state correctly.

KungFuJosh:

--- Quote from: DavidPlatt on November 21, 2024, 12:18:48 am ---It looks as if updating the modulation state via SCPI doesn't always set all of the internal state correctly.

--- End quote ---

Page 21 of the programming guide:


--- Quote ---COMMAND SYNTAX
<channel>:MoDulateWaVe <type>
<channel>:MoDulateWaVe <parameter>,<value>
<channel>:={C1, C2}
--- End quote ---

Did you try that way?

ETA page 24 has examples that worked for me. I'm on 38R4.

Thanks,
Josh

DavidPlatt:
The command syntax for MDWV is clear enough :-)

Unfortunately, Siglent doesn't seem to have documented the parameter names needed to select the use of a specific user-provided waveform. 

If I use the GUI to put it into modulate-via-ARB mode, and then select a waveform file I've previously downloaded, and then do a "C1:MDWV?", the generator doesn't show the waveform name, or even any indication that it's modulating using a user-provided waveform.  It does show that the modulation source is the ARB, but it shows an INDEX value (as if it was modulating from a built-in ARB waveform).

So, there appears to be a disconnect somewhere in the process.  And, the documentation is lacking.  The release notes for the firmware say that it's possible to specify which ARB waveform to use, but they don't actually say how to do that (or what the limitations on the process might be).  The programming manual doesn't seem to have been updated to reflect this capability, and I haven't found any actual examples published by Siglent (I'm certainly not too proud to copy their code!)

tautech:

--- Quote from: DavidPlatt on November 21, 2024, 05:42:53 pm ---The command syntax for MDWV is clear enough :-)

Unfortunately, Siglent doesn't seem to have documented the parameter names needed to select the use of a specific user-provided waveform. 

If I use the GUI to put it into modulate-via-ARB mode, and then select a waveform file I've previously downloaded, and then do a "C1:MDWV?", the generator doesn't show the waveform name, or even any indication that it's modulating using a user-provided waveform.  It does show that the modulation source is the ARB, but it shows an INDEX value (as if it was modulating from a built-in ARB waveform).

So, there appears to be a disconnect somewhere in the process.  And, the documentation is lacking.  The release notes for the firmware say that it's possible to specify which ARB waveform to use, but they don't actually say how to do that (or what the limitations on the process might be).  The programming manual doesn't seem to have been updated to reflect this capability, and I haven't found any actual examples published by Siglent (I'm certainly not too proud to copy their code!)

--- End quote ---
Can you confirm you're working with the latest programming manual:
Programming Guide PG02_E05C

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod