# NoneType object in oscilloscope.get\_data

**URL:** <https://forum.liquidinstruments.com/t/nonetype-object-in-oscilloscope-get-data/992>\
**Category:** Software & APIs\
**Created:** [July 9, 2024, 1:01pm UTC](https://forum.liquidinstruments.com/t/nonetype-object-in-oscilloscope-get-data/992 "2024-07-09T13:01:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![HugoMarot](https://avatars.discourse-cdn.com/v4/letter/h/35a633/32.png) [@HugoMarot](https://forum.liquidinstruments.com/u/HugoMarot)\
**Post date:** [July 9, 2024, 1:01pm UTC](https://forum.liquidinstruments.com/t/nonetype-object-in-oscilloscope-get-data/992/1 "2024-07-09T13:01:15Z")

</div>

Hi,

I’m using the python API to get data from the oscilloscope function of a Moku Go. When I specify a number of measurments frame\_length that is greater than 4096, entries toward the end of both ‘ch1’ and ‘ch2’ register as NoneType Object. Changing the timout parameters (both the oscilloscope timout and the .session.read\_timeout) did not help. Using wait\_complete and wait\_reacquire also did not help. The number of list elements registering as NoneType object seems to change based on the timebase, but I have not found a particular timebase that aleviates the probleme completly. The problem is reproducible : for the same parameters, the same list elements register as NoneType objects.  
I include here a minimal working exemple :

from moku.instruments import Oscilloscope

osc = Oscilloscope(‘MokuGoIPadress’, force\_connect=True)

osc.set\_timebase(0,0.5,8192,strict=True)  
test = osc.get\_data()

---

<div class="post-metadata">

**Author:** ![dhwielens](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.liquidinstruments.com/dhwielens/32/248_2.png) [@dhwielens](https://forum.liquidinstruments.com/u/dhwielens)\
**Post date:** [July 11, 2024, 8:15am UTC](https://forum.liquidinstruments.com/t/nonetype-object-in-oscilloscope-get-data/992/2 "2024-07-11T08:15:33Z")

</div>

Hi Hugo,

This seems to be the same question as I posed before, see the thread here: [Bug: oscilloscope on Moku:Go returns incomplete data arrays with trailing NoneTypes for frame\_lenghts \> 2048](https://forum.liquidinstruments.com/t/bug-oscilloscope-on-moku-go-returns-incomplete-data-arrays-with-trailing-nonetypes-for-frame-lenghts-2048/884)

---

<div class="post-metadata">

**Author:** ![nadia](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.liquidinstruments.com/nadia/32/315_2.png) [@nadia](https://forum.liquidinstruments.com/u/nadia)\
**Post date:** [July 11, 2024, 11:58pm UTC](https://forum.liquidinstruments.com/t/nonetype-object-in-oscilloscope-get-data/992/3 "2024-07-11T23:58:51Z")

</div>

Hello @HugoMarot and @dhwielens,

For larger frame lengths and spans, there are cases where you still see None even with `wait_complete=True`, but not for the timebase you requested. If you have requested `t1, t2`, get\_data will give you data for the span `t1, t1+x`, and the NoneTypes will be present only for this additional x and not for t1 to t2. For example, the data will look like this:

```auto
'time':[t1 ... t2, t2+n, t2+n*2 ... t2+x]
'data':[float ... float, None, None ... None]

```