982
edits
mNo edit summary |
|||
| Line 106: | Line 106: | ||
* Pi to AtMega and Atmega to Pi requires an id for the AtMega interface port associated with the property and the value. | * 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. | * 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. | ||
for details see: [[Howto:Build your own Panel or Cockpit - Software]] | |||
== Switches == | == Switches == | ||
edits