Input2Ivy - Revision history

IHaveADrone: spelling

2016-09-15T17:00:31Z

spelling

← Older revision		Revision as of 11:00, 15 September 2016
Line 6:		Line 6:
	= Compiling Input2Ivy =		= Compiling Input2Ivy =

	The program is located in <tt>sw/ground_segment/joystick</tt>. It should already be compiled with the top level make, you also can ~~explictly~~ build it with <tt>make</tt> in <tt>sw/ground_segment/joystick</tt>		The program is located in <tt>sw/ground_segment/joystick</tt>. It should already be compiled with the top level make, you also can explicitly build it with <tt>make</tt> in <tt>sw/ground_segment/joystick</tt>

	* the C library sdl_stick (using SDL)		* the C library sdl_stick (using SDL)

Earthpatrol at 17:38, 2 September 2016

2016-09-02T17:38:04Z

← Older revision		Revision as of 11:38, 2 September 2016
Line 102:		Line 102:
	= Usage =		= Usage =

	./sw/ground_segment/joystick/input2ivy [options] config_file.xml		$ ./sw/ground_segment/joystick/input2ivy [options] config_file.xml

	The options are:		The options are:
Line 112:		Line 112:
	* -id set the joystick ID (in range [0,255], a random value is chosen if not set)		* -id set the joystick ID (in range [0,255], a random value is chosen if not set)
	Do not forget the configuration file name after the options.		Do not forget the configuration file name after the options.

			Example invocation on Mac OS X using a SNES gamepad configuration as input:

			$ ./sw/ground_segment/joystick/input2ivy -b 224.255.255.255:2010 -ac Teensy_Fly_Quad_Elle0_v1_2_214 -d 0 snes_gamepad.xml

	Input2Ivy can be launched from the Paparazzi Center if your conf/control_panel.xml have the correct 'program' entry. (See conf/control_panel.xml.example)		Input2Ivy can be launched from the Paparazzi Center if your conf/control_panel.xml have the correct 'program' entry. (See conf/control_panel.xml.example)

	[[Category:Tools]]		[[Category:Tools]]

Flixr: /* Xml configuration file */

2014-10-28T21:14:15Z

Xml configuration file

← Older revision		Revision as of 15:14, 28 October 2014
Line 51:		Line 51:
	<source lang="xml">		<source lang="xml">
	<messages period="0.1">		<messages period="0.1">
	<message class="datalink" name="~~BOOZ_NAV_STICK~~">		<message class="datalink" name="RC_4CH" send_always="true">
	<field name="~~vx_sp~~" value="-~~pitch~~"/>		<field name="mode" value="mode"/>
	<field name="~~vy_sp~~" value="roll"/>		<field name="throttle" value="Bound(0-ly,0,127)"/>
	<field name="~~vz_sp~~" value="~~(up-down)*127~~"/>		<field name="roll" value="roll"/>
	<field name="~~r_sp~~" value="~~(right-left)*127~~"/>		<field name="yaw" value="yaw"/>
	</message>		<field name="pitch" value="pitch"/>
			</message>
	<message class="ground" name="JUMP_TO_BLOCK" on_event="shoot && button1"/>		<message class="ground" name="JUMP_TO_BLOCK" on_event="shoot && button1"/>
	<field name="block_id" value="IndexOfBlock('land')"/>		<field name="block_id" value="IndexOfBlock('land')"/>
			</message>
			<message class="ground" name="DL_SETTING" on_event="button2">
			<field name="index" value="IndexOfSetting(kill_throttle)"/>
			<field name="value" value="1"/>
	</message>		</message>
	...		...

Flixr: /* Xml configuration file */

2014-10-28T20:59:56Z

Xml configuration file

← Older revision		Revision as of 14:59, 28 October 2014
Line 16:		Line 16:
	== Xml configuration file ==		== Xml configuration file ==

	Input2Ivy reads the configuration of your input device in a ~~Xml~~ file located in conf/joystick. The format is as follow:		Input2Ivy reads the configuration of your input device in a xml file located in <tt>conf/joystick</tt>. The format is as follow:
	<source lang="xml">		<source lang="xml">
	<joystick>		<joystick>

Flixr: /* Compiling Input2Ivy */

2014-10-28T20:57:19Z

Compiling Input2Ivy

← Older revision		Revision as of 14:57, 28 October 2014
Line 6:		Line 6:
	= Compiling Input2Ivy =		= Compiling Input2Ivy =

	The program is located in sw/ground_segment/joystick. ~~In order to use~~ it ~~you need type '~~make' in ~~this folder after building the whole paparazzi sources (it will be added in the default set of compile program in the future).~~		The program is located in <tt>sw/ground_segment/joystick</tt>. It should already be compiled with the top level make, you also can explictly build it with <tt>make</tt> in <tt>sw/ground_segment/joystick</tt>

	~~The compiled programs are:~~
	* the C library sdl_stick (using SDL)		* the C library sdl_stick (using SDL)
	* input2ivy (ocaml main program that uses sdl_stick)		* input2ivy (ocaml main program that uses sdl_stick)

Flixr: /* Compiling Input2Ivy */

2014-10-28T20:53:30Z

Compiling Input2Ivy

← Older revision		Revision as of 14:53, 28 October 2014
Line 9:		Line 9:

	The compiled programs are:		The compiled programs are:
	* the C library ~~usb_stick~~ (~~we are planing to use~~ SDL ~~in the future for better cross-platform integration~~)		* the C library sdl_stick (using SDL)
	* input2ivy (ocaml main program that uses ~~usb_stick~~)		* input2ivy (ocaml main program that uses sdl_stick)
	* test_stick (a small C test program that display raw values of your joystick)		* test_stick (a small C test program that display raw values of your joystick)

IHaveADrone: source lang to xml

2014-10-07T13:47:40Z

source lang to xml

← Older revision		Revision as of 07:47, 7 October 2014
Line 18:		Line 18:

	Input2Ivy reads the configuration of your input device in a Xml file located in conf/joystick. The format is as follow:		Input2Ivy reads the configuration of your input device in a Xml file located in conf/joystick. The format is as follow:
			<source lang="xml">
	<joystick>		<joystick>
			</source>
	Start with the node 'joystick', no DTD yet.		Start with the node 'joystick', no DTD yet.

			<source lang="xml">
	<input>		<input>
	<axis index="0" name="roll"/>		<axis index="0" name="roll"/>
Line 32:		Line 34:
	...		...
	</input>		</input>
			</source>

	In this section, all the axis and buttons are described with an index and a name. Both have to be unique.		In this section, all the axis and buttons are described with an index and a name. Both have to be unique.
	* the index is the actual axis or button number of your input device (you can use 'test_stick' to determine each index)		* the index is the actual axis or button number of your input device (you can use 'test_stick' to determine each index)
	* the name is chosen by the user		* the name is chosen by the user

			<source lang="xml">
	<variables>		<variables>
	<var name="mode" default="0"/>		<var name="mode" default="0"/>
Line 42:		Line 47:
	...		...
	</variables>		</variables>
			</source>
	The section 'variables' allows to declare local variables to the program, those value can be changed based on inputs event. First you need to declare the variable with a default value (integer) and then each event is describe with the 'set' node. It is possible to use logical "C-like" expression for the event (&&, \|\|, <, >, ...).		The section 'variables' allows to declare local variables to the program, those value can be changed based on inputs event. First you need to declare the variable with a default value (integer) and then each event is describe with the 'set' node. It is possible to use logical "C-like" expression for the event (&&, \|\|, <, >, ...).

			<source lang="xml">
	<messages period="0.1">		<messages period="0.1">
	<message class="datalink" name="BOOZ_NAV_STICK">		<message class="datalink" name="BOOZ_NAV_STICK">
Line 56:		Line 63:
	...		...
	</messages>		</messages>
			</source>
	The 'messages' section describes the messages sent to [[Ivy]].		The 'messages' section describes the messages sent to [[Ivy]].
	* the 'period' attribute define the period for sending the messages. A message is send only the at least one of its field has changed since last sending. Only messages with 'send_always="true"' are always sent.		* the 'period' attribute define the period for sending the messages. A message is send only the at least one of its field has changed since last sending. Only messages with 'send_always="true"' are always sent.
Line 66:		Line 74:
	** name: the name of the field (mandatory)		** name: the name of the field (mandatory)
	** value: the value to be sent (here, expressions can be used, see below) (mandatory)		** value: the value to be sent (here, expressions can be used, see below) (mandatory)
			<source lang="xml">
	</joystick>		</joystick>
			</source>
	Close 'joystick' node.		Close 'joystick' node.

Flixr: since v4.2 the -d option specified the sdl index (usually 0)

2013-06-10T13:04:34Z

since v4.2 the -d option specified the sdl index (usually 0)

← Older revision		Revision as of 07:04, 10 June 2013
Line 94:		Line 94:
	* -ac <AC name> the name of your aircraft (mandatory)		* -ac <AC name> the name of your aircraft (mandatory)
	* -b <ivy_bus> the an ivy bus address (default address used if not set)		* -b <ivy_bus> the an ivy bus address (default address used if not set)
	* -d <device_name> set the device name (default is /dev/input/js0)		* -d <device_index> set the SDL device index (default is 0)
			** for paparazzi versions older than v4.2 use: -d <device_name> set the device name (default is /dev/input/js0))
	* -v verbose mode (can also be used to identify the channels)		* -v verbose mode (can also be used to identify the channels)
	* -id set the joystick ID (in range [0,255], a random value is chosen if not set)		* -id set the joystick ID (in range [0,255], a random value is chosen if not set)

Flixr: /* Trims */

2013-02-11T21:10:37Z

Trims

← Older revision		Revision as of 15:10, 11 February 2013
Line 83:		Line 83:

	== Trims ==		== Trims ==
			First calibrate your joystick as described on the [[Joystick]] page.

	~~TBD~~		In flight trimming is to be done...

	= Usage =		= Usage =

Flixr at 13:53, 24 January 2013

2013-01-24T13:53:46Z

← Older revision		Revision as of 07:53, 24 January 2013
Line 99:		Line 99:

	Input2Ivy can be launched from the Paparazzi Center if your conf/control_panel.xml have the correct 'program' entry. (See conf/control_panel.xml.example)		Input2Ivy can be launched from the Paparazzi Center if your conf/control_panel.xml have the correct 'program' entry. (See conf/control_panel.xml.example)

			[[Category:Tools]]