06-06-2023, 10:50 AM
I have to test it later as I do not have the puck.js at hand right now, but it I think we overlooked that the timestamps from the puck.js are based on its own internal clock. Phyphox usually uses timestamps that "pause" when phyphox is paused, i.e. when you stop at 5 seconds and continue your measurement a minute later, the next timestamp will be something like 5.1 seconds, but from the puck.js we would get 65 seconds as the next timetamp.
This should be an easy fix as phyhphox just needs to be told to expect this. I have attached a version that should hopefully not exhibit this problem. (Untested, will test it later unless you beat me to it.)
This should be an easy fix as phyhphox just needs to be told to expect this. I have attached a version that should hopefully not exhibit this problem. (Untested, will test it later unless you beat me to it.)