User:SilaS - Revision history

SilaS at 20:30, 6 October 2009

2009-10-06T20:30:51Z

← Older revision		Revision as of 14:30, 6 October 2009
Line 109:		Line 109:

	It makes You after You plug the usb cable into your laptop a new /dev/paparazzi/usb link to the corresponding ttyUSB. You can use it at link definition and you can finaly forget to watching every time, where did it mapped time-to-time the device :-)		It makes You after You plug the usb cable into your laptop a new /dev/paparazzi/usb link to the corresponding ttyUSB. You can use it at link definition and you can finaly forget to watching every time, where did it mapped time-to-time the device :-)

			<h2>The achivement</h2>

			[[Jet powered]]

	<h2>Contact</h2>		<h2>Contact</h2>

SilaS at 10:49, 22 January 2008

2008-01-22T10:49:33Z

← Older revision		Revision as of 04:49, 22 January 2008
Line 31:		Line 31:
	<h2>On going:</h2>		<h2>On going:</h2>
	<ul>		<ul>
	<li>My first flight ~~plan plans: failover return to home~~, ~~simple circle around home~~</li>		<li>I conducted the first AUTO2 flight!</li>
			<li>It still kill my throttle, because my batteries drop voltage too deep during motorized flight...</li>
	<li>Fly it in AUTO1, AUTO2 and if stable transfer it to p13</li>		<li>Fly it in AUTO1, AUTO2 and if stable transfer it to p13</li>
	</ul>		</ul>

SilaS at 10:45, 22 January 2008

2008-01-22T10:45:52Z

← Older revision		Revision as of 04:45, 22 January 2008
Line 23:		Line 23:
	<li>I installed it on my old estarter http://silas.fornax.hu/album/flying/200710/tiny/</li>		<li>I installed it on my old estarter http://silas.fornax.hu/album/flying/200710/tiny/</li>
	<li>The SDK-AC4868-250 FINALY is on my DESK!</li>		<li>The SDK-AC4868-250 FINALY is on my DESK!</li>
			<li>Calibration! almost done.</li>
			<li>Configuration of SDK-AC4868-250!!!</li>
			<li>Deal with IR sensor to produce a correct artifical horizon. DONE.</li>
	</ul>		</ul>
	<p>		<p>

SilaS at 10:45, 22 January 2008

2008-01-22T10:45:24Z

← Older revision		Revision as of 04:45, 22 January 2008
Line 28:		Line 28:
	<h2>On going:</h2>		<h2>On going:</h2>
	<ul>		<ul>
	~~<li>Calibration! almost done.</li>~~
	~~<li>Configuration of SDK-AC4868-250!!!</li>~~
	~~<li>Deal with IR sensor to produce a correct artifical horizon. DONE.</li>~~
	<li>My first flight plan plans: failover return to home, simple circle around home</li>		<li>My first flight plan plans: failover return to home, simple circle around home</li>
	<li>Fly it in AUTO1, AUTO2 and if stable transfer it to p13</li>		<li>Fly it in AUTO1, AUTO2 and if stable transfer it to p13</li>

SilaS at 10:39, 22 January 2008

2008-01-22T10:39:04Z

← Older revision		Revision as of 04:39, 22 January 2008
Line 61:		Line 61:
	Then use this patch:		Then use this patch:

			<pre>
	--- cp2101.c 2006-09-06 21:36:31.000000000 +0200		--- cp2101.c 2006-09-06 21:36:31.000000000 +0200
	+++ cp2101.c-working 2007-12-18 21:34:25.000000000 +0100		+++ cp2101.c-working 2007-12-18 21:34:25.000000000 +0100
Line 96:		Line 97:
	{ USB_DEVICE(0x10AB, 0x10C5) }, /* Siemens MC60 Cable */		{ USB_DEVICE(0x10AB, 0x10C5) }, /* Siemens MC60 Cable */
	{ } /* Terminating Entry */		{ } /* Terminating Entry */
			</pre>

	If You want to made it a bit more confortable, then made udev rules, like this 10-aerocomm.rules:		If You want to made it a bit more confortable, then made udev rules, like this 10-aerocomm.rules:
			<pre>
	BUS=="usb", SYSFS{serial}=="14338", KERNEL=="ttyUSB*", SYMLINK+="cp2101", MODE="0666"		BUS=="usb", SYSFS{serial}=="14338", KERNEL=="ttyUSB*", SYMLINK+="cp2101", MODE="0666"

	# mapping		# mapping
	BUS=="usb", SYSFS{idVendor}=="10c4", SYSFS{idProduct}=="81e7", KERNEL=="ttyUSB*", SYMLINK+="paparazzi/usb", GROUP="dialout"		BUS=="usb", SYSFS{idVendor}=="10c4", SYSFS{idProduct}=="81e7", KERNEL=="ttyUSB*", SYMLINK+="paparazzi/usb", GROUP="dialout"
			</pre>

	It makes You after You plug the usb cable into your laptop a new /dev/paparazzi/usb link to the corresponding ttyUSB. You can use it at link definition and you can finaly forget to watching every time, where did it mapped time-to-time the device :-)		It makes You after You plug the usb cable into your laptop a new /dev/paparazzi/usb link to the corresponding ttyUSB. You can use it at link definition and you can finaly forget to watching every time, where did it mapped time-to-time the device :-)

SilaS at 10:33, 22 January 2008

2008-01-22T10:33:42Z

@@ Line 55: / Line 55: @@
 [[Image:PC230110 small.JPG]]
-...
+I am using kernel 2.6.22-14.generic from package.
 <h2>Contact</h2>

SilaS at 10:25, 22 January 2008

2008-01-22T10:25:04Z

← Older revision		Revision as of 04:25, 22 January 2008
Line 53:		Line 53:
	First of all, the standard cp2103 driver in the kernel does not known the Aerocomm Developer Board. Therefore You need to patch the kernel module and use it, if You want to use it in well designed developer board to avoid EMI.		First of all, the standard cp2103 driver in the kernel does not known the Aerocomm Developer Board. Therefore You need to patch the kernel module and use it, if You want to use it in well designed developer board to avoid EMI.

	[[Image:PC230110 small.~~jpg~~]]		[[Image:PC230110 small.JPG]]

	...		...

SilaS at 10:23, 22 January 2008

2008-01-22T10:23:51Z

← Older revision		Revision as of 04:23, 22 January 2008
Line 53:		Line 53:
	First of all, the standard cp2103 driver in the kernel does not known the Aerocomm Developer Board. Therefore You need to patch the kernel module and use it, if You want to use it in well designed developer board to avoid EMI.		First of all, the standard cp2103 driver in the kernel does not known the Aerocomm Developer Board. Therefore You need to patch the kernel module and use it, if You want to use it in well designed developer board to avoid EMI.

	[[Image:~~PC230110_small~~.jpg]]		[[Image:PC230110 small.jpg]]

	...		...

SilaS at 10:20, 22 January 2008

2008-01-22T10:20:22Z

← Older revision		Revision as of 04:20, 22 January 2008
Line 52:		Line 52:

	First of all, the standard cp2103 driver in the kernel does not known the Aerocomm Developer Board. Therefore You need to patch the kernel module and use it, if You want to use it in well designed developer board to avoid EMI.		First of all, the standard cp2103 driver in the kernel does not known the Aerocomm Developer Board. Therefore You need to patch the kernel module and use it, if You want to use it in well designed developer board to avoid EMI.

			[[Image:PC230110_small.jpg]]

	...		...

SilaS at 10:09, 22 January 2008

2008-01-22T10:09:37Z

← Older revision		Revision as of 04:09, 22 January 2008
Line 44:		Line 44:
	- and of course the R/C is affected also - mostly from the modem<br>		- and of course the R/C is affected also - mostly from the modem<br>
	- the video sends a continuous wave at a very high frequency, but the modem sends "blocks" of data, so even though it is operating at high frequency, it is "turning on/off" at a much lower frequency, frequencies similar to R/C or analog sensors<br>		- the video sends a continuous wave at a very high frequency, but the modem sends "blocks" of data, so even though it is operating at high frequency, it is "turning on/off" at a much lower frequency, frequencies similar to R/C or analog sensors<br>

			<h2>Contribution</h2>

			<h3>SDK-AC4868-250 ground modem part</h3>

			How to use your modem inside the developer board over USB cable?

			First of all, the standard cp2103 driver in the kernel does not known the Aerocomm Developer Board. Therefore You need to patch the kernel module and use it, if You want to use it in well designed developer board to avoid EMI.

			...

	<h2>Contact</h2>		<h2>Contact</h2>
Line 49:		Line 59:
	Please contact me, if You are able to help to achieve this goals, or of course have any questions!		Please contact me, if You are able to help to achieve this goals, or of course have any questions!

	SilaS <silas"at"~~fornax~~.hu>		SilaS <silas"at"silas.hu>