We aim to develop and produce the best solution for your application
in the field of optical measurement technique. To help us to live up to
your expectations and improve our products permanently we need
your ideas and suggestions. Therefore, please let us know about
possible criticism or ideas. We and our international partners are
looking forward to hearing from you.
Thorlabs GmbH
Warning
Sections marked by this symbol explain dangers that might result in
personal injury or death. Always read the associated information
carefully, before performing the indicated procedure.
Attention
Paragraphs preceeded by this symbol explain hazards that could
damage the instrument and the connected equipment or may cause
loss of data.
Note
This manual also contains "NOTES" and "HINTS" written in this form.
The PM400 Handheld Optical Power and Energy Meter is designed to measure the optical
power of laser light or other monochromatic or near monochromatic light sources and the energy of pulsed light sources.
The space-saving, battery powered design is compatible with all Thorlabs “C-Series” Photodiode, Thermal, Pyroelectric sensors, and custom Photodiode, Thermal and Pyroelectric detectors. Combined with a fast USB device interface, these features open a wide range of applications in Manufacturing, Quality Control, Quality Assurance, and R&D for stationary and field use.
A remote control software, including drivers and applications for LabVIEW and C, makes it easy
to integrate the instrument in test and measurement systems. The software package can be
downloaded from
All statements regarding safety of operation and technical data in this instruction manual will
only apply when the unit is operated correctly as it was designed for.
The power meter PM400 must not be operated in explosion endangered environments!
All modules, sensors and externally connected devices must only be operated with properly
shielded connection cables.
Only with written consent from Thorlabs may changes to single components be carried out or
components not supplied by Thorlabs be used.
Do not remove covers!
This precision device is only serviceable if properly packed into the complete original packaging
including the plastic foam sleeves. If necessary, ask for a replacement package.
Note
This equipment has been tested and found to comply with the limits for a Class A digital device,
pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment.
This equipment generates, uses, and can radiate radio frequency energy and, if not installed
and used in accordance with the instruction manual, may cause harmful interference to radio
communications. Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his own expense.
PM400-PMA post-mount adapter – fix to back with two M3 screws
·
PM400-AUXadapter card with GPIO ports and a sensor for ambient temperature and
relative humidity measurement.
·
TSP-TH external NTC (thermistor temperature sensor)
Please visit our homepage http://www.thorlabs.com for various accessories like fiber adapters,
posts and post holders, data sheets and further information.
1.3 Requirements
These are the requirements to the PC intended to be used for remote operation of the PM400.
Hardware Requirements
CPU:1 GHz or higher
RAM:256 MB
Graphic cardMin. 32 MB memory
Hard discMin 100 MB free storage space
Interfacefree USB2.0 port, USB cable according the USB 2.0 specification
Software Requirements
The PM400 software is compatible with the following operating systems:
·
Windows® XP (32-bit) SP3
·
Windows® Vista (32-bit, 64-bit)
·
Windows® 7 (32-bit, 64-bit)
·
Windows® 8.1 (32-bit, 64-bit)
·
Windows® 10 (32-bit, 64-bit)
For operation of the PM400, also an NI-VISA (version 5.4. or higher) is required. This NI-VISA
engines comes with the Thorlabs GmbH PM400 installation package, but can be downloaded
also from National Instruments' website www.ni.com. A LabVIEW Engine 2015 is included as
well.
Thorlabs DFU (Device Firmware Update) Wizard Version 2.6
Download the ZIP archive and extract the files to your computer. Below, the appropriate installation steps are shown fore installation to a Windows 7 64 bit operating system.
Note
The described below procedure applies to a computer without installed NI VISA 5.4.1 Runtime
and NI LabView Runtime 2015. If these components are installed already and correctly recognized, the installer skips the installation and resumes with Thorlabs software installation.
Start the installation by executing the file setup.exe as shown in above screenshot.
Click "Yes" to start installation.
Note
You need administrator privileges to install the software!
Select "I accept..." if you do so, then click "Next" to continue.
Click "Next" to continue.
You might be prompted to restart the computer. In order to ensure proper installation of subsequent components, it is strongly recommended to restart your computer now.
You might be prompted to restart the computer. In order to ensure proper installation of subsequent components, it is strongly recommended to restart your computer now.
Installing Thorlabs Software
After rebooting the computer, the installer continues automatically.
Note If the installation process does not resume automatically, please execute the setup.exe
Read the information, then click "Next". In the last window click "Finish". On the desktop three
new icons appear that allow to execute the installed software.
Switch on your PM400, and connect it to a free USB port using the USB cable that was attached. The required driver software is being installed.
For first use, connect the PM400 to a suitable charging device and charge the battery for
4 hours.
·
Connect the optical sensor (C-Series - red DSUB connector) to the DSUB jack (4) on the top
of the device.
·
Switch on the PM400.
·
The PM400 starts in the last view that was used before shutdown.
3.1 Measurement Screens
Needle Screen
Analog needle simulation with digital measurement value. The needle has a factor 10 zooming
function. Further, there are indicators for the extreme values that can be set to the actual value
by the reset key.
The lower display bar shows from left the set wavelength, status of Delta measurement and the
Numeric Display - Photodiode Sensor with External 10 dB Attenuator
Bandwidth Setting
Resolution of the digital
value
Toggle to change units
Display Update rate
Next Screen
Graph Display in Capturing Mode
Start / Stop Capturing
Show all results/
Roll latest
Open folder with captured
files
Analyze capture (Switch
to Viewer Mode)
Next Screen
Numerical Display
Numerical display with bar graph. This view has six additional small configurable displays with
additional, sensor specific information.
The sub-display configuration is accessible by drop down menus.
The lower display bar shows from left the set wavelength, status of Delta measurement and the
Zero compensation value.
Graph Display
The graph display allows to capture measurements over time and to analyze the results.
Tap on the measurement unit ("mW") to toggle between AUTO and MANUAL ranging.
When AUTO is enabled, the arrows are are shown in outlines.
mW
To switch from AUTO to manual, either tap on the measurement unit ("mW") or on one
of the arrows. When MANUAL is enabled, the arrows are are shown filled.
Depending on the detected sensor, the icon in the upper right corner allows to set specific features: Bandwidth setting (Photodiode sensors), Acceleration setting (Thermal
sensors) and Trigger level (Pyro-electric Energy sensors)
The Display Resolution can be set to 3, 4 or 5 significant digits.
Toggles between linear and logarithmic representation of the measurement results.
The Display Update Rate can be set to 10, 3 of 1 update per second.
3.2 Measurement Configuration
Ranging
The PM400 can be operated in AUTO and MANUAL ranging mode.
Press the button to enter the spectral correction menu.
This menu contains 12 entries, all of them are configurable. To edit an entry, press and hold it
for ~ 2 sec. The edit window comes up:
Now you can create an entry in either nanometers, micrometers or wavenumber or to load a
light spectrum curve in .csv format. Confirm and chose your entry
The actual wavelength setting value displays in the field above the button in Needle and Numerical measurement screens.
Press the button to enter the Delta Mode. The actual measurement value is set to zero,
saved as reference and the difference to the reference value. is displayed. The reference value
displays in the field above the operating button.
The scale-based indicators go to a middle setting.
3.5 Zeroing
Press the button to enter the Zeroing menu. Follow the displayed instructions.
After successful Zeroing, the Zero value is displayed in the field above the button in Need-
In order to take into account the attenuation of external devices (e.g. filter, beam splitter) to the
displayed measurement value, a correction factor can be assigned.
To enter the menu for the filter correction, press the ATTN button in the Numerical or Needle
screen:
A page with 12 free configurable presets comes up:
The attenuation can be assigned in "times" (e.g., "x2"), in percent, dB or in OD (optical density)
numbers. To edit an entry, press and hold it for ~2 seconds.
In this configuration window you can create an entry for an external filter etc. Further, there is
the possibility to load a complete filter transmission curve in .csv format. Press OK to confirm.
Then tap the edited entry to activate it. With active correction, the button displays in a different
color and shows the set value:
To disable the correction press and hold the ATTN button for 2 seconds, or chose an entry with
“OFF”.
Transmission curves of external filters (csv: wavelength, transmission)
¢
Translation files for language setting (UTF-8 w/o BOM: special format)
¢
Capturing files (csv: relative time, level)
¢
Screenshot images (bmp)
¢
Spectral curves of light sources (csv: wavelength, relative Intensity)
¢
Support document files and Software
3.7 Data Handling
The PM400 has an internal 4 GB flash memory that holds captured measurement data, specific
correction, and language files. This internal memory is allocated by default to the system.
For accessing or modifying these data externally, and adding or removing files, the memory can
be mounted to a USB link to a PC. Therefore, call the system menu and tap the icon "Owner
PM400".
The icon changes to "Owner USB" and an additional red ‘memory card’ icon appears in the
header bar. The connected PC recognizes the PM400 memory as a "Removable Disk" that can
be accessed from the Windows explorer:
This memory also contains the device manuals, drivers and applications.
In the Numerical screen, 6 subpanels can be configured in order to display additional results:
To configure a subpanel, tap to it and select from the drop-down list the desired parameter.
Please note, that additional parameters are sensor-dependent, as stated in the table below:
1
) - Available only if a sensor-internal temperature sensor is detected.
Lock / unlock GUI control; in Remote operation: performs GTL (Go To Local) command
Submenu Power Options
·
Dim Backlight and Auto-Shutdown on battery and mains operation
·
Battery state information
Submenu AUX IN / Out
·
Enable / Disable GPIO ports
Submenu Laser Calculator
·
Submenu Laser Calculator: Allows entering beam parameters for correct calculation of
the additional parameters
·
Submenu Unit Converter: Allows optical power conversion between W and dBm, wavelength conversion between wavelength, frequency, wave numbers and photon energy.
Submenu Date / Time
·
Set date and time
Submenu Capture Settings
·
Set long-time capture parameters: capture control (manual, time, number of samples) and
capture interval (10 ms to 60 s)
by connecting it to a PC USB port. In this case, the internal charging circuit enters the "Slow
Charge" mode at a max. current of 500 mA, as it usually delivered by a PC Standard USB
port.
·
by connecting it to a wall-plug charger as it comes with smart phones, tablets etc. These
chargers have a so called "Dedicated Charging Port". In this case, the PM400 enters the
high current charging mode, with a maximum current of 1 A.
With a connected PC or charger, the Battery Charging Indicator displays the charging status:
·
Red: The battery is charging.
·
Green: The battery is fully charged. Remove the charger under environmental aspects.
·
Red blinking: The connected charger is not compatible with the Dedicated Charging Port
specification. The battery is charged only with a current of about 100 mA.
3.11 Analog and Auxiliary I/O
Analog Out
The Analog Output jack provides the amplified photo-diode current or the amplified thermal or
pyroelectric sensor voltage. The signals from the analog output are not wavelength- and zerocorrected. The analog output voltage can range from 0 to +2.0V. It is is measurement range dependent and can be calculated to:
Auxiliary I/O
This 14 pin connector in the top panel gives access to four configurable general purpose input/output (GPIO) pins and two 10bit ADC inputs.
With the optional available environmental module that can be plugged into this connector it is
possible to monitor the room temperature and the relative humidity.
The PM400 optical power meter contains a USB 2.0 interface for remote control of the unit by
an external PC. Connect the unit via the Mini-USB connector in the top panel to a free USB port
of your PC.
Prior to connect the PM400, make sure that at least the NI-VISA Runtime 5.4.1 is installed to
the computer. This software is available on the National Instruments website www.ni.com, and
included with with the PM400 software package as well.
When connecting the PM400 first time, a new hardware will be found.
4.1 PM400 Utility Software
The PM400 comes with an utility software that easily enables remote operation of the PM400 as well as othe Thorlabs GmbH Power Meters - along with visualizing and logging of measurement data. The PM400 utility software does not require the installation of the instrument drivers
as described in section Using the Instrument Drivers.
After launching the PM400 utility program it will automatically screen for connected console devices. Select the desired device and press o.k. In case that the connected console is not yet
recognized, press Rescan to perform a new search for connected devices.
The identification string contains the following items:
USB0USB Port number
0x1313Thorlabs Vendor ID
0x8075Product ID = PM400
P5000102Instrument serial number
INSTRMeasurement instrument device
The display has a configurable display resolution. Independent
from the measurement range the display always has the full number of the selected digits.
To achieve best AD converter resolution it is necessary to set the
measurement range according to the signal to measure.
A trigger indicator shows whether the unit is sampling data ‘A’ indicator or a new measurement value gets displayed ‘T’ indicator
and green light.
Left Sub Display
The display has the following configurable items:
- no display
- maximum value - sampling until reset
- ratio max/min value - sampling until reset
- power or energy density
- alternate unit depending on connected sensor
Available choices depend on the connected sensor
Right Sub Display
The display has the following configurable items, the possible
choices depend on the connected sensor:
The bargraph indicator shows the incidence or the used measurement range.
Statistics screen
Statistical values in linear and logarithmic representation
Data logging screen
Shows the logging history data
Histogram Power /
Energy Histogram
- displays histogram data
Chart Display
Power/Energy Chart
Range button
Press to open a dialog box for setting the measurement range.
The indicator in the button shows the currently used measurement
range in the chosen unit. A green light indicates 'auto-ranging'
Shortcut: [Shift + F1]
Wavelength /
Response button
Press this button to open a dialog box for setting the correction
wavelength, or in adapter mode to enter the responsivity value in
A/W or V/W. The currently used parameter is indicated in the button label.
Shortcut: [Shift + F2]
Measurement configuration
button
Depending on the connected sensor the following parameters can
be set in the dialog box:
- display resolution - set number of digits
- averaging rate, a rate of 3000 averages the incoming measurement values for approx. 1 second
- photodiode bandwidth HI and LO
- acceleration circuit for thermal sensors ON, AUTO and OFF
- trigger level for pyroelectric sensors
- Zeroing for photodiode and thermal sensors
Shortcut: [Shift + F3]
Units / Display button
A dialog box with the following items appears:
- configure unit of measure, depending on the connected sensor [W, J, dBm, V and A]
- configure the left sub display
- configure the right sub display
Shortcut: [Shift + F4]
Logging configuration button
- Opens a dialog box to:
- set averaging rate for logging
- set interval between samples
- set number of samples
- configure logging into data file
Shortcut: Shift + F5
Start/Stop log button
- start and stop data logging
Shortcut: [Shift + F6]
Reset / Clear button
- reset min/max monitor
- clear power / energy graph
- clear power / energy histogram
- clear power / energy statistics
- clear log screen
Shortcut: [Shift + F7]
Quit button
- stops the PM400 application
- to restart press the white arrow in the tool bar
Shortcut: [Shift + F8]
- save / recall remote control specific parameters
Shortcut: [Shift + F9]
Long Term Measurement
- sets the device to local mode between the measurement intervals
Shortcut: [Shift + F10]
4.2 Using the Instrument Drivers
Instrument Driver Installation
The PM400 software package contains a set of instrument drivers that allows conveniently remote controlling the instrument in most common programming languages. The instrument drivers must be installed, please follow the setup dialog instructions.
Note
To successfully complete the install of the PM400 USB driver you must have Administrator privileges on the PC which you are performing the install.
Prior to connecting the PM400 with a PC, please check if NI-VISA is installed on the PC, otherwise install NI-VISA that is available for free from the National Instruments website www.ni.com
or from the data carrier that came with the instrument.
After successfully installing the drivers connect the PM400 to a USB port of your PC. The PC
will find a PM400 test and measurement device. Please follow the instructions of the dialog
screens and allow the installing.
Instrument Driver Example
The following LabVIEW example demonstrates how to use the instrument drivers for measurement tasks. The example is included on the data carrier that came with the instrument.
*.h (header file)
*.lib (static library)
or
.net wrapper dll
LabView
*.fp (function panel) and NI VISA instrument driver
Beside that, LabVIEW driver vi's are provided with the *.llb
container file
5 Write Your Own Application
In order to write your own application, you need a specific instrument driver and some tools for
use in different programming environments. The driver and tools are included in the installer
package and cannot be found as separate files on the installation CD.
In this section the location of drivers and files, required for programming in different environments, are given for installation under Windows XP (32 bit) and Windows 7 (32 and 64 bit)
Note
PM400 software and drivers contains 32 bit and 64 bit applications.
In 32 bit systems, only the 32 bit components are installed to
C:\Program Files\...
In 64 bit systems the 64 bit components are being installed to
C:\Program Files\...
while 32 bit components can be found at
C:\Program Files (x86)\...
In the table below you will find a summary of what files you need for particular programming environments.
Note
All above environments require also the NI VISA instrument driver dll !
During NI-VISA Runtime installation, a system environment variable VXIPNPPATH for including
files is created. It contains the information where the drivers are installed to, usually to C:
\Program Files\IVI Foundation\VISA\WinNT\.
This is the reason, why after installation of a NI-VISA Runtime a system reboot is required: This
environment variable is necessary for installation of the instrument driver software components.
In the next sections the location of above files is described in detail.
Thorlabs PM100x/PM160/PM200 Instrument Driver Sample Application with console interface.
Read the comment text in the sample.c file for more information.
This VI shows how to communicate with a PM400 optical power/energy meter with
SCPI commands. The following steps are demonstrated within this application:
- Initializing the instrument
- Getting system info
- Setting parameters
- Measurement configuration
- Measuring queue
- Fetching and displaying a measurement value
- Closing the application
5.4 Simple LabVIEW Example using SCPI commands
The PM400 Instrument driver is not required for this LabVIEW example.
Averaging Rate
Sets the averaging rate - 3000 averages take approximately 1s for performing a new
measurement value
Readout Config
Selects the measurement parameter
- POW power measurement in W
- CURR current measurement in A
- VOLT voltage measurement in V
- ENER energy measurement in J
- FREQ frequency / repetition rate measurement in Hz
- PDEN power density measurement in W/cm²
- EDEN energy density measurement in J/cm²
- RES thermistor resistance measurement in Ohm
- TEMP temperature measurement in °C
Stop
Stops application
Timeout [ms]
Sets a timeout value in ms that allows the instrument to sample.
The timeout must be longer than it takes to perform a new measurement. This has
especially to be considered when performing single shot energy measurements.
Error log
Error indicator, 'no error' is suppressed
Readout string
Formatted measurement value
- limitation to 4 significant digits
- SI notation
- '.' decimal separator
- appended unit according readout configuration
New
Indicator lights up, when a new measurement value is processed
Sensor Flags
Sensor flag bitmap:
1 Is power sensor
2 Is energy sensor
16 Response settable
32 Wavelength settable
64 Tau settable
256 Has temperature sensor
Sensor Name
Name of connected power/energy sensor
Sensor SN
Serial number of connected power/energy sensor
This section describes in detail the SCPI command set with respect to PM400 power meter
console. However, these commands are compatible with PM100A, PM100D and PM100USB
consoles as well as with the PM160 Hand-held Power Meter, except some console and sensor
related functions.
5.5.1 An Introduction to the SCPI language
The PM400 interface commands use the SCPI (Standard Commands for Programmable Instruments), an ASCII-based command language that was designed for test and measurement instruments.
SCPI commands are based on a hierarchical structure, also known as a tree system. In this
system, associated commands are grouped together under a common node or root, thus forming subsystems. A portion of the SENSE subsystem is shown below to illustrate the tree system.
The command syntax shows most commands (and some parameters) as a mixture of upperand lower-case letters. The upper-case letters indicate the abbreviated spelling for the com-
mand. For shorter program lines, send the abbreviated form. For better program readability,
send the long form.
For example, in the above syntax statement, CURR and CURRENT are both acceptable forms.
You can use upper- or lower-case letters. Therefore, CURRENT, current and Current are
all acceptable. Other forms, such as CUR and CURREN, will generate an error.
Braces ( { } ) enclose the parameter choices for a given command string. The braces are not
sent with the command string. A vertical bar ( | ) separates multiple parameter choices for a given command string.
Triangle brackets ( < > ) indicate that you must specify a value for the enclosed parameter. For
example, the above syntax statement shows the range parameter enclosed in triangle brackets.
The brackets are not sent with the command string. You must specify a value for the parameter
(such as "CURR:DC:RANG 50E-6").
Some parameters are enclosed in square brackets ( [ ] ). The brackets indicate that the
parameter is optional and can be omitted. The brackets are not sent with the command string.
In this example [:DC] can be omitted, so the command string can be shortened to
“CURR:RANG 50E-6”. If you do not specify a value for an optional parameter, the power/energy meter chooses a default value.
Command Separators
A colon ( : ) is used to separate a command keyword from a lower-level keyword. You must insert a blank space to separate a parameter from a command keyword. If a command requires
more than one parameter, you must separate adjacent parameters using a comma as shown
below:
"SYST:TIME 10, 34, 48"
A semicolon ( ; ) is used to separate commands within the same subsystem, and can also minimize typing. For example, sending the following command string:
"CORR:BEAM 1; WAV 1310"
... is the same as sending the following two commands:
"CORR:BEAM 1"
"CORR:WAV 1310"
Use a colon and a semicolon to link commands from different subsystems. For example, in the
following command string, an error is generated if you do not use both the colon and semicolon:
"CORR:BEAM 1;:AVER 300"
Using the MIN and MAX Parameters
You can substitute MINimum orMAXimum in place of a parameter for many commands. For ex-
ample, consider the following command:
Instead of selecting a specific current range, you can substitute MIN to set the range to its minimum value or MAX to set the range to its maximum value.
Querying Parameter Settings
You can query the current value of most parameters by adding a question mark (?) to the command. For example, the following command sets the operating wavelength to 1550 nm:
"CORR:WAV 1550"
You can query the operating wavelength by executing: "CORR:WAV?". You can also query the
minimum or maximum operating wavelength allowed as follows:
"CORR:WAV? MIN"
"CORR:WAV? MAX"
Caution
If you send two query commands without reading the response from the first, and then attempt
to read the second response, you may receive some data from the first response followed by
the complete second response. To avoid this, do not send a query command without reading
the response. When you cannot avoid this situation, send a device clear before sending the second query command.
SCPI Command Terminators
A command string sent to the power/energy meter must terminate with a <new line> character.
The IEEE-488 EOI (end-or-identify) message is interpreted as a <new line> character and can
be used to terminate a command string in place of a <new line> character. A <carriage return>
followed by a <new line> is also accepted. Command string termination will always reset the
current SCPI command path to the root level.
IEEE488.2 Common Commands
The IEEE-488.2 standard defines a set of common commands that perform functions like reset,
self-test, and status operations. Common commands always begin with an asterisk (*), are four
to five characters in length, and may include one or more parameters. The command keyword
is separated from the first parameter by a blank space. Use a semicolon (;) to separate multiple commands as shown below:
"*RST; *CLS; *ESE 32; *OPC?"
SCPI Parameter Types
The SCPI language defines several different data formats to be used in program messages
and response messages.
Numeric Parameters Commands that require numeric parameters will accept all commonly
used decimal representations of numbers including optional signs, decimal points, and scientific
notation.
Special values for numeric parameters like MINimum, MAXimum and DEFault are also accepted. You can also send engineering unit suffixes with numeric parameters (e.g., M,K, oru).
If only specific numeric values are accepted, the power/energy meter will automatically round
the input numeric parameters. The following command uses a numeric parameter:
Discrete Parameters Discrete parameters are used to program settings that have a limited
number of values (like W,DBM). They can have a short form and a long form just like command
keywords. You can mix upper- and lower-case letters. Query responses will always return the
short form in all upper-case letters. The following command uses discrete parameters:
POW:UNIT {W|DBM}
Boolean Parameters Boolean parameters represent a single binary condition that is either true
or false. For a false condition, the power/energy meter will accept “OFF” or “0”. For a true condition, the meter will accept “ON” or “1”. When you query a boolean setting, the instrument will
always return “0” or “1”. The following command uses a boolean parameter:
CURRent:RANGe:AUTO {OFF|0|ON|1}
String Parameters String parameters can contain virtually any set of ASCII characters. A string
must begin and end with matching quotes; either with a single quote or with a double quote.
You can include the quote delimiter as part of the string by typing it twice without any characters in between. The following command uses a string parameter:
Set the Operation Complete bit in the Standard Event Register
*OPC?
Operation complete query
Places a “1” into the output queue when all
device operations have been completed
*RST
Reset command
Returns the unit to the *RST default condition
*SRE
<NRf>
Service request enable command
Programs the Service Request Enable Register
*SRE?
Service request enable query
Reads the Service Request Enable Register
*STB?
Status byte query
Reads the Status Byte Register
*TST?
Self-test query
Performs the unit’s self-test and returns the result.
*WAI
Wait-to-continue command
Wait until all previous commands are executed
5.5.2 IEEE488.2 Common Commands
Common commands are device commands that are common to all devices according to the
IEEE488.2 standard. These commands are designed and defined by this standard. Most of the
commands are described in detail in this section. The following common commands associated
with the status structure are covered in the “Status Structure” section: *CLS, *ESE, *ESE?,
*ESR?, *SRE, *SRE?, *STB?
The identification code includes the manufacturer, model code, serial number, and firmware revision levels and is sent in the following format: THORLABS,MMM,SSS,X.X.X
Where:MMM is the model code
SSSis the serial number
X.X.X is the instrument firmware revision level
*OPC – operation complete - set OPC bit
*OPC? – operation complete query – places a “1” in output queue
When *OPC is sent, the OPC bit in the Standard Event Register will set after all pending command operations are complete. When *OPC? is sent, an ASCII “1” is placed in the Output
Queue after all pending command operations are complete.
Typically, either one of these commands is sent after the INITiate command. The INITiate command is used to take the instrument out of idle in order to perform measurements. While operating within the trigger model layers, many sent commands will not execute. After all programmed operations are completed, the instrument returns to the idle state at which time all pending
commands (including *OPC and/or *OPC?) are executed. After the last pending command is
executed, the OPC bit and/or an ASCII “1” is placed in the Output Queue.
When *OPC is sent, the OPC bit in the Standard Event Register will set after all pending command operations are complete. When *OPC? is sent, an ASCII “1” is placed in the Output
Queue after all pending command operations are complete.
*RST – reset – return instrument to defaults
When the *RST command is sent, the instrument performs the following operations:
·
Returns the instrument to the default conditions
·
Cancels all pending commands.
·
Cancels response to any previously received *OPC and *OPC? commands.
*TST? – self-test query – run self test and read result
Use this query command to perform the instrument self-test routine. The command places the
coded result in the Output Queue. A returned value of zero (0) indicates that the test passed,
other values indicate that the test failed.
*WAI – wait-to-continue – wait until previous commands are completed
The *WAI command is a no operation command for the instrument and thus, does not need to
be used. It is there for conformance to IEEE488.2.
Activate/deactivate the beeper. (SCPI Vol.2 §21.2.3)
:STATe?
Return the state of the the beeper (SCPI Vol.2 §21.2.3)
:ERRor
[:NEXT]?
Returns the latest <error code, “message”>. (SCPI Vol.2 §21.8.8)
:VERSion?
Query level of SCPI standard (1999.0) . (SCPI Vol.2 §21.21)
:DATE <year>,<month>,<day>
Sets the instrument’s calendar. (SCPI Vol.2 §21.7)
:DATE?
Query the instrument’s calendar. (SCPI Vol.2 §21.7)
:TIME <hour>,<min>,<sec>
Sets the instrument’s clock. (SCPI Vol.2 §21.19)
:TIME?
Query the instrument’s clock. (SCPI Vol.2 §21.19)
:LFRequency <numeric value>
Sets the instrument’s line frequency setting to 50 or 60Hz. (SCPI Vol.2
§21.13)
:LFRequency?
Query the instrument’s line frequency setting. (SCPI Vol.2 §21.13)
:SENSor
:IDN?
Query information about the connected sensor. This is a query only
command. The response consists of the following fields:
<name>,<sn>,<cal_msg>,<type>,<subtype>,<flags>
<name> Sensor name in string response format
<sn> Sensor serial number in string response format
<cal_msg>calibration message in string response format
<type> Sensor type in NR1 format
<subtype>Sensor subtype in NR1 format
<flags> Sensor flags as bitmap in NR1 format.
Flag:
Dec.value:
Is power sensor
1
Is energy sensor
2
Response settable
16
Wavelength settable
32
Tau settable
64
Has temperature sensor
256
5.5.2.3 PM400 specific SCPI Command Reference
See also SCPI Specification, Version 1999.0, May, 1999, http://www.scpiconsortium.org . All
commands with a ’SCPI’ checkmark are described in the SCPI specification.
All described commands work also with the PM100D, PM100A, PM100USB and PM160 instruments (with some limitations due to the hardware capabilities).
Sets the thermopile accelerator state
Queries the thermopile accelerator state
Sets the thermopile accelerator to auto mode
Queries thermopile accelerator auto mode
Sets thermopile time constant 0-63% in s
Protect the PM400 from adverse weather conditions. The PM400 is not water resistant.
Attention
To avoid damage to the instrument, do not expose it to spray, liquids or solvents!
The unit does not need a regular maintenance by the user. It does not contain any modules
and/or components that could be repaired by the user himself. If a malfunction occurs, please
contact Thorlabs GmbH for return instructions.
Also, please contact Thorlabs GmbH for replacement of the rechargeable battery:
Do not remove covers!
6.1 Version Information
The System Info screen of the PM400 shows important information:
The PM400 is capable to support custom made detectors. Please read carefully the following
instruction prior to connecting a self made sensor.
PinConnection
3AGND (analog ground): photodiode ground (anode), thermal and pyro sensor
ground
4photodiode cathode
5pyroelectric sensor +
8thermal sensor +
7PRESENT: Connect this pin via a 1kΩ – 10kΩ resistor to pin 3 (AGND) to ena-
ble a custom sensor
1+5V (max. current 100 mA from this pin)
6DGND (digital ground)
9n.c.
Warning
Pin 2 is uniquely used for the EEPROM Digital I/O (memory in Thorlabs sensor heads) and
MUST NOT be used. Connecting this pin may cause malfunction of the PM400.
Thorlabs GmbH warrants material and production of the PM400 for a period of 24 months starting with the date of shipment. During this warranty period Thorlabs GmbH will see to defaults
by repair or by exchange if these are entitled to warranty.
For warranty repairs or service the unit must be sent back to Thorlabs GmbH. The customer will
carry the shipping costs to Thorlabs GmbH, in case of warranty repairs Thorlabs GmbH will carry the shipping costs back to the customer.
If no warranty repair is applicable the customer also has to carry the costs for back shipment.
In case of shipment from outside EU duties, taxes etc. which should arise have to be carried by
the customer.
Thorlabs GmbH warrants the hard- and/or software determined by Thorlabs GmbH for this unit
to operate fault-free provided that they are handled according to our requirements. However,
Thorlabs GmbH does not warrant a fault free and uninterrupted operation of the unit, of the
software or firmware for special applications nor this instruction manual to be error free. Thorlabs GmbH is not liable for consequential damages.
Restriction of warranty
The warranty mentioned before does not cover errors and defects being the result of improper
treatment, software or interface not supplied by us, modification, misuse or operation outside
the defined ambient stated by us or unauthorized maintenance.
Further claims will not be consented to and will not be acknowledged. Thorlabs GmbH does explicitly not warrant the usability or the economical use for certain cases of application.
Thorlabs GmbH reserves the right to change this instruction manual or the technical data of the
described unit at any time.
Thorlabs GmbH has taken every possible care in preparing this document. We however assume no liability for the content, completeness or quality of the information contained therein. The
content of this document is regularly updated and adapted to reflect the current status of the
hardware and/or software. We furthermore do not guarantee that this product will function without errors, even if the stated specifications are adhered to.
Under no circumstances can we guarantee that a particular objective can be achieved with the
purchase of this product.
Insofar as permitted under statutory regulations, we assume no liability for direct damage, indirect damage or damages suffered by third parties resulting from the purchase of this product. In
no event shall any liability exceed the purchase price of the product.
Please note that the content of this document is neither part of any previous or existing agreement, promise, representation or legal relationship, nor an alteration or amendment thereof. All
obligations of Thorlabs GmbH result from the respective contract of sale, which also includes
the complete and exclusively applicable warranty regulations. These contractual warranty regulations are neither extended nor limited by the information contained in this document. Should
you require further information on this product, or encounter specific problems that are not discussed in sufficient detail in the document, please contact your local Thorlabs GmbH dealer or
system installer.
All rights reserved. This document may not be reproduced, transmitted or translated to another
language, either as a whole or in parts, without the prior written permission of Thorlabs GmbH.
As required by the WEEE (Waste Electrical and Electronic Equipment Directive) of the European Community and the corresponding national laws, Thorlabs GmbH offers all end users in
the EC the possibility to return “end of life” units without incurring disposal charges.
This offer is valid for Thorlabs GmbH electrical and electronic equipment
·
sold after August 13th 2005
·
marked correspondingly with the crossed out “wheelie bin” logo (see figure below)
·
sold to a company or institute within the EC
·
currently owned by a company or institute within the EC
·
still complete, not disassembled and not contaminated
As the WEEE directive applies to self contained operational electrical and electronic products,
this “end of life” take back service does not refer to other Thorlabs GmbH products, such as
·
pure OEM products, that means assemblies to be built into a unit by the user (e. g. OEM
laser driver cards)
·
components
·
mechanics and optics
·
left over parts of units disassembled by the user (PCB’s, housings etc.).
Waste treatment on your own responsibility
If you do not return an “end of life” unit to Thorlabs GmbH, you must hand it to a company specialized in waste recovery. Do not dispose of the unit in a litter bin or at a public waste disposal
site.
WEEE Number (Germany) : DE97581288
Ecological background
It is well known that waste treatment pollutes the environment by releasing toxic products during decomposition. The aim of the European RoHS Directive is to reduce the content of toxic
substances in electronic products in the future.
The intent of the WEEE Directive is to enforce the recycling of WEEE. A controlled recycling of
end-of-life products will thereby avoid negative impacts on the environment.