Jump to content

Recommended Posts

Posted

I have created a new flightplan via abris and insert the coordinates into pvi-800. But when i fly with ap-route, then he fly automaticaly to waypoint 2 and then shows the route end in the overhead panel. When i select button 2 on pvi-panel, then there is empty. But when i reselect the nav button and then button two, the coordinates shows in the nav-panel and the helicopter is turning to waypoint 3. On waypoint 3 the route end again...

 

What did i take wrong?? or is it a bug?

 

sorry for bad english

 

Regards Intruder

Monitor: ASUS TUF Gaming VG27AQL1A| Case: Thermaltake Overseer RX-I | PSU: EVGA SuperNOVA 1300 G2 80+ GOLD, 1300W| Mobo: Gigabyte Z390 Aorus Master | CPU: Intel Core i9 9900KS @5 GHz | CPU-Cooler: Noctua NH-D15 Tower Cooler | RAM: 32GB G.Skill F4-4133C17-8GTZR | GPU:NVIDIA GeForce RTX4090 OC 24GB |SSD: Samsung SSD 860 M.2 1TB | Keyboard: Logitech G110 | Mouse: Logitech G502 | Gaming Devices: Hotas WW Orion 2 Stick&Throttle, Thrustmaster MFD, Pimax Crystal, Stream Deck XL

 

[sIGPIC][/sIGPIC]

Posted

hi SunDown

 

When i flying the route created in the editor, then ap route is flying automaticaly all waypoints and switch also the waypoints in pvi-800. But when i unload the route and create my own, he is flying perfekt the first waypoint, but on this first waypoint the ap route shows "route end".

I dont think(hope so) i did make anything wrong on programming the route in the nav-panel, but i´m not 100% sure. Maybe a betatester can help, if anyone is trying this.

 

Regards Intruder

Monitor: ASUS TUF Gaming VG27AQL1A| Case: Thermaltake Overseer RX-I | PSU: EVGA SuperNOVA 1300 G2 80+ GOLD, 1300W| Mobo: Gigabyte Z390 Aorus Master | CPU: Intel Core i9 9900KS @5 GHz | CPU-Cooler: Noctua NH-D15 Tower Cooler | RAM: 32GB G.Skill F4-4133C17-8GTZR | GPU:NVIDIA GeForce RTX4090 OC 24GB |SSD: Samsung SSD 860 M.2 1TB | Keyboard: Logitech G110 | Mouse: Logitech G502 | Gaming Devices: Hotas WW Orion 2 Stick&Throttle, Thrustmaster MFD, Pimax Crystal, Stream Deck XL

 

[sIGPIC][/sIGPIC]

Posted
are you in route mode [R] ?

 

yes

Monitor: ASUS TUF Gaming VG27AQL1A| Case: Thermaltake Overseer RX-I | PSU: EVGA SuperNOVA 1300 G2 80+ GOLD, 1300W| Mobo: Gigabyte Z390 Aorus Master | CPU: Intel Core i9 9900KS @5 GHz | CPU-Cooler: Noctua NH-D15 Tower Cooler | RAM: 32GB G.Skill F4-4133C17-8GTZR | GPU:NVIDIA GeForce RTX4090 OC 24GB |SSD: Samsung SSD 860 M.2 1TB | Keyboard: Logitech G110 | Mouse: Logitech G502 | Gaming Devices: Hotas WW Orion 2 Stick&Throttle, Thrustmaster MFD, Pimax Crystal, Stream Deck XL

 

[sIGPIC][/sIGPIC]

Posted

Inputting waypoint coordinates into the PNK

 

1. From the ABRIS, load the flight plan you wish to program into the PNK and select the Flight Plan sub-mode for selecting WP coordinates.

 

2. Set the PVI mode selector to the “ВВОД” (Enter-Edit) position.

 

3. From the PVI, enter WP (AF, TP, Fix point) sub-mode by pressing the “ППМ” (WP) (AF, TP, Fixed point) push-button. This will then illuminate the PVI display and indicate the number of pre-programmed points.

 

4. Press the push-button on the PVI-800 keypad that corresponds to the desired WP (AF, TP, or Fixed point) number. This will then display that number on the WP Waypoint display and the AF, OP, REF number will appear on the lower display.

 

5. From the PVI panel, enter the coordinates of the first point using the keypad.

 

o Enter the geographic latitude positive-negative with the 0 «+» or 1 «-» buttons (the entire territory modeled in the game has positive latitude and longitude). The «+» sign is not displayed during input.

 

o Sequentially enter the digits of the geographic latitude with decimals. The value of the latitude is displayed on the upper PVI display window.

 

o Enter «+» sign for the geographic longitude with the 0 button. The «+» sign is not displayed during input.

 

o Sequentially enter the digits of the geographic longitude with decimals.

 

The value of the longitude is displayed on the lower PVI display window.

 

6. Once you have entered the latitude and longitude values, the “ВВОД” (Enter) push-button will illuminate.

 

7. Make sure the entered data is correct and then press the “ВВОД” (Enter) button.

 

8. In case of data entry error, press the “СБРОС” (Reset) button and repeat the process of coordinate input of a given point.

 

9. To disengage the WPs (AF, TP, Fixed point) sub-mode, press the “ППМ” (WP) (AF, TP, Fixed point) push-button again and the button illumination will extinguish.

 

10. Using this procedure, use the data from the ABRIS to enter the coordinates of all required WPs, AFs, TPs, and Fix points.

 

 

That is straight out of Chapter 5 in the manual.

C Co 6-6 CAV

USLANTCOM

image.png

CW1.png

Posted

yep, i did exactly doing this in this sequence.

 

After input the coordinates, they show all in nav-panel. But after reach waypoint one, the navpanel switch not to the next waypoint and when press button 2, the display is empty. When reselect the navbutton and then press the button 2, the wayponit shows correct and route mode is flying to waypoint 2.

 

Regards Intruder

Monitor: ASUS TUF Gaming VG27AQL1A| Case: Thermaltake Overseer RX-I | PSU: EVGA SuperNOVA 1300 G2 80+ GOLD, 1300W| Mobo: Gigabyte Z390 Aorus Master | CPU: Intel Core i9 9900KS @5 GHz | CPU-Cooler: Noctua NH-D15 Tower Cooler | RAM: 32GB G.Skill F4-4133C17-8GTZR | GPU:NVIDIA GeForce RTX4090 OC 24GB |SSD: Samsung SSD 860 M.2 1TB | Keyboard: Logitech G110 | Mouse: Logitech G502 | Gaming Devices: Hotas WW Orion 2 Stick&Throttle, Thrustmaster MFD, Pimax Crystal, Stream Deck XL

 

[sIGPIC][/sIGPIC]

Posted

After you input each steerpoint, you create a route by switching the PVI back to 'Operations' (ie. the normal mode) and program the route as follows:

 

Hit the NAV/WP button, then the NAV point you want to be first in the sequence, then ENTER.

Repeat this for each STP in the sequence. After this, hit NAV, then NAV again, STP/WP 1, then route.

[sIGPIC][/sIGPIC]

Reminder: SAM = Speed Bump :D

I used to play flight sims like you, but then I took a slammer to the knee - Yoda

Posted

Yep, that was going to be my next post. Sounds like you are inputting the data correctly, but the PVI-800 doesn't know that you want link of them together into a route. Section 5-4 of the manual covers that procedure.

C Co 6-6 CAV

USLANTCOM

image.png

CW1.png

Posted (edited)
After you input each steerpoint, you create a route by switching the PVI back to 'Operations' (ie. the normal mode) and program the route as follows:

 

Hit the NAV/WP button, then the NAV point you want to be first in the sequence, then ENTER.

Repeat this for each STP in the sequence. After this, hit NAV, then NAV again, STP/WP 1, then route.

 

 

yep, this can be my problem. I dont hit the nav button after all input. I will trying this later and report.

 

Edit: Nope, didnt work for me. Further route end after each waypoint. :dunno:

 

Regards Intruder

Edited by Intruder_360

Monitor: ASUS TUF Gaming VG27AQL1A| Case: Thermaltake Overseer RX-I | PSU: EVGA SuperNOVA 1300 G2 80+ GOLD, 1300W| Mobo: Gigabyte Z390 Aorus Master | CPU: Intel Core i9 9900KS @5 GHz | CPU-Cooler: Noctua NH-D15 Tower Cooler | RAM: 32GB G.Skill F4-4133C17-8GTZR | GPU:NVIDIA GeForce RTX4090 OC 24GB |SSD: Samsung SSD 860 M.2 1TB | Keyboard: Logitech G110 | Mouse: Logitech G502 | Gaming Devices: Hotas WW Orion 2 Stick&Throttle, Thrustmaster MFD, Pimax Crystal, Stream Deck XL

 

[sIGPIC][/sIGPIC]

  • 1 year later...
Posted

I think I understand the problem here. Intruder are you using NAVTGT points or WPT points for your route? Only WPT (1,2,3,4,5, and 6) will automatically advance when in route mode. The NAVTGT points are entirely independent of each other so one you arrive at NAVTGT #4 it won't go to #5 automatically and you'll get a "ROUTE END" warning on the overhead.

Posted (edited)

Following up on this as I have been working with inputting traget points in the PVI-800.

 

I have the ABRIS set to DDD:MM.MM which is the format that the PVI-800 wants, BUT does the PVI-800 accept the hundreths of a minute data? To me it looks like the PVI-800 only accepts DDD:MM.M.

 

For instance, I attempt to input the following for TP1:

 

0(+), 0,4,3,0,5,1,9 for 043 degrees, 05 minutes and 19 hundredths of a minute.

 

but the PVI-800 does not accept the final "9" (what I mean is that it doesn't display it, so I don't know if I have poluted the next set of numbers.

 

So I try again and input 0(+),0,4,3,0,5,1 for Lat.

Then 0 (+), 0,4,1,1,0,9 (again the PVI-800 doesnt accept/display the final 9 so I start again with this final input sequence:

 

Lat: 0(+),0,4,3,0,5,1

Lon: 0(+),0,4,1,1,1,0

 

<ENTER> on PVI-800 keypad

 

I set back to OPER mode and check TP1 and I see:

 

43051 in the top set of numbers 043 degress, 05 minutes and 1 tenth of a minute (should have rounded up myself) and

041109 in the bottom set of numbers. 041 degrees 10 minutes and 9 tenths of a minute ( so the PVI-800 changed 11 minutes to 10.9 minutes).

 

Is the PVI-800 rounding the entries? Why? What does it use for the rounding calculation since I didn't input the hundreths of a minute?

 

Thanks,

Edited by Major SNAFU
Posted (edited)

There are some values we found the PVI-800 would oddly reject; for example doing an Instant Action and trying to re-key in the coordinates for WPT1 would result it in not accepting the last digit either and would appear to round it down.

 

Check out this thread too:-

 

http://forums.eagle.ru/showthread.php?t=47579&page=4

Edited by topdog
my head wasn't screwed on right the first time through

[ i7 2600k 4.6GHz :: 16GB Mushkin Blackline LV :: EVGA GTX 1080ti 11GB ]

[ TM Warthog / Saitek Rudder :: Oculus Rift :: Obutto cockpit :: Acer HN274H 27" 120Hz :: 3D Vision Ready ]

Posted (edited)

Many thanks!

 

 

I want to point out, with respects to the other thread, that I am not attempting to overwrite anything.

 

This is a mission I made for myself with no TP or FixPoints (haven't had time to read on how to do them in the mission editor).

 

I am inputing fresh coordinates for a new TP 1 (no pre-existing data).

Edited by Major SNAFU
Posted

We're probably just victims of the nuances of floating point math in (x86 architecture) computers causing some crazy rounding at times, it isn't entirely accurate so there are some apparent approximations occurring due to precision loss at varying degrees.

 

Unless this is an accurate model of some craziness from the PVI-800 itself :D

[ i7 2600k 4.6GHz :: 16GB Mushkin Blackline LV :: EVGA GTX 1080ti 11GB ]

[ TM Warthog / Saitek Rudder :: Oculus Rift :: Obutto cockpit :: Acer HN274H 27" 120Hz :: 3D Vision Ready ]

Posted

Just to be clear, so the PVI-800 only accepts DDD.MM.M, not DDD.MM.MM?

 

In none of my attempts to input data into the PVI-800 would it accept and display the hundreths of a minute place. So we should always round the tenths place as we feel appropriate for the mission, correct?

 

So as a minute equals (at sea level) 1853 meters), then .1 minutes is 185 meters and .01 is 18.53 meters.

 

So the PVI-800 is accurate to around 185 meters, plus half again to be safe due to rounding.

 

Do I have that right?

Posted

Yeah, PVI is DDD°MM.M so rounding required. There's no hidden hundredths of minute digit. With either the LUA edit or just changing the ABRIS options every mission you can get the ABRIS in DDD°MM.MM. Hopefully when INU drift is added in a patch even that 185m will seem like a distant memory. Longitude hundredth's of a minute are more accurate than the similar precision in latitude significantly distant from the equator.

 

But when i reselect the nav button and then button two, the coordinates shows in the nav-panel and the helicopter is turning to waypoint 3

 

Be aware that the ABRIS waypoint names and the PVI waypoint numbers are independent. Sometimes the names don't match between ABRIS and PVI. ABRIS point "BILLY" might be PVI point "3" or ABRIS point "0004" might be PVI point "5." They only match if you are lucky or you make sure when entering.

 

I still have the very strong suspicion that Intruder 360 is using NAVTGT points for his PVI-800 route and expecting that the PVI will string NAVTGT#1 to NAVTGT#2 to NAVTGT#3 while in ROUTE mode, while it doesn't. Only WPT type points have that behavior.

 

A good way to break a big mystery into smaller parts is to ask can he use ROUTE as he wants with a mission-default collection of points. If he can do this without any problems then we can be sure that any problem is not on using the points but on how they are entered before use.

 

That's the first time I've seen the PVI rounding error when not associated with the overwrite of a mission-default value. It might be base-2 rounding error like computers do sometimes. There are ways to avoid this when programming though.

 

The PVI display should respond to a valid and complete coordinate pair by lighting up the ENTER button before it can be entered. Perhaps there is a mistake in not selecting the appropriate task button and waypoint number before entering the coordinate? A lot of this can be spot checked by using the CHECK PVI master mode and seeing if the coordinate is the one you tried to enter.

Posted

I am certain I am entering the coordinates properly, because when I use them they take me to the correct position. So I think I have that licked.

 

The more I play with the PVI-800 (and ABRIS) the more I am finding them a real asset. I can see using target points to keep track of potential threats, etc.

 

Thanks for the information.

 

SNAFU

  • 11 months later...
Posted

Hey!

Can someone please tell me what's wrong when the “ППМ” (WP) button is not responding, so it don't has the green light? Thank You!

screenshot000im.jpg

(example in this situation by pressing ППМ, OT is closing and the PVI is looks like turned off)

[sIGPIC][/sIGPIC]

Posted

It's just a minor iluminating bug in the 1.0.2 patch.

AMD Ryzen 1400 // 16 GB DDR4 2933Mhz // Nvidia 1060 6GB // W10 64bit // Microsoft Sidewinder Precision 2

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...