vault backup: 2025-02-03 07:04:13
This commit is contained in:
Binary file not shown.
BIN
OneNote/OSD/Admin and General/.syncthing.TODO.md.tmp
Normal file
BIN
OneNote/OSD/Admin and General/.syncthing.TODO.md.tmp
Normal file
Binary file not shown.
BIN
OneNote/OSD/Admin and General/.syncthing.Todo 1.md.tmp
Normal file
BIN
OneNote/OSD/Admin and General/.syncthing.Todo 1.md.tmp
Normal file
Binary file not shown.
BIN
OneNote/OSD/Admin and General/.syncthing.Tools.md.tmp
Normal file
BIN
OneNote/OSD/Admin and General/.syncthing.Tools.md.tmp
Normal file
Binary file not shown.
@@ -1,5 +0,0 @@
|
||||
Articles
|
||||
|
||||
- [ ] How to 3D-Print with checklist.
|
||||
|
||||
- [ ] How to work with slack, confluence and gdrive
|
||||
@@ -1,65 +0,0 @@
|
||||
# Allgemeine Situation
|
||||
|
||||
Ich möchte ein paar Gedanken bezüglich OneSecondDelivery mit dir teilen und habe alles niedergeschrieben.
|
||||
|
||||
|
||||
|
||||
Nachdem ihr entschieden habt alles nach Zürich zu verschieben hattest du mich gefragt, ob ich noch länger bei OSD dabei bleiben möchte. Ich habe dir zugesagt, wobei ich darauf vermerkt habe, dass ich mich dazumal nicht wohl gefühlt habe, da ich auseinander gerissen war zwischen Lausanne, Zürich und Luzern. Ich bin dann noch länger in Lausanne geblieben um die wichtige Deadline zu erreichen, welche aber bis heute nicht erreicht wurde. Wir haben abgemacht, dass ich mich melde wie es geht in Zürich. Jetzt nach 2 Monaten muss ich sagen das es sich nicht verbessert hat, eher verschlechtert. Ich finde es sehr schön hier in Zürich mehr mit Alena und Freunden zu machen, bin aber sehr unzufrieden mit der Arbeit und möchte das offen mit dir teilen, da mir die Kommunikation zwischen uns von Anfang an sehr viel Wert gewesen ist.
|
||||
|
||||
|
||||
|
||||
Durch Selbstreflektion merke ich, dass ich mich überhaupt nicht wohl fühle. Ich fühle mich komplett ausgelaugt - konstant. Meine Positivität ist zum grössten Teil auf der Strecke geblieben und es drückt auch im privaten Leben durch, was mich sehr stört. Am Ende fast jedes Tages denke ich das es kein guter war und nicht viel funktioniert hat wie hätte sollen. Jedes Mal wenn ich die Treppe runter gehe in Richtung "Büro" fühle ich eine Abneigung und möchte am liebsten nicht runter gehen. Das hat vor allem damit zu tun, dass ich den ganzen Tag alleine im Keller sitze und alleine an irgendwelchen Dingen herumtüftle. Es ist überhaupt kein Teamspirit vorhanden und ich habe keine Ahnung woran Inigo, Floris, oder Jerry arbeitet. Wir haben immer wieder gesagt, dass das besser wird, aber auch nach 16 Monaten ist es nicht wirklich besser. Ich bin mir bewusst, dass das zu einem blöden Zeitpunkt kommt, da sich vielleicht viele dieser Dinge ändern werden, sobald Investmentgelder organisiert sind. Aber wir sagen das schon seit Monaten und ich spüre nicht wirklichen Fortschritt. Bezüglich Team beschäftigen mich mehrere Punkte, zum Beispiel möchte ich mit anderen Leuten an einem Projekt arbeiten, um technisches Feedback zu bekommen und wichtige Punkte miteinander diskutieren zu können. Vor allem denke ich, dass wir "Experten" brauchen können, da das Development so viel schneller wäre und Leute wie Inigo und ich viel mehr und schneller lernen können was alle vorwärts bringt. Dann fände ich es wirklich wichtig auch zwischen den verschiedenen Themen Austausch zu haben mit einem wöchentlichen 10-Minuten Meeting oder so, wo alle mitmachen. Das hilft einerseits das Gesamtbild zu sehen und andererseits hilft es allen einen Schritt zurück zu gehen und sich selbst und seine Arbeit objektiver zu betrachten. Etwas anderes ist, dass ich bisher an vielen verschiedenen Dingen arbeiten musste, aber immer wieder etwas neues Priorität hatte, was dazu geführt hat, dass ich nichts wirklich abgeschlossen habe. Ich habe manchmal das gefühl für sehr vieles gleichzeitig verantwortlich zu sein, und nicht nur verantwortlich sondern auch derjenige der es ausführen muss.
|
||||
|
||||
|
||||
|
||||
Ich merke insgesamt, dass es mir nicht gut geht und sich die Situation eher verschlechtert als verbessert. Das beschäftigt mich ziemlich und ich glaube ich bin nicht bereit meine Gesundheit aufs Spiel zu setzen. Für mich gibt es verschiedene Anzeichen: es wirkt sich auf meine Motivation an der Arbeit wie auch im privaten Leben aus, ich bin durchgehend erschöpft und kann kaum aufs Wochenende warten, ich bin sehr oft schlecht gelaunt, was ich vorher nicht wirklich hatte (und das hast du ja sogar von dir aus bemerkt in Lausanne), manchmal kriege ich eine komplette Blockade beim Arbeiten und denke dass ich alles hinschmeissen sollte (was ich eigentlich nicht möchte).
|
||||
|
||||
|
||||
|
||||
Ich wollte dir vorschlagen, das zusammen zu erörtern und Lösungsansätze zu suchen. Ich bin davon überzeugt das vieles viel besser wird sobald wir alle in Zürich sind, fühle mich aber so als ob das schon seit langer Zeit herausgeschoben wird.
|
||||
|
||||
Key Points
|
||||
|
||||
- Leere versprechen
|
||||
- Bubble
|
||||
- Team
|
||||
- Ich lerne nichts mehr
|
||||
- Motivation
|
||||
- Wirkung auf privates leben
|
||||
- Signs of burnout
|
||||
|
||||
- 90% sind schlechte tage
|
||||
- Immer schlecht gelaunt
|
||||
- Konstant erschöpft
|
||||
- Ich habe keine freude mehr
|
||||
- Ich möchte niemandem mehr erzählen was ich mache bei OSD (erkläre immer alles in denselben alten sätzen)
|
||||
- Prokrastination
|
||||
- Vielleicht bin ich nicht der richtige für den job
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
**Positiv**
|
||||
|
||||
- Neuanfang in Zürich -> Mitgestaltung, Team, etc.
|
||||
|
||||
**Negativ**
|
||||
|
||||
- Nach 16 Monaten nicht so viel Start-up erfahrung
|
||||
- Ausgeleiert
|
||||
- Motivation viel kleiner geworden
|
||||
|
||||
**Kommunikation**
|
||||
|
||||
- Immer so schnell wie möglich
|
||||
- Keine Team meetings -> ich habe keine ahnung was di anderen machen.
|
||||
|
||||
Was mir sorgen macht
|
||||
|
||||
- Ich fühle mich trapped wegen aktien.
|
||||
- Möchte aber trotzdem entlöhnt werden für was ich geleistet habe
|
||||
@@ -1,67 +0,0 @@
|
||||
# Plan
|
||||
|
||||
1. Say i'm recording
|
||||
2. Ask to tell you what had already been discussed with dannick
|
||||
3. Talk about his experience:
|
||||
4. Explain high level electrical system
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
# Electrical System
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
- Show high level block diagram
|
||||
- Show what we have:
|
||||
|
||||
- Power Distribution Board
|
||||
- Carrierboard for google corals
|
||||
- Explain what we want:
|
||||
|
||||
- Carrierboard including the flight controller FMU v6
|
||||
- Power distribution board V2
|
||||
- Integration into drone
|
||||
- What problems are there:
|
||||
|
||||
- Electrical interference: GNSS high precision, LTE, RF frequencies, high current motors
|
||||
- Redundancy: custom ESC solution
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
# Prepare
|
||||
|
||||
- [ ] PDB and Carrierboard
|
||||
|
||||
- [ ] Show Pinout px4
|
||||
|
||||
|
||||
|
||||
# Questions
|
||||
|
||||
- [ ] What equipment do you need?
|
||||
|
||||
- [ ] What is your understanding of the different protocols?
|
||||
|
||||
- [ ] CAN?
|
||||
|
||||
- [ ] SPI, UART, I2C?
|
||||
|
||||
- [ ] What's the approach to redundancy?
|
||||
|
||||
- [ ] What is your experience with EMI?
|
||||
|
||||
- [ ] RF-Design?
|
||||
|
||||
- [ ] How have you worked in your other jobs?
|
||||
|
||||
Have you worked19.08.21 s?
|
||||
|
||||
EMI?
|
||||
|
||||
Have you worked with gps, lte, cameras
|
||||
@@ -1,63 +0,0 @@
|
||||
# Plan
|
||||
|
||||
1. Say i'm recording
|
||||
2. Ask to tell you what had already been discussed with dannick
|
||||
3. Talk about his experience:
|
||||
|
||||
1. 3Phase inverter --> tell me about it
|
||||
2. Have you designed pcbs before? What sort of PDB?
|
||||
3. What were typical courses which apply to this job?
|
||||
4. Explain high level electrical system
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
# Electrical System
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
- Show high level block diagram
|
||||
- Show what we have:
|
||||
|
||||
- Power Distribution Board
|
||||
- Carrierboard for google corals
|
||||
- Explain what we want:
|
||||
|
||||
- Carrierboard including the flight controller FMU v6
|
||||
- Power distribution board V2
|
||||
- Integration into drone
|
||||
- What problems are there:
|
||||
|
||||
- Electrical interference: GNSS high precision, LTE, RF frequencies, high current motors
|
||||
- Redundancy: custom ESC solution
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
# Prepare
|
||||
|
||||
- [ ] PDB and Carrierboard
|
||||
|
||||
- [ ] Show Pinout px4
|
||||
|
||||
|
||||
|
||||
# Questions
|
||||
|
||||
- [ ] What equipment do you need?
|
||||
|
||||
- [ ] What is your understanding of the different protocols?
|
||||
|
||||
- [ ] CAN?
|
||||
|
||||
- [ ] SPI, UART, I2C?
|
||||
|
||||
- [ ] What's the approach to redundancy?
|
||||
|
||||
- [ ] What is your experience with EMI?
|
||||
|
||||
- [ ] RF-Design?
|
||||
@@ -1,5 +0,0 @@
|
||||
# Open Expenses
|
||||
|
||||
- [ ] Rent July (850.-)
|
||||
|
||||
- [x] Sbb billete woche in lausanne?
|
||||
@@ -1,122 +0,0 @@
|
||||
# Hardware
|
||||
|
||||
|
||||
|
||||
- [ ] Make the prototype hover
|
||||
|
||||
- [x] Build Mock-up body to not destroy it while testing
|
||||
|
||||
- [x] Servo calibration
|
||||
|
||||
- [ ] Test without propellers
|
||||
|
||||
- [ ] Add propellers
|
||||
|
||||
- [ ] Control system check by flying while holding
|
||||
|
||||
- [ ] Look at logs, do they contain all variables that should be monitored?
|
||||
|
||||
- [ ] Do we need to customize the log?
|
||||
|
||||
- [ ] Does the control system input look healthy?
|
||||
|
||||
|
||||
|
||||
|
||||
- [ ] Make redundant esc's
|
||||
|
||||
- [ ] Proof of work:
|
||||
|
||||
- [ ] Using 2 vescs and a custom application show that 2 vescs can control a single motor
|
||||
|
||||
- [ ] Where does the error signal come from? How can we generate it / monitor the health of the esc?
|
||||
|
||||
|
||||
|
||||
|
||||
- [ ] Version 2 of PDB
|
||||
|
||||
- [ ] Make 5V rail and 7.4V rail redundant!
|
||||
|
||||
- [ ] Formfactor & Weight!
|
||||
|
||||
|
||||
|
||||
- [ ] Carrierboard No. 2
|
||||
|
||||
- [ ] Coral vs Qualcomm --> See performance etc. with Iñigo
|
||||
|
||||
- [ ] If Coral
|
||||
|
||||
- [ ] Decide on cameras and make custom connector
|
||||
|
||||
|
||||
|
||||
|
||||
- [ ] Sensors & Actuation
|
||||
|
||||
- [ ] GPS: Decide which GPS modules & antennas
|
||||
|
||||
- [ ] --> test performance between ZED & NEO (with and without correction services)
|
||||
|
||||
- [ ] Test antenna performance
|
||||
|
||||
- [ ] IoT: Is SARA chip enough? --> make or use API to integrate SARA into our ROS system.
|
||||
|
||||
- [ ] Define purpose precisely of SARA Chip. What needs to be communicated? What packages exchanged?
|
||||
|
||||
- [ ] Airspeed sensor
|
||||
|
||||
- [ ] Test windspeed sensor when it arrives
|
||||
|
||||
- [ ] How important is it? Do we manage without?
|
||||
|
||||
- [ ] Research Stall and stall detection (can It be detected without windspeed sensor?)
|
||||
|
||||
- [ ] What is the lifetime of the servos? Can we find better servos?
|
||||
|
||||
- [ ] What servos does nasa use on their Ingenuity copter? --> Maxon
|
||||
|
||||
- [ ] Send email to maxon
|
||||
|
||||
- [ ] Are there servos that run on 6s? --> would greatly simplify pdb.
|
||||
|
||||
# Software
|
||||
|
||||
- [ ] Sensors & Actuation
|
||||
|
||||
- [ ] Attach GPS Module to PX4
|
||||
|
||||
- [ ] Does it work?
|
||||
|
||||
- [ ] How do we need to tweak it?
|
||||
|
||||
|
||||
|
||||
- [ ] Communication High level
|
||||
|
||||
- [ ] What packages are being sent between corals and px4?
|
||||
|
||||
- [ ] What data needs to be shared? (make a list! GPS, etc.)
|
||||
|
||||
- [ ] Redundancy
|
||||
|
||||
- [ ] How do we run 2 px4s in parallel?
|
||||
|
||||
- [ ] Make high-level node graph of our architecture
|
||||
|
||||
- [ ] What nodes work fine, what nodes need to be implemented?
|
||||
|
||||
- [ ] Make requirements list of PX4 part. Is it suited as it is or does it need to be modified?
|
||||
|
||||
- [ ] Low-level Communication
|
||||
|
||||
- [ ] UAVCAN vs other protocols
|
||||
|
||||
- [ ] Qualcomm vs Coral. 
|
||||
|
||||
# Modelling & Control System
|
||||
|
||||
- [ ] Make the prototype hover like a heli
|
||||
|
||||
- [ ] Model the drone with matlab and come up with strategy for control system
|
||||
@@ -1,43 +0,0 @@
|
||||
- [ ] Oscilloscope
|
||||
|
||||
- [ ] PDB
|
||||
|
||||
- [ ] Multimeter
|
||||
|
||||
- [ ] Jumper cables
|
||||
|
||||
- [ ] Breadboard
|
||||
|
||||
- [ ] Resistors
|
||||
|
||||
- [ ] Pot
|
||||
|
||||
- [ ] VESCS
|
||||
|
||||
- [ ] Usb-cables
|
||||
|
||||
- [ ] Swd Programmer
|
||||
|
||||
- [ ] Powersupply
|
||||
|
||||
- [ ] Arduino uno & every
|
||||
|
||||
|
||||
|
||||
Honey
|
||||
|
||||
|
||||
|
||||
Steckleiste
|
||||
|
||||
|
||||
|
||||
- [ ] Computer
|
||||
|
||||
- [ ] Screen
|
||||
|
||||
- [ ] Keyboard
|
||||
|
||||
- [ ] Mouse
|
||||
|
||||
- [ ] Thumbdrive
|
||||
@@ -1,61 +0,0 @@
|
||||
# Short Term
|
||||
|
||||
- [ ] Record new data with same script
|
||||
|
||||
- [ ] 0 period at start and end
|
||||
|
||||
- [ ] Include 0-10% mod in steps of 1%
|
||||
|
||||
- [ ] Record mechanical symmetry experiment
|
||||
|
||||
- [ ] Roll-pitch circle at constant modulation and constant throttle.
|
||||
|
||||
- [ ] Thrust drop experiment
|
||||
|
||||
- [ ] Is there a thrust drop when modulating
|
||||
|
||||
- [ ] Fit angle adjuster
|
||||
|
||||
1. - [ ] Collect data points and preprocess them (LP-filter, drift correction, gaussian fit: is it normally distributed?)
|
||||
2. - [ ] Fit different functions
|
||||
3. - [ ] Implement correction algorithm
|
||||
4. - [ ] Evaluate ajuster --> plot should show always same angle.
|
||||
5. - [ ] Repeat 1-4 until good results
|
||||
|
||||
- [ ] Implement on PX4
|
||||
|
||||
- [ ] Repair drone to make it flyable.
|
||||
|
||||
|
||||
|
||||
Data Analysis
|
||||
|
||||
- Add lower RPM data 0-2000 RPM with modulations
|
||||
-
|
||||
|
||||
|
||||
|
||||
|
||||
# Mid Term
|
||||
|
||||
- [ ] OneSec Data analysis library
|
||||
|
||||
- [ ] Drift-correction function
|
||||
|
||||
- [ ] Force Torque analysis class
|
||||
|
||||
- [ ] Properly implement PX4 code with upstream. Nice commits and comments
|
||||
|
||||
- [ ] Look at Jerrys code
|
||||
|
||||
- [ ] Good habits?
|
||||
|
||||
- [ ] Do presentation with git and how we want to develop.
|
||||
|
||||
- [ ] Implement circular roll-pitch input in PX4
|
||||
|
||||
- [ ] Test it's influence
|
||||
|
||||
# Long Term
|
||||
|
||||
# Brain Drain
|
||||
@@ -1,104 +0,0 @@
|
||||
# Today
|
||||
|
||||
- [ ] Unified naming system of prototypes and versions. For all hardware and all software
|
||||
|
||||
- [ ] Sensor integration virtual swashplate into px4
|
||||
|
||||
- [x] Github
|
||||
|
||||
|
||||
|
||||
# Later at some point
|
||||
|
||||
- [ ] Fuse system. What fuse to place where and how to separate different parts?
|
||||
|
||||
- [ ] Find temperature sensors and integrate onto pcb (where main components are)
|
||||
|
||||
- [ ] Finish schematics TOBY L210
|
||||
|
||||
- [ ] Finish connection camera connector to SOM
|
||||
|
||||
- [ ] Fan connector
|
||||
|
||||
- [ ] Decide on GNSS solution with Dannick
|
||||
|
||||
- [ ] Power button to other qualcomm and possible physical switch as well.
|
||||
|
||||
- [ ] Order latching cables and crimp set
|
||||
|
||||
- [x] Add DEBUG UART Testpoints or pins
|
||||
|
||||
# Completed
|
||||
|
||||
- [x] Send email to Atlantik Elektronik, confirming reception of vision system
|
||||
|
||||
- Confirm reception
|
||||
- We broke camera, while testing --> are there replacements?
|
||||
- Camera works for us --> is it possible to customize the camera? (longer cable, different lens
|
||||
- Heat dissipation for camera
|
||||
- Heat dissipation for SOM (do they have any values?)
|
||||
- How to send original unit back?
|
||||
- For custom carrier-board. Can wifi/bluetooth antennas on SOM be used?
|
||||
- Are there any more resources available? (schematics of SOM?)
|
||||
|
||||
# Swashplate Analysis
|
||||
|
||||
- [ ] How bad are the vibrations?
|
||||
|
||||
- [ ] What are the steps needed to make it fly?
|
||||
|
||||
|
||||
|
||||
|
||||
1. Test without motors: Is swashplate well calibrated?
|
||||
2. Test vibrations of one motor and the other and together without propellers.
|
||||
|
||||
1. Analyze the data (vibration analysis & rpm feedback)
|
||||
2. Are the main vibration frequencies related to the rpm?
|
||||
3. What are the causes of those vibrations?
|
||||
4. Are they problematic?
|
||||
3. Are the motor shafts thick enough?
|
||||
|
||||
# Electronics Thoughts
|
||||
|
||||
- [ ] PDB is bad! No regenerative breaking possibility included. If used with regenerative breaking escs there will be huge voltage spikes which damage other things.
|
||||
|
||||
|
||||
|
||||
# Mid-Term
|
||||
|
||||
- [ ] Prepare meeting Dannick allgemeine situation
|
||||
|
||||
- [ ] Wie geht es mir?
|
||||
|
||||
- [ ] Lösungsvorschläge?
|
||||
|
||||
- [ ] Was stört mich an der ganzen Situation?
|
||||
|
||||
- [ ] Meeting Dannick Drive Train
|
||||
|
||||
- [ ] Übersichtsdokument:
|
||||
|
||||
- [ ] Swash: probleme was probiert mögliche lösungen
|
||||
|
||||
- [ ] Virt swash: probleme was probiert mögliche lösungen
|
||||
|
||||
|
||||
|
||||
# Short-Term
|
||||
|
||||
- [ ] Test twisted vs normal props
|
||||
|
||||
- [ ] Tune control system rate controller
|
||||
|
||||
- [ ] Implement position control and tune
|
||||
|
||||
- [ ] RTK?
|
||||
|
||||
- [ ] Optical Flow?
|
||||
|
||||
- [ ] Discuss with Dannick
|
||||
|
||||
- [ ] Sign contracts for stock and employment
|
||||
|
||||
# Long-Term
|
||||
@@ -1 +0,0 @@
|
||||
[https://www.ecalc.ch](https://www.ecalc.ch)
|
||||
BIN
OneNote/OSD/Assembly/.syncthing.Dos & Don'ts.md.tmp
Normal file
BIN
OneNote/OSD/Assembly/.syncthing.Dos & Don'ts.md.tmp
Normal file
Binary file not shown.
@@ -1,5 +0,0 @@
|
||||
Dos
|
||||
|
||||
- Keep wires as short as possible.
|
||||
- [Twist battery cables](https://www.4qd.co.uk/docs/good-wiring-practise/) and motor cables to reduce loop inductance --> less interference
|
||||
- [Add ferrite chokes](https://www.4qd.co.uk/docs/motor-noise-suppression/) and other filters to reduce spikes
|
||||
BIN
OneNote/OSD/Atlantik/.syncthing.Atlantik - 27.10.21.md.tmp
Normal file
BIN
OneNote/OSD/Atlantik/.syncthing.Atlantik - 27.10.21.md.tmp
Normal file
Binary file not shown.
BIN
OneNote/OSD/Atlantik/.syncthing.Atlantik - 5.5.21.md.tmp
Normal file
BIN
OneNote/OSD/Atlantik/.syncthing.Atlantik - 5.5.21.md.tmp
Normal file
Binary file not shown.
@@ -1,19 +0,0 @@
|
||||
# Vorbereitung
|
||||
|
||||
|
||||
|
||||
## Fragen
|
||||
|
||||
### Service Package
|
||||
|
||||
- Service Period
|
||||
|
||||
|
||||
|
||||
## State of the Art - Electronics
|
||||
|
||||
### Main Board
|
||||
|
||||
|
||||
|
||||
 
|
||||
@@ -1,34 +0,0 @@
|
||||
# Questions
|
||||
|
||||
- [ ] Fragen in Mail
|
||||
|
||||
- [ ] Software support included in the support package
|
||||
|
||||
# Notes
|
||||
|
||||
- RB5 related products: leadtime of up to 36 weeks!
|
||||
- We can order a bundle with Atlantik Elektorik, they provide both EG25 and other quectel modules.
|
||||
- AE has Antenna specialists, which can take a look at our design
|
||||
- We are leaving the free support package… What support do we want in the future?
|
||||
- Thundercomm has turn-key solutions, where they provide the whole PCBA. They can manufacture them and assemble them, including their SOM.
|
||||
|
||||
- - [ ] What are their capabilities?
|
||||
- Advantage, because thundercomm will be interested in producing everything on time.
|
||||
- We could (and maybe should) work together with Thundercomm. They have large expertise in drone electronics, since they have produced the electronics for several drone companies (e.g. parrot).
|
||||
|
||||
|
||||
|
||||
|
||||
# Todo
|
||||
|
||||
- [ ] Block Diagram mit AE teilen
|
||||
|
||||
- [ ] Decide with Dannick if we need level 2 or 3 of support. Or customized support package.
|
||||
|
||||
- [ ] Haben wir NDA unterzeichnet?
|
||||
|
||||
- [ ] @Dominik, hast du news bezüglich Design files? Du hast letztes Mal gesagt du würdest Atlantik Elektronik fragen.
|
||||
|
||||
|
||||
|
||||
Mit Zlatko und Dominik
|
||||
BIN
OneNote/OSD/Battery/.syncthing.Requirements.md.tmp
Normal file
BIN
OneNote/OSD/Battery/.syncthing.Requirements.md.tmp
Normal file
Binary file not shown.
@@ -1,18 +0,0 @@
|
||||
- Overcurrent protection
|
||||
- Overcharging over discharging protection
|
||||
- Over-voltage, under-voltage
|
||||
- Under temperature
|
||||
- Switch to shut off the battery
|
||||
- Balanced charging
|
||||
- Communication with system (can? I2C?)
|
||||
|
||||
- Cell voltages
|
||||
- State of Charge (SoC)
|
||||
- State of health (SOH) capacity compared to initial capacity
|
||||
- Temperatures
|
||||
- Current
|
||||
- State of Safety (any safety indication: combination of SoC, SOH, temperatures, currents, etc.)
|
||||
- Energy delivered since last charge
|
||||
- Internal impedance --> can be used to estimate when to replace battery
|
||||
- Coulomb counter (how much charge delivered so far and how much is stored?
|
||||
- Total number of cycles
|
||||
BIN
OneNote/OSD/CarrierBoard/.syncthing.CAD - Software.md.tmp
Normal file
BIN
OneNote/OSD/CarrierBoard/.syncthing.CAD - Software.md.tmp
Normal file
Binary file not shown.
BIN
OneNote/OSD/CarrierBoard/.syncthing.Design Rules.md.tmp
Normal file
BIN
OneNote/OSD/CarrierBoard/.syncthing.Design Rules.md.tmp
Normal file
Binary file not shown.
BIN
OneNote/OSD/CarrierBoard/.syncthing.Ethernet research.md.tmp
Normal file
BIN
OneNote/OSD/CarrierBoard/.syncthing.Ethernet research.md.tmp
Normal file
Binary file not shown.
Binary file not shown.
BIN
OneNote/OSD/CarrierBoard/.syncthing.Lessons V0.1.2.md.tmp
Normal file
BIN
OneNote/OSD/CarrierBoard/.syncthing.Lessons V0.1.2.md.tmp
Normal file
Binary file not shown.
BIN
OneNote/OSD/CarrierBoard/.syncthing.TODO.md.tmp
Normal file
BIN
OneNote/OSD/CarrierBoard/.syncthing.TODO.md.tmp
Normal file
Binary file not shown.
BIN
OneNote/OSD/CarrierBoard/.syncthing.Todos for V0.2.md.tmp
Normal file
BIN
OneNote/OSD/CarrierBoard/.syncthing.Todos for V0.2.md.tmp
Normal file
Binary file not shown.
@@ -1,3 +0,0 @@
|
||||
KiCad - Open Source
|
||||
|
||||
What could be used to simulate a circuit?
|
||||
@@ -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
|
||||
@@ -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
|
||||
@@ -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)
|
||||
@@ -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)
|
||||
@@ -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.
|
||||
@@ -1,5 +0,0 @@
|
||||
Submodules
|
||||
|
||||
- Power Distribution Board
|
||||
- Flight Controller
|
||||
- Coral SoM Footprint
|
||||
@@ -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)
|
||||
@@ -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
|
||||
@@ -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
|
||||
Binary file not shown.
BIN
OneNote/OSD/Control System/.syncthing.Learning.md.tmp
Normal file
BIN
OneNote/OSD/Control System/.syncthing.Learning.md.tmp
Normal file
Binary file not shown.
Binary file not shown.
@@ -1,41 +0,0 @@
|
||||
Xdd = Ax + Bu
|
||||
|
||||
Y = Cx + Du
|
||||
|
||||
|
||||
|
||||
|
||||
A and B decide if it is controllable
|
||||
|
||||
C and D decide if it is observable
|
||||
|
||||
# Controlability
|
||||
|
||||
- System can be uncontrollable linearly, but controllable non-linearly
|
||||
|
||||
|
||||
|
||||
|
||||
## Linear Systems
|
||||
|
||||
1. Compute Controllability Matrix C = [B AB … A^(n-1)B]
|
||||
2. If rank( C) = n <==> controllable
|
||||
3. Singular value decomposition (SVD) tells us about:it orders singular vectors to show most controllable to least controllable states
|
||||
|
||||
|
||||
|
||||
- If system is controllable then:
|
||||
|
||||
- Arbitrary eigenvalue (pole) placementu = -Kx <==> xd = (A-BK)x
|
||||
- Reachibility (get to any state in R^n)R_t = R_n
|
||||
|
||||
Definitions
|
||||
|
||||
- Reachable set R_t: all vectors in Rn that can be reached zome where sys is controllable
|
||||
- Controllability Matrix: C = [B AB … A^(n-1)B]This matrix is equivalent to an impulse response in dicrete time: basically matrix says wether the control input reaches all the states eventually.
|
||||
- Controllability Gramian:W_t = 
|
||||
|
||||
- 
|
||||
- Stabilizibility: all unstable directions (eigenvectors) are controllable.
|
||||
|
||||
- Unstable and lightly damped directions should be controllable!
|
||||
@@ -1,13 +0,0 @@
|
||||
[https://apmonitor.com/pdc/](https://apmonitor.com/pdc/)
|
||||
|
||||
[https://apmonitor.com/pdc/index.php/Main/ModelSimulation](https://apmonitor.com/pdc/index.php/Main/ModelSimulation)
|
||||
|
||||
[https://ch.mathworks.com/de/videos/tech-talks/controls.html](https://ch.mathworks.com/de/videos/tech-talks/controls.html)
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Good overview of drone control
|
||||
|
||||
[A_review_on_drones_controlled_in_real-time.pdf](https://onedrive.live.com/embed?resid=D05036151E62BA13%213756&filename=A_review_on_drones_controlled_in_real-time.pdf&authkey=!AEvlrbu_TdPVjBw)
|
||||
@@ -1,4 +0,0 @@
|
||||
==A====utomatic Control Of Aircraft & Missile ( Blakelock)==
|
||||
|
||||
|
||||
> From <[https://archive.org/details/AutomaticControlOfAircraftMissileBlakelock/page/n79/mode/2up](https://archive.org/details/AutomaticControlOfAircraftMissileBlakelock/page/n79/mode/2up)>
|
||||
@@ -1,16 +0,0 @@
|
||||
[https://ethz.ch/content/dam/ethz/special-interest/mavt/dynamic-systems-n-control/idsc-dam/Lectures/Control-Systems-2/Exercises/python-control.pdf](https://ethz.ch/content/dam/ethz/special-interest/mavt/dynamic-systems-n-control/idsc-dam/Lectures/Control-Systems-2/Exercises/python-control.pdf)
|
||||
|
||||
|
||||
|
||||
|
||||
# Books
|
||||
|
||||
- Dynamical Systems with Applications using Python
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Websites
|
||||
|
||||
- [https://www.eigensteve.com/](https://www.eigensteve.com/)
|
||||
BIN
OneNote/OSD/Courses/.syncthing.Arduino Low level.md.tmp
Normal file
BIN
OneNote/OSD/Courses/.syncthing.Arduino Low level.md.tmp
Normal file
Binary file not shown.
Binary file not shown.
@@ -1,34 +0,0 @@
|
||||
## Timers available on Arduino Uno
|
||||
|
||||
|
||||

|
||||
|
||||
If we use Timer 0 for something else, the arduino functions delay, millis, … won't work properly anymore.
|
||||
@@ -1,46 +0,0 @@
|
||||
## Sensors
|
||||
|
||||
GPS: Accuracy: 3-5m, @2Hz
|
||||
|
||||
Indoor: 1mm @ 200-500 Hz
|
||||
|
||||
## Research
|
||||
|
||||
[https://vision.in.tum.de/publications](https://vision.in.tum.de/publications)
|
||||
|
||||
|
||||
|
||||
## Geometry
|
||||
|
||||
Invert, concatenate, estimate, optimize 3D orientation
|
||||
|
||||
## Algorithms
|
||||
|
||||
IMU Strapdown Algorithm
|
||||
|
||||
Control Theory
|
||||
|
||||

|
||||
|
||||
Watch out: The inner control loops must be around an order of magnitude faster than the outer ones, such that they appear "static". If not you can get interference between the two
|
||||
BIN
OneNote/OSD/ESC/.syncthing.Flipsky VESC repair.md.tmp
Normal file
BIN
OneNote/OSD/ESC/.syncthing.Flipsky VESC repair.md.tmp
Normal file
Binary file not shown.
Binary file not shown.
BIN
OneNote/OSD/ESC/.syncthing.ST-Motor Control.md.tmp
Normal file
BIN
OneNote/OSD/ESC/.syncthing.ST-Motor Control.md.tmp
Normal file
Binary file not shown.
Binary file not shown.
BIN
OneNote/OSD/ESC/.syncthing.STM32 Resources.md.tmp
Normal file
BIN
OneNote/OSD/ESC/.syncthing.STM32 Resources.md.tmp
Normal file
Binary file not shown.
@@ -1 +0,0 @@
|
||||
When trying to hook up 2 esc's in parallel, the 3V3 regulator broke. Marking(LG33) It is probably a [mic5219](https://ww1.microchip.com/downloads/en/DeviceDoc/MIC5219-500mA-Peak-Output-LDO-Regulator-DS20006021A.pdf). Can be [found on digi--key](https://www.digikey.ch/product-detail/de/microchip-technology/MIC5219-3-3YM5-TR/576-1281-1-ND/771902)
|
||||
@@ -1 +0,0 @@
|
||||
[https://github.com/odriverobotics/ODrive](https://github.com/odriverobotics/ODrive)
|
||||
@@ -1 +0,0 @@
|
||||
[https://www.st.com/resource/en/application_note/dm00666970-current-sensing-in-bldc-motor-application-stmicroelectronics.pdf](https://www.st.com/resource/en/application_note/dm00666970-current-sensing-in-bldc-motor-application-stmicroelectronics.pdf)
|
||||
@@ -1,3 +0,0 @@
|
||||
# Tutorials
|
||||
|
||||
- [https://www.playembedded.org/blog/stm32-gpio-chibios-pal/](https://www.playembedded.org/blog/stm32-gpio-chibios-pal/)
|
||||
@@ -1 +0,0 @@
|
||||
[https://www.st.com/content/st_com/en/support/learning/stm32-education/stm32-moocs/Motor_Control_MOOC_Part_3.html](https://www.st.com/content/st_com/en/support/learning/stm32-education/stm32-moocs/Motor_Control_MOOC_Part_3.html)
|
||||
Binary file not shown.
@@ -1,12 +0,0 @@
|
||||
We could add our custom flight controller to our board, since it is all [published](https://github.com/pixhawk/Hardware)
|
||||
|
||||
|
||||
|
||||
[https://docs.google.com/spreadsheets/d/1-n0__BYDedQrc_2NHqBenG1DNepAgnHpSGglke-QQwY/edit#gid=730959725](https://docs.google.com/spreadsheets/d/1-n0__BYDedQrc_2NHqBenG1DNepAgnHpSGglke-QQwY/edit#gid=730959725)
|
||||
|
||||
Example pinout for fmuv5
|
||||
|
||||
|
||||
|
||||
|
||||
Newest draft: [FMUv6X](https://github.com/pixhawk/Pixhawk-Standards/blob/master/DS-012%20Pixhawk%20Autopilot%20v6X%20Standard.pdf)
|
||||
BIN
OneNote/OSD/Hardware/.syncthing.Can sniffer.md.tmp
Normal file
BIN
OneNote/OSD/Hardware/.syncthing.Can sniffer.md.tmp
Normal file
Binary file not shown.
BIN
OneNote/OSD/Hardware/.syncthing.JTAG.md.tmp
Normal file
BIN
OneNote/OSD/Hardware/.syncthing.JTAG.md.tmp
Normal file
Binary file not shown.
BIN
OneNote/OSD/Hardware/.syncthing.Overview.md.tmp
Normal file
BIN
OneNote/OSD/Hardware/.syncthing.Overview.md.tmp
Normal file
Binary file not shown.
@@ -1,7 +0,0 @@
|
||||
[https://www.8devices.com/products/usb2can_korlan](https://www.8devices.com/products/usb2can_korlan)
|
||||
|
||||
kvaser leaf light v2
|
||||
|
||||
[https://www.rusoku.com/products](https://www.rusoku.com/products)
|
||||
|
||||
[https://www.distrelec.ch/en/can-bus-analyzer-microchip-apgdt002/p/17334511](https://www.distrelec.ch/en/can-bus-analyzer-microchip-apgdt002/p/17334511)
|
||||
@@ -1,21 +0,0 @@
|
||||
[https://blog.senr.io/blog/jtag-explained](https://blog.senr.io/blog/jtag-explained)
|
||||
|
||||
|
||||
|
||||
What is JTAG?
|
||||
|
||||
It's an interface to connect to a chip/pcb and to test/debug/program it.
|
||||
|
||||
It is incredibly powerful
|
||||
|
||||
JTAG with FlightControllers
|
||||
|
||||
[https://discuss.ardupilot.org/t/low-level-debugging-the-stm32-and-ardupilot/49280](https://discuss.ardupilot.org/t/low-level-debugging-the-stm32-and-ardupilot/49280)
|
||||
|
||||
|
||||
|
||||
Use Probe to debug with JTAG
|
||||
|
||||
[https://dev.px4.io/v1.10/en/debug/system_console.html](https://dev.px4.io/v1.10/en/debug/system_console.html)
|
||||
|
||||
[https://kb.zubax.com/display/MAINKB/Dronecode+Probe+documentation](https://kb.zubax.com/display/MAINKB/Dronecode+Probe+documentation)
|
||||
@@ -1,3 +0,0 @@
|
||||
Good Companion Computer Peripheral Overview
|
||||
|
||||
[https://docs.px4.io/v1.9.0/en/peripherals/companion_computer_peripherals.html](https://docs.px4.io/v1.9.0/en/peripherals/companion_computer_peripherals.html)
|
||||
BIN
OneNote/OSD/Ideas/.syncthing.Security.md.tmp
Normal file
BIN
OneNote/OSD/Ideas/.syncthing.Security.md.tmp
Normal file
Binary file not shown.
@@ -1,23 +0,0 @@
|
||||
MavLink
|
||||
|
||||
Communication between base station and drone must be encrypted!
|
||||
|
||||
|
||||
|
||||
|
||||
[https://discuss.px4.io/t/mavlink-security-problem/5921/6](https://discuss.px4.io/t/mavlink-security-problem/5921/6)
|
||||
|
||||
[https://hackaday.com/2015/10/15/hijacking-quadcopters-with-a-mavlink-exploit/](https://hackaday.com/2015/10/15/hijacking-quadcopters-with-a-mavlink-exploit/)
|
||||
|
||||
|
||||
|
||||
Paper:
|
||||
|
||||
[1905.00265.pdf](https://onedrive.live.com/embed?resid=D05036151E62BA13%212688&filename=1905.00265.pdf&authkey=!AIRAvZFMYUQgHXk)
|
||||
|
||||
|
||||
|
||||
|
||||
Algorithms:
|
||||
|
||||
Have a function on both base and drone that calculates a hash based on time and place or other things like mac address. Send hashed hash.
|
||||
@@ -1,220 +0,0 @@
|
||||
# Preparation
|
||||
|
||||
## Information
|
||||
|
||||
- Mostly Europe, Australia, US
|
||||
|
||||
|
||||
|
||||
|
||||
## Questions
|
||||
|
||||
- [x] Datasheet availability?
|
||||
|
||||
- [x] Is Quectel EG25-G best module for us?
|
||||
|
||||
- [x] Lead-Time
|
||||
|
||||
- [x] Wholesale prices
|
||||
|
||||
- [ ] Industrial/automotive grade
|
||||
|
||||
- [ ] Reliability Testing
|
||||
|
||||
- [ ] Certification procedure with Quectel Module?
|
||||
|
||||
- [ ] We do not have consumer product, no CE certificate needed.
|
||||
|
||||
- [ ] What do we need to consider?
|
||||
|
||||
- [ ] Interface
|
||||
|
||||
- [ ] USB 2.0
|
||||
|
||||
- [ ] Uart?
|
||||
|
||||
- [ ] Both simultaneously
|
||||
|
||||
- [ ] Guaranteed time of product life (10y?)--> if qualcomm cancels they will cancel as well.they will replace it as well.
|
||||
|
||||
- [ ] Module without GNSS?
|
||||
|
||||
- [ ] Precision of builtin GNSS?
|
||||
|
||||
- [ ] Effect of 1 or 2 (receive diversity antenna) Antennas?
|
||||
|
||||
- [ ] What are expected data rates and reception coverage?
|
||||
|
||||
- [ ] Difference formfactor? LCC / LGA
|
||||
|
||||
- [ ] Difference LTE FDD / TDD (Frequency / Time Division Duplexing)
|
||||
|
||||
- [ ] What chipset is used within module?Qualcomm 9X07
|
||||
|
||||
- [ ] What is advantage of Quectel eG25-g compared to other modules?
|
||||
|
||||
- [ ] Samples available?--> yes
|
||||
|
||||
GNSS:
|
||||
|
||||
Standalon required!
|
||||
|
||||
EG25-G --> precision up to 10m can happen quite often
|
||||
|
||||
|
||||
|
||||
Why Cat4 --> 4k video feed
|
||||
|
||||
Why international
|
||||
|
||||
|
||||
|
||||
|
||||
ISO16494 --> automotvie
|
||||
|
||||
|
||||
|
||||
Android smart modules
|
||||
|
||||
|
||||
|
||||
|
||||
360 deg support
|
||||
|
||||
|
||||

|
||||
|
||||
Field engineering
|
||||
|
||||
|
||||
|
||||
|
||||
Certification --> we send, they do the tests then 3rd party gives certificate
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
FAE Lukas
|
||||
|
||||
|
||||
|
||||
|
||||
Manufacturing
|
||||
|
||||

|
||||
|
||||
Smart modules
|
||||
|
||||

|
||||
|
||||
Min quantity: 10k pieces.
|
||||
|
||||
|
||||
|
||||
|
||||
Lead time 26 weeks
|
||||
|
||||
Prototypes 20 modules no problem.
|
||||
|
||||
|
||||
|
||||
Distributors:
|
||||
|
||||
Package Quantity -- 250
|
||||
|
||||
Import is difficult! Distributors have solved that problem
|
||||
|
||||
-->Tekmodul (munich germany) good support, also with antenna design. Quectel can help as well with Antenna design (Stephan from Quectel)
|
||||
|
||||
|
||||
|
||||
|
||||
Wholesale < 30$ for 1k+ and 10k+
|
||||
|
||||
|
||||
|
||||
Alternative
|
||||
|
||||
- EC200 (ASR chipset) save $5 roughly
|
||||
|
||||
|
||||
|
||||
**Certification**
|
||||
|
||||
Test in lab
|
||||
|
||||
CE is available for the module itself
|
||||
@@ -1,9 +0,0 @@
|
||||
# Questions
|
||||
|
||||
- [ ] What are the next steps regarding product integration?
|
||||
|
||||
- [ ] How to proceed with design? Follow Datasheet and system integration manual?
|
||||
|
||||
- [ ] How close is too close between LTE module, GNSS module and high current or high switching chips?
|
||||
|
||||
- [ ] Advantage over ublox?
|
||||
BIN
OneNote/OSD/Motors/.syncthing.BLDC Theory.md.tmp
Normal file
BIN
OneNote/OSD/Motors/.syncthing.BLDC Theory.md.tmp
Normal file
Binary file not shown.
@@ -1 +0,0 @@
|
||||
Good theory, easy to grasp: [http://web.mit.edu/first/scooter/motormath.pdf](http://web.mit.edu/first/scooter/motormath.pdf)
|
||||
@@ -1 +0,0 @@
|
||||
§
|
||||
BIN
OneNote/OSD/PDB/.syncthing.Buck Converter Learnings.md.tmp
Normal file
BIN
OneNote/OSD/PDB/.syncthing.Buck Converter Learnings.md.tmp
Normal file
Binary file not shown.
BIN
OneNote/OSD/PDB/.syncthing.V0.1.md.tmp
Normal file
BIN
OneNote/OSD/PDB/.syncthing.V0.1.md.tmp
Normal file
Binary file not shown.
BIN
OneNote/OSD/PDB/.syncthing.V0.2.md.tmp
Normal file
BIN
OneNote/OSD/PDB/.syncthing.V0.2.md.tmp
Normal file
Binary file not shown.
@@ -1,5 +0,0 @@
|
||||
TI Course:
|
||||
|
||||
[https://training.ti.com/common-mistakes-dcdc-components-features?context=1127730-1135482-1139329-1135477&cu=1135482](https://training.ti.com/common-mistakes-dcdc-components-features?context=1127730-1135482-1139329-1135477&cu=1135482)
|
||||
|
||||
[https://www.ti.com/seclit/ml/slup384/slup384.pdf](https://www.ti.com/seclit/ml/slup384/slup384.pdf)
|
||||
@@ -1,4 +0,0 @@
|
||||
Add max load to dc-converters:
|
||||
|
||||
- Observe temperature with thermal camera
|
||||
- Observe signals from dc-dc converters -- sw-node, input, output ripple, etc.
|
||||
@@ -1,11 +0,0 @@
|
||||
Precise TODOS:
|
||||
|
||||
|
||||
|
||||
**Requirements**
|
||||
|
||||
- [ ] Battery protection & redundancy
|
||||
|
||||
- [ ] Battery status communication (load cycles, current, remaining capacity, current voltage
|
||||
|
||||
- [ ] 5V source for carrier board
|
||||
@@ -1,7 +0,0 @@
|
||||
- [ ] Add on-board fuses to separate several subcircuits. In case of failure not the entire board stops working
|
||||
|
||||
- [ ] Solution for excess energy release (some sort of valve) e.g. regenerative breaking usually releases reverse currents into the batteries, but in our case it is blocked because of the ideal diodes. Compare [this manual](https://files.zubax.com/products/io.px4.sapog/Sapog_v2_Reference_Manual.pdf) page 12/39.
|
||||
|
||||
Battery:
|
||||
|
||||
Is it possible to have ideal diode and still use reverse currents?
|
||||
BIN
OneNote/OSD/Planning/.syncthing.How to plan.md.tmp
Normal file
BIN
OneNote/OSD/Planning/.syncthing.How to plan.md.tmp
Normal file
Binary file not shown.
@@ -1,17 +0,0 @@
|
||||
1. Project Map
|
||||
|
||||
1. What is the destination
|
||||
2. Who joins?
|
||||
3. What are major milestones?
|
||||
4. What obstacles and alternative routes?
|
||||
2. Stakeholders
|
||||
|
||||
1. Who?
|
||||
2. Expetations and influence?
|
||||
3. How to use their feedback
|
||||
3. Timeline
|
||||
|
||||
1. Don't be overly optimistic
|
||||
2. Make gantt chart
|
||||
4. Recruit team
|
||||
5. Goals and scope
|
||||
BIN
OneNote/OSD/Research/.syncthing.Books.md.tmp
Normal file
BIN
OneNote/OSD/Research/.syncthing.Books.md.tmp
Normal file
Binary file not shown.
BIN
OneNote/OSD/Research/.syncthing.ESD.md.tmp
Normal file
BIN
OneNote/OSD/Research/.syncthing.ESD.md.tmp
Normal file
Binary file not shown.
BIN
OneNote/OSD/Research/.syncthing.GNSS.md.tmp
Normal file
BIN
OneNote/OSD/Research/.syncthing.GNSS.md.tmp
Normal file
Binary file not shown.
BIN
OneNote/OSD/Research/.syncthing.Helicopter.md.tmp
Normal file
BIN
OneNote/OSD/Research/.syncthing.Helicopter.md.tmp
Normal file
Binary file not shown.
BIN
OneNote/OSD/Research/.syncthing.PCB Design.md.tmp
Normal file
BIN
OneNote/OSD/Research/.syncthing.PCB Design.md.tmp
Normal file
Binary file not shown.
Binary file not shown.
@@ -1,3 +0,0 @@
|
||||
1. Amir MY, Abbas V (2010) Modeling and neural control of quadcopter helicopter: MATLAB-SIMULINK based modeling, simulation and neural control of quadcopter helicopter. LAP LAMBERT Academic Publishing, Germany
|
||||
2. PutroIE(2011)Modelingandcontrolsimulationforautonomousquadcopter:quadcopternonlinearmodelingand control simulation using Matlab/Simulink environment. LAP Lambert Academic Publishing
|
||||
3. Norris D (2014) Build your own quadcopter: power up your designs with the Parallax Elev-8. McGraw-Hill Edu- cation, New York
|
||||
@@ -1,324 +0,0 @@
|
||||
[Notes to ESD essentials by TI](https://training.ti.com/esd-essentials-what-esd?context=1136983-1139548-1135647)
|
||||
|
||||
|
||||
|
||||
ESD - Electrostatic discharge
|
||||
|
||||
This happens when you're getting charged up positively and touch a conductor.
|
||||
|
||||
Large voltages can be generated that can damage Ics.
|
||||
|
||||
|
||||
|
||||
ESD diodes can be used to direct those ESD-currents into GND, before they can reach the Ics
|
||||
|
||||
|
||||

|
||||
|
||||
# Chapter 2 - ESD Working Voltage
|
||||
|
||||
Also known as Reverse Standoff Voltage
|
||||
|
||||
|
||||

|
||||
|
||||
Indicated by red: BreakDown Voltage. Any voltage larger than this will make the diode conductive.
|
||||
|
||||
|
||||

|
||||
|
||||
The signal level, which is used normally should be below VRWM --> like that we have below 10 nA leakage current.
|
||||
|
||||
|
||||
|
||||
The working voltage of the diode you choose should be slightly higher than the largest signal.
|
||||
|
||||
|
||||

|
||||
|
||||
# IEC 610000-4-2 ESD Rating
|
||||
|
||||
|
||||

|
||||
|
||||
|
||||
## Human Body Model (HBM) ESD
|
||||
|
||||
This is used to estimat the manufacturing, assembly and shipping. Not for the final use!
|
||||
|
||||
|
||||
|
||||
## Charge Device Model (CDM) ESD
|
||||
|
||||
ESD discharge through charged device into ground. Also only Manufacturing, assembly and shipping.
|
||||
|
||||
|
||||
|
||||
## IEC 61000-4-2
|
||||
|
||||
This is the model that simulates the final use by the user. There are 4 Levels and devices next to interface connectors should use at least level 4.
|
||||
|
||||
|
||||

|
||||
|
||||
# Clamping Voltage
|
||||
|
||||
This is the important measure, because it describes the voltage protection capability of the clamping diode.
|
||||
|
||||

|
||||

|
||||
|
||||
Depending on the ESD strike a different current is shunted through the diode. This results in a remaining voltage drop, which the system circuitry will be exposed to. That is the voltage that can still damage our system. --> select diode according to max voltage that system can survive.
|
||||
|
||||
# Parasitic Capacitance
|
||||
|
||||

|
||||
|
||||
Because of the physics the diode can be modeled as a capacitor. Hence it will influence the circuit during normal operation.
|
||||
|
||||
|
||||
|
||||
If parasitic capacitance is high it can influence the signal:
|
||||
|
||||

|
||||
|
||||
This means for a highspeed signal it is extremely important that the parasitic capacitance is small.
|
||||
|
||||
|
||||
|
||||
General overview:
|
||||
|
||||

|
||||
|
||||
|
||||
# ESD Protection selection
|
||||
|
||||

|
||||

|
||||
@@ -1,13 +0,0 @@
|
||||
Can we use AI to improve GNSS signals?
|
||||
|
||||
|
||||
|
||||
[https://insidegnss.com/what-are-the-roles-of-artificial-intelligence-and-machine-learning-in-gnss-positioning/](https://insidegnss.com/what-are-the-roles-of-artificial-intelligence-and-machine-learning-in-gnss-positioning/)
|
||||
|
||||
|
||||
|
||||
--> use semantic image comparison with database.
|
||||
|
||||
--> multipath detection
|
||||
|
||||
--> better sensor fusion
|
||||
@@ -1,112 +0,0 @@
|
||||
> [!caution] This page contained a drawing which was not converted.
|
||||
|
||||
Tip speed should not exceed 200 m/s.
|
||||
|
||||
For us that is roughly 6400 rpm.
|
||||
|
||||
Formula: 200*60/D/pi
|
||||
|
||||
- Rotor size and max weight are first things to consider.
|
||||
- Normalizing Entities to compare between models --> make dimensionless
|
||||
|
||||
- Non-dimensional induced velocity
|
||||
|
||||
- 
|
||||
- Thrust coefficient
|
||||
|
||||
- 
|
||||
- VT is tip speed of blade
|
||||
- Thrust is divided by dynamic pressure times area --> gives Force [N]
|
||||
- Combined:
|
||||
|
||||
- 
|
||||
- Power overview:
|
||||
|
||||
- Induced Power is major part of power during hover
|
||||
- Power to overcome blade drag PO
|
||||
- ==Solidity== of rotor:
|
||||
|
||||
- 
|
||||
- Skin friction drag:
|
||||
|
||||
- 
|
||||
|
||||
|
||||
- 
|
||||
- Rotor efficiency: M = Pi/PO --> Figure of Merit
|
||||
|
||||
- 
|
||||
- ki is induced power factor because of a variation in induced velocity
|
||||
|
||||
|
||||
|
||||
|
||||
# Blade Aerodynamics
|
||||
|
||||
- 
|
||||
- Angles:
|
||||
|
||||
- Inflow Angle (small angle approx)
|
||||
- 
|
||||
- Theta: pitch control by pilot
|
||||
- Alpha: angle of attack seen by blade
|
||||
- Aerodynamic forces
|
||||
|
||||
- Lift and Drag
|
||||
|
||||
- 
|
||||
- Thrust
|
||||
|
||||
- 
|
||||
- Blade Torque
|
||||
|
||||
- 
|
||||
- Thrust coefficient with a linear twist blade and the assumption of no stall and no compressibility
|
||||
|
||||
- 
|
||||
|
||||
- 
|
||||
- Lambda: inflow factor
|
||||
|
||||
- 
|
||||
- Relating the inflow factor to momentum theory (see above)
|
||||
|
||||
- 
|
||||
- Relationship between inflow factor and pitch setting
|
||||
|
||||
- 
|
||||
- Why are blades twisted? My assumption is that the angle of attack seen by the blade depends on the wind speed it experiences. This in turn, depends on the radius and the angular velocity of the blade. The closer you are at the hub, the larger is the inflow angle and thus the smaller is the angle of attack. That means if we twist the blade and add additional aoa close to the hub and remove aoa where the speed is high, we will have more lift in total and not have a stalling condition somewhere and not at other places.
|
||||
|
||||
|
||||
|
||||
# Flapping, Feathering & Lead-Lag
|
||||
|
||||
- Coriolis Force induces lag
|
||||
|
||||
- 
|
||||
-
|
||||
@@ -1 +0,0 @@
|
||||
[Great article about Ground return paths and mixed signal pcbs](https://www.maximintegrated.com/en/design/technical-documents/tutorials/5/5450.html)
|
||||
@@ -1,5 +0,0 @@
|
||||
# Ideas
|
||||
|
||||
- Use large coaxial for thrust (collective) and pitch only and add small rotors on wings for roll.
|
||||
|
||||
-
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user