As I am new on SSC-32 and have question about control SSC-32 via bluetooth. Can anybody tell how to do this? I have one A7-eb500, a EagleTec USB Bluetooth adapter and one SSC-32. Thks.
Ricky
I’m using this adapter with my notebook’s internal bluetooth. It works same way as serial cable, but there is not implemented DTR signal. You will need to provide power for adapter. It is possible to do by connecting 5V to pin 9 on the adapter connector.
Connection should work up to 100 meters, what is enough for every application I think 
That adapter is pretty slick. Far too expensive if you ask me though. Look here: sparkfun.com/commerce/present.php?p=Bluetooth%20Primer for how to implement a simple serial link using a Bluetooth modules from Sparkfun for less than half the cost. Basically the idea is the same for your module, CHPOL. You need a pinout. I actually had a difficult time finding this in the manual from Parallax (Not sure if you have the Appmod version of the eb500). But the pins should be similar to the Sparkfun module. Only power, ground, Rx, and Tx are needed for most applications.
EDIT: In case you do have the Parallax version, the manual is here: parallax.com/dl/docs/prod/comm/eb500UserManual.pdf The I/O stuff is on page 16-17. The module has the additional ability to let to stamp know if it has a connection or needs to get one, which might be useful.
Thks a lot, it is really help. I’ll study and post result later.
CHPOLA
Hello, Tillin9, I’m having same feeling now. I got both devies connected but can not talk each other. My eb500 is Appmod version. Do you mean that use Sparkfun instead of eb500 is better?
Thks,CHPOLA
Um… I don’t really understand. If they’re connected properly they should be able to talk just fine. Really you just need to debug your connections. I can recommended the Sparkfun module, since I have one and have followed the tutorial, hooking it up is very easy. I said it was cheaper than the F2M01 vili42 recommended, and I think it is better than most other modules I have seen since it is smaller and the documentation is very good.
However, since you already have the module, I don’t think you should get rid of it just yet. You should only need to find the Tx and Rx pins. If you happen to have access to an osciloscope you can just check the signal from every pin while having the computer send data. You do have the Bluetooth link correct and are sending data to the right COM port, etc.?
Finding the pin for the SC-32 to communicate to the computer is harder, I guess you could try it pinwise, but there is a slim chance you could damage something that way. Hopefully with the manual I linked (or other documents on Parallax’s site) you can find out where the other pin is using the first as reference. Parallax’s documentation is sometimes wrong, and sometimes tricky, since there are multiple board revisions and such. A trip to the Parallax forum might also be a good idea if you can’t figure it out yourself. They have a number of engineers (the people who wrote the stamp books) answering questions. Since I never used the Appmod, and they designed it, I’m sure they could be a lot more helpful.
Yes, I was mad with Parallax’s manual, sometime they will just delete the statements if we found they are wrong or not correct. Or sometime their instructions can not follow but anyway, I brought some of their parts. I have to fix it out.
Going back, I found on the remote devise’s com port only showing one. Is it should be two? one Tx and one Rx? Do we need to connect twice? One from PC and one from eb500? 
thks
CHPOLA
The PC should only show one COM port for the eb500. However, the total number of COMs shown depends on your machine. I was just saying to make sure the computer recognized the bluetooth serial port (i.e. gave it a COM number) and when you try to communicate, you direct information to that port. This is opposed to say COM1 which is generally the built-in one on the motherboard. On my module and machine (when under windows) the bluetooth port is COM8.
My best advice is to head over to the Parallax forum and bug them. At the very least they should be able to point you in the right direction.
Sorry, wish I could be more helpful.
Hello, my Wibot parts arrived and try to test my boards. I found the Wibot board layout is different with Breakout board that I can not find on Wibotics site. I got Witbot connected but no respond from SSC-32. I wonder the connection of TX and RX is wrong. Is it TX to TX and RX To RX or TX to RX and RX to TX?
Thks
CHPOLA
I looked at the sparkfun thing and it looks like you need to know a bit about electronics to set it up. The pictures look like its set up on an experimentors bread board…
I found these little plug and play things and was wondering why they wouldn’t work. They even have a version you can plug into your USB port…
gridconnect.com/bluetooth-rs232.html
Will these work with my SSC-32?
Hello, MYKL. I’m still working on the Wiport and they should work.
Thks
Ricky
PS. I’ll order a pair of Bluetooth/RS-232 to test.
It’s always TX to RX and RX to TX.
Think of what they mean: Transmit to Recieve and Recieve to Transmit.
TX is analagous to the microphone of a phone and RX, the phone’s speaker.
You speak into the microphone on one end and it comes out the speaker on the other guy’s end.
Thks Nick. I can connect SSC-32 via Wiport now and they move undercontrol.
bst rgds,
CHPOLA