I did read about that ability of the card to drive at 1/2 the value for channels 3, 4 & 5, but it would be a pain in the ass to move all those wires and everything around.

I think I'll just add a simple in-line resistor as you imply. So let's just look at X in my example below. I'll of course do the same after I test with X but for now I'll just focus on 1 driver to see if it gets me to the desired results.

The driver has 2 pins for the resolver a signal and a common for lack of better terms. I would think that I just want to put 1 resistor in line on the signal wire; a 470 Ohm as you suggest. But please correct me if I'm wrong.

When I was looking at my o-scope for the resolvers over the past 2 days. The SIN and COS signals were very fuzzy (noisy?) as opposed to the signal (driver) loop. So maybe that's also an indication of things being overdriven?

1. It should be easy to move the resolvers around since each resolver should be on a single 8 terminal plug
2. You will not be able to see the sine/cosine signals very well without a differential (common mode noise rejecting) scope input.

Yeah I thought about that after I replied ...just move the whole block of 8 pins. Should I also move the signal blocks back from P4 to P3 so that everything is lined up again?

Also I realized if I put a resistor in I would want it in parallel with the driver coil so that resistor would actually go across the 2 pins for the driver coil sharing some of the voltage the the driver originally got and thereby reducing the voltage making it to the driver coil. Is that what you really meant?

I'll see about moving my X resolver block over to the P3 row today and let you know how that affects things after I set that row to half power with the jumper.

Question for you guys on a different note. Is there a way to map keys (such as S) from the keyboard out to my gamepad? Right now I can jog and move my bed with my gamepad but when I have a PAUSE in my gcode I have to go to my keyboard to press S and it would be nice to map that to a button on the gamepad.

nevermind I found the issue
My num_resolvers=3 (at the top of the file) was the problem
When I set this up to 6 that solved the problem. Starting from 00 = 1, by the time you get to 05 that =6 resolvers

well I got rid of my error but I can't move my servos. The signals coming out of AOUT0 and AOUT1 are dead.

I'm trying to determine what parameter I need to change to fix this but I can't seem to find it in the .hal file. My suspicion is that it's PNCCONF or the SVRM6_48.PIN file in my firmware folder. At this point my issue seems to be something small, just misconfigured.