1 / 6

Software breakout session: FPA related OPUS issues

Software breakout session: FPA related OPUS issues. Michael J. Nasse , Carol Hirschmugl. Bruker OPUS issues (newest version: 6.5 SP 1 Build: 6, 5, 92 (20080204)). Extremely sensitive to disturbances during acquisition Don’t move the mouse Network card to outside world disabled

barr
Download Presentation

Software breakout session: FPA related OPUS issues

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Software breakout session: FPA related OPUS issues Michael J. Nasse, Carol Hirschmugl

  2. Bruker OPUS issues (newest version: 6.5 SP 1 Build: 6, 5, 92 (20080204)) • Extremely sensitive to disturbances during acquisition • Don’t move the mouse • Network card to outside world disabled • No antivirus running in background • Reference interferogram not saved • Mirror velocity is silently set to 80% of FPA frame rate in Video Assisted Mode • FPA mosaic size limited: max: 2x3 with 96x96 pixels, 4 cm-1 resolution (filesize < 2GB), but programs such as ENVI can be used • FPA parameters not saved in OPUS files (gain, integration time, offset, etc.) • 128x128 pixels does not work in 4 cm-1 resolution: Out of Memory even with 4GB • FPA electronics temperature readout fails • OPUS runs under Vista (even 64bit) for analysis, but can’t run hardware devices, so that it can’t be used for the acquisition computer

  3. Computer equipment Gigabit Network card 2 Gigabit Network card 1 Network card 1 Private network Acquisition computer (32bit XP, 4 GB RAM) Analysis computer(64bit Vista, 8 cores, 8 GB RAM, 3 TB hard disk) Bruker instruments

  4. Automatic data transfer: acquisition → analysis computer We use a batch file to transfer our data from the acquisition computer to the analysis computer. After acquiring data in OPUS we immediately unload the file in OPUS (we don’t look at the data on the analysis computer, we just acquire it there, that helps to keep OPUS stable) and run the batch file. After that, the computer is ready to take data again (OPUS can keep running in the background as long as the files to tranfer are unloaded). The batch file does the following: Enable network connection between acquisition computer and analysis computer(this does the same as “disable” in the Windows Device Manager) Transfer files with your favorite synchronization program, we use GoodSync (Shareware),but Microsoft has a free program called SyncToy or you can use the free FreeFileSync Disable the network connection again, so that you are ready to take data again Here is the code: devcon enable *SUBSYS_13768086 "C:\Program Files\Siber Systems\GoodSync\GoodSync.exe" /miniwin /exit sync /all devcon disable *SUBSYS_13768086 The *SUBSYS… has to be replaced with the code corresponding to your specific network card. See online documentation for devcon.exe. The link for devcon is below. • FreeFileSync: http://sourceforge.net/projects/freefilesync/ • SyncToy: http://www.microsoft.com/Downloads/details.aspx?familyid=C26EFA36-98E0-4EE9-A7C5-98D0592D8C52&displaylang=en • Devcon: http://support.microsoft.com/kb/311272

  5. Bruker OPUS database

  6. Bruker OPUS database SFM: Sample Form SNM: Sample Name

More Related