No announcement yet.

How do I determine my AR SPM Software Version?


  • How do I determine my AR SPM Software Version?

    So you have a problem with the software. In order to help us fix the problem, we need to know your version information. There are two easy ways to find this information.

    Inspect the title bar:
    Example Title Bars

    • Experiment Name is the name you give to your work.
    • Instrument Name is the type of AR instrument you own.
    • AR SPM Software is the version of software written by Asylum Research and is the most important number to us. From that we can determine the versions of our lower level XOP code as well.
      • For versions <=120000, the version is a date: YYMMDD with + MMDD since the version went live.
      • For versions >=13.00.00 it is VersionNumber.MM.BuildNumber, where the MM is the number of months since the version went live.

    • Igor Pro is the version of the scientific graphing and data analysis tool created by WaveMetrics. It may also be useful for us to know the Igor version number, but generally this does not matter too much.

    Or go to the Help menu.
    SPM software version table

    • Go to the Help -> MFP Versions menu. This will bring up a table of all your versions.
    • Hit Ctrl + A (to select the entire table).
    • Hit Ctrl + C (to copy the contents of the table to your clip board).
    • Go to your email program where you are writing up your bug report.
    • Hit Ctrl + V (to paste the table into your email message).
      Posting comments is disabled.



    Latest Articles


    • Software version compatability
      by Bemis
      There is an issue with the XYZ gains and older versions of the software.
      If you go to version 12 or above, then your system will be using the new gain system. Once you go to the new gains, your instrument should not use versions < 101010.

      If you want to continue using 101010, you need to make sure it is >= 101010+4706 If you want to continue using 111111, you need to make sure it is > 1126 ...
      2015-05-08, 01:14 PM
    • Building a New real time computer
      by Bemis
      Current recommended system:

      Dell Precision T3500 Workstations
      Intel QuadCore Xeon 3500 series (2.80GHz)
      6GB DDR3 RAM
      2 320GB SATA Hard Drives (RAID1 mirror)
      2012-05-24, 11:14 AM
    • How to install Asylum USB Drivers
      by Bemis
      There are currently 2 versions of the USB drivers, we will refer to them as old and new. The version of the MFP3D software you want will determine if you need old or new drivers.

      MFP3D Version Old Drivers New Drivers
      2011-06-28, 10:02 AM
    • How to write code to click on buttons
      by Bemis
      One of the easiest ways to get started writing Igor code is to write something that simply clicks on Asylum buttons in a certain order. Here is how to get started with that. 1) Bring up the panel that has the button you want to click on. 2) Hit Ctrl + T to bring up the tools for the panel. 3) Click on the second button on the left that now shows. 4) Double Click on the button you want to use. 5) For buttons there are 2 things you need to get from this dialog. The Control name (First ...
      2011-02-02, 08:39 AM
    • Running Copies of the Igor Pro / AR Software
      by Bemis
      There are typically two main reasons to make a copy of the Igor Pro / AR Software, and they are slightly different.
      1. You want to try out some new MFP3D code. There is a new feature that is in the unstable code that you want to try out, but it is the new code. There are going to be bugs, and so you want to be able to go back quickly, and you don't want other people in the lab to have to deal with the new bugs. This is by far the most common reason, and the easier way to make a Igor
      2010-03-17, 03:11 AM
    • Reporting Bugs
      by ARadmin
      Send bug reports to [email protected], but to help us resolve it quickly, please read on and learn how to compose a useful report for us to work from.

      Composing your Bug Report

      Effective bug reports are the most likely to be fixed. These guidelines explain how to write such reports.

      • Be precise
      • Be clear - explain it so others can reproduce the bug
      • One bug per report
      • No bug is too trivial to report - small bugs may hide big
      2010-03-17, 01:51 AM