Jump to content

[REPORTED] TOT Behavior where WO/S exists


Recommended Posts

Posted

Apologies for the long post. Hopefully succinct and with evidence and tracks.

 

Case 1) Direct routing to a selected point:

With a WO/S present, waypoint steering selected and nothing designated, TOT should be to the offset via the waypoint (you must manually select the WO/S steering once over the waypoint i.e., with the EHSD or WOF). Ref: TACMAN Vol.1 1.15.6.1.1 Direct Routing.

 

At present, TOT only takes you to the waypoint. See attached track ("AV8B - TOT WOS.trk").

 

With WO/S present, waypoint steering selected and the waypoint designated, TOT is to the waypoint direct. Ref: TACMAN Vol.1 1.15.6.1.1 Direct Routing.

This functions correctly, no track attached.

 

With WO/S present, WO/S steering selected (designated or not), TOT is to the WO/S direct. Ref: TACMAN Vol.1 1.15.6.1.1 Direct Routing.

This functions correctly, no track attached.

 

Case 2) Sequential Routing

Where WO/S exists for the TERM waypoint, the SEQ string is from waypoint 0 to the TERM WO/S. I.e., if waypoint 3 is TERM and WO/S3 exists then the string is:
W0 -> W1 -> W2 -> W3 -> WO/S3
This is currently correct (you have to designate WO/S manually at the term waypoint but I assume this is correct behavior based on the NSEQ overlay below). However, TOT should be to the TERM WO/S rather than the (current) TERM waypoint.
Ref: TACMAN Vol.1 1.15.6.1.2 Sequential Routing

 

At present, TOT only goes to the TERM waypoint even if a TERM WO/S exists (no track for this, but I have a track for the NSEQ version below and it is essentially the same problem).

 

Case 3) Non-Sequential Routing

Where WO/S exists for the final IGRS waypoint, the NSEQ string is through all the intermediate waypoints to the final IGRS WO/S. I.e., if the IGRS string is "5, 4, 3", and the EGRS string is “2, 1" and WO/S3 exists then the string is:
W5 -> W4-> W3 -> WO/S3 …. -> W2 -> W1
This is currently correct (as before you have to designate WO/S manually at the final IGRS waypoint). I even noticed from the NSEQ overlay that the string is correctly routed through the WO/S (i.e., the EGRS starts from the IGRS WO/S). However, TOT should be to the final IGRS WO/S (if it exists) rather than the (current) final IGRS waypoint.
Ref: TACMAN Vol.1 1.15.6.1.3 Non-sequential Routing

 

See track attached ("AV8B - NSEQ WOS TOT.trk").


Note: In my initial post on this on the post about the CS/T bug, I incorrectly stated that the SEQ and NSEQ strings should be through all intermediate WO/S as this is what is stated in the copy of the TACMAN I have access to (2002). However it would appear from more recent NATOPS (2008) that this was changed in H4.0 and beyond so current routing is correct, just not TOT: "With H4.0 only the offset to TERM in SEQ string or the final point of the IGRS string of a NSEQ route shall be included in a route” Ref: NATOPS (2008) 23.9.24 NSEQ Pushbutton
 

AV8B - TOT WOS.trk AV8B - NSEQ WOS TOT.trk

  • 1 month later...
  • AlphaJuliet changed the title to [REPORTED] TOT Behavior where WO/S exists
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...