936
edits
Howto:Build your own Panel or Cockpit - Cockpit Systems and Hardware: Difference between revisions
Jump to navigation
Jump to search
Howto:Build your own Panel or Cockpit - Cockpit Systems and Hardware (view source)
Revision as of 14:40, 30 November 2017
, 30 November 2017no edit summary
No edit summary |
|||
| Line 2: | Line 2: | ||
{{WIP}} | {{WIP}} | ||
==== Overview ==== | ==== Overview ==== | ||
There are five levels of hardware and software activity needed for a cockpit. | There are five levels of hardware and software activity needed for a cockpit. Levels 1-4 may include software. The levels provide a model for thinking about how to structure the hardware and software of the cockpit. This model does not necessarily mean that the work done at a given level must run on a physically separate platforms. | ||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
! Level !! What's there | ! Level !! What's there !! Why | ||
|- | |- | ||
| Simulator Software | | Simulator Software | ||
| Line 12: | Line 12: | ||
* X-Plane | * X-Plane | ||
* Prepare3D | * Prepare3D | ||
| Provides a model of the airplane, it's controls, its visual aspects, its motion and its environment. Simulator Software communicates with external hardware through one or more interfaces. | |||
|- | |- | ||
| Cockpit System | | Cockpit System | ||
| Line 18: | Line 19: | ||
* BeagleBone | * BeagleBone | ||
* PC | * PC | ||
| Through the Simulator Software's external interface, the cockpit system provides user inputs from cockpit controls, radios and instruments. At the same time, the system obtains model data to drive physical display canges in the cockpit. | |||
|- | |- | ||
| Controllers || | | Controllers || | ||
| Line 24: | Line 26: | ||
* Communicate directly with the processor providing Cockpit Data Processing and Communication | * Communicate directly with the processor providing Cockpit Data Processing and Communication | ||
* Controllers are usually dedicated to one specific type of hardware | * Controllers are usually dedicated to one specific type of hardware | ||
| Controllers provide a means to off-load needed work from the cockpit system. There are several reasons to use a controller and there may be several of them. | |||
Controllers can be implemented as a separate hardware layer, or can be software running on the same hardware as the cockpit system. | |||
Reasons: | |||
* Reduces complexity of the Cockpit System | |||
* Not enough I/O pins | |||
* Not enough time for the System to do all the work needed | |||
<br> | |||
A cockpit may contain several controllers. | |||
|- | |- | ||
| Hardware Driver Circuits || | | Hardware Driver Circuits || Specialized chips or circuits for one specific type of hardware<br> | ||
* Analog to Digital Converters (ADC) | * Analog to Digital Converters (ADC) | ||
* Digital to Analog Converters (DAC) | * Digital to Analog Converters (DAC) | ||
| Line 33: | Line 45: | ||
* H Bridge Circuits | * H Bridge Circuits | ||
* Amplifiers | * Amplifiers | ||
| Hardware driver circuits provide specialized interfaces between controllers and physical hardware components. | |||
In some cases the interface is integrated with the hardware the controller is running on. | |||
|- | |- | ||
| Low Level Hardware || Switches, Displays, Rheostats, Encoders, Meters, Dials<br/><br/> | | Low Level Hardware || Switches, Displays, Rheostats, Encoders, Meters, Dials<br/><br/> | ||
| Line 52: | Line 66: | ||
Controllers can communicate with Low Level Driver Circuits or directly with the low level hardware. | Controllers can communicate with Low Level Driver Circuits or directly with the low level hardware. | ||
==== Raspberry Pi - Arduino Communication ==== | |||
https://oscarliang.com/raspberry-pi-arduino-connected-i2c/ <br/> | |||
https://oscarliang.com/connect-raspberry-pi-and-arduino-usb-cable/<br/> | |||
https://oscarliang.com/raspberry-pi-and-arduino-connected-serial-gpio/<br/> | |||
https://oscarliang.com/arduino-timer-and-interrupt-tutorial/<br/> | |||
<br/> | |||
==== Low Level Driver Circuits ==== | ==== Low Level Driver Circuits ==== | ||
===== Arduino, PIC or STM ===== | ===== Arduino, PIC or STM ===== | ||