Bankrupt
-
The KAP 140 does not support a flight director, but since I've been seeing many people ask about it, I might add one that is optionally toggleable on the tablet. That way I hopefully won't get too many complaints about it being unrealistic in the other direction. I'm glad you're enjoying it
-
The KAP 140 does not support a flight director, but since I've been seeing many people ask about it, I might add one that is optionally toggleable on the tablet. That way I hopefully won't get too many complaints about it being unrealistic in the other direction. I'm glad you're enjoying it
-
The KAP 140 does not support a flight director, but since I've been seeing many people ask about it, I might add one that is optionally toggleable on the tablet. That way I hopefully won't get too many complaints about it being unrealistic in the other direction. I'm glad you're enjoying it
@Black-Square said in Bankrupt:
The KAP 140 does not support a flight director, but since I've been seeing many people ask about it, I might add one that is optionally toggleable on the tablet. That way I hopefully won't get too many complaints about it being unrealistic in the other direction. I'm glad you're enjoying it
Hi Nick, congratulations on the 208.
I fly with a KAP140 IRL and it's fine when you get used to it. The only thing I'm seeing in the sim that differs is when you engage the autopilot IRL it engages 'rol' and 'vs' mode (at whatever the vs was when engaged). As I understand it the KAP 140 is rate based and does not have a 'pitch' function.
I hope that's of some use.
Cheers
-
@Black-Square said in Bankrupt:
The KAP 140 does not support a flight director, but since I've been seeing many people ask about it, I might add one that is optionally toggleable on the tablet. That way I hopefully won't get too many complaints about it being unrealistic in the other direction. I'm glad you're enjoying it
Hi Nick, congratulations on the 208.
I fly with a KAP140 IRL and it's fine when you get used to it. The only thing I'm seeing in the sim that differs is when you engage the autopilot IRL it engages 'rol' and 'vs' mode (at whatever the vs was when engaged). As I understand it the KAP 140 is rate based and does not have a 'pitch' function.
I hope that's of some use.
Cheers
@slod I just wanted to let you know that I was working on this last night, and share the post I made in another thread on the subject:
I think I was able to arrive at the optimal solution with only some small edits to the code. I also improved some other small things in the KAP140 while I was there. The only thing I'm not sure about relates to the behavior of the real world unit. If you engage the autopilot when you are already within 200ft of your selected altitude, the vertical speed will be zero, and it will capture the selected altitude. All things considered, this is a very small tradeoff in my eyes, compared to what is sometimes required to circumvent the native autopilot. It's always amazing when you implement some of these small things, and you can immediately feel how much more intuitive they are. Thanks, guys!
EDIT: The capability to display "PIT" mode still resides in my KAP 140 code, but you should not see it during normal operation. I've left it there more as a debugging tool, since errant autopilot modes are my best tool for diagnosing GPS addon issues.
-
@slod I just wanted to let you know that I was working on this last night, and share the post I made in another thread on the subject:
I think I was able to arrive at the optimal solution with only some small edits to the code. I also improved some other small things in the KAP140 while I was there. The only thing I'm not sure about relates to the behavior of the real world unit. If you engage the autopilot when you are already within 200ft of your selected altitude, the vertical speed will be zero, and it will capture the selected altitude. All things considered, this is a very small tradeoff in my eyes, compared to what is sometimes required to circumvent the native autopilot. It's always amazing when you implement some of these small things, and you can immediately feel how much more intuitive they are. Thanks, guys!
EDIT: The capability to display "PIT" mode still resides in my KAP 140 code, but you should not see it during normal operation. I've left it there more as a debugging tool, since errant autopilot modes are my best tool for diagnosing GPS addon issues.
@Black-Square said in Bankrupt:
@slod I just wanted to let you know that I was working on this last night, and share the post I made in another thread on the subject:
I think I was able to arrive at the optimal solution with only some small edits to the code. I also improved some other small things in the KAP140 while I was there. The only thing I'm not sure about relates to the behavior of the real world unit. If you engage the autopilot when you are already within 200ft of your selected altitude, the vertical speed will be zero, and it will capture the selected altitude. All things considered, this is a very small tradeoff in my eyes, compared to what is sometimes required to circumvent the native autopilot. It's always amazing when you implement some of these small things, and you can immediately feel how much more intuitive they are. Thanks, guys!
EDIT: The capability to display "PIT" mode still resides in my KAP 140 code, but you should not see it during normal operation. I've left it there more as a debugging tool, since errant autopilot modes are my best tool for diagnosing GPS addon issues.
Thanks Nick, I did see that. I can’t believe how fast you work! I was only trying to help - certainly not complaining. Next time I’m flying I’ll try engaging within 200ft of target and see what happens.
Cheers
-
@Black-Square said in Bankrupt:
@slod I just wanted to let you know that I was working on this last night, and share the post I made in another thread on the subject:
I think I was able to arrive at the optimal solution with only some small edits to the code. I also improved some other small things in the KAP140 while I was there. The only thing I'm not sure about relates to the behavior of the real world unit. If you engage the autopilot when you are already within 200ft of your selected altitude, the vertical speed will be zero, and it will capture the selected altitude. All things considered, this is a very small tradeoff in my eyes, compared to what is sometimes required to circumvent the native autopilot. It's always amazing when you implement some of these small things, and you can immediately feel how much more intuitive they are. Thanks, guys!
EDIT: The capability to display "PIT" mode still resides in my KAP 140 code, but you should not see it during normal operation. I've left it there more as a debugging tool, since errant autopilot modes are my best tool for diagnosing GPS addon issues.
Thanks Nick, I did see that. I can’t believe how fast you work! I was only trying to help - certainly not complaining. Next time I’m flying I’ll try engaging within 200ft of target and see what happens.
Cheers
@slod That would be great. I sure hope that's the real world behavior, because trying to circumvent that behavior would open a can of worms. And here I thought I was slow to this one... I took at least a few hours off after the release just working on Twin Commander minutiae to clear my head.
-
@slod That would be great. I sure hope that's the real world behavior, because trying to circumvent that behavior would open a can of worms. And here I thought I was slow to this one... I took at least a few hours off after the release just working on Twin Commander minutiae to clear my head.
@Black-Square said in Bankrupt:
@slod That would be great. I sure hope that's the real world behavior, because trying to circumvent that behavior would open a can of worms. And here I thought I was slow to this one... I took at least a few hours off after the release just working on Twin Commander minutiae to clear my head.
Hi Nick, thinking about it , when you first engage the autopilot you have the manually press the 'arm' button, so using your 200ft example you'd probably blow through your selected altitude if you weren't really quick! One quirk of the unit is that when in 'alt hold' if you select a new altitude and enter 'vs' mode the unit automatically 'arms'. I'm not sure if that happens when selecting a new altitude or when entering 'vs' mode but I'll check next time for the fun of it.
You're proposed work around is more than enough though!
You can see why anyone with enough cash goes for a digital autopilot!
Cheers
