2024-11-26(3): Project

Org 

readthedocs -> dev documentation (jjj todo screenplay of steps, draw on whiteboard)
Project task list restructured, jjj link and explain
80 20 regel
- nun bei den restlichen 80 angekommen, plus ein paar features und nun lernen wir c++ :-)

Show 

Github and Git: Project Management 

as user (you)
- fork
- clone
- push pull among team
- pull request
- pull upstream changes
  - whats a remote
  - pulling from there (upstream)
switch hat to me (link me@gh jjj)
- execute pull request
- show what gh says on pr page, explain with a shetch
- whine a little
  - show how I can rely on tests
  - absolutely neccessary in large scale development -> linux kernel (gh is kindergarten)

Development, Including `sshfs`

Development Process

Project Status 

Car Itself 

Will close tasks soon
In favor of steering application
- (ACTIVE) Commandline Driving
- (ACTIVE) Crazy Car (Steering App)
⟶ POSIX Message Queues
We will need a defined human/human interface between hardware and software
- (ACTIVE) Hardware Initialization

Sensors 

(ACTIVE) Gyroscope (BNO055)
- Address conflict with the proximity sensor
- Close task in favor of …
- Sensor Values Into File (CSV)
(CLOSED) Proximity Sensor: VL53L1X
- Still a problem with 32bit I2C writes
  - The status register shows the value of 0 when default I2C bus speed is used
  - Shows 1 when I2C bus speed matches that of Arduino (jjj what is that?). Funny because this is a higher speed.
- Use a scope to compare both patterns

Miscellaneous 

PWM, as configured per config.txt
- … must be quiesced by a systemd unit that exports it. This sounds wrong.
- … goes mad again 10 seconds later when boot is near complete. The boot takes so long because it’s a desktop boot.
- ⟶ What if we don’t boot into desktop?
Alternative: use PCA chip on Crazy-Pi.
Switch all to native Pi build (build on Pi locally) because toolchain is crap.