Menu

#150 b1900d from YPDN GPS search cannot find destination.

Fixed
nobody
2011-06-05
2010-07-22
Anonymous
No

Originally created by: grg.gdsr (code.google.com)
Originally owned by: zakalawe@mac.com

What steps will reproduce the problem?
1.Start FlightGear with b1900d at YPDN Darwin Austrailia
2.Start b1900d, set GPS APR and GPS CRS to on.
3.Set aircraft panel NAV, IAS and ALT to on.
4.Open Equipment, GPS.
5.In the type drop down box choose any.
6.In the Search field type and other airport code.
7.Click Search
What is the expected output? What do you see instead?
The expected is for airport to be found and the name shown on the right.
What I see instead is nothing found just blank on the right and the airport I am at (YPDN) remaining in view above after I click DTO.

What version of the product are you using? On what operating system?
I'm using FlightGear 2.0.0-2. Converted from tgz packages for Slackware to Debian packages foe Ubuntu using alien.
Operating system: Ubuntu 10.04 lucid

Please provide any additional information below.
The same happens when taking off from some other airports eg. WIIJ Yogyakarta Indonesia.

Discussion

  • Anonymous

    Anonymous - 2010-07-25

    Originally posted by: grg.gdsr (code.google.com)

    Of course with this bug I cannot use the autopilot to fly to another airport.

     
  • Anonymous

    Anonymous - 2010-07-27

    Originally posted by: grg.gdsr (code.google.com)

    An update to make this report more clear; it is on certain airports that the Search in GPS cannot find. If I enter RPLL (Manille Ninoy Aquino INTL, Phillipines), WIIJ (Yogyakarta, Indonesia). It wont find them. I'm not certain of all the airports it wont find or if it on wont find them from YPDN. It will find YBCS (Cairns INTL), from YPDN. I will test more to see if YPDN is not the only airport those airports mentioned, cannot be found.

     
  • Anonymous

    Anonymous - 2010-07-27

    Originally posted by: grg.gdsr (code.google.com)

    It does not seem to matther what airport you start before takeoff. It is certain  airports cannot be found in the GPS Search function. I tried starting the b1900 from RPLL and it could not find YBCS, VNKT (Kathmandu), RJBB (Kansai INTL). It could find VHHH (Hongkong INTL)

     
  • Anonymous

    Anonymous - 2010-07-28

    Originally posted by: grg.gdsr (code.google.com)

    It seems to be a matter of how distant the airport is from the aircraft start airport. Is this just a limitation of GPS, that is also in reality or a real bug?
    Flying a A380-House does not have this problem with its autopilot. navigating to distant airports but it uses a different system.
    So can someone tell me if this is just a limitation of GPS navigation or a bug?

     
  • Anonymous

    Anonymous - 2010-07-30

    Originally posted by: zakalawe@mac.com

    This is a limitation of my search code, which the GPS uses - the problem is avoiding a long pause (like five or ten seconds) while searching *partial* airport identifiers, which are intended to be searched by proximity. What I need to do, is detect when you've entered more than 2 characters to search on, and switch to an alphabetic instead of distance based search.

    Labels: Cockpit gps
    Owner: zakalawe
    Status: Accepted

     
  • Anonymous

    Anonymous - 2011-06-05

    Originally posted by: bre... (code.google.com)@gmail.com

    (No comment was entered for this change.)

    Status: Temp

     
  • Anonymous

    Anonymous - 2011-06-05

    Originally posted by: bre... (code.google.com)@gmail.com

    (No comment was entered for this change.)

    Status: Fixed

     

Log in to post a comment.

MongoDB Logo MongoDB