Release Notes
Release Notes
Release Notes
70
Software Release Notes
Notice
• All rights are reserved, including those to reproduce this document or parts thereof in any form without permission in
writing from Shimadzu Corporation.
• Information in this document is subject to change without notice and does not represent a commitment on the part of the
vendor.
• Any errors or omissions which may have occurred in this document despite the utmost care taken in its production will be
corrected as soon as possible, although not necessarily immediately after detection.
• Please be kindly advised that Shimadzu Corporation is not liable for any outcomes caused by your use of this document.
• Microsoft and Windows are registered trademarks of Microsoft Corporation in the United States and/or other countries.
The TM and ® symbols are omitted in this document.
1. Overview
Thank you for purchasing UVProbe Version 2.70 control software for Shimadzu UV-Vis(-NIR) spectrophotometers.
These release notes describe changes and precautions for Version 2.70 of UVProbe software.
The following chapter describes changes in functionality and software fixes included in the latest version of UVProbe.
Customers with UVProbe Version 2.62 or earlier should also refer to Chapter 3, which describes the history of
functionality changes included in each version. Chapter 4 describes precautions and advice for using UVProbe software.
Please read and understand these release notes before using the UVProbe software.
[product configuration]
The contents of UVProbe Version 2.70 setup CD are as follows.
UVProbe Version 2.70
Authentication Tool Version 1.10
Virtual COM Port Driver for USB Version 1.3.0.0
[operating environment]
UVProbe Version 2.70 supports
Windows 10 Pro (64-bit versions)
Windows 7 Professional (32/64-bit versions)
1. Change of the number of decimal places became the target of the audit trail in the photometric module.
2. Editing of comments in photometric data files (*.std, *.unk, *.pho) and kinetics data files (*.kin) became the target of the
audit trail.
3. When datasets are deleted in spectrum data files (*.spc) or kinetics data files (*.kin), dataset history is created.
2.2.Bug Fixes
Common Functionality
1. Fixed the bug that some characters entered in the Sample ID field became garbled in the photometric module. This bug
occurs only in UVProbe Ver.2.61 and Ver.2.62.
2. Fixed the bug that, in the photometric module, unsaved photometric data files (*.pho) were not automatically saved when
the files were newly created after the template file was saved. This bug occurs only when the UVProbe is used in the GLP
mode.
1. Fixed the bug that correct photometric type of the data was not displayed on the LabSolutions DataManager when
photometric data files (*.std, *.unk, *.pho) were saved while the photometric module was not opened.
2. Fixed the bug that changes to the files were prohibited when "Prohibit changing of files whose result files have
not been confirmed" in the Security Policy was turned ON even though the report (PDF file) did not include
the confirmation form.
3. The text in the log outputted when editing comments in spectrum data files (*.spc) was changed.
4. Fixed the bug that, in kinetics measurement method files, the 1st decimal place was not recorded in the log outputted when
sampling pitch was changed.
5. Fixed the bug that, on the reason input screen, the dataset history of data processing was handled as the 2nd version when
the data processing was automatically conducted after spectrum measurement.
6. Fixed the bug that the UVProbe was forcefully terminated when measurement was performed with a standard sample file
(*.std) opened. This bug occurs only for the UVProbe Ver.2.61 and Ver.2.62 under the LabSolutions DB or CS system
environment.
7. Fixed the bug that it was prohibited to export sample files (*.unk) and to save the template of sample files (*.unk) when
"Prohibit saving data file as other name" in the security policy was turned ON.
8. Fixed the bug that no data file was registered to the database when a carriage return was inserted between the 63rd and 64th
characters of the comment of the dataset.
1. Fixed the bug that the Sample ID field became empty on the Agent Manager when photometric data files (*.std, *.unk,
*.pho) were registered in the Agent. This bug occurs only in UVProbe Ver.2.62.
2. Changes were made so that even if UVProbe or the OS shuts down unexpectedly during quantitative analysis or
photometric measurement, files including only the sample rows for which measurement has been completed are registered
to the database when UVProbe starts up next time.
3. The " Confirmation Form " in which users can enter the results of checking result files (function of Data Manager) has been
added to the print object (link text) of UVProbe.
Bug Fixes
1. The indication of statistical function r2 for the calibration curve has been changed from "correlation coefficient r2" to
"squared correlation coefficient r2" Also, "multiple correlation coefficient r2" was changed to "squared multiple correlation
coefficient r(M)2".
2. Changes were made to display a message to indicate that the exiting process is being carried out when exiting UVProbe.
3. Fixed the problem of standard sample files (*.Std) being saved, even when photometric files (*.pho) were not saved.
2. Fixed the problem of the instrument information for the measurement method being overwritten with the information of the
registered instrument when viewed or printed, when data created on a model that is different from the instrument registered
to the LabSolutions DB or CS system was opened in the postrun analysis mode.
2. The location of the folder for saving sample data files and measurement method files during installation was changed
(moved from the installation folder to "C:\UVProbe-Data" folder).
When measurement methods are changed and saved, any changes made since the last time methods were
saved are recorded and saved in the measurement method file.
Measurements can no longer be started if the specified measurement method is not saved.
Reasons can be entered for changes made since the last time the file was saved.
A description and reasons for measurement method changes are registered as an audit trail log event in the
Log Browser (a LabSolutions application).
A history of changes to the currently loaded (specified) measurement method file can be viewed and
printed.
4. Reasons can now be entered for changes made to data files (such as for data processing).
Reasons can be entered for changes made since the last time the file was saved.
Note: If changes were made to multiple sets of data, reasons can be entered for each data set.
A description and reasons for data file changes are registered as an audit trail log event in the Log
Browser (a LabSolutions application).
Entered reasons for changes are added to the data history and saved together with the data file.
6. [Spectrum/Time Course Modules) User rights for executing data processing were added.
7. The name of the results file created when the data file was registered was added to the file information column in the
sample information view of Data Manager.
A results file ("Tables.html") containing data processing results (peak detection table, point picking table, and area
calculation table) can be sent to a folder for uploading to a host computer using a LIMS connection option.
8. A tab page for displaying data processing results (peak detection, point picking, and area calculation) was added to the data
information view in Data Manager.
A text file containing data processing results (peak detection table, point picking table, and area calculation
table) can be sent to a folder for uploading to a host computer using a LIMS connection option.
Multi-data reports can now include peak detection and point picking values.
9. [Spectrum/Time Course Modules] Changes were made so that when a file contains multiple data sets, the analytical results
for the last data set to be edited are registered in Data Manager as a results file or data information.
10. The name of the measurement method file used was added to the data file summary information.
11. Local files can now only be imported in the postrun analysis mode using UVProbe.
12. The Created By field for report files automatically registered for quick printing when projects are created is left blank.
13. [Photometric Module] Changes were made so that when measurement data protection policies are enabled (for GLP
compliance or when connected to LabSolutions), data is not saved automatically as a data file before data is measured
(when there is no data).
15. The file name was added to sub-messages in the log registered in the Log Browser when measurements are started.
16. [Photometric Module] Changes were made so that accessory units parameters cannot be changed after starting
measurements.
17. Fixed the problem of the report file size increasing when the preview function is repeated for a report file that contains a
pasted bitmap image.
18. [Photometric Module] Fixed the problem of data files remaining unsaved even after changing the EX column checkbox
setting in standard sample tables.
19. [Photometric Module] Fixed the problem of changes to the units on the equation tab page in measurement methods not
being recorded in data histories.
20. [Photometric Module] Fixed the problem of changes to the passed text or failed text on the Pass/Fail tab page in
measurement methods not being recorded in data histories.
21. [Kinetics Module] Fixed the problem of only point picking histories being repeatedly recorded whenever data files
containing point picking results are opened.
22. [Photometric Module] Previously, when a file was renamed and saved, only the new name was recorded in the data history.
Therefore, a file name change history was added, so that the file name prior to a file name change can be confirmed.
23. [Kinetics Module] Fixed the problem of parameter changes in activity value tables not being recorded in data histories or
unsaved.
24. Changes were made so that UVProbe is not launched if "LSSService.exe" is not running on the UV control computer
(ACQ).
25. Changes were made so that an error message is now displayed if a PDF output fails.
26. Changes were made so that measurements cannot be started if the LSS service has stopped on the ACQ computer.
27. Fixed the problem of the file version being incremented each time the [Save As] button is repeatedly clicked.
28. [Photometric Module] Previously when data version count management is enabled and a data file is saved with a new
name, the version number prior to saving the renamed file was entered as the file number recorded together in the log event
for saving the renamed file in the data history. Therefore, changes were made so that the file name is no longer included in
the history if a renamed file is saved.
3. Fixed the bug that the function checking for repeated sample IDs did not work properly when the Auto Fill function was
ON in Photometric module.
4. Fixed the bug that files were not saved properly if the user pressed the save button on the toolbar after entering comments
in Photometric module.
5. [Only when LabSolutions DB/CS system has been installed] Fixed the bug that the function to check prohibited letters in
filenames did not work properly when an Auto or Repeat Scan in Spectrum module, or Photometric measurement was
performed.
6. [Only when LabSolutions DB/CS system has been installed] Fixed the bug that, when unsaved data was printed, the status
indication on headers was not printed properly depending on the printer's resolution setting.
7. [Only when LabSolutions DB/CS system has been installed] Fixed the bug that the user was able to control the instrument
even from the UVProbe running in Postrun analysis mode, by using function keys.
8. [Only when CLASS-Agent system has been installed] Fixed the bug that no data file was registered to the database when
multiple data files were saved simultaneously in UVProbe.
2. Added a user privilege for "monitoring a photometric value". Any user without the privilege cannot view a photometric
value with the real-time monitor except during measurement.
3. Added a user privilege for "canceling measurement". Any user without the privilege cannot cancel measurement on the
way.
Note: Security policies and user privileges are available only when the LabSolutions DB/CS(UV) system is
configured.
4. Fixed the bug that, in measurement with the Kinetics module, a data file saved under a different name was displayed with
its original file name in an output PDF file.
5. Fixed the bug that, during configuration of the LabSolutions DB/CS, the [Change Name] button was enabled as default
when the file property window of Spectrum module was opened.
6. Fixed the bug that a data file was not registered in the database when outputting a PDF file failed.
7. Fixed the bug that changing user settings of the SkyPDF driver led to failure in outputting a PDF file.
8. Fixed the bug that inputting a file name in the [Save as] window and then moving a focus to any file in the file list caused a
file to overwrite the focused file taking its file name without displaying a confirmation message.
Fixed a problem where using quick print of the data print table only printed up to 2 pages.
Fixed a problem where the copy command did not work only in cases when the entire column was selected by clicking
the title cell in the data print table.
[Data Manager]
Fixed a problem where, when photometric files (*.pho) were created by importing standard files (*.std), one of the
data numbers that showed the storage count was skipped.
[Security Policy/Photometric Module]
Even when the [Protect raw data] policy was enabled, it was possible to discard unsaved data depending on the
sequence of operation, so a modification was made to ensure that data cannot be discarded.
The row height of data history can now be automatically adjusted. When history information does not fit in a cell
width, it will be displayed in multiple rows.
Undoing and redoing the changes made to the number of digits to be displayed have been disabled.
On the [Attachments] tab page for each measurement method, all names of the CPS accessories are shown as [CPS].
In Spectrum and Kinetics measurement, the [New Data Set] dialog box was displayed after measurement was
completed, but this dialog box has now been displayed before measurement starts. After the file name and other
information are entered and [OK] is clicked, measurement starts.
[Close All] has been added to the [File] menu. All the data files saved in memory can be closed by selecting [Close
All].
The [Close] function has been added to graph legends. Selecting the data name in the graph legend and then right-
clicking [Close] can close the files including the data set.
Values and texts can now be pasted on the comment columns of Peak Pick, Point Pick, Peak Area, and Main table (for
Kinetics only).
The corrected values that were displayed only after a cell blank was performed can now be checked in instrument
history.
A wavelength range set for a measurement parameter is now recorded as measurement method information included in
a data set. Accordingly, when measurement is interrupted, the wavelength range will not be the same as the actual
measurement range.
If unsaved data exists when [New] is selected, the data is automatically saved before it enables making a new file.
It is now possible to perform calculation using the values rounded to the displayed number of digits after the decimal
point. Refer to Help for the details on calculation types and settings to be used. (Enter "settings" in the keyword field
and select [Settings] / [Settings – Photometric].)
The setting to show/hide calibration curve formula and correlation coefficient has been added to the information that is
saved to a template file.
Weighting factor for absorbance can now be set in the calculation formula for 2-wavelength quantitation (absorbance
difference).
Absorbance difference = K1 x Absorbance 1 - K2 x Absorbance 2
Previously, K1 and K2 were fixed to "1," but it can now be set arbitrarily.
The effective number of digits for calibration curve coefficient to be displayed on a calibration curve graph has now
been fixed as six. The numbers beyond the range from 99999.9 to 0.00100000 are shown as exponents.
When am unsaved data file is printed, "Status: Temporary" is printed in the header. Changes have been made not to
save data files automatically before printing.
When the Point Pick was specified on a graph, in some cases the wavelength values were not displayed correctly in the
Point Pick table. Depending on wavelengths, some were rounded up and others were rounded down. This problem has
been fixed.
If the number of displayed Y-axis value digits after the decimal point is set to six, the last digit of the Y-axis scale was
displayed as 1 depending on conditions. This problem has been fixed.
"Report File Name" (one of the selectable information at [Link Text Object]) can now be printed by the Quick Print or
Auto Print.
When a line feed was inserted in the additional information for a measurement method, the line feed was not correctly
inserted in print. This problem has been fixed.
When repeat scan was performed with data processing in the measurement method enabled, the analyst's name was
always blank in the data set created by data processing. This problem has been fixed.
When measurement was interrupted with data processing in the measurement method enabled, the sampling pitch,
measurement method information included in a data set, was not the same as the actual value. This problem has been
fixed.
Unmeasured rows, which only contains sample IDs, can now be deleted.
The following errors have been detected in the interpretation of user-defined equations and they have now been fixed.
When an equation included log 10 or sqrt, the arithmetic calculation was not performed in the correct
sequence.
When an equation included multiplication and exponentiation, the calculation was not performed in the correct
sequence. When the multiplication expression was written first, then it is calculated first. One erroneous
example was A*B^C. In this equation, A was first multiplied with B and then the calculated value was raised
to the Cth power.
Negative values could be assigned to log 10, In, sqrt, and Abs and incorrect values were returned.
When the newly-created measurement method was closed by clicking the [Esc] key or the [x] button, the measurement
parameters that were printed after measurement included information different from the settings. This problem has
been fixed.
3-wavelength arithmetic calculation using peaks detected by range measurement can now be performed.
When the Auto Fill function was applied, unmeasured rows were registered to Agent in the sample table. This problem
has been fixed. Accordingly, when the data file with the sample table including the active Auto Fill function is opened
using the UVProbe software, the sample IDs will not be added automatically.
Measurement was interrupted depending on the combination of the accumulating time and sampling pitch settings.
This problem has been fixed.
If the file name was already incremented to 999 and measurement was performed with [Auto increment of file name]
enabled, the UVProbe software was locked. This problem has been fixed. Even when the file name exceeds 999,
measurement can now be continued by adding the measurement time (hour/minute/second) to file names.
When [Save All] was selected, only the time stamps were updated for the already-saved files. This problem has been
fixed.
Measurement was interrupted when the screen lock function is opened during the measurement interlocking with the
ASC-5. This problem has been fixed.
An application error occurred when a data file was unsaved and a report file for PDF output was printed from the
report generator. This problem has been fixed.
17. When the user account for log-in includes full-width characters, the UVProbe software installation failed. This problem has
been fixed.
18. If the user name was changed in the LabSolutions user management function by Agent System Connected with
LabSolutions LCGC, the user with that user name could not use the UVProbe user management function. This problem has
been fixed.
If you copy it from the [Edit] – [Copy] menu, the graph is copied as a Picture . (The same result when Ctrl+C or a
tool button is used.)
6. The Peak Pick algorithm is improved.
A same photometric value is regarded as a rise (or drop) as was the case in the previous version. To detect it as a
peak, however, at least one increase (or decrease) of the photometric value is now required.
If there are multiple candidate points for a peak, previously the point with the shortest wavelength was adopted.
However, this version adopts the point with the middle wavelength. If the number of candidate points is even, the
point with the longer wavelength is adopted from the middle two points.
7. The function to view measurement methods is added to Spectrum/Kinetics module.
Even a user without right to edit the method, or even during measurement, information of the measurement method
currently set can be viewed from the [View] – [Current Method] menu. However, when the measurement is performed with
another module when the method is viewed, information about the instrument and attachments does not appear.
8. Automatic linefeed is added to the measurement method object of Report Generator.
If the number of lines pertaining to the link source method information exceeds the vertical size of the measurement
method object embedded in a report, a line feed is inserted automatically.
9. When the data acquired with UV-1800 was loaded in Photometric module, the content could not be saved even after
the comment was modified.
10. After photometric measurement with GLP mode, when a report is printed out using the report generator the photometric
data remaining unsaved, then the unsaved data is saved automatically, but a portion of the information about the instrument
is lost.
11. After a new user whose ID contains double-byte characters is added, when the user tries to login with one-byte characters
as the user ID, then the login fails without showing any error message.
12. When “Active Instrument Information” (Linked Text object) was included in a report template, printing reports or PDF
reports through the use of the template failed. It was fixed.
3.10. Functional Changes and Fixes Included in UVProbe Version 2.35
UVProbe came to support Windows 7.
The default data set name shown in windows is “Filename - Data Set Name”.
The default background color for all graphs was changed from gray to white. In addition, the default line colors for
the graph and the hatching colors for peak area were changed to make it more visible against the white.
Part of the report template used for the quick print function was changed.
Report templates can be freely created and associated with files for the quick print function, but many customers
were using the default settings. Therefore, report templates installed as default settings for the following four types of
graphs were changed to a more typical Landscape mode in letter size. Note that this association can be freely
changed via the [View] - [Settings] - [Quick Print] window.
Overlay Spectrum Graph
Active Spectrum Graph
Overlay Time Course Graph
Active Time Course Graph
The method for displaying the [Print Preview] window was changed.
UVProbe was changed to display print preview images in black and white for black and white printers and in color
for color printers. With previous versions, the print preview appeared in color regardless of the printer type.
The method for displaying and printing the [Method Parameters] window was changed.
UVProbe now displays and prints method parameters separated in to blocks according to parameter type. Previous
versions displayed them as a series of blocks in the order [Measurement Parameters], [Sample Information],
[Instrument Parameters], and so on, depending on the module.
Version 2.30 changes the block order by moving [Sample Information] to the bottom. This results in moving
[Instrument Properties] upward, which is typically considered more important than [Sample Information]. Therefore,
this improves the visibility of more important information in the window and reduces the chance of it extending
outside the print area.
The decision branching for selecting detectors was changed for setting UV-3600 series instrument parameters.
The choice in previous versions was [Direct/External]. This was changed to [Direct/External(2Detectors) /
External(3Detectors)]. This allows using optional external detector unit (integral sphere type) with three different
types detectors (PM, InGaAs, and PbS).
If a measurement method using the Auto Print feature is loaded and measurements are performed, the specified file
path or report file may not exist on the PC. In such cases, the measurement would finish without printing results or
displaying an error message. This can cause problems, so the software was changed to check to make sure the report
file exists on loading the measurement method. If the file does not exist, a warning message is displayed.
Scan Speed settings for Auto Scan measurements were eliminated. These settings functioned in UVProbe Versions
1.0X to 1.1X, but from Version 2.00 and thereafter, the setting was ignored even if specified, and scans were always
performed at Fast speed. The software knows that scan speed is fixed at Fast speed for measurements in the
Photometric module and, considering the purpose for the Auto Scan feature, specifying the Scan Speed is not very
meaningful. Therefore, UV-1600, UV-1700, UV-2400, UV-2500, and UV-3100 series models have scan speed fixed
at Fast speed and UV-3600 and SolidSpec-3700 series models have scan speed fixed at Medium speed. (UV-1800
series models are fixed at Fast speed.)
4. Program Alteration Check (Check the Program files)
UVProbe Ver.2.00 only allowed logging in using “Admin” as the user, but Version 2.01 or later version allows any user to
log in (only if optional CLASS-Agent software is not installed).
5. Security Functions
The maximum number of characters allows for passwords was limited to 14 (at SU1).
6. File Operations
When a template file was loaded, the file become “untitled” in memory. The Automatically Save function in GLP mode
requires always assigning filenames. Therefore, the software was changed to open a filename dialog box whenever a
template file is loaded and prompt to enter a filename. The default filename in this dialog box is “<template file
name>_yymmdd_hhmmss”.
3.20. Functional Changes Included in UVProbe Version 2.00
1. FDA's 21 CFR Part11 Compliance
Installing UVProbe Agent allows automatically registering spectrum data files and photometric data files into the
database.
UVProbe can be locked when leaving the computer unattended with UVProbe running.
An Automatically Save function was added that automatically saves any unsaved data stored in memory, whenever
data is printed or UVProbe is closed.
A data transfer function was added that transfers event log and instrument history data to the Agent database.
2. Application Mode
Previous versions allowed setting the Security and GLP functions ON or OFF, but from this version these functions are
specified by selecting [Normal mode], [Security mode], or [GLP mode].
3. Shimadzu User Authentication Tool
User management functions were changed to be performed via the [Shimadzu User Authentication Tool]. This allows
increasing UVProbe security and managing User ID and Password information in one location on the Shimadzu Instrument
Network.
4. File Format Changes
Due to the addition of UVProbe Agent connectivity functions, file formats were changed as well. This makes data from
UVProbe versions 1.12 and earlier compatible with UVProbe versions 2.00 and later, but also makes data obtained with
UVProbe versions 2.00 and later no longer compatible with UVProbe versions 1.12 and earlier.
5. Cell Blank Function (Photometric Module)
The Cell Blank function, which was only available in the Kinetics module, was added to the Photometic module. This
allows obtaining accurate photometric (quantitative) measurements even when using an external MMC-1600 (8/16-
Microcell).
6. Legend Print Function
When printing an overlay of multiple spectra or time-course graphs, it is now possible to print a legend along with the
graphs to distinguish between them.
7. Data Set Summary Print Function
A summary of the date and time when data was acquired, information about the instrument used to acquire the data, and
other information, can be printed along with the corresponding data.
8. UVPC Format File Export Function (Spectrum Module)
Spectrum data obtained using UVProbe can now be exported in UVPC format. Spectrum data measured using UVProbe
can now be imported and used in calculations using optional software (UVPC-COL:Color Measurement Software or
UVPC-FLM:Film Thickness Measurement Software).
Please note when importing UVPC Photometric standard files (*.mwq) the weight factor is not imported.
When loading UVPC Photometric files (*.pho) and the Parameters are set to Quantitative, Ratio or Difference, the
Resultant calculation is not imported.
Please note that importing UVPC Quantitative or UVPC Photometric files that contain repetitions is not currently
supported.
5. Operations During Communications
Unplugging the communication cable or turning off the instrument while attempting communication with instrument may
make your system unstable. It is highly recommended that any current measurement reading is completed and proper
UVProbe shutdown procedures are performed prior to turning off the instrument, unplugging the communication cable, or
disassembling the hardware configuration.
6. "Please note the following points when loading the PHO file (*.pho) acquired with UV-1900 (stand-alone).
If a hyphen is included in the sample ID, the hyphen will be automatically replaced with an underscore.
If a space is included in the sample ID, the space will be automatically replaced with an underscore.
It will be impossible to load the file if the table contains identical sample IDs."
In the Photometric method, it is possible to create a Pass/Fail equation that contains another Pass/Fail equation. In
this situation Pass is equivalent to the value 1 and Fail is equivalent to a value of 0.
2. Data Processing Settings
If no instrument has been installed after a Photometric file is loaded if the Manipulation property sheet is displayed the
Operator list on the Transformation tab is empty. To correct this situation, please install an instrument.
3. Specifying Measurement Methods
Occasionally after performing a standard measurement using the Range feature the data will be displayed in the Standard
Table but not in the Standard Curve. To correct this situation simply open the Method property sheet and select Close. This
problem does not affect the integrity of the data, only the display of the data in the graph is affected.
4. Handling Data Files
If a data file (in any of the following formats) is acquired by an instrument whose type is different from that selected in
UVProbe, do not open the file without a step described below. Otherwise, information unique to the instrument type cannot
be loaded, and measurement parameters (such as slit width) included in the file are reset, causing information stored during
measurement to be lost.
- Photometric files (*.pho)
- Standard files (*.std)
- Sample (unknown sample) files (*.unk)
- Measurement method files (*.pmd)
To prevent this problem, select the type (instrument) on the instrument bar in the main window before opening the file.
The instrument bar can be shown or hidden from the “View” menu.
For details of the instrument bar, see the help menu. (Type in “Instrument” as a keyword, and select “instrument bar”. )
If the instrument type is not registered in UVProbe, follow the procedure described in the UVProbe Tutorial to add the
instrument.
In the Spectrum module and the Kinetics module when working with loaded datasets of two or three kinds of
measuring modes (T%, R%, Abs) the displayed Overlay graph in Print Preview may not be the same as in the main
screen's Overlay graph. For example, if the user changes the Overlay graph properties to have the left axis show T%
and the right shows “None”, Print Preview will attempt to display the next available dataset to the next available axis.
To ensure you preview (or print) what is being displayed in the main screen's Overlay graph, it is necessary to go to
the Graph menu and select the “Graph Legend” menu item and deselect those datasets that are not to be displayed.
2. Editing Reports
When an object in report generator is in edit mode, it is possible for the object to be accidentally deleted. This can
occur when the user has pressed the delete key when trying to remove a character in a table or graph. This occurs
because the delete key has a dual functionality, one to delete objects and the other to delete characters. This situation
can be avoided by using the backspace key to remove the character.
When using Report Generator, some objects can be printed outside of the specified margin and some cannot.
In the Settings dialog of Report Generator, the accelerator keys for the color boxes do not work.
In Report Generator when an object has been set to print on every page, the object order is ignored.
When using the History table object in Report Generator, the column width is not copied from the Spectrum, Kinetics
or Photometric module. The width specified in Report Generator will be used.
The following is a known problem related to printing reports. Occasionally a report will be printed out in Landscape
mode rather than Portrait mode. This is due to a synchronization problem with the Report Generator Page Setup
dialog and the printed report. To work around this problem simply select the correct mode from the Page Setup
dialog in Report Generator.
When transferring report files from computer to computer the report file may not print to the correct printer. All
report files store information about the printer that the report will be printed. When the printer the report was created
for is not available an attempt will be made to print the report to the default printer. If problems are experienced with
this operation simply open the report in Report Generator select an available printer and save the report. The report
should now be able to be printed.
When the Report Generator's Line Control object has been selected as dotted, or dash-dotted, etc. The image will
appear good when it is previewed, but dependent on the selected printer driver, may print as a solid line. To correct
this problem, change the pen width's value to a new value greater than 2.
3. Printing Reports
When printing reports the error message “Server Busy” may be displayed. This occurs when two reports are printed
back to back before the first report finishes printing. This message will automatically disappear after the first print
job has completed. If this situation occurs please wait for the message to disappear and if necessary re-print the
report.
A potential problem may occur when printing reports. An error message, “Failed to connect. Link may be broken.”
may be displayed. If this occurs a crash will occur after this message is displayed. This does not affect the integrity of
UVProbe or its data. However the background printing engine will be stopped. Please retry the last printing operation
to correct this situation.
Certain objects, not written by Shimadzu, may cause painting problems when inserted into the Report Generator
using the “Insert Object” feature. One of the known objects is a Microsoft Word Object.
3. On occasion, UVProbe may become unstable and even freeze because of a conflict with certain instrument attachments or
software configuration without showing warning. To avoid potential data loss it is strongly recommended to perform the
save operation after sample measurements.
4. Restrictions for Help
Clicking on the Search tab in a Windows Help file generates an FTS (full text search) file in the Windows System folder. A
restricted user on Windows does not have write access to this folder. This means the user is unable to use the Search tab in
UVProbe Help files. At the first time, please logon with the administrator authority and use the “Search” function. If once
the FTS file is made, a restricted user can use the search function at the next time.
4.11. Precautions for Using UV-3600/SolidSpec-3700 Series Systems
1. Specifying Measurement Methods
In case sampling pitch is set to small values (UV/Visible: 0.01nm, NIR: 0.01nm, 0.05nm, 0.1nm) and spectrum data
is obtained with wide wavelength range, wavelength may become inaccurate. (Max 0.4nm in UV/Visible, 1.6nm in
NIR) We recommend using wavelength range less than 20nm in UV/Visible region and less than 80nm in NIR
region.
When spectrum data of wide wavelength range is obtained with 0.01nm pitch, too many peaks and valleys may be
detected. As UVProbe consumes quite a lot of time and memory to handle these peaks, the response of UVProbe
may become very slow. These peaks are detected because number of data points in 1nm raised dramatically, and
small noises are detected as peaks. We recommend using wavelength range less than 20nm with 0.01nm sampling
pitch. Moreover, please use 0.05nm or above sampling pitch for the wavelength region larger than grating change
wavelength. (As wavelength moves each 0.05nm in NIR region, 5 continuous data points have equal values even
when sampling pitch is set as 0.01nm. These stairs each 5 data points are detected as peaks by mistake. To avoid this
problem, set 5 or larger Points to Peak Pick property.
2. Using the X-Y Stage for Measurements
When Photometric Repeat scan is performed with using a sequence file of X-Y Stage and by pushing Measurement
Start Button of the instrument, the repetition measurement for the specified count comes to be done at the destination
position of each sequence. If “Prompt before Read” is checked, the commands in the sequence file are performed
until number of it reaches the repeat count. In this case, total number of commands for moving stage in the sequence
file must be a multiple of the repeat count. Otherwise, last repeat measurement has to be terminated by the Stop
button, and the data will be lost.
Push instrument's Measurement Start Button, or click Cancel button of the X-Y Stage status display dialog box, in
order to interrupt the execution of the sequence file of X-Y Stage. It is not possible to resume measurement on the
way of the sequence file. If Stop button of UVProbe is pushed, only one measurement is interrupted, but the rest of
steps in the sequence file will be continued.
3. Using the [Start Measurement] Button for Measurements
In GLP mode, when the screen lock function is effective, measurement by Measurement Start Button of the instrument
cannot be used.
4.12. Precautions for Using CLASS-Agent systems
1. Data files acquired by the Kinetics module are not applicable, so they can’t be registered in the database.
2. When data manipulations creating new data sets are performed repeatedly in short time, it can happen that the data file
registration function does not work well. If you perform data manipulations for a single data file, wait more than 5 seconds
before you continue operation.
3. If the length of a file name is longer than 126 characters, the data file can not be registered in the database.
4. About PDF output
After changing on/off settings for PDF output, your computer needs restarting.
When you read created PDF files, use Adobe Reader ver 6.0 or later.
The following file types are subject for PDF output. Template file or log file are not applicable.
- spectrum file (.SPC)
- photometric file (.PHO, .UNK, .STD)
When new PDF file is created, UVProbe overwrites the PDF file in the destination folder if it has same name.
"Report File Name", one of the available item of "Link Text Object", cannot be used for PDF Output template.