@noopwafel have you managed to initialize it following the "OWON Oscilloscope PC Guidance Manual" ?
I'm trying to write a C client with libusb for measurements, but after finding+opening the device, the device reply is the same whatever command I send (START, STARTBIN ecc). if I try to bulkread the data, it gives usb timeout.
Quote from: nzasch on Today at 01:26:44 am@noopwafel have you managed to initialize it following the "OWON Oscilloscope PC Guidance Manual" ?
No, the 'tiny' scopes don't seem to support anything that complicated, they just provide chunks of raw data from the FPGA and you need to do quite a lot of initialization/configuration (including uploading the FPGA bitstream and downloading the calibration data - they don't even handle the calibration internally). They will reset themselves (which I guess might be responsible for disconnections) if the host doesn't send a command for more than a few seconds, or the communication desynchronizes. My VDS1022I will keep capturing for quite a long time (via USB2) via my sigrok driver without any apparent problems, but I didn't try the Windows software for more than a few minutes (just enough to get a packet capture).
Had anyone get the VDS 1022I worked on Linux? I've use Ubuntu 18.04.1 and had tried https://github.com/tinwhisker/Owon-VDS1022 and it doesn't work after following the instructions. My lsusb shows my scope as a Owon PDS6062T.
Had anyone get the VDS 1022I worked on Linux? I've use Ubuntu 18.04.1 and had tried https://github.com/tinwhisker/Owon-VDS1022 and it doesn't work after following the instructions. My lsusb shows my scope as a Owon PDS6062T.
FYI, the "PDS6062T" listing is just part of the lookup table in the Linux kernel, because it shares the same PID/VID. AFAIK, that's all it shares though.
We could possibly email the usb id's maintainer to make it generic? PDS6062T Oscilloscope -> OWON USB Oscilloscope
http://www.linux-usb.org/usb.ids
GreySpammer-Tir had success/progress I believe in getting the USB driver working:
https://github.com/tinwhisker/Owon-VDS1022/issues/6#issuecomment-433426973
I'm yet to find time to revisit the Linux package, but I'll probably sort a script over the holiday period.
Just picked up a VDS1022I to live in my laptop bag for all the times when "I didn't think I'd need to bring a scope".
Kudos to OWON for making a low-cost USB box called "Oscilloscope" which appears to actually have an oscilloscope in it! I've tried a few others and they have been universally terrible, appearing to be nothing more than USB sampling/streaming devices which "don't quite" send a consistent stream of samples to bad PC software.
This one seems much better (ie: It actually works!).
Have seen a few glitches in the software, most of which are livable, however I've encountered one thing that as really annoying, and I'm wondering if anyone else has encountered this and/or if workarounds are known.
Problem is when I want to "zoom in" on a captured waveform .. With the scope stopped, I can change the horizontal timebase and pan around an expanded image ... SOMETIMES ... certain captures just don't let me do this. For example, if I capture at 100us/div, I can "zoom" to 10us/div (10 times). But I can't capture at 1000us/div (1ms/div) and zoom to 100us/div ... just no change in the displayed waveform.
Second part of the problem is when I want to proceed and perform another capture after stopping and zooming. Upon hitting "start", the software freezes, and does one of:
- Hang forever
- Long delay (often minutes) then "just terminate"
- Long delay (as above) then scope disconnects and reconnects and capture proceeds
My scope came with software version 1.0.29 .. I've tried the latest (1.0.30) and several previous releases all with the same results.
Going back as far as 1.0.23, I get different (and better) results:
- Scope almost always lets me zoom, no matter what the capture rate.
- Still has trouble starting another capture, but device disconnects/reconnects within a few seconds and capture proceeds.
So, 1.0.23 is workable, but I wonder what "fixes" I'm giving up...
Has anyone else encountered this? Any workarounds?
Is there a better way to zoom in on a captured waveform that I just haven't found?
It would have been really nice if they made the "zoom" function in the horizontal menu work as a zoom/review when the scope is stopped instead of just telling you to screw off and come back when the scope is running.
Regards,
Dave
I've found that the latest VDS1022 firmware seems do not allow incremental transfer of the new data in slow sampling rate mode. It just continuously write on the 5K data buffer in loop without any indication of the current cursor position . This make impossible to do continuous data recording and if so it's a bit a pity for so well equipped hardware.
Any hint about this?
By the way I'm implementing the support for the VDS1022 under Android. I'm wondering if any wish to do some test , I may provide some promo codes to the first who ask @ support[at]martinloren.com. It requires USB OTG and maybe some powered USB HUB if phone current from USB is not enough .
There must surely be a mechanism at work otherwise there would be no way of syncing correctly to the display.
Dave, thanks for coming back and reporting you impressions, glad it lived up to expectations as there is still precious little review info out there.
Looking back at the notes I made when I linked my previous versions, I noted that 1.0.23 was stable for me, later versions have seemed to concentrate on breaking an then fixing features. I don't remember seeing any new features on later versions. My guess is that the later releases have been more to do with achieving some level of common code base with the newer, higher bandwidth models, I suspect that the VDS1022 was 'complete' by 1.0.23. I don't know anything else for sure though, and in the absence of any release notes... The only way to know for sure is to dig into the code.
I haven't experienced the zoom followed by hang on capture issued - not something I've done to be honest. My suspicion is that if you're getting into a situation where timebase changes and the stored waveform doesn't, then the scope and s/w are likely to end up with different understandings of what the timebase actually is! potentially causing the hang. Have you tried restoring the timebase setting to what it was for the previous capture?
I haven't done much with the versions since 1.0.23 apart from the 'breakages' I mentioned (the reason for archiving them!). Not because I've outgrown it - I just haven't spent much time in my lab.
I've found that the latest VDS1022 firmware seems do not allow incremental transfer of the new data in slow sampling rate mode. It just continuously write on the 5K data buffer in loop without any indication of the current cursor position . This make impossible to do continuous data recording and if so it's a bit a pity for so well equipped hardware.
Any hint about this?
By the way I'm implementing the support for the VDS1022 under Android. I'm wondering if any wish to do some test , I may provide some promo codes to the first who ask @ support[at]martinloren.com. It requires USB OTG and maybe some powered USB HUB if phone current from USB is not enough .
Dave, thanks for coming back and reporting you impressions, glad it lived up to expectations as there is still precious little review info out there.
Looking back at the notes I made when I linked my previous versions, I noted that 1.0.23 was stable for me, later versions have seemed to concentrate on breaking an then fixing features. I don't remember seeing any new features on later versions. My guess is that the later releases have been more to do with achieving some level of common code base with the newer, higher bandwidth models, I suspect that the VDS1022 was 'complete' by 1.0.23. I don't know anything else for sure though, and in the absence of any release notes... The only way to know for sure is to dig into the code.
I haven't experienced the zoom followed by hang on capture issued - not something I've done to be honest. My suspicion is that if you're getting into a situation where timebase changes and the stored waveform doesn't, then the scope and s/w are likely to end up with different understandings of what the timebase actually is! potentially causing the hang. Have you tried restoring the timebase setting to what it was for the previous capture?
I haven't done much with the versions since 1.0.23 apart from the 'breakages' I mentioned (the reason for archiving them!). Not because I've outgrown it - I just haven't spent much time in my lab.
Thanks for the info. So far I've not noticed anything new past 1.0.23 either.
I have tried setting the timebase back to the original capture before proceeding, and it still hangs. Very odd - even 5k points is worth being able to zoom in (my TDS210 has only 2.5k and I zoom in with it all the time).
I'd be curious to know if you can reproduce the issue - just do a capture, stop the scope, adjust horizontal to "zoom in", then just start the scope again. For me it hangs very often. 1.0.23 recovers quite quickly, but you will still see a reconnecting message ... just would like to confirm it's not something "special" about my scope/setup.
Dave
Dave, thanks for coming back and reporting you impressions, glad it lived up to expectations as there is still precious little review info out there.
Looking back at the notes I made when I linked my previous versions, I noted that 1.0.23 was stable for me, later versions have seemed to concentrate on breaking an then fixing features. I don't remember seeing any new features on later versions. My guess is that the later releases have been more to do with achieving some level of common code base with the newer, higher bandwidth models, I suspect that the VDS1022 was 'complete' by 1.0.23. I don't know anything else for sure though, and in the absence of any release notes... The only way to know for sure is to dig into the code.
I haven't experienced the zoom followed by hang on capture issued - not something I've done to be honest. My suspicion is that if you're getting into a situation where timebase changes and the stored waveform doesn't, then the scope and s/w are likely to end up with different understandings of what the timebase actually is! potentially causing the hang. Have you tried restoring the timebase setting to what it was for the previous capture?
I haven't done much with the versions since 1.0.23 apart from the 'breakages' I mentioned (the reason for archiving them!). Not because I've outgrown it - I just haven't spent much time in my lab.
Thanks for the info. So far I've not noticed anything new past 1.0.23 either.
I have tried setting the timebase back to the original capture before proceeding, and it still hangs. Very odd - even 5k points is worth being able to zoom in (my TDS210 has only 2.5k and I zoom in with it all the time).
I'd be curious to know if you can reproduce the issue - just do a capture, stop the scope, adjust horizontal to "zoom in", then just start the scope again. For me it hangs very often. 1.0.23 recovers quite quickly, but you will still see a reconnecting message ... just would like to confirm it's not something "special" about my scope/setup.
Dave
Sorry for my lethargy last night, I'm fighting a bit of an infection.
Odd, I had installed 1.0.30 when I saw it, but hadn't got as far as plugging in the VDS. I just tried it (1kHz cal, Ch1) and came up with some strange results. It auto triggered ok, but when I hit stop and then clicked on the timebase it crashed immediately and repeatably. For some reason single trace was greyed out too.
I uninstalled 1.0.30 and installed 1.0.29, tried exactly the same and it worked perfectly. Manual or single trigger, whatever timebase I zoomed to after stopping and restarting. Never flinched.
Thinking it was another introduced 'breakage' I was set to confirming it by re-installing 1.0.30 (uninstalling 1.0.29 first). To my surprise if now finding that 1.0.30 works perfectly too. I've tried it many times in succession with across a silly range of zooms / unzooms and it hasn't missed a beat.
The only differences I can think of are..
1. I did the first 1.0.30 installation 'cold', thinking I must get around to plugging in and checking that (in fact I had to use the install F/W option before it would see the VDS). I think it may actually have been a 'clean install' as I've only recently brought this laptop up. This time, I did all the uninstalls / reinstalls with the VDS still plugged in.
2. The VDS had a few minutes to warm up before I uninstalled 1.0.29
3. 1.0.29 might have left something in the registry that 1.0.30 needs?
This is all on Win7 SP1 64bit pro by the way.
You might want to check for USB supply voltage, but I'm pushing my luck with a 3m USB cable at the moment so that sounds unlikely. Maybe try a different port though.
Sorry I couldn't give you a definitive they broke it in Version xxxx.
P.S. Just to be clear, I haven't seen any reconnect message - I think you may indeed have a setup issue.