Jump to content
The simFlight Network Forums

Jason Fayre

Members
  • Content Count

    40
  • Joined

  • Last visited

Community Reputation

2 Neutral

About Jason Fayre

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling
  • Location
    Toronto

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Ron. This message doesn't belong in the FSUIPC support group. The software I'm writing is Talking Flight Monitor, formerly called Flight Following. I believe you are familiar with it. I'm not writing a simulator. The software is an add-on for Prepar3d and FSX.
  2. Thanks Pete, Just so I'm clear, I can also use the offset block at 4200 right? It seems like most people are using 66c0, but 4200 has more space available.
  3. Hello, In the flight sim accessibility software I'm developing, I want to add support for reading info from the A2A family of aircraft. I'm doing this by reading panel variables with a LUA script, then writing those values to offsets that my software will read. I'm noticing that some of the readings will periodically show 0. For example, when reading the Engine CHT gauge with the Eng1_CHT variable repeatedly (say once a second), I will sometimes just get a 0 value. This is with the A2A bonanza. I'm using the event.Lvar function to update offset 66c0 when the var changes. My question is, is this normal? I don't know if a2a makes these variables fluctuate on-purpose to make the gauges more realistic? I'm totally blind, so I can't visually see what the gauges are doing.
  4. ah ok! I think it just clicked. I was just misunderstanding the documentation. I assumed the NNNN part needed to be in the high 16 bits as well. How about my second question above, regarding the actual format of the write?
  5. Sorry, one more question, and I apoligize if this is a dumb newbie question. What format am I writing 0d6c in? I know 0d70 is a null-terminated string. IN the python module, I need to specify the format of each read/write. For 32-bit values, I only have the option of a signed or unsigned value. I can also specify the number of bytes to be written for a string. Here is the section out of the pyuipc readme, if that helps at all: 'data' should be a list of tuples of two items. The first item of each tuple should be an offset to read or write. The second item denotes the type of the value to be read from or written into the offset. it should be either a string or an integer. If it is a string, it denotes a type of a fixed size: - b: a 1-byte unsigned value, to be converted into a Python int - 😄 a 1-byte signed value, to be converted into a Python int - h: a 2-byte signed value, to be converted into a Python int - H: a 2-byte unsigned value, to be converted into a Python int - d: a 4-byte signed value, to be converted into a Python int - u: a 4-byte unsigned value, to be converted into a Python long - l: an 8-byte signed value, to be converted into a Python long - L: an 8-byte unsigned value, to be converted into a Python long - f: an 8-byte floating point value, to be converted into a Python double If the second item is an integer, it denotes a string. If the value is positive, the string is of a fixed length with no zero terminator. If the value is negative, its absolute value is the maximal length of the string, but the string itself is zero terminated.
  6. Thanks pete. I know how to write to offsets using Python, but I'm having some trouble understanding what to write/read to offset 0d6c. I understand that the user offset I want to store the data in from the l:var is in the low 16 bits, but what do I store in the high 16 bits? I've read the documentation, I'm just not totally understanding how this works.
  7. Hello, In the accesibility software I'm developing, I've been asked to interface with A2A aircraft. Many of the specific settings that A2A uses can be accessed with local panel variables. My question is, what's the best way to do this? I need to be able to read several variables from the sim and then pass the data to my software, I assume with a fsuipc offset? I may also need to write variables, based on user input from my software. I know I can do a direct read of an l:var with fsuipc offsets, but I can't quite work out how to do it with the pyuipc module in python. I've also read that this can be slow, especially if I'm reading a lot of variables. Is it best to do this with a lua script and then just write the data to some of the user defined offsets that my software can then read? I assume that someone will need a registered FSUIPC version for a lua script to work, correct? Any pointers would be apreciated.
  8. oh wow! I missed that one! Is that the same as subtracting the magnetic variation from the true heading? If so, I'll just use that.
  9. Hi, Thanks for this! That will probably help, but I don't understand why the values I'm getting are wrong.
  10. Hello, I've had a long standing bug in my code that I really need to figure out. Let me first say that math is absolutely not my strong point. When calculating magnetic heading, my result will read as over 360 once the heading wraps around. So, 5 degrees might read as 365, 15 might read as 375. I've used the same calculation as what is listed in the fsuipc record to CSV lua script, but I'm not getting the same results. My code is in python. All the other offsets I'm using (well over 100 now), are working great. It's just this one that's tripping me up. Here is the code I'm using. I really hope someone can sort this out. The variables mentioned are grabbing the raw offset data from fsuipc. self.headingTrue = self.instr['Heading'] * 360 / (65536 * 65536) self.headingCorrected = self.instr['Heading'] - (self.instr['MagneticVariation'] * 65536) self.headingCorrected = self.headingCorrected * 360 / (65536 * 65536)
  11. Hello, For the flight sim accessibility software I'm writing, I've been asked if there is a way of detecting when a user is on the runway centre line, either during take off or landing. I see that the r5.csv that is produced by Makerwys give CentreLat and CentreLong fields, but I'm having trouble figuring out what to do with them. Is this the position of the centre line at the start of the runway? Also, any reason this data isn't included in the runways.xml file? I'm using python, and XML is a bit easier to deal with. I'm sure this is possible to calculate, since I've seen other software give the number of feet left or right of centre when landing. Any help would be apreciated.
  12. Hello all, Using my Flight Following software for blind flight sim users, several people are asking me if there is a way to change the next GPS waypoint. When flying on Vatsim, the controller will often tell a pilot to go direct to a waypoint. The current autopilot software we use doesn't support this. So, is there a way I can do this through FSUIPC? In looking at the documentation, I can read the next waypoint, which I'm doing already, but can I actually change the waypoint, going direct to one further along in the flight plan? I know this can be done with the FMC, but that isn't accessible either for blind users. Thanks!
  13. Hello, First of all, I want to thank Pete and everyone else for your help. The advice I've received on this forum has been hugely helpful in developing my application. As I mentioned in an earlier post, one of the facilities my software provides is reading out SimConnect messages via text to speech. This allow a blind flight sim user to read messages from Pro aTC/X, GSX, Active Sky, etc. I just had an issue reported by a user who is using rc4. I haven't used RC4 in years. When RC4 displays it's menus, it has a waypoint line at the top of the display that updates with heading, time to waypoint, etc. This is causing the rc4 window to read every time this is updated. I assume this is because it is updating the SimConnect changed offset, so my script thinks it is a new message. I was hoping to use the event id to do some specific processing on RC4 messages, but the event id seems to always be 0. Does anyone have any suggestions on how I might handle this? All I want to do is read the new RC4 menu when it updates with new options, like I'm doing with GSX.
  14. Hello, I'm looking at the offsets and trying to figure what is the best way to determine if nav1 detects a localiser and glide slope. I think I saw a glide slope detected flag, but I don't see anything for localiser. Would I just use the localiser signal offset?
  15. Actually. I may have found something. Would the offset at 2EA0: Elevator Trim Deflection, give me what I need?
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.