diff options
author | gennyble <gen@nyble.dev> | 2023-06-08 00:54:51 -0500 |
---|---|---|
committer | gennyble <gen@nyble.dev> | 2023-06-08 00:54:51 -0500 |
commit | aec3f2c27e228155bed768f9490a724de1f9bda3 (patch) | |
tree | b8e68f54db18741c0b8c98441ddda1d829a6a542 /README.md | |
parent | f0ab93507bc7de8be6172768e19d6f9baa5e46e7 (diff) | |
download | lri-rs-aec3f2c27e228155bed768f9490a724de1f9bda3.tar.gz lri-rs-aec3f2c27e228155bed768f9490a724de1f9bda3.zip |
readme
Diffstat (limited to 'README.md')
-rw-r--r-- | README.md | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/README.md b/README.md index 9d27d22..6a764e4 100644 --- a/README.md +++ b/README.md @@ -16,12 +16,14 @@ of the file header? Can we parse the message in the header with the protobuf as described in: [dllu/lri-rs](https://github.com/dllu/lri-rs/blob/main/proto/lightheader.proto)? ### File Header -The file seems to consist of a header followed be a proto buf message +The LightHeader seems to consist of a header followed be a proto buf message that then gets appended to it. The header is **little endian** #### File Header Structure +This is only sometimes the case. It seems that "header length (32)" field is sometimes a lot *a lot* bigger. in that case you have the sensor data. perhaps then the message length is some inidication to protobuf data? perhaps it's nothing? padding? + The header is 32 bytes long. and goes as follows: | bytes | meaning | | ----- | ------- | @@ -35,6 +37,7 @@ The header is 32 bytes long. and goes as follows: and then follows the message which already has a known length ## Image Sensors +Listen in sensor_type.proto of lri-rs | Sensor | Resolutions | Output | | - | - | - | |