If you have used the option to export measured spectra in CODE using Excel format you can now import these spectra in batch mode.
There is a restriction, however: The spectra must be stored in the first worksheet of the Excel document, with the first wavelength in cell A1.
The number of the file format to be used in the batch control sheet is 27.
This feature is available starting with object generation 4.48.
It does now!
Starting with object generation 4.42, you can now import measured ellipsometer angles from Woollam *.dat files. Files of this kind may contain data for several angles of incidence and several sample positions – hence we have to filter out the data relevant for individual spectrum objects. Details are explained here.
We have repaired the export of optical constants of some types of materials (in particular effective dielectric function objects) to the workbook.
Several import routines for the workbook or the batch control window look for empty cells to detect the end of a data block. These routines failed when the workbook contained cells which looked empty but contained an invisible carriage return character.
Starting with object generation 4.28 this is fixed – a carriage return character is treated like an empty cell now.
We have introduced the above mentioned new type of material object in 2014 already. However, we forgot to add documentation to explain how to use it. This has been done now …
Here is the link to the updated SCOUT documentation page:
http://www.mtheiss.com/help/final/html/scout3/?motivation.htm
During the last months we have implemented a lot of hardware related functions in CODE. Powerful script commands can be used to perform automated optical measurements. Trigger objects can execute actions based on obtained values of spectrometers, optical sensors or motors.
We have now opened a connection to the outside industrial world by adding OPC clients (available in the list of spectrometers). A client automatically connects to a server and retrieves a parameter value at a user-defined rate. The value is available as optical function and can be used in trigger conditions. This way CODE actions can be triggered externally.
A typical application is triggering spectrum recording based on the position of a product in a production line.
In order to realize some hardware projects we have implemented spectrometer objects that can handle up to 3 Avantes or tec5 spectrometers. Spectra are recorded simultaneously.
We have used these objects for production control systems recording transmittance and reflectance from both sides of coated glass. In addition, we use 3 spectrometers in an integrating sphere system that records reflectance and transmittance of light scattering samples like textured solar glass.
Starting with object generation 4.20 you can now select if a spectrometer object acquires new data at automation steps.
The default behaviour is to acquire new data at each automation step. Objects that do this are painted in red in the list of spectrometers. Objects which do not record data at automation events are drawn in gray.
In order to toggle data acquisition on and off press function key F4 (or F5).
The computation of NFRC U-factors and SHGC values involves an iterative process to achieve a stable temperature profile within the glazing. The net energy flow is computed once temperature differences betweeen 2 iterations are below a threshold value. This value has been 0.0001 (K) up to now.
Starting in CODE version 4.20 you can individually set the threshold for each integral quantity. In particular, you can set smaller values to avoid (very small) differences between CODE and WINDOW results for U-factors.