LabAdviser/314/Microscopy 314-307/TEM/Tips/Aztec

From LabAdviser
Jump to navigation Jump to search

Feedback to this page: click here

(content by Jens Kling @DTU Nanolab, Janyuary 2022)


Connection problem with Aztec

Here are the two main connection/communication problems with Aztec:


Communication to the microscope

If Aztec is indicating problems connecting to the microscope, or if f.ex. the high tension is indicated wrongly in the software, you need to check the communication software on the microscope PC. It is named FEI MPO server and should be found in the bottom right of the task bar (see screenshot). Double click on it, to open a window, and then close that window. Go to the Start Menu and find the OINA Tecnai MPO Server there.

MPO server in task bar


restart MPO server from Start menu


After restarting the software here, go back to the support PC and restart Aztec. Communication should be re-established.

If there still is no communication with the microscope, you physically need to re-boot the box. Close Aztec. On the backside of one of the boxes is a power switch. Turn the box off and also un-plug the Firewire cable from this box. Wait 10s. Plug in the Firewire cable and power on the box. Then restart the support PC. The issue should be solved.


Communication with the detector

If Aztec is indicating problems communicating with the detector, you need to re-start the Oxford system. Close Aztec, go to the Start menu and find the software Tidy Up under Oxford. This software re-boots the communication box for the Oxford system (grey and blue box under the microscope table). After running the software, re-start the support PC. This typically fixes the issue.

Oxfords Tidy UP software


If there still is no communication with the detector, you physically need to re-boot the box. Close Aztec. On the backside of one of the boxes is a power switch. Turn the box off and also un-plug the Firewire cable from this box. Wait 10s. Plug in the Firewire cable and power on the box. Then restart the support PC. The issue should be solved.