Thomas Sarlandie

I like your workaround but we should fix the underlying issue and not generate anything if the sensor is not responding.

I think we both agree here ;) * I agree with your solution to just disable the IMU in the configuration. I think [this already works](https://github.com/sarfata/kbox-firmware/blob/master/src/host/main.cpp#L145). * I agree that...

> BTW does the EEPROM get harmed by writing to it too often? Great question! On the Teensy the EEPROM is not really an EEPROM. It's a "fake EEPROM" in...

I think the easiest way to do this if we decide to store the log value in this "EEPROM" is just to make sure we use a "backup to FlexRAM...

Thanks for the suggestion. Could you make those changes and send a pull-request?

Not sure. I guess the person implementing this gets to decide ;) My first intuition would be to just check that the user has changed the default information. This way...

The README gives some explanation: https://practicingruby.com/articles/tricks-for-working-with-text-and-files but it seems a bit outdated. For 25kHz, you will need a period of 40us. If you change [`CYCLE_TIME_US `](https://github.com/sarfata/pi-blaster/blob/7af3d142573dc177c285c5c56d5f6f426d22a09c/pi-blaster.c#L111) in the source code...

After the changes in the code, the startup code shows: ``` pi@raspberrypi:~/pi-blaster $ sudo ./pi-blaster -D MBox Board Revision: 0x10 DMA Channels Info: 0x7f35, using DMA Channel: 14 Using hardware:...

Yes I have done some tests too and I it does not work when there are less than 200 samples (cycles period divided by time unit). So right now the...

No sorry. I have not been working on this project.