# Issue saving high res buffer with Oscilloscope **URL:** \ **Category:** Support & Troubleshooting\ **Created:** [October 11, 2022, 2:32pm UTC](https://forum.liquidinstruments.com/t/issue-saving-high-res-buffer-with-oscilloscope/587 "2022-10-11T14:32:49Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![slw](https://avatars.discourse-cdn.com/v4/letter/s/f4b2a3/32.png) [@slw](https://forum.liquidinstruments.com/u/slw)\ **Post date:** [October 11, 2022, 2:51pm UTC](https://forum.liquidinstruments.com/t/issue-saving-high-res-buffer-with-oscilloscope/587/2 "2022-10-11T14:51:07Z")
Looking around the forum a little bit, this could be a related issue to this one from about 8 months ago: > [@Python API Moku Pro Oscilloscope Single Trigger & wait\_reaquire Inconsistency](https://forum.liquidinstruments.com/t/python-api-moku-pro-oscilloscope-single-trigger-wait-reaquire-inconsistency/501): > > Hi guys. Just to start, as I know it is important, I am using a moku pro with firmware version 555 and the python moku library version 2.2. I believe these are the most up to date at the time of writing this? (I do not see any indication for a firmware update on the desktop app, and I am not sure there is any place to manually check for those on it) To act as a test, I was utilizing the following code: osc = Oscilloscope('10.220.15.164', force\_connect=True) osc.set\_timebase(-100e-6, 500e-6) o… Have there been any updates on that issue? For now we will use the datalogger to take continuous data and trigger offline. --- _[View the full topic](https://forum.liquidinstruments.com/t/issue-saving-high-res-buffer-with-oscilloscope/587)._