Showing related tags and posts across the entire site.
-
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
-
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...
-
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...
-
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...
-
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...
-
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...