img115.imageshack.us/img115/2525/49549268.jpg
I tried updating the SSC-32 firmware from 2.01XE to the latest 2.03XE through Lynxterm and encountered the above error message. I didnt proceed with the Jumper method to update. Commands like ver, servo move, query etc all are working perfectly,so the serial connection wont be the problem.
Any thoughts,why lynxterm is prompting this error?
Thanks
Make sure the SSC-32 is running at the correct speed of 115200 (ie both baud rate jumpers are in).
I ran into this recently as well! I tried the hardware method it mentioned and it did not work for me. Once I got my SSC-32 set for the high baud rate mine worked fine.
Kurt
I am connected through Bluesmirf at 9600 baud rate,which never connected me at 115.2K even i followed the bluesmirf tutorial many a times.so if i change the baud rate to 115.2k at this time,i may get connected in the lynxterm but it would never return any result to ver command!
Its another issue which i wanted to seek assistance for,and now it seems it should be resolved first or the firmware update would never work for me,since i dont have a serial port to make a direct cable connection.
Any thoughts on why blusmirf not connecting at 115.2?actually,as mentioned in the tutorial,when i issue “+++” command,it doesnt return me any result,same as the case with the AT and the rest of the commands. I.e i am never successfull in entering the configuration mode as explained by the tutorial.however,everything works perfectly at 9600 baud rate.all the commands work fine.
I really appreciate ur cooperation in this regard.
Thanks alot
Yes the firmware update requires high speed bidirectional communication. If you have the baud rate set lower it will not work. Also all of the serial port / USB to serial drivers need to be optimized as in the troubleshooting guide for this to work. In other words if you have a problem with your serial port speed this is where you will notice it.
lynxmotion.net/viewtopic.php?t=4702
We are adding this information to the SSC-32 users manual.
Thanks everyone,
I made the direct serial connection with SSC-32 at 115.2k baud rate and attempted to do firmware upgrade. Success!
Everything worked perfect.
Thanks for all the cooperation.
Regards,
umar
Hello, I have problems with my ssc-32, I can not have communication with the board, the LED is not lit and I can never read the soft version, or update the firmware, I can do?
I use a usb converter to serial port can be for this?
thanks, greetings
Forget about all the other things. You need to make the green LED light up. Remove all servos, cables, etc and apply the 9vdc battery. We need to get the LED to light up.
I only have connected the serial port and 9V, and will not turn green LED ever. I tested on a PC with a serial and will not. I think I have the ATMEGA168 erased, or broken. How can I fix it? I can burn again?
I’m answering your email…
ok,
Is this normal? is the screen that I get. Sorry about the level of English.
Did the ssc-32 origionally work? In the past there have been others that tried to reflash the ssc-32 chip because of other issues that had nothing to do with the ssc-32 chip. Did you attempt to reflash your chip? Below is a post of an uneeded reflash attempt.
Hello, I have not attempted a reflash but not if being anecesario because there is no way to go.
