Howto:Build your own Panel or Cockpit - Prototyping: Difference between revisions

Jump to navigation Jump to search
mNo edit summary
Line 98: Line 98:


== Flightgear Properties and Hardware Interfaces ==
== Flightgear Properties and Hardware Interfaces ==
* Mapping of Flightgear properties to hardware interfaces and one or more addresses on those interfaces
* Mapping of each Flightgear property to a hardware interface and one or more addresses on the interface and to a routine to translate and move data between them.
* Pi to Flightgear requires Property Path, Name and Value.  Protocol is documented on Flightgear Wiki.
* Pi to Max7221 is defined by the chip
* Pi to Port Expander is defined by the chip and a driver on the Pi to use the port expander instead of a gpio pin
* Pi to AtMega and Atmega to Pi requires an id for the AtMega interface port associated with the property and the value.
* To save time on the SPI or I2c intefaces, a table will be loaded down from the Pi to the ATMega at startup.  On the AtMega, it will contain the AtMega Interface Port Id, identify the port's handler routine and the hardware addressing data for the port. On the Pi, it will contain the AtMega Interface Port Id, the path and name of the Flightgear property and the id of the Pi Routine responsible for translating between the Property Value and the AtMega Hardware Value.
 
== Switches ==
== Switches ==
* Map anything that behaves like a switch as a switch  
* Map anything that behaves like a switch as a switch  
982

edits

Navigation menu