-
The printable manual for 1.50 is now in the same directory with the installer (ftp://sboftp.bruker-nano.com/outgoing/GPTech/Software/NanoScope_Analysis/). Note that this will not be kept as current as the online manual that is available by pressing the F1 key or clicking on the blue question mark icon, but it should get you started if you really need
-
Hi Juliane, Sorry to be so vague, but I have not tried to recover raw data myself. It should be possible, but will probably require some work to get it functioning. I can get someone in software to explain the header parameters that are used to back calculate raw mean in the roughness analysis if you would like to take it on... --Bede
-
Another possibility is that Nanoscope did not shut down correctly and is still paritally running. Rebooting the computer would eliminate that possibility. --Bede
-
Hi Qian, What version of Nanoscope did you use to collect the force curves? Can you provide one of the files that is giving you problems? Are you able to open the file at all? --Bede
-
Hi Dietmar, To make the 3d image have the correct scaling, you need to adjust the 'Zaxis Aspect Ratio' to consider both the Scan Size and the Z scale: Right click on the color scale bar, choose 'Color Scale...' and choose the 'Modify Data Scale' tab Adjust the 'Display' 'Maximum' and 'Minimum' if desired
-
Glad to hear that you figured it out. It is important that the gain is not too small or too large -- you will see the curves jumping and big variations in the peak force error if the gain is too large as well... --Bede
-
Hi Dietmar, Are most of the curves in the HSDC capture like this? Or is this an unusual curve? If you look at the force vs. Z plot in the force monitor (in realtime) do you see the same behavior? Or do they look correct in realtime? What version of Nanoscope and Nanoscope analysis are you using? --Bede
-
Hi Sreejith, Did you try my suggestions in the previous post? When was the last time you were able to tune correctly? What has changed since then? --Bede
-
By the way -- in one of your earlier posts you mention that the number of curves is limited in Point&Shoot. That is only partially true -- You can capture thousands of curves in an array in P&S, but there is a limit on how many can be overlaid offline in Nanoscope Analysis. If you create your own offline analysis code, there is no need for that
-
Hi Alessandro, You are correct, the topographic map in FV is built using the height, not the height sensor and you can expect some distortion for very tall samples. If you are willing to ramp more slowly, you could use closed loop Z with FV. The CLZ feedback loop will linearize the height so that it matches the height sensor, but there is always some