アカウント作成  |   ログイン

View All »Matching Part Numbers


カートは空です
         

ベンチトップ型ブラシレスDCモーターコントローラ


  • One-, Two-, and Three-Channel Models Available
  • Supports 3-Phase, Brushless, DC Servo Motors
    with up to 5 A Peak Coil Current
  • Encoder Feedback
  • APT™ Control Software Suite

BBD203

3-Channel Controller

BBD201

1-Channel Controller

GUI Panel

Related Items


Please Wait
他のブラシレスDCサーボコントローラ
K-Cube™ Single-Channel Controller
BBD102_Rear
Click to Enlarge

BBD202の背面パネル

MJC001 Full Set Up
上の写真は、ブラシレスDCモーターコントローラBBD202とジョイスティックコンソールMJC001、Olympus製顕微鏡XI71に取り付けられたXYステージMLS203です。

特長

  • 当社の3相ブラシレスDCサーボモータ製品をサポート
  • エンコーダによる速度と位置の閉ループ制御
  • ユーザI/Oポートがモニタ用エンコーダ信号を表示
  • AUX I/Oポートがデジタル入力と出力信号を表示
  • apt™ソフトウェア制御による完全サポート
  • 簡単USB接続
  • すべてのapt™コントローラ製品とシームレスな統合が可能
  • ActiveX® ソフトウェア グラフィカルパネル

BBDシリーズのブラシレスDCモーターコントローラは、高速(1秒につき数百ミリ単位)および高いエンコーダ分解能(100 nm未満)での操作が必要なモーションコントロール用途に適しています。このコントローラは、3チャンネルまでの高精度モーションコントロールを行い、当社のMLS203シリーズ2軸走査ステージと併用することで、顕微鏡サンプルの操作をはじめとする幅広い用途にお使いいただけます。最新のデジタルおよびアナログ技術と高帯域幅、高出力のサーボ制御回路により、当社製の回転式およびリニア式3相ブラシレスDCサーボモータ製品を駆動する設計となっています。

これらのコントローラは、apt™シリーズ製品と組み合わせることにより、標準的な制御およびプログラミングインターフェイスを提供し、自動モーションコントロール用途に簡単に組み入れることができます。このユニットは、現場での再プログラミングが可能なので、新しいプログラミングインターフェイス(顕微鏡標準コマンドセットなど)を追加して、新しいファームウェアに合わせアップグレードすることが可能です。

USBで接続するだけで、簡単にパソコンで制御できます。複数のユニットを、多軸モーションコントロール用途向けに、標準USBハブを経由し、1台のパソコンへ接続することができます。apt™ソフトウェアと組み合わせ、複雑な動作シーケンスを短時間で稼動させることが可能です。すべての関連操作パラメータは、当社のステージおよびアクチュエータ製品用に自動設定されています。「モーションコントロールソフトウェア」タブで詳述されている広範なActiveX®プログラミング環境を使うと、高度なカスタム制御用途やシーケンスが可能になります。このActiveXには、LabviewやC++、Matlabといった幅広い開発環境用ソフトウェアが含まれています。

BBDシリーズへのソフトウェアインターフェイスは、他のapt™シリーズコントローラと高度に統合されているので、簡単にシステムへ組み込み、短期間で習得することができます。このユニットはapt™シリーズの新製品コントローラですが、十分な機能を有するapt™シリーズPCソフトウェアツールにバックアップされているので、箱から出してすぐにお使いいただけます。

尚、BBD20xシリーズのコントローラは、特にベンチトップでご使用いただけるよう設計されています。19インチラックの用途にはコントローラRBD201をご使用ください。

ブラシ付きDCサーボモータの制御について
このコントローラは、高出力ブラシレスDCサーボモータ用です。当社のブラシ付きDCサーボモータの制御に関しては、DCサーボモータードライバK-Cube KDC101をご参照ください。

ジョイスティックコンソール(オプション)
ジョイスティックコンソールMJC001は、顕微鏡をお使いになる際にステージを触覚的に手動で位置決めできるように設計されています。このコンソールには、XY制御用の2軸ジョイスティックが付いています。ほとんどの用途において、コントローラ内に保存されたデフォルトのパラメータ設定で、さらに設定する必 要なく箱から出してすぐお使いいただけるので、ホストPCに接続せずにリモート操作を行うことができます。

Item #BBD201BBD202BBD203
Number of Channels123
Drive Connector8 Pin DIN, Round, Female
Feedback Connector15-Pin D-Type
Brushless Continuous Output2.5 A5 A5 A
PWM Frequency40 kHz
Operating ModesPosition and Velocity
Control Algorithm16-Bit Digital PID Servo Loop with Velocity and Acceleration Feedforward
Velocity ProfileTrapezoidal/S-Curve
Position Count32 Bit
Position FeedbackIncremental Encoder
Encoder Bandwidth2.5 MHz (10 M Counts/sec)
Encoder Supply5 V
AUX Control Connector15-Pin D-Type
External System CommunicationsType B USB, Female
Input Power Requirements250 VA
Volt: 100 to 240 VAC
Freq: 47 to 63 Hz
Fuse: 3.15 A
Dimensions174 mm x 245 mm x 126 mm
(6.85" x 9.65" x 4.96")
240 mm x 337.9 mm x 124.8 mm
(9.5" x 13.3" x 4.9")
Weight3.46 kg (7.6 lb)6.1 kg (13.42 lb)

モータードライブ

メス型

BBD MOTOR DRIVE

PinDescriptionPinDescription
1Motor Phase V5Stage ID
2GND6GND
3Temp Sensor (Not Used)7Motor Phase W
4Motor Phase U8Enable

フィードバック

Dタイプメス型

BBD FEEDBACK

PinDescriptionPinDescription
1Not Connected9GND
2GND10Limit Switch +
3Not Connected11Limit Switch -
4Index -12Index +
5QB -13QB +
6QA -14QA +
7a5 V15Not Connected
8a5 V
  • 7と8は内部短絡

ユーザI/O

Dタイプオス型

15 Oin DIN Male

PinDescriptionPinDescription
15 V9QA +
2Trigger IN10QA -
3Trigger OUT11QB+
4Ground12QB -
5Ground13Index/Ref +
6For Future Use14Index/Ref -
7For Future Use15Ground
8For Future Use

補助I/O

Dタイプメス型

BBD FEEDBACK

PinDescriptionPinDescription
1Digital O/P 19Digital Ground
2Digital O/P 210Digital Ground
3Digital O/P 311For Future Use
4Digital O/P 412For Future Use
5Digital Ground13Digital I/P 4
6Digital I/P 1145 V Supply O/P
7Digital I/P 2155 V Supply O/P
8Digital I/P 3

ハンドセット

Mini DINメス型

Handset Connector

PinDescriptionPinDescription
1RX (controller intput)/RS2324Supply Voltage for Handset 5V
2Ground5TX (controller output)/RS232
3Ground6Ground

インターコネクト

Dタイプオス型

9Pin DIN Male

PinDescriptionPin>Description
1Not Connected6Not Connected
2RX (controller input)7Not Connected
3TX (controller output)8Not Connected
4Not Connected9Not Connected
5Ground

USB

USB B型メス

Handset Connector

当社では幅広い種類のモーションコントローラを駆動できるよう、Kinesis® ソフトウェアパッケージと従来のAPT™(Advanced Positioning Technology)ソフトウェアパッケージの2種類のプラットフォームをご用意しております。どちらのパッケージも小型で低出力のシングルチャンネルドライバ(K-Cube™やT-Cube™など)から高出力でマルチチャンネルのモジュール式19インチラックナノポジショニングシステム(APTラックシステム)まで幅広い種類のモーションコントローラをカバーするKinesisシリーズのデバイスを制御できます。

Kinesisソフトウェアには、最新のC#、Visual Basic、LabVIEW™またはその他の.NETに対応する言語を使用してカスタムプログラムを作成するサードパーティの開発者向けに、.NETコントロールが付属しています。また、.NETフレームワークを使用しない用途向けに低級言語用のDLLライブラリも付いています。センターシーケンスマネージャが、当社の全てのモーションコントロールハードウェアの統合と同期をサポートします。

Kinesis Software
KinesisのGUIスクリーン
APT Software
APTのGUIスクリーン

当社従来のAPTシステムソフトウェアプラットフォームは、C#、Visual Basic、LabVIEWまたはその他のActive-Xに対応する言語を使用してカスタムプログラムを作成するサードパーティの開発者向けに、ActiveXをベースとしたコントロールが付属しています。また、ハードウェア無しでカスタムプログラムの開発を行うためのシミュレーターモードも付いています。

これらの共通のソフトウェアプラットフォームにより、あらゆるKinesisとAPTコントローラをシングルアプリケーションに簡単に組み込むことができます。ソフトウェアツールは1セット習得するだけで共通した操作が可能です。シングルチャンネルシステムからマルチチャンネルシステムまで、あらゆるコントローラを組み合わせ、全てを1台のPCのソフトウェアインターフェイスから制御することが実現可能です。

このソフトウェアパッケージを使用するには2つの手段があります。GUI(グラフィカルユーザーインターフェイス)ユーティリティを使用したコントローラとの直接対話ならびに「out of the box」コントロール、またはご選択の開発言語でカスタム統合の位置決めやアライメントソリューションを簡単にプログラムできる一連のプログラミングインターフェイスです。

APTシステムソフトウェアをよりご理解いただけるために様々なチュートリアルビデオもご用意しております。ビデオではソフトウェアの概要とAPT Configユーティリティをご説明しています。また、ソフトウェアのシミュレーターモードを利用すると、コントローラを接続しないでソフトウェアを試すことができます。その方法を説明したビデオもあります。これらのビデオは「APTチュートリアル」タブ内のリンクからご覧いただけます。

ソフトウェア

Kinesis バージョン 1.14.23

このKinesisソフトウェアパッケージには、当社のKinesisならびにAPT™システムコントローラを制御するためのGUIが含まれています。

下記もご用意しております:

  • 通信プロトコル
Software Download

ソフトウェア

APT バージョン 3.21.4

このAPTソフトウェアパッケージには、当社のAPT™およびKinesisシステムコントローラを制御するためのGUIが含まれています。

下記もご用意しております:

  • 通信プロトコル
Software Download

これらのビデオでは、プログラミングおよび非プログラミングの両方の点から、APTシステムソフトウェアの使用法の基礎をご説明しています。付属のAPTユーティリティの使用法を示したビデオもあるので、箱から出してすぐにAPTコントローラを制御できます。また、Visual Basic、LabView、Visual C++を使うカスタムソフトウェア用のプログラミングの基礎を説明した多くのビデオもありますのでご覧ください。

 Click here to view the video tutorial 

更に、プログラマの方のためにLabViewを用いてAPTソフトウェアをプログラムするためのガイドもございます。

Labview IconClick here to view the LabView guideLabview Icon

Posted Comments:
Mathias Hüne  (posted 2019-11-15 09:44:21.103)
Hi, I want to trigger the controller externally with a digital trigger. In the APTUser software, I set the Input trigger on my desired trigger behaviour (e.g rel move on rising edge) and this works so far. But unfortunately I can not figure out, how I set the distance. In the manual it is written, that the last value from move_rel is used. But either in my APT based python software nor in the APTUser software I have this command. So how can I set this value? I have also tried the Kinesis software, where I also can enable the Trigger. But this did not work at all. Do you have an idea or an example?
cwright  (posted 2019-11-22 09:44:00.0)
Response from Charles at Thorlabs: Hello Thank you for contacting us. The relative move distance is not available through APT’s GUI and must be set through ActiveX controls or serial commands. I will reach out to you directly to help troubleshoot your program.
user  (posted 2019-07-02 12:31:40.44)
Hi, I am having some issues getting this recognized in uManager. I see below that someone else requested some support. Any idea hints as to how to get this the BBD202 recognized? Many thanks for your help. A
AManickavasagam  (posted 2019-07-04 09:46:42.0)
Response from Arunthathi at Thorlabs: Thanks for your query. We will contact you directly with the documentation that might help set up the controller correctly in Micromanager.
Ekin Kocabas  (posted 2019-04-24 19:14:01.243)
Hello, I'm developing a python wrapper for the Kinesis C API to connect to BBD202 with two DDS220 stages in XY configuration. I had the following questions/comments. Current Setup ------------- * Windows 10 64 bit * Using Kinesis Version 1.14.16 C API (64 bit) * Two DDS220 stages connected as XY to a BBD202 controller * Python wrapping via ctypes, homing and basic motion commands implemented Questions/Comments ------------------ 1) TLI_DeviceInfo Struct Reference in Thorlabs.MotionControl.C_API.chm file does not match the definition in the Thorlabs.MotionControl.Benchtop.BrushlessMotor.h file. For instance, in the chm file TLI_DeviceInfo has a field called "maxPaddles" which is absent in the header file. 2) Why does the example code under BMC_Open checks for BMC_Open(serialNo) != 0 to execute the contents of the if statement? Does running BMC_LoadSettings and BMC_StartPolling automatically connect to the controller? 3) Without a BMC_LoadSettings call, position related functions such as BMC_GetRealValueFromDeviceUnit or BMC_GetMotorParamsExt do not work. Are there other inter-functional dependencies? It would be great to have those reflected in the documentation. 4) I try to use BMC_SetLimitsSoftwareApproachPolicy and BMC_SetMotorTravelLimits functions to limit motion by the stages, but BMC_MoveToPosition function overrides the travel limits. What is the proper way to limit the travel range for the DDS220 stages through the C API?
rmiron  (posted 2019-04-25 04:27:22.0)
Response from Radu at Thorlabs: Hello, Ekin. Thank you for taking the time to bring these issues to our attention. I have relayed your feedback internally such that our C_API documentation gets improved. I will try to address your points in order. 1) maxPaddles is a parameter of the TLI_DeviceInfo struct defined in Thorlabs.MotionControl.Polarizer.h. That is why it is mentioned in the .chm file. 2) BMC_Open is the function call which connects the controller to the PC. By checking whether the call returned 0, one is effectively checking whether the connection was initialised successfully. I advise you to add an else statement which prints the returned value (the error code) in case there are any connection issues. 3) Without a BMC_LoadSettings call, the PC does not know what motor parameters to use for conversions between real and device units. Every other method which requires such knowledge will be negatively affected. There are many other similar inter-functional dependencies (some functions need to be called before others in order for the code to run successfully) that are not documented. I agree that this situation needs to be amended. 4) I will contact you directly in order to check whether you have identified a bug, or whether the custom limits get overridden by a different function call. If it is a bug, we will fix it by the next software release. In the meantime, you could bypass the problem by amending your code such that it checks whether a stage has been ordered to move outside of this custom travel range.
aurelien.duboin  (posted 2018-03-21 11:07:26.443)
Good morning, I'm trying to run a MLS203 stage with a BBD202 Controller under Micromanager (build 1.4.23). When using the Thorlabs device adapter library I can connect the controller through a virtual COM, however then the stage moves only along X axis and the delay between 2 moves is approx 10s. The other adapter Thorlabs APTstages appears unavailable in the Hardware configuration wizard of Micromanager despite I'm copying the APT.dll in Micromanager folder. The stage is working fine under Metamorph on the same computer. Can you confirm which adapter I need to use under Micromanager ? Do I have to use APTconfig first to configure the controller ? Many thanks in advance, Best regards
bhallewell  (posted 2018-04-05 04:24:35.0)
Response from Ben at Thorlabs: I will contact you to see if I can assist you. Please note that Micromanager is an Open Source program and so it is possible that changes have been made to the program which is forcing this to not function correctly. It may be worth trying to use an older version of Micro-Manager (1.4.21) where we previously contributed to fixing issues with motor stage movement and XY stage initialization.
davide.musiari  (posted 2017-06-01 17:24:56.09)
Good afternoon, I'm trying to create a c++ program allowing me to control the 2 DDS220 stages through the BBD202 controller. I'm succeeding in importing the .h files and the other libraries, but I don't undestrand how to implement functions, such as motortype. Furthermore, I'm looking for the commands that gives the possibility to communicate with the controller. May you send me an easy example of c++ implementation? kind regards
bhallewell  (posted 2017-06-09 06:03:35.0)
Response from Ben at Thorlabs: The motor type for BBD202 is selected on controller start-up & therefore shouldn't need to be selected. We have some video tutorial resources for controlling our Motion Control hardware through ActiveX controls via use of our APT software package as well as C# .NET managed examples for the BBD202 via our Kinesis package. APT methods are defined in the APT Server help file from the APT software download & Kinesis methods outlined within the .NET API from the Kinesis download. Kinesis is our latest version of software which we would recommend use of. Kinesis Examples Download area (see - BBD Console Managed). https://www.thorlabs.com/newgrouppage9.cfm?objectgroup_id=10285 Note - To query the Stage settings, you can refer to methods outlined in Thorlabs::MotionControl::GenericMotorCLI::Settings::MotorDeviceSettings from the .NET API guide. https://www.thorlabs.com/newgrouppage9.cfm?objectgroup_id=10285 APT Visual C++ Tutorials https://www.thorlabs.com/tutorials/APTProgramming.cfm
simone.decataldo  (posted 2017-05-11 11:57:15.81)
Good morning, We purchased two DDS220 translation stages with its specific control drive BBD202. We manage to move indipendently the 2 linear stages, but now we are facing a problem: we are not able to connect the 2 linear motors and give them simultaneous operations. We believe that the solution is in the APTUser Application, but we haven't found yet; then we hope to receive some technical advice from you. kind regards
bhallewell  (posted 2017-05-22 08:18:59.0)
Response from Ben at Thorlabs: Thank you for your feedback. It is unfortunate to hear that these devices are not currently meeting your expectations. I'll contact you directly to see if I can assist you.
eliana.cordero  (posted 2017-02-14 09:11:45.33)
The APT available to install does not content the BBD202 control unit which enables me to stablish the communication with the controller and the platform. also the Kinetics software does not work, I get a message that indicates that the applciation is going to close and that I should revew the error log. I would appreciate if any solution is suggested. Kind regards, Eliana Cordero
bwood  (posted 2017-02-15 11:13:18.0)
Response from Ben at Thorlabs: I am sorry to hear about your difficulties connecting our BBD202 controller to your computer. This question will likely require additional troubleshooting, so I will be in contact with you directly. However, one piece of advice I can give is that the "Firmware Update Utility" included with APT and Kinesis, is a good tool to use for initial communications troubleshooting. If your controller appears in the utility, that means that basic USB communications have been established with the controller.
chiwon.lee  (posted 2016-11-02 11:27:35.76)
Hello, I'm using BBD01 controller. On trying to do labview programming, I have a problem that my labview sub-vi doesn't communicate with the controller. The error message says that "A software call has been made to a control which is not currently communicating with any hardware. This may be because the control has not been started or due to incorrect serial number or missing hardware.". The serial number that I put on my sub-vi is the same with the one used in the APT User software. The controller is working well through the APT User, but not through the labview.
bhallewell  (posted 2016-11-03 10:00:04.0)
Response from Ben at Thorlabs: I will contact you directly to help you with using APT with LabVIEW. A number of web-based resources including examples, a help guide & video tutorials can be found in the following link. https://www.thorlabs.com/newgrouppage9.cfm?objectgroup_id=8348
okirfan  (posted 2016-10-21 08:01:56.927)
I want to use BBD203 (along with DDS 220) with lockin amplifier SR830, I don't know where to connect SR830 in this Assembly. Also, previously I used newport stuff. Can you provide program for pump probe spectroscopy with these? thanks
msoulby  (posted 2016-10-25 06:35:37.0)
Response from Mike at Thorlabs: We will contact you directly to discuss your application
jwlee  (posted 2016-07-02 03:44:20.337)
I tried to install APT software 32bit in my PC(windows enterprise 64bit). Another computer completely installed but my PC dosen't installed and error massage below, ##IDS_DIFX_X86##. So please, resolve this problem.
bhallewell  (posted 2016-07-04 06:37:15.0)
Response from Ben at Thorlabs: Thank you for your response here. Please ensure that you are downloading & installing either the 32-bit for 64-bit OS version of APT or the full 64-bit software package. https://www.thorlabs.de/software_pages/ViewSoftwarePage.cfm?Code=Motion_Control I would also recommend trying our new Kinesis software package, which includes such benefits as an improved Sequence Manager & improvements to connectivity sensitivities that exist within the older APT framework. This is also free to download & install from the above link.
balaji  (posted 2015-09-24 22:28:15.08)
Hi I have been using a range of APT software driven instruments such as TDC controller, BBD002 servo controller etc., I want to point out that there is some issue with 64 bit software for 64 bit platform. The 32 bit for 64 bit works fine. Secondly and more importantly we have been trying to shift to using USB/serial communication while I have been able to list the com port after enabling Load VCP in the advanced tab of the driver. However having hard time sending commans through serial terminal software such as commdebug, real term etc., They all recogonise the com port but the device is totally unresponsive left to wonder if there is some way to test the communication and if we need to use a FTDI library to issue a write command rather than through terminal software
msoulby  (posted 2015-09-28 10:14:12.0)
Response from Mike at Thorlabs: The VCP setting should be set up as follows. Baud rate = 115200; Flow control = RTS/CTS; Bits per word = 8; Number of stop bits = 1; Parity = NONE. We have contacted you directly with the latest version of the communications protocols for our motion control products and also some brief instructions on how to use this is a terminal emulator, in this case Termite. Using the identify command MGMSG_MOD_IDENTIFY (0x0223) is a good way to check you have established communication with the controller, this command will flash the front panel LEDs of the addressed controller.
yannick.dmello  (posted 2014-07-28 11:42:54.91)
I am using the BBD203 to drive a translation stage and we have encountered two issues: 1. The controller seems to power off if left idle for over a few minutes, this is very inconvenient for remote controlled operation and I have not yet found a fix. I am using two controllers and only one of them has this issue. Can this setting be changed? 2. The translation stage does not move in exactly 0.1um precision though the software claims it does. How exactly can this be calibrated? Thank you
msoulby  (posted 2014-07-29 06:24:12.0)
Response from Mike at Thorlabs: (1) The controller should not power off after just five minutes, I suspect that there could be an issue with that controller especially in light of the fact that your second controller seems to operate correctly. We will need to get the controller back for evaluation/repair. Our US office will be in contact with you shortly regarding this. (2) The brushless DC motors all make use of a linear encoder to give feedback from the stage to the controller to obtain the correct position, we are confident that the encoder gives the correct distance travelled. This closed loop system uses a PID control loop to control how the stage reaches the final position, these PID settings can be tuned in the settings panel of APT to suit different customer applications to account for load, acceleration, speed, move size, etc.. As you are using such a small move size it will be worth taking a look through the BBD203 manual for more details on the settings and how they affect stage movements, the manual can be viewed here http://www.thorlabs.de/thorcat/23900/BBD203-Manual.pdf
ilr  (posted 2014-07-01 20:46:15.93)
Hello again. Did you manage to find a workaround to access motor's serial number from the controller? We are considering making a comercial product based on your BBD controller and MLS motors. Obviously, we would like to protect our product from being purchased once, but used on many setups with the same controller (just by replugging cables). So a workaround will be very much appreciated!
msoulby  (posted 2014-07-03 10:28:15.0)
Response from Mike at Thorlabs: Unfortunately there is no work around for this. Our controllers can often operate with a number of stage variants which is why we have the APT config utility so that the user can assign each controller serial number to a certain stage or axis. This controller serial number is how each stage is identified in APT. This means that the controller is not limited to using just one type of stage. However this does mean that attention needs to be paid to how the cables are connected to ensure you assign the correct axis to that particular channel.
ilr  (posted 2014-01-22 02:42:11.16)
Thank you again for the explanation, Mike! Since HWSerialNum is a property from the MG17Motor control, I thought I was setting up a motor's S/N, but now I see what you mean. I would really appreciate any workaround.
ilr  (posted 2014-01-20 17:46:58.493)
Thank you for your reply, Mike! I am a bit confused now, even though I have programmed fully one setup. Does the motor serial number belong to the controller or to the translation stage (MLS203)? I am asking because I would like to programmatically bind a translation stage to a particular controller, so that one cannot plug another (but same model) stage to a given controller. I was thinking to use controller's S/N together with motor's S/N. Is that possible?
msoulby  (posted 2014-01-21 05:00:24.0)
Response from Mike at Thorlabs: There is a motor serial number and this is read by the BBD202 controller, however as this is not generally required we did not develop an ActiveX method to help expose this. The only serial numbers you can use will be the serial numbers of the controller channels and not the motor. As the APT server does not see the motor it only sees the controller then each serial number needs to be configured to a particular stage before run time in our APT config utility. The APT config utility sets parameters used by the APT server specific to the stage you are using, for example travel length, max velocity, max acceleration, etc… these settings are all stored in the APTServer.ini file in the windows directory. As the APT server does not see the motor it is not possible to set a controller to a specific motor; currently the only way would be to ensure the same channel and stage have their connectors clearly labelled. We are however looking to see if there might be a workaround to access this value from the controller and we will contact you directly with our findings.
ilr  (posted 2014-01-18 17:09:14.277)
I am using BBD202 controller and two motors with my own software to make 2D scans. To enumerate the motors and get their serial numbers, I use the technique described in the manual. In particular, I use MG17System object and its methods GetNumHWUnits and GetHWSerialNum. Those serial numbers are then used with MG17Motor to address the particular motor. Now I would like to buy one more BBD202 controller, which will be controlled simultaneously with the same software (my own). How do I distinguish between the two controllers? I know that they have different serial numbers, but I could not find any reference in the manual saying how I can obtain this serial number and then use with the MG17System object to talk to the proper controller. Is it possible to operate two BBD202 controllers simultaneously that are connected on the same USB bus?
msoulby  (posted 2014-01-20 09:25:25.0)
Response from Mike at Thorlabs: Yes it is possible to use two controllers simultaneously on the same USB bus. The only way to address each individual channel is to use the HWSerialNum ActiveX property from the MG17Motor control. The correct serial number can be found above each channel on the rear panel of the BBD202 controller. Each controller will have the same hardware type but will have a unique set of serial numbers allowing each channel to be easily recognised; each channel will need its own instance of the MG17Motor.ocx control.
+1 数量 資料 型番 - ユニバーサル規格 定価(税抜) 出荷予定日
BBD201 Support Documentation
BBD2011軸-3相ブラシレスDCサーボコントローラ、ベンチトップ型
¥281,913
3-5 Days
BBD202 Support Documentation
BBD2022軸-3相ブラシレスDCサーボコントローラ、ベンチトップ型
¥425,684
Today
BBD203 Support Documentation
BBD2033軸-3相ブラシレスDCサーボコントローラ、ベンチトップ型
¥540,757
3-5 Days
MJC001 Support Documentation
MJC0012軸顕微鏡用ジョイスティックコンソール
¥142,786
Today
ログイン  |   マイアカウント  |   Contacts  |   個人情報保護方針  |   ホーム  |   FAQ  |   Site Index
Regional Websites:East Coast US | West Coast US | Europe | Asia | China
Copyright © 1999-2020 Thorlabs, Inc.
Sales: +81-3-6915-7701
Tech Supports: +81-3-6915-7701


High Quality Thorlabs Logo 1000px:Save this Image