It seems that a number of people are having the same problem with the Philips based BGB203 Bluetooth modules getting stuck in Data Mode forever, unable to enter Command Mode.
I used the Silver version and got them to work. Two things I was fighting with to make them work :
When I started I used the gold manual and it did not work. Until I found out the silver ones I have use other commands, e.g. +++ for silver and $$$ for gold to switch to command mode
I had very unstable start-ups when using 5V supply; 3V3 supply works great. Altough the description says it works on 3V3…6V or something like that
I’m another person who is having trouble with the Silver radios. I’m using the escape command “+++” without any luck. I have run the module on 3.3v and 5v. I have had one of sparkfun’s discontinued models work great in a previous project. I guess i’m posting this in hopes of a refund or seeing that sparkfun will discontinue these models. What good is it if I can’t change the baud rate?
Start up a HyperTerminal window, configured to the com port the ‘FDTI’ at 9600/8/N/1/none. Hook up your bluetooth module to it, the 4 basic pins VCC/TX/RX/GND, make sure the TX/RX are in the right order (swapped)
Start up another HyperTerminal window, this time connect to the bluetooth module in data mode using SPP com part, again 9600/8/N/1/none.
Typing keys on one terminal will appear on the other and vice versa. So that confirms everything works (Firmware exist!).
Now issue the escape sequence (+++) on the terminal connected to SPP com port. You should see the other terminal, connected to FDTI com port, going into ‘Command Mode’.
Type ATI, bluetooth module will return its firmware version.
Do as you wish as per the bluetooth AT command set.
I had trouble for a while (could never get into command mode), then it suddenly began to work. I never found out why, but since it “started working” the first time I used it on a different day I’m guessing I kept making the same mistake before, but after going away for a while and coming back to it, I had to start over and probably read the documentation properly that time
I am also having trouble with my bluesmirf gold. I have connected it to my oopic-r microcontroller. I am able to connect it via terminal program but the module is not responding.
Once powered, the red light starts flashing. When I connect to the outgoing serial port with terminal program the red led stops flashing and the green led turns on. However, when I type $$$ I get no reply.
I’ve tried with baud rate 9600 and 115200, data bits 8, stop bits 1, parity none, flow control none.
I would really appreciate if you could help with this. I really need to get this work!
detox:
I am also having trouble with my bluesmirf gold. I have connected it to my oopic-r microcontroller. I am able to connect it via terminal program but the module is not responding.
Once powered, the red light starts flashing. When I connect to the outgoing serial port with terminal program the red led stops flashing and the green led turns on. However, when I type $$$ I get no reply.
I’ve tried with baud rate 9600 and 115200, data bits 8, stop bits 1, parity none, flow control none.
I would really appreciate if you could help with this. I really need to get this work!
Ok, I managed to solve the problem. Simply by forcing line edit off from the terminal program settings. I don’t know why this did the trick but at least it’s working now.
I was having the same problem and in my case it turned out that the problem was the “+” key I was using. When I tried to get in command mode by typing three “+” characters I instinctively hit the “+” key at the far right of the keyboard, the one in the number pad. For some reason this key was not being interpreted as a “+” and so switching the the “+” above the “=” solved the problem in my case. I doubt this is the source of everyone’s problems but it might help somebody.
Am using WRL-08474 (BGB 203) module. Unable to enter command mode only trying for past many days. Shld i use 2 COM ports to enter command mode? Tell me in detail the interface used between the system and module to enter command mode… i need to configure baud rate to 36,400,timeout is 20sec should i first need to config the timeout? Can anyone help me in doing this.
I’ve used both the silver and gold versions. My personal experience:
For the Silver one, +++ goes into command mode; $$$ does not work. Also, you have to use the AT+ commands once you’re in command mode. Most of the AT+ commands are temporary, so you have to do AT+FLS to write the current settings into flash.
For the Gold one, $$$ works, and the “set” Sx, XXXX commands that write directly to flash in the manual seems to work fine. the AT+ commands don’t work with it.
The silver defaults to 9600, while the gold is 115200.
However, for both of these I had to connect them through a USB-Serial adapter. I can’t seem to get either of them into CMD mode through the bluetooth end, which is in theory possible.
RN-41 command mode may be entered any time thru the USART interface by sending “$$$”.
RN-41 command mode may be entered using bluetooth wireless, only for the first 60 seconds after power up by sending “$$$”. This is the default timeout.
Down load and read the Advanced User manual from Roving Networks for a full description of all commands.
The default baud on the RN-41 is 115K. Not sure if sparkfun changes the baud to 9600 before it ships the bluesmirf.
I have a bluesmirf gold dongle. I am using putty to connect to the device on windows 7. I was unable to enter command mode and tried various things posted on the forumn to no avail. Here is what worked for me:
When you power on the bluesmirf, the red light blinks rapidly. Then it slows down after a short time. If I connect using putty while the light is blinking faster and type $$$, then I can enter command mode. Once the light is blinking a little more slowly, I can no longer enter command mode. Hope that helps!
