Stanford SSI Wiki

Changes

Gen 2 Architecture (view source)

Revision as of 22:41, 31 August 2017

2,327 bytes added ,  22:41, 31 August 2017
→‎Data Bus
Line 1: Line 1: −
{{tech-sidebar
+
{{HONEY-sidebar
−
| header = HONEY
+
| header = HONEY Architecture
−
| img link = File:HONEy.jpg
+
| img link = File:HONEY2.jpg
 
| designer = Kirill Safin
 
| designer = Kirill Safin
 
| techline = Balloons Core Architecture
 
| techline = Balloons Core Architecture
 
| version = Generation II
 
| version = Generation II
 
| name = HONEY
 
| name = HONEY
−
| missions = SSI-52 onward
+
| 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.  
    
The HONEY specification is outlined below in exhaustive detail, and the bottom of the page lists implementations required by any board utilizing the HONEY architecture.
 
The HONEY specification is outlined below in exhaustive detail, and the bottom of the page lists implementations required by any board utilizing the HONEY architecture.
Line 23: Line 23:  
The dimensions of a HONEY-compliant board are exactly 10x10 cm. Boards are 0.062" in thickness (this is important for the physical fastening of the flight stack to the payload container, which is sensitive to the thicknesses of boards in the flight stack. Boards also have four through-holes at each corner, designated for standoffs. The holes are designed for M3 standoffs, which are indented 250 mil from both edges of the respective corner. The board also necessarily consists of a PC/104+ connector for the flight stack data bus, a 10-pin (5x2) connector for the flight stack power bus, a 6-pin (3x2) connector for the flight stack CAN bus, and an 8 pin (4x2) connector (NON stack through) for holding jumpers for implementing CAN terminating impedances. These connectors are not physically located on the board in a whole-number fashion, but must be implemented with exact precision to allow for proper stack-through ability. The PC/104+ connector also comes with a paired shroud that clips onto the board via four through-holes, which, while not strictly required for operation, is highly encouraged and is part of the stack-up Altium part. Boards are expected to not exceed their boundaries by more than 0.25". The flight stack has 0.5" of space around it, between its outer dimensions and the walls of the payload container.
 
The dimensions of a HONEY-compliant board are exactly 10x10 cm. Boards are 0.062" in thickness (this is important for the physical fastening of the flight stack to the payload container, which is sensitive to the thicknesses of boards in the flight stack. Boards also have four through-holes at each corner, designated for standoffs. The holes are designed for M3 standoffs, which are indented 250 mil from both edges of the respective corner. The board also necessarily consists of a PC/104+ connector for the flight stack data bus, a 10-pin (5x2) connector for the flight stack power bus, a 6-pin (3x2) connector for the flight stack CAN bus, and an 8 pin (4x2) connector (NON stack through) for holding jumpers for implementing CAN terminating impedances. These connectors are not physically located on the board in a whole-number fashion, but must be implemented with exact precision to allow for proper stack-through ability. The PC/104+ connector also comes with a paired shroud that clips onto the board via four through-holes, which, while not strictly required for operation, is highly encouraged and is part of the stack-up Altium part. Boards are expected to not exceed their boundaries by more than 0.25". The flight stack has 0.5" of space around it, between its outer dimensions and the walls of the payload container.
   −
The connectors and hardware used in each case are:
+
The connectors and hardware used in each case can be found on the [[HONEY_Standardized_Connectors|HONEY Standardized Connectors Page]]
 
* Data Bus: Harwin M22-6003005
 
* Data Bus: Harwin M22-6003005
 
* Data Bus Shroud: Harwin M22-6043098
 
* Data Bus Shroud: Harwin M22-6043098
Line 192: Line 192:  
|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).
+
|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
 
|NO
 
|-
 
|-
−
|37, 42-111, 113-120
+
|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
 +
|-
 +
|105-108
 +
|12V
 +
|These pins, although on the databus, provide 12V power for 12V applications -- when used, all four nets should be connected together and used in parallel.
 +
|NO
 +
|-
 +
|113/114
 +
|(+5V and -5V) (SIG)
 +
|These pins are meant to be used for signal applications requiring a dual polarity +5V to -5V rail-to-rail supply. They only put out 15 mA, and should not be used for any power applications whatsoever.
 +
|NO
 +
|-
 +
|115/114
 +
|(+12V and -12V) (SIG)
 +
|These pins are meant to be used for signal applications requiring a dual polarity +12V to -12V rail-to-rail supply. They only put out 15 mA, and should not be used for any power applications whatsoever.
 +
|NO
 +
|-
 +
|37, 42-111, 117-120
 
|NC
 
|NC
 
|Reserved -- these can be used for any purpose at the time being, as long as it is agreed in advance.
 
|Reserved -- these can be used for any purpose at the time being, as long as it is agreed in advance.
Line 261: Line 286:  
|IO/12
 
|IO/12
 
|-
 
|-
−
|IO/13
+
|BLUEJ_PRESENT
 
|RESERVED
 
|RESERVED
 
|RESERVED
 
|RESERVED
Line 311: Line 336:  
|RESERVED
 
|RESERVED
 
|-
 
|-
−
|RESERVED
+
|RB_TX -->
−
|RESERVED
+
|RB_RX <--
−
|RESERVED
+
|RB_NETAV
−
|RESERVED
+
|RB_SLP
 
|-
 
|-
−
|RESERVED
+
|RB_RI
−
|RESERVED
+
|RB_EN
 
|RESERVED
 
|RESERVED
 
|RESERVED
 
|RESERVED
Line 341: Line 366:  
|RESERVED
 
|RESERVED
 
|-
 
|-
−
|RESERVED
+
|12V
−
|RESERVED
+
|12V
−
|RESERVED
+
|12V
−
|RESERVED
+
|12V
 
|-
 
|-
 
|RESERVED
 
|RESERVED
Line 351: Line 376:  
|CAN_SPD
 
|CAN_SPD
 
|-
 
|-
−
|RESERVED
+
|Pos 5V (SIG)
−
|RESERVED
+
|Neg 5V (SIG)
−
|RESERVED
+
|Pos 12V (SIG)
−
|RESERVED
+
|Neg 12V (SIG)
 
|-
 
|-
 
|RESERVED
 
|RESERVED
Line 404: Line 429:  
|-
 
|-
 
|2_TERM_1
 
|2_TERM_1
−
|2_TERM_21
+
|2_TERM_2
 
|-
 
|-
 
|NC
 
|NC
Line 412: Line 437:  
|NC
 
|NC
 
|}
 
|}
 +
 +
 +
[[File:allcan.JPG | right| thumb | <center> CAN, showing terminating impedance implemented </center>]]
 +
 +
 +
== Software Specification ==
 +
HONEY implements a flight stack-wide software suite called '''STINGR (Stack Transmission & Inter-Nodal Gesture Repository''', which provides a variety of function calls, interrupt handlers, and error-handling for communication within the stack, primarily utilizing the CAN Bus.
 +
 +
The full STINGR specification can be found on the [[Gen 1 Software|STINGR]] page.
    
== Implementation ==
 
== Implementation ==
Line 438: Line 472:  
#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]]
Retrieved from "https://ssi-wiki.stanford.edu/Special:MobileDiff/2466...2961"