Functions
	PARAM_DEFINE_INT32 (SDLOG_UTC_OFFSET, 0)
	UTC offset (unit: min) More...

	PARAM_DEFINE_INT32 (SDLOG_MODE, 0)
	Logging Mode. More...

	PARAM_DEFINE_INT32 (SDLOG_MISSION, 0)
	Mission Log. More...

	PARAM_DEFINE_INT32 (SDLOG_PROFILE, 3)
	Logging topic profile (integer bitmask). More...

	PARAM_DEFINE_INT32 (SDLOG_DIRS_MAX, 0)
	Maximum number of log directories to keep. More...

	PARAM_DEFINE_INT32 (SDLOG_UUID, 1)
	Log UUID. More...

Function Documentation

◆ PARAM_DEFINE_INT32() [1/6]

PARAM_DEFINE_INT32	(	SDLOG_UTC_OFFSET	,
		0
	)

UTC offset (unit: min)

the difference in hours and minutes from Coordinated Universal Time (UTC) for a your place and date.

for example, In case of South Korea(UTC+09:00), UTC offset is 540 min (9*60)

refer to https://en.wikipedia.org/wiki/List_of_UTC_time_offsets

min -1000 1000 SD Logging

◆ PARAM_DEFINE_INT32() [2/6]

PARAM_DEFINE_INT32	(	SDLOG_MODE	,
		0
	)

Logging Mode.

Determines when to start and stop logging. By default, logging is started when arming the system, and stopped when disarming.

-1 disabled 0 when armed until disarm (default) 1 from boot until disarm 2 from boot until shutdown 3 depending on AUX1 RC channel

true SD Logging

◆ PARAM_DEFINE_INT32() [3/6]

PARAM_DEFINE_INT32	(	SDLOG_MISSION	,
		0
	)

Mission Log.

If enabled, a small additional "mission" log file will be written to the SD card. The log contains just those messages that are useful for tasks like generating flight statistics and geotagging.

The different modes can be used to further reduce the logged data (and thus the log file size). For example, choose geotagging mode to only log data required for geotagging.

Note that the normal/full log is still created, and contains all the data in the mission log (and more).

0 Disabled 1 All mission messages 2 Geotagging messages

true SD Logging

◆ PARAM_DEFINE_INT32() [4/6]

PARAM_DEFINE_INT32	(	SDLOG_PROFILE	,
		3
	)

Logging topic profile (integer bitmask).

This integer bitmask controls the set and rates of logged topics. The default allows for general log analysis and estimator replay, while keeping the log file size reasonably small.

Enabling multiple sets leads to higher bandwidth requirements and larger log files.

Set bits true to enable: 0 : Default set (used for general log analysis) 1 : Full rate estimator (EKF2) replay topics 2 : Topics for thermal calibration (high rate raw IMU and Baro sensor data) 3 : Topics for system identification (high rate actuator control and IMU data) 4 : Full rates for analysis of fast maneuvers (RC, attitude, rates and actuators) 5 : Debugging topics (debug_*.msg topics, for custom code) 6 : Topics for sensor comparison (low rate raw IMU, Baro and Magnetomer data) 7 : Topics for computer vision and collision avoidance

0 255 0 Default set (general log analysis) 1 Estimator replay (EKF2) 2 Thermal calibration 3 System identification 4 High rate 5 Debug 6 Sensor comparison 7 Computer Vision and Avoidance true SD Logging

◆ PARAM_DEFINE_INT32() [5/6]

PARAM_DEFINE_INT32	(	SDLOG_DIRS_MAX	,
		0
	)

Maximum number of log directories to keep.

If there are more log directories than this value, the system will delete the oldest directories during startup.

In addition, the system will delete old logs if there is not enough free space left. The minimum amount is 300 MB.

If this is set to 0, old directories will only be removed if the free space falls below the minimum.

Note: this does not apply to mission log files.

0 1000 true SD Logging

◆ PARAM_DEFINE_INT32() [6/6]

PARAM_DEFINE_INT32	(	SDLOG_UUID	,
		1
	)

Log UUID.

If set to 1, add an ID to the log, which uniquely identifies the vehicle

SD Logging