[Using ipc.readLvar() with names with spaces]

On 25 June 2016 at 8:36 PM, Pete Dowson said:

I just checked, and, in fact, if you try to read an L:var which doesn't exist you actually get zero, not "nil" -- there's an error in my code there, which I will correct in the next FSUIPC update.  Currently you can only check whether it exists or not by using

n = ipc.getLvarId("name")

which will return nil if it doesn't exist.

But from what you say, the "nil" error you are getting is because it thinks the function you are calling doesn't exist. There's no library called "pic", so that could be one reason -- or is that another autocorrection gone wrong?

Also is isn't "readLVar" but "readLvar" -- another autocorrection? Surely not? Lua is case sensitive -- every character must be correctly upper or lower case.

If you really are using ipc.readLvar then I think you need LINDA support. I don't know what it is doing to get that screwed up, I don't know it at all I'm afraid.

BTW use the built-in FSUIPC assignable control "List local panel variables" to get a list of all the valid L:vars for the current aircraft, and their current values.

Pete

Thank you for the confirmation and information Pete. I was beginning to pull my hair out (and there is not much on top to come out).

PS. You are correct. I was trying to type the non-word "ipc" but autocorrect kept changing it to "pic" fast they I could see that it was doing it. 

[Using ipc.readLvar() with names with spaces]

7 minutes ago, aua668 said:

Hi,

 

Have you already tried:    x = ipc.readLvar("L:TURB ENG1 EPR")

 

That's how I read Lvars (with success).

 

Rgds

Reinhard

 

Yes thank you aua668. I tried using 'L:' (optional) and I get the error 'attempt to call field 'readLVar' (a nil value)' in the line with the statement:

epr = pic.readLvar("L:TURB ENG1 EPR").

[Using ipc.readLvar() with names with spaces]

Thank you Pete. That is strange. In a LINDA module LUA function I have used the instruction  x = ipc.readLvar("TURB ENG1 EPR") which returns a nil value and flags an error. When I trace the same Lvar (with spaces) in the LINDA tracer it works correctly and I can see the returned values.

The missing 'L' in ipc.readLvar was caused by autocorrect.

[Using ipc.readLvar() with names with spaces]

MOVED TO THE FSUIPC SUPPORT FORUM

Hi Pete

Some of the Lvars for the Aerosoft Airbus contain spaces (e.g. TURB ENG1 EPR) instead of the usual convention of using underscore (_). When these particular Lvars are used with ipc.readvar() FSUIPC4 returns a nil value (not found). However, when I can trace these Lvars using LINDA. Does the ipc.readLvar() command strip out the space characters?

[FSUIPC 4.95 - SimConnect_Text logging]

Sorry forgot paste the lines:

  3554233 ## SimConnect_Text: fWhite=0, 0x3303=0
  3555356 ## SimConnect_Text: fWhite=0, 0x3303=0
  3556339 ## SimConnect_Text: fWhite=0, 0x3303=0
  3557244 ## SimConnect_Text: fWhite=0, 0x3303=0
  3558258 ## SimConnect_Text: fWhite=0, 0x3303=0
  3559147 ## SimConnect_Text: fWhite=0, 0x3303=0

Pete, LINDA logs its activity to the LINDA Console window through FSUIPC4. This is used for reporting and debugging purposes.

[FSUIPC 4.95 - SimConnect_Text logging]

Since updating to FSUIPC4 4.95 I am seeing the following line repeatedly included in the FSUIPC4.log file (and in the LINDA console). Nothing else has changed in my configuration (P3Dv3.2, PMDG737 NGX, ASNv4.1, LINDA 2.7.x). Can this be inhibited?

[FSUIPC4 Offsets - AP Altitude/VS with A2A in FSX]

Will do. Thank you for looking. I'll report back.

 

Andrew

[FSUIPC4 Offsets - AP Altitude/VS with A2A in FSX]

Thank you Pete. It may only be A2A but P3D who have moved the goal posts. A2A may just be using the P3D definition for AP Alt and VS for both platforms.

 

Looking at the Lockheed Martin definition (http://www.prepar3d.com/SDKv2/LearningCenter/utilities/variables/simulation_variables.html#Aircraft%20Autopilot%20Data):

 

 

AUTOPILOT ALTITUDE LOCK VAR Selected altitude ("Altitude bug") Feet Y Shared Cockpit

 

AUTOPILOT VERTICAL HOLD VAR Selected vertical speed ("VSI bug") Feet/minute Y Shared Cockpit

 

I will inquire further with them.

[FSUIPC4 Offsets - AP Altitude/VS with A2A in FSX]

Hi Pete

 

I am the support developer for LINDA and have found an interesting issue with the offsets for Autopilot Altitude (07D4) and Vertical Velocity (07F2) with A2A aircraft add ons in FSX and P3D. I wonder what your view is.

 

The offsets are:

• 07D4  4 bytes  Autopilot altitude value, as metres*65536
• 07F2  2 bytes  Autopilot vertical speed value, as ft/min

​The altitude is quoted as being in metres and the vertical speed in ft/min.

 

​I have found through detailed tests that the conversion of Altitude from metres to feet is required only if the A2A A182 or C172 aircraft are used or when using P3D (alt = round(0x07D4 * 3.2808399 / 65536)). The reverse applies to the Vertical Speed. If not A2A or P3D, VS= round(0x07F2 / 3.2808399).

 

In all other cases (FSX and non-A2A), the offsets are defined as AP Alt in feet and AP VS in metres/sec. This is opposite from the FSUIPC4 Status of IPC Offsets for FSX document.

 

[POV View Resetting to Straight Ahead]

After over a year with any problems, my joystick HAT POV set up has gone crazy. The view has all of a sudden started resetting itself to the straight ahead (eye point reset) view on releasing the hat switch.  I have tried reassigning the Pan Left/Right/Up/Down to the Hat buttons with repeat in FSUIPC 4.937, but as soon as I release it springs back to view ahead. All FSX assignments have been deleted.

 

Can anyone suggest what has gone wrong?