SSC-32 Broken

Lynxmotion Electronics & Software
1

Hi,
I am using the Phoenix V2.0 Hex, for a uni project.
I try to install some FSR on the tip of the legs, to keep the height of the chassis fixed even when moving over minor obstacles.
While I was connecting the FSR to the SCC-32 (making a curve in the end of each wire and power was ON as well ~ epic tard), I short-circuited VS2 pins 30, 31 etc (not all at once).
The robot reacted just like I stroke its nerve system and after a reboot, the servos never worked again. No instruction from the ps2 controller ever reached the hex.
~I am using a 7.5 v battery.
~Jumpers: BAUD for atom pro, VL=VS1, VS2=VS1(2 jumpers there)
~Readings: VL 7.5 (where battery is connected)
VS1 and VS2 1.4, but being ubstable most of the time, showing some mV
~LED: steady green and when TX, RX is connect, blinking.

Did I burn any trace on the scc-32, which I cannot see? Did I burn the regulator? What reading should I get from VS1 and VS2?

I don’t have much time left and the accident occured in the worst possible moment.

Looking forward to hearing from you.
Cloud

p.s. all servos are removed during those tests
regulator gives 5v output, so it looks fine

2

Even though there is perfect continuity with VL and VS1 and VS2 (multimeter beeped in every reading), for a strange reason, the voltage reading is not the same…
The reading currently dropped from 1.4 to an unspecific mv value…

3

Update:
The regulator had a 5V output, which was not going to vs1 jumper pin, therefore I soldered a wire to vs1.
As a result, I got 5v back on both vs1 and vs2.
Servos started working once again, but they are quite “drunk”. Not only that, but hexa doesn’t receive PS2 instructions anymore.

4

Really hard to tell what was fried. If only a few pins are not working, then try to use other pins on the SSC-32 and change the code accordingly.