AGM-65 operation
-
2.8.12.1.11.4 TMS fwd with the SOI on the WPN page commands the Maverick to track. TMS aft breaks track, and the Maverick will return to the commanded LOS.
2.8.12.1.11.8 In non-TGP operations, the SOI moves to the WPN page (if displayed) upon the target designation. If the SOI is on the FCR page with either FTT or GMTT selected, then the SOI moves to the WPN page upon the target designation after the radar has acquired track. If the SOI changes from WPN to another sensor while the selected Maverick is in slew mode, then the Maverick is commanded into SLAVE (BORE) mode.
In BMS, mavericks do not return to the commanded LOS after TMS aft. If the SOI changes to another sensor, the maverick does not get commanded in SLAVE. And most frustratingly, mavericks align well initially, and the first slew control is what causes the ‘misalignment’ causing it to require boresighting.
Is there any hope for any of these bugs to be fixed in 4.33.5?
-
There is always hope.
-
In BMS, mavericks do not return to the commanded LOS after TMS aft. If the SOI changes to another sensor, the maverick does not get commanded in SLAVE. And most frustratingly, mavericks align well initially, and the first slew control is what causes the ‘misalignment’ causing it to require boresighting.
Is there any hope for any of these bugs to be fixed in 4.33.5?
Blu, this is interesting. I’ve not noticed the Mavs going “wonky”. Could the fact I’ve gotten pretty good at the TMS Aft>Wide FOV>cursor zero “manuver” be a factor?
-
If you don’t have a designation you should CAGE MAV…then UNCAGE once you have a designation and they should then slave to that on UNCAGE no matter what the SOI is.
This ROT should help prevent any seeker drift…if there is any.