Difference between revisions of "User/LisaM"

From PaparazziUAV
Jump to navigation Jump to search
(Moved revision history to its right place)
m (redirect to correct page right away)
 
(19 intermediate revisions by 5 users not shown)
Line 1: Line 1:
= Introduction =
#REDIRECT [[Lisa/M v2.0]]
 
If you consider yourself a developer this flexible piece of UAS hardware is for you. If you enjoy writing software and consider yourself an early adopter this is the board to use. Have fun implementing and extending the already great features. To show of your work and also to ask questions, you are welcomed on the paparazzi mailinglist, this Wiki and the freenode paparazzi IRC channel. This nice piece of hardware can be used for various purposes. Ofcourse as an Autopilot board, but only by uploading another firmware also a servo extension board and more. A good idea of how this nice piece of hardware looks like is shown on the Photos here. If you are not so interested in all of this at the moment since you just have this shiny new board on you desk and want to connect and fly the thing, then go to the page [http://paparazzi.enac.fr/wiki/User/LisaM/Tutorial/FixedWing using the board as an '''Autopilot''' for an airplane] or go [http://paparazzi.enac.fr/wiki/User/LisaM/Tutorial/RotorCraft here for uses a an '''Autopilot''' in a quadrotor]
 
[[Image:Lisa_M_V1_0_top_with_coin.jpg|thumb|Lisa/M V1.0 top view]]
[[Image:Lisa_M_V1_0_bottom_with_coin.jpg|thumb|Lisa/M V1.0 bottom view]]
[[Image:Lisa_M_V1_0_top.jpg|thumb|Lisa/M V1.0 top view]]
[[Image:Lisa_M_V1_0_bottom.jpg|thumb|Lisa/M V1.0 bottom view]]
 
= Initial Setup =
 
If you want to just simply setup the board for use as an Autopilot and are looking for information about how to get the Lisa/M board up and running and where to connect other hardware just follow the link below if you have that great Lisa/M board and want to get get it airborne fast.
 
[[User/LisaM/Tutorial/FixedWing]] An airplane or just plane.
 
[[User/LisaM/Tutorial/RotorCraft]] everything that flies via moving blades, for example Helicopter, Quadcopter or something alike
= Features =
 
Lisa/M is based on the 64 pins STM32F105RC processor featuring 64k of RAM and 256k of FLASH. All the pins are exposed, providing access to the complete set of the STM32 peripherals.
 
 
== Overview ==
 
* Single [http://www.st.com/stm32 STM32 MCU]
* Pressure sensor [http://www.bosch-sensortec.com/content/language1/html/3477.htm BMP085]
* 7 x Analog input channels
* 3 x Generic digital in-/out-puts
* 2 x 3.3V TTL UART (5V tolerant)
* 7 x Servo PPM outputs
* 1 x CAN bus
* 1 x [http://en.wikipedia.org/wiki/Serial_Peripheral_Interface SPI] bus
* 1 x [http://en.wikipedia.org/wiki/I2c I<sup>2</sup>C] bus
* 1 x Micro USB
* 4 x status LEDs with attached test point
* 10.8 grams (0.4 oz) (with Aspirin IMU mounted)
* 9.9 grams (0.35 oz) (without Aspirin IMU mounted)
* ~33mm x ~56mm x ~10mm
* 4 layers PCB design
 
with mounted IMU has the following additional sensors on board:
 
* 3 Axis Gyroscope
* 3 Axis Accelerometer
* 3 Axis Magnetometer
 
The pressure sensor is mounted directly on the board as this sensor is not provided by Aspirin. Exept for a GPS unit you have all necessary sensors for full attitude and altitude stabilization in an extremely small package. Adding only an external GPS unit, it is a full fledged Autopilot.
 
== Footprint ==
 
This autopilot is very small. The footprint is only 33mm by 56mm by 10mm including the servo connector pins. It will fit in a small UAS very well. There is a spot for mounting the [http://paparazzi.enac.fr/wiki/AspirinIMU Aspirin IMU] directly on board.
 
== MCU ==
 
In brief, the STM32 features 3 USARTS, 2 SPI, 2 I2C, 1 CAN, a plethora of timers, ADCs and a generic DMA able to serve all of them. On the board, a number of the communication interfaces are level shifted with user selectable voltage to allow interfacing with all kind of peripherals.
 
== Onboard IMU ==
 
The Lisa/M comes with [http://paparazzi.enac.fr/wiki/AspirinIMU Aspirin IMU] mounted, for easy attitude estimation in the smallest package possible.
 
== JTAG ==
 
Information about debugging can be found [http://paparazzi.enac.fr/wiki/Dev/Debugging here]
 
= Hardware Revision History =
 
== Changes between v0.1 and v1.0 ==
* Switched to stm32f105 to be able to use usb and can at the same time
* Added alternative use of the adc lines as led output
* ...
 
== Changes between v1.0 and v1.1 ==
* Removed pull-ups on the USB gpio
* Removed pull-ups on the CAN gpio
* Connected usb_vbus to pa9 (needed by the USBotg)
* Removed USB pullup transistor as usbotg has a built in pullup
* Swapped UART1 with UART3 (uart1 was used for gps and pa9 was it's tx line, to be able to talk to the gps unit uart3 is a better choice, as uart1 only has an rx line now it is a better choice for spektrum RX modules)
* Removed USART3 TX gpio from the GPIO connector and moved to the GPS connector
* Added voltage selector jumpers to the RC RX connector; to enable powering of 3v3 or an 5v receivers
* Replaced vertical board solution with through hole servo pin headers (easier assembly)
* Servo connectors are in groups of two; for easier assembly
* Servo VBUS is connected together on all four layers; for lower resistance
* Moved LED's from under the analog2 connector; to be able to populate LED's and the connector
* Moved the RC RX connector a bit; to prevent crashing with the jtag plug
* Added one additional servo connector; now we have all 8 accessible through the standard servo connectors
* Fixed servo channel labeling to start at '''S0''' as it is the case on TWOG and Tiny autopilot boards
* Added secondary through hole picoblade USB connector for easier routing of USB inside an airframe
* ...
 
== Changes between v1.1 and v2.0 ==
* Lot's of silkscreen improvements
* Added attributes to all parts to make the usage of bom-ex ulp possible.
* Improved routing to allow teardropping
* Fixed stm32f1, f2 and f4 compatibility circuit. (has to jump to ground not to 3v3)
* Connected existing UART RX pullups to the respective connector power pins instead of 3v3. To prevent connecting 5V over IO pin to the 3v3 power rail.
* Added pullups on all UART RX lines to prevent undesired floatation.
* LED's are connected to 3v3 now. To make sure we don't have an issue with voltage tolerance on the gpio pins.
* ...
 
= Architecture =
 
= Usage scenarios =
 
For regular Autopilot boards a full Lisa/M board is needed. For some scenarios just a basic Lisa/M without IMU and pressure sensor is needed, this makes the board cheaper of course.
 
== As a basic Autopilot ==
 
To use the Lisa/M as an autopilot, we need to attach a GPS receiver. A nice uBlox LEA-5H or newer will perform great.
 
== As and advanced Autopilot ==
 
Also an external airspeedsensor like the Eagletree would enhance a fixedwing airframe. Ofcourse an extention cable from microUAS to Mini USB to the outside of the airframe is very practical.
Currently UART3 outlet is used to talk to GPS reciever.
 
== As a servo extender ==
 
Sometimes being able to steer seven actuators is just not enough. One need for example flaps that enhance aileron or an airbrake and automatic landingfacility. Maybe special ACL lights, or four cameras with zoom. By using a coupled second basic Lisa/M and connect this to the master AP board we can extend our amount of servos.
 
== As a Safety Pilot Device ==
 
To provide an extra safety level required in some UAS challenges a second Lisa board can make it easy to adhere to the rules for such a challenge.
 
== As a Data Logger ==
 
Maybe you have a need only to log all kinds of data, like temperature, volts, amps, height, airspeed only. For this we can setup a Lisa/M board. Then we are flexible and add whatever sensors we want. Collecting this data can be to a storage medium like an micro SD card. Sometimes there is no need for realtime data collection but just for storing a huge dataset.
 
== As a Camera controller ==
On some models that do not require much servos (for example - flying wing with only 3 chanels used), spare channels can be used for camera control.
 
== As a Airframe Tracker ==
 
A remote antenna or camera on a tripod is on of the may option to use a Lisa/M Board. The remote device Must be able to get data from the pale in one form or another.
 
= Pinout =
 
Pins Name and Type are specified with respect to the Autopilot Board
 
[[Image:LisaM_V1_0_top_labeled.png|700px]]
 
= Schematic =
 
<gallery>
Image:Lisa_m_v1_0_sheet_1.png | LisaM V1.0 Schematic Sheet 1/3
Image:Lisa_m_v1_0_sheet_2.png | LisaM V1.0 Schematic Sheet 2/3
Image:Lisa_m_v1_0_sheet_3.png | LisaM V1.0 Schematic Sheet 3/3
</gallery>
 
= Electrical Connections to the Airborne Equipment =
 
= PCB =
 
== Gerber & Drill Files  ==
 
= Assembly =
 
== Components Layout ==
 
== Mechanical drawing ==
 
[[Image:LisaM_V1_0_top_mechanical.png|500px]]
 
=== Bill Of Material ===
 
 
[[Category:User_Documentation]] [[Category:Hardware]]
 
= PCB and assembled boards suppliers =
 
For private companies and enthusiast Paparazzi hardware suppliers, see [[Get_Hardware|Get Hardware]] page.
 
= Downloads =
 
The CAD files are also available from the [http://svn.sv.gnu.org/svn/paparazzi/paparazzi-hardware/trunk/lisa_m/ paparazzi-hardware svn server]
 
'''Schematics'''
* [[Image:Lisa m v1 0 sheet1 of 3.pdf]]
* [[Image:Lisa m v1 0 sheet2 of 3.pdf]]
* [[Image:Lisa m v1 0 sheet3 of 3.pdf]]
 
'''Source files'''
:*download ''LisaM v1.00 Eagle design (zip)''
'''Gerber & Drill files'''
:*download '' gerber & drill files (zip)''
'''Assembly files'''
:*download ''(pdf)''
:*download '' (zipped .xls file)''

Latest revision as of 07:46, 16 December 2012

Redirect to:

Retrieved from "http://wiki.paparazziuav.org/w/index.php?title=User/LisaM&oldid=13884"