Acceleration Sampling Frequency Issues

Offen
  • Stimmt etwas nicht?
#2,498 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
Ein halber Tag
Anfängerfreundlichkeit
48/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
cpp
Bereich
embedded-iot

Rechercherichtung

The problem is in the accelerometer chip driver, where the whole FIFO buffer is read on each sample instead of only the number of valid entries the chip reports. Start by finding the FIFO read path in that driver and check the linked PineTimeSD pull request #22 for the approach the reporter used. Done means each read fetches only the valid readings, so the sampling rate matches the requested 25 Hz; this needs hardware to verify fully.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Verification
  • I searched for similar issues (including closed issues) and found none was relevant.
Introduce the issue

I use a fork of InfiniTime as a data source for my OpenSeizureDetector epileptic seizure detection project.

I noticed that although we were requesting 25 Hz accelerometer sampling frequency, we were receiving data at more like 28 Hz.

The cause seemed to be that each time we read it, we were reading the entire contents of the FIFO buffer on the accelerometer chip, rather than the number of valid readings stated on the chip.

I have fixed this in my fork, but thought you might like to implement the fix in the main InfiniTime firmware too. I also improved the error handling in the accelerometer chip driver as part of the change.

See https://github.com/OpenSeizureDetector/PineTimeSD/pull/22

Preferred solution

You might want to implement the same change (https://github.com/OpenSeizureDetector/PineTimeSD/pull/22) - I don't think it has been fixed in InfiniTime as far as I can see.

I think the 'best' option is to set up accelerometer handling as a separate task and use interrupts to drive the FIFO reading, but that is a bigger change to implement so I haven't done that yet.

Version

No response

Vorherrschende Sprache
C
Sterne
3.4k
Forks
1.1k
Ø Merge
6 Std. 10 Min.
Gemergte PRs (30 T.)
5

Entwicklungsumgebung

In Codespaces öffnen

Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus InfiniTimeOrg/InfiniTime

Alle Issues in InfiniTimeOrg/InfiniTime

Ähnliche Issues

Weitere Issues zu C

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.