I was trying to follow these instructions: (http://www.a2asimulations.com/forum/viewtopic.php?f=23&t=19751)
"STEP 3.
Next, when in your plane in FSX, open up FSUIPC. The first thing we need to do is assign some controls for the LUA program we just moved. I suggest using two key presses you dont use for anything else (I use F3 and F4). Next using FSUIPC set a key for each of these two commands which you should find in the control list:
'Lua log Lvars' and 'LuaKillAll'
There are other controls associated with LUAs, however I only used these two.
Click ok in FSUIPC and return to your cockpit. Now, press the key assigned to 'Lua log Lvars' and you will see a panel with a lot of red text come up, press the key for LuaKillAll and this should disappear(sometimes you need to press both a few times for it to work). If that works you can now read LVars within the cockpit! (this is the key to this whole system and how we can operate these controls, thanks Pete Dowson!!!! (the maker of FSUIPC))
Now start the LUA and then start flicking switches in the cockpit with your mouse, you should see all sorts of things come up in red text (it may be 'rolling' anyway as things like oxygen or hydraulic pressure deplete). Dont worry about trying to read these entries within FSX, there is an easier way!
After trying some controls stop the LUA and go to your 'Modules' folder. Now you should see a file called 'log.lvars.log'
Open this file using notepad and you will see all of the entries that appeared in red on your screen in FSX within this file. Every time you start the LUA in FSX, entries are added to this file, however you need to shut it down and start it again every time you do this wioth the last entires being at the bottom. The entries in this file are Lvars, or local variables and they cover all sorts of things, though their names generally give you an idea of what they do. What use are these things? well we are going to use these entries to create a Macro file.]
As stated, using this procedure does not result in a "lua window with red letters" but does indeed open a lua log. I understand your statement about not allowing enough time and will try again tonight allowing more time. I looked at the documentation you specified ( fsuipc4 for advanced users page 35) . It looks about the same as what I tried except the assigned control suggested is "list local panel variables" instead of "lua log lvars". I will also try this tonight.
I also noted that the Wilco panel I am trying to access seems to be linked to a DLL and not XML. I am not sure if this rules out LVAR usage.
Thanks for your quick response. d:-)