I have had to replace 4 SSC-32 boards in the past couple of months. The robot will communicate for one lab and then an hour later it won’t. Green data LED turns off but nothing happens.
The first time it happend, I actually removed both chips on the board and replaced them from a backup board that I had, and it fixed the problem.
For the last three, I have had to replace the board completely…for lack of replacement chips. I learned after the forst one and bought some backups.
Once the SSC-32 board is replaced, the arm works fine. Connectivity is restored.
Does anyone else seem to have this problem? or am I doing something wrong that I might be blowing the chips.
Does anyone know where I might be able to buy just the chips and which one might be dedicated to the communication problem?
I’ve followed this forum for many years and have an ssc-32. I’ve never seen a problem with an ssc-32 that didn’t lead back to something the end user had done.
Most likely, especially since you keep having repeated failures. You might want to get an electronic savy person to independently verify the design and wiring for your setup.
its just a simple Atmega168. You can even program these yourself with a firmware update. sorry to brake that to you.
or buy it pre-programmed…
lynxmotion.com/p-624-ssc-32- … -chip.aspx
Before you go and blow another one it might be worth posting an image of your wiring.