Andrew

One concept that has been floating around in my head for a while and is on the same lines as your transmitter is to have a "UAV Listen" plugin on the GCS.
This would allow for a second GCS to connect to the main GCS that is actually talking to the flight hardware and essentially relay the UAV Objects.
I would imagine having the ability to allow the secondary clients read/write access or only read access to the UAV Objects.

I see a few situations for this, one is I have a serial link between the flight h/w and GCS but my phone/tablet only has wifi/bluetooth ... I can have my laptop sitting by my side relaying the flight info to my phone mounted on my Tx...
Another would be to transmit flight info across the world in real time, someone in Australia can watch me fly live in USA (Read only) and even help me debug problems I am having...

If this is a feature others see as worthwhile then it would be good if the changes you propose support it as well...

Have you plugged the cc in via USB and confirmed it is good?

It is worth checking the telemetry serial baud rate configured on the cc whilst you have the USB connected.

I believe it defaults to 57600 and Your previous post indicated you had the wifi module set to 9600.

The scope plugin has the ability to save csv files. It saves at a periodic rate and saves the last value received for each UAVobject variable defined in it's settings.

It can save from live connection and should also work for a replay of a log file but I haven't tried it.

I would try a few basic tests first.

Can you confirm that the GCS virtual sticks follow you Tx sticks when it is connected. this will confirm the input is configured correctly.
Next, to test the config you don't want any stabilization as this will introduce another unknown.
without any stabilization, the swash should follow your commands directly from the Tx.
Next turn the stabilization back on and perform the test you have been describing.

you may have to change which is the "1st servo" to get the fore/aft correct, but if you change that you will likely have to swap the left/right channel assignments.
when looking down on the swash with the tail towards you, the image on the GCS config page should show the servos as you see them...

Depending on which version of the GCS you are using, the curve 2 settings are configurable.

Check the collective pass through and it will reveal another drop down for you to select the source.

There are two versions of this out there based on firmware updates, the older one which could only be configured for a single type of receiver at compile time and the newer which allows runtime config of the receiver type.

The newer one also requires you to modify the input tab to configure which channel is used as the input...