NT Data Logging - Revision history

OlliW: /* Live Recording */

2023-04-08T03:02:57Z

Live Recording

← Older revision		Revision as of 05:02, 8 April 2023
Line 128:		Line 128:
	USB-TTL adapter Tx -> do not connect		USB-TTL adapter Tx -> do not connect

	The USB-TTL adapter's Tx line '''''must not''''' be connected to the STorM32's NT Rx line, i.e., ~~should~~ be left floating.		The USB-TTL adapter's Tx line '''''must not''''' be connected to the STorM32's NT Rx line, i.e., must be left floating.

	== Data Fields ==		== Data Fields ==

2023-01-21T13:45:33Z

← Older revision		Revision as of 15:45, 21 January 2023
Line 1:		Line 1:
	''The information on this page refers to firmware v2.59e and higher.''		<span style="font-size:88%">''The information on this page refers to firmware v2.59e and higher.''</span>

	A data logger, the NT Logger, can be connected to the NT bus, which allows us to record on a micro SD card a substantial amount of data. The data are recorded for each cycle of the controller loop, i.e., with the maximal possible time resolution. The NT Logger is quite small and can be easily mounted on any vehicle. This way one can get highly accurate and informative data taken during a real flight condition. The same data can also be recorded on the ground, without the need of a NT Logger, using the live-recording feature.		A data logger, the NT Logger, can be connected to the NT bus, which allows us to record on a micro SD card a substantial amount of data. The data are recorded for each cycle of the controller loop, i.e., with the maximal possible time resolution. The NT Logger is quite small and can be easily mounted on any vehicle. This way one can get highly accurate and informative data taken during a real flight condition. The same data can also be recorded on the ground, without the need of a NT Logger, using the live-recording feature.

2021-09-08T14:46:59Z

Data Fields

2021-09-08T14:45:11Z

Data Fields

← Older revision		Revision as of 16:45, 8 September 2021
Line 153:		Line 153:
	{{DATACLASS\|PID SetP Pitch,Roll,Yaw}}: <br>		{{DATACLASS\|PID SetP Pitch,Roll,Yaw}}: <br>
	PID controller setpoint angles.		PID controller setpoint angles.

			{{DATACLASS\|PID P I D Pitch,Roll,Yaw}}: <br>
			PID controller internal values of the P, I, and D term.

	{{DATACLASS\|PID Pitch,Roll,Yaw}}: <br>		{{DATACLASS\|PID Pitch,Roll,Yaw}}: <br>

2021-09-08T14:43:40Z

← Older revision		Revision as of 16:43, 8 September 2021
Line 1:		Line 1:
	''The information on this page refers to firmware v2.~~56e~~ and higher.''		''The information on this page refers to firmware v2.59e and higher.''

	A data logger, the NT Logger, can be connected to the NT bus, which allows us to record on a micro SD card a substantial amount of data. The data are recorded for each cycle of the controller loop, i.e., with the maximal possible time resolution. The NT Logger is quite small and can be easily mounted on any vehicle. This way one can get highly accurate and informative data taken during a real flight condition. The same data can also be recorded on the ground, without the need of a NT Logger, using the live-recording feature.		A data logger, the NT Logger, can be connected to the NT bus, which allows us to record on a micro SD card a substantial amount of data. The data are recorded for each cycle of the controller loop, i.e., with the maximal possible time resolution. The NT Logger is quite small and can be easily mounted on any vehicle. This way one can get highly accurate and informative data taken during a real flight condition. The same data can also be recorded on the ground, without the need of a NT Logger, using the live-recording feature.

2021-09-08T14:42:33Z

GUI Settings

← Older revision		Revision as of 16:42, 8 September 2021
Line 91:		Line 91:
	!data		!data
	\|-		\|-
	\|style="text-align:left;" \| {{PARAMVALUE\|~~basic~~}} \|\| SetLogger, CmdAhrs, SetMotorAll, CmdEncoderData, CmdStorm32LinkData		\|style="text-align:left;" \| {{PARAMVALUE\|Basic}} \|\| SetLogger, CmdAhrs, SetMotorAll, CmdEncoderData, CmdStorm32LinkData
	\|-		\|-
	\|style="text-align:left;" \| {{PARAMVALUE\|~~acc~~ + ~~gyro~~ raw}} \|\| CmdAccGyroRaw for Imu1 & Imu2		\|style="text-align:left;" \| {{PARAMVALUE\|Acc + Gyro raw}} \|\| CmdAccGyroRaw for Imu1 & Imu2
	\|-		\|-
	\|style="text-align:left;" \| {{PARAMVALUE\|~~pid in~~}} \|\| CmdPidIn		\|style="text-align:left;" \| {{PARAMVALUE\|PID In}} \|\| CmdPidIn
	\|-		\|-
	\|style="text-align:left;" \| {{PARAMVALUE\|~~pid~~}} \|\| CmdPid		\|style="text-align:left;" \| {{PARAMVALUE\|PID Out}} \|\| CmdPid
	\|-		\|-
	\|style="text-align:left;" \| {{PARAMVALUE\|~~acc~~ + ~~gyro~~}} \|\| CmdAccGyro for Imu1 & Imu2		\|style="text-align:left;" \| {{PARAMVALUE\|Acc + Gyro}} \|\| CmdAccGyro for Imu1 & Imu2
	\|-		\|-
	\|style="text-align:left;" \| {{PARAMVALUE\|~~inputs~~}} \|\| CmdFunctionInputValues		\|style="text-align:left;" \| {{PARAMVALUE\|Inputs}} \|\| CmdFunctionInputValues
			\|-
			\|style="text-align:left;" \| {{PARAMVALUE\|PID I D}} \|\| CmdPidID
			\|-
			\|style="text-align:left;" \| {{PARAMVALUE\|STorM32 Link}} \|\| CmdStorm32Link
	\|}		\|}

2021-03-03T11:52:28Z

Data Fields

← Older revision		Revision as of 13:52, 3 March 2021
Line 128:		Line 128:
	== Data Fields ==		== Data Fields ==

	Depending on the configuration, i.e., the {{PARAMNAME\|NT Logging}} setting (see [[#GUI Settings\|GUI Settings]]) and if it is a NT or T-STorM32 build, some data fields may not be available ~~and~~ their values are set to zero.		Depending on the configuration, i.e., the {{PARAMNAME\|NT Logging}} setting (see [[#GUI Settings\|GUI Settings]]) and if it is a NT or T-STorM32 build, some data fields may not be available. In this case their values are set to zero.

	{{DATACLASS\|Performance}}: <br>		{{DATACLASS\|Performance}}: <br>

2021-03-03T11:51:56Z

Data Fields

← Older revision		Revision as of 13:51, 3 March 2021
Line 128:		Line 128:
	== Data Fields ==		== Data Fields ==

	Depending on the configuration, i.e. the {{PARAMNAME\|NT Logging}} setting (see [[#GUI Settings\|GUI Settings]]) and if it is a NT or T-STorM32 build, some data fields may not be available~~. In this case the~~ values are set to zero.		Depending on the configuration, i.e., the {{PARAMNAME\|NT Logging}} setting (see [[#GUI Settings\|GUI Settings]]) and if it is a NT or T-STorM32 build, some data fields may not be available and their values are set to zero.

	{{DATACLASS\|Performance}}: <br>		{{DATACLASS\|Performance}}: <br>

2021-03-03T11:51:08Z

Data Fields

← Older revision		Revision as of 13:51, 3 March 2021
Line 128:		Line 128:
	== Data Fields ==		== Data Fields ==

	Depending on the configuration, i.e. the {{PARAMNAME\|NT Logging}} setting (see [[#GUI Settings]]) and if it is a NT or T-STorM32 build, some data fields may not be available. In this case the values are set to zero.		Depending on the configuration, i.e. the {{PARAMNAME\|NT Logging}} setting (see [[#GUI Settings\|GUI Settings]]) and if it is a NT or T-STorM32 build, some data fields may not be available. In this case the values are set to zero.

	{{DATACLASS\|Performance}}: <br>		{{DATACLASS\|Performance}}: <br>

2021-03-03T11:50:22Z

Data Fields

← Older revision		Revision as of 13:50, 3 March 2021
Line 128:		Line 128:
	== Data Fields ==		== Data Fields ==

	Depending on the configuration, i.e. the {{PARAMNAME\|NT Logging}} setting (see [#GUI Settings]) and if it is a NT or T-STorM32 build, some data fields may not be available. In this case the values are set to zero.		Depending on the configuration, i.e. the {{PARAMNAME\|NT Logging}} setting (see [[#GUI Settings]]) and if it is a NT or T-STorM32 build, some data fields may not be available. In this case the values are set to zero.

	{{DATACLASS\|Performance}}: <br>		{{DATACLASS\|Performance}}: <br>