Skip to content

Commit 156eafa

Browse files
committedJan 6, 2016
Merge pull request #38 from SenteraLLC/JRW-Stackup_Photo
Stackup photo
2 parents 3645954 + da96fbb commit 156eafa

File tree

4 files changed

+17
-4
lines changed

4 files changed

+17
-4
lines changed
 

‎README.md

+17-4
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
1-
# FMU Communications Board
1+
# FMU Communications Board
22

33
Initial development performed by partnership of [Sentera, LLC](https://sentera.com/) and [University of Minnesota](http://www.uav.aem.umn.edu/).
44

55
## System Overview
6-
![System Diagram](/doc/System%20Diagram.png?raw=true "System Diagram")
6+
![System Diagram](/doc/System%20Diagram.jpg?raw=true "System Diagram")
77

88
The FMU Communications Board is designed as a component of the Flight Management System. The FMU Communications Board is a Microchip PIC32 based module with the primary function of managing communications between the FMU Processing Board and the rest of the Flight Management System. The Ethernet and CAN communication protocols are detailed in file [UMN FMU Communication Protocol](/doc/UMN%20FMU%20Communication%20Protocol.docx).
99

@@ -59,6 +59,19 @@ The hardware contains the following physical interfaces:
5959
6060
*Note: Power for the FMU Communications Board must be in the range of 3.6V to 36V.*
6161

62+
### Hardware Stackup
63+
![Stackup Build](/doc/Hardware%20Stack.jpg?raw=true "Stackup Build")
64+
65+
The above picture shows a constructed hardware stackup. The boards on the stackup (from bottom to top) are:
66+
67+
1. FMU Processing Board (Beaglebone Black)
68+
2. Beaglebone Cape - with IMU
69+
3. GPS receiver
70+
4. Sentera Comms Board
71+
5. uHard Datalink
72+
73+
Additional hardware photos can be found on the University of Minnesota [media page](http://www.uav.aem.umn.edu/wiki/Media).
74+
6275
## Software Overview
6376
Source code is commented using Doxygen style formatting. Therefore, Doxygen can be used to generate an easily navigable document which provides greater detail into the software's operation than the overview which is provided here.
6477

@@ -81,10 +94,10 @@ The software implements a preemptive, cyclic executive using eight threads. The
8194

8295
4. **Default**: Thread is executed if any unexpected interrupts occur.
8396

84-
All main software processing is performed in the 'Reset' thread. All other threads have a higher priority (i.e. can preempt the 'Reset' thread) and purely handle servicing of the hardware. The 'Reset' thread implement cooperative multitasking, where tasks are performed continuously, with the execution time of individual tasks being in the micro-second order of magnitude. This allows for immediate response to system inputs and a small jitter in system output timing.
97+
All main software processing is performed in the 'Reset' thread. All other threads have a higher priority (i.e. can preempt the 'Reset' thread) and purely handle servicing of the hardware. The 'Reset' thread implements cooperative multitasking, where tasks are performed continuously, with the execution time of individual tasks being in the micro-second order of magnitude. This allows for immediate response to system inputs and a small jitter in system output timing.
8598

8699
### Software Modules
87-
The software is a modular design. The software modules are explained below, and map directly to [source code](/src) file names:
100+
The software is a modular design. The software modules are explained below, and map directly to [source code](/src) file or folder names:
88101

89102
>**adc**: Analog to Digital Converter (ADC) driver.
90103

‎doc/Hardware Stack.jpg

106 KB
Loading

‎doc/System Diagram.jpg

57.5 KB
Loading

‎doc/System Diagram.png

-127 KB
Binary file not shown.

0 commit comments

Comments
 (0)
Please sign in to comment.