Changes

Jump to navigation Jump to search
no edit summary
Line 1: Line 1:  +
{{HONEY-sidebar
 +
| header = Viper
 +
| img link = File:Viper.jpg
 +
| designer = Kirill Safin
 +
| techline = Balloons Breakouts
 +
| version = Generation I
 +
| name = Viper
 +
}}
 +
 
'''Viper''' is the first generation HONEY Breakout Board. Viper breaks out most of the important signal and power lines from the HONEY stack Data Bus & Power Bus, as well as the CAN Bus, to enable connecting to the HONEY flight stack remotely, over cable.
 
'''Viper''' is the first generation HONEY Breakout Board. Viper breaks out most of the important signal and power lines from the HONEY stack Data Bus & Power Bus, as well as the CAN Bus, to enable connecting to the HONEY flight stack remotely, over cable.
 +
 +
As of August 10th, 2017, all HONEY flight stacks require Viper as the bottom-most (stack-terminating) board. This makes Viper a FCC (Flight Critical Component). This is both for physical and electrical reasons -- Viper is the only board with a non-stackthrough data bus, making it the choice for the bottom-most board. This was previously the BMS, due to the need for enough space for the battery pack -- however, the maximum spacing between flight stack boards has since increased to 20mm, allowing the BMS to be on the stack interior, and necessitating an alternate stack-terminating board -- Viper was chosen. Necessarily having Viper in a Flight Stack also guarantees any stack can be debugged using the master breakout, or expanded using payload breakouts.
    
This enables two important capabilities, such as:
 
This enables two important capabilities, such as:
Line 18: Line 29:  
There is no need for more than two payload breakouts, with the expectation that all boards that receive the payload breakout also have a secondary connector to allow for continued daisy chaining. This is the case, for example, on ProtoBee.
 
There is no need for more than two payload breakouts, with the expectation that all boards that receive the payload breakout also have a secondary connector to allow for continued daisy chaining. This is the case, for example, on ProtoBee.
   −
The particular payload breakout itself is a 1.27mm pitch 2x25 pin keyed, shrouded connector. This decision was made to make the breakout as small as possible, and keep the cabling thin. The exact connector, and associated cabling, are:
+
Details of the Venom Breakout can be found on the [[Venom_Breakout | Venom Breakout]] page.
   −
Connector: Samtec SHF-125-01-L-D-RA
+
[[File: Viper2.png | right| thumb | <center> Viper Routing </center>]]
Cabling: Samtec FFSD-25-D-XX.XX-01-N
     −
In the above, XX.XX denotes the length -- which can be custom as desired, in inches (2 inch minimum).
+
=== Master Breakout ===
 +
In addition to the Venom Breakout, Viper also includes a larger, 56-pin 2.54mm (standard) pitch connector known as the Master Breakout -- or, more formally, the '''Fang Breakout'''.
   −
The specific pin out for ''Venom Breakout'' is the following, with the first row as the top, second row as the bottom, left to right as seen looking into the receptacle from the board-edge.
+
The ''Fang Breakout'' breaks out the remainder of what the Viper Breakout was unable to breakout, or what was deemed inessential for a payload to have access to. This includes the secondary CAN Bus and some additional avionics GPIO pins.
   −
{| class="wikitable"
+
[[Category:HONEY]]
|-
  −
|5V
  −
|3.3V BUS
  −
|VBATT (4.2V)
  −
|12V
  −
|1.8V
  −
|SDA
  −
|SCL
  −
|MOSI
  −
|MISO
  −
|SCLK
  −
|VA_PWM
  −
|CHIRP
  −
|R_MCU
  −
|R_ALL
  −
|S_READY
  −
|LOW_PWR
  −
|FMODE
  −
|SYS_F3
  −
|SYS_F4
  −
|SYS_F5
  −
|SYS_F6
  −
|(+5 S)
  −
|(-5 S)
  −
|CAN_SPD
  −
|GND
  −
|-
  −
|5V
  −
|3.3V BUS
  −
|VBATT (4.2V)
  −
|12V
  −
|VADJ OUT
  −
|TX4
  −
|RX4
  −
|TX6
  −
|RX6
  −
|DAC0
  −
|DAC1
  −
|AV29
  −
|AV42
  −
|AV17
  −
|AV16
  −
|AV35
  −
|AV36
  −
|AV37
  −
|AV38
  −
|CAN1_H
  −
|CAN1_L
  −
|(+12 S)
  −
|(-12 S)
  −
|3.3V CAN
  −
|GND
  −
|}
 

Navigation menu