Hello,
When using the Agilent 33522B, I have noticed that using SOUR:FUNC:ARB {} to select a new waveform from volatile memory caues the offset and amplitude settings return to default values of 0V and 100mV. I can then set the desired amplitude and offset, but my device under test cannot withstand the temporary jump to the default values.
I am using the SOUR:DATA:ARB command over GPIB to first create the waveforms in volatile memory. Is there a way to specify the metadata (amplitude, offset, etc.) along with the waveform so that the output does not return to defaults when selecting a new waveform?
This was not an issue for older 33522A models, for which the current metadata was retained when selecting a new waveform. From the manual:
"In firmware revisions 1.12 and before, the instrument did not update waveform metadata (sample rate, voltage
range, and filter setting) when switching from one arbitrary waveform to another. The new arbitrary waveform
adopted the metadata of the waveform already in memory. Therefore, an arbitrary waveform designed to play at one
voltage range, sample rate, and filter setting (as specified in the waveform’s metadata) was changed to another set of
metadata. After firmware revision 1.12, arbitrary waveforms load any metadata present in the arbitrary waveform file,
so that they play the way they previously played."
I would actually prefer using the older firmware, unless there is a simple workaround for this issue. Would it be possible to obtain an older version of the firmware (1.12 or earlier) and run it on a model 33522B?
Thanks in advance for any help.
When using the Agilent 33522B, I have noticed that using SOUR:FUNC:ARB {
I am using the SOUR:DATA:ARB command over GPIB to first create the waveforms in volatile memory. Is there a way to specify the metadata (amplitude, offset, etc.) along with the waveform so that the output does not return to defaults when selecting a new waveform?
This was not an issue for older 33522A models, for which the current metadata was retained when selecting a new waveform. From the manual:
"In firmware revisions 1.12 and before, the instrument did not update waveform metadata (sample rate, voltage
range, and filter setting) when switching from one arbitrary waveform to another. The new arbitrary waveform
adopted the metadata of the waveform already in memory. Therefore, an arbitrary waveform designed to play at one
voltage range, sample rate, and filter setting (as specified in the waveform’s metadata) was changed to another set of
metadata. After firmware revision 1.12, arbitrary waveforms load any metadata present in the arbitrary waveform file,
so that they play the way they previously played."
I would actually prefer using the older firmware, unless there is a simple workaround for this issue. Would it be possible to obtain an older version of the firmware (1.12 or earlier) and run it on a model 33522B?
Thanks in advance for any help.
There was a a switch in operational philosophy there, which lead to the changes your seeing.
The forum won't let me attache rev 1.11 file because it is too large. I will try and get it on an FTP server you can access tomorrow. I will warn you rev 1.11 was pretty buggy, but if it works for your application great.
Another possible solution to your problem, which wouldn't require rolling back the firmware, would be to use sequencing for your arbitrary waveforms. There are no discontinuities or offset changes while switching waveforms in a sequence. Sequencing would be a good solution if you know what order your waveforms are going to be played. Let me know if you are interested in trying sequencing and I can help you build a sequence with your waveforms.