• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

The KLN90B for FSX/Prepar3d in beta.

@Tushka: bear in mind that one cannot add a 3d object to a virtual cockpit unless one has the interior model's source file (.max or .gmax) and can Merge the 3d objects, tag the controls with the XML script from modeldef.xml, and then export and compile a new model file.[/QUOTE]

I'm aware of this limitation unfortunately, meaning that if let's example say a functional 3D model for KLN is made, and the source code is open, and then the developers of the Tu-154 will fit the KLN90 3D model into the interior source model of the Tu-154. I don't claim to know much about programming but for them should be a simple task. Other developers could do the same, add the KLN to their models. The user of course cannot do this...
 
KC13 said:
Has anyone tried this in FS9 on the original PT Tu-154B?
Click to expand...

Unlikely it will work for FS9 due it was exported to FSX. I tried on the Il-62 with no success. FS9 KLN is good as it is anyway, no need for change :)

Anyway Dutch, I'm interested in FS9 too as I have my Tu-134. Do you think there is any way you can make the KLN connect with the (custom) autopilot of the SCS Tu-134? I'm not asking you to spend extra time and resources working on that plane, just if maybe there is a way I can do it myself.
 
The current version will not work on FS9 because it uses SimConnect. The gauge does export four variables that are used by the ABSU, and most probably you could pick those up and use them under FS9. Except it won't run under FS9 because of SimConnect.

I'm not exactly sure how vital SimConnect is in this FSX gauge. Probably should look to see what we'd lose if it was made optional.
 
Dutch said:
The current version will not work on FS9 because it uses SimConnect. The gauge does export four variables that are used by the ABSU, and most probably you could pick those up and use them under FS9. Except it won't run under FS9 because of SimConnect.

I'm not exactly sure how vital SimConnect is in this FSX gauge. Probably should look to see what we'd lose if it was made optional.
Click to expand...

It's ok, I think better to focus on FSX as those older FS9 jetliners already have a fully working GPS + some other navigation methods.
 
Nice to have the KLN back in my "older" cockpits.
:) I love it!

One feature request for the future: When adding new waypoints in flightplan, it would be helpful if it read the keyboard like the default gps does. Yeah, I know, not entirely realistic, but very helpfull when adding the longer flights ;)
 
Last edited:
I noticed something: I run Win8, when I have FSX without compatibility mode on, KLN crashes the sim on init pos page, when it's on Win7 compatibility, everything is fine.
 
An update to the problem: KLN itself seem to read the current UTC time wrong, when it is in Win7 compatibility mode this doesn't crash FSX, but without it it does unless the correct one is entered.
 
Hi Dutch and others,

thanks for picking up this very nice sim tool. I am refreshing my sim hobby after some 5 years of pause and I was delighted to see this initiation. I hope it is going on, though as I see Dutch dissapeared for a while :(

I can confirm that on Win 8.1 (Windows 7 compatibility mode) the GPS is not picking up the time and shows what is displayed on the User Guide as well (08:10:00 UTC). The date is OK.

I made some tests and I think the functionality most missing is the SID/STAR selection. As I understand it was disabled due to some serious bugs. If the code should be touched anyhow, would not be useful to change the SID/STAR file format to a one that is provided by Navigraph already? If this and the ISEC file would be available from Navigraph, that would possibly make the GPS even more popular. I am not familiar with the GPS code, but in general changing the input parsing would not be a big deal. I might contribute if needed (possibly not with the complete SID/STAR management code, but at least with the file parsing part).

Gabor
 
Last edited:
Also it seems the GPS is not bound to the main power or avionics power. It's a long time I haven't program FS, but as I remember it would be too much difficult to "block" turning the GPS on if avionics is off. It is not a critical issue anyhow.
 
Does anyone know how I could reach Dutch? It seems he had totally dissapeared from this forum for several months.
 
Note, I am here, but working on other (revenue-producing) sim projects. But Gabor here has the code and is working on it, and I'm looking forward to his improvements.

I use the KLN90B in most all my airplanes in place of more modern GPS units. I simply prefer it.

But then, most of my favorite airplanes were flying in the 1960s. I rarely go past 70s vintage. I like round gauges.
 
Hi,

Yes, I am working on the SID/STAR handling. Hopefully I can come up with some improvements soon. At the moment I try to clean up the code and find the bugs, but right after I migh initiate here a discussion about if we should use an Airac FMS format (as an alternative) so that we could get the updates regularly. We don't have to ask for a specific (new) format, we might use an existing one.

https://www.navigraph.com/FmsDataManualInstall.aspx

Gabor
 
Hi,

I have prepared v0.77B of KLN90B. It was not tested thoroughly yet but seems to be stable. This has no installer. Use the v0.76B package and update the gauge DLL from this package. I will have limited internet access during the next week. After that I will continue working on v0.78B.

Download link: KLN90B v0.77B Beta (including PDF)

Installation
  1. Install v0.76B with its installer.
  2. Overwrite the kln90b.dll with the new DLL in the Gauges directory of FSX.
  3. Install any of the supported Navigraph FMS Data packs. No such package is provided with the KLN90B package itself.
  4. Make the necessary modifications in the KLN90B.CNF config file in the KLN90B directory of FSX
  5. [UPDATE] Delete the PTT_XXX.DAT files in the KLN90B folder and let the program to re-generate them on startup!
  6. Run FSX. It might ask you to allow using the new version of the DLL. Acknowledge it.
Improvements
  1. SID/STAR bugs are fixed and feature is re-enabled.
  2. Besides the current navigation pack, support for three Navigraph FMS packages are added.
  3. SID/STAR transition support is added to APT+7 pages (see KLN 90B Pilot Guide chapter 6.2 SID/STAR Procedures). Available if used with any of the Navigraph FMS packages.
  4. Offers adding the STAR airport to the flight plan if it is not yet included (see KLN 90B Pilot Guide chapter 6.2.2 Selecting a STAR point 7)
  5. Removes possible duplicate waypoints at the end of the SID and at the beginning of the STAR.
  6. Maximum number of flight plan points is increased from the real life 30 to 50 to support longer SID/STARs. In later versions this might be going in the config file as parameter to support those who want to stick to the real life limitations.
  7. Displaying UTC time on the INIT page.
  8. ILS frequencies are added correctly for airports with add-on sceneries.
  9. Fully qualified debug file name can be defined in the config file.
  10. Storing only live flight plan points into the flight plan file (no garbage points at the end of each FP).
Supported FMS packages
  1. PT proprietary package (no updates are planned)
  2. EADT KLN 90B from Navigraph
  3. PSS Airbus/Boeing/Dash from Navigraph
  4. vasFMC Flight Management from Navigraph
Definition of the FMS package in the config file

Define the FMS package you have installed in the KLN90B.CNF configuration file including the package identifier number and the path to the package.

[KLN90B]
NAVDATA=4 ; Navigation data package number (0-4)
; 0: no external navigation database
; 1: traditional PTT database (no transitions)
; 2: "EADT KLN 90B" pack
; 3: "PSS Airbus/Boeing/Dash" pack
; 4: "vasFMC Flight Management" pack
NAVDIR=D:\SIM\FSX\KLN90B\DB\VASFMC ; Navigation data directory

Please document any bugs and suggestions.

Gabor
 
Last edited:
Thank you. Downloading.

Are you going to add the support for the 3d buttons in the VC?
 
Great work! Having looked at that SID/STAR code, it was such a terrific tangle I was seriously contemplating starting over with it. But you just waded in there and fixed it.

I'll be downloading your update soon.

If I had time I'd work on the screen-only version that's controlled by Lvars so it can be placed in with a 3D model. Now that the SID/STAR mess is fixed that's probably a good next step to move in.

But at the moment, for the next few months at least, I have my plate full of other FS code.
 
I'm testing it in FSX:SE When i press the enter button, KLN crash FSX.

Nombre del evento de problema: APPCRASH
Nombre de la aplicación: fsx.exe
Versión de la aplicación: 10.0.62615.0
Marca de tiempo de la aplicación: 559f9a9a
Nombre del módulo con errores: ntdll.dll
Versión del módulo con errores: 6.1.7601.18933
Marca de tiempo del módulo con errores: 55a69e20
Código de excepción: c0000005
Desplazamiento de excepción: 000331a5
Versión del sistema operativo: 6.1.7601.2.1.0.256.49
Id. de configuración regional: 3082
Información adicional 1: 0a9e
Información adicional 2: 0a9e372d3b4ad19135b953a78882e789
Información adicional 3: 0a9e
Información adicional 4: 0a9e372d3b4ad19135b953a78882e789

Conf file:
[INTERFACE]
KOHLSMAN=1 ; Do we read the Altimeter settings?
APHDG=1 ; Do we drive the AP heading in HDG mode with NAV/GPS on GPS?
OBSIN=0 ; Do we read the NAV1 OBS setting?
OBSOUT=0 ; Can we set the NAV1 OBS setting?
AIRDATA=1 ; Can we read air data from the interface?
FUEL=1 ; Can we read fuel data from the interface?

[KLN90B]
FONT=0 ; 0=Lucida Console (default) 1=Terminus (must be installed on box)
NAVDATA=0 ; Navigation data package number (0-4)
; 0: no external navigation database
; 1: traditional PTT database (no transitions)
; 2: "EADT KLN 90B" pack
; 3: "PSS Airbus/Boeing/Dash" pack
; 4: "vasFMC Flight Management" pack
NAVDIR=D:\SIM\FSX\KLN90B\DB\VASFMC ; Navigation data directory
RUNWAYS=0 ; 0=load only hard surface runways, 1=all runways
ILSFREQ=1 ; 0=do not load ILS frequency data, 1=load ILS frequencies
TC=170754
TB=986895

[DEBUG]
LOGFNAME=E:\Steam\steamapps\common\FSX\KLN90B\debug.dat ; Debug file name. Comment out if no debug is needed.
 
Last edited:
You must log in or register to reply here.
Back
Top