vault backup: 2025-02-03 07:04:13

OneNote/OSD/CarrierBoard/CAD - Software.md

@@ -1,3 +0,0 @@
-KiCad - Open Source
-
-What could be used to simulate a circuit?

OneNote/OSD/CarrierBoard/Design Rules Overview.md

@@ -1,42 +0,0 @@
-## MIPI design Rules
-
-Goal: 100 Ohm Impedance
-
-  
-
-Track width:
-
-Track spacing:
-
-  
-
-Via hole:
-
-Via size:
-
-Via spacing:
-
-  
-  
-
-## USB micro design Rules
-
-Goal: 90 Ohm differential Impedance and 90 ohm differential via impedance
-
-  
-
-Track width: 0.2032 mm
-
-Track spacing: 0.127mm
-
-Gives 89,886 Ohm
-
-  
-
-Via hole: 0.2
-
-Via size: 0,75
-
-Via spacing: 0,85
-
-Gives 89,834 Ohm

OneNote/OSD/CarrierBoard/Design Rules.md

@@ -1,13 +0,0 @@
-## Controlled Impedance
-
-[http://design.iconnect007.com/index.php/article/62513/what-is-trace-impedance-and-why-do-we-care/62516/](http://design.iconnect007.com/index.php/article/62513/what-is-trace-impedance-and-why-do-we-care/62516/)
-
-  
-
-## Dont forget at end:
-
-- Double check impedance control
-    
-    - includes vias and removing of stubs (backdrilling of vias)
-- No traces at board edge
-- Many stitching vias everywhere

OneNote/OSD/CarrierBoard/Ethernet research.md

@@ -1,42 +0,0 @@
-Question stack exchange EE
-
-  
-
-Hello
-
-  
-
-My goal is to set up a high-speed network link between two identical processors (Qualcomm SOMs) that will be present on the same PCB. Since I have severe restrictions on weight I cannot use the standard ethernet way with an RJ45 and a cable to set this up. The two possible interfaces on the processors for the network link are PCIe 3.0 or a USB 3.1 GEN2 interface.
-
-  
-
-My current idea is to use an ethernet bridge IC like the [LAN7430 from microchip][1] at the PCIe-port on both processors and add a single ethernet transformer (e.g. [H5084NL from pulse electronics][2]) in between. This would set up an ethernet link 1000BASE-T between the two processors. According to [this][3] and [this question][4] the magnetics are recommended to provide a stable connection. They also mention the problem with connections that are shorter than 1m, which I don't know yet how to solve.
-
-  
-
-Is this the best solution for this problem? Since I do not have access to a MAC-port I cannot implement the direct MAC to MAC connection as proposed by [user dim in this question][4].
-
-  
-
-With this solution, using the PCIe port, I could achieve 1Gbit/s with the 1000BASE-T Ethernet. According to the USB specifications, the USB 3.1 GEN2 interface is capable of achieving up to 10 Gbit/s, which would be preferable for my application.
-
-  
-
-Is it possible to implement a reliable USB network without cable
-
-  
-  
-  
-
-[1]: [https://www.microchip.com/wwwproducts/en/LAN7430](https://www.microchip.com/wwwproducts/en/LAN7430)
-
-[2]: [https://productfinder.pulseeng.com/product/H5084NL](https://productfinder.pulseeng.com/product/H5084NL)
-
-[3]: [https://electronics.stackexchange.com/q/90330/255394](https://electronics.stackexchange.com/q/90330/255394)
-
-[4]: [https://electronics.stackexchange.com/q/378310/255394](https://electronics.stackexchange.com/q/378310/255394)
-
-  
-  
-
-[https://www.one-tab.com/page/pPYRBiErRWahS_zJR4kc7g](https://www.one-tab.com/page/pPYRBiErRWahS_zJR4kc7g)

OneNote/OSD/CarrierBoard/Learning from DJI Mavic Air.md

@@ -1 +0,0 @@
-[https://medium.com/amazing-hardware/mavic-air-2-dji-uav-disassembly-analysis-38783979b95a](https://medium.com/amazing-hardware/mavic-air-2-dji-uav-disassembly-analysis-38783979b95a)

OneNote/OSD/CarrierBoard/Lessons V0.1.2.md

@@ -1,34 +0,0 @@
-Implement in next version:
-
-- [ ] Shunt resistor to measure current draw of coral or of the whole board.
-
-- [ ] Use the same gpiopin for fancontrol as the dev-board
-
-- [ ] Better label output pins.
-
-- [ ] Make connectors asymetrical for good connections.
-
-- [ ] All pins that eventually are needed should be exposed somehow (testpoint or connector)
-
-- [ ] Add LED's to GPIO pins to know their state
-
-- [ ] Add switches or jumpers to power only certain parts of the board
-
-- [ ] Connect Enable pins of Ic's to pin headers or gpios of the processor. In case it is needed it can be used. E.g power supply of SARA chip
-
-- [ ] Add via or tp for everything you eventually want to measure.
-
-- [ ] Place testpoint on vcc on last cap before entering ic.
-
-- [ ] Add gpio level shifter
-
-- [ ] Swap rx tx sara
-
-- [ ] If v0.2 is still mainly for debugging: add buttons for reset and pwr pins: as in [this open source project](https://cdn.sparkfun.com/assets/a/c/b/1/0/lte_cat_m1_shield_sara-r4_schematic.pdf)
-
-  
-
-- Implement HDMI in first version to be able to debug: Is it even booting up?
-- Make pin connectors for all essential pins: Boot pins, boot configure pins, reset pins, etc: Like this you have the possibility to measure the signal and overwrite it if necessary.
-- First version should just be the coral connectors + power and all necessary things to boot. All other accessories
-- Ask google before starting development what is the absolute minimum bare bones for a working base-board.

OneNote/OSD/CarrierBoard/Overview.md

@@ -1,5 +0,0 @@
-Submodules
-
-- Power Distribution Board
-- Flight Controller
-- Coral SoM Footprint

OneNote/OSD/CarrierBoard/TODO.md

@@ -1,19 +0,0 @@
-## Camera Interface
-
-- [ ] Check camera connectors once we decided on cameras. Do those mipi cameras have a reset or pwdn? update them...
-
-- [ ] Check I2C connection: --> what is it needed for?
-
-## General
-
-- [ ] Add Testpoints (TP) as in the dev-board to test circuits with multimeter/oscilloscope
-
-Do we need isolators to break ground loops?
-
-[https://www.ti.com/product/ISO7762](https://www.ti.com/product/ISO7762)
-
-  
-
-See:
-
-[https://docs.odriverobotics.com/ground-loops.html](https://docs.odriverobotics.com/ground-loops.html)

OneNote/OSD/CarrierBoard/ToDo Carrier RB5.md

@@ -1,27 +0,0 @@
-# OneSec Monocopter 1
-
-- [ ] Fast working implementation of GNSS
-
-- [ ] Worldwide LTE-Chip (Quectel)
-
-- [ ] Power Distribution
-
-OneSec Monocopter 2
-
-- [ ] Night Vision Cameras & IR-Flashlights
-
-- [ ] Solar panels from [Flisom](https://www.flisom.com/wp-content/uploads/2017/08/Datasheet_ultra-light-CIGS-eFilm-solar-cell-material.pdf)
-
-- [ ] Better Motors (custom carbonfiber)
-
-- [ ] Snapdragon 888 or later generation
-
-- [ ] Regenerative breaking
-
-- [ ] Aerodynamic improvements
-
-- [ ] Graphene Batteries (removes necessity for battery swap)
-
-- [ ] Better propeller blades
-
-- [ ] High precision GNSS + Antenna

OneNote/OSD/CarrierBoard/Todos for V0.2.md

@@ -1,83 +0,0 @@
-**GENERAL TODOS**
-
-  
-
-- [ ] Proper Power connector to connect with PDB
-
-- [ ] Our own gps module
-
-- [ ] Working heat-sink solution: --> place corals further apart from each other.
-
-- [ ] Make the board smaller! --> Weight saving, less expensive
-
-- [ ] Use both sides for components.
-
-- [ ] Put more LED's:
-
-- [ ] Make more pinouts if V0.2 is still a debug board.
-
-**Ideas:**
-
-Do we want to integrate more sensors onto the board? Temperature, pressure, gyro? #question
-
-How do we measure the position of the flaps/payload bay? #question
-
-Do we need more storage? Implement flash storage or sd-card? #question
-
-Buy sara board from [sparkfun](https://www.sparkfun.com/products/14997)?
-
-**To Decide before start:**
-
-- [ ] USB-C yes or no?
-
-- [ ] MIPI yes or no?
-
-- [x] Open drain pins: use own transistor or device tree approach? --> Open drain also for PWR_ON
-
-- [ ] DEBUG board: yes or no?
-
-- [ ] Stress test antenna sara.
-
-**Precise TODO's:**
-
-- [ ] Remap SARA Rx/Tx
-
-- [ ] Decide scope of board: still debugging?
-
-- [ ] Rewire orange coral status led: with datasheet decide current limiting resistor to have full power at steady on. --> allows to regulate dimness with pwm.
-
-- [ ] Use large size resistor for important settings: e.g. voltage regulators
-
-- [ ] Make single pin of gnd to attach oscilloscope crocodile clamp
-
-- [ ] Find Power connector to connect to PDB.
-
-- [ ] Remove 0-Ohm resistors where they are not needed anymore, but provide testpoints!
-
-- [ ] Don't use Testpoints: Use holes like jtag: you can later on add pins if needed.
-
-- [ ] Add LED to id-pin of cc-control of usb-c (it is a open drain pin) --> when pulled to gnd it should activate a transistor that connects the led to gnd.
-
-- [ ] Gpio link to do hard reset between corals.
-
-- [ ] Flight controller connectors:
-
-- [ ] 2x UART
-
-- [ ] 2x GND Power
-
-- [ ] 2x 5V Power
-
-- [ ] ?x GNSS connection
-
-- [ ] ?x GND between lines for shielding
-
-- [ ] General Connectors
-
-- [ ] 1x GND, 5V for RC (asym-conn)
-
-- [ ] 2x GND, 5V for fans (asym-conn)
-
-- [ ] 5x GND, 5V DNP conn for eventualities
-
-- [ ] same with 3.3v and 1.8V