Discovered my Fix.

Any Switches and or Knobs not only need the klid variable triggered they also need there subsequent animations called as well and in the correct order as well.

I had to call

G02_004_SW3 = 1
G02_004_SW3_LAST = 0
klid = 1702004


using this template for activation I used some conditional variables and now have the button functioning as an up and down / disconnect button.

Push once for CWS , Push Again to put into CMD mode , Pushing once more Disconnects and starts over.

Hope this helps anyone else trying to understand the structure of cockpit variables.

I used a program called spad.next it allows you see variables being passed through the simulator , some developers have variables visible and some do not.  so you can add all the local variables while the sim is live , flick your switches and dials.  Then you go back to Spad.next and look through variables that have changes most recently.  Those variables are mostly likely involved in the execution of your button / switch / dial.  Then through looking at Captain Sims other SDK documentation on other aircraft and how there variables are laid out and what they mean , it was a series of trial and error in determine how the L1011 is laid out.  That's a really quick look at how I figured it out.  I'm still finishing up the rest of the Autopilot and testing this evening, looking forward to flying some routes very soon!

There are probably a few different reasons why they may have chosen not to release it yet but we can always hope.

I think there is a free version of SPAD.next , I bought it because I use it with the Saitek radios for ease of compatability with other simulators and software variables.  I also write and have written honeycomb profiles for several other aircraft for P3D / x-plane and Spad has really help speed things along if the simulator doesn't have a way to view variable through FSUIPC. My needs it fits me but for your needs the free version might just be enough to get you what you need.  Good luck to ya out there and here's to hoping for an SDK sometime in the future.

Thanks for the share.  That AP function led me to give up trying to figure it out.