LEAP Suite Feedback/3.0 beta RC4

From Northwestern University Center for Atom-Probe Tomography
Revision as of 21:30, 25 May 2006 by Dieter (talk | contribs) (→‎Feature Requests)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search


  • Northwestern would like an update on the FIM functionality. As an interim, since we still have LEAP vision, can FIM be done with LEAP vision? We are aware that LCC and LEAP vision can't be run at the same time, since the cameras can be accessed by only one program at a time. Thus, will LEAP vision alone alow us to to FIM? I recall that with the old LCC, part of the controls (HV controls) were in LCC, so LEAPvision alone will probably not do it.
  • We still have those hot channels on the MCP and need a burn-off procedure. Is there a way to power up the MCP over night? I believe the easiest way to do that is just starting a voltage run with no tip in and auto-evaporation control off so that it will keep the tip voltage at say 500V, but the MCP powered up and let it go like this over night?
  • Even after a (good) laser pulse energy calibration, there is no green check next to the 250kHz anymore. Has this feature been dropped with RC4, or are we doing something wrong?
  • We would like to install ISDB1.4 on a PC different from the LCC, so that users can enter their tips independently. ISDB1.4, however, was not included with the LEAP Suite 3.0 Beta RC4. This is the only CD with LEAP Suite3.0 we can find (what happened to the CD's from the original installation on April 19?). Can you give us somehow access or perhaps even e-mail us ISDB1.4?
  • I think we have addressed this question before, but why can't we adjust gain and exposure on the bottom microscope camera?
  • Likewise, in 'puck exchange', we can't change gain and exposure for the side camera. For the top camera, which supposedly is identical to the side camera, gain and exposure can be adjusted.

Feature Requests

  • We would like the camera-snapshots back. They are useful to document tip alignment and aperture views and how they change for different runs and over time.
  • I think I had mentioned this to Eric already when he was here, but it seems an even more natural feature to me now: A way to track how the beam position changes during a run, and also over time, perhaps with aperture. The position is currently displayed in a numeric field in the xy-scan pane. How about having that field being a pop-down menu with the last beam positions with a time-stamp with format "HH:MM:SS (x,y,z)"? The feature could be expanded to serve as a beam position memory, with the possibility to select a past position and have the beam go there. Switching quickly between two or more positions could be very useful for specific applications such as studying the beam-tip interactions. There could be a graphical way of tracking the history of the beam positions as well, perhaps right-clicking on the beam-position graph shows the last 10 positions or 'something'.
  • Dynamic beam tracking in laser mode. When a run is stable and goes at a sufficient rate, the laser could just continuously oscillate in x and y direction with an amplitude of FWHM or less to detect tip motion and beam alignment. This would be leass disruptive than a xy scan every few minutes but may still guarantee optimum beam alignmen. Imago supports this idea and Eric Strennen knows about it
  • ISDB should also store and make retrievable beam position and power/pulse fraction
  • the 'home' button in system schematic and puck alignment tab should read 'home z' since in fact it homes only z
  • What is referenced to as 'evaporation rate' is in fact a 'detection rate'. In fact, at the same 'detection rate', the evap rate would be very different let's say for 80mm and 128mm flight path. -- Dieter 16:30, 25 May 2006 (CDT)



  • "LAS - no pulses detected - detector T zero input not receiving trigger pulses" --- this was initially reported as occurring at least twice between Wednesday and Friday of last week, but it appears to have occurred twelve times following the initial report. According to Dieter and Kevin, "the error occurred eleven times when performing manually an xy-scan, which we typically do when a tip develops to align the beam. The last time it occurred out of the blue while 5M or about 20 minutes into a run. The error ends the run and the save dialogue comes up, it thus prevents us currently from getting long runs."
    Kevin Yoon told me today (Mon May 22) that the this error message was preceded by a drop of the measured Laser Power to zero in the 'run statistics' pane.
  • Following a laser power-on sequence, a message prompt was received that required a power meter calibration. However, the "Pulse Energy Calibrate" button on the "Instrument Admin" tab didn't appear to do anything. It was green but after clicking on it nothing happened.
  • We shut down the laser since we wanted to run only voltage atom probe in the evening. Sure enough, when hitting 'Acquire' in voltage atom-probe, it did pop up an error message, interestingly enough, that the 'laser beam energy is not calibrated', not noticing that the laser wasn't running at all. These interferences between laser atom probe and voltage atom probe are annoying, but fortunately this one just wanted to be acknowledged.
  • Voltage atom probe keeps complaining that 'the wave-plate is not calibrated' (sic) when trying to start a voltage pulsed run. Acknowledging the message will let you proceed. (24 May 06 DI)

Interface/General program freezes/logouts

  • The buttons on the instrument flange stage motion would remain "on" when selected. This was cleared on a few occasions by simply selecting one of the other directions of motion. However, on at least one occasion, the stage motor continued to move after the command was removed by the user, which caused the specimen to move dangerously close to the local electrode before finally stopping.
  • When clicking incidentally with the scroll wheel on a camera view, the cursor gets stuck in scroll mode and won't reset until one moves it elsewhere and clicks.
  • When Davis was closed manually it would not open automatically when choosing the voltage or laser atom probe tabs. Initially this was remedied by logging out and logging back in to the client PC, but it was suggested that they stop the Davis program through task manager, and this seems to work.
  • DAVis stopped updating a couple of hours into a longer run. This could be fixed by closing DAVis, killing the process, and restarting DAVis.
  • The LCC user was logged out for some reason on Friday, May 12, morning around 3am and PC was restarted. According to the Windows event logs, it was not initiated by a program, such as Windows auto update. Dieter was verifying whether or not this was done by a user. The user claimed to have shut down the laser (current standard procedure at NU), but NOT to have logged out.
  • (Run ends while LCC is minimized trap). This happens when LCC is minimized when a run ends (MCP back current - tip fracture...). When the LCC program is minimized and the end-of-experiment dialogue pops up, one is unable to restore or maximize LCC as the dialogue window has focus. The only known way out is to use the keyboard to try to blindly complete the dialogue before maximizing the LCC window. It would be better if this either launched as a separate window or was integrated in such a way that it did not steal the focus from the LCC. At the very least, blind entry should be made easier by making "unknown" or "null" the default for both run quality and specimen conditition (because then people could merely hit return once to accept the run).

Stage Control

  • Stage controller twice did not automatically came back up fully after a flash. A manual power reset on the controller was required.

Laser warnings during voltage pulse

Specimen voltage stopped ramping while in voltage pulse mode every 10 minutes four times in a row on Thursday afternoon. unchecking auto-evaporation control would not let you increase the voltage manually. After a few seconds, the run terminated with the error message:

"0504 Programming Assertion Failed. Could Not Start the Scan. Section Lock Attempt Failed." popping up on the client PC. At least once in one of these four instances, LSS PC displayed error message

"Programming Assertion Failed. Module ISbeammanager.cpp line 423"

As mentioned, this happened during a voltage scan. Since it seemed to be an interference with the auto-scan feature of laser atom probe, which was set to 10 minutes repeat, auto scan was changed to 1000. This did not change the behavior, "0504 Programming Assertion Failed. Could Not Start the Scan. Section Lock Attempt Failed." came up after 10 minutes again. This problem did not reoccur Friday. Saturday, however, Marsha was "staring at the screen at the time in question (10 minutes), and the program did seem to pause for about two seconds at that very moment, but no error message came up and the run(s) continued."