Maverick training mission boresight question
-
Don’t forget the Search box in the top right corner. I typed in TGP 018 and this is what was found:
TGP HNDF FAIL 018 is a missile boresight correlation fail.
TGP HNDF FAIL 019 is missile boresight correlator out of toleranceI expect to get those errors with a handoff failure, but the point is I still get them after a confirmed handoff.
But again, I need to go back over it and see if something is out of sequence.
-
The fault isn’t dependent on succeeding on a second attempt. It’s probably something like you had a failure on a “handoff session” and it persists until the end of the session. Oddly I followed (probably) the training document’s procedure exactly and didn’t find the fault to be so persistent as described here. I’m curious about exact reproducing instructions.
-
TGP on the left MFD, WPN page on the right, station 7 65D uncaged.
1. locate destroyer on TGP
2. TGP, NARO
3. point track destroyer with TMS Up
4. WPN, SOI, narrow FOV, centre destroyer, TMS Up
5. OSB 20 to boresight
6. NWS to switch to station 3
7. uncage
8. TGP, SOI, point track destroyer with TMS Up
9. WPN, SOI, narrow FOV, centre destroyer, TMS Up
10. OSB 20 to boresight
11. F-ACK
12. dogfight master mode
13. a-g master mode
14. TGP, centre ship, TMS up
15. NWS to switch to station 7
16. TGP, centre ship, TMS up
17. C above stations 3 and 7
18. F-ACK
19.test page, clearThe list clears, then re-populates.
-
As an aside, when doing the boresight calibration operationally you never incur a fault. By switching SOI to WPN after the handoff is initiated but before it fails, it is interrupted and no fault occurs while performing the BSGT. The instructions with the training mission are to demonstrate the fault only. I know this is separate from the behavior we’re talking about.
I try a reduced form of your procedure and get not the same issue.
1. Attempt handoff with un-boresighted missile, wait for fault generation.
2. SOI WPN, slew to track and BSGT missile.
3. Cycle in-out DGFT.
4. Attempt handoff again with boresighted missile, wait for completion.
5. CLR on TEST page, fault does not return.I then attempted the full procedure and could not get the issue.
I assume you’re generating the initial fault on step #3 in your post. We can ignore the F-ACK press because it does nothing. However when the PFL message (this includes the minimized “AV” in the corner) disappears is also exactly the same time when the MFL (TEST page) can be cleared without coming back. The PFL entry should clear exactly when the next attempted handoff completes (any missile). So the new hunt is to find a situation where you get a successful handoff but the PFL entry remains.
-
Thanks, Frederf.
I have no idea what’s going on with it. The one thing I have noticed is that when I enter the test page the “C” disappears over station 3.
1.pitch set to alt hold
2.throttle to 85%
3.master mode to a-g
4.sms, select agm65d
5.sms, power on
6.sms, control page, west of, steerpoint 5, auto power on, exit control page
7.icp, nav mode
8.wait 12-15 miles from steerpoint 4
9.icp, a-g mode
10.left mfd, tgp, a-g submode
11.right mfd, wpn page
12.master arm, simulate
13.uncage
14.tgp, slew to destroyer, naro, tms up to point track
15.wpn, slew, fov, tms up, boresight
16.master mode, dogfight
17.master mode a-g
18.tgp, tms up
19.c appears above station 3
20.clear master caution, f-ack, left mfd enter test page
21.c disappears above station 3
22.clear errors
23.errors re-populate -
Please post a video
-
I’m going to put up a temporary video as soon as I can render it. I did notice on a boresighting video that AV is still illuminated on the PFLD after boresighting. I’m guessing if he were to try to clear the fault list the whole thing would light up again. I have to assume AV is meant to clear.
-
(video removed as it has served its purpose and the boresighting process is incomplete)
-
Your AGM65 is still tracking the target after you exit the AG mode. (BTW did you use MSL OVRD or AA mode). At time 2:21 you can clearly see the BSGT adjacent to OSB 20 indicating a valid lock. You then try to handoff with the TGP resulting in a successful handoff.
I would suggest that you break the AGM-65 lock with a transition to DGFT or MSL OVRD and then back to AG mode. If you still see the AGM-65 locked, transfer the SOI to the WPN page a break lock with TMS AFT. You could also try a see if target rejection works and then try to handoff. ( Use TGP and TMS right ).I would also suggest you boresight on a fixed target.See how that works for station 3 .( remember you need to boresight all stations).
A minor detail. You dont need to change the FOV on the WPN page. The TGP will do that for you. Just be sure you in a TGP track mode and change the FOV to NFOV. It will force the WPN page in NFOV
In the real jet you don’t need to be in a track mode to change the WPN FOV. -
Bingo!
And I don’t mean I’m low on fuel.
I had to break the lock on WPN with TMS aft prior to the second handoff. That isn’t mentioned in the training manual, so either it’s an oversight there or it’s a bug, because clearly switching to dogfight mode doesn’t clear all locks.
Thank you, all, thank you, all.
-
Your AGM65 is still tracking the target after you exit the AG mode.
How is that possible? Shouldn’t leaving the AG master mode deselect the missile and break any track?
-
How is that possible? Shouldn’t leaving the AG master mode deselect the missile and break any track?
Maybe not if it’s still tracking your current SPI.
-
How is that possible? Shouldn’t leaving the AG master mode deselect the missile and break any track?
Correct.
It could be the code flipping out with 4 stations loaded.