How come Addwpt doesn't seem to adjust height?

[crixus5678]

Hi,

I am just wondering if this is the correct way for adding waypoint.

0:00:00>Cre A0, A320, 2.8, 105, 100, 8175, 220
0:00:00>Addwpt A0, 2.7, 105.2, 7225, ,
0:00:00>Addwpt A0, 2.6, 105.21, 6475, ,

Because i dont see the altitude at 8175 feet decreasing

[crixus5678]

okay seems like i have to set DEST before the waypoint and it will descend nicely

[jooste]

Hi @crixus5678,

BlueSky tries to mimic as much as possible conventional aircraft autopilot/FMS logic. This means that you need to explicitly enable VNAV to be able to follow speed/altitude constraints in the route.

[crixus5678]

oh okay, noted with thanks

actually is the conflict detection reliable? i tried to model some flight paths from the absd data but there so many conflict and LOS alert. I am not sure is it because i didn't set the speed correctly so there is some inaccuracies in the data (e.g. sensor noise)

[jooste]

The built-in conflict detection is a closed-form analytical solution, which assumes constant velocity, climb rate, and heading. If you cannot assume that these variables are constant within the lookahead time of five minutes (the default) you'll need a conflict detection method that also considers intent. Detection of losses of separation is straightforward, as it only needs to consider the current positions.

[crixus5678]

thank you for the fast reply. So, conflict is like a warning that in the next few minutes or so, the airplanes in conflict will likely be too close, and I can actually ignore it if I only consider the loss of separation as too close between airplanes?

Does the LOS follow the standard LOS definition? Horizontal 5 nautical miles and vertical 1000 feets?

[jooste]

A conflict is indeed a predicted loss of separation. The default separation settings are indeed 5 NM horizontal and 1,000 ft vertical, but these can be configured per aircraft (PZRADIUS and PZHEIGHT).

[crixus5678]

thank you. i shall reevaluate the simulation tomorrow.

[crixus5678]

Thank you for the response so far, just wondering if this is the correct manner of setting the PZRADIUS and PZHEIGHT

0:00:00.00>ASAS ON
0:00:00.00>Cre AC1, A320, 2, 104, 100, 25000, 220
0:00:00.00>AC1, VNAV on
0:00:00.00>PZRADIUS 3, AC1
0:00:00.00>PZHEIGHT 1000,AC1

[jooste]

Yes, that's the correct notation. You can also list more than one aircraft in one call to PZ*.

[crixus5678]

Another question i have is that is it possible for me to leave out the speed component and set the way point by defining the time such that it will auto-calculate the speed and the airplane will definitely reach the waypoint/dest at the specific time?
Is there any example which i can refer to if it is possible?

[jooste]

yes, you can use the RTA function for that! RTA acid wptid time.

[crixus5678]

Hi,

Can i confirm if this is the correct way of using RTA?

0:00:00>Cre TA, E290, J1, 20, 0, 0
0:00:00>Dest TA, D36
0:00:00>Addwpt TA, J14, 0, ,
0:00:00>Addwpt TA, J32, 0, ,
0:00:00>Addwpt TA, J46, 0, ,
0:00:00>Addwpt TA, J30, 0, ,
0:00:00>Addwpt TA, D36, 0, ,
0:00:00>TA, VNAV on
0:00:00>RTA, TA, D36, 00:01.00
0:00:00>TA AT D36 DO DEL TA

Because the speed doesn't appears to automatically adjust and reach D36 within 1 minute

[jooste]

Note that you can get more information on a BlueSky stack function by calling HELP <function name> in the BlueSky command line.

[crixus5678]

okay noted with thanks

[crixus5678]

If i were to try a simple example, is it something like this? I do see the speed adjusting (cap at 317) but i believe the unit of the time is wrong because it doesn't reach the BP waypoint at 00:05

00:00:00.00>ASAS ON
00:00:00.00>TAXI OFF 1
00:00:00.00>Cre KL204,A320, 2.74, 101.70, 120, 2000, 150
00:00:00.00>Pan WMKK
00:00:00.00>Orig KL204,WMKK
00:00:00.00>Dest KL204 WSSS
00:00:00.00>Addwpt KL204 BP, 2500
00:00:00.00>RTA KL204 BP 00:05

EDIT: Seems like there are some internal constraints, experiment with different altitude at 10000 when i added BP as waypoint, the speed adjusted to 400

[jooste]

Yes, the speed envelope varies with aircraft type and altitude.