I realize that there are some discussions about this issue. But, I haven’t found anything directly on point with this issue.
I recently received a new SSC-32 card. I do not have an available serial port. So, I don’t use the DB-9 connector. Instead, a USB-to-serial converter is in use (at COM8). The converter has been tested with other devices and functions fine. The SSC-32 manual doesn’t appear to say it, but the logic level (+5v) TTL serial pins on the SSC-32 board appear to be inverted logic. After I inverted the signal, I got the green SSC-32 led to blink. My understanding is that that means the Atmega 168 is 99% functional and receiving data (although perhaps not at the correct baud rate).
The problem is that regardless of what baud setting I select, I still get the “Can’t find SSC-32 card” error message. So, if it is blinking, am I close?
There is a DB-9 connector with RS-232 levels, an also a header with TTL levels. Your USB adapter probably has a DB-9 connector. so plug it in. There are other threads (even sticky!) on the USB cable and it’s use.
I tried the DB-9 port first (COM1 on my laptop and a commercial quality cable). However, I never got the SSC-32 to respond, just the steady green light. And, yes, I did test the laptop COM port in a closed loop with the USB-to-serial converter (a MAX232 used to bridge the logic levels) and they spoke to each other. I have ordered the USB converter you suggested (FTDI UC-232R-NE ChiPi) in your troubleshooting note, so we’ll see the result.
The question I have is, if the SSC-32 is blinking, does that mean that the logic levels are ok and it is just a baud issue. I should be really close, but Lynxterm can’t see the SSC-32 board…
If the LED is blinking I would think baud rate would be the only variable left. However, I only have experience sending TTL data via the Atom or Basic Stamp processors. I do not know anything about your USB / TTL adapter and if inverting the data is necessary.
One thing comes to mind here. The SSC-32 will not process any commands until it receives a carriage return. Are you sending it?
Hi, first sry for my English.
I have a problem with my SSC-32. Before was all good, but yesterday was my bad day
Status is:
when is power on LED stay on
when I click on Reg. button on LynxTerm I get message “Can’t find SSC-32 card” and LED shutdown and stay off
then, when I click to other buttons (all=1500 or All=0) LED blink once and stay off
when I write VER I get nothing and LED stay still off
when I click in Timeouts options on ‘VER’ Test button I get “Byte Read: 0” under the button and LED blink once and stay off
when I try write #0 P750 nothing happens and LED stay still off
when I try move with that thing on the right side Channel 00 (where I have the servo plugged in) nothing happens servo is still on the start position and LED blinking when I moving with that thing, other stay off
cable converter function good, I tried it with mini-ABB + BAP28 all function good
all works fine before
What configuration I have:
VS1=VS2, plugged 2 jumpers ||
VL=VS1, unplugged
new 9V battery connected on VL
Baund is on 115,2k, 2 jumpers ||
2 jumpers plugged on TX and RX ||
using HL-340 converter cable on COM9
Settings on LynxTerm:
Port COM9
Baud rate 115200
other settings are default at all
So what wrong with my SSC-32? Is it dead? What shall I do? Pls help me.
And I have some other question. When I bought ATMEGA chip from other manufacture some like this sos.sk/?str=371&artnum=51774, can I putt your firmware V2 to that chip? I will do this if the chip is dead, because you (Lynxmotion, Inc.) not send to Slovakia, and IF then will too much cost for me. But I need resolution if is board (or something on it) dead or chip ATMEGA. I hope is it only the chip and I will be able putt your firmware on new one. THX for all your post.
look like you have EXACTLY the same problem as me… by the way, have you bought your SSC-32 at Robotshop.ca? take a look at the “plz, help a noob ” topic… i tried serial and i still get the same problem… tried each baud configuration possible, same again… formated PC, same problem… tried Vista, XP… still not working…
i even tried on my friend computer who use a serial plotter, so the computer serial port work rightly and i’m not getting respond at all…
And what are you using to base this on? Two forum posts… If there was a bad batch of SSC-32’s the forum would be on fire… There is nothing wrong with the SSC-32’s.
I tried in 2PCs with wall adapter on 7,5V, and nothing changed. Baud rate and jumpers, is correct, because before I did same configuration and all works fine all pins works correct with my program. My problem start after when I tried phoenix1.3.bas code.
What I did:
connect PC with mini-ABB for load code phoenix1.3.bas.
switch on power for logic and servos, old program start and all legs moved with commands from BAP with my program.
in ATOM-Pro IDE 08.0.1.7 I changed this row in code for configuration mini-ABB
[code];[SERIAL CONNECTIONS]
SSC_LM_SETUP con 1 ;Changes the SSC pins corresponding to the setup
;1 = Setup with connector to the front
;0 = Setup with connector to the back
SSC_OUT con P15 ;Output pin for (SSC32 RX) on BotBoard (Yellow)
SSC_IN con P14 ;Input pin for (SSC32 TX) on BotBoard (Blue)
SSC_BAUTE con i38400 ;SSC32 Baute rate
;--------------------------------------------------------------------
;[PS2 Controller]
PS2DAT con P4 ;PS2 Controller DAT (Brown)
PS2CMD con P5 ;PS2 controller CMD (Orange)
PS2SEL con P6 ;PS2 Controller SEL (Blue)
PS2CLK con P7 ;PS2 Controller CLK (White)
PadMode con $79
;--------------------------------------------------------------------[/code]
other rows are same like phoenix1.3.bas.
then load program to BAP, all loaded right
after load I heard noise from mini-ABB and all servos goes to center positions (1500uS)
LED on SSC-32 blinked many times then shutdown and stay off
I turn on PS2 joystick, my receiver communicate with PS2 joystick and join to him.
I press button START on PS2, I heard noise specified for start robot but legs did notihing, LED on SSC-32 blink many times then shutdown and stay off
I press other buttons but only square button and select do something because I heard noise some like beep or something, but it is all what robot did work.
then I press START and shutdown all power, looked on the code if I miss something but all looks good som I tried all this again
but when I press square 3times in short time, all servos on 6 legs did something like when they have overpulse or something, after 3 seconds I shutdown all power.
after that SSC-32 started this things what he do today.
So I’m sure something on SSC-32 is damaged, or I don’t know, but all servos works right and BAP is OK I tried them with program for commanding servos.
Maybe all is right, maybe it is only bad dream, but if no, maybe I destroyed heart of my mini octopod
What can I do? Is there any test program or something what helps me for knowing what is going on? What is damage? This is my diploma project and I need full function of SSC-32 for demonstration.
THX for all yours posting.
I know that, so yes I had plugged bidirectional cable for this communications.
I can post an image of my wiring it is not possible now because when I saw that, but maybe I replug all connectors and make pictures, but it’s only beta version of my project so either permissive
I’m going to ask you to use a little more punctuation in your posts. I’m not at all sure what you are trying to say here. Please post an image of your wiring.
Using lynxterm with the ssc-32 connected to a serial port, send the “ver” command to the ssc-32 and see if you get a response. If this works, connect a single servo to the ssc-32 and see if you can get it to move. Make sure the ssc-32 and lynxterm are using the same baud setting.
zoomkat: when I try send a ver command nothing happen only LED blink once. Of course lynxterm and SSC32 have same baud setting 115,2k. When I click in Timeouts options on ‘VER’ Test button I get “Byte Read: 0” under the button and LED blink once and stay off. When I click on Reg. button on LynxTerm I get message “Can’t find SSC-32 card” this is strange, before this was not happened. There is the point, something is wrong with SSC-32 because all works right before. (before what I tried that phoenix code, what I wrote upper.) Before I used that same miniABB and SSC-32 with my program and all works fine, but then as I tried to Phoenix code, something go wrong with the SSC-32. I’m sure I made a mistake somewhere just don’t know where.
Can the SSC go wrong, after the user do some mistake? Heh I know my English is so bad Realy sry
Do you remember what you have done to the board since it worked OK? The board probably could be damaged, but more likely something like a jumper incorrectly set or a lose connection. Have you disconnected or reconnected anything?
zoomkat: when the board “worked” with phoenix code I didn’t touch anything, only when that 6 legs did some like overpulse or what, I switched off all power. That is all. I never touch robot if is it on the power. I don’t understand what happened it is strange and bad for me . Maybe it’s here only one option, buy new SSC-32 . Oh dear, my consultant of diploma project killing me . But how I explain that?
You say you have the boards connected as in the image. If you are trying to send commands to the SSC-32 with it’s DB9 connection are you pulling the wires off the connector by the DB9 and replacing the jumpers? Please submit a real photo of your wiring. A drawing is nice, but it’s not the same.
The two jumpers by the DB9 connector must be in place to enable RS232 communication on the DB9 connector. When connecting to a PC these jumpers need to be in place. They need to be oriented vertical (when you can read SSC-32.)
The two jumpers by the DB9 connector must be removed to allow TTL communication from the Bot Board II. When this is done the SSC-32 will no longer receive data from the DB9.
Again, an actual picture would be helpful. Your post states you are communicating at 115200 - yet your picture shows the jumpers on the SSC-32 set for 38400. I noticed this because I just made a similar mistake!
Robot Dude: That image shows the connects what I had when the SSC-32 was “damage”, no when I tried to connect to PC. I thought you need that picture
For all: Now when I again tried to configured connections and jumpers again for connect to PC, I did some miracle because all works right, all is OK. Maybe I did same mistake over and over with some jumpers or I don’t know but it works for now, I don’t believe it but all is OK so thx everybody.
Robot Dude: you are the best of the best THX for your help, patience and your time.
Zoomkat: you are also best and thx for your time also.
I was believed it is only bad dream and it was THX for all.
” topic… i tried serial and i still get the same problem… tried each baud configuration possible, same again… formated PC, same problem… tried Vista, XP… still not working…
