I suspect NeoWidEx will not tell us very much at this stage --- the servo is probably not reporting that it's in good health, which means that the controller won't be ready to talk to the Lisa or to NeoWidEx. But it might be worth a try.
Here is the haystack where we will need to look for our first needle: the servo schematics.
Let me know if anything obvious leaps out at you
What we need first of all is an understanding about how the servo works on the hardware level --- something I don't have at the moment. A careful study of the schematics would probably produce this, given enough time --- another thing I don't have a lot of right now.
There is plenty of stuff here that can go wrong. All kinds of analog circuitry that helps the servo know where it is and how much it's moving. For a traditional troubleshooting strategy, we'd take steps like these:
- Understand better how it all works, maybe dividing the circuit up into separate sections that have different functions.
- Come up with theories for how malfunctions in these sections could affect the servo.
- Identify theories that match the bang-bang behaviour you're seeing.
- Come up with ways to detect through measurement which of the theories is actually responsible for the behaviour.
- Applying these methods, identify the component whose malfunction is actually causing the problem.
- Replace or repair that component and hope it fixes things.
For an example of what I mean in option 4: we could suppose that the problem is coming from (a) part of the mechanism that measures the head location or (b) part of the mechanism that controls the motor that moves the head. To distinguish between the two, we'd want to show that measurements of the signals made by the head location system are correct/faulty and show that measurements of the control signals/voice coil actuation are faulty/correct. (In reality, we probably want to divide the servo system into more granular functional components.)
All of this is to say that we have a tricky troubleshooting problem on our hands --- and we also haven't completely determined that the problem rests in the servo board --- it could be somewhere else!
It would probably be a good idea to get started learning how to use your oscilloscope. Do you have any convenient way of practicing this skill --- maybe probing around a battery-powered radio or an Arduino-driven circuit or something like that?
How are you with understanding schematics and electronic circuits? (I would rate my abilities as "amateur" at best!)