This image is from the Torquesim Cirrus SR20 Avidyne aircraft for Xplane.  I'm operating dual 430's from Realsimgear and the RealityXP 430 plugin. The good folks over at Torquesim tell me that the data references on the screen as indicated by the Nav, Bearing and Aux buttons are based on data their model receives from RealityXP.  The HSI and data on the Nav, Bearing and Aux buttons should match and the bearing pointer on the HSI should point to the GPS waypoint KAND.  It says it is pointed at KAND, but as you can see, the bearing is pointing at 2 degrees rather than 91.  91 is correct.  The Nav button seems to work fine as long as you only try to use it with GPS1.  Won't work with GPS2, but that is a minor problem.  I was hoping this problem could have been addressed in the latest RealityXP update, but I tried it this morning and this was not addressed.

I can affect the appearance of the bearing pointer and data in the Bearing and Aux buttons by changing the data flow settings in the pull-down GPS1 settings. But even then the results are not reliable and if, say, the Bearing pointer does actually lock on to the correct bearing, it stays there and will not rotate as the aircraft position changes.

So please let me know if this is a problem with Reality XP or if it is with the Cirrus Avidyne from Torquesim.  It would be great to get this worked out. 

Thanks,

Hank Sullivan

 

 

 

 

Hi Hank,

It would be best if they contact me with the exact list of datarefs they are using and under which condition. This way I can help them reviewing whether they are using the correct ones and I can review whether there is a bug in ours!

In the meantime, you can easily cross-check the RXP datarefs directly in the dataref editor. They are all documented in the RXP User's Manual and this might be a good starting point we gather as much additional info in this topic this way?

If you could show a screenshot of the same situation with the same EFIS values, but with the datarefs on the side to compare which is which, it would be great.

Edited July 2, 20214 yr by RXP

Thanks for the response.  You said, "If you could show a screenshot of the same situation with the same EFIS values, but with the datarefs on the side to compare which is which, it would be great."  I'm not sure what that means.  Also, how do I gain access to the datarefs editor?

Dataref Editor is standard feature in XP11: Plugin > Dataref Editor!

https://developer.x-plane.com/tools/datarefeditor/ 

(an older document about it because I don't remember you have to download it in XP11, but I honestly might just be presuming it is standard plugin, I'm just so used to having it for ages it is quite standard to me actually 🙂 )

 

Edited July 2, 20214 yr by RXP

Thank you.  Looking into it.

On 7/2/2021 at 11:42 AM, RXP said:

Hi Hank,

It would be best if they contact me with the exact list of datarefs they are using and under which condition. This way I can help them reviewing whether they are using the correct ones and I can review whether there is a bug in ours!

In the meantime, you can easily cross-check the RXP datarefs directly in the dataref editor. They are all documented in the RXP User's Manual and this might be a good starting point we gather as much additional info in this topic this way?

If you could show a screenshot of the same situation with the same EFIS values, but with the datarefs on the side to compare which is which, it would be great.

Hi Jean-Luc,

I've just sent over an email to you with this info.

Thank you Coop and Jean-Luc for looking at this.  I will look forward to a resolution.

Hank

@Hank Sullivan
I'd appreciate you'd share a screenshot where I can see the EFIS in the same situation/location you've setup above but with the data ref editor window showing the RXP data refs side-by-side. This will help too!

5 hours ago, RXP said:

@Hank Sullivan
I'd appreciate you'd share a screenshot where I can see the EFIS in the same situation/location you've setup above but with the data ref editor window showing the RXP data refs side-by-side. This will help too!

I'm not sure I know what you are asking.  I downloaded the Dataref plugin and installed.  When I go to the menu and select Show datarefs, i get a window with a long list of data refs, but which are not correlated to anything you see on the screen.  And there are more items in the list than can be shown on the screen.  Here's what I got.

 

I can't zoom the picture, it is tool small!

however you can filter the display: click on the black area right below the green list, type RXP, and this will display only the datarefs with "RXP" in their name/path!

OK, here are two images, one of them a close up of only the RXP datarefs.  I believe they should be readable.

 

 

That didn't work.  Will try another. 

As you can see, when you hit the "Bearing" button, the dataref toggles among the following settings: OFF, GPS1,VLOC1, GPS2, OF VLOC2.  So in each case, obviously, the PFD is calling for a different piece of data to display on the screen.  As I was describing above, when I call for any of those pieces of data via either the BEARING button or AUX button (both pull from the same data), the data it calls to display is erroneous.  But by going to the plugins menu, and just toggling between the data flow settings, say changing GPS>SIM TO GPS<> SIM, I can affect the data we see on the screen, sometimes bringing up the correct data.  Even then, however, the data remains frozen, the BEARING pointer for example never changing as the bearing should naturally change when wandering off course to whatever waypoint of VOR one might have selected.  Thanks again for looking at this.

 

 

Thanks for these, this is invaluable feedback which tells me exactly what they should do in the EFIS code!

Awesome!!!!  This is a great sim and you have an invaluable product for true to life training.