-
Sample output of NanoMan Strip chart when using 100steps script. This was collected on an Icon with Icon scanner using Nanoscope v8.15.
-
Hi Jason, Are you planning on using PicoForce scripting or do you already have one of our scripting packages like lithoscript or nanoscript? What channel do you want to ramp? The Z piezo position? Do you need to collect data during the ramp or only between ramps? --Bede
-
This code has been tested and works for any kind of HSDC data. Indepedant if 1, 2, 3 or 4 datachannels are saved. It separates the MHz data and the kHz data in different data-arrays. The file is a zip file, containing 3 m-files. The main code is readHSDC(filename). The way to introduce this code in MatLab is as; [DataMHz, DatakHz, TimeMHz, TimekHz]
-
The way the COM interface works, you launch your python program and it sets up communication with Nanoscope. Your python program has all the capabilities from python and its modules (launching other programs, beeping, analyzing, plotting, etc.) and it can control Nanoscope using the commands made available through COM. These commands are described in
-
Hi Andres, If you have already succeeded in running a script to change scan size, you are well on your way to controlling your system from python! That means that you must have a Nanoscript key (to allow access to the COM interface) and Nanoscope must be registered as a COM server. There is a lot of information about python online, but I like the python
-
Hi Cosmin, There are separate sections in the header for each data channel. Each of the sections starts with a line "\*Ciao HSDC list". You will find different Data offsets, lengths and scales for each channel. I looked around and found an Igor procedure to read HSDC files! Here is a description of the procedure: Igor function to read a Nanoscope
-
Igor function to read a Nanoscope High Speed Data Capture (HSDC) file and load the data into Igor waves with appropriate scaling. The native Nanoscope file is read and the ASCII header is parsed to get scaling factors while the binary part is read directly, so no export is required. See the comments at the beginning of the file for more details on usage
-
HSDC files are usually so large that they are unmanageable when exported to ASCII. It is usually much more efficient to directly read the native NanoScope files instead. This is especially true if you plan on analyzing a large number of files. Nanoscope files are composed of an ASCII header that contains information about the microscope configuration
-
Plot of HSDC data created with Python(X, Y) Script