Tunnel - Revision history

IHaveADrone: XML coloring

2017-11-22T18:46:25Z

XML coloring

← Older revision		Revision as of 12:46, 22 November 2017
Line 14:		Line 14:
	An example on a Lisa M autopilot board		An example on a Lisa M autopilot board

			<source lang="xml">
	<firmware name="setup">		<firmware name="setup">
	<target name="tunnel" board="lisa_m_2.0" />		<target name="tunnel" board="lisa_m_2.0" />
	<target name="usb_tunnel_0" board="lisa_m_2.0" />		<target name="usb_tunnel_0" board="lisa_m_2.0" />
	</firmware>		</firmware>
			</source>

	Note, that you must replace the value of <code>board</code> with your board name.		Note, that you must replace the value of <code>board</code> with your board name.

Openuas at 10:34, 22 November 2017

2017-11-22T10:34:07Z

← Older revision		Revision as of 04:34, 22 November 2017
Line 21:		Line 21:
	Note, that you must replace the value of <code>board</code> with your board name.		Note, that you must replace the value of <code>board</code> with your board name.

	At the current state of the code only UART1 goes to UART2 and is sadly not configurable. Due to the opensource nature of PPRZ this can be made so ofcourse, you are welcomed to enhance the arch/uart_tunnel.c to add more and better functionality flexible tunnel port configuration.		At the current state of the code only '''UART1''' goes to '''UART2''' and Vice versa and is sadly not configurable. Due to the opensource nature of PPRZ this can be made so ofcourse, you are welcomed to enhance the arch/uart_tunnel.c to add more and better functionality flexible tunnel port configuration.

			Note that UART1 TX has no simple Physical connection on a Lisa/M


	== UART tunnel ==		== UART tunnel ==

Openuas at 10:32, 22 November 2017

2017-11-22T10:32:46Z

← Older revision		Revision as of 04:32, 22 November 2017
Line 22:		Line 22:

	At the current state of the code only UART1 goes to UART2 and is sadly not configurable. Due to the opensource nature of PPRZ this can be made so ofcourse, you are welcomed to enhance the arch/uart_tunnel.c to add more and better functionality flexible tunnel port configuration.		At the current state of the code only UART1 goes to UART2 and is sadly not configurable. Due to the opensource nature of PPRZ this can be made so ofcourse, you are welcomed to enhance the arch/uart_tunnel.c to add more and better functionality flexible tunnel port configuration.

	~~Side note: Only tested with TWOG board, might not (yet?) work on a Lisa M or other AP boards...~~

	== UART tunnel ==		== UART tunnel ==

Openuas at 09:48, 22 November 2017

2017-11-22T09:48:16Z

← Older revision		Revision as of 03:48, 22 November 2017
Line 22:		Line 22:

	At the current state of the code only UART1 goes to UART2 and is sadly not configurable. Due to the opensource nature of PPRZ this can be made so ofcourse, you are welcomed to enhance the arch/uart_tunnel.c to add more and better functionality flexible tunnel port configuration.		At the current state of the code only UART1 goes to UART2 and is sadly not configurable. Due to the opensource nature of PPRZ this can be made so ofcourse, you are welcomed to enhance the arch/uart_tunnel.c to add more and better functionality flexible tunnel port configuration.

			Side note: Only tested with TWOG board, might not (yet?) work on a Lisa M or other AP boards...

	== UART tunnel ==		== UART tunnel ==

Openuas at 09:39, 22 November 2017

2017-11-22T09:39:03Z

← Older revision		Revision as of 03:39, 22 November 2017
Line 4:		Line 4:
	\|}		\|}

	The Tunnel is serial-to-serial pass-through ~~that~~ connects ~~the~~ serial port, e.g. from the GPS, directly to the modem serial port or a USB-to-serial connection.		The Tunnel is serial-to-serial pass-through. It connects an autopilot serial port, e.g. from the GPS, directly to the modem serial port or a USB-to-serial connection. This I/O in turn can go to your development PC for example. There are other uses no doubt, but this in the most common use.

	The Tunnel completely replaces the normal autopilot code, leaving the USB bootloader intact). Use this for example to gain direct access to the GPS for debugging or testing. Also for configuration with [[GPS#GPS_configuration_using_U-Center\|U-Center]] it will be quite useful.		The Tunnel completely replaces the normal autopilot code, leaving the USB bootloader intact). Use this for example to gain direct access to the GPS for debugging or testing. Also for configuration with [[GPS#GPS_configuration_using_U-Center\|U-Center]] it will be quite useful.

Openuas at 09:36, 22 November 2017

2017-11-22T09:36:16Z

← Older revision		Revision as of 03:36, 22 November 2017
Line 4:		Line 4:
	\|}		\|}

	~~This completely replaces the normal autopilot code (leaving the USB bootloader intact) with a simple~~ serial-to-serial pass-through that ~~essentially~~ connects the serial port (e.g. from the GPS) directly to the modem serial port or a USB-to-serial connection ~~that creates a~~ USB ~~serial port that goes to GPS port or modem port~~. Use this ~~only~~ to gain direct access to the GPS for testing/configuration with [[GPS#GPS_configuration_using_U-Center\|U-Center]] ~~or other software~~.		The Tunnel is serial-to-serial pass-through that connects the serial port, e.g. from the GPS, directly to the modem serial port or a USB-to-serial connection.

			The Tunnel completely replaces the normal autopilot code, leaving the USB bootloader intact). Use this for example to gain direct access to the GPS for debugging or testing. Also for configuration with [[GPS#GPS_configuration_using_U-Center\|U-Center]] it will be quite useful.

	You can either use a serial UART tunnel or USB tunnel:		You can either use a serial UART tunnel or USB tunnel:

	You have to add the tunnel targets to your airframe file ~~if you want to use them~~. The tunnel targets must be part of a firmware section of <code>name="setup"</code>. ~~Add this too, if~~ it doesn't already exist in your airframe file.		You have to add the tunnel targets to your airframe file. The tunnel targets must be part of a firmware section of <code>name="setup"</code>. If it doesn't already exist in your airframe file, just add it.

			An example on a Lisa M autopilot board

	<firmware name="setup">		<firmware name="setup">
	<target name="tunnel" board="~~twog_1~~.0" />		<target name="tunnel" board="lisa_m_2.0" />
	<target name="usb_tunnel_0" board="~~twog_1~~.0" />		<target name="usb_tunnel_0" board="lisa_m_2.0" />
	</firmware>		</firmware>
	Note, that you must replace the value of <code>board</code> with your board name.
			Note, that you must replace the value of <code>board</code> with your board name.

			At the current state of the code only UART1 goes to UART2 and is sadly not configurable. Due to the opensource nature of PPRZ this can be made so ofcourse, you are welcomed to enhance the arch/uart_tunnel.c to add more and better functionality flexible tunnel port configuration.

	== UART tunnel ==		== UART tunnel ==

Simmis: Making sure ppl will not repeat my mistake and will understand that they may need to add another firmware section when using the tunnel.

2015-08-14T17:44:19Z

Making sure ppl will not repeat my mistake and will understand that they may need to add another firmware section when using the tunnel.

← Older revision		Revision as of 11:44, 14 August 2015
Line 8:		Line 8:
	You can either use a serial UART tunnel or USB tunnel:		You can either use a serial UART tunnel or USB tunnel:

	You have to add the tunnel targets to your airframe file if you want to use them:		You have to add the tunnel targets to your airframe file if you want to use them. The tunnel targets must be part of a firmware section of <code>name="setup"</code>. Add this too, if it doesn't already exist in your airframe file.
	<firmware name="setup">		<firmware name="setup">
	<target name="tunnel" board="twog_1.0" />		<target name="tunnel" board="twog_1.0" />
	<target name="usb_tunnel_0" board="twog_1.0" />		<target name="usb_tunnel_0" board="twog_1.0" />
	</firmware>		</firmware>
			Note, that you must replace the value of <code>board</code> with your board name.
	== UART tunnel ==		== UART tunnel ==

Flixr: move tunnel stuff from compiling page to here

2013-02-07T15:31:43Z

move tunnel stuff from compiling page to here

@@ Line 1: / Line 1: @@
 Required Cables:
 <ol>
@@ Line 21: / Line 51: @@
 </pre>
 <p>Now your Tiny2.11 will tunnel UART1 from the GPS direct to the serial connector on the board. So, using the 8-pin Molex to FTDI cable adapter (or use the wireless link e.g. XBee) you can use your computer to interact with the GPS module. One example is using u-blox u-center program to configure your GPS module. Like the bootloader if you bought your Tiny2.11 assembled check with your 3rd party vendors configured your GPS. Good chance you won't need to use the tunnel or configure the GPS module.</p> The required cable may included with 3rd party vendors!
-[[Category:User_Documentation]]
+[[Category:Firmware]] [[Category:User_Documentation]]

Esden at 20:30, 10 March 2011

2011-03-10T20:30:38Z

← Older revision		Revision as of 14:30, 10 March 2011
Line 22:		Line 22:
	<p>Now your Tiny2.11 will tunnel UART1 from the GPS direct to the serial connector on the board. So, using the 8-pin Molex to FTDI cable adapter (or use the wireless link e.g. XBee) you can use your computer to interact with the GPS module. One example is using u-blox u-center program to configure your GPS module. Like the bootloader if you bought your Tiny2.11 assembled check with your 3rd party vendors configured your GPS. Good chance you won't need to use the tunnel or configure the GPS module.</p> The required cable may included with 3rd party vendors!		<p>Now your Tiny2.11 will tunnel UART1 from the GPS direct to the serial connector on the board. So, using the 8-pin Molex to FTDI cable adapter (or use the wireless link e.g. XBee) you can use your computer to interact with the GPS module. One example is using u-blox u-center program to configure your GPS module. Like the bootloader if you bought your Tiny2.11 assembled check with your 3rd party vendors configured your GPS. Good chance you won't need to use the tunnel or configure the GPS module.</p> The required cable may included with 3rd party vendors!
	[http://paparazzi.enac.fr/wiki/Tiny_v2#Programming BACK]		[http://paparazzi.enac.fr/wiki/Tiny_v2#Programming BACK]

			[[Category:User_Documentation]]

Flixr: fix link

2010-10-08T21:55:13Z

fix link

← Older revision		Revision as of 15:55, 8 October 2010
Line 21:		Line 21:
	</pre>		</pre>
	<p>Now your Tiny2.11 will tunnel UART1 from the GPS direct to the serial connector on the board. So, using the 8-pin Molex to FTDI cable adapter (or use the wireless link e.g. XBee) you can use your computer to interact with the GPS module. One example is using u-blox u-center program to configure your GPS module. Like the bootloader if you bought your Tiny2.11 assembled check with your 3rd party vendors configured your GPS. Good chance you won't need to use the tunnel or configure the GPS module.</p> The required cable may included with 3rd party vendors!		<p>Now your Tiny2.11 will tunnel UART1 from the GPS direct to the serial connector on the board. So, using the 8-pin Molex to FTDI cable adapter (or use the wireless link e.g. XBee) you can use your computer to interact with the GPS module. One example is using u-blox u-center program to configure your GPS module. Like the bootloader if you bought your Tiny2.11 assembled check with your 3rd party vendors configured your GPS. Good chance you won't need to use the tunnel or configure the GPS module.</p> The required cable may included with 3rd party vendors!
	[http://paparazzi.enac.fr/wiki~~/index.php~~/Tiny_v2#Programming BACK]		[http://paparazzi.enac.fr/wiki/Tiny_v2#Programming BACK]