Test Flight Data #2
Replies: 1 comment
-
; PRODUCT_ID = IMU-GPS+alt : ACCEL GYRO PARAMETERS ; MAGNETOMETER PARAMETERS ; PRESSURE SENSOR PARAMETERS ; GPS PARAMETERS ;gps_update interval, in seconds ; discipline RTC with GPS time ; dynamic models 0-->potable 2-->stationary 3-->pedestran 4--> automotive, 5-->sea, 6,7,8-->airborn ; minlock minimum HDOP in meters considered to be acceptable lock ; used in on/off mode number of good samples to collect before turning off ; extra parameters to logger operation ; FILE PARAMETERS ; EVENT DETECTOR PARAMETERS ; set timestamp to UTC seconds since Jan 1, 1970 instead of time since start of file ;control brightness of LEDs, values are 'off' or 'high' ;uncomment following line to activate logger upon disconnect from USB ; wakeupTime uses crontab format, except that six fields are required |
Beta Was this translation helpful? Give feedback.
-
Successful test flights yesterday. 3 flights with both loggers installed (6 data sets).
Unfortunately, the config was set to start a new file after 180,000 rows of data which works out to roughly 14 minutes of logging time. I have now increased this to 360,000 which should be plenty for a 20 minute flight. There is an option to only begin recording when a certain height above the base altitude is reached, but inaccuracies in the GPS data (vdop) might cause this to start/stop recording data during a flight so I wont use this feature for now, instead rely on manually starting the loggers before each flight.
The position in the Perkoz meant both loggers buttons were accessible to the front seat pilot.
Observations on the test data:
Test Flights 1 and 3 were general sorties with an instructor and student teaching/learning sports manouvers.
Test Flight 2 was a full sports sequence (2024 Known 1).
The rear logger didn't seem to record test flight 1, and only captured part of test flight 2. This could have been user error.
Beta Was this translation helpful? Give feedback.
All reactions