Don't ad-block us - support your favorite websites. We have safe, unobstrusive, robotics related ads that you actually want to see - see here for more.
0 Members and 1 Guest are viewing this topic.
A BlueSMiRF acts like a serial cable. Unless you're accessing the internal utilities, it won't respond (and those aren't that easy to get to). Try connecting the RX_I and TX_O pins together to make a loopback connection, and see if you can get any data. Also, try a variety of different baud rates: it's supposed to be 115.2kBaud, but it may have accidentally been changed.
If you can see what you type echoed back to you, your BlueSMiRF is working (this is a good thing.)If you don't have a device with hardware flow control attached to the BlueSMiRF, or you want to use software flow control, you need to bridge RTS and CTS (just solder a wire across). The inability to enter command mode is probably because of the flow control thing - fix that first. Worst case, it's still quite usable without the command mode (I have yet to use command mode for anything, since my uC can handle 115.2kBaud serial).
If there's no particular reason to use a lower baud rate, it's my personal preference to leave it at 115200 baud, since the actual serial part is handled in hardware, and doesn't make a significant increase to the CPU load. Higher speeds generally mean that the write/read calls block for shorter periods of time, and help with timing in general.