# Very long headless recordings (weeks)

**URL:** <https://forum.qoitech.com/t/very-long-headless-recordings-weeks/436>\
**Category:** Support\
**Created:** [April 13, 2022, 8:06am UTC](https://forum.qoitech.com/t/very-long-headless-recordings-weeks/436 "2022-04-13T08:06:07Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![neilmacmullen](https://avatars.discourse-cdn.com/v4/letter/n/a88e57/32.png) [@neilmacmullen](https://forum.qoitech.com/u/neilmacmullen)\
**Post date:** [April 13, 2022, 8:06am UTC](https://forum.qoitech.com/t/very-long-headless-recordings-weeks/436/1 "2022-04-13T08:06:07Z")

</div>

I asked something similar a couple of years back and at the time I don’t think it was possible but hopefully things have moved on since…

The scenario is that we would like to use the Otii in automated testing. One test involves monitoring our device over several weeks to ensure that overall power consumption really is as expected (the device spends extended periods in very low power mode and periodically wakes up to perform tasks).

What we’d need to do to support this is use the C# TCP client library to start a recording then stream the latest power measurements periodically (every 60 seconds should be fine). We can decimate the data client-side to manage file-size.

It looks like the server API has various ways of getting recordings but it’s not clear to me if there is a way to pull off streamed data in a way that avoids having to interrupt the recording or avoids the otii eventually runng out of internal storage.

Is it possible to do what we want?

_Edit_ Looks like there was a [request about this](https://forum.qoitech.com/t/data-streaming/289) back in 2019 where the answer was “no”.

Thanks,  
Neil

---

<div class="post-metadata">

**Author:** ![neilmacmullen](https://avatars.discourse-cdn.com/v4/letter/n/a88e57/32.png) [@neilmacmullen](https://forum.qoitech.com/u/neilmacmullen)\
**Post date:** [April 27, 2022, 10:12am UTC](https://forum.qoitech.com/t/very-long-headless-recordings-weeks/436/2 "2022-04-27T10:12:05Z")

</div>

Ping ?

---

<div class="post-metadata">

**Author:** ![bjorn.rosqvist](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.qoitech.com/bjorn.rosqvist/32/238_2.png) [@bjorn.rosqvist](https://forum.qoitech.com/u/bjorn.rosqvist)\
**Post date:** [April 27, 2022, 11:57am UTC](https://forum.qoitech.com/t/very-long-headless-recordings-weeks/436/3 "2022-04-27T11:57:10Z")

</div>

Hi Neil,

To be able to do this, you need to do as in the post you found.  
As mentioned, the drawback is that you will loose some 10s of ms of data when you start a new recording.  
This will be improved in the major release we are working on.

Best regards,  
Björn

---

<div class="post-metadata">

**Author:** ![neilmacmullen](https://avatars.discourse-cdn.com/v4/letter/n/a88e57/32.png) [@neilmacmullen](https://forum.qoitech.com/u/neilmacmullen)\
**Post date:** [May 10, 2022, 9:55am UTC](https://forum.qoitech.com/t/very-long-headless-recordings-weeks/436/4 "2022-05-10T09:55:44Z")

</div>

Bjorn, thanks for the info. The obvious follow-up question is when the next major release is due? 😉

In the meantime, can you advise on a “sensible” record/download frequency? Obviously if download very frequently (every second) we’ll miss a lot of samples but conversely if we download infrequently (once per day), we’ll have very long gaps because the download itself may take a considerable time.

---

<div class="post-metadata">

**Author:** ![bjorn.rosqvist](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.qoitech.com/bjorn.rosqvist/32/238_2.png) [@bjorn.rosqvist](https://forum.qoitech.com/u/bjorn.rosqvist)\
**Post date:** [May 20, 2022, 8:52am UTC](https://forum.qoitech.com/t/very-long-headless-recordings-weeks/436/5 "2022-05-20T08:52:27Z")

</div>

Hi,

We are soon to start a beta test of the major release, if you are interested in participating just create a case in our case system ([Qoitech](https://www.qoitech.com/cases)) and describe your user case.  
We will then get back to you with more details when we are ready to start.

Regarding sensible start/stop frequency, I am sorry I have no recommendation here since this depends a lot on your device cycle time, your computer disc performance, operating system etc, so I cannot recommend anything but ask you to test yourself, sorry for this.

Best regards,  
Björn