Procedure Abris-PVI

Anyone know the proper way to do this? As part of the start-up procedure in the manual it states to enter ABRIS coordinates into the PVI. I know it isn't necessary but I thought what the heck, why not?

There's one problem....there's a digit missing in the PVI compared to the ABRIS. Do I round up? Round down? Or is it formulaic, and I need to do some math to convert the coordinates? Everytime I do this my coordinates are off.

The ABRIS also supports 2 formats for showing coordinates. Which format is the PVI using?

The last digit in the PVI is in 10's of a minute, IIRC.

minute? I'm sorry i don't understand, is it then something other than part of a coordinate? What do you mean by "minutes" Perhaps I should rephrase the question. If the E/W coordinate in ABRIS reads:

40.56'74

How should this be entered into the PVI? Or should I switch to the other format in ABRIS? In that case, how is that entered, as that too contains an extra digit

Minute as in time

or

minute as in size

minutes as in 1/60th of a degree of lat/long. I too look forward to the correct method of entering data.

Coordinates are in hours/minutes/seconds. However on the PVR-800, coordinates are hours/minutes/10ths of a minute. So...

 

N33"12'30 = N3312.5

 

At least that's how it works in my airplane.

 

Hope this helps,

Smokin' Hole

Through epic forum-searching, I located the above post. I'm going to give this a shot!

Through epic forum-searching

+1 for effort

Looks like the above works! The PVI is in the "Decimal" format the ABRIS uses, so you must change the ABRIS default on mission start to match format. You do NOT round the figures. Therefore, if ABRIS reads 43.77.57, you enter into the PVI 43.77.5

I also discovered a bug. The PVI will not always reflect what you enter in the "edit" mode when switching to "Operate"

The top line of the PVI will not accept a figure that ends in "1", and will display it as "0" when switching to operate mode. I tried a few other digits, and it doesn't seem to do this with them. However, it did not seem to throw off the navigation at all. I set up a 2 waypoint route in ABRIS, entered into PVI, and the autopilot (with desired course activated) flew me perefectly from one to the other.

This is strange, as the items you set in the mission editor are shifted from their actual counterparts in mission. This means that, unlike my previous post on the matter, it appears that it is the mission editor coordinates that are NG, in-mission ABRIS seems to take the coordinates just fine.

The question now becomes, I know INU drift is not enabled, but if you INU update on a coordinate that is NOT the one set in the mission editor (and thus the PVI), is the INU then thrown off by that? Or is the INU always 100% accurate at this point in its implementation?

The PVI uses the XXX°YY.Y' format while the ABRIS uses the XXX°YY'ZZ" format by default. To have the ABRIS use the XXX°YY.YY' format by default, look here: http://forums.eagle.ru/showthread.php?t=37116

You should be really careful how you write coordinates to avoid confusion. 45.4.56 is meaningless or just plain wrong for example.

You should most definitely round to the nearest tenth of a minute. 45.66' is closer to 45.7' than it is to 45.6'.

As for a bug in the PVI about the 1 digit thing... I find that really hard to believe. Are you sure you're using the 0/1 keys to differentiate between North/South and East/West, using any preceding zeros (ex. 045°56.4 instead of 45°56.4), and making sure to hit enter at the end of the sequence? I've entered quite a few coordinates into the PVI and have never seen that error.

Right the coordinates I give above are meaningless, only meant to demonstrate an example.

I am positive. It occurs with the digit "1" and only in the top row, last digit entered. I can post a track tomorrow if desired. Like I said, not a huge deal. Took me where I needed to go anyway.

I am aware that 0 and 1 differentiate + or - coordinates resepctively, but I assure you, after the first time I saw it, I thought I did it wrong. I re-entered the coordinate. It happened again. 3rd time I made dang sure I entered a 1 and not a zero, and, voila, a 0 in operate mode.