No SPI

[Zenra]

Ok, I have been having a great time since the early betas and I know that I have read the solution to this problem before on this forum but am unable to find my way back to it with searches today.

 

My question is: I enter the coordinates for a few waypoints i noted as points of interest while reviewing the Mission Planning map while on the ramp waiting for the EGI to complete alignment. Is there a way I can get the CDU / terrain database to provide the ground elevation for the location (i.e., L/L or UTM coordinates) automatically? The problem is that if I enter the waypoint without explicitly setting an elevation when I cycle to the new waypoint to set it as my STEERPOINT the system flags "NO SPI" and I am therefore unable to slave the other sensors to it. I expect this is realistic behavior, but I am trying to figure out the best way to set up such waypoints while on the ramp and be able to call them up during the mission and slew the TGP, or other sensors, to them the same way I can with other per-set mission waypoints, mark points, etc.

 

Seems like I must be missing something simple, so don't hesitate to be brutal pointing out what I might be doing wrong. :music_whistling:

[hassata]

If I understand the question correctly, then:

 

Steerpoint or waypoint are simply points in space used for navigation. You have to make something the SPI to get sensors to look in that direction. To make something SPI, you have to point a sensor at it and TMS Up Long. You can point with the TGP, TDC (HUD 'box'), or, in certain instances, the map. To point using the map, you have to be be able to designate with the cursor. You can most easily do this by making a mark point (TMS right short).

 

Someone please correct me if any of this is wrong.

 

Edit: If you are just trying to get the TGP to look at a waypoint, cycle to make it the steerpoint, then China Aft Long. You can set SPI to Steerpoint with TMS Aft Long.

Edited December 31, 2011 by hassata

[ralfidude]

When you enter coordinates, North and East the Elevation is inputed automatically.

 

Switch the knob to Mission, select the newly created waypoint by cycling to it, and then slave your TGP to it with china long, and presto.

[Olgerd]

DTSAS needs EGI in NAV mode to determine coordinates. IRL all changes in CDU database are made only after EGI is fully aligned and is in NAV mode. You always can enter altitude manually if you know it. Alternatively you can add 'initial points' in the mission editor. They will be loaded into CDU with correct elevations automatically.

[Zenra]

DTSAS needs EGI in NAV mode to determine coordinates. IRL all changes in CDU database are made only after EGI is fully aligned and is in NAV mode. You always can enter altitude manually if you know it. Alternatively you can add 'initial points' in the mission editor. They will be loaded into CDU with correct elevations automatically.

 

Oglerd,

 

Thanks - that explains it. I did not realize the EGI needed to be fully aligned in order for the system to be able to determine the ground elevation of the coordinates entered. I never had such a problem entering coordinates from JTAC, and this is the first time I tried to save time by entering points from the mission planner map during start up. I had assumed that having the DTS database loaded would be sufficient. I stand corrected!

 

Thanks again, and a Happy New Year to all!