Simple question about jtac

[Joker73]

Hi , i saw many videos on youtube about jtac , this in particularly

. In the mission i created i put the coordinates on the cdu and create the markpoint , 9 in my case , but when i try to put it in to the steerpoint info on the cdu as in the video , always i received "cdu input error" and i don't understand why. Any suggestions? Thanks.

[nomdeplume]

Usually caused by an odd (i.e. not even) number of digits in the coordinate. The JTAC script will drop a leading 0 when giving coordinates.

 

If it's not that... maybe post a track and/or the mission with a step-by-step of what you're doing and we should be able to spot it.

[Joker73]

Ok , i do the start up , afetr take off i switch the cdu from "flightplan" to "mark" , push function 2 and choose waypoint to prepare insert coordinates. Then i contact jtac , do check in and receive 9 lines with the coordinates "fh699680" that i put in to the cdu switching to upm and insert it as new waypoint number 9. At this point when i push fuction 0 (steer) and i type 9 follow the botton under osb 19 i receive always "cdu input error" even i create the new waypoint.

[Abbath]

Enter "fh6990068000"

[Joker73]

Enter "fh6990068000"

 

Always "cdu error input" i received. This is the mission

freeflight - Joker.miz

[Weaponz248]

Hey man, Give this video a shot,

http://www.youtube.com/watch?v=pKDIQWZIHmo

 

Also I leave the steer point set to mission.

 

You dont need to add the zeros just make sure its the exact coordinates that JTAC gave you.

 

Also instead of pushing func 0 just hit the OSB button next to the 9 should look like this..

 

[Joker73]

Hey man, Give this video a shot,

http://www.youtube.com/watch?v=pKDIQWZIHmo

 

Also I leave the steer point set to mission.

 

You dont need to add the zeros just make sure its the exact coordinates that JTAC gave you.

 

Also instead of pushing func 0 just hit the OSB button next to the 9 should look like this..

 

 

The func 0 is the botton i push after create the new waypoint , just for looking info about the steerpoint so as you told me, i already hit before OSB next to the 9.

[winz]

I've got one simple queston about jtac operation. How do I navigate to the IP, is it stored in the CDU? I've read the manual and this thing must have eluded me.

 

Edit: I created a simple mission with one navigation point, FORD, in it. And obviously the point is stored in CDU as nav point, but when I select it, the nav point name is MS001, it's position matches FORD np position, but why isn't it named ford?

Edited February 14, 2011 by winz

[nomdeplume]

I've got one simple queston about jtac operation. How do I navigate to the IP, is it stored in the CDU? I've read the manual and this thing must have eluded me.

 

I don't think the nav points are included in the CDU. Certainly they're not present when set to 'mission' mode. I don't know if their absence is just a beta thing or permanent. (Hmm I think your update just invalidated this line!)

 

If mission authors expect you to make use of the nav points, I would assume they'd either tell you in the mission briefing where they are, and/or have waypoints colocated with the navpoints.

[winz]

Thanks :)

So, what's the correct procedure of attack? Do I run in from what direction I please?

[nomdeplume]

Depends on the instructions from the JTAC... they often tell you "final attack heading x y" where that means you should make the attack with your heading between those two directions. e.g. "final attacking heading 45 135" means you should be somewhere between NE and SE when you make the attack.

 

Sometimes they don't care and won't give any such instructions, in which case you should be free to attack from whatever directions you deem most suitable.

 

If they do tell you to attack from a particular IP then you should probably do so, and hope the mission maker has provided a means for you to locate that IP. Generally if you run in from the wrong direction they'll tell you to abort, so you can always resort to trial and error! :)

[winz]

All clear, thanks a lot.