my ssc-32 wont update the firmware for the amtel 168. the current firmware is blank. my amtel 168 came out of my ssc and now that its back in, it wont move any of the servos.
Can someone please help?
So how did all that happen? 
Did you insert the IC in the wrong way? Make sure the two arcs line up.
Edit: I didn’t think about that, but kurte might be right about the Baud Rate. The SSC-32 needs to be set to 115.2k (When both jumpers are on) for Firmware updates.
Also make sure all of the pins went into the socket. Sometimes you can bend over a pin when you are trying to insert an IC. Likewise make sure it is seated well in the socket.
I am like zoomkat and wondering what happened. Also did your SSC-32 work properly before the processor was removed? i.e. are you sure it is the processor? What is it hooked up to now? Are proper commands being sent to it? Is the correct baud rate jumpers in? Do you have proper power going to it?
Kurt
Please pick a place to work on this… 
You have multiple posts and you’re sending me PM’s. It’s quite impossible to track what you have done and what are the results of what I have told you to try.
What is powering VL?
What is powering VS?
What are the jumper settings?
Does the green LED light up?
You do realize that only one program that uses the serial port can be open at a time right… Close all programs and open only the LynxTerm program.
Until you have the basic communications back please stop trying to change the firmware…
How did the amtel 168 “come out” of the ssc-32? Mine is in very tight and takes a lot of effort to remove it from the socket. If you are trying to flash your own amtel 168 using an update, I don’t think that will work.
Why would anyone want to flash there own atmega 168? whats wrong with the one that came with the SSC?
BTW, its an ATMEGA, not an AMTEL.
hmm, actually ATmega is a product line manufactured by Atmel. 
oh and uh kattdatty911 if you removed the ATmega168 from your SSC-32, erased it and then tried to program it with a device programmer then you shall have no pie as you have more than likely erased the bootloader, which is how you upgrade the firmware with the lynxmotion applications like lynxterm.
lynxmotion.com/Product.aspx?productID=624&CategoryID=52 will get you back to zero where you can resume fixing your communication issue.
my atmega 168 didnt come out by its self i actually took it out to see what it was( yea i know, stupid move on my part.lol) but when it popped out i forgot which direction it was in so i looked at the online picture of the product, then put it back in. i am pretty positive i put it in the right way. when i turned the ssc back on, the green light did come on and it appeared as if everything was working properly, but when i went on lynxterm to move one of the servos with the scroll bar, it wouldnt move. the light on the ssc still is on and seems to be fine. my servos also seem to work fine on a pulsout command straight from my bs2.
for my servo voltage i have 4 new"AAA" batteries
for logic voltage i have one new 9-volt battery.
my ssc-32 was working fine before the chip came out.
i dont know what flashing or bootloading is so im sure thats not the problem. i am very new to all this so i really appreciate all your comments. Robotdude i will now stay in this topic. oh, and wut do you mean by jumper settings. i will try everyone’s ideas and get back to you guys.
Thanx :slight_smile:if you’ve tried it from the bs2, you must of changed the baud rate. What ever your baud rate is set too, click the “SETUP” button in the Lynxterm, and change the baud rate in there to whatever it is on the SSC-32.
Also, a picture might help.
Oh, and the jumpers are the little black parts that are on the pins on the SSC-32.
Ok great. The atmel chip has a half circle on one end and a small dot in the corner. Put that small dot where the SSC-32 board shows pin1 and an arrow.
Here’s the kinda guy I am. I took the chip out of my test board, installed it backwards, and powered it up for grins. The chip got warm and the regulator got hot! And only after about 30 seconds! I pulled it out and reinstalled it correctly and the regulator provided me with 4.99vdc and the green LED lit up. So the robot hardware gods may be shining on you today.
Jumpers are what are used to enable the DB9 serial port, the baud rate, and powering options. Which begs the question. Do you have the DB9 enable jumpers installed. These are where you would connect the TTL coms for using a Bot Board to send commands instead of the PC. One last thing, all of the jumpers are oriented vertical on the board when you can read SSC-32…
Here, I edited a picture from LM to show you what everyone’s talking about :
Yes, that could definitely cause some problems.
This is why I said it would be nice to see a picture of your connections. It would be SO much easier to spot the problems.
ive set up the board exactly like the pic, with the exception of the #5 jumper removed. now how do i know what baud rate i need to set it on?
With both jumpers connected where is says “BAUD”, Your baud rate will be 115.2k (which is what you want). Look at the picture, and you’ll see how to connect them.
As for Lynxterm, to set the Baud rate:
http://www.majhost.com/gallery/DarthToa/Computers/lynxterm.png
thanks everybody for all your help i moved my serial cable to the back of my computer and it seems to be working fine now. i dont know how, seeing as my bs2 used the same port and was able to be programmed…???
thanks everybody 
PS; can someone show me what jumpers must be moved in order to have my bs2 give my ssc commands? what baudrate must it be on?