Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Data is not being collected from the Movesense device in the CATCH study #442

Closed
bardram opened this issue Nov 7, 2024 · 1 comment · Fixed by #446
Closed

Data is not being collected from the Movesense device in the CATCH study #442

bardram opened this issue Nov 7, 2024 · 1 comment · Fixed by #446
Assignees
Labels
bug Something isn't working

Comments

@bardram
Copy link
Contributor

bardram commented Nov 7, 2024

The sensing is not restarted when connecting the device. Here is the log:

[log] New connected device with serial: 233830000816
[log] [CAMS DEBUG] MovesenseDeviceManager - setting device status: connected
[log] [CAMS DEBUG] MovesenseDeviceManager - Successfully connected.
[log] [CAMS DEBUG] MovesenseDeviceManager - Getting device info.
[log] [CAMS DEBUG] MovesenseDeviceManager - Setting up battery monitoring.
[log] [CAMS INFO] MovesenseDeviceManager - Restarting sampling...
[log] [CAMS INFO] Restarting TaskControlExecutor [729843102] (started)
[log] [CAMS INFO] Restarting NoOpTriggerExecutor [740692428] (started)
[log] [CAMS INFO] Restarting TaskControlExecutor [552593698] (started)
[log] [CAMS INFO] Restarting ImmediateTriggerExecutor [680206657] (started)
[log] [CAMS INFO] Starting BackgroundTaskExecutor [602670991] (started)
[log] [CAMS WARNING] Trying to start a BackgroundTaskExecutor in a state where this cannot be done - state: 'started'. Ignoring this.

which shows that the BackgroundTaskExecutor isn't started, since it is already in a started state.

@bardram bardram self-assigned this Nov 7, 2024
@bardram bardram added the bug Something isn't working label Nov 7, 2024
@bardram
Copy link
Contributor Author

bardram commented Nov 7, 2024

Similar to #408

bardram added a commit that referenced this issue Nov 8, 2024
bardram added a commit that referenced this issue Nov 10, 2024
* fix of #442
* fix of #444
* fix of #445
@bardram bardram linked a pull request Nov 10, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant