LabNation Wiki - User contributions [en]

ADC resolution - voltage dividing/multiplying stage

2017-07-15T12:22:38Z

Esteevens:

=General=
When you are using ranges (20mV/div - 100mV/div) it uses a different path than when using (200mV/div or higher), this is to reduce noise and to get more resolution. You'll always hear the relay switching in the transition between those ranges.

On each voltage range (vertical resolution in volts/div) you will have different minimum and maximum value that the scope can measure.

This depends on your current vertical offset and there is some extra room out of the screen (that is different on each range) but as general rule of thumb if a signal goes outside of the screen vertically you are probably exceeding the limits of that range and the scope is clipping the signal.

So you need to adjust the resolution and vertical offset so you can see the whole signal in the screen (vertically) if you want to measure it.

=Example for a 2V signal=

Since the main grid on the SmartScope software has 8 division and your signal is 2V that means that 200mV/div x 8 divisions = 1.6V is not enough, and that is why your voltage got clamped to 1.4V, probably your were using an offset of -3 division giving you only 7 div. x 200mV = 1.4V! so your signal was clamped to 1.4V

And in lower ranges it will be even worse, but that is the normal operation of any scope, you cannot measure larger signals than what you can fit in the screen in your current range.

=Voltage resolution=

The resolution of the scope also varies between ranges, so don't expect to see exactly the same value in each range, but they should be really close.

The resolution of the ranges is displayed in the next table:

{| class="wikitable"
! Range Max.
!Resolution Max.
!Resolution Typ.
|-
| 20 mV/div || 1.6 mV || 2 mV
|-
| 50 mV/div || 1.6 mV || 2 mV
|-
| 100 mV/div || 3.2 mV || 5 mV
|-
| 200 mV/div || 6.3 mV ||10 mV
|-
| 500 mV/div || 17 mV || 20 mV
|-
| 1 V/div ||32 mV ||50 mV
|-
| 2 V/div || 63 mV || 100 mV
|-
| 5 V/div || 157 mV || 200 mV
|-
|}

In addition to that, different ranges use different amplification so noise, temperature and small calibration errors could make also the values differ even more.

And after all, this is an 8-bits scope, it is not intended for precise voltage measurement, so you can be confident that it will give you an accuracy of arround 10% of your current volts/div but do not ask for more wink. So in 1V/div the figures will be accurate to 0.1V, and in 500mV/div to 0.05V.

Probes: x1 or x10 modus

2016-02-19T05:07:57Z

Esteevens:

First the specs you'll get using the probes at 1X/10X with SmartScope (they are not exact, just approximate reference values):

{| class="wikitable"
!
! x1
! x10
|-
| Impedance || 1 MΩ // 100pF || 10 MΩ // 20pF
|-
| Bandwidth|| 6 MHz || 30 MHz
|-
| Max. Voltage Range || ±30 V || ±300 V
|-
| Max. Amplitude || 40Vpp || 400Vpp
|-
| Voltage Resolution (V/AdcUnit) || 2 mV || 20 mV
|-
|}

Let's talk about all that...

'''Impedance:''' This will be the load you'll apply to the point under test. When you are probing a node you are adding a 1/10MΩ resistor to ground in that point and a parallel capacitor of 100/20pF to ground too. That means that a 10X probe will be better because it'll have less impact on the actual signal in the circuit.

'''Bandwidth:''' To put it simply, the bandwidth tells you from what frequency up the signals will be 'smoothed'. If you are working with sine waves you'll only get attenuation, but for square or any complex signal they need to be 1/10 of the bandwidth or slower, otherwise you'll see distorted waveforms. So what this means? At 1X you'll be limited to 600Khz square signals but at 10X you can go up to 3Mhz square signals without significant deformation. So once again a 10X probe will be better. The probe is actually 60Mhz but the scope has 30Mhz bandwidth (You actually always want your probe to be of higher bandwidth that the scope otherwise you'll get double attenuation).

By the way, all this does not mean that you cannot see signals faster than 3Mhz, you can, actually you can see signals all the way to 50Mhz (half of the sampling frequency), but after 3Mhz you'll start to notice the loss of higher frequency components, meaning edges will not look as sharp as they actually are.Around 20Mhz or so you'll see everything like a sine wave, and after that you'll get into aliasing problems reaching the limits of the sampling rate.

'''Max. Voltage Range:''' Since you have 10x attenuation you'll have 10x more range. So 10x probe is better again. Actually, it is a bit more complex, because the probe could be damaged if the voltage and the frequency are both high (and it could also damage the scope). Without entering in details this is a simple table of the safe voltage ranges with the probe in 10x:

{| class="wikitable"
! Frequency
! Voltage Range
|-
| 0 - 20 kHz|| ±200 V / 120 VAC
|-
| 20 kHz - 200 kHz|| ±100 V / 60 VAC
|-
| 200 kHz - 50 MHz|| ±25 V / 16 VAC
|-
|}

'''Max. Voltage Resolution:''' This is the minimal voltage difference that the ADC of the scope can measure (with the volts/div in the lowest ranges of course). Here 1x probe is better because due to the probe attenuation you'll have 1/10 of the resolution. But of course this will only be true in the lowest ranges, once you get to 500mv/div you'll have the same resolution using 1x or 10X probe.

'''So, long story short,''' ''a 10x probe will be better'' in all cases except two:
* When you want to measure small signals (under 2Vpp) with more resolution than 20mV.
* When you are measuring signals of 1Mhz or lower and you want to filter out high frequency noise (over 6Mhz).

Probes: x1 or x10 modus

2016-02-19T05:06:18Z

Esteevens:

First the specs you'll get using the probes at 1X/10X with SmartScope (they are not exact, just approximate reference values):

{| class="wikitable"
!
! X1
! X10
|-
| Impedance || 1 MΩ // 100pF || 10 MΩ // 20pF
|-
| Bandwidth|| 6 MHz || 30 MHz
|-
| Max. Voltage Range || ±30 V || ±300 V
|-
| Max. Amplitude || 40Vpp || 400Vpp
|-
| Voltage Resolution (V/AdcUnit) || 2 mV || 20 mV
|-
|}

Let's talk about all that...

'''Impedance:''' This will be the load you'll apply to the point under test. When you are probing a node you are adding a 1/10MΩ resistor to ground in that point and a parallel capacitor of 100/20pF to ground too. That means that a 10X probe will be better because it'll have less impact on the actual signal in the circuit.

'''Bandwidth:''' To put it simply, the bandwidth tells you from what frequency up the signals will be 'smoothed'. If you are working with sine waves you'll only get attenuation, but for square or any complex signal they need to be 1/10 of the bandwidth or slower, otherwise you'll see distorted waveforms. So what this means? At 1X you'll be limited to 600Khz square signals but at 10X you can go up to 3Mhz square signals without significant deformation. So once again a 10X probe will be better. The probe is actually 60Mhz but the scope has 30Mhz bandwidth (You actually always want your probe to be of higher bandwidth that the scope otherwise you'll get double attenuation).

By the way, all this does not mean that you cannot see signals faster than 3Mhz, you can, actually you can see signals all the way to 50Mhz (half of the sampling frequency), but after 3Mhz you'll start to notice the loss of higher frequency components, meaning edges will not look as sharp as they actually are.Around 20Mhz or so you'll see everything like a sine wave, and after that you'll get into aliasing problems reaching the limits of the sampling rate.

'''Max. Voltage Range:''' Since you have 10x attenuation you'll have 10x more range. So 10x probe is better again. Actually, it is a bit more complex, because the probe could be damaged if the voltage and the frequency are both high (and it could also damage the scope). Without entering in details this is a simple table of the safe voltage ranges with the probe in 10x:

{| class="wikitable"
! Frequency
! Voltage Range
|-
| 0 - 20 kHz|| ±200 V / 120 VAC
|-
| 20 kHz - 200 kHz|| ±100 V / 60 VAC
|-
| 200 kHz - 50 MHz|| ±25 V / 16 VAC
|-
|}

'''Max. Voltage Resolution:''' This is the minimal voltage difference that the ADC of the scope can measure (with the volts/div in the lowest ranges of course). Here 1x probe is better because due to the probe attenuation you'll have 1/10 of the resolution. But of course this will only be true in the lowest ranges, once you get to 500mv/div you'll have the same resolution using 1x or 10X probe.

'''So, long story short,''' ''a 10x probe will be better'' in all cases except two:
* When you want to measure small signals (under 2Vpp) with more resolution than 20mV.
* When you are measuring signals of 1Mhz or lower and you want to filter out high frequency noise (over 6Mhz).

Panorama (RAM zoom) functionality

2016-01-27T22:24:21Z

Esteevens:

(available on SW version v0.0.8 and above)

The SmartScope comes with 64Mbit of RAM, which by default is used to provide a 4M (4,096 x 106) sample buffer for each channel. In general, this means that whenever you stop an acquisition, you can zoom in about 1000 times on the waves currently displayed. This can be very useful in case you want to trigger on an event, and study in fine detail all causing and resulting effects which happened before or after that event.
=User Graphical Interface elements=
An example screenshot is presented below, after which the main elements will be described below.
 [[File:Panorama2.png|800px]]

'''The Panorama'''
 The Panorama is the bar shown at the top of the screen. It displays the entire contents of the RAM memory.

'''The ViewFinder'''
 The ViewFinder is the area of the Panorama corresponding to the area currently displayed on the main screen. It is highlighted on the Panorama, to give a clear '''visual indication''' of which section of the Panorama you’re currently inspecting on the main screen. This is further enhanced by the highlights underneath the Panorama, visually linking the area of the main graph to the ViewFinder.

The ViewFinder can be moved across the Panorama by swiping it, dragging it by mouse, or by CTRL+Left/Right.

'''The Trigger'''
 The position of the trigger is also shown in the Panorama. In case the trigger is outside the timespan of the main graph, this gives a quick indication of where the trigger is relative to the signal visualized in the main graph.

=Using the Panorama and ViewFinder=
Using Touch and Mouse, you can directly manipulate the element of the visual interface.
Using Keyboard, all operations acting directly on the Panorama and ViewFinder are accessed by holding the CTRL key pressed.

The following table can be used as quick reference:
{| class="wikitable"
!
! Touch
! Mouse
! Keyboard
|-
| Regular Zoom in (without changing ViewFinder size) || Pinch main graph || Mousewheel scroll on main graph || End
|-
| Regular Zoom out (without changing ViewFinder size) || Pinch main graph || Mousewheel scroll on main graph || Home
|-
| ViewFinder Zoom in (increases ViewFinder size) || Pinch Viewfinder || Mousewheel scroll on ViewFinder || CTRL+End
|-
| ViewFinder Zoom out (decrceases ViewFinder size) || Pinch Viewfinder || Mousewheel scroll on ViewFinder || CTRL+Home
|-
| Move ViewFinder || Drag ViewFinder || Drag ViewFinder || Ctrl+Left/Right
|-
| Show the Panorama || Double-tap top border || Double-click top border || P
|-
| Hide the Panorama || Double-tap Panorama || Double-click Panorama || P
|}

=Help! I’m getting terribly slow refresh rates=
In certain configurations, using the Panorama might result in undesirably slow refresh rates.

Let’s apply some simple math on the screenshot at the top of this page. The main graph is set to 200us/div, resulting in 1,2ms shown on the total screen, so you could expect up to 800 updates per second. However, notice that the full Panorama is much larger than the currently set ViewFinder: about 1%. This means that it takes 120ms to fill a new Panorama with samples! As such, the maximum refresh rate of the screen will be 8Hz.

In case this is undesired, either:
* Enlarge the ViewFinder using CTRL+Home and afterwards Zoom in on the global timescale using ‘Home’
* Hide the Panorama using ‘P’
=Under the hood=
==When is the Panorama shown/hidden?==
In case the Panorama is hidden, and you stop the acquisition of the SmartScope, the Panorama is automatically shown, inviting you to browse through the data stored in the RAM on the SmartScope. When you continue the aquisition without changing anything to the ViewFinder, the Panorama is hidden again. Other than those cases, the Panorama will not hide or show itself automatically.

In case you don't use the Panorama and want to free up the screen area it is consuming, simply press the 'P' button or double-click on the Panorama. When hiding the Panorama, the buffersize is minimized to correspond to the main graph, making sure the maximum data refresh rate is achieved.

==Acquisition speed and buffer size details==
By opening up the System measurement box at the bottom-right of the screen, you can find 4 parameters controlled by the Panorama and ViewFinder configuration:
*Acquisition: shows the timespan of data stored inside the RAM
*VF Length: shows the timespan represented by the ViewFinder
*VF Offset: shows the time offset of the ViewFinder, relative to the first sample of the Panorama
*Sample rate: the rate at which analog voltages and/or digital signals are acquired and stored inside the RAM. In case the Panorama size is set larger than 4e6 samples, the sample rate will automatically be downscaled to the optimal speed.

Panorama (RAM zoom) functionality

2016-01-27T14:05:23Z

Esteevens:

(available on SW version v0.0.8 and above)

The SmartScope comes with 64Mbit of RAM, which by default is used to provide a 4M (4.096 x 106) sample buffer for each channel. In general, this means that whenever you stop an acquisition, you can zoom in about 1000 times on the waves currently displayed. This can be very useful in case you want to trigger on an event, and study in fine detail all causing and resulting effects which happened before or after that event.
=User Graphical Interface elements=
An example screenshot is presented below, after which the main elements will be described below.
 [[File:Panorama2.png|800px]]

'''The Panorama'''
 The Panorama is the bar shown at the top of the screen. It displays the entire contents of the RAM memory.

'''The ViewFinder'''
 The ViewFinder is the area of the Panorama corresponding to the area currently displayed on the main screen. It is highlighted on the Panorama, to give a clear '''visual indication''' of which section of the Panorama you’re currently inspecting on the main screen. This is further enhanced by the highlights underneath the Panorama, visually linking the area of the main graph to the ViewFinder.

The ViewFinder can be moved across the Panorama by swiping it, dragging it by mouse, or by CTRL+Left/Right.

'''The Trigger'''
 The position of the trigger is also shown in the Panorama. In case the trigger is outside the timespan of the main graph, this gives a quick indication of where the trigger is relative to the signal visualized in the main graph.

=Using the Panorama and ViewFinder=
Using Touch and Mouse, you can directly manipulate the element of the visual interface.
Using Keyboard, all operations acting directly on the Panorama and ViewFinder are accessed by holding the CTRL key pressed.

The following table can be used as quick reference:
{| class="wikitable"
!
! Touch
! Mouse
! Keyboard
|-
| Regular Zoom in (without changing ViewFinder size) || Pinch main graph || Mousewheel scroll on main graph || End
|-
| Regular Zoom out (without changing ViewFinder size) || Pinch main graph || Mousewheel scroll on main graph || Home
|-
| ViewFinder Zoom in (increases ViewFinder size) || Pinch Viewfinder || Mousewheel scroll on ViewFinder || CTRL+End
|-
| ViewFinder Zoom out (decrceases ViewFinder size) || Pinch Viewfinder || Mousewheel scroll on ViewFinder || CTRL+Home
|-
| Move ViewFinder || Drag ViewFinder || Drag ViewFinder || Ctrl+Left/Right
|-
| Show the Panorama || Double-tap top border || Double-click top border || P
|-
| Hide the Panorama || Double-tap Panorama || Double-click Panorama || P
|}

=Help! I’m getting terribly slow refresh rates=
In certain configurations, using the Panorama might result in undesirably slow refresh rates.

Let’s apply some simple math on the screenshot at the top of this page. The main graph is set to 200us/div, resulting in 1,2ms shown on the total screen, so you could expect up to 800 updates per second. However, notice that the full Panorama is much larger than the currently set ViewFinder: about 1%. This means that it takes 120ms to fill a new Panorama with samples! As such, the maximum refresh rate of the screen will be 8Hz.

In case this is undesired, either:
* Enlarge the ViewFinder using CTRL+Home and afterwards Zoom in on the global timescale using ‘Home’
* Hide the Panorama using ‘P’
=Under the hood=
==When is the Panorama shown/hidden?==
In case the Panorama is hidden, and you stop the acquisition of the SmartScope, the Panorama is automatically shown, inviting you to browse through the data stored in the RAM on the SmartScope. When you continue the aquisition without changing anything to the ViewFinder, the Panorama is hidden again. Other than those cases, the Panorama will not hide or show itself automatically.

In case you don't use the Panorama and want to free up the screen area it is consuming, simply press the 'P' button or double-click on the Panorama. When hiding the Panorama, the buffersize is minimized to correspond to the main graph, making sure the maximum data refresh rate is achieved.

==Acquisition speed and buffer size details==
By opening up the System measurement box at the bottom-right of the screen, you can find 4 parameters controlled by the Panorama and ViewFinder configuration:
*Acquisition: shows the timespan of data stored inside the RAM
*VF Length: shows the timespan represented by the ViewFinder
*VF Offset: shows the time offset of the ViewFinder, relative to the first sample of the Panorama
*Sample rate: the rate at which analog voltages and/or digital signals are acquired and stored inside the RAM. In case the Panorama size is set larger than 4e6 samples, the sample rate will automatically be downscaled to the optimal speed.

Howto Videos

2016-01-27T08:54:41Z

Esteevens:

==SmartScope Controls==
{{#ev:youtube|feGdiQOJWHI}}

==Acquisition Overview==
{{#ev:youtube|7oYi9yIijAc}}

=== (partial) transcript ===
The system measurement box shows the length of the acquisition buffer as well as the sample rate. Right now that is 2.62ms and 100MHz. Given the memory of 4M samples, we can acquire up to 40ms without subsampling (4M samples / 100M samples per second). However this is not enabled by default as it would slow down the data refresh rate. By default the acquisition buffer is twice the size of what you see on the grid. I open the acquisition overview buffer by pressing V. The viewport is moved around by dragging the highlighted part. Moving the trigger is done by dragging the shaded part...

==Cursors and measurements==
{{#ev:youtube|rYmdZJyOu0Y}}

==Acquisition modes==
{{#ev:youtube|WKrIH7zo8M0}}

Panorama (RAM zoom) functionality

2016-01-27T08:32:23Z

Esteevens:

(available on SW version v0.0.8 and above)

The SmartScope comes with 64Mbit of RAM, which by default is used to provide a 4M (4.0 x 106) sample buffer for each channel. In general, this means that whenever you stop an acquisition, you can zoom in about 1000 times on the waves currently displayed. This can be very useful in case you want to trigger on an event, and study in fine detail all causing and resulting effects which happened before or after that event.
=User Graphical Interface elements=
An example screenshot is presented below, after which the main elements will be described below.
 [[File:Panorama2.png|800px]]

'''The Panorama'''
 The Panorama is the bar shown at the top of the screen. It displays the entire contents of the RAM memory.

'''The ViewFinder'''
 The ViewFinder is the area of the Panorama corresponding to the area currently displayed on the main screen. It is highlighted on the Panorama, to give a clear '''visual indication''' of which section of the Panorama you’re currently inspecting on the main screen. This is further enhanced by the highlights underneath the Panorama, visually linking the area of the main graph to the ViewFinder.

The ViewFinder can be moved across the Panorama by swiping it, dragging it by mouse, or by CTRL+Left/Right.

'''The Trigger'''
 The position of the trigger is also shown in the Panorama. In case the trigger is outside the timespan of the main graph, this gives a quick indication of where the trigger is relative to the signal visualized in the main graph.

=Using the Panorama and ViewFinder=
Using Touch and Mouse, you can directly manipulate the element of the visual interface.
Using Keyboard, all operations acting directly on the Panorama and ViewFinder are accessed by holding the CTRL key pressed.

The following table can be used as quick reference:
{| class="wikitable"
!
! Touch
! Mouse
! Keyboard
|-
| Regular Zoom in (without changing ViewFinder size) || Pinch main graph || Mousewheel scroll on main graph || End
|-
| Regular Zoom out (without changing ViewFinder size) || Pinch main graph || Mousewheel scroll on main graph || Home
|-
| ViewFinder Zoom in (increases ViewFinder size) || Pinch Viewfinder || Mousewheel scroll on ViewFinder || CTRL+End
|-
| ViewFinder Zoom out (decrceases ViewFinder size) || Pinch Viewfinder || Mousewheel scroll on ViewFinder || CTRL+Home
|-
| Move ViewFinder || Drag ViewFinder || Drag ViewFinder || Ctrl+Left/Right
|-
| Show the Panorama || Double-tap top border || Double-click top border || P
|-
| Hide the Panorama || Double-tap Panorama || Double-click Panorama || P
|}

=Help! I’m getting terribly slow refresh rates=
In certain configurations, using the Panorama might result in undesirably slow refresh rates.

Let’s apply some simple math on the screenshot at the top of this page. The main graph is set to 200us/div, resulting in 1,2ms shown on the total screen, so you could expect up to 800 updates per second. However, notice that the full Panorama is much larger than the currently set ViewFinder: about 1%. This means that it takes 120ms to fill a new Panorama with samples! As such, the maximum refresh rate of the screen will be 8Hz.

In case this is undesired, either:
* Enlarge the ViewFinder using CTRL+Home and afterwards Zoom in on the global timescale using ‘Home’
* Hide the Panorama using ‘P’
=Under the hood=
==When is the Panorama shown/hidden?==
In case the Panorama is hidden, and you stop the acquisition of the SmartScope, the Panorama is automatically shown, inviting you to browse through the data stored in the RAM on the SmartScope. When you continue the aquisition without changing anything to the ViewFinder, the Panorama is hidden again. Other than those cases, the Panorama will not hide or show itself automatically.

In case you don't use the Panorama and want to free up the screen area it is consuming, simply press the 'P' button or double-click on the Panorama. When hiding the Panorama, the buffersize is minimized to correspond to the main graph, making sure the maximum data refresh rate is achieved.

==Acquisition speed and buffer size details==
By opening up the System measurement box at the bottom-right of the screen, you can find 4 parameters controlled by the Panorama and ViewFinder configuration:
*Acquisition: shows the timespan of data stored inside the RAM
*VF Length: shows the timespan represented by the ViewFinder
*VF Offset: shows the time offset of the ViewFinder, relative to the first sample of the Panorama
*Sample rate: the rate at which analog voltages and/or digital signals are acquired and stored inside the RAM. In case the Panorama size is set larger than 4e6 samples, the sample rate will automatically be downscaled to the optimal speed.

Arbitrary Waveform Generator (AWG)

2016-01-03T19:20:12Z

Esteevens:

The SmartScope has an Arbitrary waveform generator, capable of generating signals between the [0V, 3.3V] voltage range at a sample rate of 100MS/s.
= AWG pin location =
The signal generated by the AWG is presented on the 3rd-left pin on the bottom row of the [[AUX_connector_pinout|'''AUX connector''']], as shown in the following image: 
[[File:AWGoutput.png|400px]] 
Please keep in mind that you always should bridge 2 wires between 2 separate devices. In this case:
* The AWG output signal
* The ground, so both devices have the same reference voltage. (0V means the same on both devices)
In the image above, you can see the AWG pin is surrounded by 2 ground pins, either of which you can use to connect to the other device.

= Configuring the AWG using pre-defined waves =
You can define your own waveforms (see below), or you can use one of the built-in signals which have been predefined in the SmartScope app. In order to do so, first open up the main menu by tapping on the LabNation logo at the bottom-left of the screen, and expand the AWG menu.
 [[File:AWG_activate.png|800px]] 
Next, select the type of predefined waveform you want the AWG to generate:
 [[File:AWG_selectWave.png|800px]] 
Configure the amplitude, offset and frequency of the wave to be generated.
 '''TIP''': Dragging a cursor down allows to fine-tune the value.
 '''NOTE''': At this point the AWG output is not yet active. You have to use the 'Upload function' button to activate the output (see further). 
 
The AWG is configurable within these limits:
{| class="wikitable"
|-
! Parameter
! Minimum value
! Maximum value
|-
| Amplitude
| 0V
| 3.3V
|-
| Offset
| 0V
| 3.3V (max amplitude will decrease accordingly!)
|-
| Frequency
| 191Hz
| 781kHz
|}
 [[File:AWG_freq.png|800px]] 
And finally : hit the 'Upload function' button, which will transfer the data to the SmartScope and '''activate''' the AWG output.
 '''NOTE''': This data upload can require up to 2 seconds, during which any acquisition of the oscilloscope or logic analyzer will pause. 
 [[File:AWG_upload.png|800px]] 
= Configuring the AWG using csv files =
'''IMPORTANT''': The app expects the CSV file to use a '''semicolon''' (;) as a field separator and a '''comma''' (,) as decimal symbol. Download one of the samples below to make sure your CSV works.
 '''NOTE1''': The CSV file '''may''' contain more than the number of samples specified in the parameters. Further samples will simply be ignored
 '''NOTE2''': This only works with a SmartScope connected. Otherwise, the side menu won't contain an AWG item
If you haven't used dropbox with the SmartScope
# Tap sidemenu > AWG > Upload from dropbox
# The app will tell you it doesn't have permission to dropbox and ask for it by sending you off to the dropbox website
# Grant access and return to the app
# The app now creates the AWG folder and will inform you that this new folder is empty.

#Generate a CSV file using the [[Media:awg_worksheet.xlsx|AWG excel worksheet]]. A sample CSV can be found for a [[Media:sine.csv|sine]] and [[Media:block.csv|block]] wave.
#Drop your CSV file in the AWG folder (<dropbox>/'''Apps'''/LabNation SmartScope/AWG) using a file manager
#In the app, tap sidemenu > AWG > Upload from dropbox
#You should now be able to choose the CSV file

== Under the hood ==
The AWG is driven by a 100MHz clock, reading out a memory containing ''up to'' 2048 samples.

{| class="wikitable"
|-
! Parameter
! Range
! Description
|-
| Samples
| 1-2048
| The number of samples used. The AWG loops on these samples. (< 0.0.8.4 had a minimum of 128 samples)
|-
| SampleStretch
| 0-255
| The number of cycles to repeat each sample
|-
| BeginData
|
| Field to indicate that from here on the sample voltage levels follow
|}

The [[Media:awg_worksheet.xlsx|AWG excel worksheet]] contains examples of how to compute these parameters.

== Sample CSV ==
<pre>
Value;Field;Description
8;Samples;The number of samples to use (later samples are ignored)
244;SampleStretch;The number of times to repeat a sample
0,1;BeginData;Data begins here
0,2;;
0,3;;
0,4;;
0,3;;
0,2;;
0,1;;
0;;
</pre>