Hello all. I have the WRL-00158 Bluesmirf modem with ver 4.77 firmware with the duck antenna and the SSC-32 servo controler. When I use Lynxterm I can enter the command mode with “$$$” and check out the settings but when I try “VER” and press enter nothing happens. I can plug in with my Trendnet TU-S9 usb to serial cable and I can communicate with the SSC-32 just fine and can even connect via Python and run a program I made to control the robot. When I try the slider bar in Lynxterm nothing happens as well. I have tried messing with time out values, incrementing “Read Interval” by 100 and also “Read total constant” by values of 100. I get 0 bytes back every time. I even tried using Baudrate 9600. Again I can get to command mode but “VER” doesn’t work. I changed BDrate back to 115K by typing “SU,11” in command mode. And I set jumpers correctly on SSC-32 when trying the 2 diff BDrates.
I have searched the forums and net for days and have tried on a fresh battery and even tried enabling something in the Bluesmirf to improve latency issue. I’m stumped. Can I get some help.
I don’t know if this will help. I use the same Blue Smirf modem, but I never set the buadrate with the modem interface. If I recall correctly, I’m running at 115K. I’m talking to a PIC18F4620 and not an SSC-32, but that shouldn’t matter. No handshake lines connected. There is a setup for baud rate in the windoz XP driver under USB, of course.
I checked the Baudrate in “Device Manager” on the XP laptop I’m testing it on. The COM port the Bluetooth is attached to was set to 9600. I set it to 115200 but can still only get to command mode, “VER” test in Lynxterm still yields no results.
I do not have a bluetooth setup so anything I say should be taken with a grain of salt!
But questions do come to mind.
When you try to communicate with the SSC-32, does the LED on the SSC-32 blink at all. If it does, it says that it is receiving something. May be garbage, may be wrong baud… But it is receiving something…
If not recieving anything have you tried to swap RX/TX wires? Sometimes I find that different devices label things like this differently. On some TX implies this is the TX from the device and others it is connect me to the TX of the target… Also make sure you have a ground pin
When you enter the $$$ command are you talking to your local BT device or the remote BT device? Again not much experience with BT. But with XBEE using +++ to get into command mode is for the local XBEE…
Edit: 4) I meant to ask also after you changed baud rates in the device manager or the like, did you go back to the terminal program, disconnect the serial port, change the baud rate in the setting and reconnect? That is usually how I have the best luck.
SOLVED OMG it was the RX and TX wires, they needed to be switched. And after closer examination it was not the MFG mislabeling but my own noobness. This is my first time trying a robot project like this, I should have relized TX --> RX and RX --> TX.
Now I can communicated with the robot and even control it using Python, via WIRELESS. Thanks a lot guys, It was changing Baudrate on laptop COM port after installing bluetooth dongle and kurte’s suggestion of checking the wires. I really appreciate it. Now I can start my robotic army MUHAHAHAHA…
Here is a website I made for the bot, more pics and directions, will update it this week on installing the BlueSmirf and my “troubleshooting” issues.
Thanks again.
OMG it was the RX and TX wires, they needed to be switched. And after closer examination it was not the MFG mislabeling but my own noobness. This is my first time trying a robot project like this, I should have relized TX --> RX and RX --> TX.