Forum >Bluetooth Adapter Mini/addressing multiple devices
Bluetooth Adapter Mini/addressing multiple devices
dm 2012-02-12 02:54:20 8723 Views4 Replies Any help is appreciated, I have a lot of questions all relating to the same problem.
I’m working with two Rover 5 Tank kits ([url=http://www.dfrobot.com/index.php?route=product/product&filter_name=ROB0059&product_id=410]http://www.dfrobot.com/index.php?route=product/product&filter_name=ROB0059&product_id=410[/url])
The goal is to control 2 robots from the same machine via Bluetooth. While it works with single robot, when I try to control two robots it doesn’t work:
• Neither of 2 robots moves
• Link state (as according to LED on DFRobot Bluetooth V3) on one of robots is “not connected”
• Every time I try to connect two dongles (Bluetooth Adapter Mini) Windows (7) detects new devices and installs drivers, then if try to connect only single dongle Windows again detects new devices and reinstalls all drivers. But then nothing works.
At [url=http://www.dfrobot.com/index.php?route=product/product&product_id=288]http://www.dfrobot.com/index.php?route=product/product&product_id=288[/url] I see comment that many dongles have the same address and cannot work with the same PC. Is it the problem?
Then who can suggest the right way to manage a few devices via Bluetooth with single PC? If this is the problem of Bluetooth Adapter Mini, can I use usual USB Bluetooth dongles?
Is it possible to address a few [DFRobot Bluetooth V3] devices from the same USB Bluetooth dongle or should I install a few dongles and connect each one to only single [DFRobot Bluetooth V3]?
Also there is paring code 1234 by default. Should I change it for one of devices to address them separately?
Thanks
I’m working with two Rover 5 Tank kits ([url=http://www.dfrobot.com/index.php?route=product/product&filter_name=ROB0059&product_id=410]http://www.dfrobot.com/index.php?route=product/product&filter_name=ROB0059&product_id=410[/url])
The goal is to control 2 robots from the same machine via Bluetooth. While it works with single robot, when I try to control two robots it doesn’t work:
• Neither of 2 robots moves
• Link state (as according to LED on DFRobot Bluetooth V3) on one of robots is “not connected”
• Every time I try to connect two dongles (Bluetooth Adapter Mini) Windows (7) detects new devices and installs drivers, then if try to connect only single dongle Windows again detects new devices and reinstalls all drivers. But then nothing works.
At [url=http://www.dfrobot.com/index.php?route=product/product&product_id=288]http://www.dfrobot.com/index.php?route=product/product&product_id=288[/url] I see comment that many dongles have the same address and cannot work with the same PC. Is it the problem?
Then who can suggest the right way to manage a few devices via Bluetooth with single PC? If this is the problem of Bluetooth Adapter Mini, can I use usual USB Bluetooth dongles?
Is it possible to address a few [DFRobot Bluetooth V3] devices from the same USB Bluetooth dongle or should I install a few dongles and connect each one to only single [DFRobot Bluetooth V3]?
Also there is paring code 1234 by default. Should I change it for one of devices to address them separately?
Thanks
2012-02-14 19:51:53 Yep. Our bluetooth module can only do peer to peer communication at this moment. 
R2D2C3PO
R2D2C3PO 2012-02-13 22:42:56 [quote="Lauren"]
Hello,
If you could drive both of Bluetooth module with signal dongle, I think now you just need to make a simple protocol to control two robots.
exp:
!AF -> robot A move forward
!BF -> robot B move forward
note:
! -> header byte
A -> address byte
F -> command byte
Like the commands above , when the two robot receive all the commands from the dongle, they could figure out whether the command is valid according to the byte after the header byte.
:)
[/quote]
Thanks Lauren. Actually this is exactly one of options I was thinking of. But the problem appears to be simpler. When single dongle connects to multiple Bluetooth modules, Windows (in my case) creates one virtual COM-port (really 2, in and out) per Bluetooth module. You can just work with ports, no broadcast. dm
Hello,
If you could drive both of Bluetooth module with signal dongle, I think now you just need to make a simple protocol to control two robots.
exp:
!AF -> robot A move forward
!BF -> robot B move forward
note:
! -> header byte
A -> address byte
F -> command byte
Like the commands above , when the two robot receive all the commands from the dongle, they could figure out whether the command is valid according to the byte after the header byte.
:)
[/quote]
Thanks Lauren. Actually this is exactly one of options I was thinking of. But the problem appears to be simpler. When single dongle connects to multiple Bluetooth modules, Windows (in my case) creates one virtual COM-port (really 2, in and out) per Bluetooth module. You can just work with ports, no broadcast.
dm 2012-02-13 18:36:31 Hello,
If you could drive both of Bluetooth module with signal dongle, I think now you just need to make a simple protocol to control two robots.
exp:
!AF -> robot A move forward
!BF -> robot B move forward
note:
! -> header byte
A -> address byte
F -> command byte
Like the commands above , when the two robot receive all the commands from the dongle, they could figure out whether the command is valid according to the byte after the header byte.
:) Lauren
If you could drive both of Bluetooth module with signal dongle, I think now you just need to make a simple protocol to control two robots.
exp:
!AF -> robot A move forward
!BF -> robot B move forward
note:
! -> header byte
A -> address byte
F -> command byte
Like the commands above , when the two robot receive all the commands from the dongle, they could figure out whether the command is valid according to the byte after the header byte.
:)
Lauren 2012-02-12 09:30:07 Current results. Use single dongle for all [DFRobot Bluetooth] chips. The same paring code for many devices seems to be ok. dm
dm 