This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
leon:mx-fleet [2017/10/23 10:13] grzegorz |
leon:mx-fleet [2019/04/13 09:19] rafal [CAM] |
||
|---|---|---|---|
| Line 20: | Line 20: | ||
| ===== CAM ===== | ===== CAM ===== | ||
| + | <box>It is possible to integrate Leon with **CAMP**. Leon exports aircraft **TAH & TAC** (Total Aircraft Hours & Cycles) as well as **APU** hours (if updated in Journey Log in Leon). CAMP integration works one way only. It means that data updated in Leon updates data in CAMP, but data updated at CAMP's end does not update data in Leon. </box> | ||
| Here you can define such values for each aircraft, as: | Here you can define such values for each aircraft, as: | ||
| Line 29: | Line 29: | ||
| The filter allows you to view flights with/without Journey Log inserted, or only with Journey Log. It is also possible to see TAH value in **decimal**. | The filter allows you to view flights with/without Journey Log inserted, or only with Journey Log. It is also possible to see TAH value in **decimal**. | ||
| - | [{{ :leon:mx-fleet:tah_decimal_on.png?200|TAH in decimal }}] | ||
| [{{ :leon:mx-fleet:tah_decimal_off.png?200|TAH in minutes }}] | [{{ :leon:mx-fleet:tah_decimal_off.png?200|TAH in minutes }}] | ||
| + | [{{ :leon:mx-fleet:tah_decimal_on.png?200|TAH in decimal }}] | ||
| - | Leon calculates it with a pattern: | + | Leon converts values into decimal with a pattern: |
| * 00-03:59 min = 0.0 | * 00-03:59 min = 0.0 | ||
| * 04-09:59 min = 0.1 | * 04-09:59 min = 0.1 | ||
| Line 46: | Line 46: | ||
| - | <box>It is possible to integrate Leon with **CAMP**. Leon exports aircraft **TAH & TAC** (Total Aircraft Hours & Cycles) as well as **APU** hours (if updated in Journey Log in Leon). CAMP integration works one way only. It means that data updated in Leon updates data in CAMP, but data updated at CAMP's end does not update data in Leon. </box> | ||
| - | [{{ :leon:mx-fleet:cam main screen.png?150|CAM data main screen}}] | + | [{{ :leon:mx-fleet:CAM3.png?150|CAM data main screen}}] |
| Section '**Airframe**' defines data for total TAH & TAC of the aircraft (without splitting on engines). That data is also displayed in main Fleet screen, column 'Airframe'. | Section '**Airframe**' defines data for total TAH & TAC of the aircraft (without splitting on engines). That data is also displayed in main Fleet screen, column 'Airframe'. | ||
| Line 62: | Line 61: | ||
| When you add a new flight on that particular aircraft, 'Airframe' TAH & TAC will change as well as TAH & TAC for each separate engine. To view it, hover the mouse over the icon {{:leon:icons:silnik.png?20|}} in Settings > Fleet section, and you will see exact information in the pop-up window (see example below). | When you add a new flight on that particular aircraft, 'Airframe' TAH & TAC will change as well as TAH & TAC for each separate engine. To view it, hover the mouse over the icon {{:leon:icons:silnik.png?20|}} in Settings > Fleet section, and you will see exact information in the pop-up window (see example below). | ||
| + | **Warnings** will help to trigger CAM warnings in Edit Flight or when adding the Flight depending on the values inserted in **Flight hours** and **Flight cycles** fields. | ||
| **APU** | **APU** | ||
| - | You can also add seperate data for '**APU**' (Aircraft Power Unit), however, APU hours and cycles **do not** get automatically increased from the journey log entries (like engines). Here you can input initial APU value and the date when the system should start counting it from. This is a cummulative value, not hours per single flight. With APU, Leon just **stores** the latest value you provide here, which should be updated every time you have the new one. | + | You can also add separate data for '**APU**' (Aircraft Power Unit), however, APU hours and cycles **do not** get automatically increased from the journey log entries (like engines). Here you can input initial APU value and the date when the system should start counting it from. This is a cumulative value, not hours per single flight. With APU, Leon just **stores** the latest value you provide here, which should be updated every time you have the new one. |
| - | **Example** - if APU start TAH was 100:00 then after one sector APU was 01:00 - you should add in your Journey Log into APU field a total value of 101:00 as it needs to be summary value (start APU + sector one). | + | **Example** - if APU start TAH was 100:00 then after one sector APU was 01:00 - you should add in your Journey Log into APU field a total value of 101:00 as it needs to be the summary value (start APU + sector one). |
| If **APU** Hours input in [[leon:journey-log|Journey Log]] are lower than the value from previous JL or the minimum value indicated in Settings > Fleet, Leon will show the warning: | If **APU** Hours input in [[leon:journey-log|Journey Log]] are lower than the value from previous JL or the minimum value indicated in Settings > Fleet, Leon will show the warning: | ||
| Line 76: | Line 75: | ||
| </html>. | </html>. | ||
| + | ------------------------- | ||
| ===== Oil Consumption ===== | ===== Oil Consumption ===== | ||
| - | [{{ :leon:mx-fleet:CAM - Oil Consumption.png?200|CAM - fleet oil consumption }}] | + | [{{ :leon:mx-fleet:CAM3.png?200|CAM - fleet oil consumption }}] |
| It is possible to monitor **oil consumption** per engine and per APU. You can define how many quarters of oil (in decimal numbers) have been used on a particular flight - a field **Oil uplift** in Journey Log has to be filled in for this purpose. | It is possible to monitor **oil consumption** per engine and per APU. You can define how many quarters of oil (in decimal numbers) have been used on a particular flight - a field **Oil uplift** in Journey Log has to be filled in for this purpose. | ||