-
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.
PT KLN90B Thread
- Thread starter Dutch
- Start date
- Messages
- 25
- Country
Tushka, you are the man!
The SID/STAR code looks like a crash waiting to happen. I think I am going to temporarily disable access to the APT 7 page until we can get it fixed. It doesn't put the waypoints in the right place half the time anyway.
Dutch
Yes, I know. The SID/STARS made a lot of crashes so often that I never bothered to use them, and the waypoints are occasionally never in the right place and many times some waypoints are missing. They're incomplete, could be with the fact that some STAR have separate "STAR" and a separate "transition", which the KLN can't work out. The best you can do is to manually add the waypoint coordinates while you're flying, at least you will know they're accurate.
- Messages
- 158
- Country
We'll get that sorted out, but right now I'm dealing with strangeness at the very core of the code. Here's what.
I'm tracking down the situation where it' spamming MSGs at me to set the OBS. What it's actually doing is switching the "active leg" all around as I fly. I found out why, annnnnnnd:
This is the real reason why it gets "lost" so often.
On every cycle, it re-calculates what the "active leg" is. It defines the current active leg as : the closest waypoint in the direction the airplane is currently pointing that is not the nearest one to you.
For example, in testing I have a flight plan whose first leg carries me on a course of 101 degrees. When I line up on runway 34, I should be on leg 1, right? Wrong, according to our current KLN logic. It so happens that on runway 34 I am pointing in the direction of the 4th waypoint in my flight plan. So it makes that waypoint my active leg! If I rotate my aircraft around on the runway, I can actually see it changing the active waypoints, based on the direction I'm facing !!! The mind boggles.
This works, in practice, only if you ignore what the KLN is telling you until you are on course for your first waypoint. Then, it will actually fly to it, and change the waypoint to the next leg based on this logic, and fly to that. As long as you manually get it on course, it may stay there, but using this logic if it ever wanders off for any reason (like, say, turning to a new heading) it may find a waypoint out there that it thinks is the new leg just because it's pointing to it -- and start flying towards that!
This logic only works when the waypoints are in a more or less straight line. SIDS and STARS often zigzag. No wonder it can't follow them!
The correct logic is: the active leg is the first leg and it remains the first leg until 1) you manually change it, or 2) you get close enough to the destination of that leg to cause it to automatically sequence to the next leg. And so on to the last leg.
We're going to fix that, right now.
Dutch
I'm tracking down the situation where it' spamming MSGs at me to set the OBS. What it's actually doing is switching the "active leg" all around as I fly. I found out why, annnnnnnd:
This is the real reason why it gets "lost" so often.
On every cycle, it re-calculates what the "active leg" is. It defines the current active leg as : the closest waypoint in the direction the airplane is currently pointing that is not the nearest one to you.
For example, in testing I have a flight plan whose first leg carries me on a course of 101 degrees. When I line up on runway 34, I should be on leg 1, right? Wrong, according to our current KLN logic. It so happens that on runway 34 I am pointing in the direction of the 4th waypoint in my flight plan. So it makes that waypoint my active leg! If I rotate my aircraft around on the runway, I can actually see it changing the active waypoints, based on the direction I'm facing !!! The mind boggles.
This works, in practice, only if you ignore what the KLN is telling you until you are on course for your first waypoint. Then, it will actually fly to it, and change the waypoint to the next leg based on this logic, and fly to that. As long as you manually get it on course, it may stay there, but using this logic if it ever wanders off for any reason (like, say, turning to a new heading) it may find a waypoint out there that it thinks is the new leg just because it's pointing to it -- and start flying towards that!
This logic only works when the waypoints are in a more or less straight line. SIDS and STARS often zigzag. No wonder it can't follow them!
The correct logic is: the active leg is the first leg and it remains the first leg until 1) you manually change it, or 2) you get close enough to the destination of that leg to cause it to automatically sequence to the next leg. And so on to the last leg.
We're going to fix that, right now.
Dutch
Last edited:
- Messages
- 158
- Country
All right, we have 0.074B ready. This is a big step forward, as you can clearly see from the different look! Thanks, Tushka. Same link address as before.
Here's the change log:
// 150118 CEO 0.074B Indicated Altitude and Kohlsman setting are now read from the air data interface
// 150119 CEO 0.074B Fixed bug where intersections in the MSFS flight plan weren't copied into FPL0.
// 150119 CEO 0.074B Changed waypoint-sequencing logic to reproduce what the real KLN90B does.
// 150119 CEO 0.074B Changed background image to a higher resolution gray bezel.
// 150119 CEO 0.074B Revised course intercept logic to be more aggressive in getting back on course.
This version will start up a little differently because we are starting to interface the KLN90 to the aircraft's systems. We are picking up the Altimeter setting, so it's no longer necessary to enter (or skip over) the BARO setting on the first page. So now, it will start on APPROVE? and you can just press ENT to proceed. You'll note that now it will show the current indicated altitude and baro setting from the altimeter in your airplane. Auto-magically. This was a real option in the KLN90B but since it took an expensive interface few used it. In FSX, this interface is cheap! If you want the old method, put KOHLSMAN=0 in the new [INTERFACE] section of your kln90b.cnf file. (But changing that baro has no effect on the operation of our simulated KLN90 and never did as far as I know.)
The following only applies to the option to drive the default AP heading from the KLN90. It does not yet apply to the ABSU of the TU-154.
The other major change (and this may take some testing on everyone's part) is the smarter behavior flying the course. It will start on waypoint 1 and fly to 2, then sequence to 3, and on like that as it passes each one. The active leg will only sequence to the next when you get within about a mile of its destination waypoint. The only way to change the sequencing is to select a new waypoint manually. This is done in the correct KLN90 way. If you're on the SUPER NAV 5 page, pull out the right knob and select the waypoint you want, then press DTO twice. Or, you can put FPL0 on the left side, select CRSR, go to the waypoint you want, then press DTO again twice.
If you are off course and the KLN90 is flying your airplane by driving the AP HDG, it will direct you back on course by a 20-degree course correction until you intercept the DTK course, then it will proceed to the next waypoint normally. This will not happen if you are within 10 miles of the destination waypoint for this leg, or you are more than 90 degrees off course. In either of those cases it will fly direct to the destination waypoint, then resume its normal course sequencing.
We are getting there. The next release will probably have sound and be in a proper installer.
NOTE: I highly recommend not trying to use the SID/STAR page. We will fix it, but for now it is crash-prone.
Dutch
Current contents of my KLN90B.CNF file:
[INTERFACE]
KOHLSMAN=1
[KLN90B]
FONT=1
EXTINTDB=1
TC=373253
TB=1381653
Here's the change log:
// 150118 CEO 0.074B Indicated Altitude and Kohlsman setting are now read from the air data interface
// 150119 CEO 0.074B Fixed bug where intersections in the MSFS flight plan weren't copied into FPL0.
// 150119 CEO 0.074B Changed waypoint-sequencing logic to reproduce what the real KLN90B does.
// 150119 CEO 0.074B Changed background image to a higher resolution gray bezel.
// 150119 CEO 0.074B Revised course intercept logic to be more aggressive in getting back on course.
This version will start up a little differently because we are starting to interface the KLN90 to the aircraft's systems. We are picking up the Altimeter setting, so it's no longer necessary to enter (or skip over) the BARO setting on the first page. So now, it will start on APPROVE? and you can just press ENT to proceed. You'll note that now it will show the current indicated altitude and baro setting from the altimeter in your airplane. Auto-magically. This was a real option in the KLN90B but since it took an expensive interface few used it. In FSX, this interface is cheap! If you want the old method, put KOHLSMAN=0 in the new [INTERFACE] section of your kln90b.cnf file. (But changing that baro has no effect on the operation of our simulated KLN90 and never did as far as I know.)
The following only applies to the option to drive the default AP heading from the KLN90. It does not yet apply to the ABSU of the TU-154.
The other major change (and this may take some testing on everyone's part) is the smarter behavior flying the course. It will start on waypoint 1 and fly to 2, then sequence to 3, and on like that as it passes each one. The active leg will only sequence to the next when you get within about a mile of its destination waypoint. The only way to change the sequencing is to select a new waypoint manually. This is done in the correct KLN90 way. If you're on the SUPER NAV 5 page, pull out the right knob and select the waypoint you want, then press DTO twice. Or, you can put FPL0 on the left side, select CRSR, go to the waypoint you want, then press DTO again twice.
If you are off course and the KLN90 is flying your airplane by driving the AP HDG, it will direct you back on course by a 20-degree course correction until you intercept the DTK course, then it will proceed to the next waypoint normally. This will not happen if you are within 10 miles of the destination waypoint for this leg, or you are more than 90 degrees off course. In either of those cases it will fly direct to the destination waypoint, then resume its normal course sequencing.
We are getting there. The next release will probably have sound and be in a proper installer.
NOTE: I highly recommend not trying to use the SID/STAR page. We will fix it, but for now it is crash-prone.
Dutch
Current contents of my KLN90B.CNF file:
[INTERFACE]
KOHLSMAN=1
[KLN90B]
FONT=1
EXTINTDB=1
TC=373253
TB=1381653
- Messages
- 3,278
- Country
great, I have the Tu 154 B as a great addon for fsx.
- Messages
- 158
- Country
This is likely the last beta I'll announce here. We probably need a new home, or a new thread. Maybe in the Showroom here.
Beta 0.075B uploaded, available at the same link. The white borders are gone. You can now access ILS frequencies on the APT 5 page, previously the unused REMARKS page. Also, you have the option to include all runways not just the hard surface ones. Several more bugs are fixed and the KLN90B.CNF file is expanded in function. Here's the change log:
// 150120 CEO 0.075B ILS frequencies added in place of previously unused APT 5.
// 150120 CEO 0.075B Now supports both HRD and SFT runway types.
// 150120 CEO 0.075B corrected a couple more cases of string overflow on APT pages.
// 150120 CEO 0.075B Added options to be able to control AP HDG mode, ILS freq, and soft runways.
// 150120 CEO 0.075B Implemented the MSG-ENT shortcut to the nearest airport pages.
Here are the current contents of my KLN90B.CNF file. All the settings here are default:
Beta 0.075B uploaded, available at the same link. The white borders are gone. You can now access ILS frequencies on the APT 5 page, previously the unused REMARKS page. Also, you have the option to include all runways not just the hard surface ones. Several more bugs are fixed and the KLN90B.CNF file is expanded in function. Here's the change log:
// 150120 CEO 0.075B ILS frequencies added in place of previously unused APT 5.
// 150120 CEO 0.075B Now supports both HRD and SFT runway types.
// 150120 CEO 0.075B corrected a couple more cases of string overflow on APT pages.
// 150120 CEO 0.075B Added options to be able to control AP HDG mode, ILS freq, and soft runways.
// 150120 CEO 0.075B Implemented the MSG-ENT shortcut to the nearest airport pages.
Here are the current contents of my KLN90B.CNF file. All the settings here are default:
Code:
; when you enable the RUNWAYS or ILSFREQ options for the 1st time you will need to rebuild your database to see them.
[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=1 ; 0=Lucida Console (default) 1=Terminus (must be installed on box)
EXTINTDB=1 ; Use separate 'Isec.txt' and sidstars folder in place of MSFS INTs?
RUNWAYS=1 ; 0=load only hard surface runways, 1=all runways
ILSFREQ=1 ; 0=do not load ILS frequency data, 1=load ILS frequencies
; Do not modify these and leave them at the end - they record the brightness setting
TC=441350
TB=1513239- Messages
- 25
- Country
I'm currently on a flight to Petropavlovsk-Kamchatskiy with the past beta (not the one you just uploaded), it is still connecting to ABSU fortunately although some Russians at avsim.su are having problems.
I agree the showroom would be a better place to announce, will gather more attention. It seems you are working really fast : )
I agree the showroom would be a better place to announce, will gather more attention. It seems you are working really fast : )
euroastar350
Resource contributor
- Messages
- 862
- Country
Is there a way to have the GPS display separate from the background? Would be very useful for developers like myself since I can build the base and the polygon on which the GPS will be displayed.
- Messages
- 158
- Country
I can't understand the problems with the ABSU. Those four variables are still being exported just like always. That hasn't changed. Perhaps they aren't properly connecting it using the controls in the TU-154?
You should use the latest upload. I was on a flight in a 727 using the previous release and it took off 30 degrees in the wrong direction after passing a waypoint. I fixed that, but 0.74B has that potential problem. That's why I uploaded this one fast
There is still a problem with re-starting the flight plan after a waypoint is skipped using DTO. (But that never used to work either.)
I'll announce the next release in the Showroom. It'll probably be a few days. I think 0.075B will hold out a while and I have other things I need to tend to.
Dutch
You should use the latest upload. I was on a flight in a 727 using the previous release and it took off 30 degrees in the wrong direction after passing a waypoint. I fixed that, but 0.74B has that potential problem. That's why I uploaded this one fast
There is still a problem with re-starting the flight plan after a waypoint is skipped using DTO. (But that never used to work either.)
I'll announce the next release in the Showroom. It'll probably be a few days. I think 0.075B will hold out a while and I have other things I need to tend to.
Dutch
- Messages
- 25
- Country
Probably the problems don't have to do with the connection between the ABSU and KLN at all, just a combination of an outdated autopilot along with a GPS on beta. ABSU is not up to modern standards anymore in real life either. It does work however, just with unusual tracking charasterictics. I also experienced issues similar to yours and I'm glad it's fixed. When you talk about 727, do you mean the captain sim 727? I've always wanted to fly that plane but it uses only VOR and NDB navigation, which unfortunately many airports and routes today are RNAV only.
Will wait for the next release, we all have things to do, no rush
Will wait for the next release, we all have things to do, no rush
- Messages
- 158
- Country
Yes, I have the Captain Sim 727. It's a good add-on and I fly it all the time. However, in order to be authentic you need to install quite a number of user-developed fixes that are in the Captain Sim 727 forum. Out of the box it's a bit flawed and they've never fixed it and probably never will. But the users stepped in and did it.
The KLN90B works great with it. When the AP is in heading mode the KLN will drive it to where you need to go. The 727 becomes RNAV-capable!
Speaking of which, I'm spending most of my time right now working on the core nav functions. It's already flying much more exactly on course now that the wind correction is factored in properly. I really want it to track almost as closely as the default GPS does on its course. Funny that the course worked out by the KLN isn't exactly what the default GPS figures. But it's close. Now to nail the intercept mode and it's ready to go I think. It really should and must fly accurately the course that's plotted. Even if the airplane makes sloppy wide turns, it should get you back on course no matter where you are.
Dutch
The KLN90B works great with it. When the AP is in heading mode the KLN will drive it to where you need to go. The 727 becomes RNAV-capable!
Speaking of which, I'm spending most of my time right now working on the core nav functions. It's already flying much more exactly on course now that the wind correction is factored in properly. I really want it to track almost as closely as the default GPS does on its course. Funny that the course worked out by the KLN isn't exactly what the default GPS figures. But it's close. Now to nail the intercept mode and it's ready to go I think. It really should and must fly accurately the course that's plotted. Even if the airplane makes sloppy wide turns, it should get you back on course no matter where you are.
Dutch
- Messages
- 158
- Country
As of today 0.076B is released. This is the one where we make the transition to the showroom. It has significant enhancements.
The previously announced link will not get you this new version. It's not just the DLL any more but is packaged in an installer because now there's much more to the gauge than just the DLL. There's documentation and sounds, mainly. Those will be in your KLN90B folder when you install this.
Check out the thread in the Showroom with KLN90B for FSX/Prepar3d for the new link.
Dutch
The previously announced link will not get you this new version. It's not just the DLL any more but is packaged in an installer because now there's much more to the gauge than just the DLL. There's documentation and sounds, mainly. Those will be in your KLN90B folder when you install this.
Check out the thread in the Showroom with KLN90B for FSX/Prepar3d for the new link.
Dutch