UDP Output - Revision history

Thomas: /* Debugging */

2012-02-05T00:11:06Z

Debugging

← Older revision		Revision as of 00:11, 5 February 2012
Line 106:		Line 106:
	total size: 132 bytes		total size: 132 bytes

	=== Debugging ===		== Debugging ==
	To check that you have everything correctly set up, you can use the 'nc' or 'ncat' command which is available on both windows and linux. On Windows it is distributed in the [http://nmap.org/download.html NMap] software.		To check that you have everything correctly set up, you can use the 'nc' or 'ncat' command which is available on both windows and linux. On Windows it is distributed in the [http://nmap.org/download.html NMap] software.

Thomas at 00:10, 5 February 2012

2012-02-05T00:10:53Z

← Older revision		Revision as of 00:10, 5 February 2012
Line 105:		Line 105:

	total size: 132 bytes		total size: 132 bytes

			=== Debugging ===
			To check that you have everything correctly set up, you can use the 'nc' or 'ncat' command which is available on both windows and linux. On Windows it is distributed in the [http://nmap.org/download.html NMap] software.

			Assuming that you have set the output to port 6060 you can type the following into a terminal window while Silent Wings is running:

			ncat -l -u localhost 6060

			And the terminal window should be filled with the output of the protocol you have selected, for example with the condor protocol:

			time=12.08
			airspeed=30.327
			altitude=1183.170
			vario=-0.850
			evario=-0.851
			nettovario=0.000
			integrator=-0.838
			compass=220.21
			...


	[[Category:Interfaces]]		[[Category:Interfaces]]

Ola at 11:12, 16 July 2011

2011-07-16T11:12:38Z

← Older revision		Revision as of 11:12, 16 July 2011
Line 14:		Line 14:

	== Condor Protocol ==		== Condor Protocol ==

			To enable it, use the option

			output_udp_protocol = condor

	The Condor protcol consists of a bunch of strings on the format TAG=VALUE. The values sent by Silent Wings are (without the <> brackets):		The Condor protcol consists of a bunch of strings on the format TAG=VALUE. The values sent by Silent Wings are (without the <> brackets):

Thomas at 21:59, 19 April 2011

2011-04-19T21:59:48Z

← Older revision		Revision as of 21:59, 19 April 2011
Line 3:		Line 3:
	Silent Wings can output various flight data to a configurable UDP socket. This can be useful for add-on developers and cockpit builders. Specifically, we support the Simmeters protocol for output of flight data to [http://www.simmeters.com Simmeters] instrument panels. In addition, we support the Condor format and our own binary format.		Silent Wings can output various flight data to a configurable UDP socket. This can be useful for add-on developers and cockpit builders. Specifically, we support the Simmeters protocol for output of flight data to [http://www.simmeters.com Simmeters] instrument panels. In addition, we support the Condor format and our own binary format.

	use_output_udp = ~~false~~		The following options in the "options.dat" file control the UDP protocol settings.

			use_output_udp = true
	output_udp_protocol = simmeters		output_udp_protocol = simmeters
	output_udp_address = localhost		output_udp_address = localhost

Thomas at 14:52, 6 July 2009

2009-07-06T14:52:57Z

← Older revision		Revision as of 14:52, 6 July 2009
Line 13:		Line 13:
	== Condor Protocol ==		== Condor Protocol ==

	The Condor protcol consists of a bunch of strings on the format TAG=VALUE. The values sent by Silent Wings are:		The Condor protcol consists of a bunch of strings on the format TAG=VALUE. The values sent by Silent Wings are (without the <> brackets):

	time=<decimal hours>		time=<decimal hours>

Thomas at 14:52, 6 July 2009

2009-07-06T14:52:31Z

← Older revision		Revision as of 14:52, 6 July 2009
Line 23:		Line 23:
	integrator=<integrated vario>		integrator=<integrated vario>
	compass=<compass heading>		compass=<compass heading>
	slipball=<ball angle (radians)>		slipball=<ball angle (radians) [2]>
	turnrate=<rad/sec>		turnrate=<rad/sec>
	yawstringangle=<radians>		yawstringangle=<radians>

Thomas at 14:50, 6 July 2009

2009-07-06T14:50:12Z

← Older revision		Revision as of 14:50, 6 July 2009
Line 12:		Line 12:

	== Condor Protocol ==		== Condor Protocol ==

			The Condor protcol consists of a bunch of strings on the format TAG=VALUE. The values sent by Silent Wings are:

			time=<decimal hours>
			airspeed=<absolute airspeed>
			altitude=<altitude>
			vario=<variometer value [1]>
			evario=<variometer values [1]>
			nettovario=<netto vario>
			integrator=<integrated vario>
			compass=<compass heading>
			slipball=<ball angle (radians)>
			turnrate=<rad/sec>
			yawstringangle=<radians>
			radiofrequency=<current comm frequency>
			yaw=<rotation about z axis, radians>
			pitch=<rotation about y axis, radians>
			bank=<rotation about x axis, radians>
			quaternionx=<quaternion representation of aircraft orientation, X component>
			quaterniony=<quaternion representation of aircraft orientation, Y component>
			quaternionz=<quaternion representation of aircraft orientation, Z component>
			quaternionw=<quaternion representation of aircraft orientation, W component>
			ax=<accelleration along X axis>
			ay=<accelleration along Y axis>
			az=<accelleration along Z axis>
			vx=<velocity along X axis (m/s)>
			vy=<velocity along Y axis (m/s)>
			vz=<velocity along Z axis (m/s)>
			rollrate=<radians/second around X axis>
			pitchrate=<radians/second around Y axis>
			yawrate=<radians/second around Z axis>
			gforce=<filtered g load>

			Note [1]: The first variometer value is filtered with a slow
			filter to simulate a slower mechanical vario. The "evario" value
			is the variometer value that is normally indicated in the
			instrument panel.

			Note [2]: The slip ball is calibrated to +/- 15 degrees in radians

			All coordinate values are given in aircraft body coordinates
			which are defined as X forward, Y right and Z down.

	== Binary Protocol ==		== Binary Protocol ==

Thomas: /* Binary Protocol */

2008-02-06T21:39:53Z

Binary Protocol

← Older revision		Revision as of 21:39, 6 February 2008
Line 16:		Line 16:

	The binary protocol is the most compact, and gives the best precision, but can be harder to program and debug.		The binary protocol is the most compact, and gives the best precision, but can be harder to program and debug.
			To enable it, use the option

			output_udp_protocol = binary

			in the options.dat file.

			The binary protocol sends the following data:

	unsigned int timestamp; // Millisec Timestamp		unsigned int timestamp; // Millisec Timestamp

Thomas: /* Binary Protocol */

2008-02-06T14:44:28Z

Binary Protocol

← Older revision		Revision as of 14:44, 6 February 2008
Line 20:		Line 20:
	double position_latitude; // Degrees Position latitude,		double position_latitude; // Degrees Position latitude,
	double position_longitude; // Degrees longitude,		double position_longitude; // Degrees longitude,
	~~double position_altitude_QNH~~; // m ~~altitude~~ - relative to Sea-level		float altitude_msl; // m Altitude - relative to Sea-level
	float altitude_ground; // m Altitude above gnd		float altitude_ground; // m Altitude above gnd
	float altitude_ground_45; // m gnd 45 degrees ahead (NOT IMPLEMENTED YET),		float altitude_ground_45; // m gnd 45 degrees ahead (NOT IMPLEMENTED YET),
Line 36:		Line 36:
	float vy_wind		float vy_wind
	float vz_wind		float vz_wind
			float v_eas // m/sec Equivalent (indicated) air speed.
	float ax // m/sec2 Acceleration vector in body axis		float ax // m/sec2 Acceleration vector in body axis
	float ay		float ay
	float az		float az
	~~float v_eas // m/sec Equivalent (indicated) air speed.~~
	float angle_of_attack; // Degrees Angle of attack		float angle_of_attack; // Degrees Angle of attack
	float angle_sideslip; // Degrees Sideslip angle		float angle_sideslip; // Degrees Sideslip angle
Line 49:		Line 49:
	float temperature // Celcius Air temperature at aircraft altitude.		float temperature // Celcius Air temperature at aircraft altitude.

			total size: 132 bytes

	[[Category:Interfaces]]		[[Category:Interfaces]]

Thomas at 00:05, 6 January 2008

2008-01-06T00:05:54Z

← Older revision		Revision as of 00:05, 6 January 2008
Line 1:		Line 1:
	''Note: This feature is implemented in Silent Wings 1.08. It will not work with earlier versions''		''Note: This feature is implemented in Silent Wings 1.08. It will not work with earlier versions''

	Silent Wings can output various flight data to a configurable UDP socket. This can be useful for add-on developers and cockpit builders. Specifically, we support the ~~Simkits~~ protocol for output of flight data to [http://www.~~simkits~~.com ~~SimKits~~] instrument panels. In addition, we support the Condor format and our own binary format.		Silent Wings can output various flight data to a configurable UDP socket. This can be useful for add-on developers and cockpit builders. Specifically, we support the Simmeters protocol for output of flight data to [http://www.simmeters.com Simmeters] instrument panels. In addition, we support the Condor format and our own binary format.

	use_output_udp = false		use_output_udp = false
Line 9:		Line 9:
	output_udp_rate = 30		output_udp_rate = 30

	== ~~Simkits~~ Protocol ==		== Simmeters Protocol ==

	== Condor Protocol ==		== Condor Protocol ==