Open ivogeorg opened 2 years ago
magnetometer and/or gyroscope for sensors?
We can take a page from EyesSat book and put this I2C temp sensor directly on top of the CPU...
@NotfatPrince, I am adding your good finds from Teams here:
Let's track important resources here rather than Teams. Combing through both to sync takes valuable time.
An IMU might be very useful to get data about the motion of a strung balloon cubesat for planning of future flights (e.g. stabilization, etc.).
The fastest solution under the current time constraints are to use the SparkFun Qwiic SHIM Kit for Raspberry Pi with extra sensors, for example the SparkFun High Precision Temperature Sensor - TMP117 (Qwiic) and others. The Qwiic devices can be easily daisy-chained on the I2C bus.
Sensors and RPi HATs and SHIM connector and arriving tomorrow, Tue, Oct 26.
@PaulAJanes Latest update: The telemetry gathering should be a standalone application/package. It will be controlled by the Flight Executive.
Each record has a UUID, a datetime stamp (yyyy-mm-dd hh:mm:ss, 24 hours military time format), and a set of sources in a fixed order of the data columns. Records look like a table. For example: | UUID | Datetime | Src1 | Src2 | Scr3 | Src4 |
---|---|---|---|---|---|---|
345-80012 | 2021-11-18 13:46:19 | data1 | data2 | data3 | data4 |
@ivogeorg I'm going to attempt to populate a lookup table with known sensor ids and associated info, such as registers, what those registers return in terms of how many bytes and what data it is, whether you can write to any registers and which ones and what can be written, what the range of return values is and what is the step value of the last LSB.
The idea is to be able to hook up any sensor to the system and have the system just figure out how to interact with it. In the inevitable event that I run out of time, I'll supplement with some specific code for known sensors.
I'll also be writing a framework for generic versions of different types so that, in the event that a given sensor is not on the table, some basic instructions exist to interact with the thing.
For now, I'm focusing on I2C interactions, but it should be easy-ish to convert for other systems.
@PaulAJanes, it's probably best to use the logging
facility from the Python Library. No need to reinvent the wheel. Probably the easiest way to log. We can feed into the pub-sub messaging bus before calling logging
.
Description
Currently the data collected from the daisy-chained sensors is stored in a .csv file using this code
TO DO
Knowledge
T sensor guide Environmental Sensor guide IMU sensor guide RPi internal temperature UPS power board for now Python Tutorial starting scripts upon tuning on
Deliverables
For Indoor lab test of the system: