PMS50 GNS530 mod

Use the large right knob to change page groups and the small right knob to navigate between the pages of a group. The traffic page is the 4th of the NAV pages group.

1 Like

I do fly this IRL, and at least in our aircraft there is no integration between them whatsoever
Strictly Com1/Nav1 & Com2/Nav2 seperated, they are not linked at all

There may of course be other setups but ours don’t interact (and don’t have a crossfill function visible)
Possibly due to how they were installed

1 Like

With no Cross Fill to confuse things, then I assume they are 100% independent.

ie Each could be in its own OBS mode with different References and bearing, and a simple selector to determine which GPS was driving the AP.

In the Asobo setup, two GPS’s seem to be “over linked” so in effect, they are both putting the same output to the AP, which is permanent connected to ??? GPS:1 (or GPS:2)

I guess one could investigate when the AP is connected, and see what happens if each GPS is turned off in turn !!

Not tried that — do I really want to and see what happens ??

The “off” position just disables the screen. They don’t actually turn off unfortunately. You can see that by the missing boot sequence when turning it on again.

As for independent GNS in a stack - Which is the one that the HSI will use for the Autopilot? How is that decided? Or do they really just independently operate NAV1 and NAV2 and you can set the autopilot to either of these?

Basically the GNS technically could hold their individual flight plans just like the the Aerosoft CRJ has it’s own flight plan without publishing it to the MSFS internals which allows them to have even own nav data.
But detaching the GNSes from the native MSFS flight plan would mean a LOT of work and I don’t see the benefit of that.

I suspect that would be a configuration OPTION in Real World, but in MSFS, it appears they are automatically Cross Linked, (Both for FP & OBS !!), so they only driven from the nav1 CDI, and sende same output from Dual GPS system are effective “ORed” together.

There only seems to be one “OBS” ( No OBS:1 and OBS:2 )

So it was designed somewhat DUMBED down, and now to make it anything more, is probably a significant change, which will mess up existing aircraft, which in itself, might be a good enough reason to leave “semi well” alone.

The more one looks below the surface, the more dirty laundry one discovers !! - so its probably better not to look too hard.

Well, I guess it’s much easier and for most players sufficient to implement it like that. There is just one flight plan in MSFS that you can load and most aircraft have only one flight plan available.
So implementing a separation between two GNS in a stack would benefit only a few aircraft really and I understand that they didn’t bother doing that step.

The last 20% to perfection cost you 80% of your time according to the Pareto principle. And Asobo with all the work still to be done need to decide when to stop and leave the rest for the major addon aircraft/system developers.

All that is made in your aircraft configuration files. At startup the GPS get this information so it knows if it’s linked to COM1/COM2, NAV1/NAV2.

I’m sorry, I was referring to the real ones that operate independently except for the cross fill.
So they basically feed the two NAV sources and you then can switch the AP between NAV1 and NAV2 to decide which of the GNS’es flight plan it should follow (considering CDI is set to GPS)?

Ahhh, Those configuration files that get HIDDEN from your prying eyes, in the Premium Aircraft, and MS Store 3rd party Aircraft :stuck_out_tongue:

Exactly – I thought we started off talking about Real World, to determine how close to Real World the Asobo system was 


As it is now is not Terrible
 it’s simplified, and that for many is a good thing.
When it comes down to it, not many planes have Dual (different) GPS systems installed, (but it is Nice to have the redundancy)

1 Like

Anyone any idea why the Magenta Line on the OBS bearing does not go all the way to the OBS reference. ? Seems to stop about 1 mile short.

The RW Unit, and the Garmin Simulator have the Magenta Line running all the way up to the OBS reference point.

Distance Rounding Off errors ? ( seen that else where in the Asobo GPS code – and fixed by @ScorpionFilm422 )

Not a big deal – “Cosmetic” – but once you see it, it can bug the hell out of you !!

Also, The OBS line seems to be RED – not MAGENTA like the Garmin Trainer.

I actually like that, a different but similar color, so I hope that “Color Bug” does NOT get fixed :slight_smile:

@N6722C I wanted to send you a PM following up our past conversations about this, I just hit the reply button by habit instead LOL. I don’t want to interpose in this topic otherwise.

thanks - managed to find it!
think I have it set up right (at the top right the mode was showing as oper) - but didn’t
get any traffic displaying (although saw some aircraft visually)?

Correct! (AP switching uses the standard NAV1/2 switch, the unit nav mode then defines if you’re guiding via GPS or NAV)

I do think they behave exactly the same even if crossfill is available, to the best of my knowledge they always remain independant in operation (which makes sense from a redundancy point of view) but again, ours are fully seperated.
This might be a simple setting, or it might require additional wiring in which case it is very clear why we don’t have it
 cost! :smile:

1 Like

The units in game are most likely tied together because they’re not units, they’re just simple interfaces into the underlying game mechanics. For example, the flight plan you see (at least in the default GPS) is not a flight plan that’s been loaded into the GPS unit, it’s the flight plan that you loaded into the game, before the flight started, and it’s the same flight plan that is feeding ATC.

If that’s the case then you cannot have two separate default GPS units showing different data because they’re getting their data from the same source.

By contrast, the RealityXP GNS530/430 for FSX/P3D were using the Garmin Trainer and as such were running outside the sim. The in-sim gauge was feeding sensor data into the trainer, which would handle all GPS logic, and would then return control data to the gauge, which would actuate controls on the plane. I believe that this is how a real simulation of any GPS unit will have to be achieved, not necessarily by using Garmin Trainer (cause that one has some serious drawbacks), but by having all the GPS logic running in a separate module, outside the sim. Even though the work that has been done on improving the default units is amazing and the improvement is obvious, i don’t know how sustainable it is. Developers are already running into all sorts of sim imposed limitations. I guess we’ll have to wait for the SDK to mature a bit.

2 Likes

Please read the TCAS chapter in the docs:

TCAS

TCAS (anti collision system) information is available from the menu of the second NAV page (Map page). When activated, the word “TCAS” is displayed in the upper left corner of the screen. The TCAS mode state is saved across game sessions.

If TCAS is not activated, all the aircraft are represented by a small airplane pictogram whatever their distance and relative altitude.

In TCAS mode aircraft near your position are represented by the usual TCAS symbols with the following range:

  • Red square if relative distance < 2nm and relative altitude < 800ft.
  • Orange circle if relative distance < 4nm and relative altitude < 1000ft.
  • Filled blank diamond if relative distance < 6nm and relative altitude < 1200ft.
  • Un-filled blank diamond if relative distance < 30nm and relative altitude < 2700ft.

Altitude deviation from own aircraft altitude is displayed (in hundreds of feet) for each target symbol. An arrow near the symbol tells if the aircraft is climbing or descending (altitude trend).

In TCAS mode, the declutter level 3 only displays TCAS data and the flight plan. TCAS data is available only to ranges <= 35nm. On the ground aircraft (not moving) are excluded from display.

TCAS algorithms used in the mod are very simple and based only on the proximity. There is no calculation about any projected collision like in real instruments.

TCAS data is disabled if your own aircraft is below 500ft AGL.

@N6722C, not only do I not know the answer to your question (sorry about that), I’m also not completely clear on wht the OBS stuff is or why I should care. Care to fill a brother in?

1 Like

I’m quite curious about the TCAS in the Aerosoft CRJ since it not only displays AI aircraft but also “injected” ones from VATSOM/VPilot etc. Not sure about regular MSFS multiplayer aicraft though.

Do you know how they do it? Is it something that’s possible for the GNS530 as well?

My understanding of this is a bit basic. Someone with more knowledge might correct me or fill in some details as I am unclear on the details of OBS myself.

OBS originally in pre GPS days let you fly a radial to a VOR.

These days it more commonly refers to a feature on a GPS used to fly direct to a waypoint in a flight plan (as opposed to NAV mode that tries to get you back on the original track to that waypoint). Useful if you have diverted from the flight plan and it now makes more sense to fly direct to the next waypoint and rejoin the flight plan there.