Page 3 of 3 FirstFirst 123
Results 21 to 28 of 28
  1. #21
    150+ Forum Groupie
    Join Date
    Jan 2006
    Location
    UK / Germany
    Posts
    174
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Hi

    As a suggestion perhaps the best thing for those of you with this error occuring constantly is to send in the logs. You can do all the flying you like, inside out, upside down, it won't help us to solve the problem, we already know the error is there at random in FSX, but we can't recreate it.

    Regards
    Jonathan Richardson
    Project Magenta
    Jonathan Richardson

  2. #22
    150+ Forum Groupie
    Join Date
    Nov 2005
    Location
    Helsinki - Finland
    Posts
    152
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Great idea, can You kindly assist here a bit. How to create and what
    log exactly You need? I would be happy to help here.
    ---
    ...do I send PmSystems log to You also, it seemed to crash.
    It is cold &dark mode now, which I do not want. I have unchecked
    those cold and dark mode. Also in pmsystems.ini it says OFF.
    But when PmSystems start, overhead is cold and dark, but does not
    react to any commands? There is propably some kind of problem with
    pmsoftware and my io hardware (opencockpits).

  3. #23
    150+ Forum Groupie
    Join Date
    Jan 2006
    Location
    UK / Germany
    Posts
    174
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Hi

    This is about the MCP, not pmSystems. There is a logging function in the MCP Log=On and this will produce general and a approach log. This might be useful.

    Regards
    Jonathan Richardson
    Project Magenta
    Jonathan Richardson

  4. #24
    150+ Forum Groupie
    Join Date
    Nov 2005
    Location
    Helsinki - Finland
    Posts
    152
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    For A320 can it be FCU log , not mcp log? I'm in work now so
    I cannot check. I'll get back on this tonight.
    I'll be most happy to help out here, Jonathan

  5. #25
    150+ Forum Groupie
    Join Date
    Jan 2006
    Location
    UK / Germany
    Posts
    174
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Yes, the FCU has logging facilities as well. If you send in logs, please be clear to mark them as the FSX G/S capture problem in the subject. As to whether the logs will contain the required specific info needed to track and find the problem I can not say at this stage but it is more likely to help rather than flying various approaches because we already know of the problem.

    Regards
    Jonathan Richardson
    Project Magenta
    Jonathan Richardson

  6. #26
    10+ Posting Member
    Join Date
    Apr 2008
    Location
    The Netherlands
    Posts
    16
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Red face Found a way to avoid/solve the problem

    In our case the GS problem always occurred just after the AP picks up the GS nodding down, the kite has the intention to follow the GS, and stops doing that, adding thrust to stay on the altitude selected in the MCP.
    We talked with a KLM Captain/instructor about this. The pro's hit the AP button as soon as the Localizer comes alive, even if the GS isn't alive yet. So we now do the same. When the GS is alive and approaching the middle, we lower the IAS on the MCP with 5 or 10 kts. The plane is lowering it's speed while the GS bug passes the middle and without one exception (so far) it will follow the GS perfectly.
    We'll keep on testing....

    On the other hand... someone suggested to set the milliseconds in the mcp.ini file at 80 instead of within the range 50-70. We did, but then the anunciators of the gear start to behave in a very strange way. F.i. when we are at the ramp, before engine startup the EGT's start to act like a crazy windmill. So we started to play with the millisecond figure simultaniously with testing the GS problem and are still searching for the right figure in OUR system. Numbers within the range 50-70 give us a better performance.
    "Ladies and Gentleman..., Captain"
    http://www.b737sim.nl

  7. Thanks brianwilliamson thanked for this post
  8. #27
    150+ Forum Groupie
    Join Date
    Jan 2006
    Location
    UK / Germany
    Posts
    174
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Hi

    The problem is if there is any instability in VS prior to the the GS capture, then the VS might win (depending on some other factors) and the MCP triggers into a VS mode rather than GS capture mode. (It misses what it is supposed to do unfortunately). This won't happen in FS9, only FSX. If your approach is rock solid prior to GS capture you are much less likely to get the problem in FSX, this is why it has been so difficult to trace. Now we understand more the cause, and to some better degree how to recreate it, hopefully we are more on track to find a solution.

    Regards
    Jonathan Richardson
    Jonathan Richardson

  9. #28
    150+ Forum Groupie
    Join Date
    Nov 2005
    Location
    Helsinki - Finland
    Posts
    152
    Contribute If you enjoy reading the
    content here, click the below
    image to support MyCockpit site.
    Click Here To Contribute To Our Site

    Intercepting G/S path

    Hello again,
    I hope Pm stuff finds something to cure this overshoot problem.
    I noticed one thig just after series of testing my IFDG Alitalia A319 (pm site).
    When I make an approach with autopilot lateral and vertical managed (dotted)
    sometimes it does overshoot of G/S path, but when I pull HDG to the pilot it
    NEVER does overshoot. Is this just a miracle or not, but it seems true.
    So, before turning to RWY heading I pull hdg to me while alt and spd are both
    managed the plane turns to LOC nicely and finally follows G/S path. That small
    magenta circle comes down with magenta diamond like it should.
    ---
    One problem I still have and that is my aircraft goes to cruising level too slowly so
    it makes new TOC points to the plan.

Page 3 of 3 FirstFirst 123

Similar Threads

  1. OC relay card suddenly behaves strange.
    By crashdog in forum OpenCockpits General Discussion
    Replies: 1
    Last Post: 07-18-2010, 10:29 AM
  2. Trim indicaor suddenly gone
    By FlightsimBerlin in forum PM Boeing GC
    Replies: 1
    Last Post: 08-17-2009, 08:46 PM