Products > Test Equipment
Siglent SDG1000 (aka LeCroy WaveStation) firmware updates
<< < (11/23) > >>
nixxon:

--- Quote from: commongrounder on May 02, 2013, 02:14:42 am ---MasterOfNone  Thank you for the description of the workaround using FM.  It does have the advantage of allowing any "shape" (i.e. sweep curve) to be used, although I have to say it is clunky to implement and adjust on the fly.  Also there is the issue of output triggering at the beginning of each sweep pass, which is essential for my work plans. I would prefer that Siglent correct the improper curve of the built in log sweep.
nixxon  It would be interesting to see if you could create this decade sweep curve in a CSV file that fit the 16k point record length for the SDG1000 series arb files.  Haven't messed with Easywave to see what values are used for the levels (14 bit, plus/minus 8192 levels, or plus/minus 3 volts)?

--- End quote ---

I found an old csv-file i previously have worked on and believe I found the correct format of csv-files from my old file.

 Now I have converted the data from Excel columns A and C into a new csv-file. The content looks like this:

X,CH1,
Second,Volt,
0.00000e+00,1.84271e+00,
1.00000e-03,1.84396e+00,
2.00000e-03,1.84520e+00,
3.00000e-03,1.84643e+00,
4.00000e-03,1.84767e+00,
5.00000e-03,1.84891e+00,
6.00000e-03,1.85014e+00,
7.00000e-03,1.85137e+00,
8.00000e-03,1.85260e+00,
9.00000e-03,1.85383e+00,
1.00000e-02,1.85505e+00,
1.10000e-02,1.85628e+00,
1.20000e-02,1.85750e+00,
etc. etc.

I will try the file on my SDG1020 when I get home (if I get the time today).

It is a 2.001 second log sweep from 1 to 100 Hz with 2Vpp and +1V offset. (just like the graph in my above post (page 3)) It is based on a table with 1 mS increments. (2001 values).
(you should delete the very last line ("2.00000e+00,1.00000e+00,") if absolute correct timing is needed (2.000 seconds)  :-/O )

I enclose the csv-file. If anyone would like to try it, please feel free to do so. IIRC, it must be "played back" on the AWG at a frequency of 0.5 Hz to generate the intended frequency sweep over the 2 second sample time.

At 1 Hz "playback", the frequency span would be 2 - 200 Hz
At 10 Hz "playback", the frequency span would be 20 Hz - 2 kHz
At 100 Hz "playback", the frequency span would be 200 Hz - 20 kHz
At 1 kHz "playback", the frequency span would be 2 - 200 kHz
At 1 MHz "playback", the frequency span would be 2 - 200 MHz
enjoy!

Because .csv files are not allowed, I had to change the file type to .txt. Please change the file type back to .csv before importing into your AWG.

EDIT: File removed, it didn't work as expected. It shows up on the Siglent as a strange signal with an amplitude of 8.995 Vpp and Offset of 5.497 VDC. Enclosed is a screenshot of the csv-file played back @ 1 Hz. (the sweep time looks spot on 1000 mS)
commongrounder:
rf-loop asked what issue I was having with triggering using the FM modulated method of generating a "log" (or any other type of) sweep.  The first time I tried this, the trigger output was syncing to the carrier frequency, when what I wanted was the modulation frequency.  I have discovered that I can get it to trigger on the modulation signal by being sure I set FM Dev. last in the order of setup.  So it turned out not to be a problem, as much as understanding the way the setup works.

I look forward to trying nixxons CSV file, when I get back to the shop.
nixxon:
I am trying to figure out the correct csv format for the Siglent. I saved a csv and a bmp file from my triggered Rigol DS1102E, and that csv file looked like garbage when imported into the Siglent as well. Screenshot below shows the kind of wave that was saved as csv on the scope and imported into the Siglent AWG.

The csv file starts out like this:

X,CH1,
Second,Volt,
1.80000e-01,1.76e+00,
1.80400e-01,1.48e+00,
1.80800e-01,1.44e+00,
1.81200e-01,1.04e+00,
1.81600e-01,1.04e+00,
1.82000e-01,5.60e-01,
1.82400e-01,4.80e-01,
1.82800e-01,1.20e-01,
1.83200e-01,1.20e-01,
1.83600e-01,-4.00e-02,
1.84000e-01,-1.60e-01,
1.84400e-01,-4.00e-02,
1.84800e-01,-4.00e-02,
1.85200e-01,2.00e-01,
1.85600e-01,2.80e-01,
nixxon:
I don't believe the Siglent is broken (yet). I loaded a home made test signal (csv-file named TEK_CAL3.csv) that I made a while back to generate a test pattern on my AWG to adjust the display geometry on some old Tektronix CROs. This file loads and runs like a charm on the Siglent AWG. Strange. I will have to study these files some more. I enclose the test file (with the file type changed temporarily from .csv to .txt), if anyone else would like to use it or troubleshoot with me.

It starts with a spike of 1.5 Vpp, followed by 9 spikes of 1.0 Vpp. The output from the Siglent of this file is perfect on both the X and Y scale. I will leave a Rigol screenshot for you to see as well.

The test file starts like this:

X,CH1,
Second,Volt,
0.00000e+00,1.50000e+00,
1.00000e-06,1.50000e+00,
2.00000e-06,0.00000e+00,
3.00000e-06,0.00000e+00,
4.00000e-06,0.00000e+00,
5.00000e-06,0.00000e+00,
6.00000e-06,0.00000e+00,
7.00000e-06,0.00000e+00,
8.00000e-06,0.00000e+00,
9.00000e-06,0.00000e+00,
1.00000e-05,0.00000e+00,
1.10000e-05,0.00000e+00,
1.20000e-05,0.00000e+00,
1.30000e-05,0.00000e+00,
1.40000e-05,0.00000e+00,
1.50000e-05,0.00000e+00,
1.60000e-05,0.00000e+00,
commongrounder:
nixxon Did you try including the header information?  Adding a header with the 1000 point record length to your TEK3 file allowed it to open in Easywave.  If you can get it to open and display as expected there, then it should work in the generator.  Here is a header from a typical CSV file for the SDG1000 series (typos and all!):

data lenth,16384
frequency,1000.000000000
amp,6.000000000
offset,0.000000000
phase,0.000000000




xpos,value

The xpos and value statements were at the top of the x and y columns on all of the Siglent csvs I looked at.  Just change the "data lenth," to the number of points in your file.
Navigation
Message Index
Next page
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod