PVI INU reference points

[andqui]

Is INU drift modeled? I was flying a long-ish mission online yesterday, and towards the end I noticed there was a slight discrepancy between the ABRIS and INU reported distances. The mission was not built with any reference points, so I didn't know how to perform an update.

 

Is there a way to make your own reference points in the chopper, without using the mission editor. For example, if I land at an advanced FARP to rearm, can I note the GPS coordinates on the ABRIS to manually enter a new reference point on the PVI, and then perform a "fly-over" alignment? If so, how do I go about manually entering one?

 

thanks

[Fishbreath]

I don't think INU drift is modeled. I believe it's the case with the real chopper that the GNSS is used to perform in-flight updates on the INU anyway (just about the only way the ABRIS system connects to the navigation/targeting complex in that direction).

 

I dunno what's up with the drift you observed. Do you have the mission handy?

[mvsgas]

You can find more info in this forums and in youtube about the PVI-800/INU.

The drift is not modeled AFAIK. I do not believe the PVI-800/INU communicate with the ABRISS/GNSS in any way. The differences you notice is because the PVI-800/INU are not as precises as the ABRISS with GNSS. So PVI-800 is made to get you to the right city, ABRISS will get you to the right street. You can get coordinates out of the ABRISS and enter them into the PVI-800 ( several videos on how in youtube) but they will still not match perfectly.

[Raptor9]

Another thing that causes confusion is the PVI Lat/Long readout is in DD*MM.M'/DDD*MM.M' format.

 

I used to think the last digit was in seconds rounded to the nearest 10th integer; like 32 seconds would be rounded to 3. But when I started seeing numbers go above 6 in the last digit, I realized that was not the case.

[madyogi]

Another thing that causes confusion is the PVI Lat/Long readout is in DD*MM.M'/DDD*MM.M' format.

 

I used to think the last digit was in seconds rounded to the nearest 10th integer; like 32 seconds would be rounded to 3. But when I started seeing numbers go above 6 in the last digit, I realized that was not the case.

 

1st of all, the digits layout changes, depending on things you pick on the PVI - I guess you know that!

 

For WP navig., the last number in 6-digit rows for lat/long panels, is in range 0..9, where 0 is like 0..9[%] and 9 is like 90..99[%] of 'seconds' for indicated location.

 

Every minute goes ++1, when seconds counter 'overflows' 9 (resets back to 0). Every minute goes --1, when seconds counter drops below 0.

 

1*=60'; 1' = 60''

so for 44*56',8 you should end up somewhere near 44*56',~48''

 

I guess it was stated somewhere in the man. but im not in a mood to read it again as long as ED isn't in a mood to fix the KA bugs... :doh: :joystick:

 

O, the DD/DDD is actually DDD/DDD and 1st 0 is not indicated, though you need to press it when manually programming the PVI.

 

Look at it like X/Y axis where Greenwich location is the center. Further you have [0]DD/0DD 1st quarter; [0]DD/1DD 2nd; 1DD/0DD 3rd and 1DD/1DD 4th quarter of entire world... I leave it to you, to find out which one is where... :D

 

The INU was 'modelled' as you called it, in BS1/2, when it was not part of the DCS. The goal was to locate the INU position with own "seat" or at least with a shkval's laser, next press the 'lock' buton (I think), to "correct the INU drift". One could also put INU points in the mission editor, but i guess all of that was too hard to digest for guys that are afraid to read manuals...

Edited September 19, 2014 by madyogi