2024-11-05(6): Project, Sysprog Recap
Org
Clarify licensing status
used training material (faschingbauer.me) is GPL3
also on faschingbauer.me: project management, design docs, thereby that material is also under GPL3
No specific license: https://github.com/jfasch/FH-STECE2022 (this year’s EC2 project) and https://github.com/jfasch/FH-ENDLESS (my contributions to it)
Which license to pick? -> https://choosealicense.com/
Define hardware (task group) owner
Material
Recap
class point. Emphasize onconst, and initializationsigned vs. unsigned:
SysFSPWMPinhas a mixture ofuint64_tandint64_t. Should take care, mostly about semantics:periodandduty_cyclecannot become negative, so these should possibly be unsigned. But how about conversion toSysFSFile’s methods, which currently only takeint64_t. Solution: check for overflow/conversion, or adduint64_tmethods toSysFSFile.
Project
Software implications: aggregating objects into instances of higher level types
(DONE) RC Servo Control, which aggregates a (DONE) PMW Abstraction On Top Of /sys/class/pwm/
(DONE) Motor Control: BTN9960LV, which aggregates one or two (DONE) PMW Abstraction On Top Of /sys/class/pwm/
(DONE) Motor Control: BTN9960LV
How’s it with hardware? Do we need 2 PWMs, or just one?
Ask for permission of car layout docs -> put it in repo
How’s it with software? Write test together.
-
How’s it with software? Write test together.
(CLOSED) Proximity Sensor: VL53L1X: talk about usage sketch of
class VL53L1X(ACTIVE) Gyroscope (BNO055): talk about usage sketch of
class BNO055
Homework
ip addrSomeone to implement signed/unsigned? ⟶ std::stoull()
Myself
create git page, and link it to course main page
./fh-stece22-suite: /usr/lib/arm-linux-gnueabihf/libstdc++.so.6: version `GLIBCXX_3.4.26' not found (required by ./fh-stece22-suite)uint64/int64 woes (pwm vs. sysfsfile) -> see existing commented-out test