AIR MANAGER

[SurferTim]

I prefer the old type instruments. That is what I learned on in 1969. That is why this is a DHC-6-300+ rather than a -400.

I do have a glass panel planned for this display. The vertical linear type airspeed and altitude gauges are actually easier and less processor power hungry. No rotating except the artificial horizon..

Some of the glass panels aren't as effective at IFR. The B777-300 can't determine when you cross a VOR radial more than 45 degrees off your heading. The pointer disappears off the display. Not good on departure from KLAX, where you need to cross the SMO 160R before starting your turn and you are heading 250. You can't tell when to turn. I can with the old panel.

The only thing missing from the radar altimeter in the DHC-6-300 is an audible alarm when decision height (or minimum terrain clearance) is reached.
Mine will get that today. To stay with the old instruments, it will probably not be voice.

It already has the mods that let it use this heading controller.

This is the current version I use. It is a 200M download due to the large number of liveries. Somebody went to a lot of work making them, so I left them.
http://www.prolectron.com/flightgear/dhc6p.zip
I'll post when it has an audible warning for the radar altimeter.

[D-ECHO]

Then make the change above.
After this line in IDG-PA28/Nasal/stec55x.nas

Code: Select all

 var updateFast = maketimer(0.05, ITAF, ITAF.loopFast);

add the code above.

I know the code above does a bounce.
If one changes, it changes the other.
When the other changes, it changes the one, but it is the same value, so no listener triggered.
It is the cost of sharing information.

Hey SurferTim,
if you want I can add a property rule to the PA28 (assuming you are using the PA28 by now, not the IDG one anymore?) and include it in the repository, so you don't need to have that separate patch and won't face problems installing updated versions.

[SurferTim]

I don't fly the PA28, but Robertfm does, and he wanted to use this panel.
One of the PA28s did fine, the other didn't.
I fixed the one that didn't for him.
The fix is pretty straight-up code. I have a new version of the fix that works better.

Thanks for the help with the FGv2019.2.0 compile. It is working fine.
Did we get the download_and_compile.sh script fixed for future users?

This works on the DHC6 and can be modified to work with most aircraft.
Add this to the bottom of Nasal/systems.nas

Code: Select all

# SurferTim added

setlistener("/instrumentation/heading-indicator-real-dg/heading-bug-deg", func(test){
   setprop("/autopilot/settings/heading-bug-deg",test.getValue());
},0,0);

setlistener("/autopilot/settings/heading-bug-deg", func(test){
     setprop("/instrumentation/heading-indicator-real-dg/heading-bug-deg",test.getValue());
},0,0);

setlistener("/sim/signals/fdm-initialized", func(){
     setprop("/autopilot/settings/heading-bug-deg",getprop("/instrumentation/heading-indicator-real-dg/heading-bug-deg"))
},0,0);

[Robertfm]

Is it a simple process to fit Mark 7 GPWS in some like the PA28.

[Robertfm]

I don't fly the PA28, but Robertfm does, and he wanted to use this panel.
One of the PA28s did fine, the other didn't.
I fixed the one that didn't for him.
The fix is pretty straight-up code. I have a new version of the fix that works better.

Thanks for the help with the FGv2019.2.0 compile. It is working fine.
Did we get the download_and_compile.sh script fixed for future users?

This works on the DHC6 and can be modified to work with most aircraft.
Add this to the bottom of Nasal/systems.nas

Code: Select all

# SurferTim added

setlistener("/instrumentation/heading-indicator-real-dg/heading-bug-deg", func(test){
   setprop("/autopilot/settings/heading-bug-deg",test.getValue());
},0,0);

setlistener("/autopilot/settings/heading-bug-deg", func(test){
     setprop("/instrumentation/heading-indicator-real-dg/heading-bug-deg",test.getValue());
},0,0);

setlistener("/sim/signals/fdm-initialized", func(){
     setprop("/autopilot/settings/heading-bug-deg",getprop("/instrumentation/heading-indicator-real-dg/heading-bug-deg"))
},0,0);

Does the new version you mention stop the occasional flicker from the panel when the 'No Connection banner flashes momentarily. If so what is the new code.

[SurferTim]

The "NO CONNECTION" message flashes if you are not receiving at least 10 packets/second.
It will flash off and on when starting the sim, but once running, you shouldn't get that message.
If it is flickering, you are right at the limit.

This panel uses about 38% of my processor according to top.
FG uses a bunch too.
Put them together on the same machine, and you may have speed problems.

Edit: When I tried this on my Windows 10 box, it did not flicker, even when FG running on the same machine.

[Robertfm]

I will take a look at my system monitor although the FPS is usually stable according to FG's monitor @ 60

[SurferTim]

My FG was also at 60 fps. That would almost guarantee 30 packets/second.

I have a new version that has some minor mods, like a window on the gyrocompass that shows the exact heading in the center of the compass when you scroll over the knob.

I'll upload it once I check it today.

Edit: I have noticed lately when I'm around other aircraft that FG stutters (very jerky motion). That could cause that message.

There is a way to check the speed of the panel. With FG running, press and hold down the gyro heading bug '>' button.
If you are receiving 30 packets/second, the heading bug should change 30 degrees/second.
The number of degrees it changes in a second is your packet rate.

This does not reflect a test of only FlightGear. It is possible that FG is sending 30 packets/second, but the Python code is running so slow it isn't getting every packet. This is UDP.

[SurferTim]

Here is the latest version of Pirate's Panel. Note no v1 this time.
http://www.prolectron.com/flightgear/PiratesPanel.zip

[Robertfm]

My FG was also at 60 fps. That would almost guarantee 30 packets/second.

I have a new version that has some minor mods, like a window on the gyrocompass that shows the exact heading in the center of the compass when you scroll over the knob.

I'll upload it once I check it today.

Edit: I have noticed lately when I'm around other aircraft that FG stutters (very jerky motion). That could cause that message.

There is a way to check the speed of the panel. With FG running, press and hold down the gyro heading bug '>' button.
If you are receiving 30 packets/second, the heading bug should change 30 degrees/second.
The number of degrees it changes in a second is your packet rate.

This does not reflect a test of only FlightGear. It is possible that FG is sending 30 packets/second, but the Python code is running so slow it isn't getting every packet. This is UDP.

Checked in task manager and combine use of python and fg was slightly over 30% CPU & 19% GPU whilst flying. I will use your method after I down load new version of pirate.

[SurferTim]

OK. I checked the time on the packet send. It is taking about 33000us per iteration when connected. That is about 30 times per second.
It takes about 115000us per iteration when not connected. That is a little over a tenth of a second.
After some experimentation, I found it takes two iterations to update a value, so it should update at 15 degrees per second if you hold down the mouse button.

That is due to the listeners delay on the FG end.
If you and I did not need the listeners, it should update at 30 degrees/second.
Note I say "should".

[Robertfm]

Downloaded new pirate that makes life so much easier, big and bold. Thanks.

[SurferTim]

Good to hear.

Did you read my edit? If you are using an aircraft that you didn't need to modify with the listeners, you may get 30 degrees/second on the heading bug.
I think it is due to the listeners causing a one iteration delay in the FG machine.

[Robertfm]

I haven't tried it yet as I am flying I will do it when on the ground that way I can what happens.

[SurferTim]

I tried on both PA28s. One has the listeners, and the other doesn't.
It did not seem to make a difference. 15 degrees/second.