defyent

Okay, yes ultimately all our gauges are custom made with SimAvio. I've used the dataref editor to find all your datarefs, but im looking through the manual now as well.

Okay I see. I guess if the standard course selector could still drive the OBS function when "Connect to vor indicator" was disabled that would solve my issue. However I've found a work around which will give me all the functionality I need but it's going to require a bit code and a custom course Up/Down command that switches from the obs_mag to gps_course_degtm to nav1_course_degm depending on which mode I'm in. Not the end of the world I should be able to get it done in half a day or so. It could be possible yes, I do all my testing with the standard 172 and some modified autopilot switches.

So I'm trying to find the right combination of setting to match how my real aircraft works with the 530. Here is what I need to do. I need the gps to run the auto pilot, but also allow the autopilot to fly a radial off the vor/hsi (Connect gps to autopilot) I need the gps to talk to the hsi when in GPS mode. (Connect GPS to HSI) I need the obs button to work and be connected to the course selector on the hsi. (Connect hsi/obs (input)) I need to be able to read bearing indicator information for both vor's and gps waypoints regardless of the CDI mode (GPS or VLOC) The issue is with a combination of the last two options. In order for my course indicator to drive the OBS feature on the 530, I must have "Connect GPS to VOR indicator" enabled. However when this feature is enabled and the gps is in GPS mode, nav1_relative_bearing gets overwritten with GPS bearing information, and nav1_bearing_deg_mag freezes. Why is GPS bearing information going to the nav1 datarefs and not the gps datarefs in x-plane? How can I separate out these features so I can get realistic functionality? Thanks in Advance. (Edit: It even seems when I disable "Connect gps to vor indicator" the cdi and course indicator on the hsi also stop working. I thought that was "Connect gps to hsi"???

So it turns out that it was not RXP, but rather SimAvio that was messing with my autopilot. Sorry for the confusion.

Sorry I had my initial reason wrong. The reason I can't use "Connect gps to hsi" is because when it's enabled the autopilot will not follow a vor/hsi.

Thanks for the reply. The flickering happens with all the stock xplane10 aircraft, but I mostly use the 172 for testing. When I don't have RXP active I have control over the CDI source, the cdi nor the cdi source does not flick it back automatically. It seems this only happens when RXP's "Connect GPS to HSI" feature is on. The reason I need to know the state of the obs is so I can create a custom auto slew feature. I can't use the autoslew in RXP for two reasons, one is that I can't use Connect gps to hsi for the reason mentioned above, but the other is that RXP's autoslew only works when a leg is activated, which isn't how the autoslew in our real aircraft work. Our autoslew constantly updates and locks the course indicator. But autoslew can't be active when in OBS mode. For now I've determined when OBS mode is active by looking for the gps_nav_id being blank while sim/cockpit2/radios/actuators/HSI_source_select_pilot = 2. But this is very much a kludge and may not work in all circumstances.

So I answered my own question for the first one by finding sim/cockpit2/radios/actuators/HSI_source_select_pilot. But how about the OBS button on the 530? Can't seem to find a way to figure out what mode that it is.

Hello, I have two questions, the first is, is there a way to determine from dataref's which mode the CDI button in is in? VLOC vs GPS? Second, it seems that when I have "Connect CDI mode to NAV/GPS Switch" enabled, the gps/nav switch constantly flicks back and forth between gps and nav, making my cdi but tick back and forth. It's as if RXP is trying to enable one feature and xplane is trying to make it revert back. Any idea how to fix this? Cheers.