Motorized Filter Wheel Selection Guide

Item #	# of Slots	Filter Diameter	Features
FW102C	6	1"	BNC, RS-232 and USB Interfaces No Driver Required
FW103	6	1"	Fast Switching Time

Features

6-Position Filter Wheel
Accepts Ø1" Filters up to 0.25" (6.35 mm) Thick
900 ms Typical Access Time
Programmable Filter Sequences
SM1-Threaded Access Ports
Cage System Compatible
External Trigger In (increment control)
External Trigger Out (provision from software)
Bi-Directional Controls
BNC, RS-232, and USB Interfaces
Local or Remote Control

The FW102C stepper-motor-driven filter wheel will be the successor to the FW102 and FW102B motorized filter wheels. As with its former counterparts, the FW102C wheel measures Ø4" and will accomodate up to six Ø1" filters up to 0.25" (6.35 mm) thick. Each port is equipped with SM1 threading, making it compatible with our lens tube line. In addition, the filter wheels are cage compatible via the four 4-40 taps surrounding each filter access port. The filter wheel in intended for use in a host of automated applications including color CCD photography, fluorescence microscopy, and photometry.

Remote or Manual Operation
Filter selection can be made manually from the push buttons on the unit, or remotely from a USB 2.0 interface, BNC input, or RS-232 connection. The BNC input accepts a TTL level signal to trigger the rotation of the filter wheel. An easy-to-read display indicates the filter selection; the display intensity can be adjusted, making this filter wheel a nice choice for light-sensitive environments.

Mounting Options
The filter wheel design provides easy mounting to optical instruments. Two SM1-threaded ports are provided on the FW102C. Thorlabs offers an extensive selection of adapters (C-mount camera, microscope, and telescope mounts) for mating our SM1-compatible components to other thread standards. Removable covers are provided to allow either or both ports to be opened. The unit is powered by a 12 volt DC supply (provided with the unit).

Specifications*
Access Time for Adjacent Locations (Typ.)	900 ms
Accuracy/Repeatability	±2°
Filter Diameters	1"
Filter Thicknesses	≤0.25" (6.35 mm)

*As this system is still in development, all specifications are subject to change.

Programming & Remote Control
Automation of filter sequences is available through the USB 2.0 interface. A simple command language facilitates the filter selections and the retrieval of filter status. The FW102C comes with the controller, filter housing, a filter wheel, a simple-to-use GUI application program, a 12 Volt DC supply, and 6 threaded retaining rings for holding the Ø1" optics in place.

Computer Control Connections

D-type Female

DB9 Female

USB 2.0 Mini-B

Type A to Mini-B Cable Included

Pin	Connection	Pin	Connection
1	N.C.	6	Connected to Pin 4
2	TxD (From FW102C)	7	N.C
3	RxD (To FW102C)	8	N.C
4	Connected To Pin 6	9	N.C.
5	Signal Ground	9	N.C.

Input*/Output Trigger

BNC

*5.3 Max Input

Software for the FW102C Motorized Filter Wheel

Software

Version 3.2.0 (April 10, 2013)

Standard full software version including a redesigned GUI.

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 1 2 3 4Very Useful

Enter Comments Below:

Characters remaining 8000

Posted Comments:

Poster: jlow

Posted Date: 2012-10-11 16:43:00.0

Response from Jeremy at Thorlabs: You can control the FW102C through MatLab via a command line interface. The settings for the COM port is laid out on page 10 of the manual (http://www.thorlabs.com/Thorcat/20200/FW102C-Manual.pdf). The syntax and the commands are on page 11. You can also accomplish this via the ActiveX control. The ActiveX methods are laid out on page 12 of the manual. If you want to convert the C++ code to MatLab, you could possibly accomplish that through the MEX-function in MatLab.

Poster: hwei

Posted Date: 2012-10-10 09:09:57.597

Hi, I understand that the software support LabView and C++. I'm just wondering if I can control the wheel from Matlab. Thanks. Hong Wei

Poster: tcohen

Posted Date: 2012-09-13 16:02:00.0

Response from Tim at Thorlabs: If your FW102C is having difficulty cycling through the filter positions and the display is reading E1, it may be an internal mechanical problem indicating friction in the rotation. I will contact you to get more information so that we can provide you with a corrected unit as soon as possible.

Poster: jscheuch

Posted Date: 2012-09-13 15:11:41.0

I am using the FW102C and I received the error code E1 on the LED display. What does this code mean?

Poster: bdada

Posted Date: 2012-05-31 18:47:00.0

Response from Buki at Thorlabs: We were successful in communicating with and controlling the filter wheel with uManager. Please check the baud rate under the configuration; if you did did not change it from the default setting of 9600 it will not work unless you previously changed the baud rate setting of the Filter Wheel. Please contact TechSupport@thorlabs.com to discuss this further.

Poster: bdada

Posted Date: 2012-05-31 16:13:00.0

Response from Buki at Thorlabs: Thank you for your feedback. I'm sorry you're having a problem using the FW102C with uManager. We are currently running some tests and will provide more detailed results shortly that will hopefully resolve the issue you're experiencing. We do not have your contact information, so please email TechSupport@thorlabs.com if you want to have direct communication with us and a Software Engineer regarding this issue.

Poster:

Posted Date: 2012-05-30 17:35:24.0

We purchased the filter wheel FW102C and thought it can be used with uManager. Unfortunately, it doesn't work on our hand. The software can recognize the COM and the filter wheel in the setup process. However, there is no hardware response (i.e. wheel switch) when capturing. Does anyone (or the manufacturer) have a way to make it work? At the same time, others need to be cautious if you want to purchase filter wheels to pair with micromanager. TOFRA has cheap filter wheels that we have tested to work with uManager.

Poster: tcohen

Posted Date: 2012-05-24 15:05:00.0

Response from Tim at Thorlabs: Thank you for your feedback! Some noise can occur in the device based on the play in the gears and does not indicate a problem. In addition, the filter wheel can be discriminatory positioned clockwise or counterclockwise. I will contact you to see if your device is operating normally or needs repair and to provide information on the control.

Poster: alee

Posted Date: 2012-05-23 07:09:53.0

Hi, I have been using a FW102C for a few months now and am starting to have a few problems, when moving the wheel in one direction it works fine, when I try and move the wheel in the other direction the move is much noisier and takes longer, do you know what is causing this and if it is damaging the wheel? This happens regardless of whether I use the actual buttons on the filter wheel or move it programatically. Is there a way of forcing the filterwheel to move in one direction only using serial communication, i think at the moment the filter wheel just takes the quickest route to it's new position in my program.

Poster: tcohen

Posted Date: 2012-04-19 17:09:00.0

Response from Tim at Thorlabs: Thank you for your feedback! ActiveX components will not run within a 64bit client environment. However, drivers are included with the software package and the FW102C can be used with command line language through the RS232 port.

Poster: robert.prevedel

Posted Date: 2012-04-19 11:58:20.0

Hi, is the ActiveX interface of the GUI interface for the FW102C 32bit? I need to control it through LabViews 64bit and found out that the APT software does not support 64bit e.g. Alternatively, is it possible to use the RS232 connection through LabViews and would this work on a 64 bit platform? Please let me know, cheers, Robert

Poster: tcohen

Posted Date: 2012-03-28 14:27:00.0

Response from Tim at Thorlabs: Thank you for your feedback. The FW102C has an accuracy of +/- 2 degrees.

Poster: plascottages

Posted Date: 2012-03-27 08:43:04.0

Do you have any data on the positioning accuracy of the wheel. I would like to use the device for selecting between different masks - each etched into a 1" diameter disc - but I need to check how well each will be positioned.

Poster: bdada

Posted Date: 2012-02-08 20:53:00.0

Response from Buki at Thorlabs to huiwang.ai: Thank you for your feedback. To use the FW102C as a shutter or "block", you would need to fill one of the filter wheel positions with an SM1PL - SM1 Plug. You could then use Micro Manager to move the wheel to the position which has the SM1PL installed in order to "block" the light. We have contacted you for further support.

Poster: huiwang.ai

Posted Date: 2012-02-01 16:42:33.0

We now have two FW102C in the lab in one system. They are doing their job well. We hope to get two other filter wheels to control the light path of our other fluorescence microscope (one excitation, one emission). We also hope that we can use a "block" filter in the wheel to work as a shutter. We did some investigation, and found that the ones from Sutter can do this (see the link below). We tried our own FW102C, and cannot figure out how to do the job. Now I believe it needs some work on the uManager software adapter. Could you possibly help us on that? http://micro-manager.3463995.n2.nabble.com/filter-wheel-as-shutter-tt4952897.html#none

Poster: bdada

Posted Date: 2011-10-31 16:07:00.0

Response from Buki at Thorlabs: Thank you for using our feedback tool. It sounds like you are trying to control the filter wheel through the ActiveX control. We have a list of ActiveX methods which can be found on page 12 of the manual at http://www.thorlabs.com/Thorcat/20200/20242-D02.pdf. The methods are only used to do text-based control. While we do not provide full support for 3rd party software, please do not hesistate to contact TechSupport@thorlabs.com for further assistance.

Poster: eugene_l

Posted Date: 2011-10-24 06:19:50.0

I couldn't use AxtiveX contol in Java. May be you replace your ActiveX control(OCX) on ActiveX object (simple COM object). How I think, your ActiveX control is not used to display any visual information. Eugene B.

Poster:

Posted Date: 2011-10-21 21:16:20.0

I couldn't use AxtiveX contol in Java. May be you replace your ActiveX control(OCX) on ActiveX object (simple COM object). How I think your ActiveX control is not used to display any visual information. Eugene B.

Poster: jjurado

Posted Date: 2011-06-27 17:55:00.0

Response from Javier at Thorlabs to zwizhy: Thank you very much for contacting us. You can certainly use the same code you developed for the FW102B with the FW102C filter wheel. The communications protocol is identical for both B and C versions.

Poster: zwizhy

Posted Date: 2011-06-27 00:57:49.0

Hello, I made a code for fw102b with the api from the manual. can i use the code directly to control a fw102c? Hope your reply. Please answer quickly . Thank You. Customer Email: zwizhy@gmail.com This customer would like to be contacted.

Poster: bdada

Posted Date: 2011-06-09 12:37:00.0

Response from Buki at Thorlabs: Thank you for your feedback. The internal threading on the FW102C is SM1 (1.035"-40) and the tolerance is ±0.005". These are meant to hold regular 1" optics, depending on the tolerance of the optics you use. Please contact TechSupport@thorlabs.com if you have more questions about this matter.

Poster: rmontminy

Posted Date: 2011-06-07 15:24:27.0

Filter wheels specify they hold 1" diameter filters but dont actually call out a tolerance in the available literature. We use this wheel with off the shelf filters and sometimes they dont fit so were forced to sand the edges of the filters. I would assume these wheels are meant to hold commercially available 1" optics?

Poster: bdada

Posted Date: 2011-04-29 12:29:00.0

Response from Buki at Thorlabs: Thank you for your feedback. The FW102C has SM1 (1.035"-40) threading. If your light source is threaded, you can use one of our adapters to mount your light source to the FW102C filter wheel. Please review our selection of adapters by using the following link: http://www.thorlabs.com/NewGroupPage9.cfm?ObjectGroup_ID=1524. If your light source is unthreaded or if you have further questions, please contact TechSupport@thorlabs.com

Poster:

Posted Date: 2011-04-28 21:03:48.0

Hi, i want to use this filter wheel to select light from Sutter Lambda LS, do you have any suggestions on which mounting adaptors should I order? I want to save some money, since the Sutter system (controller + filter wheels) is very expensive.

Poster: carsten.schmidt

Posted Date: 2011-03-15 17:01:59.0

Hi. I am using a couple of FW102B and FW102C since the year 2008. I am frequently experiencing the same problems as smcmanus and guspank: I am loosing the connection to filterwheel after a couple of hours. My workaround was to include a relay, which switched off the power to the FW. After 10 seconds power was restored and everything was fine again. Now Ive got a couple of questions: 1) I have one system, where this doesnt work anymore. It can take hours or even a reboot to reestablish the communication. The specific fw102b dates back to 06/2009, application s/w update from vs1.0 to vs1.02 (my newest version) didnt help. The fw worked more or less fine with the error occuring only once every three months, but now it occurs everyday. In an older post I read a firmware update might help? My issues got worse after I changed the instruments setup (more data is forced through the USB ports). Three other fw102b work fine with the new setup. LabView Errors are: Driver Status: (Hex 0xBFFF0015) (time out?) and (Hex 0xBFFA1190) The session handle is not valid. 2) The fw was excessively used (hundred thousands of revolutions). Has it possibly reached the end of its expected lifetime? How do I notice if a fw does? 3) My FW102C are realtively new. Do I have to expect the same issues? Until now everything works fine! Thanks in advance.

Poster: jjurado

Posted Date: 2011-03-15 14:27:00.0

Response from Javier at Thorlabs to carsten.schmidt: Thank you for submitting your inquiry. You can try updating the firmware to the latest version; however, if the wheels really have several 100,000 cycles on them then they are getting very close to the end of their life and the firmware update will not help. The loss of communication and the need to cycle the power is an indication that the FW102B is not completing the commanded move. This occurs more frequently as the wheel ages. The latest firmware is a little more robust in trying to force the wheel to complete the move, but even this does not work all the time. The FW102C will not have this issue, as its life time is much longer than that of the FW102B.I will contact you directly for further support.

Poster: jjurado

Posted Date: 2011-02-17 10:31:00.0

Response from Javier at Thorlabs to starandwave: Thank you for submitting your request. Although we do not have supporting documentation for C# applications, you can certainly control the FW102B filter in this environment. You can establish communication by setting up a communication port and passing the commands outlined in the manual: http://www.thorlabs.com/Thorcat/16600/16667-D02.pdf Please note, however, that this filter wheel has been superseded by the FW102C. The programmings requirements will be the same.

Poster: starandwave

Posted Date: 2011-02-16 05:30:14.0

hello. We have plan to use FW102B. This product is possile to control using C# language for motorized control? Please answer quickly . Await for your reply.! Thank You.

Poster:

Posted Date: 2010-12-22 10:46:06.0

For our application, the FW102C has no advantage over the FW102B. It has way too much backlash in its gearing and the device is much larger and heavier than it needs to be. The on/off switch needs to be relocated or recessed as jhorton pointed out. We bought one to see if it can replace the FW102B in our system, but it doesnt come close.

Poster: tor

Posted Date: 2010-11-15 09:26:57.0

Response from Tor at Thorlabs to shshim: Thank you for your inquiry. Per our direct response, we provide two methods for integration – a serial command line interface and an ActiveX control (OCX). The command line interface is documented in the manul; sample code for Labview and C++ is provided for the ActiveX control. Please let us know if you have further inquiries.

Poster: shshim

Posted Date: 2010-11-14 15:25:17.0

Id like to make my own python code to integrate FW102C with other instruments such as camera, AOTF, shutters, and so on. What dll and command should I use to communicate with the filter wheel? Would you provide any user guide or manual for such external control? Thanks in advance!

Poster: Thorlabs

Posted Date: 2010-07-27 09:29:24.0

Response from Javier at Thorlabs to jhorton: Thank you very much for your feedback. I will share your comments with our electronics department. We will take this into account for future revisions and improvements of this filter wheel.

Poster: jhorton

Posted Date: 2010-07-23 17:47:21.0

The on/off switch is the only part that prevents mounting the FW flush along that face, so it would be much better to locate the switch down with the advance position buttons. Also The gigantic body is now a horrible inconvenience when compared to the very compact FW102b

Poster: apalmentieri

Posted Date: 2010-01-27 09:23:56.0

A response from Adam at Thorlabs to thabaaron: When posting a command throught the serial connection the > usually means it is ready for the next command if it prints below the output. When it prints above the output, it means that the program is out of sync with the serial port and you must escape the sequence. To fully answer this question we will need to know how you are communicating with the device. We suggest using hyperterminal. I will contact you directly to get more information.

Poster: thabaaron

Posted Date: 2010-01-26 22:57:02.0

I am communicating with a FW102 through a serial connection, and whenever the filter wheel prints to the serial port(for example, after a pos? command), it prints a > over the top of the output. Any suggestions for a fix?

Poster: apalmentieri

Posted Date: 2010-01-14 12:18:11.0

A response from Adam at Thorlabs: Are you using this unit on a USB hub? If so, connecting the unit directly to the computer may fix this problem. If you cannot disconnect the unit from the hub and the firmware update did not work, we can swap out the unit with a new unit from stock. I will email you directly to get more information.

Poster: acarlott

Posted Date: 2010-01-14 11:44:53.0

We are having a lot of problems with the FW212B: using the USB cord, the connection is often lost and the only way to get it back is to restart the computer. When manually controlled the filter wheel often gets blocked or can even begins to run endlessly. It has to be shutdown to be used again. All these problems have happened with (and previously, without) the updated firmware. Does Thorlabs knows any solution to these problems ?

Poster: apalmentieri

Posted Date: 2010-01-12 12:31:34.0

A response from Adam at Thorlabs to guspank: Our last firmware update on September 28, 2009 to version 1.04 should have corrected this problem. I will send you an email to verify the exact firmware version you are using.

Poster: guspank

Posted Date: 2010-01-12 11:16:28.0

I am having the exact same problem as poster smcmanus on 4/15 where the FW102B intermittently locks up to the point where even the manual buttons do not work until power is cycled on the device. I would be very interested to know more details on the source of this issue and its resolution. I can easily add a larger delay, though I doubt this is the problem as we only send one command every so often. We do access the filter wheel through a USBGear (USBG-7U2ML) hub. Unfortunately, removing the filter wheel from the hub is not a viable option as it is integrated into a system. None of the other devices have any issues, only the filter wheel. Is there any way to work around this issue, or at least to recover from it through software?

Poster: apalmentieri

Posted Date: 2009-12-30 13:42:10.0

A response from Adam at Thorlabs to Tom: Tom, I am sorry, but we had to remove the feedback from 12/28 because it was incorrect. Please note that the FW102B and FW212B do have permanent magnets.

Poster: killian

Posted Date: 2009-12-28 14:12:43.0

Are there any permanent magnets in the Motorized Filter Wheels? Regards, Tom Killian

Poster: klee

Posted Date: 2009-10-28 16:28:53.0

A response from Lou at Thorlabs to cdorrer: You might have an issue with the firmware in the wheel not retaining updated info in the EPROM. We will send you update program to fix it. Unzip the file into some directory and then with the wheel attached and turned on but no applications running, run Reprogram.exe. This should update the firmware. If you should change the baud rate, once you reconnects to the wheel at the new baud rate, you should send the "save" command. If not, when you cycles power to the wheel it will revert back to the original baud rate.

Poster: cdorrer

Posted Date: 2009-10-28 12:54:31.0

The baud rate for the serial port switches back to 9600 baud even after changing it to 115200 and saving the change in the Automation Explorer. If the baud rate is set through the Windows Hardware control panel, a problem occurs because the VISA rate (9600) is different from the Windows rate (115200). Additionally, sessions open via the Automation Explorer or directly with Labview do not operate (e.g. generate a Framing Error). This occurs on two different computers.

Poster: leichner

Posted Date: 2009-06-23 09:16:16.0

A FTDI type of device needs to have a driver installed. This is what enables RS232 protocol to work with a USB port. They are both serial but the protocol is different. Typically Windows assigns a USR type of interface (RS232 to USB) to COM3 or COM7. You can force the COM7 assignment to COM3. As long as the hardware is connected the port assignment remains. Once the a device is disconnected the port setting can change next time around. The application software must have the option to negotiate port settings. If a fixed dedicated port is necessary then the argument not to do away with RS232 is very strong.

Poster: andrew.litak

Posted Date: 2009-06-22 11:03:40.0

Recently converted older serial interface FW102s to USB FW102Bs. Since windows assigns com ports dynamically, is there any way to identify each filter wheel so it will always be recognized regardless of what new USB device maybe be plugged in or which USB port its in?

Poster: Greg

Posted Date: 2009-04-16 11:23:33.0

A response from Greg at Thorlabs to smcmanus: Thank you for your feedback on the FW102B. There are a few different possibilities that may be causing the filter wheels to stall. First, there may be too many devices connected to your computer as USB is shared. If you are using a USB hub, please try connecting the filter wheels directly to your computer. We have seen issues with certain hubs not working as well as others when multiple devices are connected. If you send commands too quickly to the filter wheels, you may fill up the memory buffer. This can stall the system. If you send commands only after the wheel has completed a move, this will not be an issue. The wheel takes roughly 600 ms to change position, thus sending commands after a greater interval of time is ideal. A member of our Technical Support group has been put in contact with you to ensure that we identify the source of your issue and resolve it.

Poster: smcmanus

Posted Date: 2009-04-15 16:37:47.0

I have four of the FW102B wheels with USB connection. I intermitently loose communication with some of the wheels during testing. Once the communication is lost I have to kill power to the filter wheel to get it to respond again. Even the manual control no longer works until the power is cycled. Any ideas why this happens? Do I need a special driver or are the Windows XP defaults okay? Thanks, Sid

Poster: Greg

Posted Date: 2009-03-27 13:38:38.0

A response from Greg at Thorlabs to oarteaga: Thank you for submitting feedback. A member of our Technical Support team has been forwarded your feedback and will be in contact with you soon so that you can get the FW102B working.

Poster: oarteaga

Posted Date: 2009-03-27 10:06:43.0

We have just set up the filter wheel, but we are not able to communite with it with usb. The driver is correctly installed and a new emulated serial port appears in the computer (COM5). However when we try to connect with if we get the message: "Unable to connect to FW102B". The same in 3 different computers. Of course we select the appropiate com port and baud rate in the configuration setup of the program.

Poster: Laurie

Posted Date: 2008-08-05 08:52:27.0

A response from Laurie at Thorlabs to iyerv: Thank you for your interest in our FW series of motorized filters. Based on the information you provided in your post, I would suggest that you try the following: (1) Ensure that your light is striking the filter wheel at normal incidence. (2) Ensure that all filters are mounted such that the incident beam is also normal to their surfaces (Use canned air to clean out any dust particles that may be in the filter wheel slots). (3) Although our standard retaining rings generally produce good results, you could consider switching to our stress-free retaining rings (SM1LTRR). If you continue to experience unsatisfactory results after trying these things, please let us know.

Poster: iyerv

Posted Date: 2008-08-04 16:03:56.0

Weve just set up this filter wheel, and notice that there are substantial shifts in the beam position at about 1m distance, about an order-of-magnitude greater than I noticed with a rival filter wheel product (New Focus) that Ive used in the past. Can you recommend anything to improve this? For one, Im surprised theres no O-ring with each filter to ensure consistent mounting.

Poster: Tyler

Posted Date: 2008-06-26 16:42:22.0

A response from Tyler at Thorlabs to jjohnson: I will have an applications engineer start a dialog with you about this issue. However, in short, each filter wheel has a unique USB id. When a PC sees a new USB device for the first time it creates a registry key where it associates the USB id with a serial port. The next time it sees that device, it attempts to assign the same port to the device as the previous time. This works fine unless some other device has been attached that is now assigned to that port. In that case, the next available port is assigned to the device. So if you attach 5 filter wheels, and there are no new devices taking up any of the original 5 ports, then everything should be fine even if you attach them to different USB ports or use a different USB hub.

Poster: jjohnson

Posted Date: 2008-06-25 13:16:24.0

Hi, My application will use up to 5 filter wheels (so sometimes a usb hub will be used). What would be the process to assure that each filter wheel gets the same COM port each time the system comes up? (users would have a hard time with this!) Thanks, J

Click on any phrase below to search our site using our new Search Engine:

1 aperature 1' aperature 1 Filters 1' Filters 1 inch aperature 1 inch Filters 1 inch shutter 1 shutter 1" aperature 1" Filters 1"-aperature 12 position 12 Position Filter Wheel 12 Position Motorized Filter Wheel USB 12-Position Filter Wheel 1-inch aperature 1-inch Filters 4 4 inch 6 position 6 Position Filter Wheel 6-position 6-Position Filter Wheel Astronomyfilter wheel driven C mount camera C-mount camera combination filter filter holder Filter mount Filter Wheel Stations Ø1 filter wheel system filter wheel USB filter wheel USB 2.0 filter wheel USB2.0 filter wheel with USB filter wheel with USB 2.0 filter wheel with USB2.0 Fluorescence Microscopes four inch FW102 FW102A FW102B FW102C FW212B FWSH102 Interchangeable Filter Wheels laser shutter microscope Modern Astronomy motor motor driven filter wheel motor driven filter wheels motor-driven filter wheel motor-driven filter wheels motorized Motorized Filter Wheel motorized flip mount motorized-filter wheel motoroized filter wheels ND filter one inch aperature one inch shutter optical modulator optical modulators optical mount shutter Six Position Six Position Filter Wheel Six-Position SM05 SM05 compatible SM05-compatible SM1 SM1 compatible SM1-compatible telescope mount twelve position wheel

View All »Matching Part Numbers

Stepper-Motor-Driven Filter Wheels

Motorized Filter Wheel Selection Guide

Features

Computer Control Connections

D-type Female

USB 2.0 Mini-B

Input*/Output Trigger

BNC

Software for the FW102C Motorized Filter Wheel

Software