This is going to seem a bit rambling, so I apologize in advance
I've been playing around with STK (taking advantage of the 30 day trial of the Astrogator module), and after a week, finally got a Corrective Combination burn. I'm going to try to do the same thing with GMAT, which has the advantage of being free (I'm afraid to ask what Astrogator costs
) but the disadvantage of being largely undocumented, AFAIK. I'm hoping my knowledge of STK can transfer over...
A couple of things I've noticed--when inputting the state vector from Orbiter, I had to transpose the Y and Z values for both position and velocity to get the proper orbit. This may be tied in to something I found when STK actually calculated the burn, which I'll go into in a moment.
Also, I found if I use the historic value of -5.7 fps for the phasing maneuver, I'm way too far ahead of the SIVB, which would require a significantly bigger burn to put the CSM in the correct position for CSI. One of the wiki's mentioned that a -2.5 fps burn puts you in the correct position, so I used that, and it worked very well.
After running Astrogator, I got delta V's close to the historic values--about 6 fps off in X, 2 fps in Z, and within .5 fps in Y, but the signs are reversed for the Y and Z values. My guess is that it has something to do with transposing the values from the state vector. It's almost as if the two coordinate systems are mirror images of each other about the X axis. Over the weekend, I'm going to try to do the actual rendezvous sequence, and see how it turns out.
The issue of the phasing burn value raises a question in my mind--as much as we want to fly "by the numbers", I suspect that there are going to be times when the "real world" numbers don't quite work in the Orbiter world. Do we acknowledge that, and if so, how?