Scenario Generator problems

[Joao Pereira 1256632]

I'm trying to make a program that generates scenario files for a specific FIR. I dont understand two things:

 

1- What's the difference between this:

"@N:RZO029:4157:1:38.0:-15.0:30000:0:0:0

$FPRZO029:*A:I:A320:449:LPPT:0623:0623:300:LPPD:01:37:02:18::/v/:KOMUT 38020 BEKUN GOMOS "

 

and this:

"@N:RZO029:4157:1:38.0:-15.0:30000:0:0:0

$FPRZO029:*A:I:A320:449:LPPT:0623:0623:300:LPPD:01:37:02:18

$ROUTE:RZO029:KOMUT 38020 BEKUN GOMOS "

 

I noticed that Euroscope treats these differently but i can't see why from the Scenario File wiki.Supposedly they are the same right?

 

2- A lot of aircrafts are showing the RAM warning in the TAG promptly when the simulation starts. E.g:

"@N:ROZ192:4275:1:41.0:-40.0:38000:0:0:0

$FPROZ192:*A:I:A320:420:KBOS:0551:0551:380:LPPD:02:09:04:27::/v/:41040 39030 SOMUL DOKAS "

Why is this happening? I'm pretty sure i'm introducing the initial aircraft positions correctly

 

Thank you in advance

[David Zhong]

The $ROUTE line describes the flown route, while the route in $FP is only for the flight plan.

 

The $FP route is display in the flight plan window and used for the graphical route, RAM, etc. This is stuff that Euroscope does everyday on the network.

 

$ROUTE is specifically for the simulator. It commands the 'autopilot' to fly a particular sequence of fixes. It can sometimes be useful for this to be different from the flight plan route, for example, a runway-dependant SID/STAR or visual-nav aircraft. For a runway-dependant SID/STAR, Euroscope looks at the airport default runway or the aircraft [Mod - Happy Thoughts]igned runway to p[Mod - Happy Thoughts] the route. If the controller changes this while the aircraft is flying, you don't want the aircraft to suddenly change course!

[Miguel Frias]

Just to complement the info, since João doesn't control:

 

$FP is the flight plan the controller sees. It should contain airways and waypoints:

 

example: LPPT-LPPR

$FP would be: FTM A5 MANIK (old routes, not using new ones)

$ROUTE would be: FTM XAMAX MANIK (to make sure the plane follows the 'exploded' route)

 

 

Also... you can simulate that a pilot filed a correct route, but suddenly goes elsewhere:

$ROUTE = FTM XAMAX ABLEG

 

This will allow automatic insertion of a "pilot error"

 

 

Regarding the RAM error: the oceanic coordinates are probably not in the sector file. Therefore, Euroscope "thinks" the aircraft are not following the [Mod - Happy Thoughts]igned route.

[Joao Pereira 1256632]

Ah ok, now i understand. Thank you guys

 

@Miguel Frias. So i need to manually input all the waypoints of the FIR i want (in my case the Santa Maria) in the Sector file?

 

I have one other doubt that i hope you can dissipate:

 

-In the plug-in making there are a lot of functions to get the next FIR waypoint, get the exit FIR waypoint, the exit FIR time prediciton, etc. But to do that i need to set my active FIR inside the plug-in right? I found a void SelectActiveSectorFile(void) function but can't use it properly. Is this the right way to go?

[Miguel Frias]

If you're using Santa Maria area, you should use our own LPPO sector file. If you are using Lisboa Control area (LPPC) then use that sector file.

 

If you need both, then you must create a sort of merge between the two, by copying the [FIXES] section of both files (and maybe even VOR/NDB, etc).

[Joao Pereira 1256632]

Have a new question, sry guys

 

For example this FP:

@N:BAW930:4751:1:35.0:-30.0:34000:0:0:0

$FPBAW930:*A:I:A320:445:EGLL:0628:0628:340:SBGR:01:32:04:08::/v/:4520N 4027N 3530N 3033N 2536N 2038N 1340N

 

when the simulation starts, the airplane is drew at 3530N (i can see it there and if i ask the plug-in to tell me the last point where it was it gives 3530N) and instead of going to the next waypoint (3033N) it starts going to the right. This explains all the RAM signals in the TAGs

 

Is this happening because i didn't put heading in the FP?

 

Edit: Calculated the heading between the 2 waypoints (~210º), converted it with the scenario file advice: ( Heading * 2.88 + 0.5 ) * 4. and still the aircraft starts going East instead of West South

Edited April 3, 2014 at 03:09 AM by Guest

[Joao Pereira 1256632]

If you're using Santa Maria area, you should use our own LPPO sector file. If you are using Lisboa Control area (LPPC) then use that sector file.

 

If you need both, then you must create a sort of merge between the two, by copying the [FIXES] section of both files (and maybe even VOR/NDB, etc).

 

I have the LPPO's sector file

[Todor Atanasov 878664]

I don't see the $ROUTE part.

[Miguel Frias]

I have the LPPO's sector file

Whatever you find listed in the VOR/NDB or FIXES section, you can use as part of route. Not sure which version you have but you can create any lat/long waypoint manually example:

 

[FIXES]

...

3820N N038.00.00.000 W020.00.00.000

...

[Joao Pereira 1256632]

I don't see the $ROUTE part.

 

On wiki it says that the $ROUTE part is optional.

 

But even if i put it like this:

 

$ROUTE:BAW930:4520N 4027N 3530N 3033N 2536N 2038N 1340N

 

the aircraft starts going East...

[Todor Atanasov 878664]

Can you show us the points defined in the sct file

[Joao Pereira 1256632]

Can you show us the points defined in the sct file

 

 

The 2 points in question in the SCT file:

"3530N N035.00.00.000 W030.00.00.000 ; - N35 00 W030 00

3033N N030.00.00.000 W033.00.00.000 ; - N30 00 W033 00"

 

When i'm in Euroscope and i go to the "Display Settings->Show Fixes" it displayes all the corret fixes so i don'believe the problem is there.

[Todor Atanasov 878664]

Have a new question, sry guys

 

For example this FP:

@N:BAW930:4751:1:35.0:-30.0:34000:0:0:0

$FPBAW930:*A:I:A320:445:EGLL:0628:0628:340:SBGR:01:32:04:08::/v/:4520N 4027N 3530N 3033N 2536N 2038N 1340N

 

when the simulation starts, the airplane is drew at 3530N (i can see it there and if i ask the plug-in to tell me the last point where it was it gives 3530N) and instead of going to the next waypoint (3033N) it starts going to the right. This explains all the RAM signals in the TAGs

 

Is this happening because i didn't put heading in the FP?

 

Edit: Calculated the heading between the 2 waypoints (~210º), converted it with the scenario file advice: ( Heading * 2.88 + 0.5 ) * 4. and still the aircraft starts going East instead of West South

 

It is doing what you have told him to do

 

You have said to the simulator: "create a traffic at these coordinates :@N:BAW930:4751:1:35.0:-30.0:34000:0:0:0 and then follow the route starting from point 4520N with coordinates N45.00.00.000 E20.00.00.000".

 

Also use the N/S and W/E in the scenario, not +/-

[Joao Pereira 1256632]

Have a new question, sry guys

 

For example this FP:

@N:BAW930:4751:1:35.0:-30.0:34000:0:0:0

$FPBAW930:*A:I:A320:445:EGLL:0628:0628:340:SBGR:01:32:04:08::/v/:4520N 4027N 3530N 3033N 2536N 2038N 1340N

 

when the simulation starts, the airplane is drew at 3530N (i can see it there and if i ask the plug-in to tell me the last point where it was it gives 3530N) and instead of going to the next waypoint (3033N) it starts going to the right. This explains all the RAM signals in the TAGs

 

Is this happening because i didn't put heading in the FP?

 

Edit: Calculated the heading between the 2 waypoints (~210º), converted it with the scenario file advice: ( Heading * 2.88 + 0.5 ) * 4. and still the aircraft starts going East instead of West South

 

It is doing what you have told him to do

 

You have said to the simulator: "create a traffic at these coordinates :@N:BAW930:4751:1:35.0:-30.0:34000:0:0:0 and then follow the route starting from point 4520N with coordinates N45.00.00.000 E20.00.00.000".

 

Also use the N/S and W/E in the scenario, not +/-

 

 

Ah ok, i didn't knew that's how route worked. I thought that by putting the aircraft on 3530N he would start its route there and follow for the next waypoint on the Route.

 

Ty for the info mate

 

So, is there any way to put some last waypoints of the aircraft in the scneario file without it following them (because its the past)? Because i will probably need those past waypoints as soon as the aircraft is drew for plug-in sake

[Todor Atanasov 878664]

That is where the $ROUTE part comes along. Simply put there the next points, and the $FP will have the full route

[Joao Pereira 1256632]

That's it Todor, thank you for the help!

[Todor Atanasov 878664]

No problem

[Gergely Csernak]

I don't see the $ROUTE part.

On wiki it says that the $ROUTE part is optional.

 

Sorry guys. It seems to be an error on my side. We are just editing the WIKI pages to be modified for the upcoming v3.2. And it seems that the scenario file description was edited by me in the current page not in the new version. I restored the original one now.

In 3.1 the $ROUTE is not optional. You must specify it. In 3.2 it will really be optional, and if missing the route for the simulator will be extracted from $FP line. Consider this if you are building your own generator at the moment. Also there will be some more additional parameters you may want to define.

Also note that if you simulate a flying aircraft, the heading data is just ignored. The plane will be heading to the next point along the route.

[Joao Pereira 1256632]

Also there will be some more additional parameters you may want to define.

 

Which additional parameters are you talking about?

[Joao Pereira 1256632]

Also use the N/S and W/E in the scenario, not +/-

 

For people who check this thread in the future, i just want to say that this is very important. I still had errors in the places where the aircrafts were displayed and solved them by aplying Todor's advice

[Gergely Csernak]

Also there will be some more additional parameters you may want to define.

 

Which additional parameters are you talking about?

 

Things like:

 

- Predefined routes for missed approach, traffic pattern, visual approach,

- METAR lines for tower simulator,

- Initial pseudo pilot callsign,

- plane type, livery, taxiway usage, maximum taxi speed