It says these modules have password 1234 … which is fine, but what about BT identifiers? Do they all come with unique IDs like ether MACs? or can the id’s be programmed?
Everyone gets their own mac address. I will do some tests but I am pretty sure they will just show up as different com ports and thus, eclipse or processing would simply run multiple serial lines. --one for each unit.
you typically can’t reprogram a bluetooth MAC address, but they should be different. on the other hand you can likely change the module name which shows up during a search, but that feature is module dependent.
I’ve found the bare Bluetooth modules are difficult to solder even with a microscope and surface mount soldering station, I really don’t like the half via pins they use. The four dollar premium for the presoldered breakout board is worth every penny to me.
in windows each bluetooth device with serial port profile will have a unique COM port associated with it. You can discover it by right clicking the bluetooth icon in the windows tray and clicking Show Bluetooth Devices, then right click the bluetooth device and click properties. Then by viewing the different tabs of the properties window it will show a COM port for the Bluetooth services offered for that device. Helpful when you have a swarm and you need to determine which device is communicating on which COM port.
By the fact that Windows (or other OS) understands them as seperate devices was the part I was concerned about. When I get the pieces together, I suspect that MRL will ask each uC who it is. That way regardless of how the OS identifies the BT/Com devices, MRL will identify with the uC’s response and bind them with the appropriate SerialService during runtime.
In the past I have seen com ports register differently depending on bootup, and many other variables.
But having the uC respond (as long as there IS a connection) would allow identification of the each uC consistently…
Good for when the bots have slightly different capabilities, e.g. IR sensor on bot #1 vs WiiDAR on bot #2 vs Servo gripper on bot #3…
The distributer did not dicern the difference between “host” and “passive” modules when I purchased them. I ordered 6 and they randomly sent me 5 host modules and 1 passive. Now, I see that they make the distinction and are selling them seperately. Grrr… the passive ones are more useful for me… I’ll be ordering more passive units…
the name of the passive controller turned to “?” when I got distracted with other things and fire’d this up again
they are definately implementing a small subset of AT+ commands - so programming is hit or miss
and this one drove me (more) crazy !!! They implemented some of the AT+ commands without = … So, that AT+NAME=BLAH will give it a name of “=BLAH” Grrr… anyway it took a while to figure that one out… not sure which commands they have accessable… I can verify that you CAN change the name if send AT+NAMEBLAH to BLAH
I can also verify that I have successfully connected from a rocketfish bt dongle from my computer to the passive unit at 9600.
Tomorrow I’ll try to change baud rate to something more exciting…
Absolutely no luck regarding changing the baud rate…
Here’s some of the documentation I’ve found (so far this is the best)
Enter to AT mode: Way1: Supply power to module and input high level to PIN34 at the same time, the module will enter to AT mode with the baud rate-38400. Way2: In the first step, supply power to module; In the second step, input high level to PIN34. Then the module will enter to AT mode with the baud rate-9600. Way1 is recommended.
Uh… is way2 way1 …?!? uh… say again? … wish my kanji was better