I've tried and tried to boresight the Mavricks?
-
“It has the exact same effect of pushing your belly button” - what …… your finger gets covered in blue fluff when you press CZ … that’s has to be a bug ;0)
-
Yeah I tried it. Not only does CZ with tracking TGP not disrupt the TGP track, it doesn’t disrupt anything. There’s no change when CZ is pressed when TGP is tracking in any system across the whole jet. It has the exact same effect of pushing your belly button.
And that is how the real system behaves.
-
And that is how the real system behaves.
So having TGP as point track is sort of enforcing the SPI. I guess this makes sense really, as having the TGP look one way and the FCR trying to look to another place than SPI would cause sync issues? I’m just guessing here, learning as I go
-
I’m not entirely sure why this is a surprise, unless I’ve misunderstood the above. The behaviour is as documented:
From the -34 3.1 SPI MANAGEMENT (page 144):
CZ command is effective only when no sensor tracking state exists, otherwise the SPI position will not change as the tracking sensor will force it back to the same position.
This line is also the last line on page 167, at the end of the AGM-65D/G Missile Boresight Procedures, i.e. the Optional steps (TGP only) to test if you can successfully HANDOFF a target after boresighting
Also relevant to this (on page 141):
When one of the above sensors is in tracking state (i.e. GM radar in FTT or TGP in non-slave mode) the SPI is slaved to the tracking sensor. If one of the sensors is in tracking state and the pilot is commanding the other sensor to track as well, then the first sensor will break track automatically and update its position with the SPI (which is slaved to the tracking sensor). It is not possible to have both GM radar and TGP in tracking states at the same time.
-
“CZ command is effective only when no sensor tracking state exists, otherwise the SPI position will not change as the tracking sensor will force it back to the same position.”
Hhhmmm…Is is perhaps an interesting “why” to the “what” that is TMS down>wide FOV>cursor zero procedure? You have to remove the tracking state(with TMS down) before you can reset the SPI.
-
“CZ command is effective only when no sensor tracking state exists, otherwise the SPI position will not change as the tracking sensor will force it back to the same position.”
Hhhmmm…Is is perhaps an interesting “why” to the “what” that is TMS down>wide FOV>cursor zero procedure? You have to remove the tracking state(with TMS down) before you can reset the SPI.
Only TMS aft can cancel a track mode. CZ cancels all accumulated slews, but it cannot cancel a track mode . Hope that answers your question
Newer tapes are more pilot friendly. A TMS aft of <0,5 seconds commands a CZ, if the TGP is SOI and if the TGP is not currently in any track mode.
-
Does switching to MRM cancel TGP track?
-
Yes it dose and so dose DGFT ,( You could also argue that toggling the TGP to off/on will cancel a track mode), but that involves a master mode change, not HOTAS or MFD-OSB SOI functionality
-
The boresighting process should be done always when the WPN is indicating the target in range ?
-
Here’s a good video for boresighting IMO (an easy and quick way).
I do it almost like this now. There’s more than one way of doing it. You can lock with the WPN first then the TGP etc. Basically, you just have to have the TGP and the WPN locked to the same target and hit the Boresight button. It’s actually pretty easy once I grabbed that simple concept. I was getting confused by too many details for a long long time. Anyway, you have to be in range for the WPN to get a lock, I’d say its around 15nm but surely by 12nm you should be able to lock armor up, which is outside of the weapon range I think but not out of range for a lock.The way I remember the method in the training manual – for me – that’s a good way to learn about handoff failures and how to deal with them, so I highly recommend working through that process, but I personally don’t boresight like that, it takes me too long.
So, if you are having problems, I’d recommend a nice and easy Maverick racetrack. I’ll be going about 300 knots, get my target in the TGP before turning in hot at 15nm. Once my nose is pointed at the target. TMS UP to lock first target. Wait for handoff. MSL STEP. TMS UP to lock second target. Now wait for weapon to be in range. Nose down easy if necessary to get in the keyhole and wait for the cross to stop blinking. Pickle 1. Verify cross is not blinking, adjust to keyhole if needed. Pickle 2. You should be able to turn off by 6nm. Flow out to a safe spot 15nm out, regain your preferred altitude, while doing so you can uncage your next round of mavericks, check with Awacs to see if the picture has changed. Get your next set of targets in your TGP (not locked but located). Of course, this assumes your side has control of the airspace and you have a racetrack that is clear of AAA and SAM threats. But, in my view, that’s the type of scenario you are looking for to have fun with Mavericks when you are first learning them.