|
Group: Forum Members
Posts: 13,
Visits: 30
|
Forgot to turn off flight logging so ended up with my drive home recorded on the flight log.
To edit the drive out of the log, I exported to a gpx file, opened in Notepad and deleted the segments relating to the drive. That leaves me with a clean gpx file which displays the correct flight log when I import it back in to SD.
How do I save this as a SD flightlog? I tried renaming the .gpx as a .flightlog file and saving in the skydemon/logs folder, but it doesn't work. Couldn't find any 'save log file' functionality to put a .flightlog file in to the skydemon/logs folder.
|
|
Group: Forum Members
Posts: 323,
Visits: 388
|
+xSo we know how we can NOT do that, but how can we actually edit the log? I have the same issue - after landing used "blocks on" and "engine off" buttons, but forgot to tap "back to planning mode". And what next? SD logged all my way home (driving), and I have no idea how to remove the erroneous tracks.
Any idea? BTW - why does it log anything after "engine off", while on the ground, using motor powered aircraft?
Maybe besides possibility to merge flight logs, there should also be an option to split them? As you recognized, you cannot edit the .flightlog file, which btw was one reason our supervisor accepted Skydemon for logging purposes.
Regarding your BTW, did you learn the concept of 'block time' in training and how it works? Just for recap - 'Engine off' will only mark 'end of flight', all other movement on the ground until 'on block' is still block time, you remember? For us i.e. refuelling after flight at the station and being tugged to final park position is blocktime until at the parking position.
|
|
Group: Forum Members
Posts: 4,
Visits: 19
|
+xThe flight logs in SkyDemon are not designed to be user-editable. Your log sounds like it is valid in terms of the timings, which is the important thing, but you forgot to stop SkyDemon so presumably it logged your drive home. Perhaps that produce extra flights? We may be able to do something about it, because I agree that sounds undesirable, but it would be good to have your confirmation of the problem.
Exactly, that's the clue of my question. Flight logging is actually correct and timings are valid, however it produced some additional flights as I was driving home with SD in by bag, because I simply didn't return "back to planning mode" - I forgot. However I made it "on blocks" and "engine off". And that's the problem. All I need to do is to correct the log by removing the erroneous additional "flight" logged when I was driving home. That would be great if you could do anything to solve that.
+xAs you recognized, you cannot edit the .flightlog file, which btw was one reason our supervisor accepted Skydemon for logging purposes.
Regarding your BTW, did you learn the concept of 'block time' in training and how it works? Just for recap - 'Engine off' will only mark 'end of flight', all other movement on the ground until 'on block' is still block time, you remember? For us i.e. refuelling after flight at the station and being tugged to final park position is blocktime until at the parking position.
I don't need to edit it freely, I just need to correct some specific errors like stated above. Nothing more than that. Regarding "block time concept" - yes, of course, I know it very well, but I daresay we don't understand each other's viewpoint. Refueling and being towed to parking position counted as a flight time seems to be strange for me, but for you it's not, I think, and I have no idea why. Besides ICAO, EASA and FAA rules, even SD manual says "SkyDemon will automatically log On Blocks from the time you last moved before tapping Engine Off.", and this idea is correct. Don't confuse the terms. That's the sequence:
1) Engine Start 2) Off Blocks 3) Take Off 4) Landing 5) On Blocks 6) Engine Off
|