Jump to content
The simFlight Network Forums

cjellwood

Members
  • Posts

    60
  • Joined

  • Last visited

Posts posted by cjellwood

  1. thanks Pete, yer a legend!

    It has been a good day all round. Me and eldest son went to Southend airport today for some instrument tuition and ended up meeting some engineers who gave me a back stage pass to the Vulcan area where they were turning it around and firing up the hair dryers. One does not realise how huge this bird is until it move 2ft above your head.

    Anyway, pressure settings were explained and I was able to tune to ATIS for the QNH data so to make the pressure adjustment. The adjustments are very modest so I dont think my virtual life was in danger when not giving it due respect in FS :)

    SP_A0886.jpg

    SP_A0887.jpg

  2. no worries, I am delighted with the level of accuracy dealt by FSCUIP so far in this project so will put this down to the 9/10 devil that always appears in my projects. maybe keep an eye out for this G1000 reading in future simconnect versions (assuming there will be future versions). btw, i did update to latest version prior to this test :D

    This weekend I have a meeting with a helicopter instructor at southend airport. The point of the meeting is to take notes of the controls to aid my motion sim project but while there I will make a point of learning about this setting and its application.

    thanks

    Chris

  3. hmmm this is odd. I have been testing with the Cessna 172SP that has Garmin glass display as you already know. The follwing list is a timeline of what happened when I selected the standard Cessna (normal gauges) and the output recieved

    1. Loaded default Cessna 172 and changed Altimeter calibration knob to 30.01.

    "The FSCUIP data successfully changed to this value and displayed correctly as expected"

    2. With the reading remaining at 30.01, I changed aircraft mid flight to the Cessna 172SP (Garmin glass display)

    "Kollsman window successfully showed the reading as selected in previous aircraft in both FS and FSCUIP"

    3. Remaining in the Cessna 172SP, I changed the altimeter setting to 30.15

    "Kollsman window in FS changes as expected but FSCUIP output remained as 30.01"

    4. Changed aircraft mid flight back to standard Cessna 172

    "Suprised to see that the Kollsman reading was still at 30.01??"

    So the Kollsman value is fine when going from standard Cessna to the 172SP but not the other way around. I cant get my head around this so am taking dogs for a walk :roll:

  4. I increased the value and here is the log output below. The value displayed on the screen did not change when value altered

    ********* FSUIPC4, Version 4.30 by Pete Dowson *********

    User Name="Christopher Ellwood"

    User Addr="c.ellwood2@btinternet.com"

    FSUIPC4 Key is provided

    WIDEFS7 not user registered, or expired

    [Continuation log requested by user]

    Running inside FSX (SimConnect Acc/SP2 Oct07)

    Module base=61000000

    Wind smoothing fix is fully installed

    306265 System time = 12:46:25, FSX time = 12:41:46 (20:41Z)

    306312 Monitor IPC:0330 (U16) = 16210

    312437 *** EVENT: Cntrl= 65883 (0x0001015b), Param= 2 (0x00000002) KOHLSMAN_INC

    313219 *** EVENT: Cntrl= 65883 (0x0001015b), Param= 2 (0x00000002) KOHLSMAN_INC

    313969 *** EVENT: Cntrl= 65883 (0x0001015b), Param= 2 (0x00000002) KOHLSMAN_INC

    314687 *** EVENT: Cntrl= 65883 (0x0001015b), Param= 2 (0x00000002) KOHLSMAN_INC

    315453 *** EVENT: Cntrl= 65883 (0x0001015b), Param= 2 (0x00000002) KOHLSMAN_INC

    316219 *** EVENT: Cntrl= 65883 (0x0001015b), Param= 2 (0x00000002) KOHLSMAN_INC

    316765 *** EVENT: Cntrl= 65883 (0x0001015b), Param= 2 (0x00000002) KOHLSMAN_INC

    317453 *** EVENT: Cntrl= 65883 (0x0001015b), Param= 2 (0x00000002) KOHLSMAN_INC

    318015 *** EVENT: Cntrl= 65883 (0x0001015b), Param= 2 (0x00000002) KOHLSMAN_INC

    318578 *** EVENT: Cntrl= 65883 (0x0001015b), Param= 2 (0x00000002) KOHLSMAN_INC

    319047 *** EVENT: Cntrl= 65883 (0x0001015b), Param= 2 (0x00000002) KOHLSMAN_INC

    319437 *** EVENT: Cntrl= 65883 (0x0001015b), Param= 2 (0x00000002) KOHLSMAN_INC

    319703 *** EVENT: Cntrl= 65883 (0x0001015b), Param= 2 (0x00000002) KOHLSMAN_INC

    319937 *** EVENT: Cntrl= 65883 (0x0001015b), Param= 2 (0x00000002) KOHLSMAN_INC

    320156 *** EVENT: Cntrl= 65883 (0x0001015b), Param= 2 (0x00000002) KOHLSMAN_INC

    320390 *** EVENT: Cntrl= 65883 (0x0001015b), Param= 2 (0x00000002) KOHLSMAN_INC

    320656 *** EVENT: Cntrl= 65883 (0x0001015b), Param= 2 (0x00000002) KOHLSMAN_INC

    321375 *** EVENT: Cntrl= 65883 (0x0001015b), Param= 2 (0x00000002) KOHLSMAN_INC

    322937 *** EVENT: Cntrl= 65883 (0x0001015b), Param= 2 (0x00000002) KOHLSMAN_INC

    323922 *** EVENT: Cntrl= 65883 (0x0001015b), Param= 2 (0x00000002) KOHLSMAN_INC

    331594 *** EVENT: Cntrl= 65794 (0x00010102), Param= 0 (0x00000000) PAUSE_ON

    339156 Sim stopped: average frame rate for last 33 secs = 33.9 fps

  5. Hi, here is a pic to show the value I am trying to work with. I assume from previous queries that this is the Kollsman window backed up by the fact that I have successfully retrieved this value (thanks paul) but it does not change when I adjust the altimeter setting knob? The value changes in FS but not in FSCUIP output

    kollsman.jpg

    Maybe i do not understand this value as much as i should and possibly missing a brick in the logic. Sorry if that is the case

    Chris

  6. Hi again Pete, sorry to be a pest. In an earlier message I asked about the Kollsman window data and you recommended a particaular offset 0330 which seems great according to the docs but I am still lost over it? The data shown in FS is usually '29.92' for this value but the offset 0330 does not change in the interrogator output when I change the value in FS? Also the data output in interrogator looks nothing like 29.92. I am completely lost for this value, please help

    Chris

  7. hi Pete, I have a query for you about WideFS. The display app I am building currently working on has a host/client system similar to widefs and does not actually require widefs because I have my own host running on the main pc liasing with FSCUIP and serving connections to client etc. Well, i am thinking of scrubbing the host part of it and simply having the client lias with WideFS for the connection.

    Advantage: No host to install or screw around with when i just want to run FS and FLY!

    Disadvantage: WideFS client will need to be started on client machine prior to my client app starting. Also will need to register WideFS

    I dont mind registering WideFS, I made a booboo when I registered and paid originally because I only registered and paid for the basic FSCUIP. I forgot to register WideFS also :( I know I can upgrade but 2 days ago my other half gave birth to my third son meaning all hobby money is going on nappies until mum says otherwise.

    ok so to the point sorry, can I write the WideFS client into my client code so it simply connects to FS on launch? My code is VB and will ask my clever friend to do the coding so I dont give you more stress :x

    At the moment i am waiting for Aerosofts FSMap serial to arrive which apparently requires WideFS to function as client. Do you know if this has a similar built in WideFS client or runs seperate?

    Thanks

    Chris

  8. Hi, sorry to be a pest but I have another small issue. I have just completed the NAV/COM display and everything fine apart from I noticed the COM value is supplied as 5 digits long (123.45), whereas the real pfd display shows 6 digits (123.455). Do I have to live with 5 digits only or am I doing somthing dumb as usual? The data is being read from offset as UShort

    Dim COM1Freq As New Offset(Of UShort)(&H34E)

    thanks

    Chris

  9. I dont wish to scare you but my impairment is because of schitzophrenia. Not the type where people hear voices I must stress! :twisted: Parts of my brain do not communicate with eachother properly so although my eyes are perfectly fine, what goes into them registers in the wrong area of the brain and causes masses of confusion. I have discovered the brain to be a very bizare piece of meat that can completely change our perception of reality if something does not add up or goes astray. It can sometimes create a completely new reality by filling in blanks on its own accord again if input data is incorrect or does not fit with the current belief. So in general my problem is that my brain makes assumptions based on too much varied data then does not allow me to correct or pursue for the correct answer to problems because it has already decided that itself is correct and no more information is required so delivers it to the trash bin or somewhere more exciting. The most annoying part of this is that when someone points out the correct answer to me, I realise that I already knew it! It is unlikely for someone that not have this defect to understand, most think I am just crazy or ignorant lol. I see many people have this problem, it is just more apparent/amplified in me.

    So the reason for my project is to create a flight environment that bombards me with indisputable data that cannot be argued with.

    Neo was right, nothing is real it is just our perception. But the spoon is real because i am using it to eat all the leftover christmas pudding :)

  10. thanks Mr Pete :) I did see that offset in the guide but was confused when it said that FS does not use it? Anyways all good now thanks

    Here is a screen shot of my pfd so far written in VB/GDI. Just to alter a few things on this section then later today i will start on the surrounding indicators such as oil temp, pressure, fuel etc. Shouold be a cracking little tool when finnishd although like all my projects they never are finnished lol So whats wrong with pretty pictures eh?

    scrshot1.gif

  11. the doc that says , "For degrees *360/65536. Convert True headings to Magnetic by subtracting this value". I just naturally assumed that once factoring was done then the subtraction took place? What you say is obvious now I see it before me sorry. The fact that -1 = 359 was not the issue I did not understand, it was the issue I needed help resolving which you have done

    Thanks

  12. This stage turned out ok in the end. I thought this was going the be the easy part!

    To get around the negative value problem I simply created an argument to sniff the '-' and add 360. The doc gave me the impression that once the factoring was done correct then everything swims but obviously not. Surely Pete is aware of this glitch but relies on people being inteligent lol .

    Public Class frmMain

    Dim Altitude As New Offset(Of Integer)(&H3324)

    Dim AirSpeed As New Offset(Of Integer)(&H2BC)

    Dim Pitch As New Offset(Of Integer)(&H578)

    Dim Bank As New Offset(Of Integer)(&H57C)

    Dim Heading As New Offset(Of UInteger)(&H580)

    Dim MagVar As New Offset(Of Integer)(&H2A0)

    Dim Flaps As New Offset(Of Integer)(&HBFC)

    ...

    txtAirSpeed.Text = FormatNumber((AirSpeed.Value / 128D), 1).ToString

    txtAltitude.Text = Altitude.Value.ToString

    Dim BankValue = FormatNumber((Bank.Value / 10000000), 1).ToString

    txtBank.Text = BankValue.ToString

    Dim FlapsValue As Long = Flaps.Value

    txtFlaps.Text = Flaps.Value.ToString

    Dim HeadingValue As Double = Heading.Value

    HeadingValue = HeadingValue * 360

    HeadingValue = HeadingValue / 4294967296

    HeadingValue = HeadingValue - 17.89124

    If HeadingValue < 0 Then HeadingValue += 360

    txtHeading.Text = FormatNumber((HeadingValue), 1).ToString

    Dim PitchValue = FormatNumber((Pitch.Value / 10000000), 1).ToString

    txtPitch.Text = PitchValue.ToString

    Gives this nice output. (you probably seen this before but I am impressed)

    Untitled-2.gif

  13. I am factoring in the magnetic variation but that poses a new problem that may expose a bug in the works. The factored magnetic variation value is a constant 18.20435 when viewed in the Interrogator. Subtracting this from the heading value is easy but I get an obvious math problem when the heading is at between 343 -> 349 degrees i.e 343 - 18 = -1

    so basically, now when I am at between 343 -> 359 degrees I get a negative value again?

    I think it would be easier to just use the giro offset before I get banned for being a pain in the ass :)

    on that subject, you reccomended using 'UInteger' to solve the previous problem... can you tell me what that type would be to get the Float64 value from 2B00?

  14. The value I am getting from offset 0580 heading is different from the data Interrogator shows? example:

    when the plane goes west to say '330 degrees', Interrogator shows 4143547924 where as my data read shows -151419372 ??

    It is in sync when flying East so why the different data going west? Shouold Interrogator not be showing raw data the same as what I get from 0580?

    Thanks

  15. Hi, I am having trouble with heading offset 0580. When my plane is heading 30 degrees, the FSCUIP shows 46? Here is my code ...

    txtAirSpeed.Text = FormatNumber((AirSpeed.Value / 128D)).ToString

    txtAltitude.Text = Altitude.Value.ToString

    Dim BankValue = FormatNumber((Bank.Value / 10000000), 1).ToString

    txtBank.Text = BankValue.ToString

    txtFlaps.Text = Flaps.Value.ToString

    Dim HeadingValue As Long = Heading.Value

    HeadingValue = HeadingValue * 360

    HeadingValue = HeadingValue / 4294967296

    txtHeading.Text = HeadingValue.ToString

    Dim PitchValue = FormatNumber((Pitch.Value / 10000000), 1).ToString

    txtPitch.Text = PitchValue.ToString

    am i doing something really dumb?

×
×
  • 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.