CDU data entry questions

[Bahger]

I'm rusty after a long layoff but this left me scratching my head:

 

In "Smerch Hunt" JTAC gives target coordinates in UTC format, LN followed by six numbers. I'm pretty sure I inputted this data correctly in the CDU:

 

FLT/MARK/MSN rotary to FLT

CDU mode to WP

In CDU select UTC where default is Lat/Long

Enter data in bottom data entry field

Enter name for target

Switch to MSN (i.e. "Mission") option in the rotary

Cycle steerpoints in HUD to recently-added Mission waypoint

Slave TGP to it

 

...But there was nothing there. It's quite possible that I missed a step. I remember a couple of "quirks", such as the need to add a zero to L/L coordinates in certain circumstances and, with UTC coordinates, there's something about zones needing to be switched, which I don't think I ever understood fully.

 

I want to make a mission in which the player is given UTC or L/L coordinates to input/prosecute but I need to clear up whatever confusion appears to be assailing me before I do so. Can someone advise? Many thanks.

Edited February 28, 2013 by Bahger

[Evil.Bonsai]

sounds about right. The only way to tell for certain is to post a trk file.

 

I believe the missing zeros was fixed. You should be given 6 numbers.

 

For Smerch Hunt, you should be in zone 38. 37 is near the coast. If I remember correctly, Smerch Hunt is set pretty far east.

[WildBillKelsoe]

I'm rusty after a long layoff but this left me scratching my head:

 

In "Smerch Hunt" JTAC gives target coordinates in UTC format, LN followed by six numbers. I'm pretty sure I inputted this data correctly in the CDU:

 

FLT/MARK/MSN rotary to FLT

CDU mode to WP

In CDU select UTC where default is Lat/Long

Enter data in bottom data entry field

Enter name for target

Switch to MSN (i.e. "Mission") option in the rotary

Cycle steerpoints in HUD to recently-added Mission waypoint

Slave TGP to it

 

...But there was nothing there. It's quite possible that I missed a step. I remember a couple of "quirks", such as the need to add a zero to L/L coordinates in certain circumstances and, with UTC coordinates, there's something about zones needing to be switched, which I don't think I ever understood fully.

 

I want to make a mission in which the player is given UTC or L/L coordinates to input/prosecute but I need to clear up whatever confusion appears to be assailing me before I do so. Can someone advise? Many thanks.

 

probably 37/38T

[Bahger]

probably 37/38T

 

So how do I adjust for this?

[SmokeyTheLung]

On the waypoint page there is a an OSB to the right of a number, followed by a question mark (for example: 7?) The number represents the next available waypoint that you can create. Did you press that OSB?

[Bahger]

On the waypoint page there is a an OSB to the right of a number, followed by a question mark (for example: 7?) The number represents the next available waypoint that you can create. Did you press that OSB?

 

I think that when I do that, it moves me up to the next WP (i.e. 8 , so I have found the best MO to be entering the data first, i.e. in the bottom data field, name the newly-created mission steerpoint and then hit the ? button. Am I off-kilter here?

[HugePanic]

i usuall just press the ? button, THEN i go to the CDU and modify the waypoint. Name first, then coordiantes. If i remember right, in smerch-hunt the targets are not sooo precisely at the coordinate position, so you have to search....

[Blooze]

I think that when I do that, it moves me up to the next WP (i.e. 8 , so I have found the best MO to be entering the data first, i.e. in the bottom data field, name the newly-created mission steerpoint and then hit the ? button. Am I off-kilter here?

 

I think that unless you go to next waypoint first you will be renaming an existing waypoint. You need to go to 8 because 7 has already been created. I always hit the ? button first and never have any problems.

[Yurgon]

You should really post a track, that would make debugging so much easier. :)

 

In "Smerch Hunt" JTAC gives target coordinates in UTC format [...]

 

Nitpicking a bit: UTC is for timezones, what you're referring to is the Universal Transverse Mercator system/projection aka UTM. :beer:

 

BTW UTM, look at this map and locate the Black Sea/Georgia region. Et voila, 37T/38T demystified. :thumbup:

[cichlidfan]

Et voila, 37T/38T demystified. :thumbup:

 

For a closer look at 37T/38T see the attached. It was originally posted here almost 2 years ago so I don't recall who it came from.

dcsgridmap.pdf

[Bahger]

OK, so, with thanks for your help so far, and apologies for the somewhat basic question, what significance do these two zones have in terms of how I enter given UTM coordinates into the CDU?

[Evil.Bonsai]

Doesn't change how you enter the coordinates, just changes where those coordinates are located. If your target is in zone 37T, you would need to enter that in the CDU else your coordinates will be WAY off.

 

IF you're not sure and you're close to the line separating the two zones, just enter your coordinates. If they seem way off, change to the other zone and you should be able to find your target.

 

Make sure to double check your coordinate entry. Several times I've swapped M/N w/o realizing it and sat trying to figure out why my coordinates are so far off.

[Bahger]

So if I'm on a border between, say LN and KN, then, if I'm given coords that start with LN, I input those and they are in the middle of nowhere, I should try KN followed by the same 6 numbers? Sorry about the dopey question but what I know I know and what I don't...I don't.

[Evil.Bonsai]

So if I'm on a border between, say LN and KN, then, if I'm given coords that start with LN, I input those and they are in the middle of nowhere, I should try KN followed by the same 6 numbers? Sorry about the dopey question but what I know I know and what I don't...I don't.

 

No, no, no...you're getting them mixed up.

 

The LN or KN or whatever is just as important as the numbers for the coordinates. That doesn't change from what you're given (ie, LN543987).

 

37T and 38T are a much larger area (that contains the coordinates, as example given above). The problem is that UNLESS you're right on the edge of 37T/38T you pretty much never have to worry about it. However, if you start/takeoff in one zone, say near the coast (37T) and attack targets a few miles east, you're going to have to change 37T to 38T in the cdu. Georgia is MOSTLy all in 38T except for a strip near the coast, which is in 37T.

 

search youtube for dcs a10c cdu tutorials. You will likely have to play with it a bit before it really starts to sink in.

[Bahger]

Thanks, Bonsai, I feel like a real novice now. But I've learned, and I'm sure I'll figure out the zone-change input field in the CDU after I've played with it for a while.

[Evil.Bonsai]

You're welcome. :) I learned here, reading all the posts I could find about it, even checked internet for UTM and MGRS info. This is why I have my "Location" over there on the left. Zone is 14R, MGRS coordinates PU170610.

 

And to add a small amount of confusion: there are actually 10 numbers used for a more precise location. You can see these in the Mission editor map and on the f10 map while flying. I don't remember the difference between using all 10 versus just 6 (leaving off the last 2 digits of the easting and northing). It's enough info to point the TGP in the right area and find your target.

 

Good reference: http://en.wikipedia.org/wiki/Military_grid_reference_system

 

also says using 6 numbers will give an error of 100m vs 1m for all 10.

Edited March 2, 2013 by Evil.Bonsai