Jump to content
The simFlight Network Forums

Adrie

Members
  • Posts

    3
  • Joined

  • Last visited

Everything posted by Adrie

  1. Dear Pete, Best wishes for the new year! Health and happiness and lots of software challenges! It's been a while ago since i looked into the matter, but i've had many other things to do. Anyway, i've picked it up again and done a test run with logging. I've done this run with FS2004 and FSInterrogate 1.8.0.21 It's with a Cessna 172 standing on the ground, FS2004 is not paused. I've setup the logging (with IPCs now). The log is attached as a zipped file. Then i've done reads and writes with FSInterrogate only, not with my software. I've first read all data a few times, then i've read 0C3E as Signed16bit three times (values are 31, 32, 33 resp. so drift is ticking ok), see 3 lines at 760375 ev. Further on in line 788000 the value shown is 34 (drift is ticking ok). Then i've written 0 (as a Signed16bit) in 0C3E, see line 790000; this seems ok. (a question though: is it normal that only 1 byte is written?) In the next line 790016 i've re-read the data, and it shows 0 correctly, but in reading a second time (see next line 790016) the value popped back to 34. This is exactly the problem i've described previously to you. Then i've repeated write, read and re-read, see line 794703, write value 81 = hex51, reading (next line 794703) shows correctly hex51, but re-reading a bit later in the second-line 794734 the value popped back to 34 (this is the same value as in 788000, so no drift-increment took place). Some more re-reading shows that the value continues incrementing from 34. I hope this gives some insight in the described problem. Regards from Adrie Voordijk FSUIPC_log.zip
  2. Pete, Thanks for your rapid reply. I've installed FSUIPC 3.70 and re-run my tests. The behaviour is the same. I've made 2 test-runs with logging, both with FSUIPC logging (suffix AV1 and AV2) and also my s/w internal logging. I have annotated my 2nd test-run log (AV2) in a word document, so please have a look at that. I hope this will give you enough information to see why i am confused. Thanks in advance and Regards, Adrie FSUIPC logs and AV logs.zip
  3. L.S., I am driving from/to FS2004 via FSUIPC an (external to MS FS) Heading Indicator instrument with a Gyrodrift Compensation knob. FSUIPC is version 3.201 of 16 Febr. 2004. My software reads 3 values via FSUIPC: True Heading in $0580,4 Magnetic Variation in $02A0,2 and Gyrodrift in $0C3E,2. It calculates 'Indicated Heading' (Indic.Hdg = True Heading + Gyrodrift - Magnetic Variation) and sends this regularly to the instrument; this goes fine. I encounter difficulties when the user turns the Gyrodrift Compensation knob on the instrument and i want to send the altered value to FS via FSUIPC. I observe the following: - the start situation is: Gyrodrift=0 degr, Magnetic Variation=-3.0 degr and True Heading=231 degr; the Indicated course is 234 degr, all ok, - my s/w reads the given Gyrodrift Compensation value from the instrument, lets say 0.5 degree, converted to FS 16 bit smallint this gives 81, - my s/w writes via fsuipc this value of 81 in $0C3E,2 - the next time that my s/w reads the 3 values, the Gyrodrift repeats my value of 81, - the problem is that the next time thereafter (16 ms later) my s/w reads a Gyrodrift of 0, so 'something' has overwritten my input. Only when I increase the given value over 192 (is > 1 degr) a non-zero value is read back in the 2nd cycle, but it is still lower than the given value. I have tried the same by: - setting the FS in slew-mode, then update the value, then set back to normal mode, but the same effect, - setting FS drift-simulation OFF, but the same effect. - I have not tried this with a newer version of FS. My questions are: - Do you know about this 'problem'? - Is this solved in newer versions of FS? - Is there another way to in/de-crease the Gyrodrift value in FS? - Is there any other way that you can help me? Thanks in advance and Regards, Adrie
×
×
  • 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.