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

IMPORTANT INFORMATION!

Before starting the new release 0.77B, delete the PTT_XXX.DAT files in the KLN90B folder and let the program to re-generate them on startup!

I optimized some memory eating code of the eralier versions and store the PTT_APT.DAT (Airports) file differently. The new program version crashes if reads the old file. Delete the *.DAT files before starting the new version first time.

I add this to the documentation and to my post above about the new release.

(this happens if we don't have a clean installer)
 
Last edited:
Crashed again. I deleted all .dat files. When KLN finish to rebuild all navdata and turn to display the current position it crash.
 
Dutch said:
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.
Click to expand...

No need for L vars. You can use a screen only version and hex key events.
 
ce_zeta said:
Crashed again. I deleted all .dat files. When KLN finish to rebuild all navdata and turn to display the current position it crash.
Click to expand...

Hi ce_zeta,

I removed KLN90B and went through the installation process that I defined in the doc.

  • I installed Dutch's v0.76B
  • I deleted al *.PTT files
  • I set NAVDATA=0 in the config file as you had done
  • I copied the DLL from my v0.77B package.

It did not crash for me, though I retried several times.

I am using Windows 8.1 and FSX not SE version. I will send you a DLL version with more detailed logging if the problem persists, but at first wait for some others to start up the GPS on their system.

Gabor
 
Thanks Gabor. I tested the gauge with navdata = 0 and 1 with same results.

I will test it in a clean gauge installation. I am using W7 64 bits with FSX:SE (I have all simconnect installed)

Yeap, we need more feedback from other users.
 
ce_zeta said:
Thanks Gabor. I tested the gauge with navdata = 0 and 1 with same results.

I will test it in a clean gauge installation. I am using W7 64 bits with FSX:SE (I have all simconnect installed)

Yeap, we need more feedback from other users.
Click to expand...

I made it crashed now with your exact config file. So there will be a solution soon. I am checking the source of the crash.
 
Gabor hrasko said:
I made it crashed now with your exact config file. So there will be a solution soon. I am checking the source of the crash.
Click to expand...

I AM confused now. It is crashing nw for me all the time. I can't make it work. Unfortunatelly I have to stop debugginh it now and maybe I won't have time for some days. I will try my bests anyhow.
 
Strange. I reinstalled the KLN and now it's working.

[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=1 ; 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=D:\SIM\FSX\KLN90B\debug.dat ; Debug file name. Comment out if no debug is needed.

Set NAVDATA to 1 and using this navdata = crash
Deleting all .DATs = working
 
Last edited:
I will work on this mystical crash issue some days later as I hate if something like this happens. However I received news about one more short positive preliminary test from one of my Tu154 fan friends. I even received some photos about leaving LHBP on BADOV1D SID :)

Tu154-gps-test.jpg
 
Hi all, i have a little question... if i want to use the kln with Autopilot programed in XML... is possible connect directly or i need use something else (like a conversor)? thank you in advance
 
I nearly finshed my panel working on my U206G Soloy. Many users worldwide ask for your KLN90B in my VC and I did it. Lightmaps aren´t set, don´t wonder.

23556915fa.jpg


Is there a possibility to get the modeldef XML-script of the knops? Perpaps I could do a short tutorial for developers. What do you think?

Thomas
 
Hello Gabor,
first of all, thank you for your effort. This gauge looks very good and I like it. But I have some problem with crashes. Reporting:

I use Win7 64bit, FSX Steam Edition. UAC turned completely of. I installed the version from Dutch and copied your files over it. After installing vasFMC AIRAC 1513 and updating default FSX navaids/fixes using this excelent tool (World Navaids Package from this guy: http://www.aero.sors.fr/navaids3.html ) I deleted all DAT files and generated new ones. Everything seems to be working, but when I attempt to load STAR into an empty FPL, it crashes. It also crashes when searching in right VOR page (this is very easy to replicate). Attached I am sending you my screenshots with marks of what I clicked. I am also attaching my config file. Those crashes leave no report in the debug file.

If I could help you with finding the bug, you can send me some version which logs more information, or I can give you a Teamviewer remote access to my computer if you prefer to test it on your own.

Best regards from Prague,
Pavel Brodsky
KLN90_bug_VOR.PNG
KLN90_bug2_VOR.PNG
KLN90_bug3_load_STAR.PNG


[INTERFACE]
KOHLSMAN=1 ; Do we read the Altimeter settings?
APHDG=0 ; 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=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=C:\Program Files (x86)\Steam\steamapps\common\FSX\KLN90B\NavData ; Navigation data directory
RUNWAYS=1 ; 0=load only hard surface runways, 1=all runways
ILSFREQ=1 ; 0=do not load ILS frequency data, 1=load ILS frequencies
TC=851724
TB=2302755

[DEBUG]
LOGFNAME=C:\Program Files (x86)\Steam\steamapps\common\FSX\KLN90B\debug.dat ; Debug file name. Comment out if no debug is needed.
 
Hi Gabor,

Thanks very much for your efforts with the KLN. But I also experience crashes. My setup:

- W7-64 bit. FSX boxed edition.
- Also installed Dutch's gauge and copied your gauge over his.
- I deleted all the .DAT files and let your gauge create new ones.

It usually crashes when I am selecting a STAR. Not always but often. For instance:

klncrash2.png


Here I had loaded a 27 point flightplan UUEE-EFRO. I had already selected a SID from UUEE. Then upon selecting the star at EFRO and clicking enter on "1 RWY21", it crashes.
But if I select a star at EFRO first, and then select a SID from UUEE, it doesn't crash and the SID and STAR are inserted into the flightplan normally.

There's something else strange going on. If I first select the STAR, it show all waypoints of the STAR and inserts them correctly:

klnstar2.png


But when I then go and select the SID from UUEE, and then come back and select the same STAR at EFRO again, it doesn't show the waypoints anymore, except the landing runway:

klnstar1.png


If you need more information or testing, let me know.

Robert-Jan

[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=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=C:\Flight Simulator X\KLN90B\DB\VASFMC\NavData ; Navigation data directory
RUNWAYS=1 ; 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=D:\temp\debug.dat ; Debug file name. Comment out if no debug is needed.
 
Robert, we found that it somehow depends on if the airport (UUEE or EFHK) is already inserted in the FPL as a waypoint or not. If you insert UUEE as a waypoint before loading STAR, it does not crash. If you load STAR witout having UUEE in the FPL, it crashes (or vice versa? Cant remember right now). Try that.

Pavel
 
I did have both UUEE and EFHK in the flightplan. It doesn't show this on the screenshots because when you have a flightplan loaded in FSX and you have FPL0 as the active left page, and you click 'ENT' on the KLN, it automatically reloads the FSX flightplan into the KLN, removing the SID or STAR that you just selected. So I had a different page on the left as the active page, namely FPL1.

Anyway, I now started off with a flightplan with just UUEE and EFRO as the two only waypoints. I then selected again a UUEE SID without problems:
klntest2.png


klntest3.png


Then I went on to select a STAR at EFRO. It didn't crash this time, but it didn't show any waypoints:

klntest5.png



klntest6.png


I took a look at the STAR in the navdata, and this STAR as in fact 2 waypoints.
Then I went on to try another STAR and it crashed when I clicked 'ENT', with the runway selected.

klntestcrash.png


Robert-Jan
 
Hello,

I have problems with the database (AIRAC) ... The GPS does not recognize vasFMC cycle, so I had to use this AIRAC, but would like to know how to use the latest navigation cycle... Thanks in advance.

P.D: I followed the tutorial in this post but it does not works.
 
You must log in or register to reply here.
Back
Top