Panorama (RAM zoom) functionality - Revision history

Riemerg at 12:02, 21 August 2017

2017-08-21T12:02:28Z

← Older revision		Revision as of 12:02, 21 August 2017
Line 1:		Line 1:
	(available on SW version v0.0.8 and above)		(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.195.304) 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.		The SmartScope comes with 64Mbit of RAM, which is used to provide up to 4M (4.195.304) 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=		=User Graphical Interface elements=
	An example screenshot is presented below, after which the main elements will be described below.		An example screenshot is presented below, after which the main elements will be described below.
Line 42:		Line 42:
	\| Hide the Panorama \|\| Double-tap Panorama \|\| Double-click Panorama \|\| P		\| Hide the Panorama \|\| Double-tap Panorama \|\| Double-click Panorama \|\| P
	\|}		\|}

			=RAM size \| Acquisition depth=
			Once the Stop command is issued, the SmartScope transfers the full contents of its RAM to the PC. Since there is quite some data to be transfered, this can take a little while. The progress is indicated as a green overlay on top of the Panorama, which appears when you issue the Stop command and advances from left to right as the data comes in.
			<br><br>
			In case of 4MS per channel, this can take a little while; up to 8s even on the fastest systems. For this reason, the number of samples to be stored (acquisition depth) is set to 512kS by default. In order to increase/decrease this number, simply go to Menu -> System -> Acquisition depth as shown below.
			<br>
			[[File:AcqDepth.png]]

	=Help! I’m getting terribly slow refresh rates=		=Help! I’m getting terribly slow refresh rates=

Riemerg at 20:10, 1 October 2016

2016-10-01T20:10:24Z

← Older revision		Revision as of 20:10, 1 October 2016
Line 60:		Line 60:
	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:		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		*Acquisition: shows the timespan of data stored inside the RAM
	*VF Length: shows the timespan represented by the ViewFinder		*VP 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		*VP 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.		*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.

Riemerg at 07:53, 4 May 2016

2016-05-04T07:53:12Z

← Older revision		Revision as of 07:53, 4 May 2016
Line 1:		Line 1:
	(available on SW version v0.0.8 and above)		(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 10<sup>6</sup>~~) 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.		The SmartScope comes with 64Mbit of RAM, which by default is used to provide a 4M (4.195.304) 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=		=User Graphical Interface elements=
	An example screenshot is presented below, after which the main elements will be described below.		An example screenshot is presented below, after which the main elements will be described below.

Esteevens at 22:24, 27 January 2016

2016-01-27T22:24:21Z

← Older revision		Revision as of 22:24, 27 January 2016
Line 1:		Line 1:
	(available on SW version v0.0.8 and above)		(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 10<sup>6</sup>) 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.		The SmartScope comes with 64Mbit of RAM, which by default is used to provide a 4M (4,096 x 10<sup>6</sup>) 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=		=User Graphical Interface elements=
	An example screenshot is presented below, after which the main elements will be described below.		An example screenshot is presented below, after which the main elements will be described below.

Esteevens at 14:05, 27 January 2016

2016-01-27T14:05:23Z

← Older revision		Revision as of 14:05, 27 January 2016
Line 1:		Line 1:
	(available on SW version v0.0.8 and above)		(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 10<sup>6</sup>) 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.		The SmartScope comes with 64Mbit of RAM, which by default is used to provide a 4M (4.096 x 10<sup>6</sup>) 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=		=User Graphical Interface elements=
	An example screenshot is presented below, after which the main elements will be described below.		An example screenshot is presented below, after which the main elements will be described below.

Esteevens at 08:32, 27 January 2016

2016-01-27T08:32:23Z

← Older revision		Revision as of 08:32, 27 January 2016
Line 1:		Line 1:
	(available on SW version v0.0.8 and above)		(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 (~~4e6~~) 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.		The SmartScope comes with 64Mbit of RAM, which by default is used to provide a 4M (4.0 x 10<sup>6</sup>) 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=		=User Graphical Interface elements=
	An example screenshot is presented below, after which the main elements will be described below.		An example screenshot is presented below, after which the main elements will be described below.

Riemerg: /* Using the Panorama and ViewFinder */

2015-11-18T10:46:42Z

Using the Panorama and ViewFinder

← Older revision		Revision as of 10:46, 18 November 2015
Line 32:		Line 32:
	\| Regular Zoom out <br>(without changing ViewFinder size) \|\| Pinch main graph \|\| Mousewheel scroll on main graph \|\| Home		\| Regular Zoom out <br>(without changing ViewFinder size) \|\| Pinch main graph \|\| Mousewheel scroll on main graph \|\| Home
	\|-		\|-
	\| ViewFinder Zoom in <br>(increases ViewFinder size) \|\| Pinch Viewfinder \|\| Mousewheel scroll on ViewFinder \|\| CTRL+~~Home~~		\| ViewFinder Zoom in <br>(increases ViewFinder size) \|\| Pinch Viewfinder \|\| Mousewheel scroll on ViewFinder \|\| CTRL+End
	\|-		\|-
	\| ViewFinder Zoom out <br>(decrceases ViewFinder size) \|\| Pinch Viewfinder \|\| Mousewheel scroll on ViewFinder \|\| CTRL+~~End~~		\| ViewFinder Zoom out <br>(decrceases ViewFinder size) \|\| Pinch Viewfinder \|\| Mousewheel scroll on ViewFinder \|\| CTRL+Home
	\|-		\|-
	\| Move ViewFinder \|\| Drag ViewFinder \|\| Drag ViewFinder \|\| Ctrl+Left/Right		\| Move ViewFinder \|\| Drag ViewFinder \|\| Drag ViewFinder \|\| Ctrl+Left/Right
Line 42:		Line 42:
	\| Hide the Panorama \|\| Double-tap Panorama \|\| Double-click Panorama \|\| P		\| Hide the Panorama \|\| Double-tap Panorama \|\| Double-click Panorama \|\| P
	\|}		\|}

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

Riemerg at 10:46, 18 November 2015

2015-11-18T10:46:03Z

Riemerg at 15:59, 24 February 2015

2015-02-24T15:59:20Z

← Older revision		Revision as of 15:59, 24 February 2015
Line 32:		Line 32:
	\| Regular Zoom in <br>(without changing ViewFinder size) \|\| Pinch main graph \|\| Mousewheel scroll on main graph \|\| Home		\| Regular Zoom in <br>(without changing ViewFinder size) \|\| Pinch main graph \|\| Mousewheel scroll on main graph \|\| Home
	\|-		\|-
	\| ~~Move~~ ViewFinder \|\| ~~Drag ViewFinder~~ \|\| ~~Drag~~ ViewFinder \|\| ~~Ctrl~~+~~Left/Right~~		\| ViewFinder Zoom in <br>(increases ViewFinder size) \|\| Pinch Viewfinder \|\| Mousewheel scroll on ViewFinder \|\| CTRL+Home
	\|-		\|-
	\| ~~Increase~~ ViewFinder size \|\| Pinch Viewfinder \|\| Mousewheel scroll on ViewFinder \|\| i		\| ViewFinder Zoom in <br>(decrceases ViewFinder size) \|\| Pinch Viewfinder \|\| Mousewheel scroll on ViewFinder \|\| CTRL+End
	\|-		\|-
	\| ~~Decrease~~ ViewFinder ~~size~~ \|\| ~~Pinch Viewfinder~~ \|\| ~~Mousewheel scroll on~~ ViewFinder \|\| o		\| Move ViewFinder \|\| Drag ViewFinder \|\| Drag ViewFinder \|\| Ctrl+Left/Right
	\|-		\|-
	\| Show the Panorama \|\| Double-tap top border \|\| Double-click top border \|\| P		\| Show the Panorama \|\| Double-tap top border \|\| Double-click top border \|\| P

Riemerg at 14:28, 24 February 2015

2015-02-24T14:28:24Z

← Older revision		Revision as of 14:28, 24 February 2015
Line 28:		Line 28:
	! Keyboard		! Keyboard
	\|-		\|-
	\| Regular Zoom in <br>(without changing ViewFinder size) \|\| Pinch main graph \|\| \|\| End		\| Regular Zoom in <br>(without changing ViewFinder size) \|\| Pinch main graph \|\| Mousewheel scroll on main graph \|\| End
	\|-		\|-
	\| Regular Zoom in <br>(without changing ViewFinder size) \|\| Pinch main graph \|\| \|\| Home		\| Regular Zoom in <br>(without changing ViewFinder size) \|\| Pinch main graph \|\| Mousewheel scroll on main graph \|\| Home
	\|-		\|-
	\| Move ViewFinder \|\| Drag ViewFinder \|\| Drag ViewFinder \|\| Ctrl+Left/Right		\| Move ViewFinder \|\| Drag ViewFinder \|\| Drag ViewFinder \|\| Ctrl+Left/Right

← Older revision		Revision as of 10:46, 18 November 2015
Line 10:		Line 10:

	'''The ViewFinder'''		'''The ViewFinder'''
	<br>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.		<br>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, ~~or by~~ dragging it by mouse.		The ViewFinder can be moved across the Panorama by swiping it, dragging it by mouse, or by CTRL+Left/Right.

	'''The Trigger'''		'''The Trigger'''
Line 30:		Line 30:
	\| Regular Zoom in <br>(without changing ViewFinder size) \|\| Pinch main graph \|\| Mousewheel scroll on main graph \|\| End		\| Regular Zoom in <br>(without changing ViewFinder size) \|\| Pinch main graph \|\| Mousewheel scroll on main graph \|\| End
	\|-		\|-
	\| Regular Zoom in <br>(without changing ViewFinder size) \|\| Pinch main graph \|\| Mousewheel scroll on main graph \|\| Home		\| Regular Zoom out <br>(without changing ViewFinder size) \|\| Pinch main graph \|\| Mousewheel scroll on main graph \|\| Home
	\|-		\|-
	\| ViewFinder Zoom in <br>(increases ViewFinder size) \|\| Pinch Viewfinder \|\| Mousewheel scroll on ViewFinder \|\| CTRL+Home		\| ViewFinder Zoom in <br>(increases ViewFinder size) \|\| Pinch Viewfinder \|\| Mousewheel scroll on ViewFinder \|\| CTRL+Home
	\|-		\|-
	\| ViewFinder Zoom in <br>(decrceases ViewFinder size) \|\| Pinch Viewfinder \|\| Mousewheel scroll on ViewFinder \|\| CTRL+End		\| ViewFinder Zoom out <br>(decrceases ViewFinder size) \|\| Pinch Viewfinder \|\| Mousewheel scroll on ViewFinder \|\| CTRL+End
	\|-		\|-
	\| Move ViewFinder \|\| Drag ViewFinder \|\| Drag ViewFinder \|\| Ctrl+Left/Right		\| Move ViewFinder \|\| Drag ViewFinder \|\| Drag ViewFinder \|\| Ctrl+Left/Right
Line 43:		Line 43:
	\|}		\|}
	=Help! I’m getting terribly slow refresh rates=		=Help! I’m getting terribly slow refresh rates=
	In certain configurations, using the Panorama might result in undesirably slow ~~update~~ rates.		In certain configurations, using the Panorama might result in undesirably slow refresh rates.

	Let’s apply some 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.		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:		In case this is undesired, either:
	* Enlarge the ViewFinder using ~~‘O’~~ and afterwards Zoom in on the global timescale using ~~‘PageUp’~~		* Enlarge the ViewFinder using CTRL+Home and afterwards Zoom in on the global timescale using ‘Home’
	* Hide the Panorama using ‘P’		* Hide the Panorama using ‘P’
	=Under the hood=		=Under the hood=
	==When is the Panorama shown/hidden?==		==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 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 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 ~~occupating~~, ~~you can~~ 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.		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==		==Acquisition speed and buffer size details==
Line 61:		Line 61:
	*VF Length: shows the timespan represented by the ViewFinder		*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		*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 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.		*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.