correct as is JDAM TOO on preexisting WPDSG

[Swift.]

JDAMs in hornet will not target a pre existing waypoint designation if it was created before the weapon was placed into TOO.

JDAMTGT.trk

[BIGNEWY]

Not sure about this one, will have to investigate more, If you are not in TOO when you designate it seem reasonable to me that you would need to designate again to get the coordinates in the TOO parameters when you select TOO, and you can do that currently either by using WPDSG or TDC depress on the Radar / FLIR.

If you have any evidence the designated coordinate should populate the TOO parameters when not in TOO please PM me

thanks 

[Frederf]

22 hours ago, Swift. said:

JDAMs in hornet will not target a pre existing waypoint designation if it was created before the weapon was placed into TOO.

JDAMTGT.trk 187.31 kB · 4 downloads

This is correct behavior. The location is only sent from WPDSG to JDAM target location at the instant of WPDSG creation. If the designation exists and weapons are cycled while that designation exists no location should be sent to the new weapons. Basically the location stream from the designated point to the weapon only happens when the designated location changes. Waypoints don't change so there is no updated info flowing down the pipe to the weapon. Sensors (radar, FLIR, etc.) have small fluctuations in their value which sends a constant stream of updates to the currently selected weapon.

[BIGNEWY]

yes we had a PM together earlier, I just forgot to change the tag, edited now. 

thanks

[Swift.]

51 minutes ago, Frederf said:

This is correct behavior. The location is only sent from WPDSG to JDAM target location at the instant of WPDSG creation. If the designation exists and weapons are cycled while that designation exists no location should be sent to the new weapons. Basically the location stream from the designated point to the weapon only happens when the designated location changes. Waypoints don't change so there is no updated info flowing down the pipe to the weapon. Sensors (radar, FLIR, etc.) have small fluctuations in their value which sends a constant stream of updates to the currently selected weapon.

Perfect thanks for the gouge. What we need to check now I guess is whether the TPOD will update the TOO mission when it slews. I havent had a chance to look yet.

[Tholozor]

37 minutes ago, Swift. said:

Perfect thanks for the gouge. What we need to check now I guess is whether the TPOD will update the TOO mission when it slews. I havent had a chance to look yet.

From my own testing, coordinates will not be written during slews, only when TDC is depressed.

[Swift.]

3 minutes ago, Tholozor said:

From my own testing, coordinates will not be written during slews, only when TDC is depressed.

Does the TGT diamond move with 'undepressed' movements of the TPOD?

Because fundamentally what we are saying is that if the TGT diamond updates, then the JDAM should also update.

Edited May 3, 2022 by Swift.

[Tholozor]

2 minutes ago, Swift. said:

Does the TGT diamond move with 'undepressed' movements of the TPOD?

If the TGT designation was generated by WPDSG, then no. The TGP only became the driving source for the designation after TDC depress.

And even then, the JDAM coordinates were still only written with depress, they did not update constantly.

Edited May 3, 2022 by Tholozor

[Swift.]

22 minutes ago, Tholozor said:

If the TGT designation was generated by WPDSG, then no. The TGP only became the driving source for the designation after TDC depress.

And even then, the JDAM coordinates were still only written with depress, they did not update constantly.

 

So a different bug for a different thread then