I have the bluesmirf bluesoleil and I have it connected and it shows green light for connected, when I go into the SSC32 terminal I have setup everything as instructed but when you are to type “ver” it shows and does nothing. As you type the green light flickers on the ssc board as if its recieving input but yet I can get no response in the DOS screen for information. Everything is set juat light the online instructions say so I need some help. Thanks
Hi Roboticwolf,
The green blinking LED on the SSC tells that it does receive data. So your Bluetooth connection seems to be right. I think that the baud rate isn’t configured right. Be sure that the are correctly set on both PC and SSC side.
I also remember something about increasing a timeout value in the terminal but I suggest to try the baud rate first 
Xan
Ah yes, the Timeout Module. It’s chapter 5 in the Sequencer Manual…
lynxmotion.com/images/data/seq01h.pdf
Here is something I found strange just to try it before you all replied I changed the Baud rate on the SSC 32 to 115.2 and went into the visual seq ver1.16 and it was centering servos and running the robot why do you think this is possible if before I couldnt even get the ver to come up in the other program? Sorry I have to ask dumb questions but I suppose thats how you learn.
I’m not sure what you’re trying to say. You need to have the correct baud rate in SEQ and LynxTerm. What baud rate was LynxTerm set up for?
Correct me if i’m wrong but I think Roboticwolf is trying to say that he was able to control the servos but the ver command isn’t working. Controlling the servos only needs a one way communication. You just need to tell the servo (SSC) where to go. The ver command needs bidirectional communication. You need to send the request (ver) and wait for the answer (version number). I guess that’s where the timeout comes in Did you try to get the version number by using hyperterminal?
Xan
Oh, right you are! Good catch! If you use the instructions in the SEQ manual concerning timeouts, but with LynxTerm and the VER command it should solve your problem. then you should be able to put those timeout values in any program we offer.
what I’m saying is the program I have on CD the one you install is the one that accepts all functions with centering the bot and everything, its the downloaded program the LYNXterm one where you do the settings and all with baud beong set to 9600 and then configuring settings and then going and typing “ver” then doing the “AT” and such this is the program that wont let me retrive “VER” or move any servos, I think I described it right.
Nevermind I gues I have gotton everything set up and starting to program sequences so I guess as long as everything is running ok i’m gonna call it good.
It would be helpful if you could quote the exact tutorial you are following and the step number, image, figure, etc. you are having trouble with. All of our program use the same library for serial coms. LynxTerm is one of the simpler programs. You really need to adjust the timeouts so you can get the version back from the SSC-32. Needing to adjust the timeouts is pretty common with USB to serial cables. Because LynxTerm doesn’t have a manual I recommended you look at the manual for SEQ as the timeouts module is the same in both programs.
Im not using the serial cable Im using the wireless bluetooth does this make a diffrenece?
That’s pretty much the same deal as the serial to USB cable, you’ve got to get the timeout settings right before it’ll work. Try increasing “Read Total Constant” to somewhere around 100, and see if that works. I just used the trial and error method when I got my BlueSMiRF to work.
Looking back on a tutorial I wrote, it seems that I used these settings:
Yes, sorry it’s early here… 
I meant blue tooth modem. Both USB to serial cables and bluetooth modems often need timeouts adjusted for reliable operation.
I read chapter 5 for the timeouts can someone clarify a little more about it I dont understand it to much of what to do. I did try one setting the read interval, I changed from 20 to 30 thats about it what else can I try?
I don’t know if you saw, but I edited my post that’s up a few. Try using those settings.
I took a pic of what I took a Picture of my desktop of what I got with the setting you suggested how do i paste the pic like you did?[/code]
I hope this works this is the results I got is this a good thing?
http://i486.photobucket.com/albums/rr228/roboticwolf/destop.jpg
I looked at the image. It looks like you are able to get the version back from the SSC-32 when using the text field in LynxTerm. That’s a good thing.
I’m not sure why you aren’t getting the VER test button to work. Is that the case? If so, please go back and hit default. Then click on the VER test button. If there are missing bytes try to increase the “Read Interval” value. If it doesn’t help try to increase a little the “Read Total Multiplier” then “Read Total Constant”.
The goal is to have the “SSC32-V2.01XE” apear in the window when you click the VER test.
Hello all,
using “VER” in the terminal window does not use timeouts values.
it sends “VER” + the return character to the SSC-32
then it doesn’t “wait” anything from the SSC-32 but it’s listening
incoming characters as they arrive from the SSC-32 and display them, even if then VER string is coming in 5 minutes.
the “VER” function in the timeout form is testing for real if the communication is fast enough to handle the flow and is using a timeout value not to lock the program for a too long time.
we need a timeout for many reasons,
When RIOS or SEQ is starting it must know which firmware (and which SSC-32 chip version) is connected.
When starting a form with servo position display, it wust ask the SSC-32 servo position “Q” command.
as it can’t go further while waiting these informations a timeout must break the wait loop if there no answer from the SSC-32
the timeout is used too to know when the SSC-32 has finished to send an unknow lengh data string else it will wait hypothetical characters indefinitely
with slow communication hardware :
as the only character you received is the first one, it mean the read interval is too low
try :
read interval : 100
read total constant : 100
read total multiplier : 0
if it’s not working try to increase the read interval by 100 steps
don’t go more than 1000