Hi everyone. Finally got my RB-Dfr-95 today and started setting it up.
Sometimes Windows won’t see the bluetooth device, but after a few reboots I can get it to pair.
I’m only able to communicate via the bluetooth bee with the SSC-32U at 9600 baud, which is a bit slow for our purposes.
I am not able to figure out how to get into AT mode to change the baud.
]Does the SSC-32U need to have the same baud rate as the bluetooth bee (I assume yes because this is the only way I could get communication with the SSC-32U to work via the bluetooth bee)./:m]
]If I set the SSC-32U to 38400 (the baud at which AT mode is supposed to be available on the bluetooth bee) and put the bluetooth bee in AT mode via the switch then I am unable to connect to the bluetooth bee via the “Standard Serial over Bluetooth link” / virtual serial port. I am unable to connect to the SSC-32U via the USB serial port either. Lynx term connects, but is slow to type in to and sending over an “AT” command shows no response./:m]
]When I connect the bluetooth bee to Windows I get 4 different “Standard Serial over Bluetooth link (COMXX)” entries, each on a subsequent com port (11-14). Not sure why that happens, but it makes identifying the actual port a bit difficult. I have tried all ports to send AT commands./:m]
So, I’m reaching out because I’m stuck. I can control the servos attached to the SSC-32U at 9600 baud, but really need faster. I’d also like to actually have control over setting the name of the bluetooth bee as well as the pairing code. So… how do I get into AT mode correctly? Does the SSC-32U need to be the same baud as the bluetooth bee? Do I need to connect via bluetooth or via USB to get in to AT mode?
Thanks!
Hey,
Here are a few details that may help you:
-
You can find the manual of this device on its product page under Useful Links. It includes many details about its use. Here is a direct link to the manual.
-
Please note that you cannot use the AT mode in wireless communication. This requires physical connection to the module.
-
The way the SSC-32U is wired allows for use of a Bee module, but not to configure one (cannot be used to configure the Bee module using AT commands).
To best configure your Bee modules, you should use an adapter made for this purpose, such as: RB-Dfr-148, RB-Plx-217, RB-Spa-145, RB-Elf-108, etc.
Sincerely,
P.-S.: You may also want to check the module’s manufacturer wiki for more details. You can find it here.
Thanks, Sebastien. One unanswered question in that mix:
Do i need to have the SSC-32U set to the same baud rate as the bluetooth bee?
The DFRobot manuals don’t seem to cover that as it is an SSC-32U specific question.
Ah, so sorry I completely missed that one! 
Yes, the SSC-32U and the Bluetooth Bee needs to have the same baud rate for communication to work.
You can change the baud rate of the SSC-32U using the button (easiest, see manual page 34) or using serial commands (by modifying register 4, also on the same page).
Sincerely,
No worries, quite a few q’s in there. Makes sense for the same baud rate. Got this working this morning with an arm and rover, but wow is 9600 baud slow 
Thanks again for all the help, I might do a post on the full setup so that others don’t need to bug you so much 
Cheers!
All good then!
As a reference, the hexapod example code (Phoenix from the Lynxmotion Github) uses a baud rate of 38400 to control 18 servos, so that would prob. be enough for your purposes too.
I am sure more examples on how to do this setup would be very helpful to the RobotShop community! You could post about it here.
Sincerely,
Yeah we’re doing 115200 over the USB port to control the arms. Might try as little as 38400, but I like the responsiveness of the arm at 115200. Wish the SSC-32U could handle higher even
Yeah, I see what you mean. Unfortunately, the hardware interface of the AVR chip on that board does not handle anything faster (at least not reliably), so that would not be a trivial change (i.e.: changing chip!).
