Jump to content

tschuh00

Frozen-Inactivity
  • Content Count

    19
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

1 Neutral

Profile Information

  • Gender
    Male

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No
  1. Thanks so much IFRGuy for the detailed steps. This worked exactly as outlined!!!
  2. Are there any tricks to introducing some engine sound variability with throttle settings? I am finding that the engine sound is basically a constant pitch and volume regardless of power settings. At idle power settings there is some difference, but once increased beyond idle, the sound does not vary with power settings. I would expect, as is the case in the real Seneca, there to be a relative linear sound change with power setting.
  3. That helps thanks. I'll research the Aspen gauge some more. In the meantime, according to the SDK, the HSI CDI Needle value ranges from +/- 127. I'm seeing values more like 12700.00 which is 100 times the SDK specified range. Any thoughts on why that is?
  4. Your comment about the problem being with the Aspen is almost certainly correct. Unfortunately the author of that tool seems to have gotten out of the business, and the gauge is no longer supported. Furthermore, it's the only such gauge that I've been able to find in the marketplace that I can add to my Carenado Seneca. And so I am trying to get the best emulation possible until a new and improved version comes from another author. With that in mind, do you happen to have any further information regarding the fields that your debug tools is passing back. Of particular interest is the "HSI CDI Needle (Percenet)" field on page 3. HSI Data. I am typically seeing numbers like 12700.00. How to I interpret these numbers? Do they have any relationship to HSI deflection? Being a percentage field, I would expect them to be something like 0 - 100, correlating to centered needle through full-scale deflection at 100%.
  5. Thanks that did the trick, debugger is working now, thank you! I am going to review the data being passed now and see what's going on with the LDI and CDI/HSI discrepancies.
  6. Yes the gauge is in the Reality XP/Gauges folder. I am running on FSX. So based on your reply I moved the Debug sub-folder (along with its contents) to the FSX/Gauges folder and retried. The pop-up window is still blank. In the mean time I also tried changing the HSI Lateral Sensitivity slider from 1 to 0.1 in the GNS v2 settings. This had positive results. The LDI needle now much more closely matches the CDI needle. They are not identical (should be) but they are much closer. It is also interesting that the LDI gets more sensitive as the airplane approaches the runway threshold (as it should) whereas the CDI maintains a consistent sensitivity throughout the approach (it should scale down the closer it gets to the threshold until it gets to maximum sensitivity at the threshold at which point a full-scale deflection should be 350' either side of center. So it would be very helpful to use the aforementioned debug tool to see what is being passed.
  7. Thank you for this additional information. I added the gauge to my panel.cfg file. When I bring up the new pop-up window all I get is a blank / black screen. Should I be seeing the data being output from the GNS v2?
  8. I have the GNS530 V2 running in FSX in the Carenado Seneca V. It is interfaced to the f1 Aspen EFD1000 which has the Attitude Display on the top half of the instrument and the Navigational Display on the bottom half of the instrument. The Attitude Display includes a "Lateral Deviation Indicator (LDI)" and the Navigation Display includes a "Course Deviation Indicator(CDI)". And they both display a Glide Slope Indicator. When flying an LPV approach, presumably the LDI and CDI should be displaying the same relative deviation. However, the LDI is way more sensitive than the CDI. In other words, when the CDI is barely indicating one dot of deflection, the LDI shows an off-scale deflection. Is there a setting that I need be updating in the 530 v2 configuration so that the same data is being passed to these two indicators?
  9. Understood, and thanks for your reply. Not having the GMA340 is certainly not a big deal. I really miss the King-like autopilot panel though. But since my original post I did some additional research and ran across and started playing around with "Air Manager" product and it has a King-Like autopilot, so I should be okay for now. And on a side note - I really like your GNS v2 product. It does an excellent job of emulating the real thing, including LPV approaches!
  10. The original version of the Reality XP 530 product included a combination GMA340 audio panel and King-like autopilot panel. I don't see that panel in v2. Is it still available? The King-like autopilot panel was nice for those of us that use the King autopilot rather than the STEC.
  11. Bert - I realize this is an old thread. I was just wondering if this file is still needed, and/or needs to be changed when upgrading to RXP v2.
  12. I have tried this, and you are correct, the new RXP gauge is installed. However, I have found that the new 530 no longer functions correctly. Specifically, tuning an ILS procedure into the 530 and switching the CDI to VLOC mode no longer seems to send the correct signal to the HSI. The 530 recognizes the corresponding ILS signal. But on the HSI, the ILS vertical and horizontal guidance is not displayed. In fact, the HSI flags as if it is not receiving a valid signal. Is anyone else encountering this issue? RealityXP has said they believe the Carenado Seneca is not correctly processing the input signal.
  13. Do more detailed definitions of the various GNS settings exist anywhere? I've looked at the User's Manual, but it doesn't go into much detail. After successfully testing the LPV approach, I went back to test an ILS, and am running into problems. Specifically, when selecting an ILS procedure, and tuning the corresponding ILS frequency into the 530 V2, and setting the CDI to LOC mode, neither the localizer nor the glideslope are displaying on the Aspen, or G500/600 for that matter. When in GPS mode (not the correct mode for an ILS approach), the localizer appears on the Aspen, but still no glideslope. I'm sure this most likely requires changing one or more of the aforementioned settings. But with no further definition, and essentially 128 possible combinations of on/off for each of them, I was hoping someone might be able to point me in the right direction.
  14. That did it, thank you for the suggestion. Actually, while I was there, I set "Connect HSI/CRS output" and "Connect HSI/OBS Input" as well. So somewhere in that combination, the glideslope is now appearing again. Thank you!
  15. I have been a long-time, satisfied user of the original RXP 530. I use it within FSX in combination with the Carenado Seneca V and the Flight1 Aspen gauge pack. This combination has done a nice job of emulating the actual setup in my Seneca, with only a few minor differences. I just purchased and upgraded to the latest 530 v2 and have begun testing. My initial testing resulted in some weird problems, like not accurately tracking to a fix. But after updating to a more current worldwide.bin file, that problem went away. But now I have another problem. Officially speaking, the Aspen PFD is not able to fly an LPV approach. That's the official answer. The problem is that the Aspen PFD is not programmed to display the glideslope indicator when flying an RNAV approach. It only appears when flying an ILS approach. On the old version of the RXP 530, there was a very simple work-around. If you simply changed the CDI on the ASPEN PFD from GPS to LOC1, the Glideslope would appear. However, with the 530 V2, this workaround no longer functions. In other words, even with the CDI set to LOC1, the glideslope indicator does not appear. Any ideas on what may have changed with the 530 V2 that caused this workaround to no longer function? Tom
×
×
  • Create New...