GPIO-Sampling uses old buffer-content

orgua / shepherd

Synchronized Energy Harvesting Emulator and Recorder

MIT License

2 stars 2 forks source link

GPIO-Sampling uses old buffer-content #57

Open orgua opened 2 months ago

orgua commented 2 months ago

Latest Version. Sporadic. GPIO-Traces repeat in extracted csv after ominous 6.4s, which coincides with the ring-buffer-size.

packet_indicator.csv

block after 1724410961.0002775;0 exists twice

orgua commented 2 months ago

it should also highlevel report if buffer was used completely (only 16k entries / 100 ms)

orgua commented 2 months ago

attempted fix with multiple approaches in dev-branch:

PRU gets now partially zeroed buffer-segements
PRU had a race-condition with a loose mutex resulting in keeping old gpio-samples
python now warns on full gpio-buffer (as it can only hold 16k entries in 100 ms)
python now warns if first or last timestamp of gpio-buffer is out of scope of outer buffer-segment-period

orgua commented 2 months ago

tested with high gpio traffic and several minutes of sampling - no occurrences anymore - only warnings of full buffer keep appearing now (hint of data-loss)

orgua commented 1 month ago

new faulty behavior - one single recording has jump in timestamp

1725882187.2932773;1
1725882187.2942889;0
1725882187.295518;1
1725882187.2965307;0
1725882187.2977595;1
1725882187.2987711;0
1725882191.4949732;1
1725882187.3010132;0
1725882187.3022425;1
1725882187.3032541;0
1725882187.3044825;1
1725882187.3054957;0
1725882187.4210262;1