Concerning E.I. UBG-16, MGL and GRT monitors
How do I download data from a UBG-16?
Files that come from a UBG-16 do not contain “heading names” for each of the columns in the file (each column represents a data series, such as EGT1). As such, if a file such as this were uploaded to SavvyAviation, the parser would not be able to discern which column was EGT1, which was CHT1, and so on.
Therefore, it is necessary to configure the aircraft’s profile with these mappings. This will tell the parser, for example, that Column 1 is EGT1, column 2 is CHT2, etc.
Often, these mappings can be found in the aircraft logs from the time the UBG-16 was installed. If there are no such entries, it may be necessary to open the file and do some detective work. When opening the file with an editor, be very careful not to accidentally save over the original. This will almost certainly make it unusable. It is best to make a copy and open the copy.
Here are the steps for providing the UBG-16 configuration:
- Log into apps.savvyaviation.com
- Click on the account holder’s name in the upper right corner of the page and select “Aircraft” from the drop-down menu
- The Engine Monitor Manufacturer field should read “Electronics International (E.I.)”
- The Engine Monitor Model field should read “UBG-16”
- If either item in step 3 or 4 requires adjustment, click the Edit Aircraft button; make the necessary changes; click the Save button
- Click on the tab labeled “UBG-16 Parameters” at the bottom of the left column of tabs (If it does not display, refresh the page: (CTRL+R [Windows] or Command+R [Mac]))
- On the UBG-16 Parameters screen the current mappings will be displayed. Selecting “Typical Single” or “Typical Twin” will populate many settings, making it easier to make adjustments/additions from that point
- When satisfied, click the “Submit” button at the bottom of the list
- Select “Upload” from the menu at the top of the page, then choose “Engine Data” to ensure you are uploading files to the correct aircraft.
Note: The mappings apply to files uploaded after the mappings have been set (saved). In other words, if a few files are uploaded, and then the mappings are changed/updated, the uploaded files are not affected or changed in any way. So, if the changes made are necessary to correct mappings, it will be necessary to delete and reload flights uploaded prior to the change.
How do I upload data from an MGL Avionics engine monitor?
Files that come from a MGL Avionics engine monitors do not contain “heading names” for the EGT and CHT series. As such, if you were to upload such a file to SavvyAnalysis, we would not be able to tell which column was EGT1, which was CHT1, and so on.
To work around this, you have to configure your aircraft’s profile with these mappings. This will tell us, for example, that Sensor 1 is EGT1, column 2 is CHT2, etc.
You should be able to find these mappings in your aircraft logs at the time your MGL was installed. If you do not have such entries, you may need to play around with the mappings and do some detective work.
Here are the steps to provide us with the MGL configuration:
- Log into apps.savvyaviation.com
- Under “Account” select “Aircraft”
- Click on the “Actions Menu” icon for your aircraft
- If there is an entry “Edit MGL Mappings” select it, and skip the next two steps
- If there is no enry “Edit MGL Mappings” select the “Edit” option
- Set the Engine Monitor to “MGL”, set the Model to your MGL model and click “Save”. Then select the “Actions Menu” again and click on “Edit MGL Mappings”
- On the screen that follows you now have to tell us, how your columns are mapped. You can select “Typical 4/6 Cyl Single” or “Typical 4/6 Cyl Twin” to get most settings populated and then adjust from there.
- When you are done, click “Save”
- Select “Upload New” from the “Flights” menu, ensure you are uploading against the correct aircraft and upload your files.
Note 1: The mappings apply to file uploaded after the mappings have been set. In other words, if you upload a few files, and then change the mappings, the existing files are not affected or changed in any way.
Note 2: We only support .REC files. We do not support .EFL files. By uploading the .REC files frequently, you will likely get duplicate flights and you will have to delete those manually. Due to the MGL data format, we don’t have a good way of handling this issue at present.
I have a GRT monitor that records each flight in multiple small files. Help!
We’ve build a new feature to help with stitching together those smaller files. Here’s how it works:
Take all the flights that make up a single flight, and zip them up together. The files need to have the same filenames, except for the index numbering for the 2nd and subsequent files. For example:
DEMO-0000.log
DEMO-0000+1.log
DEMO-0000+2.log
DEMO-0000+3.log
Then rename the zip and prepend the words “grt-merge”, so for example, you could call it:
grt-merge-2014-08-24.zip
… and upload this file. Our system will recognize it, and stitch all the files together.
Why do my GRT uploads show the wrong date?
If you have a GPS connected to your GRT, flight date and time should be referenced to the GPS data. If a GPS does not exist, the GRT unit does not report the time or date, so SavvyAnalysis defaults to 2000-01-01. If you would like the date to be entered correctly for the flight, you have to name the file correctly.
If you are uploading single files and they start with this pattern:
DEMO-20161231-131500XXXX.log (where XXX is any optional text that may or may not be there) we already grab that time and date and use it as the flight start time.
If you are merging files together, you need to include the date in the name of the zip file, not the individual files. Use either of the following formats (again XXXX is optional text that will be ignored).
grt-merge-2016-12-31XXXXXX.zip
grt-merge-2016-12-31-131500XXXXXX.zip