bengo Posted March 14, 2010 Posted March 14, 2010 Short answer: You determine N/S or E/W by preceding the digits of the coordinate with a + or -. If you look to the left of the main lat/long fields you'll see there are little circular indicator lights. They display a "+" or "-" and are considered part of the value in the field to the right. Your first digit (0 or 1) determines whether the light is a "+" or a "-". You'll also notice that the 0 and 1 keys themselves have the + and - symbols on them along with the digit. The convention with the PVI-800 is Northern latitudes are positive so +45° would be 45°N and -45° would be 45°S. West is negative and East is positive for longitude. I've tried to put the advice in this thread into practice, but I can only see the "minus" appear in the circular indicator light. I could not get the "plus" to show there. Anybody got an idea what I could be doing wrong there ? i7 6700k/GTX1070-8G/MSI-Z170A Gaming Pro Carbon/32GB DDR4 Kingston HyperX PREDATOR DDR4 3000MHZ Vengeance 1600/TM Warthog #6106/Samsung SB350_S27B350H/OCZ Agility3 SSD 128GB / Win10-64/TIR5
topdog Posted March 14, 2010 Posted March 14, 2010 (edited) I don't think you need to get the plus sign to show actually; just press it at the appropriate time in the sequence depending on whether you need a positive (unlit) value with the +/0 key or negative (lit) value with the -/1 key and continue with the rest of the sequence. I also noted that I didn't seem to need a leading 0 for the sequence in the upper PVI display but I did for the lower PVI display (for the second half of the sequence). What also was odd is that I couldn't get some values to 'stick' as I entered. It started out showing 43'58'(.)7 to match Abris value 43'58'44 and I changed it to 43'58'(.)6 in the PVI and it was fine. I then went to change it back to 43'58'(.)7 and it refused, kept setting to 43'58'(.)6 again. I tried with 43'58'(.)8 and that was fine so seems some odd rounding takes place that just prevented me from regaining 43'58'(.)7 and it kept getting rounded down. Normal or seems to be a minor bug? P.s. I should note, that number sequence was for the upper display. I forget what the lower display was, but basically, these two values are the defaults for waypoint1 when going into Instant Action. It was 41'03'(.)6 or something if I recall. Edited March 14, 2010 by topdog [ 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 ]
Frederf Posted March 16, 2010 Posted March 16, 2010 I've tried to put the advice in this thread into practice, but I can only see the "minus" appear in the circular indicator light. I could not get the "plus" to show there. Anybody got an idea what I could be doing wrong there ? :doh: Ah, very good. I made a mistake! When you enter a "plus" coordinate (East or North) then the "minus" light for that line does not get lit. When you enter a "minus" coordinate then the "minus" light comes on. There is no plus light, only minus light on for negative or minus light off for positive. What also was odd is that I couldn't get some values to 'stick' as I entered. It started out showing 43'58'(.)7 to match Abris value 43'58'44 and I changed it to 43'58'(.)6 in the PVI and it was fine. I then went to change it back to 43'58'(.)7 and it refused, kept setting to 43'58'(.)6 again. I tried with 43'58'(.)8 and that was fine so seems some odd rounding takes place that just prevented me from regaining 43'58'(.)7 and it kept getting rounded down. I couldn't recreate this problem. Changed coordinate to .6, then to .7, then to .8. Worked every time. It's really easy to miss a button press or have the master mode in the wrong position or not press a task light or something like that.
26-J39 Posted March 16, 2010 Posted March 16, 2010 What also was odd is that I couldn't get some values to 'stick' as I entered. It started out showing 43'58'(.)7 to match Abris value 43'58'44 and I changed it to 43'58'(.)6 in the PVI and it was fine. I then went to change it back to 43'58'(.)7 and it refused, kept setting to 43'58'(.)6 again. I tried with 43'58'(.)8 and that was fine so seems some odd rounding takes place that just prevented me from regaining 43'58'(.)7 and it kept getting rounded down. I too have had this problem on occasion, it has not happened for a while but when it did ( if memory serves me correctly )it was the .7 i could not get to stick in PVI also. :noexpression:
topdog Posted March 16, 2010 Posted March 16, 2010 I couldn't recreate this problem. Changed coordinate to .6, then to .7, then to .8. Worked every time. It's really easy to miss a button press or have the master mode in the wrong position or not press a task light or something like that. I believe you, if you say you could not reproduce this (if it is a bug that is a possibility), but here are the steps I can follow to reproduce this consistently. It's not 'omgosh' bad of course, quite the minor 'buglet', but just in case there is something I have done wrong I would welcome enlightenment. What do you think? I can crash, recover, repeat, without touching any other controls and get this. I can quit and go back in instant action, always the same for me (1.0.1 patch, no mods except acmi file exports for tacview). [ 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 ]
bengo Posted March 16, 2010 Posted March 16, 2010 Thanks for clarifying that Frederf. i7 6700k/GTX1070-8G/MSI-Z170A Gaming Pro Carbon/32GB DDR4 Kingston HyperX PREDATOR DDR4 3000MHZ Vengeance 1600/TM Warthog #6106/Samsung SB350_S27B350H/OCZ Agility3 SSD 128GB / Win10-64/TIR5
Frederf Posted March 16, 2010 Posted March 16, 2010 (edited) Ah, there you go. Yes, if I overwrite 0-43587/0-041036 coordinates over WPT #1 then it shows 43586. I can change it to anything else 43577, 43578, but not that exact first coordinate. The second coordinate doesn't seem to matter, i.e. 0-43587/0-041000 shows up as "43576/041000." Similarly WPT #2 starts out as "043591/0041025" and if you edit WPT #2 with exactly that sequence the same problem occurs. WPT#2 shows up at "04359--0--/0041025" Meaning editing a coordinate with itself seems to subtract 1 from the last digit of the display. This only seems to happen for the coordinate the mission started with. If I change WPT #N to some arbitrary coordinate and then edit it again with the same coordinate the bug doesn't happen. In a related note, first thing in instant action try setting the PVI master knob to "check" and see if you can check WPT #2, #3, and #4. Mine are all blank despite them being defined and usable in "oper" mode. Check does seem to work with WPT #1 though. Edited March 16, 2010 by Frederf
Recommended Posts