From: W. Trevor King Date: Fri, 19 Nov 2010 18:19:47 +0000 (-0500) Subject: Update MultiMode references in general posts. X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=712b278f23172332ceb1ceb4f89019ed2a54407f;p=mw2txt.git Update MultiMode references in general posts. --- diff --git a/posts/Grr_Multimodes.mdwn b/posts/Grr_Multimodes.mdwn index 7f605f6..b4092b1 100644 --- a/posts/Grr_Multimodes.mdwn +++ b/posts/Grr_Multimodes.mdwn @@ -1,26 +1,28 @@ -[[!meta title="Grr Multimodes"]] +[[!meta title="Grr MultiModes"]] [[!meta date="2008-07-07 18:54:09"]] -There was some trouble with tapping-mode imaging this morning, and with Prof. -Yang's help things seem to be straightened out now. I tried both Nanoscopes -with both Multimodes (we have two *nominally* identical systems), but had not -bothered to swap heads. As it turned out, we had been using the infrared head -(we have three heads), which wasn't working. Not that that was the only -problem. As it turned out, tapping seems to be working with the combination -
-  Nanoscope 2 -- Multimode 1 -- Head 1 or 2
-
-As far as I can tell, the problem is generating the voltage for the piezo that -vibrates the cantilever, which seems to take place -[on the Multimode main board](http://www.physics.drexel.edu/~wking/rsrch/multimode/internals.shtml). Unless -something is seriously wrong with the Nanoscope, it shouldn't matter which -Nanoscope we use. I suppose I should trace the Nanoscope-Multimode +There was some trouble with tapping-mode imaging this morning, and +with Prof. Yang's help things seem to be straightened out now. I +tried both NanoScopes with both [[MultiModes|MultiMode]] (we have two +*nominally* identical systems), but had not bothered to swap heads. +As it turned out, we had been using the infrared head (we have three +heads), which wasn't working. Not that that was the only problem. As +it turned out, tapping seems to be working with the combination + + NanoScope 2 -- MultiMode 1 -- Head 1 or 2 + +As far as I can tell, the problem is generating the voltage for the +piezo that vibrates the cantilever, which seems to take place on the +[[MultiMode main board|MultiMode/internals]]. Unless something is +seriously wrong with the NanoScope, it shouldn't matter which +NanoScope we use. I suppose I should trace the NanoScope-MultiMode communication in both cases and look for something different. -I've no idea how generating a tunable sine wave can be so complicated. The -simple solution is to stick to *modular* equipment with open-standard, -easily-accessible communication between them, but I don't have time to develop -a system like that. Some day I will give up on Nanoscope troubleshooting and -build a [GXSM system](http://gxsm.sourceforge.net/). +I've no idea how generating a tunable sine wave can be so complicated. +The simple solution is to stick to *modular* equipment with +open-standard, easily-accessible communication between them, but I +don't have time to develop a system like that. Some day I will give +up on NanoScope troubleshooting and build a [GXSM +system](http://gxsm.sourceforge.net/). [[!tag tags/hardware]] diff --git a/posts/MultiMode.mdwn b/posts/MultiMode.mdwn index f9b8747..734488b 100644 --- a/posts/MultiMode.mdwn +++ b/posts/MultiMode.mdwn @@ -1,4 +1,4 @@ -The Multimode product line has been passed through several companies +The MultiMode product line has been passed through several companies over the years. It started out at [Digital Instruments][DI], which was aquired by [Veeco][] in February 1998 before being passed off to [Bruker][] in August 2010. @@ -15,8 +15,8 @@ notes on: * A [MultiMode manual][manual] [[!img multimode_assembled.jpg size="500x" - alt="An assembled Multimode microscope" - title="An assembled Multimode microscope"]] + alt="An assembled MultiMode microscope" + title="An assembled MultiMode microscope"]] [DI]: http://www.di.com/ [Veeco]: http://www.veeco.com/ diff --git a/posts/MultiMode/internals.rst b/posts/MultiMode/internals.rst index 1d6179b..6083aa9 100644 --- a/posts/MultiMode/internals.rst +++ b/posts/MultiMode/internals.rst @@ -172,7 +172,7 @@ Line Role To AFM head to tipholder line descriptions ======================================= -Labeled looking down on tipholder along laser, with Multimode LCD at +Labeled looking down on tipholder along laser, with MultiMode LCD at bottom from top-left: 1 2 3/4 5 6 ==== ===================== ================================================================= diff --git a/posts/MultiMode/stepper.mdwn b/posts/MultiMode/stepper.mdwn index 392cfd4..a9c7311 100644 --- a/posts/MultiMode/stepper.mdwn +++ b/posts/MultiMode/stepper.mdwn @@ -21,7 +21,7 @@ some of the more suspicious lines on an oscilloscope, I saw that lines they were TTL compatible. A short while later (wink), the LabVIEW code was up and running. The LabVIEW computer (via a PCI-6052E card and BNC-2090 box) writes TTL stepper motor currents to the relevent -lines on the Nanoscope↔Multimode cable using our break-in box. +lines on the Nanoscope↔MultiMode cable using our break-in box. Computer <-> Breakout box <-> MultiMode NanoScope <------^ @@ -33,7 +33,7 @@ Part list (outdated commercial parts linked to the current generation): * [BNC-2090](http://sine.ni.com/nips/cds/view/p/lang/en/nid/1177) * Nanoscope IIIa (altered) * Homemade break in box -* [[Multimode II AFM]] +* [[MultiMode II AFM]] Breakout box ------------ @@ -42,8 +42,8 @@ Build a DB-25 breakout box, such as the ugly hack job shown below. This gives us access to the stepper motor drive-lines. [[!img break_in_box.jpg size="500x" - alt="Break in box for Nanoscope-Multimode cable" - title="Break in box for Nanoscope-Multimode cable"]] + alt="Break in box for Nanoscope-MultiMode cable" + title="Break in box for Nanoscope-MultiMode cable"]] Control the motor ----------------- @@ -69,7 +69,7 @@ pseudo-code: write( output[index] ); } -For my Multimode, the motor steps 'Up' when I equate: +For my MultiMode, the motor steps 'Up' when I equate: @@ -89,12 +89,12 @@ Figuring it out =============== [[!img multimode_interior_0.jpg size="500x" - alt="The interior of the Multimode chassis with the main PCB removed" - title="The interior of the Multimode chassis with the main PCB removed"]] + alt="The interior of the MultiMode chassis with the main PCB removed" + title="The interior of the MultiMode chassis with the main PCB removed"]] [[!img multimode_main_board_chips.jpg size="500x" - alt="The main board of the Multimode" - title="The main board of the Multimode"]] + alt="The main board of the MultiMode" + title="The main board of the MultiMode"]] General stepper motor wiring ---------------------------- diff --git a/posts/MultiMode_head_connection_deconstructed.mdwn b/posts/MultiMode_head_connection_deconstructed.mdwn index 5b43215..b6c86fe 100644 --- a/posts/MultiMode_head_connection_deconstructed.mdwn +++ b/posts/MultiMode_head_connection_deconstructed.mdwn @@ -1,11 +1,11 @@ [[!meta title="MultiMode head connection deconstructed"]] [[!meta date="2008-07-15 17:48:17"]] -After some tapping-mode debugging, I now know what *almost* all the lines -connecting the -[MultiMode head](http://www.physics.drexel.edu/~wking/img/multimode/multimode_head.jpg) -to the -[base](http://www.physics.drexel.edu/~wking/img/multimode/multimode_base_0.jpg) -do. Take a look at my [notes](http://www.physics.drexel.edu/~wking/rsrch/multimode/internals.shtml#head). + +After some tapping-mode debugging, I now know what *almost* all the +lines connecting the [[MultiMode]] head ([[!ltio +MultiMode/multimode_head.jpg]]) to the base ([[!ltio +MultiMode/multimode_base_0.jpg]]) do. Take a look at my +[[notes|MultiMode/internals#afm-head-micro-d-15-connector-line-descriptions]]. If anyone has figured out line 4, or is using a MultiMode as an STM, please [send me an email](http://www.physics.drexel.edu/~wking/contact.shtml). diff --git a/posts/Stripchart.mdwn b/posts/Stripchart.mdwn index e3e072c..ada479b 100644 --- a/posts/Stripchart.mdwn +++ b/posts/Stripchart.mdwn @@ -1,8 +1,8 @@ [[!meta title="Stripchart"]] [[!meta date="2008-07-08 17:03:08"]] -I was trying to troubleshoot the feedback loop on our Nanoscope today, and +I was trying to troubleshoot the feedback loop on our NanoScope today, and when I went to fire up my [Comedi](http://www.comedi.org/)-driven stripcharts -monitoring some lines in the DB-25 cable connecting the Multimode to the +monitoring some lines in the DB-25 cable connecting the [[MultiMode]] to the Nanoscope, I got a bunch of wierd errors (errnos 11 and 29). I tracked them down to some of the Xlib function calls in my stripchart code (yes, I wrote my own
DB-25Role