source: doc/manual/en/index.html@ 255:2274102b5b1c

Last change on this file since 255:2274102b5b1c was 255:2274102b5b1c, checked in by István Váradi <ivaradi@…>, 12 years ago

Minor fixes
File size: 39.7 KB
Line 
1<html>
2<head>
3 <title>MAVA Logger X User's Manual</title>
4 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
5</head>
6<body>
7 <div align="center"><h1>MAVA Logger X User's Manual</h1></div>
8
9 <h2><a name="overview">Overview</a></h2>
10
11 <p>
12 MAVA Logger X is an application that monitors the execution of a
13 Malév Virtual flight, and collects data that can be sent to
14 the <a href="http://virtualairlines.hu">MAVA website</a> for further
15 evaluation. This manual describes how to use this program. To be
16 able to use all features of the program, you need to have a working
17 Internet connection, even if you don't fly on-line on VATSIM or
18 IVAO. However, it is possible to perform a flight completely offline
19 as well.
20 </p>
21
22 <p><a name="flightRating"/>
23 While monitoring your flight, the program continuously checks if your
24 airplane's configuration is always within the parameters prescribed
25 by the airline's operating procedures. For example, you have to turn
26 on or off the various lights of your aircraft according to rules,
27 you cannot exceed certain weight or speed limits, and so on. Any
28 deviation from the expected parameters, also known as a fault, can
29 result in points subtracted from the initial 100 points (or
30 percentage). The result is your <i>flight rating</i>. Some
31 deviations are so serious, that they are deemed <i>NO GO</i> faults
32 and result in the rejection of your flight.
33 </p>
34
35 <p>
36 Besides the faults the program also monitors many other parameters,
37 which are recorded in a textual <a href="#logTab"><i>log</i></a>.
38 This log is sent as a part of your PIREP
39 (<b>PI</b>lot's <b>REP</b>ort), and will be analyzed, and possibly
40 commented on by more experienced pilots of Malév Virtual. This way
41 you can perfect the way you execute your flights.
42 </p>
43
44 <p><a name="flightStages"/>
45 The application breaks up your flight into
46 several <i>stage</i>s. The advancement from one stage to another is
47 detected automatically. These stages and the conditions under which
48 they are entered are as follows:
49 <ol>
50 <li><b>boarding</b>: This is the initial stage when you start the
51 flight.</li>
52 <li><b>push-back and taxi</b>: If you release the parking brakes
53 or your ground speed becomes 5 knots or greater during the
54 boarding stage, your flight enters this stage.</li>
55 <li><b>takeoff</b>: If you turn on the landing and/or the strobe
56 lights or your ground speed exceeds 80 knots during taxi or after
57 a rejected takeoff (RTO).</li>
58 <li><b>climb</b>: When you retract the gears or you reach 3000
59 feet altitude AGL with a positive climb rate after takeoff.</li>
60 <li><b>RTO</b>: If you switch off both the landing and the
61 strobe lights, and your speed is reduced below 50 knots while on
62 the ground during takeoff.</li>
63 <li><b>cruise</b>: When the aircraft's altitude is within 2000
64 feet of the cruise altitude and you are climbing.</li>
65 <li><b>descent</b>: If the altitude decreases to more than 2000
66 feet below the cruise altitude during cruise.</li>
67 <li><b>landing</b>: If the gears are lowered and the altitude is
68 less than 2000 feet AGL during descent or go-around.</li>
69 <li><b>go-around</b>: If you retract the gears during landing.</li>
70 <li><b>taxi after landing</b>: When the aircraft is in the
71 ground and its ground speed is below 50 knots after landing.</li>
72 <li><b>parking</b>: If the parking brake is activated after taxi.</li>
73 <li><b>end</b>: If the N<sub>1</sub> of the turbines becomes
74 less than 0.5, or the RPM of the piston engines becomes 0 during
75 parking. This is the final stage.</li>
76 </ol>
77
78 <p>
79 To enhance the simulation, the program can play various
80 <a href="#prefsSounds">sound</a> files
81 during the various stages of your flight, such as the announcements
82 made by the flight attendants. These files are supplied with the
83 application, and they can be played automatically, or when you press
84 a certain hotkey in the flight simulator. You can also organize
85 pre-recorded sound files
86 into <a href="#checklistEditor">checklists</a> for the each aircraft
87 type, and these files can also be played back one-by-one when you
88 repeatedly press a key combination in the simulator. See
89 <a href="#prefsSounds">below</a> for more information on this.
90 </p>
91
92 <p><a name="onlineACARSSystem"/>
93 Malév Virtual have implemented an <i>Online ACARS System</i>, which
94 displays the status of the flights in progress. The data appears on
95 the front page of the MAVA website and also on a map.
96 </p>
97
98 <p><a name="onlineGateSystem"/>
99 Malév Virtual have also implemented an <i>Online Gate System</i>
100 which maintains a database of the aircraft in the airline's fleet
101 and their location. An aircraft may be parked at the Budapest
102 Ferihegy Airport, in which case the number of the gate or stand it
103 is located at is recorded in the database. If so, this number is
104 displayed to you when starting your flight from Ferihegy, and you
105 are recommended to place your aircraft at the indicated gate or
106 stand in the simulator. If your flight begins at Ferihegy and the
107 aircraft is away (usually due to someone else's flight), you can
108 select from which gate or stand you start your flight. The database
109 of the Online Gate System can also be displayed by using the
110 application.
111 </p>
112
113 <p>
114 These online systems can only be used when flying online.
115 </p>
116
117 <p>
118 The program can automatically update itself. When it starts up, it
119 checks if there is a newer version available. If so, it downloads
120 its files and replaces the program's current files with the new
121 ones. Then the program is restarted so that you can use the new
122 version. Besides acquiring bug fixes, updating is also important,
123 because the program can be extended with new checks or more refined
124 checks, and if you are using too old a version, the PIREP reviewers
125 may refuse your flight.
126 </p>
127
128 <h3><a name="gui">Graphical User Interface</a></h3>
129
130 <p>
131 The GUI of the application is made up of traditional building blocks
132 (buttons, checkboxes, lists, text entry boxes, etc.) found in other
133 applications as well. Many such controls have informative tooltips
134 that supplement the contents of this User's Guide in helping you
135 using the application. Many controls are also accessible by pressing
136 the <b>Alt</b> plus the underlined letter in the control's label.
137 </p>
138
139 <p>
140 The most often used part of the program is the main window, to be
141 described in detail below. When you minimize or close the window, it
142 disappears by default, but the program continues to run. You can
143 redisplay the window by clicking on the tray icon of the program,
144 which looks like the one on the picture below.
145 </p>
146
147 <div align="center">
148 <table>
149 <tr>
150 <td>
151 <img src="statusIcon1.png" alt="The status icon" hspace="20"/>
152 </td>
153 <td>
154 <img src="statusIcon2.png" alt="The status icon menu" hspace="20"/>
155 </td>
156 </table>
157 </div>
158
159 <p>
160 If you click on the tray icon when the program's window is hidden,
161 the window will be displayed. If you hover the mouse pointer over
162 the icon, the flight stage and the current rating will be
163 displayed. The tray icon has a right-button menu as well with the
164 following items:
165 <ul>
166 <li><b>Show main window</b>: displays or hides the main window.</li>
167 <li><b>Show monitor window</b>: displays or hides the monitor
168 window (see below).</li>
169 <li><b>Quit</b>: quit the application. A confirmation window will
170 be displayed.</li>
171 </ul>
172 </p>
173
174 <p>
175 You can also quit the application by selecting the <b>File/Quit</b>
176 menu item, or by pressing <b>Ctrl+Q</b>.
177 </p>
178
179 <p>
180 If you start the application, when it is already running, the main
181 window of the already running instance will be displayed instead of
182 starting a new instance of the program.
183 </p>
184
185 <h2><a name="mainWindow">The Main Window</a></h2>
186
187 <p>
188 The figure below depicts the main window of the application. The top
189 of it contains the usual menu bar, which will be described in more
190 detail later. The content area consists of several tabs the use of
191 which is described below.
192 </p>
193
194 <a name="mainWindowShot"/>
195 <div align="center"><img src="mainWindow.png" alt="The main window"/></div>
196
197 <p>
198 The bottom of the window is a status bar. Its left side contains the
199 icon indicating the status of the connection to the simulator. Since
200 the application continuously monitors the parameters of your
201 aircraft, it needs to communicate with the simulator. The icon's
202 colour indicates the health of this communication channel.
203 </p>
204
205 <p>
206 If it is grey, the program is not connected. This is normal before
207 and after the flight. If it is green, the connection is alive and
208 working properly. If it is red, the connection is broken. In this
209 case a dialog window is displayed. The most likely cause for such a
210 disruption is the crash of the simulator. If this is the case,
211 restart the simulator and try to restore the flight to a state as
212 close to the one before the crash as possible. Then click
213 the <b>Reconnect</b> button, and the program will try to
214 re-establish the connection to the simulator. It preserves all data
215 of your flight, so you can continue where you left off easily.
216 </p>
217
218 <p>
219 If the reason for the failure of the connection is something else,
220 do whatever is needed to be done to restore it. Of course, it is
221 possible that the logger application itself fails, in which case
222 you, unfortunately, have to restart the flight. Do not forget to
223 notify the author if this happens. In this case, try to copy and
224 save the <a href="#debugLog">debug log</a> and send it with your bug
225 report.
226 </p>
227
228 <p>
229 If you click the <b>Cancel</b> button in the reconnection dialog,
230 the logger will be reset as if it were stopped and restarted.
231 </p>
232
233 <p>
234 To the right of the connection status icon, you can see the current
235 <a href="#flightStages">stage</a> of the flight, if the monitoring
236 has begun. Otherwise it is a single dash. It is followed by the
237 simulator time, if the program is already connected to the
238 simulator. Then comes the current <a href="#flightRating">flight rating</a>.
239 </p>
240
241 <p>
242 The right of the status bar is normally empty, but if there is some
243 potentially long operation going on (typically communicating with
244 the MAVA servers), information about the operation is displayed
245 here. This is accompanied by the cursor becoming that of signaling
246 a busy state and most parts of the main window becoming
247 unresponsive.
248 </p>
249
250 <h3><a name="tabFlight">The Flight Tab</a></h3>
251
252 <p>
253 The flight tab is the most important tab. It consists of a sequence of
254 pages similar to wizards found in many programs. The first several of
255 these pages guide you through the various steps of the preparations
256 for your flight, while the last pages allow you to enter some
257 information about your flight necessary for its evaluation and to
258 send the PIREP (Pilot's Report) assembled by the program to the MAVA
259 server.
260 </p>
261
262 <p>
263 Each page has a title at the top indicating the purpose of the
264 page. There is a short text below this, which describes what the
265 page contains and/or what is expected from you to do with the page.
266 Below the text you can find the main information and possibly data
267 entry areas for the page. Finally, you can find the button row at
268 the bottom.
269 </p>
270
271 <p>
272 Most of the pages contain two buttons: <b>Next</b> and
273 <b>Previous</b>. These help in navigating between the pages. In most
274 cases you can go back to previously visited pages by using
275 the <b>Previous</b> button, although you cannot edit the contents of
276 some of the pages once finalized by moving to the next page using
277 the <b>Next</b> button. There are a few exceptions though, as
278 detailed below.
279 </p>
280
281 <p>
282 Many of the pages also contain a <b>Cancel flight</b>
283 button. Clicking this button will allow you to cancel the flight and
284 go back to the <a href="#flightSelectionPage">flight selection</a>
285 if you have logged in to the MAVA server, or to the login page, after
286 a confirmation of your intent.
287 </p>
288
289 <h4><a name="loginPage">The <i>Login</i> Page</a></h4>
290
291 <p>
292 The program starts with the Login page (see the
293 <a href="#mainWindowShot">picture</a> above) where you can enter the
294 your pilot's ID and password for the MAVA website. Both data are
295 given to you when joining Malév Virtual. The pilot's ID usually
296 starts with the letter <q>P</q> followed by three digits.
297 </p>
298
299 <p>
300 If you check <b>Remember password</b>, the password will be saved by
301 the program, so you don't have to enter it all the time. Note,
302 however, that the password is saved in a readable form into a
303 configuration file, so you this possibility only if your home
304 directory can be accessed only by people you trust. The pilot's ID
305 is saved anyway.
306 </p>
307
308 <p>
309 If you are about to perform the entrance flight, check
310 <b>Entrance exam</b>. In this case you don't have to (and cannot)
311 enter the password, as that is not needed for the entrance exam.
312 </p>
313
314 <p>
315 The login to the MAVA server, and proceed to the next page, press
316 the <b>Login</b> button.
317 </p>
318
319 <p>
320 If you would like to fly without an Internet connection, use
321 the <b>Fly offline</b> button. This immediately takes you to the
322 next page, without trying to log in to the MAVA server.
323 </p>
324
325 <h4><a name="flightSelectionPage">The <i>Flight selection</i> Page</a></h4>
326
327 <img src="flightSelection.png" alt="The Flight selection page"/>
328
329 <p>
330 This page displays the list of the flight you have booked previously
331 on the MAVA website, if you have <a href="#loginPage">logged in</a>
332 properly. If you chose to fly offline, the list is empty.
333 </p>
334
335 <p>
336 If you have selected a flight, you can also save it by using
337 the <b>Save flight</b> button. This is useful when planning to fly
338 offline at some later time. When preparing for that flight, you can
339 properly log in to the MAVA server, and acquire the list of your
340 booked flights. Then you can save the flight you wish to perform
341 later offline, on which occasion, you can load the saved flight.
342 </p>
343
344 <p>
345 You may need to refresh the list of flights. For example, you notice
346 that you have forgotten to book the flight you want to perform. Then
347 you can book the flight on the MAVA website, and press
348 the <b>Refresh flights</b> button to update the list.
349 </p>
350
351 <p>
352 You can also load a flight from a file by pressing the <b>Load
353 flight from file</b> button. This displays a file selection dialog
354 where you select the flight file (usually with a suffix
355 of <code>.vaflight</code>). This is mostly useful when flying
356 offline, or during the entrance exam.
357 </p>
358
359 <p>
360 Select a flight from the list, and press the <b>Next</b> button to
361 proceed with that flight.
362 </p>
363
364 <h4><a name="gataSelectionPage">The <i>LHBP gate selection</i> Page</a></h4>
365
366 <img src="gateSelection.png" alt="The LHBP gate selection page"/>
367
368 <p>
369 This page is displayed after the flight selection page only if your
370 flight starts at the Budapest Ferihegy Airport and the number of the
371 gate or stand at which your aircraft is located cannot be
372 determined.
373 </p>
374
375 <p>
376 Select a number from the list presented, and press <b>Next</b>.
377 </p>
378
379 <h4><a name="connectPage">The <i>Connect to the simulator</i> Page</a></h4>
380
381 <img src="connect.png" alt="The Connect to the simulator page"/>
382
383 <p>
384 This page displays some important information about your flight,
385 such as the type and tail number of the aircraft to use, the
386 departure airport and possibly the gate.
387 </p>
388
389 <p>
390 Select the aircraft indicated and park it at the departure airport
391 in the simulator,
392 then press <b>Connect</b> to establish the connection with the
393 simulator. If the connection cannot be established, a dialog will be
394 displayed about it, and you can <b>Try again</b> the connection
395 or <b>Cancel</b> to go back to the flight selection or to the login page.
396 </p>
397
398 <p>
399 Note, that after a successful connection, the monitoring of your
400 flight does not begin immediately, but some data can be queried by
401 the logger at this stage.
402 </p>
403
404 <h4><a name="payloadPage">The <i>Payload</i> Page</a></h4>
405
406 <img src="payload.png" alt="The Payload page"/>
407
408 <p>
409 This page displays the components of the flight's payload and the
410 calculated Zero-Fuel Weight (ZFW). You can enter here the cargo
411 weight you determined for your flight. You can also press the <b>ZFW
412 from FS</b> button, which queries the ZFW from the simulator and
413 displays the retrieved value. If the ZFW calculated from the payload
414 data differs too much from the queried one, the calculated value is
415 displayed in red. This the right time to set up the payload in the
416 simulator. If you forget about it, it will be a NO GO fault.
417 </p>
418
419 <p>
420 If you have finished with this page, press the <b>Next</b>
421 button. At this point, the <a href="#helpTab"><i>Help</i> tab</a>
422 becomes available, which you can use if you have failed to set up
423 the correct payload in the simulator. See a more detailed
424 description of it <a href="#helpTab">below</a>.
425 </p>
426
427 <h4><a name="timePage">The <i>Time</i> Page</a></h4>
428
429 <img src="time.png" alt="The Time page"/>
430
431 <p>
432 This page displays the departure and arrival times of your
433 flight in UTC. Press the <b>Time from FS</b> button to query the
434 current UTC time of the simulator. To be able to simulate the real
435 lighting circumstances of the flight, the simulator's time should match
436 the time of the flight according to the schedule. Therefore you are
437 expected to set the simulator's time properly. It is recommended to
438 set it to about 15 minutes before the departure at this stage so
439 that you have enough time to set up your flight.
440 </p>
441
442 <p>
443 When you have set the time of the simulator properly, press
444 the <b>Next</b> button.
445 </p>
446
447 <h4><a name="fuelPage">The <i>Fuel</i> Page</a></h4>
448
449 <img src="fuel.png" alt="The Fuel page"/>
450
451 <p>
452 This page contains a graphical representation of the fuel tanks of
453 your aircraft. The yellowish colour represents the current level of
454 the fuel in the tank, and turquoise slider is the expected level,
455 which is also displayed numerically (in kilograms) below each graph.
456 </p>
457
458 <p>
459 You can enter the requested amount of fuel numerically, or you can
460 set it by the turquoise sliders, though this method is less accurate. The
461 lever can be moved by clicking withinin the fuel tank's representation,
462 and you can drag it if you keep the button pressed. If your mouse
463 has a wheel, that can also be used to modify the expected level. To
464 use the wheel, keep the mouse pointer within the fuel tank's
465 graphic. Each click of the wheel increment or decrements the amount
466 by 10 kilograms. If you hold down the <b>Shift</b> key, the
467 increment will be 100, if you hold down the <b>Ctrl</b> key, the
468 increment will be 1.
469 </p>
470
471 <p>
472 When all tanks have the correct amount of fuel set, press
473 the <b>Next</b> button. This causes the pumping of the fuel to
474 start. The progress is represented by the yellowish fuel bars
475 growing or shrinking (fuel may be pumped out of a tank as
476 well). This is a relatively quick process and should finish within a
477 few seconds.
478 </p>
479
480 <h4><a name="routePage">The <i>Route</i> Page</a></h4>
481
482 <img src="route.png" alt="The Route page"/>
483
484 <p>
485 This page displays the cruise level and the flight plan route. The
486 cruise level starts out at FL240, but the route comes from the
487 booked flight. Set the cruise level to the one you have calculated
488 with, and modify the flight plan if needed. For example, if you will
489 enter some airspace that will require you to change the flight
490 level, you should add that here.
491 </p>
492
493 <p>
494 When satisfied with the information on the page, press
495 the <b>Next</b> button to advance. Note, that these data can be
496 edited later as well if you come back to this page.
497 </p>
498
499 <h4><a name="briefingPage">The <i>Briefing</i> Pages</a></h4>
500
501 <img src="briefing.png" alt="The Briefing page"/>
502
503 <p>
504 These pages display the NOTAMs and the METAR for the departure and
505 the arrival airports. You can edit the METAR if your network
506 provides a different weather, or you do not fly with real
507 weather. The METAR of the arrival airport will be updated when
508 entering the landing stage, unless you have edited it before. The
509 METARs can be edited during the whole duration of the flight. If you
510 do so, please, comment on it in the <i>Comments</i> section of
511 the <a href="#flightInfoTab"><i>Flight info</i> tab</a>.
512 </p>
513
514 <p>
515 On the second briefing page (that of the arrival airport), confirm
516 that you have read the briefing and are ready to start the flight by
517 clicking the button. This begins the monitoring of your flight with
518 the boarding stage.
519 </p>
520
521 <h4><a name="takeoffPage">The <i>Takeoff</i> Page</a></h4>
522
523 <img src="takeoff.png" alt="The Takeoff page"/>
524
525 <p>
526 On this page you have to enter the name of the departure runway, the
527 name of the Standard Instrument Departure procedure you follow after
528 takeoff and the takeoff V-speeds. While you can edit these data
529 anytime, it is recommended to do so before takeoff.
530 <p>
531
532 <p>
533 Note that if you are flying one of the Tupolev or Yak aircraft, the
534 page will look different, as speeds will have to be entered in
535 kilometres per hour.
536 </p>
537
538 <p>
539 You can proceed to the next page after takeoff, and if all data has
540 been entered, by pressing the <b>Next</b> button.
541 </p>
542
543 <h4><a name="landingPage">The <i>Landing</i> Page</a></h4>
544
545 <img src="landing.png" alt="The Landing page"/>
546
547 <p>
548 On this page you have to enter the name of the STAR and/or
549 transition you planned to follow (even if you get a different one,
550 or simply vectors from ATC, in which case add a
551 <a href="#flightInfoTab">comment</a> about it),
552 the approach type (e.g. <q>ILS</q>, <q>VOR</q>, <q>VISUAL</q>,
553 etc.), the name of the landing runway, and the landing reference speed,
554 V<sub>ref</sub>. You can enter this data during the flight, or after
555 you have landed, at your discretion. Note, that if you fly one of
556 the Tupolev or Yak aircraft, the speed will have to be entered in km/h.
557 </p>
558
559 <p>
560 When you have entered all data, press the <b>Next</b> button. It is
561 active only, if the flight has ended.
562 </p>
563
564 <h4><a name="finishPage">The <i>Finish</i> Page</a></h4>
565
566 <img src="finish.png" alt="The Finish page"/>
567
568 <p>
569 This is the final page of the flight wizard. It contains a summary
570 of your flight: the rating, the flight and block times, the distance
571 flown and the amount of fuel burnt.
572 </p>
573
574 <p>
575 You also have to provide a few pieces of information. You have to
576 select the type of the flight from the list provided (scheduled,
577 old-timer, VIP, charter) and whether it was an online flight or
578 not. If you arrive at the Budapest Ferihegy Airport, and are using
579 the Online Gate System, you also need to specify the number of the
580 gate or stand you have parked you aircraft at.
581 </p>
582
583 <p>
584 With all data entered, you may want it review your flight (i.e. the
585 earlier pages or some of the other tabs), then save or send the
586 PIREP created from it. These can be accomplished by pressing one of
587 the buttons at the bottom. A saved PIREP can be loaded later and
588 sent, if the sending fails for some reason. When a PIREP is sent, it
589 becomes available for review by the designated PIREP reviewers of
590 Malév Virtual.
591 </p>
592
593 <p>
594 You can also start a new flight using the <b>New flight</b>
595 button. If you have not saved or sent the PIREP, you will be asked
596 to confirm your intention. When starting a new flight you are taken
597 to the <a href="#flightSelectionPage">flight selection page</a>, if
598 you have logged in to the MAVA server, or to
599 the <a href="#loginPage">login page</a>, if your flight has been an
600 offline flight.
601 </p>
602
603 <h3><a name="flightInfoTab">The Flight info Tab</a></h3>
604
605 <img src="flightInfoTab.png" alt="The Flight info tab"/>
606
607 <p>
608 This tab allows one to enter some additional information about the
609 flight, if necessary.
610 </p>
611
612 <p>
613 The <i>Comments</i> text area should contain any general information
614 that you would like the PIREP reviewer to know about. For example,
615 why you changed the METAR, why you lowered the gears accidentally
616 (i.e. pressed the wrong key on the keyboard), etc.
617 </p>
618
619 <p>
620 The <i>Flight defects</i> text area should contain information about
621 any problems you encountered with the plane during the flight. For
622 example an engine stopped and why (if known), that flaps could not
623 be extended or retracted, etc.
624 </p>
625
626 <p>
627 In the <i>Delay codes</i> area you can mark one or more reasons why
628 the flight was delayed, if it was. The options are self-explanatory.
629 </p>
630
631 <h3><a name="helpTab">The Help Tab</a></h3>
632
633 <img src="helpTab.png" alt="The Help tab"/>
634
635 <p>
636 This tab provides some help for calculating and setting the payload
637 weight of the aircraft. It can be used once the
638 <a href="#payloadPage"><i>Payload</i></a>
639 (i.e. the cargo weight) is finalized. To use this tab, check
640 the <b>Using help</b> checkbox. It causes the page to become
641 sensitive and filled with data. Note, that the fact of using the
642 help is <a href="#logTab">logged</a>, so the PIREP reviewers will
643 know about it.
644 </p>
645
646 <p>
647 The most important information is after the <i>Payload:</i> label,
648 which is the payload weight of the aircraft. This value should be
649 set in the simulator as the airplane's payload weight. By pressing
650 the <b>Simulator data</b> button, the data coming from the simulator
651 can be queried and displayed. If the data is out of the tolerances,
652 it is displayed in red, otherwise in green.
653 </p>
654
655 <p>
656 The gross weight is also displayed with some maximum weights of the
657 aircraft, so it can be checked or estimated if you will remain within
658 those maximums during the flight.
659 </p>
660
661 <h3><a name="logTab">The Log Tab</a></h3>
662
663 <img src="logTab.png" alt="The Log tab"/>
664
665 <p>
666 This is the main log of your flight that will be analyzed by the
667 PIREP reviewers. Its contents is generated automatically by the
668 program, and most lines are prefixed by the simulator times the
669 information in the given line belongs to.
670 </p>
671
672 <p>
673 While the log's contents is mainly useful for PIREP reviewers, it
674 can come handy when things start to happen very fast, and you have
675 no time check each fault message passing by (if you have enabled
676 such messages at all). Later, when things calm down, you can check
677 the log to see what happened exactly, so that you know why so many
678 fault points have been awarded. For example, you may even decide to
679 abort the flight, if you think some of the faults are too
680 embarrassing :) For quick identification, the lines containing the
681 fault messages are highlighted.
682 </p>
683
684 <h3><a name="gatesTab">The Gates Tab</a></h3>
685
686 <img src="gatesTab.png" alt="The Gates tab"/>
687
688 <p>
689 This tab displays information retrieved from
690 the MAVA <a href="#onlineGateSystem">Online Gate System</a>.
691 If the program needs to retrieve data, this tab's contents
692 are refreshed automatically, but you can also refresh them manually
693 anytime using the <b>Refresh data</b> button.
694 </p>
695
696 <p>
697 The left side of the tab contains the fleet information. The tail
698 number of each aircraft is listed with the plane's status, as known
699 by the Online Gate System. The two major statuses are <i>LHBP-nn</i>
700 and <i>AWAY</i>. The former indicates that the aircraft is parked at
701 the Budapest Ferihegy Airport at gate or stand <i>nn</i>, while the
702 latter one denotes that the airplane is parked at another
703 airport. Another possible status is <i>PARKED</i>, which means that
704 the airplane is parked somewhere at the Ferihegy Airport, but we
705 (or at least the Gate System) don't know where. It may happen that
706 several aircraft are parked at the same gate or stand at
707 Ferihegy. In this case the tail numbers and the statuses of those
708 airplanes are displayed in red.
709 </p>
710
711 <p>
712 The right side contains the list of the numbers of the gates and
713 parking positions. A number is black if no aircraft is positioned at
714 the corresponding gate or stand, and it is orange, if the location
715 is occupied.
716 </p>
717
718 <h3><a name="debugLog">The Debug log</a></h3>
719
720 <img src="debugLogTab.png" alt="The Debug log tab"/>
721
722 <p>
723 This tab is not visible by default, but can be displayed by
724 selecting <b>View/Show debug log</b> or by
725 pressing <b>Ctrl+D</b>. It is another kind of log, which is mainly
726 useful for debugging. If you experience some problem with the
727 program, please, include the contents of this log with your bug
728 report. It can help a lot with finding a solution to the problem.
729 </p>
730
731 <h2><a name="loadingPIREPs">Loading PIREPs</a></h2>
732
733 <p>
734 Saved PIREPs can be loaded and sent by the program. This can
735 become necessary, for example, if you cannot send a PIREP due to
736 some network problem right after your flight, or when you
737 deliberately performed a flight without connecting to the Internet.
738 </p>
739
740 <p>
741 To load a PIREP select the <b>File/Load PIREP...</b> menu option or
742 press the <b>Ctrl+L</b> key. A file selection dialog appears, from
743 which you can select the PIREP to load. If you select a valid PIREP
744 file, it will be loaded and a new window will be displayed with the
745 most important data of your flight. By clicking <b>Send
746 PIREP...</b>, the PIREP will be sent (or at least an attempt will be
747 made at sending it). A dialog window will be displayed about the
748 results of the attempt.
749 </p>
750
751 <div align="center">
752 <img src="pirepLoaded.png" alt="The loaded PIREP window"/>
753 </div>
754
755 <p>
756 You may also want to view a saved PIREP, for example, if it is a
757 PIREP about an entrance exam flight. To do so, click the <b>View
758 PIREP...</b> button. This displays the PIREP viewer window, which
759 groups the data into three tabs. The <i>Data</i> tab contains the
760 itemized data of the flight. The <i>Comments & defects</i> tab
761 displays the comments and or flight defects entered by the
762 user. The <i>Log</i> tab contains the flight log.
763 </p>
764
765 <div align="center">
766 <img src="pirepViewer.png" alt="The PIREP Viewer"/>
767 </div>
768
769 <h2><a name="checklistEditor">Editing checklists</a></h2>
770
771 <img src="checklistEditor.png" alt="The Checklist Editor"/>
772
773 <p>
774 The checklists are lists of audio files. When checklist playback is
775 enabled (see the <a href="#prefsSounds">description</a> of
776 the <i>Preferences</i> window below), and there is a checklist for
777 the type of the aircraft used for the flight, the files constituting
778 the checklist can be played one-by-one by pressing the checklist
779 hotkey repeatedly.
780 </p>
781
782 <p>
783 The checklist editor window allows for editing the checklists. It
784 can be displayed by selecting <b>Tools/Checklist Editor...</b> or
785 pressing <b>Ctrl+C</b>. The top of the window contains an aircraft
786 type selector.
787 </p>
788
789 <p>
790 The files making up the checklist for the currently selected aircraft
791 are displayed on the right. You can move a file up or down by
792 dragging it with the mouse. You can also select one or more files
793 from the list. Then you can remove them with the <b>Remove</b>
794 button, or move them up or down by pressing <b>Move up</b>
795 and <b>Move down</b>.
796 </p>
797
798 <p>
799 To add new files to the checklist, select them in the file selector
800 on the left, and press <b>Add to checklist</b>. The file(s) will be
801 appended to the end of the checklist.
802 </p>
803
804 <p>
805 Note, that any changes you make are effective only if you press
806 the <b>OK</b> button when having finished the modifications. If the
807 flight has already started, no changes made to the corresponding
808 checklist have any effect during the flight (i.e. you will still use
809 the old checklist, or no checklist if there was none).
810 </p>
811
812 <h2><a name="prefs">The Preferences Window</a></h2>
813
814 </p>
815 The Preferences window can be displayed by
816 selecting <b>Tools/Preferences</b> or by
817 pressing <b>Ctrl+P</b>. Here you can set options that you usually
818 don't have to change for every flight. This window consists of
819 tabs grouping the options logically.
820 </p>
821
822 <h3><a name="prefsGeneral">The <i>General</i> Tab<a></h3>
823
824 <img src="prefsGeneral.png" alt="The General Tab of Preferences"/>
825
826 <p>
827 These are some general settings for various parts of the
828 program. The <i>GUI</i> frame contains options regarding the
829 behaviour of the graphical user interface. The <i>Language</i> combo
830 box can be used to selected what language the program should
831 use. Currently English and Hungarian are supported. The value
832 of <i>system default</i> means that the operating system's default
833 language is used if it is one of the supported ones or English
834 otherwise. Note, that the program must be restarted for the change
835 to take effect if you modify this setting. If the <b>Hide main window
836 when minimized</b> checkbox is checked, and you minimize the window,
837 it will actually disappear completely (i.e. not appear among the
838 other minimized windows). You can make it appear by using the tray
839 icon. If the <b>Quit when the window close button is clicked</b>
840 checkbox is checked, the program will quit, after you have confirmed
841 it. Otherwise it will just disappear, and you can use the tray icon
842 to display it again.
843 </p>
844
845 <p>
846 The <i>MAVA Online Systems</i> frame contains settings related to
847 the online systems of MAVA, the <a href="#onlineGateSystem">gate</a>
848 and the <a href="#onlineACARSSystem">ACARS</a> systems mentioned
849 above. It is recommended to enable these for normal operations.
850 </p>
851
852 <p>
853 The <i>Simulator</i> frame contains settings for how the program
854 interacts with the simulator. Most options are self-explanatory, but
855 the ones related to smoothing requires some discussion. Flight
856 Simulator is known to produce wind speed changes that are not
857 entirely realistic and can result in the simulated aircraft
858 experiencing some very high indicated airspeeds, which in turn can
859 also cause the autopilot to suddenly increase the climb rate to
860 counter the high speeds or other erratic behaviour. Since these
861 phenomena are difficult to protect oneself against without buying
862 extra products, like FSUIPC, the logger provides the possibility to
863 average the IAS and/or the VS over a few seconds so that spikes in
864 these values are smoothed. The <b>Enable the smoothing of IAS/VS
865 over N sec.</b> options allow controlling this feature. The number
866 of seconds may need experimenting with, but note that every change
867 for which you press the <b>OK</b> button is taken into account
868 immediately.
869 </p>
870
871 <h3><a name="prefsMessages">The <i>Messages</i> Tab</a></h3>
872
873 <img src="prefsMessages.png" alt="The Messages Tab of Preferences"/>
874
875 <p>
876 The program can display messages about certain events in the
877 simulator and/or it can play a warning sound when those events
878 occur. The tab allows configuring this.
879 <p>
880
881 <p>
882 The categories of the message are listed on the left. These are the
883 following:
884 </p>
885
886 <ul>
887 <li><b>Logger Error Messages</b>: error messages about the
888 internal working of the logger.</li>
889 <li><b>Information Messages</b>: informational messages about,
890 e.g., the flight stage, the end of an audio checklist, etc.</li>
891 <li><b>Fault Messages</b>: messages about the non-NO GO faults the program detects.</li>
892 <li><b>NO GO Fault Messages</b>: messages about the NO GO faults the program detects</li>
893 <li><b>Gate System Messages</b>: messages related to the
894 <a href="#onlineGateSystem">Online Gate System</a>. For example,
895 when you have landed at Ferihegy, it can display the list of the
896 available gates so that you can choose where to park, if there is
897 no ATC available.</li>
898 <li><b>Environment Messages</b>: other messages, e.g. the welcome
899 message when the flight has ended.</li>
900 <li><b>Help Messages</b>: help messages, e.g. warning about
901 entering the V-speeds into the Takeoff page before takeoff.</li>
902 <li><b>Visibility Messages</b>: messages about the visibility
903 during descent and landing.</li>
904 </ul>
905
906 <p>
907 There are two checkboxes associated with each messages category. If the
908 left one (<i>Displayed in FS</i>) is checked, the messages of the
909 category will be displayed in the simulator. If the right one
910 (<i>Sound alert</i>) is checked, and a message of the given category
911 is about to be displayed, a warning sound will be played. It is
912 mainly intended to accompany the text messages, but the two options
913 can be controlled separately, so you can select the sound alert, but
914 not the displaying of the messages. This may be useful if you don't
915 want these messages to clutter up the windscreen of your aircraft,
916 but still get some notification that some problem occurred.
917 </p>
918
919 <h3><a name="prefsSounds">The <i>Sounds</i> Tab</a></h3>
920
921 <img src="prefsSounds.png" alt="The Sounds Tab of Preferences"/>
922
923 <p>
924 This tab controls how the sounds are played by the application.
925 </p>
926
927 <p>
928 The top part is for the background sounds. These are pre-recorded
929 sound files that are played when certain conditions hold during the
930 flight. Typical examples are the various announcements the flight
931 attendants make during the flight. The <b>Enable background
932 sounds</b> checkbox controls whether such sounds are enabled at
933 all. If the <b>Pilot controls sounds</b> checkbox is enabled, the
934 pilot should start the playback of these sound files by pressing a
935 hotkey in the simulator. Note, that you should still be in the right
936 flight stage (and sometimes fulfill other conditions) to be able to
937 play the sound files. Also, one file can be played only once. If you
938 enable this option, the hotkey to press in the simulator can be
939 selected below. You can choose one of the alphanumeric keys (0-9,
940 A-Z) optionally combined with one or both of the <i>Ctrl</i>
941 and <i>Shift</i> modifiers. If this checkbox is not checked, the
942 sound files will be played automatically.
943 </p>
944
945 <p>
946 If the <b>Enable speedbrake sound at touchdown</b> checkbox is
947 checked, you will hear a distinctive sound when the spoilers deploy
948 automatically after touchdown.
949 </p>
950
951 <p>
952 The lower part, named <i>Checklists</i> contains some settings
953 related to the audio checklists belonging to the aircraft. They are
954 available only if the <b>Enable aircraft-specific checklist</b>
955 checkbox is selected. In this case another hotkey should be
956 specified. If you press this hotkey, the next file from the
957 checklist will be played.
958 </p>
959
960 <h3><a name="prefsAdvanced">The <i>Advanced</i> Tab</a></h3>
961
962 <img src="prefsAdvanced.png" alt="The Advanced Tab of Preferences"/>
963
964 <p>
965 This tab contains some settings that you normally should not
966 change. Currently, these settings are related to the automatic
967 update. If the <b>Update the program automatically</b> checkbox is
968 not checked, the automatic update at program start-up will be
969 omitted. The <i>Update URL</i> text entry field contains the URL
970 from which to download the updates. Occasionally the developers of
971 the application may tell you to change this something else, e.g. to
972 test some development version. Or it may need to be changed due to
973 organizational reasons, such as moving to a new server, etc.
974 </p>
975
976 <h2><a name="monitorWindow">The Monitor Window</a></h2>
977
978 <img src="monitorWindow.png" alt="The Monitor Window"/>
979
980 <p>
981 The monitor window can be used when debugging the program. You can
982 display it by selecting <b>View/Show monitor window</b> or by
983 pressing <b>Ctrl+M</b>. It displays the various parameters from the
984 aircraft as read from the flight simulator. During flight, it is
985 updated once per second. If something is not detected properly by
986 the logger, this window can be used to determine if the problem is
987 in interpreting and translating the data read from the simulator, or
988 when the translated data is being evaluated by other parts of the
989 program.
990 </p>
991
992</html>
Note: See TracBrowser for help on using the repository browser.