Hi @sconyers - I just tried to duplicate this by editing %LOCALAPPDATA%\joulescope\config1joulescope_config.json to 10 Hz downsampling and 1 day buffer duration. I confirm that I see lots of these errors:
Exception ignored in: 'pyjoulescope_driver.binding._on_cmd_publish2_cbk'
Traceback (most recent call last):
File "C:\repos\Jetperch\pyjoulescope\joulescope\v1\device.py", line 431, in _on_stream
b.insert(topic, value)
File "C:\repos\Jetperch\pyjoulescope\joulescope\v1\stream_buffer.py", line 228, in insert
b.add(value['sample_id'], value['data'],
File "C:\repos\Jetperch\pyjoulescope\joulescope\v1\sample_buffer.py", line 162, in add
self._buffer[ptr1:] = data[:k]
ValueError: could not broadcast input array from shape (0,) into shape (863417,)
What this error says is that no new data is available, which is then not handled well by the UI. I tried out a bunch of different settings, and it looks like the lowest output frequency that is currently well-supported by the UI with the JS220 is 5 kHz.
We are working to move downsampling onboard the JS220 and improve the Joulescope UI buffering, so what you are seeing is a temporary implementation. For the meantime, can you use 5 kHz or greater sampling rates? If you want longer durations (days, weeks, months), we recommend that you use the statistics (reductions) output, perhaps using the downsample_logging.py script.
Does this work for you?