Create an Account  |   Log In

View All »Matching Part Numbers


Your Shopping Cart is Empty
         

Shack-Hartmann Wavefront Sensors, 1.3 Megapixel Resolution


  • CCD Sensor with 1.3 Megapixel Resolution
  • Sensitivities up to λ/150
  • Wavelength Ranges of 300 - 1100 nm or 400 - 900 nm
  • Kits Available with Interchangable Microlens Arrays

WFS150-5C

Includes Post-Mounting Adapter

Application Idea

A WFS150-5C Mounted
on the KM100WFS
Kinematic Mount

Related Items


Please Wait
Shack-Hartmann Wavefront Sensor Selection Guide
  Max Speeda Wavefront
Accuracya
Wavefront
Sensitivitya
CCD Wavefront Sensor Up to 15 Hz Up to λ/50 Up to λ/150
High-Speed, CMOS Wavefront Sensor Up to 1120 Hz Up to λ/60 Up to λ/200
  • Dependent on Microlens Array

Operation Principles

Distorted Wavefront

Click to Enlarge
Schematic of a Mircrolens Array Focusing a Distorted Wavefront


The Shack-Hartmann sensor consists of a lenslet array and a camera. When a wavefront enters the lenslet array, a spotfield is created on the camera; each spot is then analyzed for intensity and location. Using this method, Shack-Hartmann wavefront sensors can dynamically measure the wavefronts of laser sources or characterize the wavefront distortion caused by optical components. In addition, they can provide real-time feedback for adaptive optics systems and are included for this reason in Thorlabs' Adaptive Optics Kits. For more details on the theory of Shack-Hartmann wavefront sensing, see the SH Tutorial tab above.

Features

  • CCD Camera Provides 1.3 Megapixel Resolution
  • Real-Time Wavefront and Intensity Distribution Measurements
  • Includes Interchangeable High-Quality Photolithographic Microlens Array
  • Nearly Diffraction-Limited Spot Size
  • Use with CW or Pulsed Light Sources
  • USB Connection to PC
  • Live Data Readout via TCP/IP
  • Compact Housing: 45.5 mm x 32.0 mm x 40.4 mm with Baseplate
  • Flexible Software Options
    • GUI Software
    • Instrument Driver Package for C Compilers
    • LabWindows™/CVI
    • LabVIEW™
    • DotNet
  • Kinematic Mount Designed for Wavefront Sensors Available Separately (See Below)

Thorlabs' High-Resolution Shack-Hartmann Wavefront Sensors, which incorporate CCD cameras with 1.3 megapixel resolution, provide accurate measurements of the wavefront shape and intensity distribution of beams. These wavefront sensors are available with either a chrome-masked microlens array for use in the 300 - 1100 nm range or an AR-coated microlens array for use in the 400 - 900 nm range. The former has a lenslet pitch of 150 µm whereas the latter is available with a lenslet pitch of either 150 or 300 µm. These three offerings allow the end user to select a system that offers high spatial resolution, enhanced contrast, or high wavefront accuracy. Please note that calibration of the microlens-camera pair is required; to purchase a new lenslet array for a previously purchased Shack-Hartmann Wavefront Sensor, please contact Technical Support for a quotation on the microlens array and calibration service.

If your application would benefit from a fast wavefront sensor, please see our line of Shack-Hartmann wavefront sensors with frame rates up to 1120 Hz. For more information about choosing the appropriate Shack-Hartmann wavefront sensor for a particular application, see the Selection Guide tab above.

Shack-Hartmann Kits with Two Microlens Arrays
Thorlabs also offers wavefront sensor kits (Item # WFS-K1 and WFS-K2) that include two microlens arrays and the base CCD camera unit loaded with the appropriate calibration data for the two lenslet arrays. Switching lenses is easy using the provided pick-up tool; the patented magnetic holder (US Patent No: 8,289,504) precisely positions the array correctly every time. These kits are ideal for situations where more than one light source or optical setup needs to be analyzed.

AO Kit Setup
Click to Enlarge

Select wavefront sensors are available in our adaptive optics kits, shown above.

Accessories
Each Shack-Hartmann Wavefront Sensor and Kit comes in a convenient storage and carrying case. Mounting accessories include an SM1A9 C-Mount to internal SM1 (1.035"-40) thread adapter for mounting Ø1" lens tubes and mounted optics, such as Neutral Density Filters, and a base plate for attaching Ø1/2" posts.

GUI Software
The included software package offers a user-friendly graphical interface with tools for choosing camera setting, calibration, analysis, and display options. All sensors require a USB2.0 port to operate. The software also includes drivers for C compilers, LabVIEW™, LabWindows/CVI™, and DotNet for integration into custom system control and data collection software. For more information on the included software or to download the latest version, see the Software tab above.

Adaptive Optics Kits
In an effort to bring adaptive optics to even more research fields, Thorlabs has partnered with Boston Micromachines Corporation (BMC) to provide adaptive optics kits. These kits bundle the three primary components for any adaptive optics system: a Multi-DM MEMS deformable mirror system, a WFS150-5C Shack-Hartmann Wavefront Sensor, and real-time control software. In addition, the kits (shown in the photo to the right) also include a light source, all collimation/imaging optics, and all mounting hardware necessary (breadboard not included). These kits are specifically designed to provide an affordable, easy-to-use adaptive optics solution that can be integrated into a research system in hours instead of months.

Camera Specifications

Item #WFS150-5CWFS150-7ARWFS300-14AR
Detector Array Type CCD
Camera Resolution (Max) 1280 x 1024 Pixels, Selectable
Pixel Size 4.65 µm x 4.65 µm
Aperture Size (Max) 5.95 mm x 4.76 mm
Frame Rate (Max) 15 Hz
Exposure Range 79 µs - 65 ms
Shutter Globala
Image Digitization 8 Bit
  • A global shutter exposes the entire detector at one time.

Microlens Array Specifications

Item #WFS150-5CWFS150-7ARWFS300-14AR
Wavelength Range 300 nm - 1100 nm 400 nm - 900 nm 400 nm - 900 nm
Effective Focal Length (When Mounted in WFS) 3.7 mm 5.2 mm 14.2 mm
Nominal Focal Length 5.2 mm 6.7 mm 18.6 mm
Reflectivity <25% <1% <1%
Number of Active Lenslets Selectable by Software, Depending on Microlens Array
Number of Active Lenslets (Max) 39 x 31 19 x 15
Substrate Material Fused Silica (Quartz)
Free Aperture Ø9 mm
Lenslet Grid Type Square Grid
Lenslet Pitch 150 µm 300 µm
Lens Shapea Round, Plano-Convex Spherical Square, Plano-Convex Parabolic
Fill Factor (Approximate)b 74.5% 100%
Lens Size Ø146 µm 300 µm x 300 µm
Coating Chrome Mask Anti-Reflection
Array Size 10 mm x 10 mm x 1.2 mm
  • The convex surfaces face the camera.
  • The Fill Factor is a measure of the fraction of incident light reaching the detector. For the WFS150-5C and WFS150-7AR, the fill factor is less than 100% because the round lenses are arranged on a square grid.

General Specifications

Item #WFS150-5CWFS150-7ARWFS300-14AR
Wavefront Accuracya λ/15 rms @ 633 nm λ/50 rms @ 633 nm
Wavefront Sensitivityb λ/50 rms @ 633 nm λ/150 rms @ 633 nm
Wavefront Dynamic Rangec >100λ @ 633 nm >50λ @ 633 nm
Local Wavefront Curvatured >7.4 mm >10.0 mm >40.0 mm
Optical Input Connector C-Mount
Physical Size (H x W x D) 40.4 mm x 32.0 mm x 45.5 mm
Power Supply <1.5 W via USB
Operating Temperature +5 to +35 °C (Non-condensing)
Storage Temperature -40 to +70 °C
External Trigger Input Specifications
Save Static Voltage Level 0 to 30 V DC
Low Level 0 to 2.0 V
High Level 5.0 V to 24 V
Trigger Slope Software Selectable: Low-High or High-Low
Input Current (Max) 10 mA
Pulse Width (Min) 100 µs
Slew Rate (Min) 35 V / msec
  • Absolute accuracy using internal reference. Measured for spherical wavefronts with a known radius of curvature.
  • Typical relative accuracy with respect to a reference wavefront (user calibration). Reference and each measurement values are averaged over 10 frames.
  • Peak-to-valley wavefront deformation over entire aperture of wavefront sensor.
  • Radius of wavefront curvature over single lenslet aperture.

All technical data are valid at 23 ± 5 °C and 45 ± 15% relative humidity (non-condensing).

How a Shack-Hartmann Wavefront Sensor Works

A Shack-Hartmann wavefront sensor uses a lenslet array to divide an incoming wavefront into an array of smaller beams. Each beam is focused onto a CMOS camera that is placed at the focal plane of the lenslet array, as shown in the figure to the left. If a uniform, planar wavefront is incident on the Shack-Hartmann sensor, each lenslet forms a spot along the optical axis of the lenslet. This yields a regularly spaced grid of spots on the detector.

A distorted wavefront, however, will cause some lenslets to focus with the spots displaced from the optical axis. Therefore, the light imaged on the sensor will consist of some regularly spaced spots mixed with displaced spots and missing spots. This information can be used to calculate the shape of the wavefront that was incident on the microlens array. Shack- Hartmann type wavefront sensors can be used to characterize the performance of optical systems. In addition, they are increasingly used in applications where real-time monitoring of the wavefront is used to control an adaptive optic with the intent of removing the wavefront distortion before creating an image.

Wavefront Distortion and Spot Displacement

As discussed above, each microlens of the lenslet array collects the light falling onto its aperture and generates a single spot at the detector plane. The figure below is a detail of a wavefront incident on a single microlens. The spot positions will be directly behind the lenses (shown in green) only if the incident wavefront is flat and parallel to the plane of the lenslets. For a wavefront which is distorted in the region of the microlens, the spot positions will be deviated in the X and Y direction (as shown by the red dot) so that every spot lies away from the optical axis z of its associated microlens by an angle θ. This angle θ is the same as the angle between the distorted wavefront and the planar wavefront, as shown in the figure.

Single Microlens Focusing

Parameters Affecting Shack-Hartmann Performance

Four parameters that influence the performance of a Shack-Hartmann wavefront sensor are the number of lenslets that cover the detector active area, the dynamic range, the measurement sensitivity, and the lenslet focal length. The number of lenslets restricts the maximum number of Zernike coefficients that a reconstruction algorithm can reliably calculate. When selecting the number of lenslets required, consider the amount of distortion being modeled (i.e., how many Zernike coefficients are needed to effectively represent the true wave aberration).

Sensitivity (αmin) is a function of the minimum detectable spot displacement (δymin), as described by the equation:

αmin = δymin / f

where f is the focal length of the microlens. Dynamic range, θmax, is a measure of the maximum extent of phase that can be measured:

αmax = δymax / f = (d / 2) / f

where d is the diameter of the microlens. Both of these equations were derived using the small angle approximation. αmin is the minimum detectable wavefront slope that can be measured by the wavefront sensor. The minimum detectable spot displacement δymin depends on the pixel size of the detector, the accuracy of the centroid algorithm, and the signal to noise ratio of the sensor. αmax is the maximum wavefront slope that can be measured by the wavefront sensor and corresponds to a spot displacement of δymax, which is equal to the lenslet radius.

A Shack-Hartmann sensor's measurement accuracy (i.e., the minimum wavefront slope that can be measured reliably) depends on its ability to precisely measure the displacement of a focused spot with respect to a reference position. A conventional algorithm will fail to determine the correct centroid of a spot if it partially overlaps another spot or if the focal spot of a lenslet falls outside of the area of the sensor assigned to detect it (spot crossover). Special algorithms can be implemented to overcome these problems, but the limit the dynamic range of the sensor. The dynamic range of a system can be increased by using a lenslet with either a larger diameter or a shorter focal length. Increasing the dynamic range by increasing the lenslet diameter decreases the number of Zernike coefficients available to represent the wavefront. Conversely, increasing the dynamic range by shortening the focal length decreases the sensor's sensitivity. Ideally, a lenslet with the longest focal length that meets both the dynamic range and measurement sensitivity requirements should be used.

The Shack-Hartmann wavefront sensor is capable of providing information about the intensity profile as well as the calculated wavefront.

Shack-Hartmann Wavefront Sensor Selection Guide
  Max Speeda Wavefront Accuracya Wavefront Sensitivitya
CCD Wavefront Sensor Up to 15 Hz Up to λ/50 Up to λ/150
High-Speed, CMOS Wavefront Sensor Up to 1120 Hz Up to λ/60 Up to λ/200
  • Dependent on Microlens Array

Selecting a Shack-Hartmann Wavefront Sensor

Thorlabs offers two different cameras for a variety of wavefront sensing applications. The wavefront sensors on this page feature a high-speed CMOS camera capable of reaching frame rates up to 1120 Hz (microlens array dependent). Thorlabs also offers a line of Shack-Hartmann wavefront sensors with a CCD camera. Each camera type is available with one of three microlens arrays offering flexibility in wavelength range, spatial resolution, spot contrast, and wavefront accuracy.

CCD sensors exhibit lower noise and higher image uniformity, but provide much slower frame rates compared to CMOS-based wavefront sensors. The high frame rate of the CMOS detector enables more wavefront measurements per second and thus can detect faster wavefront fluctuations, an important feature for sensors used in high-speed adaptive optics systems.

Measurement Speed

The CCD-based wavefront sensors have a measurement speed of 15 fps that is independent of the spot count (i.e. independent of the microlens array pitch). By contrast, the measurement speed of the wavefront sensors with CMOS cameras will decrease as the spot count increases. The plots below provide a comparison of performance of the CMOS sensor when used with the 150 µm and 300 µm pitch microlens arrays.

The WFS20 CMOS-based wavefront sensors support three different measurement modes. In the normal measurement mode, the entire spotfield image is transmitted to the PC. This mode can also be used with 2X binning, reducing the amount of data that needs to be transfered to the PC and increasing the measurement speed. In this mode, the spot location is still reported based on the real camera pixel array. Alternatively, the sensor can be used in a "High-Speed Mode" where the wavefront calculations are carried out in the control box and only the centroid locations are transmitted to the PC. This greatly decreases the amount of data that needs to be tranferred to the PC and provides the fastest measurement speeds. However, since the spotfield image is not transferred to the PC, it is harder to detect certain errors, such as those caused by camera saturation.

Choosing a Microlens Array

Each Shack-Hartmann Wavefront Sensor is available with 3 different microlens arrays. The table to the lower right details the features of the microlens included with each item.

Features of WFS Microlens Arrays
Microlens Array # High Spot Contrast High Wavefront Accuracy High Spatial Resolution Low Back Reflection
MLA150M-5C  Yes!    Yes!  
MLA150M-7AR      Yes!  Yes!
MLA300M-14AR    Yes!    Yes!

MLA150M-5C Microlens Features

This microlens array includes a chrome mask that prevents light from passing between the microlenses. This leads to a higher contrast in the spot field but will considerably increase the amount of back reflections. This microlens array can be used over an extended wavelength range of 300 nm to 1100 nm. The array features a 150 µm lens pitch, which offers a larger number of spots and thus a higher spatial resolution of the wavefront, and a wider wavefront dynamic range because of their shorter focal length.

MLA150M-7AR and MLA300M-14AR Microlens Features

Both of these microlens arrays are AR coated for the 400 nm to 900 nm wavelength range, making them ideal for applications that are sensitive to back reflections. The MLA150M-7AR microlens array has a 150 µm lens pitch, which offers a larger number of spots and thus a higher spatial resolution of the wavefront, and a wider wavefront dynamic range because of their shorter focal length. The MLA300M-14AR has a 300 µm lens pitch that supports higher wavefront accuracy and sensitivity at the expense of dynamic range and spatial resolution.

Microlens Arrays
Microlens Array # MLA150M-5Ca MLA150M-7ARa MLA300M-14ARa
Coating Chrome Masked for 300 - 1100 nm AR Coated for 400 - 900 nm
Lenslet Pitch 150 µm 300 µm
Wavefront Sensor Item #
WFS20-5C(/M)
WFS150-5C
 Yes!    
WFS20-7AR(/M)
WFS150-7AR
   Yes!  
WFS20-14AR(/M)
WFS150-14AR
     Yes!
WFS20-K1(/M)
WFS150-K1
 Yes!    Yes!
WFS20-K2(/M)
WFS150-K2
   Yes!  Yes!
  • The microlens array # refers to the identifier printed on the front of the microlens array housing(s) and cannot be ordered independently of a WFS20 sensor.

Software Update**

Version 4.6.3 (February 5, 2016)

This is the Advanced Beta Version of the wavefront sensor software package for Windows™ Vista, 7, 8.1, or later (32 or 64 bit).

  • Ability to Save Spotfield Data to Various File Types
Software Download

Software

Version 4.6.0 (November 4, 2015)

The wavefront sensor software package for Windows™ Vista, 7, 8.1, or later (32 or 64 bit).

Software Download

Software Download

Click on the Software button to the right for the latest version of Thorlabs' Shack-Hartmann Wavefront Sensor Software Package. The download includes the software package with a graphical user interface for operating the WFS in standard applications and support for developers who want to extend or adapt the functionality of the device to their special requirements.

System Requirements:

  • Windows™ Vista, 7, 8.1, or Later (32 or 64 Bit)
  • USB 2.0 or 3.0* Port
  • Graphic Resolution: 1024 x 768 Min

*When used with USB 3.0, the WFS150 and WFS300 wavefront sensors operate with reduced speed and increased minimum exposure times.

**This is the Advanced Beta Version, also known as a Release Candidate, of Thorlabs' Wavefront Sensor Software. It is provided as is for users who would benefit from the additional functionality. This software version has undergone preliminary bug testing. If it passes further tests without issue, it will eventually be released as the next official version of the wavefront sensor software.

Wavefront Display
GUI Display of Measured Wavefront

Software and Graphical User Interface

Display/Output Options
For screen images of the GUI display options, please click on the links:

Calculated Parameters

  • Beam Centroid and Diameter
  • Modal and Zonal Reconstructed Wavefront
  • Max Variance of Wavefront, Peak-to-Valley (PV), and RMS of Wavefront
  • Zernike Representations of Tilt, Defocus, Astigmatism,
    Coma, Spherical, and Higher Order Aberrations
  • Fourier and Optometric Parameters

Included Drivers

The software includes a driver package for constructing custom applications with the following software packages:

  • C Compilers
  • LabWindows™/CVI
  • LabVIEW™
  • DotNet

Please Give Us Your Feedback
 
Email Feedback On
(Optional)
Contact Me:
Your email address will NOT be displayed.
 
 
Please type the following key into the field to submit this form:
Click Here if you can not read the security code.
This code is to prevent automated spamming of our site
Thank you for your understanding.
  
 
Would this product be useful to you?   Little Use  1234Very Useful

Enter Comments Below:
 
Characters remaining  8000   
Posted Comments:
Poster:swick
Posted Date:2017-09-19 03:51:52.0
This is a response from Sebastian at Thorlabs. Thank you for the inquiry. In theory it is possible to evaluate beam parameters along the propagation axis by using wavefront, beam diameter and power distribution measured at one position. However, currently the WFS Software does not support this kind of feature. We are looking into adding this option.
Poster:e0004149
Posted Date:2017-06-15 21:37:52.037
Greetings Sir/Ma'am: My lab has recently purchased a WFS150-7AR. We require a way to extract information from the WFS in a similar way to the sample.exe file that was provided during the installation, with a few settings different (such as displaying more Zernike orders). However, attempts to run the exe file compiled from sample.c fails saying that it is not compatible with the version of Windows 10 x64 that we are running. Is there a fix to this? Details: -I have included the following files in the folder with the C script: nivisa64.lib sample.c visa.h visatype.h vpptype.h WFS.h WFS_64.lib -The only edit I made to sample.c was to change #include "wfs.h" to #include "WFS.h" -The compiler I used was GCC and this was the line I ran in the command line in the working directory of the folder containing sample.c: gcc -L "C:\Program Files (x86)\IVI Foundation\VISA\WinNT" - Wall -g -S sample.c -o sample1.exe -My OS is Windows 10 x64 Please pardon me if there are any amateur mistakes as I am new to C. Thank you in advance. Best Regards.
Poster:wskopalik
Posted Date:2017-06-16 10:45:43.0
This is a response from Wolfgang at Thorlabs. Thank you very much for your inquiry. The software and the drivers of the wavefront sensors are compatible to Windows 10. So your OS shouldn't be the problem. I assume that there might be an issue with the compilation of the file. I have contacted you directly to provide further assistance and to discuss this in more detail.
Poster:
Posted Date:2017-02-26 22:37:38.567
Dear Mr/Ms I know that I can save centroids of my desire wavefront by using the available option in file menu. But I am wondering how I can have reference plane wavefront centroids? I really appreciate it if you can help me. Best regards
Poster:swick
Posted Date:2017-02-28 03:33:50.0
This is a response from Sebastian at Thorlabs. Thank you for the inquiry. Before a User Calibration is applied please activate the 'User Calibrated Reference'. Then, you will be informed that such a default reference is created and saved to the application directory: C:\Users\current_user\Documents\Thorlabs\Wavefront Sensor\Reference The user reference file name is automatically composed of the WFS serial number, MLA name, Camera resolution index. In the manual on page 64 you can find further information. Alternatively you can use the command WFS_GetSpotReferencePositions. After installing the WFS software you can find the manual for functions and commands at C:/Program Files (x86)/IVI Foundation/VISA/WinNT/WFS/Manual/ Unfortunately, you have not left your contact details, so if you have further questions please contact our Technical Support.
Poster:joon
Posted Date:2016-10-21 20:40:12.473
Can your software handle uncircular apertures? Like donut shape? More specifically, hubble telescope aperture?
Poster:wskopalik
Posted Date:2016-10-25 09:17:47.0
This is a response from Wolfgang at Thorlabs. Thank you for your inquiry. Unfortunately, the algorithm for the calculation of the Zernike coefficients doesn't work well with donut-shaped beams. The reconstruction of the wavefront starts in the center of the beam. So if the center is missing, the results are either not reliable or the algorithm will even fail. Ideally, the pupil over which the Zernike coefficients in the software are calculated is completely filled. I have contacted you directly to provide further assistance.
Poster:rawoodruff
Posted Date:2016-09-18 00:17:12.43
We are considering using a Thorlabs Shack-Hartmann on a 1 meter diameter telescope viewing stars. Does it have sufficient sensitivity to determine wavefront error of a telescope at starlight levels of light? What photon count level is needed for it to operate at its wavefront sensitivity?
Poster:tom.sosnowski
Posted Date:2017-09-12 09:53:49.847
I have a question about the software for the Shack-Hartmann sensors. We are imaging Gaussian beams with low M^2 (typically less than 1.3) and the information we would really like to get from the software is the waist size and waist location of the measured beam. Does the software display that information, or is there a simple calculation from the measured data that can provide that information? (I realize you would have to input a wavelength value to do the calculation.) An estimate of the M^2 of the beam would also be nice, but not critical. Thanks for any help. Tom Sosnowski
Poster:swick
Posted Date:2016-09-21 09:37:56.0
This is a response from Sebastian at Thorlabs. Thank you very much for your inquiry. The min. detectable power with software version 4.6.3 is approx. 0.1 nW (WFS300-14AR, exposure time 65 ms, Gain = 5). I will contact you directly to discuss if our Shack-Hartmann Wavefront Sensors meet the requirements of your application.
Poster:muhamet.ibrahimi
Posted Date:2016-08-31 10:24:42.927
Dear Thorlabs, I am planning to make use of a WF Sensor for constructing a LFM. It is essential for me to know how and why does Effective Focal Length (When Mounted in WFS) change from the Nominal Focal Length. Regards
Poster:swick
Posted Date:2016-09-01 03:19:06.0
This is a response from Sebastian at Thorlabs. Thank you for your inquiry. The nominal focal length gets calculated from the nominal lenslet radius. Practical tests showed that for the sharpest spots the optimal distance between lenslets and the sensor chip is different. Therefore, the lenslet array is mounted at this distance which is called the effective focal length. This is the value which needs to be used in calculations too.
Poster:ryan.downey0
Posted Date:2016-07-27 14:26:31.327
Dear Thorlabs, I am trying to interface with your wavefront sensor in Matlab using the DotNet interface provided in the file WFS_Interlop64.dll. I am able to load the .dll file and call its constructor method, but when I try to call any of the other methods I recieve the error: Message: An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B) Source: Thorlabs.WFS.Interop64 HelpLink: I am using a 64bit computer running Matlab_R2016a(64bit). Do you have any advice on what to do about this error and how to interface with the WFS in Matlab. Sincerely, Ryan Downey Code Snippet: NET.addAssembly('C:\Program Files (x86)\Microsoft.NET\Primary Interop Assemblies\Thorlabs.WFS.Interop64.dll'); import Thorlabs.WFS.* import System.* wfsInstHandle = System.IntPtr; wfs = WFS(wfsInstHandle); wfs.GetInstrumentListLen();
Poster:shallwig
Posted Date:2016-07-28 02:18:24.0
This is a response from Stefan at Thorlabs. Thank you for contacting us, we will contact you directly to troubleshoot this in detail
Poster:ryan.downey0
Posted Date:2016-06-20 09:42:39.063
Dear Thorlabs, Is there a way to process wavefront sensor images in either C or Matlab and use the processed images to calculate zernike coefficients. Specifically, I want to subtract an image created by a stray beam from my main image and I noticed that the manual says not to modify the image buffer. Thanks, Ryan Downey Montana State University
Poster:shallwig
Posted Date:2016-06-23 06:05:35.0
This is a response from Stefan at Thorlabs. Thank you very much for your inquiry. In general you can use our WFS with Matlab and C but it is not possible to load modified images back into our driver for further calculations. Alternatively you can use other featuers of the WFS driver to suppress unwanted stray light. With WFS_SetBlackLevelOffset() the camera offset should be set to the minimum value (zero). With WFS_CutImageNoiseFloor() an intensity value can be set, below this value all intensities will be set to zero. I have contacted you directly to check your application in more detail.
Poster:
Posted Date:2016-05-26 07:51:04.69
I'm ordering a WFS150-7AR with trigger cable. In the manual I can see that the trigger input has an optocoupler, which means I need to put a resistor in series to define the current through the optocoupler's LED. Can you tell me the rated current of the optocoupler input, or alternatively a recommended resistor value for 5V trigger levels.
Poster:besembeson
Posted Date:2016-05-27 05:49:52.0
Response from Bweh at Thorlabs USA: We do provide the external trigger Input voltage specifications at the following page of the manual: http://www.thorlabs.com/thorcat/MTN/WFS150-7AR-Manual.pdf#page=104 Typical TTL signal levels will be suitable. Please contact me at techsupport@thorlabs.com if you have further questions.
Poster:g.makey
Posted Date:2016-03-28 09:57:24.92
Hi, I am building Matlab interface to your WFS for microscopy application. As my program deals directly with spot field (Raw data from WFS), could you please send me the spot field of your plane-wave reference wavefront? Best regards, Ghaith
Poster:besembeson
Posted Date:2016-03-28 09:20:53.0
Response from Bweh at Thorlabs USA: We will contact you directly to provide this.
Poster:tdzamba
Posted Date:2016-03-15 14:22:58.763
Is it possible to raise the exposure time past 66.501ms? I am trying to measure the wave front of a relatively dim beam, and I am having a hard time getting the intensity high enough.
Poster:tschalk
Posted Date:2016-03-17 10:10:53.0
This is a response from Thomas at Thorlabs. It is not possible to increase the exposure time to higher values. We are currently working on a USB 3.0 WFS and with this unit it will be possible to achieve higher exposure times. I will also contact you directly with more detailed information.
Poster:rrahn
Posted Date:2016-02-02 00:41:06.693
I am running camera/MLA with Matlab (2015B). I cannot save or load a reference file from Matlab, even after saving a ref file using WFS 4.6.0. Other functions work. Code snippet: function obj = WFS_Camera UsedDeviceStr = ['USB::0x1313::0x0000::','1']; res=libpointer('int8Ptr',int8(UsedDeviceStr)); calllib('WFS_64', 'WFS_init',res,1,1,obj.hdl); obj.hdlValue = obj.hdl.Value; obj.SetGain(obj.masterGainSet); obj.SetExposureTime(obj.exposureTimeSet); obj.ConfigureMLA(obj.pupilDiameterX, obj.pupilDiameterY); success = calllib 'WFS_64', 'WFS_LoadUserRefFile', obj.hdl.Value) %error code = 1074001643, "No User Reference %available!"
Poster:shallwig
Posted Date:2016-02-02 02:31:59.0
This is a response from Stefan at Thorlabs. Thank you very much for your inquiry. We will contact you directly to troubleshoot this in detail.
Poster:tabitha.a.joiner
Posted Date:2016-01-26 11:35:38.987
in what country is this item manufactured?
Poster:shallwig
Posted Date:2016-01-27 02:59:46.0
This is a response from Stefan at Thorlabs. Thank you for your inquiry. All Thorlabs Wavefront sensors get manufactured in Germany. I will contact you directly to check if you have any further questions.
Poster:osorio
Posted Date:2015-07-15 12:23:47.313
Hi! Is it possible to get raw data from the GUI? We are interested in saving Raw Spotfield Images (as JPEG, TIFF or similar) in order to post-process them ourselves. XPS files are not really an option, and centroid data files contain only information that has been already processed. Thanks in advance for the info! Clara
Poster:shallwig
Posted Date:2015-07-16 10:50:33.0
This is a response from Stefan at Thorlabs. Thank you very much for your inquiry . Unfortunately you cannot save the raw data from our GUI directly. You would have to write your own application. The raw data can be recorded by using the command "WFS_TakeSpotfieldImageAutoExpos". After that you can read the raw data out by using the command "WFS_GetSpotfieldImageCopy". When downloading the software package from our website http://www.thorlabs.com/software_pages/ViewSoftwarePage.cfm?Code=WFS also LabView driver files are copied to a location which is pre-defined by previous installations of National Instruments LabView software, for instance: C:\Program Files\National Instruments\LabVIEW\user.lib\WFS_Drv. Other compiler support and help files can be found here: C:\Program Files\IVI Foundation\VISA\WinNT\Thorlabs WFS and C:\Program Files (x86)\IVI Foundation\VISA\WinNT\WFS for 64 bit systems. Please note that there are short sample application files with supplied source code for C and LabView which should help you to understand the driver usage. For a full documentation of the driver functions please open WFS_Drv.html file or see text file WFS_Drv.txt. which you can find at the same installation path described above in the "manual" folder. I will contact you directly for further discussions.
Poster:shallwig
Posted Date:2016-01-28 05:34:56.0
This is a response from Stefan at Thorlabs. Thank you again very much for your feedback, after reviewing we have decided to add this feature (saving the raw data directly from the GUI) in the next software version which we will provide till end of February. I will contact you directly as soon as this new version is available.
Poster:E.lebedeva
Posted Date:2015-06-19 01:03:03.623
Hello! Is it suitable for large radius of curvature?
Poster:shallwig
Posted Date:2015-06-19 11:15:36.0
This is a response from Stefan at Thorlabs. Thank you very much for your inquiry. The AR coated arrays get calibrated at RoC=3m and have therefore a higher accuracy than the chrome mask version (WFS150-5C). But we do not specify the RoC accuracy in detail. From our experience at RoC > 10m the measurements get unreliable and unstable. I will contact you directly to discuss your needs in more detail.
Poster:tdzamba
Posted Date:2015-06-18 17:33:34.94
Dear Sir/Madam, I would like to interface my WFS150 with MATLAB. I was hoping to utilize the 'loadlibrary' function in MATLAB and gain access to the individual functions. However, I am having some trouble linking the appropriate files. Is there some example code to do this?
Poster:shallwig
Posted Date:2015-06-19 08:48:29.0
This is a response from Stefan at Thorlabs. Thank you very much for your inquiry. I will contact you directly and send you an example how to integrate the WFS into MATLAB.
Poster:e.lebedeva
Posted Date:2015-06-18 17:10:42.753
Hi! What are the numbers of Read noise and Active area pixel well depth? Is it possible to order the microlens array with another sizes/pitchs/focal length?
Poster:shallwig
Posted Date:2015-06-22 06:16:52.0
This is a response from Stefan at Thorlabs. Thank you for your inquiry, unfortunately we do not have any data about “Read noise” and “active area pixel well depth”. In the data sheet of the chip manufacturer https://www.thorlabs.com/thorcat/15900/DCU224M-MFGSpec.pdf these parameters are not specified in detail. I have contacted you directly regarding customized microlens arrays and to discuss your application in detail.
Poster:sfs
Posted Date:2015-06-15 06:47:02.75
Dear Sir/Madam I am using a WFS150 and it works fine. But I am also using some other IDS uEye cameras, but can't seem to get both types to work at one time. All the seems to work is to re-install eiter the IDS driver (4.60) or WFS driver (4.4). What can I do, please help? Thanks and kind regards, Francois
Poster:shallwig
Posted Date:2015-06-15 09:15:45.0
This is a response from Stefan at Thorlabs. Thank you very much for contacting us. If the WFS Software is installed on the same system like the ?Eye software the WFS gets recognized as an IDS camera. For the WFS being recognized as WFS the Thorlabs drivers have to be assigned to the WFS. I have sent you a note with screenshots showing how to do that in detail.
Poster:g.makey
Posted Date:2015-05-15 09:22:26.89
Is it possible to order custom-made WFS (or microlens array) that works at the wavelength 1.55 um?
Poster:tschalk
Posted Date:2015-05-15 09:56:05.0
This is a response from Thomas at Thorlabs. Thank you very much for your inquiry. We can offer MLAs with a AR coating for 1550nm but the cameras are not sensitive for that wavelength. I will contact you directly to discuss your application.
Poster:klaus.albers
Posted Date:2015-02-13 09:01:20.76
Do you know if the live data of the WFS can be read by Matlab? It seems difficult to connect to the NI datasocket. Alternatively: Does the software provide a logging option? Thank you and best regards, Klaus
Poster:tschalk
Posted Date:2015-02-16 04:41:44.0
This is a response from Wolfgang at Thorlabs. It is possible to read out the WFS in MATLAB using the driver dll's. The functions used in MATLAB are 'loadlibrary' and 'calllib'. I will contact you directly with further details. In the software, the data which is being displayed can be saved but a logging function is not available.
Poster:honoh
Posted Date:2015-01-13 11:30:45.147
Hi, I'm using WFS150-5C. Extremely useful. Now, I also need data for intensity distribution. How can I get numerical data for spot intensities? I mean the pixel intensity height at each spot, or integrated intensity for each spot (better). I guess there's no menu for that data in the GUI. Can I get them if I write a C or C# program? Thanks.
Poster:shallwig
Posted Date:2015-01-13 09:07:11.0
This is a response from Stefan at Thorlabs. Thank you very much for your feedback and your inquriy. We are glad to hear that the WFS150-5C Wavefront sensor is a useful tool for your application. There are two possibilities to retrieve the power distribution of the spots. You can use our WFS software which you can download from our website: http://www.thorlabs.de/software_pages/ViewSoftwarePage.cfm?Code=WFS By using “File -> Save Power Distribution Data” you can display the two-dimensional array of data containing the spot intensities in arbitrary unit. The second possibility to get these data if you have written your own program is to use the command “WFS_GetSpotIntensities” which is described in the programmers manual. The programmers manual gets downloaded with the WFS software automatically. I will contact you directly to dsicuss your application and your needs in detail.
Poster:wangyujen.eo02g
Posted Date:2014-10-14 09:41:00.377
Thanks for replying me. I would like to know how your company define the upper limits for designing the proper sample to measure. If is not proper for you to answer me here, could you please send me in email ? Thanks
Poster:shallwig
Posted Date:2014-10-15 03:53:40.0
This is a response from Stefan at Thorlabs. Thank you for your Inquiry, I have contacted you directly to discuss your application in detail.
Poster:wangyujen.eo02g
Posted Date:2014-10-14 04:58:22.57
Actually, I have two questions for the product (7AR): 1. why the dynamic range is >100*wavelength ? Is it means that this product guarantee it can measure the wavefront below 100*wavelength accurately? can you give me the definition of the parameter? I can not find the definition of dynamic range which make sense to the parameter provided in your website. 2. In your website, the effect focal length of WFS150-7AR are of 5.2mm mounted in WFS, 6.7 mm for normal mode, but there is also 5.0 mm I can find in blew table. What's that?? Thank you for replying me. I will be very appreciate for that. Wang, Yu-Jen
Poster:shallwig
Posted Date:2014-10-15 03:46:03.0
This is a repsonse from Stefan at Thorlabs. Thank you very much for your inquiry. 1) The specified dynamic range denotes the max. peak-to-valley wavefront deformation measurable across the entire aperture. This is a practical measured value for a spherical wavefront with small Radius of Curvature (RoC) and therefore high curvature. At high wavefront curvature the distance of the detected spots differs largely from the microlens pitch and the software needs to detect the spots at their shifted positions. So the specfied value describes this detection capability. 2) The nominal focal length which is 5.2 mm for the MLA150-7AR´gets calculated from the nominal lenslet radius. But practical tests showed that for the sharpest spots the optimal distance between lenslets and the sensor chip is 6.7 mm. Therefore, the lenslet array is mounted at this distance which is called the effective focal length. This is the value which needs to be used in calculations too. The 5.0 mm written in another table is a typo. We will correct this.
Poster:tdzamba
Posted Date:2014-09-17 11:21:26.443
Is it possible to raise the exposure time past the maximum allowable in the GUI (66.501ms)? I am trying to measure the wave front of a relatively dim beam, and I am having a hard time getting the intensity high enough.
Poster:shallwig
Posted Date:2014-09-18 10:39:49.0
This is a response from Stefan at Thorlabs. Thank you very much for your inquiry. With our next software update we will change the upper limits you can set in the GUI for the frame rate and the exposure time. I will contact you directly when I know the date of release.
Poster:peymaee
Posted Date:2014-08-29 10:40:26.69
Dear Mr/Mrs Can you please put a simple program by visual studio(C#) on your site to connect to one of yours SHWFS and read some values(e.g. RoC) from it?
Poster:shallwig
Posted Date:2014-09-01 05:27:56.0
This is a response from Stefan at Thorlabs. Thank you very much for your inquiry. At the moment we are working on the Release of WFS20 and are renewing the already provided C example. In the new installation package V4.2 we will also provide a C# example. This will be available in about 2 weeks. I will contact you directly to inform you when the new package is online.
Poster:tdzamba
Posted Date:2014-08-26 17:45:50.9
Is there a 64-bit version of the SDK available?
Poster:shallwig
Posted Date:2014-08-27 10:44:20.0
This is a response from Stefan at Thorlabs. Thank you very much for your inquiry. The provided software can be run either under 32 or 64 bit systems and requires Windows XP, Vista, 7 or later. The latest version of the wavefront sensor software package can be downloaded from our website here: http://www.thorlabs.de/software_pages/ViewSoftwarePage.cfm?Code=WFS The software includes a driver package for constructing applications with the following software packages: C Compilers, LabVIEW, LabWindows and DotNet. I will contact you directly to discuss your application in detail.
Poster:daniel.bogdoll
Posted Date:2014-06-13 16:04:11.407
Hello, I've got a question concerning the wave-front-sensor. Is it possible to connect it to Simulink (Matlab), so that you can analyse and work with the data live? If not, do you have a manual or something comparable to connect it to LabView? Best regards, Daniel
Poster:shallwig
Posted Date:2014-06-16 08:18:50.0
This is a response from Stefan at Thorlabs. Thank you very much for your inquiry. With the WFS driver we provide a .NET library as well as Labview Vis. The .NET library you should be able to call in Matlab. All files can be downloaded from our website here: http://www.thorlabs.de/software_pages/ViewSoftwarePage.cfm?Code=WFS The files Thorlabs.WFS.Interop.dll and Thorlabs.WFS.Interop.xml get saved on your PC under the following path: C:\Program Files\Microsoft.NET\Primary Interop Assemblies We also provide an example program in C which is helpful to see in which order the driver functions gets called. You can find it here: C:\Program Files\IVI Foundation\VISA\WinNT\Thorlabs WFS\Examples\C I will contact you directly to discuss if there are any open questions we can help you with.
Poster:rawoodruff
Posted Date:2014-01-29 18:48:14.27
Are the Shack-Hartmann sensors suitable to use in vacuum or low pressure? What temperature levels can they operate at?
Poster:tschalk
Posted Date:2014-01-30 04:54:49.0
This is a response from Thomas at Thorlabs. Thank you very much for your inquiry. Our wavefront sensors are not suitable for use in a vacuum. I don’t see any reason why they shouldn't work in an environment with low pressure but the housing is anodized and are not compatible with high vacuum. The operating temperature is from +5°C to +35°C.
Poster:
Posted Date:2013-12-01 23:48:48.48
I need to measure tip-tilt of optical surface with accuracy of 1micro-rad. Are your WFS compatible for this task?
Poster:tschalk
Posted Date:2013-12-02 08:39:46.0
This is a response from Thomas at Thorlabs. Thank you very much for your inquiry. The accuracy of the WFS is not good enough to resolve 1 micro rad. But another solution to measure the tilt-tip of an optical surface could be a camera beam profiler BC106 (http://www.thorlabs.com/newgrouppage9.cfm?objectgroup_id=3483). Please contact me at europe@thorlabs.com to discuss your application.
Poster:neil.troy
Posted Date:2013-10-23 14:01:27.89
I find that the software is hindered by the acquisition parameters that the user cannot adjust. When I connect the camera with the DCx software I have an ability to integrate on the camera for nearly a second because I can change the pixel clock but this option is not available in the Shack-Hartmann software. This limits the software's usability to us as the 65 ms limit for integration is not enough for the software to register the spot pattern. Please update the software so that this software can make better use of the camera's capabilities.
Poster:tschalk
Posted Date:2013-11-08 04:27:31.0
This is a response from Thomas at Thorlabs. Thank you very much for your suggestion for improvement. We will update the software so that the user is able to change the exposure time. I will contact you directly with more detailed information.
Poster:allandeof
Posted Date:2013-05-20 13:57:55.473
Good Evening I d like more information about possible aplications of these product. Looks like a cam with microlens. The array of microlens is responsible for its large band of sensibility (300 to 1000 nm)? Im looking for a CCD cam whith sensibility between 300 and 1000 nm, external trigger control and a minimum of 15 FPS. Can be these product what Im lokking for? Any information will be helpful. Allan Fontes
Poster:tschalk
Posted Date:2013-05-22 10:01:00.0
This is a response from Thomas at Thorlabs. The WFS has a big field of applications. It is used to test the quality of optical components or to characterize the optical properties of a laser beam. A WFS can also be used to measure the aberrations of the human eye. Thorlabs WFS consists of a camera with a mounted microlens array in front of the camera sensor. The WFS represents a modified DCU camera. The typical response of these WFS CCD cameras can be found in the manual page 129: http://www.thorlabs.com/Thorcat/19900/WFS150-5C-Manual.pdf. The WFS150-5C is specified for a wavelength range from 300 to 1100nm, it is equipped with an external trigger control and the frame rate in normal mode is 55Hz. I will contact you directly to discuss your application and to find out if the camera is what you are looking for.
Poster:kaccie
Posted Date:2013-03-27 15:13:40.42
I've been looking through your documentation on this product, and I can't help but notice something that bothers me in several drawings. In each drawing where some principle of Shack-Hartmann is explained has the lenslet array oriented such that the convex side faces the detector while the plano side faces the incoming disturbance. Is this actually how your sensors are designed or is it just a drawing? I think it's a pretty big deal since the quality of spots would be a lot worse due to spherical aberration if the plano side is facing the incoming wavefront.
Poster:sharrell
Posted Date:2013-04-04 15:44:00.0
Response from Sean at Thorlabs: Thank you for your feedback. Our microlens arrays are mounted so that the convex side are oriented towards the camera. This was done so that the input aperture of the Shack-Hartmann sensor could be more easily cleaned (since the surface is flat). When developing the wavefront sensors, both orientations of the lens array were tested and only minor differences in the resulting spot diameters were detected with the lenslet-to-camera distance optimized for each case.
Poster:jvigroux
Posted Date:2013-01-18 11:13:00.0
a response from Julien at Thorlabs: Thank you for your inquiry! the array you refer to as intensity is actually showing the wavefront data. This is why the values are both positive and negative. The raw intensity data can be viewed in the software in the spot field window. This data cannot be exported directly form the software though. One needs to use the SDK provided with the software to access this information. The array of the centroid position is indeed adapted to the chosen resolution. Due to the fact however that the microlens array is not positioned exactly in the middle of the camera, there can be a small offset between the theoretical middle (160,160 for 320x320 resolution) and the actual middle. The offset as well as the possible tilt angles of the microlens array are stored in the camera during our calibration. I will contact you directly to discuss more in details those points and your application.
Poster:sharma21.richa
Posted Date:2013-01-16 08:57:07.443
The datasocket,when opened shows 2 matrices only, by default i.e intensity matrix (showing spots X,spots Y)and centroid matrix(showing centroid positions).As far as i understand, intensities are not absolute, as we can see 0 value at the center and some negative values.If this is precisely the case, then how do we retrieve absolute intensities (in grey scale as mentioned in the manual) for each lenslet domain from this matrix ?? And is the second matrix giving us positions of centroids in terms of pixels,so that if we have selected 320*320 pixels , then for a perfect plane wave,center centroid position should be (160,160)and centroid at exterme left beginning should be at approx.(17.78,17.78) ??? Am I correct??
Poster:tschalk
Posted Date:2012-12-11 06:58:00.0
This is a response from Thomas at Thorlabs. Thank you very much for your inquiry. There is no particular reason why the measurement should change. The mechanical components and the magnets are strong enough to keep the lenslet array in the same position over years. All cameras which are used for WFS have a hot pixel correction. What happens through the aging effect and temperature cycles of the sensor, is that new hot pixels appear. Although such single pixel defects do not degrade the WFS accuracy noticeably, functions like the automatic exposure control may be influenced. In case a new, stable and strong hot pixel (more than 50 digits intensity deviation to ambient pixels) becomes visible, you may send your WFS instrument back to Thorlabs in order to repeat the hot pixel correction.
Poster:
Posted Date:2012-12-10 09:48:27.66
If I use your wavefront camera to measure a known curved mirror with the same set-up year after year will I get the same measurement or will there be a drift in the accuracy?
Poster:tschalk
Posted Date:2012-11-07 07:34:00.0
A response from Thomas at Thorlabs: Thank you for your inquiry! If you want to calculate tilt and shift you can use the Zernike coefficients Mode 2 and 3. You can find more detailed information in the manual in section 6.3.8 “Zernike Fit and Zernike Modes”. To calculate the incident angle, use these formulas: W(y)= 2*cn*y -> Incident angle y-axis: Alpha = arctan(4*c(2)/D) W(x)= 2*cn*x -> Incident angle x-axis: Betta = arctan(4*c(3)/D) c(2): value of the Zernike coefficient Mode 2 c(3): value of the Zernike coefficient Mode 3 D: Diameter of the pupil I hope this helps. I will contact you directly with more detailed information.
Poster:olivier.hignette
Posted Date:2012-11-06 10:01:18.84
I have used the SH with success to measure Radii of wavefronts , but I would now like to get the most basic information : tip tilt with respect to my initial set up( collimated wavefront) to rotate and measure wedges of plates . I could do that with an autocollimator , but i have none available right now I cannot get this information displayed , just an idea with the Zernike Bar graph
Poster:jvigroux
Posted Date:2012-07-30 06:05:00.0
A response from Julien at Thorlabs: Thank you for your inquiry! There will indeed be a chromatic shift of the focal length of the microlenses when the wavelength departs form the design wavelength. This shift will mostly however only slightly modify the focus size of the spots on the camera chip. The position of the centroid will not be affected by this shift. As a result, the wavefront measurement will remain accurate over the complete specified range
Poster:nfarmiga
Posted Date:2012-07-26 08:31:53.0
We are using the WFS150-5C for a calibration test fixture and need to know the absolute accuracy of radius of curvature measurements reported. The specs indicate that the WFS works over the waveband from 300 to 1100 nm, but the manual indicates that the sensor is calibrated at 633 nm and that the micro-lens array is fused silica (which, by itself, cannot be achromatic). Since wavefront measurement accuracy depends on the focal length of the micro-lens array, should we expect the absolute accuracy to decrease as we use wavelengths that are farther from the calibration wavelength? Or is there some sort of achromatization in the WFS lens system so that the specified wavefront accuracy applies over the entire waveband?
Poster:jvigroux
Posted Date:2012-03-27 10:36:00.0
A response from Julien at Thorlabs: Thank you for your feedback! the use of a different CCD chip for our wavefront sensor would imply a complete new design, such that we will not be able to offer a short term solution to address the point you raised. We will nonetheless definitely take into account your feedback so that, hopefully, we will be able to offer a bigger chip for the wavefront sensor soon.
Poster:dtmiller
Posted Date:2012-03-27 04:18:24.0
My research lab already has one of Thorlabs' WFS150 series wavefront sensors and we like it quite a bit. However, we constantly run into the aperture size (5.95mmx4.76mm) of the sensor being too small for the beams we diagnose, typically up to 10 mm in diameter. Given the availability of large format CCD and CMOS cameras, it would be great if Thorlabs could expand their wavefront sensor series to include a large format CCD (e.g., 10mm x 10 mm). My hunch is that many labs would fine this attractive and would be willing to pay more for the extra diameter.
Poster:jvigroux
Posted Date:2012-01-25 17:07:00.0
A response from Julien at Thorlabs: There are different approaches used to get rid of such effects. In your case, the simplest will probably consist in changing the light source for one that has a lesser coherence and/or which is possibly randomly polarized. I will contact you directly to discuss the details and requirements of your set up.
Poster:martin.staerk2011
Posted Date:2012-01-25 15:33:57.0
I use a red 4mW HeNe laser. But it creates speckles around the middle spot and so the wavefront image appears not to be plane. What type of light source would you recommend to use? Or is there another way to get rid of the speckles?
Poster:bdada
Posted Date:2011-12-28 19:35:00.0
Response from Buki at Thorlabs: Thank you for your feedback. We will contact you to quote a sensor and extra mounted lens array so you can create a custom kit for your application. Please contact TechSupport@thorlabs.com if you have any questions.
Poster:franxm
Posted Date:2011-12-28 10:06:56.0
I'm interested in a kit with two 150 um lenslet pitch, one AR and one Chrome configuration. Could this be made available? We use long and short wavelength sources. Thanks
Poster:bdada
Posted Date:2011-11-10 11:39:00.0
Response from Buki at Thorlabs: Thank you for participating in our Feedback Forum. We have contacted you to discuss your application further.
Poster:j.y.wang
Posted Date:2011-11-10 14:03:14.0
Hi, I would like to ask a question. Will the software come with the wfs be able to process an offline image taken from another camera and provide the wavefront information as it works for the wfs? Thanks.
Poster:bdada
Posted Date:2011-10-19 13:35:00.0
Response from Buki at Thorlabs: Thank you for your feedback. For the green laser diode, please consider our 543nm HeNe with part number HGP005. We also have a diode pumped solid state laser at 532nm, the DJ532-10. This would require a temperature controlled mount, such as LDM9T or TCLDM9 and a driver. Please contact TechSupport@thorlabs.com if you have further questions.
Poster:jason.tan
Posted Date:2011-10-16 21:57:03.0
I want building a single lens wavefront tester, the test wavelength :530~540nm(green), and used the WFS150-5C, the reference wavefront is a shpere wavefront, do you have any suggestion about the diode laser?
Poster:jvigroux
Posted Date:2011-09-01 14:39:00.0
A response from Julien at Thorlabs: It is not sufficient to add the path to the library WFS_Drv.lib within the project settings. You need to tell Visual Studio that this particular file needs to be loaded.There are three ways for this (one is sufficient): 1. After setting the path, you need to add the library by name "WFS_Drv.lib" in Linker--> Input--> Additional Dependencies 2. You may add the following pragma to the sample source code: #pragma comment(lib, " WFS_Drv") 3. Add the WFS_Drv.lib to the project. I will send you a project that shows how this can be done in practice.
Poster:gmgruber01
Posted Date:2011-08-31 18:31:44.0
I need some help in doing a build on the supplied sample code that came with the Wavefront Sensor (Model 150-5C). The header of the sample file suggests that all I need is to set the include path. Im using Visual Studio 2010 Pro. I have set the, includes path in the project property page to the dir = (.\VISA\WinNT\include)as it was installed. Sample does compile, but doesnt build. OK. Cant find the lib. So I set the project property page to dir = (.\VISA\WinNT\lib\msc) to find (WFS_Drv.lib). Still got build errors, so included (.\VISA\WinNT\Thorlabs WFS\Typelib) to find (WFS_Drv.def). I get the following 4 warnings & 29 errors. Can anybody help? 1>sample.c 1>c:\sw_dev\vs2010\02wfs\examples\c\sample.c(185): warning C4047: function : WFS_hdl differs in levels of indirection from void * 1>c:\sw_dev\vs2010\02wfs\examples\c\sample.c(185): warning C4024: WFS_RevisionQuery : different types for formal and actual parameter 1 1>c:\sw_dev\vs2010\02wfs\examples\c\sample.c(599): warning C4244: = : conversion from double to int, possible loss of data 1>c:\sw_dev\vs2010\02wfs\examples\c\sample.c(610): warning C4101: mla_cnt : unreferenced local variable 1>sample.obj : error LNK2019: unresolved external symbol _WFS_TakeSpotfieldImage@4 referenced in function _main 1>sample.obj : error LNK2019: unresolved external symbol _WFS_GetHighspeedWindows@28 referenced in function _main 1>sample.obj : error LNK2019: unresolved external symbol _WFS_SetHighspeedMode@20 referenced in function _main 1>sample.obj : error LNK2019: unresolved external symbol _WFS_ZernikeLsf@20 referenced in function _main 1>sample.obj : error LNK2019: unresolved external symbol _WFS_CalcWavefrontStatistics@28 referenced in function _main 1>sample.obj : error LNK2019: unresolved external symbol _WFS_CalcWavefront@16 referenced in function _main 1>sample.obj : error LNK2019: unresolved external symbol _WFS_GetSpotDeviations@12 referenced in function _main 1>sample.obj : error LNK2019: unresolved external symbol _WFS_CalcSpotToReferenceDeviations@8 referenced in function _main 1>sample.obj : error LNK2019: unresolved external symbol _WFS_GetSpotCentroids@12 referenced in function _main 1>sample.obj : error LNK2019: unresolved external symbol _WFS_CalcSpotsCentrDiaIntens@12 referenced in function _main 1>sample.obj : error LNK2019: unresolved external symbol _WFS_CalcBeamCentroidDia@20 referenced in function _main 1>sample.obj : error LNK2019: unresolved external symbol _WFS_GetSpotfieldImage@16 referenced in function _main 1>sample.obj : error LNK2019: unresolved external symbol _WFS_close@4 referenced in function _main 1>sample.obj : error LNK2019: unresolved external symbol _WFS_GetStatus@8 referenced in function _main 1>sample.obj : error LNK2019: unresolved external symbol _WFS_TakeSpotfieldImageAutoExpos@12 referenced in function _main 1>sample.obj : error LNK2019: unresolved external symbol _WFS_SetPupil@36 referenced in function _main 1>sample.obj : error LNK2019: unresolved external symbol _WFS_SetReferencePlane@8 referenced in function _main 1>sample.obj : error LNK2019: unresolved external symbol _WFS_ConfigureCam@20 referenced in function _main 1>sample.obj : error LNK2019: unresolved external symbol _WFS_SelectMla@8 referenced in function _main 1>sample.obj : error LNK2019: unresolved external symbol _WFS_GetInstrumentInfo@20 referenced in function _main 1>sample.obj : error LNK2019: unresolved external symbol _WFS_init@8 referenced in function _main 1>sample.obj : error LNK2019: unresolved external symbol _WFS_RevisionQuery@12 referenced in function _main 1>sample.obj : error LNK2019: unresolved external symbol _WFS_ErrorMessage@12 referenced in function _handle_errors 1>sample.obj : error LNK2019: unresolved external symbol _WFS_GetInstrumentListInfo@20 referenced in function _select_instrument 1>sample.obj : error LNK2019: unresolved external symbol _WFS_GetInstrumentListLen@4 referenced in function _select_instrument 1>sample.obj : error LNK2019: unresolved external symbol _WFS_GetMlaData@40 referenced in function _select_mla 1>sample.obj : error LNK2019: unresolved external symbol _WFS_GetMlaCount@8 referenced in function _select_mla 1>C:\SW_Dev\VS2010\02WFS\Examples\C\sampleWFS\Debug\sampleWFS.exe : fatal error LNK1120: 27 unresolved externals ========== Rebuild All: 0 succeeded, 1 failed, 0 skipped ==========
Poster:tor
Posted Date:2011-01-04 15:25:08.0
Response from Tor at Thorlabs to John: The WFS150C software requires a USB 2.0 port; earlier versions are not usable. Please refer to section 2.1 of the manual for details on system requirements: http://www.thorlabs.com/Thorcat/19900/19905-D02.pdf
Poster:bowen
Posted Date:2010-12-18 14:16:25.0
Does this software for the WFS150-C work on USB 1.0 ports? I have installed it on an older laptop and the camera does not come up. thanks, John Bowen bowen@photongear.com
Poster:julien
Posted Date:2010-12-08 10:36:09.0
An answer from Julien at Thorlabs: The different models of wavefront sensors differ only through the microlens array they use. Two microlens arrays have a pitch of 150µm. The MLA150M-5C (WFS150-5C) is recommended for general use where reflected light back from the array is not a problem. For application where the reflections can be an issue, we recommend using the MLA150M-7AR (WFS150-7AR), which has a broadband AR coating. The MLA300M-15AR (WFS300-14AR) uses the same AR coating but has a longer focal length and a wider pitch (300µm). This leads to an increased accuracy and sensitivity, at the expense of the dynamic range. Those points are addressed more accurately in the specs tab on the WFS web page. I will contact you directly to further discuss your application in order to find out which WFS is most adapted to your need.
Poster:gsirat1
Posted Date:2010-12-07 15:45:29.0
How to choose between the models of the Schack Hartman? What are the advantages of each model?
Poster:tor
Posted Date:2010-11-10 15:17:38.0
A response from Tor at Thorlabs to mjerzak47: We will contact you directly to troubleshoot this issue.
Poster:mjerzak47
Posted Date:2010-11-10 13:27:24.0
Hello, when I use a positive lens to generate a converging beam from a collimated beam the value of Optometric constant - Sphere has a wrong (negative) sign. Same thing happens with a negative lens - Sphere has a positive sign, why is that?
Poster:julien
Posted Date:2010-08-05 10:35:05.0
A response from Julien at Thorlabs to Laura: The array is placed above the sensor so that the X and Y directions of the array match the ones of the sensor. The position of the lenslets themselves relative to the pixels is not exactly known. Instead, a calibration is done during the production where a flat wavefront impinges perpendicularly onto the WFS. The centroid positions are then stored as calibration reference. The positions of the centroids are referenced to the top left corner of the sensor.
Poster:laura.waller
Posted Date:2010-08-02 15:53:47.0
Hello, i have one of these and am looking for the data on which pixels correspond to which lenslets in the array. Can i assume pixel (1,1) is aligned to the top left corner of lenslet (1,1) ?? Serial number info is: WFS150-5C M00239612 thanks, Laura Waller (lwaller@princeton.edu)
Poster:Thorlabs
Posted Date:2010-07-26 10:41:15.0
Response from Javier at Thorlabs to michael.schaefer: Thank you very much for your feedback. The <25% reflectivity spec for the WFS150 wavefront sensor with the chrome mask is correct. The WFS150-5C microlens is not AR coated; the chrome mask blocks light that is not passing through the microlenses. As a result, a relatively high percentage of the incoming light is reflected in exchange for high contrast.
Poster:michael.schaefer
Posted Date:2010-07-26 13:21:23.0
Hi there, you mention a reflectivity of 25??? percent for this product. shouldnt this be 0.25% ? Michael
Poster:Thorlabs
Posted Date:2010-06-25 10:14:36.0
Response from Javier at Thorlabs to angel_sinue: it appears that the data stored in the EEPROM of the WFS wavefront sensor is lost. I would recommend sending this unit back for repair. I will contact you directly.
Poster:Thorlabs
Posted Date:2010-06-25 10:29:13.0
Response from Javier at Thorlabs to xgliu: the WFS software includes instrument drivers and examples for integration with the LabVIEW and LabWindows/CVI platforms. Also, the WFS is also equipped with a DataSocket interface for live data transfer into other applications. As an example, a "wavefront sensor receiver" application including source code is also provided. I will contact you directly with a copy of the WFS manual, which explains these in detail.
Poster:angel_sinue
Posted Date:2010-06-24 21:33:07.0
Hi! I need some help with the product. It appears that the Wavefront sensor is not being recognized by the application software, instead, only the DCU camera is being recognized by the software, and therefore, no graphics from the measured wavefront are displayed, I really need some help out here.
Poster:xgliu
Posted Date:2010-06-25 16:16:53.0
hi, need to check out the software for this product. does it have any interface to other software, like LabVIEW or Matlab? In our application, we need to pass the wavefront profile to another program (in Matlab or LabVIEW)for further processing...and this is preferably in real time.... Thanks a lot...
Poster:julien
Posted Date:2010-06-08 16:26:46.0
a response from Julien at Thorlabs: We provide a SDK for the wavefront sensor (installed during the sofwtare installation), with which you can access all the basic function of the unit. Unfortunately I cannot disclose the brand and model name of the CCD camera. However, I would be happy to discuss your application with you to find a way we can help with the software implementation of the functions you need for your application. I will contact you directly per email.
Poster:nssycit
Posted Date:2010-06-08 20:57:13.0
hello, I want to know more about the Shack-Hartmann Wavefront Sensor, that is, whats the brand and model of the sensor? And can you send the SDK of the camera to me? thank you sir.
Poster:
Posted Date:2010-05-18 16:38:42.0
A response from Florian at Thorlabs to bowen: The updated drawings are now online.
Poster:Adam
Posted Date:2010-05-12 08:50:36.0
A response from Adam at Thorlabs to bowen: I agree that this thread specification should be added to the drawing. We are in the process of adding this to the drawing and will put the updated drawing on the web.
Poster:bowen
Posted Date:2010-05-11 16:36:31.0
Thread size for main optical aperture, part WFS150-5C, is not given. Text gives it, but it would be nice to have on the print.
Poster:apalmentieri
Posted Date:2010-03-01 17:13:32.0
A response from Adam at Thorlabs to gidiloo: At this time we do not have a product similar to the wavefront sensor that is AR coating at 1550nm. Unfortunately, an AR coating alone will not solve the issue as the camera will not detect the 1550nm light. Please note that we are always looking for new product ideas and I will inform our engineers of this idea. I would also like to get more information about your application, but will email you directly to get this information.
Poster:apalmentieri
Posted Date:2010-03-01 14:44:55.0
A response from Adam at Thorlabs to Ajgonsalves: Although we guarantee a wavefront accuracy of lambda/15 only, the instruments hardware might be able to detect even smaller aberrations. Especially when calibrated in the application setup using a plane or ideal spherical wavefront, the relative accuracy can be better than lambda/25 (0.04 waves). We often see such values during our production tests. Id encourage you to test a demo unit in order to check its performance in your lab. The labview drivers have the full functionality of capture and analysis.
Poster:gidiloo
Posted Date:2010-03-01 14:24:25.0
Hi, Would you have anything similar to the Shack-Hartmann Wavefront Sensor but AR for 1550nm? Thanks, Gideon
Poster:ajgonsalves
Posted Date:2010-02-12 14:54:30.0
The wavefront sensitivity seems to be quite poor for this type of wavefront sensor. e.g. ?/15 rms (@ 633 nm) for the model with 150micron lenslet pitch. Why is this? Is there a different number for the relative sensitivity as opposed to absolute? i.e. if we are subtracting a reference and looking at changes in the wavefront is the sensitivity still ?/15 rms? Also do the labview drivers support full funtionality of capture and analysis?
Poster:jens
Posted Date:2009-12-19 17:50:07.0
A reply from Jens at Thorlabs: one reason for this could be that the incorrect USB driver is used. We will have to check which serial number your sensor has and which driver is currently loaded, I will provide you the link to the driver files so this can be changed if it turns out to be the root cause. Based on the serial number we will also be able to check the calibration data of the unit. I will contact you directly with the driver details and pictures showing where to find the necessary details.
Poster:wjj
Posted Date:2009-12-19 09:40:48.0
How to solve this problem when I use this product? (1)Checksum error while loading calibration data from warefront sensor. (2)Unable to recover WFS calibration data!You are probably using a Thorlabs DCU camera which is not supported by this wavefront sensor application software!
Poster:ekrause
Posted Date:2009-12-09 14:47:48.0
A WFS 2.0 beta version is meanwhile available here: http://www.thorlabs.com/software/MUC/WFS/Software/WFS_2.0beta.zip This beta is not fully tested and misses an updated manual and help file. Please unzip and install: - USB_Cam_Driver_3.50.zip - (camera USB driver, required anyway) - WFS_Appl_2.0beta.zip - (WFS application) - WFS_Drv_2.0beta.zip - (Driver package, C, DotNet, LabView)
Poster:ekrause
Posted Date:2009-12-09 02:15:13.0
Yes, the new software release 2.0 includes a trigger option now, it will be released very soon on this web page. Edges LH or HL can trigger camera exposure with adjustable delay time (15 µs – 4 s). A special cable will be supplied for this.
Poster:
Posted Date:2009-12-08 13:49:11.0
With reference to my post of 5/5/08 and Lauries responce on 5/7/08. Has a upgrade of the software included a triggered option yet? (I guess from dtmillers posting on 7/21/09 the answer is no). Is there really a plan to suport triggering (measuring low rep rate pulsed lasers)at some point?
Poster:klee
Posted Date:2009-10-07 12:16:58.0
A response from Ken at Thorlabs to Miroslav.Belov: Can you double check the part number? We do not have BP106 in our system.
Poster:Miroslav.Belov
Posted Date:2009-10-07 11:07:47.0
Can we expand/upgrade our BP106 to a wavefront sensor? Thanks, Miro
Poster:Laurie
Posted Date:2009-09-01 15:30:06.0
Response from Laurie at Thorlabs to angelcf: Thank you for your interest in our wavefront sensors. If you look at page 33 of our manual for our adaptive optics kit (search for AOK1-UM01), which utilizes this wavefront sensor, you will find a short discussion on the indices being used for our Zernike polynomials as well as a reference. If you should need additional information, please let us know.
Poster:angelcf
Posted Date:2009-08-30 06:50:16.0
Hi Laurie at Thorlabs, could you please send me a copy of the file that lists the Zernike polynomial indices being used with your wavefront sensor software???
Poster:jhartmann
Posted Date:2009-07-21 09:56:58.0
A response from Juergen at Thorlabs to dtmiller : WFS150(C) is based on one of our CCD cameras, DCU224M. The trigger input works for DCU224M and the camera software. If its converted to WFS150, the trigger input is without function - WFS150 software does not support external triggering
Poster:dtmiller
Posted Date:2009-07-19 14:46:00.0
Does the WFS150 camera have an external trigger that allows it to be synchronized with other electronic devices? If it does not have an external trigger, does Thorlabs have any recommendations on how it can be synchronized?
Poster:jens
Posted Date:2009-07-04 06:41:57.0
A reply from Jens at Thorlabs: The definition within the wavefront data array is: first index = y, second index = x. This was chosen because our C compiler uses this convention when displaying arrays for debugging. Graphical toolbox software normally has a different convention: first index = x second index = y. That’s why the Wavefront Sensor software copies the wavefront array into another array with flipped x and y axes prior to display. Columns become rows and vice versa. If you do the same the output will be identical to the Wavefront Sensor software.
Poster:david.lee
Posted Date:2009-07-03 09:54:23.0
Does the coordinate system displayed on the wavefront error results screen match that used in the csv file output? My measurements seem to show a 180 degree rotation of the data.
Poster:Laurie
Posted Date:2008-12-23 09:04:20.0
Response from Laurie at Thorlabs to jason.zweiback: Thank you for feedback concerning our WFS150C. I am glad to hear that you have found the instrument to be helpful. Concerning the software/functionality, I have passed your comments on to the chief engineer responsible for this particular item so that he can incorporate such improvements into future versions of the software. As newer versions of the software become available, you will be able to download them from our website.
Poster:jason.zweiback
Posted Date:2008-12-22 12:10:47.0
I recently purchased a WFS150C. Overall I find the instrument easy to use and quite helpful. However, I feel the software needs some additional functionality. As far as I can tell, once you stop acquiring data the software can no longer do any calculations. This would allow one to look at the residual wavefront as one removes or adds Zernikes. Along with this, it would be useful to be able to reload a save wavefront in order to view it and do analysis. The ability to save the wavefront plot as a jpeg would also be useful.
Poster:Tyler
Posted Date:2008-10-14 11:55:42.0
A response from Tyler at Thorlabs to stordo: The software cannot currently (9/14/2008) handle a central obstruction in the spot field. However, because of your request we are working on a software revision that accommodates obstructions. We will be in contact with you as this process continues to make sure the new software will meet your specifications. This is an exciting opportunity to improve the Thorlabs Shack-Hartmann sensor, thank you for contacting us with the central obstruction issue.
Poster:Laurie
Posted Date:2008-10-13 10:08:08.0
Response from Laurie at Thorlabs to icsmith: Thank you for your feedback and interest in our wavefront sensors. Since there are various definitions for the Zernike polynomials floating around the literature, I will be personally emailing you a .pdf file that lists the Zernike polynomial indices being used with our wavefront sensor software. Once youve had a chance to take a look at it, please feel free to contact us with any additional questions so that we can clarify further if necessary.
Poster:icsmith
Posted Date:2008-10-09 18:05:17.0
There seems to be a slight inconsistency in the software package in the way it deals with Zernike modes. The instructions claim the WFS orders the Zernike terms as defined by Malacara (with the highest 2nd index coming first) but software’s main display and the table included in the wavefront sensor set up menu orders them differently? (the lowest 2nd index ,negative, coming first). Ive been writing a interface (reading the Zernike modes through the DataSocket) that can also reconstruct the phase from the Zernike and have tried both ordering schemes, the true Malacara scheme seems to give the best results in matching the "measured" wavefront display in the ThorLab software but doesnt match the "reconstructed" display well. Any ideas? a definitive listing of the indexes and the actual polynomials would be reassuring. Thanks-Ian
Poster:stordo
Posted Date:2008-10-06 10:50:59.0
I would like to know it the software can handle central obstruction. For instance, can the software reconstruct zernike coefficients of a wavefront with a round central obstruction?
Poster:Laurie
Posted Date:2008-09-12 12:43:29.0
Response from Laurie at Thorlabs to yangjiakobe: Thank you for your interest in our wavefront sensors. The WFS150C has an input aperture of 5.95 x 4.76 mm. However, based on your question of compatibility with your microscope, I presume that you are interested in the diameter of the round opening at the front of the housing, which is 32 mm. If you are not familiar with our website, mechanical drawings for all products can be found under the Drawings and Documents Tab. Here you can view a .pdf file that shows you all of the dimensions for the wavefront housing. Also, our wavefront sensors have a C-Mount thread. However, if a different threading is needed, we do offer adapters to other standards, which can be found at this website: http://www.thorlabs.com/NewGroupPage9.cfm?ObjectGroup_ID=1747&pn=SM1A9. If we can be of further assistance, please let us know.
Poster:yangjiakobe
Posted Date:2008-09-12 11:16:12.0
Dear Sir or Madam, Could you please tell me the dimensions of the aperture of the wavefront sensor 150C? We need a wave front sensor and want to fix it onto a microscope. So the thread of the mount of WFS150C should be compatible with the our microscope. Whats the type of the mount thread of WFS150C? Thank you.
Poster:Laurie
Posted Date:2008-07-17 09:01:04.0
Response from Laurie at Thorlabs to roedel: Thank you for your question. Unfortunately, our WFS150 cannot at this time be triggered externally. We are currently working on an updated version that has this functionality. If you should have additional questions, please dont hesitate to contact us.
Poster:roedel
Posted Date:2008-07-17 05:38:22.0
Dear Sir or Madam, can the wave front sensor 150 be triggered externally? That would be very important to know because we want to use it with a pulsed laser with a repetition rate of 10 Hz. Thanks in advance,
Poster:Laurie
Posted Date:2008-05-07 11:06:57.0
Response from Laurie at Thorlabs to icsmith: The WFS150 sensor is based on our DCU223M CCD camera. The appropriate trigger cable for this hardware is item CAB-DCU-T1. However, at this time, the wavefront sensor software is not capable of triggering a wavefront capture. In the next software release, a number of improvements will be implemented, including trigger capabilities. Please feel free to contact us with any additional questions.
Poster:icsmith
Posted Date:2008-05-05 18:29:38.0
It would be good to suply the micro SubD 9 pin digital control cable for this camera. Cordinating exactly when a measurment is taken is very difficult without the cameras trigger function which is only possible through the cable. The conector doesnt seem to be standard and I have been unable to find one.

1.3 Megapixel Shack-Hartmann Wavefront Sensor

Item #WFS150-5CWFS150-7ARWFS300-14AR
Wavelength Range 300 - 1100 nm 400 - 900 nm 400 - 900 nm
Effective Focal Length 3.7 mm 5.2 mm 14.0 mm
Lens Array Coating Chrome Mask AR Coated
Lenslet Pitch 150 µm 300 µm
Wavefront Accuracy λ/15 rms λ/50 rms
Wavefront Sensitivity λ/50 rms λ/150 rms
Camera Sensor Type CCD
Frame Rate 15 Hz
Camera Resolution 1280 x 1024 Pixels Max, Selectable
Based on your currency / country selection, your order will ship from Newton, New Jersey  
+1 Qty Docs Part Number - Universal Price Available / Ships
WFS150-5C Support Documentation
WFS150-5CShack-Hartmann WFS, 150 µm Pitch, Chrome Masked, 300 - 1100 nm
$4,009.00
Today
WFS150-7AR Support Documentation
WFS150-7ARShack-Hartmann WFS, 150 µm Pitch, AR Coated: 400 - 900 nm
$4,009.00
Today
WFS300-14AR Support Documentation
WFS300-14ARShack-Hartmann WFS, 300 µm Pitch, AR Coated: 400 - 900 nm
$4,009.00
Today

1.3 Megapixel Shack-Hartmann Wavefront Sensor Kits

The WFS kits combine the base camera unit and two interchangeable microlens arrays. The chart below contains the properties of the lens arrays included with each kit, for more details on the lens and camera properties please see the Specs tab above.

Item #Lens Array 1Lens Array 2
WFS-K1Chrome Mask: 300 - 1100 nm, Pitch = 150 µmAR Coated: 400 - 900 nm, Pitch = 300 µm
WFS-K2AR Coated: 400 - 900 nm, Pitch = 150 µmAR Coated: 400 - 900 nm, Pitch = 300 µm
Interchanging Microlens Arrays

How to Interchange Microlens Arrays

The microlens arrays are mounted with a precision patented magnetic holder. They can be easily interchanged and returned to the same position using the pickup tool that is included with the kit, as shown in the photo to the right.

Based on your currency / country selection, your order will ship from Newton, New Jersey  
+1 Qty Docs Part Number - Universal Price Available / Ships
WFS-K1 Support Documentation
WFS-K1Customer Inspired!High Sensitivity WFS Kit, 150 µm Pitch, Chrome Masked and 300 µm Pitch, AR Coated
$4,857.00
Today
WFS-K2 Support Documentation
WFS-K2Customer Inspired!High Sensitivity WFS Kit, 150 µm Pitch, AR Coated and 300 µm Pitch, AR Coated
$4,857.00
Lead Time

USB and Trigger Cables

The CAB-DCU-T2 cable is used to replace the USB to Micro Sub-D cable included with the 1.3 megapixel Shack-Hartmann sensors in applications where a trigger is required. For specifications for the trigger input, please see the Specs tab above.

Item #Device Side
Connector
Trigger Input
Connector
PC ConnectorShieldingLength
CAB-DCU-T2Micro Sub-D, StraightBare WireUSB 2.0, MaleDouble Shielded, 80 °C, 30 V3 m
Based on your currency / country selection, your order will ship from Newton, New Jersey  
+1 Qty Docs Part Number - Universal Price Available / Ships
CAB-DCU-T2 Support Documentation
CAB-DCU-T2Customer Inspired!USB and Trigger Cable (In Only) for DCU Series and DCC1240 Cameras, 3 m
$78.00
Today

Upgrade Service for Wavefront Sensors

Customers who purchased either a WFS150 or WFS150C wavefront sensor of our superseded earlier generation with fixed lens arrays can upgrade these SH sensors to one of the current WFS150-5C, WFS150-7AR, or WFS300-14AR models. If you order this upgrade service, your old WFS sensor must be sent back to Thorlabs. Please contact your local Tech Support Team for instructions, your choice for the updated model, and other details.

Based on your currency / country selection, your order will ship from Newton, New Jersey  
+1 Qty Docs Part Number - Universal Price Available / Ships
WFS-EXP Support Documentation
WFS-EXPWFS Upgrade Service to Exchangeable Microlens Arrays
$841.00
Lead Time

Kinematic Mount for Wavefront Sensors


This animation shows how to convert between the right- and left-handed orientations.
  • Two 80 TPI Adjusters for ±4° of Fine Tip and Tilt Control
  • 8 mrad Adjustment per Revolution
  • Platform can be Removed and Secured to Either Arm Enabling Left- or Right-Handed Configuration
  • Removable Knobs Expose Adjuster Screws with Hex Socket

Thorlabs' KM100WFS Kinematic Platform Mount provides kinematic control for our CCD-Based and High-Speed CMOS-Based Shack-Hartmann Wavefront Sensors. The mount features a similar design to our KM100PM with a modified mounting platform designed to accommodate the WFS150, WFS300, and WFS20 wavefront sensors. The WFS20 high-speed wavefront sensor can be mounted using the two #8 through holes near the front edge of the plate and the included 8-32 screws. Two M3 through holes are also provided for mounting a WFS150 or WFS300 CCD-based wavefront sensor. Each CCD-based wavefront sensor is shipped with an adapter plate for post mounting; two lengths of M3 screws are included with the KM100WFS so that this wavefront sensor can be mounted with or without the adapter plate attached.

The two pairs of holes for mounting each type of wavefront sensor are offset so that the sensor of any WFS150, WFS300, or WFS20 will sit in the same plane when secured to the mount. Any of our wavefront senors mounted on the platform will also share the same center line, but the sensor heights will vary. The the sensor of a WFS150 or WFS300 with the adapter plate attached will be 0.4 mm higher than than the sensor of a WFS20.

The DCU CCD Cameras can also be mounted on the KM100WFS: remove the two M3 screws from the bottom plate of the camera and use the longer set of M3 screws to attach the camera to the mount. Be sure not to loosen the third screw or remove the bottom plate completely, as this will expose the internal camera electronics.

The two-piece mounting platform assembly is secured to the front plate using two 4-40 screws (3/32" hex), allowing for a left- or right-handed kinematic mount. The two pieces of the mounting platform assembly are held together with two 3-48 screws [5/64" (2 mm) hex]. The animation to the right shows how to convert between the left- and right-handed orientations.

Based on your currency / country selection, your order will ship from Newton, New Jersey  
+1 Qty Docs Part Number - Universal Price Available / Ships
KM100WFS Support Documentation
KM100WFSKinematic Mount for Thorlabs' Wavefront Sensors
$81.75
Today
Log In  |   My Account  |   Contact Us  |   Careers  |   Privacy Policy  |   Home  |   FAQ  |   Site Index
Regional Websites: West Coast US | Europe | Asia | China | Japan
Copyright 1999-2017 Thorlabs, Inc.
Sales: 1-973-300-3000
Technical Support: 1-973-300-3000


High Quality Thorlabs Logo 1000px:Save this Image