<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://gwyscope.net/wiki/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://gwyscope.net/wiki/feed.php">
        <title>Gwyscope documentation</title>
        <description>open hardware SPM controller with advanced sampling support</description>
        <link>https://gwyscope.net/wiki/</link>
        <image rdf:resource="https://gwyscope.net/wiki/lib/exe/fetch.php?media=logo.png" />
       <dc:date>2026-04-09T04:57:41+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://gwyscope.net/wiki/doku.php?id=akiyama&amp;rev=1740466608&amp;do=diff"/>
                <rdf:li rdf:resource="https://gwyscope.net/wiki/doku.php?id=amkpfm&amp;rev=1740475577&amp;do=diff"/>
                <rdf:li rdf:resource="https://gwyscope.net/wiki/doku.php?id=cafm&amp;rev=1740466768&amp;do=diff"/>
                <rdf:li rdf:resource="https://gwyscope.net/wiki/doku.php?id=contact&amp;rev=1740488824&amp;do=diff"/>
                <rdf:li rdf:resource="https://gwyscope.net/wiki/doku.php?id=fmkpfm&amp;rev=1740476634&amp;do=diff"/>
                <rdf:li rdf:resource="https://gwyscope.net/wiki/doku.php?id=gui&amp;rev=1743508498&amp;do=diff"/>
                <rdf:li rdf:resource="https://gwyscope.net/wiki/doku.php?id=guistart&amp;rev=1740482226&amp;do=diff"/>
                <rdf:li rdf:resource="https://gwyscope.net/wiki/doku.php?id=hwbox&amp;rev=1740490890&amp;do=diff"/>
                <rdf:li rdf:resource="https://gwyscope.net/wiki/doku.php?id=hwboxcon&amp;rev=1740490999&amp;do=diff"/>
                <rdf:li rdf:resource="https://gwyscope.net/wiki/doku.php?id=hwboxserver&amp;rev=1740491052&amp;do=diff"/>
                <rdf:li rdf:resource="https://gwyscope.net/wiki/doku.php?id=hwboxsrv&amp;rev=1740491020&amp;do=diff"/>
                <rdf:li rdf:resource="https://gwyscope.net/wiki/doku.php?id=hwboxtest&amp;rev=1740491036&amp;do=diff"/>
                <rdf:li rdf:resource="https://gwyscope.net/wiki/doku.php?id=hwdsp&amp;rev=1740490857&amp;do=diff"/>
                <rdf:li rdf:resource="https://gwyscope.net/wiki/doku.php?id=hwperif&amp;rev=1740564947&amp;do=diff"/>
                <rdf:li rdf:resource="https://gwyscope.net/wiki/doku.php?id=hwperifardu&amp;rev=1742821631&amp;do=diff"/>
                <rdf:li rdf:resource="https://gwyscope.net/wiki/doku.php?id=hwperifpico&amp;rev=1740643082&amp;do=diff"/>
                <rdf:li rdf:resource="https://gwyscope.net/wiki/doku.php?id=hwperifthor&amp;rev=1742819820&amp;do=diff"/>
                <rdf:li rdf:resource="https://gwyscope.net/wiki/doku.php?id=hwsetup&amp;rev=1740490874&amp;do=diff"/>
                <rdf:li rdf:resource="https://gwyscope.net/wiki/doku.php?id=hwstart&amp;rev=1740557102&amp;do=diff"/>
                <rdf:li rdf:resource="https://gwyscope.net/wiki/doku.php?id=hwsvnup&amp;rev=1740491071&amp;do=diff"/>
                <rdf:li rdf:resource="https://gwyscope.net/wiki/doku.php?id=lift&amp;rev=1740486252&amp;do=diff"/>
                <rdf:li rdf:resource="https://gwyscope.net/wiki/doku.php?id=lua&amp;rev=1740489408&amp;do=diff"/>
                <rdf:li rdf:resource="https://gwyscope.net/wiki/doku.php?id=mfm&amp;rev=1747061103&amp;do=diff"/>
                <rdf:li rdf:resource="https://gwyscope.net/wiki/doku.php?id=qm&amp;rev=1743165266&amp;do=diff"/>
                <rdf:li rdf:resource="https://gwyscope.net/wiki/doku.php?id=ramp&amp;rev=1740490256&amp;do=diff"/>
                <rdf:li rdf:resource="https://gwyscope.net/wiki/doku.php?id=save&amp;rev=1740498657&amp;do=diff"/>
                <rdf:li rdf:resource="https://gwyscope.net/wiki/doku.php?id=scanpath&amp;rev=1740487145&amp;do=diff"/>
                <rdf:li rdf:resource="https://gwyscope.net/wiki/doku.php?id=settings&amp;rev=1740487265&amp;do=diff"/>
                <rdf:li rdf:resource="https://gwyscope.net/wiki/doku.php?id=sideband&amp;rev=1750923081&amp;do=diff"/>
                <rdf:li rdf:resource="https://gwyscope.net/wiki/doku.php?id=sidebar&amp;rev=1743160240&amp;do=diff"/>
                <rdf:li rdf:resource="https://gwyscope.net/wiki/doku.php?id=start&amp;rev=1740491510&amp;do=diff"/>
                <rdf:li rdf:resource="https://gwyscope.net/wiki/doku.php?id=tapping&amp;rev=1740488834&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://gwyscope.net/wiki/lib/exe/fetch.php?media=logo.png">
        <title>Gwyscope documentation</title>
        <link>https://gwyscope.net/wiki/</link>
        <url>https://gwyscope.net/wiki/lib/exe/fetch.php?media=logo.png</url>
    </image>
    <item rdf:about="https://gwyscope.net/wiki/doku.php?id=akiyama&amp;rev=1740466608&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-02-25T06:56:48+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>akiyama</title>
        <link>https://gwyscope.net/wiki/doku.php?id=akiyama&amp;rev=1740466608&amp;do=diff</link>
        <description>Sefl-sensing probes (PLL)</description>
    </item>
    <item rdf:about="https://gwyscope.net/wiki/doku.php?id=amkpfm&amp;rev=1740475577&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-02-25T09:26:17+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>amkpfm</title>
        <link>https://gwyscope.net/wiki/doku.php?id=amkpfm&amp;rev=1740475577&amp;do=diff</link>
        <description>AM KPFM

Kelvin probe force microscopy is based on minimization of the electrostatic force between conductive
AFM probe and sample by applying a voltage that compensates contact potential difference.
The simplest realisation is AM-KPFM where probe is kept out of the contact to the sample, AC voltage is applied on it and DC offset is used to minimized the mechanical oscillations caused by electrostatic forces at the AC voltage frequency. In Gwyscope we use the fast output 2, where the AC+DC signa…</description>
    </item>
    <item rdf:about="https://gwyscope.net/wiki/doku.php?id=cafm&amp;rev=1740466768&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-02-25T06:59:28+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>cafm</title>
        <link>https://gwyscope.net/wiki/doku.php?id=cafm&amp;rev=1740466768&amp;do=diff</link>
        <description>Conductive Atomic Force Microscopy</description>
    </item>
    <item rdf:about="https://gwyscope.net/wiki/doku.php?id=contact&amp;rev=1740488824&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-02-25T13:07:04+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>contact</title>
        <link>https://gwyscope.net/wiki/doku.php?id=contact&amp;rev=1740488824&amp;do=diff</link>
        <description>Contact mode measurements

Contact mode is the simplest measurement regime. The feedback loop uses signal from the probe and adjusts the z-piezo of the microscope to make this signal as close to some user defined setpoint value as possible.

To use contact mode with Gwyscope</description>
    </item>
    <item rdf:about="https://gwyscope.net/wiki/doku.php?id=fmkpfm&amp;rev=1740476634&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-02-25T09:43:54+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>fmkpfm</title>
        <link>https://gwyscope.net/wiki/doku.php?id=fmkpfm&amp;rev=1740476634&amp;do=diff</link>
        <description>FM KPFM

In contrast to AM KPFM operation, in FM KPFM the mechanical and electrical exicitation frequencies are different, which allows single pass measurements and which also means that the regime evaluates different physical interactions allowing higher spatial resolution.</description>
    </item>
    <item rdf:about="https://gwyscope.net/wiki/doku.php?id=gui&amp;rev=1743508498&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-04-01T11:54:58+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>gui</title>
        <link>https://gwyscope.net/wiki/doku.php?id=gui&amp;rev=1743508498&amp;do=diff</link>
        <description>Gwyscope GUI overview

Gwyscope is primarily designed to allow development of user's own interface, i.e. a client which connects to the server running on the hardware. A sample graphical user interface described in this section is only one of all the possible realizations of such client and therefore is far from being complete and optimized.</description>
    </item>
    <item rdf:about="https://gwyscope.net/wiki/doku.php?id=guistart&amp;rev=1740482226&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-02-25T11:17:06+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>guistart</title>
        <link>https://gwyscope.net/wiki/doku.php?id=guistart&amp;rev=1740482226&amp;do=diff</link>
        <description>Gwyscope GUI installation

Graphical user interface is designed to be run on user's computer (not on the Gwyscope boards). The computer has to be connected to a network as the GUI connects to Gwyscope boards using Ethernet interface.

To install and run the</description>
    </item>
    <item rdf:about="https://gwyscope.net/wiki/doku.php?id=hwbox&amp;rev=1740490890&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-02-25T13:41:30+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>hwbox</title>
        <link>https://gwyscope.net/wiki/doku.php?id=hwbox&amp;rev=1740490890&amp;do=diff</link>
        <description>Gwyscope box

To simplify the use of Gwyscope DSP in our lab we wrap it to a Gwyscope box, adding a power source and input and output connectors to it. No other electronics (i.e. High Voltage amps) is present in the box. It has therefore the same specifications as the DSP, with limitations related to number of input and output connector mounted on the box. Numbers of ADCs or DACs are limited by available connectors of the box. The current version we use is shown in the image below. If interested…</description>
    </item>
    <item rdf:about="https://gwyscope.net/wiki/doku.php?id=hwboxcon&amp;rev=1740490999&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-02-25T13:43:19+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>hwboxcon</title>
        <link>https://gwyscope.net/wiki/doku.php?id=hwboxcon&amp;rev=1740490999&amp;do=diff</link>
        <description>Setting up network

Before connecting any analogue inputs or outputs, we recommend adapting Red Pitaya’s network settings to match those of your lab. Therefore connect only the power supply and power on the box. The three leds on the front panel should be lit up. During the testing phase, the Red Pitaya (RP) obtained a fixed IP address (e.g.</description>
    </item>
    <item rdf:about="https://gwyscope.net/wiki/doku.php?id=hwboxserver&amp;rev=1740491052&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-02-25T13:44:12+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>hwboxserver</title>
        <link>https://gwyscope.net/wiki/doku.php?id=hwboxserver&amp;rev=1740491052&amp;do=diff</link>
        <description>Hwserver

The concept of Gwyscope is based on a server-client approach, i.e. a server - hwserver - is used to control all the hardware based on commands received from a client (e.g. Gwyscope GUI). Default hwserver installation is /root/gwyhwserver_gwyscope</description>
    </item>
    <item rdf:about="https://gwyscope.net/wiki/doku.php?id=hwboxsrv&amp;rev=1740491020&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-02-25T13:43:40+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>hwboxsrv</title>
        <link>https://gwyscope.net/wiki/doku.php?id=hwboxsrv&amp;rev=1740491020&amp;do=diff</link>
        <description>Connecting to Red Pitaya

Once you have configured your Red Pitaya's IP address, you can use a terminal to connect to it. Under Linux OS there are specific packages for different desktop environments, such as Konsole under KDE. For Windows users good terminals are</description>
    </item>
    <item rdf:about="https://gwyscope.net/wiki/doku.php?id=hwboxtest&amp;rev=1740491036&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-02-25T13:43:56+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>hwboxtest</title>
        <link>https://gwyscope.net/wiki/doku.php?id=hwboxtest&amp;rev=1740491036&amp;do=diff</link>
        <description>Basic testing

After successful login to Red Pitaya's OS a set of simple programs was provided for testing of basic functionalities. By default all these programs were installed to /root/gwyhwserver_gwyscope directory. Change to this directory and open e.g.</description>
    </item>
    <item rdf:about="https://gwyscope.net/wiki/doku.php?id=hwdsp&amp;rev=1740490857&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-02-25T13:40:57+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>hwdsp</title>
        <link>https://gwyscope.net/wiki/doku.php?id=hwdsp&amp;rev=1740490857&amp;do=diff</link>
        <description>Specifications

Basic

 Processor:  dual core ARM Cortex A9  FPGA:  Xilinx Zynq 7010 SOC  RAM:	 512 MB  System memory:  Micro SD up to 32 GB  Power consumption (max):  5 V, 2 A; ±12 V, 1 A  Communication interfaces:  RS232, I2C, 1 Gb Ethernet, USB 2.0</description>
    </item>
    <item rdf:about="https://gwyscope.net/wiki/doku.php?id=hwperif&amp;rev=1740564947&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-02-26T10:15:47+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>hwperif</title>
        <link>https://gwyscope.net/wiki/doku.php?id=hwperif&amp;rev=1740564947&amp;do=diff</link>
        <description>Peripherals

We provide several extensions to hwserver such as controllers of different motors.</description>
    </item>
    <item rdf:about="https://gwyscope.net/wiki/doku.php?id=hwperifardu&amp;rev=1742821631&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-03-24T13:07:11+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>hwperifardu</title>
        <link>https://gwyscope.net/wiki/doku.php?id=hwperifardu&amp;rev=1742821631&amp;do=diff</link>
        <description>Arduino Stepper motor

This is another kind of server - asserver - that implements a serial communication with Arduino Uno running a custom firmware controlling a two phase bipolar actuator such as ZST13 from Thorlabs. The firmware for Arduino and details on used hardware modules and wiring can be provided upon request.</description>
    </item>
    <item rdf:about="https://gwyscope.net/wiki/doku.php?id=hwperifpico&amp;rev=1740643082&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-02-27T07:58:02+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>hwperifpico</title>
        <link>https://gwyscope.net/wiki/doku.php?id=hwperifpico&amp;rev=1740643082&amp;do=diff</link>
        <description>Newport Picomotor

We have implemented control of Newport Picomotor actuator. The implementation is similar to the main hwserver, we wrote another server - pmserver - that connects to the Newport 8742 controller via Ethernet and allows for getting controller's ID, setting actuator velocity and acceleration and moving the actuator. Open the</description>
    </item>
    <item rdf:about="https://gwyscope.net/wiki/doku.php?id=hwperifthor&amp;rev=1742819820&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-03-24T12:37:00+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>hwperifthor</title>
        <link>https://gwyscope.net/wiki/doku.php?id=hwperifthor&amp;rev=1742819820&amp;do=diff</link>
        <description>Thorlabs Kinesis Stepper Motor

We implemented support for stepper motor controller KST101 from Thorlabs. Similarly to the Picomotor controller, the tkmserver communication with the controller is based on PyLabLib Python package. See Thorlabs APT/Kinesis devices web page for more info. Note that it was necessary to comment out the last two lines in</description>
    </item>
    <item rdf:about="https://gwyscope.net/wiki/doku.php?id=hwsetup&amp;rev=1740490874&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-02-25T13:41:14+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>hwsetup</title>
        <link>https://gwyscope.net/wiki/doku.php?id=hwsetup&amp;rev=1740490874&amp;do=diff</link>
        <description>Connection to SPM

Gwyscope hardware itself is not enough to perform SPM measurements, it is only the Digital Signal Processor for it. To run a SPM experiment with Gwyscope, you need a microscope hardware and some electronics: usually at least some kind of probe-sample force detection electronics and piezo amplifiers.</description>
    </item>
    <item rdf:about="https://gwyscope.net/wiki/doku.php?id=hwstart&amp;rev=1740557102&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-02-26T08:05:02+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>hwstart</title>
        <link>https://gwyscope.net/wiki/doku.php?id=hwstart&amp;rev=1740557102&amp;do=diff</link>
        <description>Gwyscope assembly

Gwyscope DSP is a shorthand for three boards combo:

	*  Red Pitaya STEMlab 125-14 (PCB Red Pitaya)
	*  Mainboard (PCB CMIPITAYA)
	*  HRDAC board (PCB CMIDAC11001)



Although we designed the boards to be connected in a stack to enhance capabilities of the Red Pitaya (RP), other use cases are possible. For example only RP board and Mainboard might be used to enhance RP with many channels high bit-depth converters or the 20-bit DAC board can also be controlled by just an</description>
    </item>
    <item rdf:about="https://gwyscope.net/wiki/doku.php?id=hwsvnup&amp;rev=1740491071&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-02-25T13:44:31+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>hwsvnup</title>
        <link>https://gwyscope.net/wiki/doku.php?id=hwsvnup&amp;rev=1740491071&amp;do=diff</link>
        <description>Updating hwserver

Stable versions of hwserver are available from Sourceforge repository, for example the version that is matched to V4 electronics is available here. You can download it to your PC, unpack it and copy it to Red Pitaya.

Development (unstable) version can be checkout using</description>
    </item>
    <item rdf:about="https://gwyscope.net/wiki/doku.php?id=lift&amp;rev=1740486252&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-02-25T12:24:12+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>lift</title>
        <link>https://gwyscope.net/wiki/doku.php?id=lift&amp;rev=1740486252&amp;do=diff</link>
        <description>Dual path measurement

In some regimes, e.g. MFM or AM-KPFM, the measurement has to be performed in two steps, first scanning the topography and then some signal slightly above surface.

To enable this, use the “Lift” tab in the main window (in Scan settings area). When non-zero number of lifts is enable, Gwyscope automatically adds channels for lift data, so they can be accessed from drop down menus in the channel and graph visualisation and are automatically stored when storing the data.</description>
    </item>
    <item rdf:about="https://gwyscope.net/wiki/doku.php?id=lua&amp;rev=1740489408&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-02-25T13:16:48+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>lua</title>
        <link>https://gwyscope.net/wiki/doku.php?id=lua&amp;rev=1740489408&amp;do=diff</link>
        <description>Lua scripting

Lua interface is a way how to control the electronics in more general way than what the Gwyscope GUI offers. The GUI provides some support to test it when Lua would be used for scanning, as a special scan path. There interface is very simple and allows loading and storing a Lua script.</description>
    </item>
    <item rdf:about="https://gwyscope.net/wiki/doku.php?id=mfm&amp;rev=1747061103&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-05-12T14:45:03+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>mfm</title>
        <link>https://gwyscope.net/wiki/doku.php?id=mfm&amp;rev=1747061103&amp;do=diff</link>
        <description>Magnetic force microscopy

Magnetic force microscopy (MFM) is a dual-pass technique in which a magnetically coated probe is used to get information about the magnetic stray field distribution above the surface.

MFM measurements are performed in tapping mode, so to perform MFM with Gwyscope, first set up the</description>
    </item>
    <item rdf:about="https://gwyscope.net/wiki/doku.php?id=qm&amp;rev=1743165266&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-03-28T12:34:26+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>qm</title>
        <link>https://gwyscope.net/wiki/doku.php?id=qm&amp;rev=1743165266&amp;do=diff</link>
        <description>Quantitative mechanics

Goal of the quantitative mechanics measurement regime is to evaluate local mechanical properties using off-resonance tapping (ORT) technique for feedback and evaluating the individual force-distance curves obtained during this process.</description>
    </item>
    <item rdf:about="https://gwyscope.net/wiki/doku.php?id=ramp&amp;rev=1740490256&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-02-25T13:30:56+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>ramp</title>
        <link>https://gwyscope.net/wiki/doku.php?id=ramp&amp;rev=1740490256&amp;do=diff</link>
        <description>Ramps

The “Ramp” tab in “Scan settings” area allows to perform ramps - to measure dependence of some quantity on some other quantity, e.g. a force-distance curve or I/V spectrum.

When use switches to this tab, the normal free-running operation of the graphs in the right panel of the</description>
    </item>
    <item rdf:about="https://gwyscope.net/wiki/doku.php?id=save&amp;rev=1740498657&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-02-25T15:50:57+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>save</title>
        <link>https://gwyscope.net/wiki/doku.php?id=save&amp;rev=1740498657&amp;do=diff</link>
        <description>Saving the data

The data are saved as Gwyddion files, using the File menu entries, i.e. user has to save file manually. Two formats are available at the moment:

	*  scanned data, regardless the scan path, are stored as XYZ files, so in Gwyddion they need rasterisation, or use of tools that are designed for XYZ data processing directly.</description>
    </item>
    <item rdf:about="https://gwyscope.net/wiki/doku.php?id=scanpath&amp;rev=1740487145&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-02-25T12:39:05+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>scanpath</title>
        <link>https://gwyscope.net/wiki/doku.php?id=scanpath&amp;rev=1740487145&amp;do=diff</link>
        <description>Scan paths

Typically, SPM data are collected on a raster pattern. Goal of Gwyscope is to demonstrate simple use of other scan patterns, so many options of scan organization are implemented. 

In the main window, in the area of “Scan settings”, there are various tabs for controlling the microscope operation and three of them control also the probe-sample motion, offering raster, path and Lua script based scans.</description>
    </item>
    <item rdf:about="https://gwyscope.net/wiki/doku.php?id=settings&amp;rev=1740487265&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-02-25T12:41:05+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>settings</title>
        <link>https://gwyscope.net/wiki/doku.php?id=settings&amp;rev=1740487265&amp;do=diff</link>
        <description>Settings

Gwyscope hardware can be used to run different SPM feedback loop regimes, e.g. contact mode, tapping mode and to work with different types of probes. The main place to set it up is the hwserver and in particular its initialisation file hwserver.ini. As part of it, different scanning regimes are pre-configured, including parameters of the feedback loop (source of feedback, speed of feedback loop), internal connections on the electronics level and selection of input signals for the elect…</description>
    </item>
    <item rdf:about="https://gwyscope.net/wiki/doku.php?id=sideband&amp;rev=1750923081&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-06-26T07:31:21+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>sideband</title>
        <link>https://gwyscope.net/wiki/doku.php?id=sideband&amp;rev=1750923081&amp;do=diff</link>
        <description>Sideband KPFM

Sideband KPFM is in principle similar to FM KPFM, again using combination of mechanical and electrical oscillation, however the amplitude at frequency which equals to sum of the excitation frequencies (mechanical+electrical) is not evaluated using two step lock-in procedure, but detected directly using the second lock-in. If we use low frequency electrical excitation as in</description>
    </item>
    <item rdf:about="https://gwyscope.net/wiki/doku.php?id=sidebar&amp;rev=1743160240&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-03-28T11:10:40+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>sidebar</title>
        <link>https://gwyscope.net/wiki/doku.php?id=sidebar&amp;rev=1743160240&amp;do=diff</link>
        <description>Hardware

	*  DSP assembly
	*  Specifications
	*  Connection to SPM
	*  Gwyscope box
	*  Setting up network
	*  Connecting to Red Pitaya
	*  Basic testing
	*  Starting hwserver
	*  Updating hwserver
	*  Peripherals
		*  Picomotor
		*  Thorlabs
		*  Arduino


Gwyscope GUI

	*  Overview
	*  Installation
	*  Settings
	*  Saving the data
	*  Scan paths
	*  Dual path measurement
	*  Contact mode measurements
	*  Tapping mode measurements
	*  Quantitative mechanics (ORT)
	*  Sefl-sensing probes (PLL)
…</description>
    </item>
    <item rdf:about="https://gwyscope.net/wiki/doku.php?id=start&amp;rev=1740491510&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-02-25T13:51:50+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>start</title>
        <link>https://gwyscope.net/wiki/doku.php?id=start&amp;rev=1740491510&amp;do=diff</link>
        <description>This Wiki provides an user documentation related to both hardware and software components of Gwyscope project. This allows you to run Gwyscope electronic boards, either standalone, or connected to the sample frontend GUI.

There are two main sections here:

	*  Hardware</description>
    </item>
    <item rdf:about="https://gwyscope.net/wiki/doku.php?id=tapping&amp;rev=1740488834&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2025-02-25T13:07:14+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>tapping</title>
        <link>https://gwyscope.net/wiki/doku.php?id=tapping&amp;rev=1740488834&amp;do=diff</link>
        <description>Tapping mode measurements

Non-contact or intermittent contact measurements, known also as Tapping mode, are based on detection of change of probe resonance when it is affected by attractive and repulsive probe-sample interactions.

To set up the hardware for tapping mode measurements, the probe-sample force related signal, e.g. vertical deflection of the cantilever, has to be connected to input of lock-in 1. The excitation signal goes from fast output 1 and has to be connected to mechanical exc…</description>
    </item>
</rdf:RDF>
