700
edits
Changes
Jump to navigation
Jump to search
Line 1:
Line 1: − + + + + + + + + + + Line 183:
Line 192: − + + + + + + + + + + + Line 267:
Line 286: − + Line 317:
Line 336: − + − + − + − + − + − + Line 453:
Line 472: + +
→Data Bus
{{HONEY-sidebar}}
{{HONEY-sidebar
| header = HONEY Architecture
| img link = File:HONEY2.jpg
| designer = Kirill Safin
| techline = Balloons Core Architecture
| version = Generation II
| name = HONEY
| acronym = Hardware Optimized Nested Electronics sYstem
}}
'''HONEY (Hardware Optimized Nested Electronics sYstem)''' is the second generation Core Flight Architecture, designed by HABEES. The HONEY architecture makes significant changes and improvements on the Generation I Architecture, including changes in physical dimensioning, stacking connectors, common power and data buses, and more.
'''HONEY (Hardware Optimized Nested Electronics sYstem)''' is the second generation Core Flight Architecture, designed by HABEES. The HONEY architecture makes significant changes and improvements on the Generation I Architecture, including changes in physical dimensioning, stacking connectors, common power and data buses, and more.
|NO
|NO
|-
|-
|29-36, 38-41
|29-36, 38-40
|IO/1 - IO/13
|IO/1 - IO/13
|These are GPIO pins directly connected to the Core Avionics. These can be used to transfer a digital signal to the avionics, have the avionics sample an analog signal, or have the avionics PWM a signal, depending on the specific GPIO pin used. If this functionality is desired, one should reference the Core Avionics schematic to determine the pin capabilities of each of the GPIO's. These can be used both as inputs (to the Core Avionics) or outputs (from the Core Avionics). On the schematic symbol for the HABEES stackup, these are referred to as "AV____" where ____ is the corresponding pin on the Main Avionics MCU (a teensy 3.6). Reference the ____ pin on the 3.6 schematic to determine its functionality.
|These are GPIO pins directly connected to the Core Avionics. These can be used to transfer a digital signal to the avionics, have the avionics sample an analog signal, or have the avionics PWM a signal, depending on the specific GPIO pin used. If this functionality is desired, one should reference the Core Avionics schematic to determine the pin capabilities of each of the GPIO's. These can be used both as inputs (to the Core Avionics) or outputs (from the Core Avionics). On the schematic symbol for the HABEES stackup, these are referred to as "AV____" where ____ is the corresponding pin on the Main Avionics MCU (a teensy 3.6). Reference the ____ pin on the 3.6 schematic to determine its functionality.
|NO
|-
|41
|BLUEJ_PRESENT
|This pin is pulled high by the BlueJay RockBlock breakout board -- to signal to the main avionics that it is in use, as opposed to the on-board 9603 modem.
|NO
|-
|81-86
|RB Breakout
|These pins are connected to the avionics RockBlock signal lines -- including TX, RX, SLP, NETAV, ENABLE, and RING INDICATOR. They are meant to allow the avionics to use an external RockBlock breakout board instead of its on-board 9603 modem, or, in the future, to allow the RockBlock to be broken out from the avionics if desired. They should not be touched by anything except the avionics. In this breakout, TX connects to an MCU TX, and RX connects to an MCU RX (as opposed to the standard swapped interface).
|NO
|NO
|-
|-
|IO/12
|IO/12
|-
|-
|IO/13
|BLUEJ_PRESENT
|RESERVED
|RESERVED
|RESERVED
|RESERVED
|RESERVED
|RESERVED
|-
|-
|RESERVED
|RB_TX -->
|RESERVED
|RB_RX <--
|RESERVED
|RB_NETAV
|RESERVED
|RB_SLP
|-
|-
|RESERVED
|RB_RI
|RESERVED
|RB_EN
|RESERVED
|RESERVED
|RESERVED
|RESERVED
#Make sure +3.3_CAN is used only to power the transceiver, and nothing else.
#Make sure +3.3_CAN is used only to power the transceiver, and nothing else.
#Make sure CAN_SPD is hard-wired to the transceiver speed pin.
#Make sure CAN_SPD is hard-wired to the transceiver speed pin.
[[Category: High Altitude Balloons]][[Category: HABEES]][[Category: HONEY]]