Maverick Aiming

[Mike5560]

Not really a simpler way to do it unless you're firing at multiple targets within 50 or so of eachother. In which case it's probably best to fly path hold autopilot nose down a few degrees and slew the MAV seeker to the TGP SPI and fire, then adjust to different targets manually through the maverick seeker. Assuming you have the TGP on the left MFCD and MAV on the right.

 

If you're slewing the maverick seeker onto different markpoints, you have two options:

1. Set HUD as SOI and DMS fwd /aft, china hat fwd long to slew, coolie hat right long to set mav as SOI and work it from there.

 

2. Leave Maverick sensor as SOI and manually switch steer/mark points with the UFC switch. I think you can hot key the UFC rocker if you have the keys to spare.

 

It's not a simple procedure, but with practice it's not unrealistic to have two mavericks rifled at different markpoints within 6 seconds of eachother. Of course, if you have moving targets things get interesting.

Edited December 6, 2014 by Mike5560

[WildBillKelsoe]

Sorry for off topic but I guess it doesn't hurt to ask here.

 

I bought A-10C but I didn't have time to fly it yet and I saw this mentioned many times already so I'm wondering. Is this long/short button pressing only a feature on TM Warthog or can you set it up like this on any hardware? Thanks.

 

Any hardware.

[StrongHarm]

Some good answers here. Thought I'd add that the most important aspect of getting the mav on target is giving it a stable platform as explained in this previous post. Below that I'll add my HOTAS ref card, it's a little more handy than the 8 pages in the manual.

 

Although the MAV can be used like the TGP, it wasn't designed for that use. Ground stabilize in your TGP uses your EGI to find a point on the ground and maintain it. MAV only has a cone of view forward of the aircraft, and uses visual recognition rather than EGI.

 

If your MAV camera zooms away from the target quickly and you can't seem to slew where you want, that means your traversal velocity is too high. In other words, as the nose of your aircraft (and the mavs) moves in a line across the line of the target, your camera is unstable. The Mav doesn't have the stabilization abilities of the TGP. Try this, it works extremely well for me, and take note: you only have to manually track on the first Mav, because this one is coming off TGP slave. The next mavs just slew, autolock, rifle:

 

*13-15k ft, 10nm separation from target area

*TGP lock and SPI target, slave all SOI to SPI

*Line up with target

*neg 8-10 on the pitch and path autopilot

*throttles all the way back

*Let the aircraft stabilize

*Switch to Mav camera and TMS FWD Short for track (first target only)

*Fire, acquire, fire, acquire... etc.

 

The mav camera is much more stable. You'll still be more than 5nm away at 10k or higher and you'll have up to 6 mavs in the air.

 

NOW.. you don't have to use the TGP to get your target on. I've actually used the MAV head to seek a target when I didn't have a TGP loaded. Once again just give the MAV head camera a stable platform. Use the above method minus the TGP in step 2, and it will not be necessary to TMS FWD Short for track, since you aren't slaved to TGP. Don't forget to use the FOV feature of the MAV head to zoom in and out on the area to facilitate faster or slower slewing.

 

Editable spreadsheet available in original post:

Edited April 29, 2016 by StrongHarm

[Phantom_Mark]

Thanks all :)

 

My colour laser hates me for printing the whole PDF :P

[Phantom_Mark]

I noticed the function to "Maverick Adjust Left/Right/Up/Down" on the DMS in Maverick mode, I cannot find a mention of it in the manual? Does this simply allow small movements to try and acquire lock, move and adjust etc or ?? explanation would be appreciated, as targeting anything with Maverick atm has become more tricky, hence trying everything I can to increase distances on locking the target, forced correlation mode is not yielding much better results tbh.

[Hansolo]

I am fairly convinced this is udes during boresighting of the Mavericks. Please take a look at this post #13;

http://www.476vfightergroup.com/showthread.php?3204-Maverick-Employment/page2

 

Cheers

Hans

[Razor18]

Yup, and that is actually the preferred method. :)

 

- Set TGP as SPI generator with TMS Forward Long

- By now, wherever you aim the TGP, that is your SPI (unless you designate another SPI generator, obviously)

 

 

Hi Guys,

 

No nitpicking, I just want to make sure to understand the principals right:

 

Wherever your SOI points (even without lock) is the SPI. As long you don’t press TMS Up Long, this SPI is just a „temporary” SPI, which wanders off if the SOI gets slewed. Without TMS Up Long first, another sensor can’t be slaved to it, because as soon you choose another sensor to slave to any SPI, it takes over SOI (and SPI generator) function from the previous one, without having any previous SPI „memorised” to be slaved to. After you TMS Up Long, you practically „drop a permanent marker”, which gets memorised, and any other (or all) sensor then can be slaved to it, as long no other SPI will be generated.

 

Or if you first set any sensor to be slaved to any SPI, then make another sensor SOI and make SPI with that (with or without TMS Up Long), the previous SOI maintains it’s „slaved to SPI” state, and follows the „new” SPI made by the new SOI?

 

Thanks

[Eddie]

Hi Guys,

 

No nitpicking, I just want to make sure to understand the principals right:

 

 

Nope, I'm afraid it's you who needs to understand the principles correctly. There is no such thing as a permanent SPI/marker or a temporary SPI. There is only the SPI, which always exists. The only thing that changes is the sensor that is generating the SPI, the sensor generating the SPI is selected via TMS Up Long, the selected SPI generator remains such until you set another sensor as SPI generator.

 

The SPI itself is a constantly updated point in 3D space, not a marked/locked/permanent target position b

[Razor18]

Nope, I'm afraid it's you who needs to understand the principles correctly.

 

Yes, that's what I meant, I wanted to make sure to understand the principle for myself. I didn't write to teach anybody... Sorry, I'm not a native english speaker. :)

 

Just asking: as long as you don't press TMS Up Long, but you have a SOI pointing somewhere (stabilised), can you slave any other sensor to this SPI?

Edited January 25, 2016 by Razor18

[Eddie]

Just asking: as long as you don't press TMS Up Long, but you have a SOI pointing somewhere (stabilised), can you slave any other sensor to this SPI?

 

If the SOI in question was previously set as SPI generator, yes, as the SPI will always follow where that sensor is pointed.

 

If it wasn't the last sensor set as SPI generator then no, slave to SPI will always slew to the current SPI regardless of the current SOI.

[Razor18]

If the SOI in question was previously set as SPI generator, yes, as the SPI will always follow where that sensor is pointed.

 

If it wasn't the last sensor set as SPI generator then no, slave to SPI will always slew to the current SPI regardless of the current SOI.

 

OK, and what happens, if You press TMS Up Long, then just slew the same SOI somwhere else, no TMS pressed, just command "All sensor to SPI" (China Hat Fwd Long). Will all sensors be pointed where the SOI is now, or where the SOI was when TMS Up Long was pressed?

[shagrat]

Pretty much correct, just there is only one SPI at any given point in time.

 

And a tip, you can see the SPI generator in the lower left of the HUD (usually the TGP).

 

You may want to have a close look at the flight manual in addition. Around pages 84-90 (in the Cockpit Control section) there is the overview of HOTAS buttons with tables as a reference.

 

In general (mission start) the SPI is on the Steerpoint, it wanders from Navpoint to Navpoint in your flight plan while you follow your route (Navpoint gets Steerpoint when selected or automatically switched by flightplan).

 

As the Steerpoint rarely is exactly "on target", you now choose a SOI (likely the TGP) and focus on a Tank (for example) 150m near the Steerpoint, with TMS up short (Hook target in point mode).

 

Currently the SPI is still on the Steerpoint!

 

Now you do TMS up long to set the TGPs hook as SPI.

Now the SPI moves from the Steerpoint to the Tank (there can only be one SPI at any given point in time).

 

The SPI is "locked" to the TGP. As the TGP tracks the Tank, it may drive down a road, the point track mode will follow it, the SPI moves with the TGP.

 

Meanwhile you can use other sensors like the maverick independent (as long as you did not "slave all sensors to SPI" with China hat fwd long)!

 

To reset the SPI to the current Steerpoint you hold TMS down long. As"sensors are not slaved to SPI" the TGP should stay on the Tank.

 

Now if you fire a Maverick you want to slave its Sensor to the SPI set by the TGP with China hat fwd long. Now, ALL sensors Maverick and (!) TGP and HUD are slaved to the current SPI.

If you select Maverick as SOI you can slew the sensor around, but unlike the TGP the Maverick isn't SPI generator so the SPI stays where it is until you hook a target with the MAV seeker and TMS up long to set it as SPI.

 

You could for example use the Mav seeker to lock a Tank, set it SPI and slave all other sensors (TGP, HUD) to it with china hat fwd long!

 

To un-slave/reset individual sensors, you need to use China hat aft short.

And finally you can slave the TGP (only the TGP) to the current Steerpoint with China hat aft long.

[Eddie]

OK, and what happens, if You press TMS Up Long, then just slew the same SOI somwhere else, no TMS pressed, just command "All sensor to SPI" (China Hat Fwd Long). Will all sensors be pointed where the SOI is now, or where the SOI was when TMS Up Long was pressed?

 

 

They'd go to where the SOI that you have set as SPI generator is pointed at that moment.

[Phantom_Mark]

I am fairly convinced this is udes during boresighting of the Mavericks. Please take a look at this post #13;

http://www.476vfightergroup.com/showthread.php?3204-Maverick-Employment/page2

 

Cheers

Hans

 

Thanks Hans :thumbup:

[apolloace]

Really Helpful

 

Yup, and that is actually the preferred method. :)

 

Follow these steps:

- Open TGP on the MFCD

- Set TGP to A-G mode

- Set TGP as SOI with Coolie Hat Right Long or Left Long according to MFCD

- Set TGP as SPI generator with TMS Forward Long

- By now, wherever you aim the TGP, that is your SPI (unless you designate another SPI generator, obviously)

- Switch MFCD to Mav

- Set Mav as SOI with Coolie Hat Right Long or Left Long according to MFCD

- Slave all to SPI with China Hat Forward Long

 

That's it, the Mav should now look where the TGP was looking. :thumbup:

 

Note, I haven't flown A-10C in a while, I'll gladly correct the above if I've gotten anything wrong.

 

Note #2, the above is one way of doing it. E.g., there are other ways to set the SOI , so if you find that another way works better for you, that's of course totally okay. :)

 

Thanks Yurgon for the steps!

 

Dot forget to push the lock button after it's pointed at the target to enable the Mav to lock on

 

By lock button I think he means TMS Up short. That should force MAV to lock on target.

 

The Final Lock On trick! Thanks to ricktoberfest & Corvus.

 

As I am a newbie learning the Hog, this thread has been really helpful for me to learn Maverick Deployment.

 

:) :)

[Razor18]

Hi Guys,

 

maybe not too much OFF in this topic: for HUD, what is the function of CHINA HAT FWD short. I see it sets MAV as SOI, but what is the function or the benefit of it?

 

THX

[Vitormouraa]

Actually, the CHINA HAT FWD SHORT zooms the MAV or the TGP, it doesn't set as SOI. Maybe you were talking about Coolie Switch, it sets the sensors as SOI.

[Kimi_uy]

China fwd short with HUD as soi makes the mav soi.

I've never used it though it must have something to do with being heads up and being padlocked to a tgt in the ground and u wanna slew/engage without looking though the mfcd. IIRC if your mav is not soi u cannot see the wagon wheel symbol.

[BaconSarnie]

IIRC if your mav is not soi u cannot see the wagon wheel symbol.

 

You can see the wagon wheel symbol in the Hud if MAV is not SOI

[Razor18]

Actually, the CHINA HAT FWD SHORT zooms the MAV or the TGP, it doesn't set as SOI. Maybe you were talking about Coolie Switch, it sets the sensors as SOI.

 

I think what you said about zooming is true only as long TGP or MAV are the SOI. Kimi_uy's feedback answers it rather, it must rather be the "HUD Maverick" mode then, when the Mavereicks range staples are also duplicated in the HUD, so you can actually eyeballing and slewing the wagon wheel onto the TGT. (?)

 

Thanks for feedback anyway

[Kimi_uy]

You can see the wagon wheel symbol in the Hud if MAV is not SOI

I stand corrected. But i do remember that it doesnt show up all the time, its either having a mav profile selected or ccip mode.

[Kimi_uy]

I think what you said about zooming is true only as long TGP or MAV are the SOI. Kimi_uy's feedback answers it rather, it must rather be the "HUD Maverick" mode then, when the Mavereicks range staples are also duplicated in the HUD, so you can actually eyeballing and slewing the wagon wheel onto the TGT. (?)

 

Thanks for feedback anyway

Indeed, its for doing a mav engagement with the hud. Of course u would need to have a proper mk1 acquisition!

[Razor18]

OK, but if it's there anyway, what is what the maual says about CHINA HAT FWD SHORT for HUD mode "Set MAV as SOI"... ?

 

What's the difference compared to "Coolie hat R or L long" to whichever MFCD has Maverick on?...

[firmek]

No difference, just another way to make Mav SOI.

[Razor18]

No difference, just another way to make Mav SOI.

 

:doh:

 

thanks tough