some confusion or WTF moment during an attempt to transfer data from ds1000z to my pc... i thought the label at the top is memory depth for 1 channel since enabling the other channel will half the memory, so i thought they must be shared (600 for one, 600 for the other), but it turned out to be even worst (at data dso->pc transfer at least)... rigol, cant you capture 600 pts per channel? so i can have 1.2Kpts memory for both ch1 and ch2 shared? maybe this involve hardware limitation but i'm not sure, i'm just confused with the top memory depth label... and with this shared-half-the-memory, i cant even get the whole screen capture for every channel at this particular setting (during stop mode, pictures below) ..
1 channel visible: 24Mpts capture per channel
2 channel visible: 6Mpts capture per channel (12Mpts / 2)
3 channel visible: 2Mpts capture per channel (6Mpts / 3)
4 channel visible: 1.5Mpts capture per channel (6Mpts / 4)
It seems that in your second attempt (with two channels enabled), you only transferred the first half of the trace on the scope screen to the PC. My guess is that the scope does indeed use 600 points per channel, as advertised. But it transfers both channels in an interleaved way. So you need to transfer 1200 data points to the PC and will have both traces complete.
Could you give that a try?
Nope, it's like how it's written in the manual:
1 channel visible: 24Mpts capture per channel
2 channel visible: 12Mpts capture per channel
3/4 channel(s) visible: 6Mpts capture per channel
1 channel visible: 24Mpts capture per channel
2 channel visible: 6Mpts capture per channel (12Mpts / 2)
3 channel visible: 2Mpts capture per channel (6Mpts / 3)
4 channel visible: 1.5Mpts capture per channel (6Mpts / 4)Nope, it's like how it's written in the manual:
1 channel visible: 24Mpts capture per channel
2 channel visible: 12Mpts capture per channel
3/4 channel(s) visible: 6Mpts capture per channel
Analog channel:
standard 12M pts (single-channel),
6M pts (dual-channel),
3M pts (3/4-channel);
optional 24 Mpts (single-channel),
12 Mpts(dual-channel),
6 Mpts (3/4-channel)
Nope, it's like how it's written in the manual:
1 channel visible: 24Mpts capture per channel
2 channel visible: 12Mpts capture per channel
3/4 channel(s) visible: 6Mpts capture per channelmaybe thats what happening in the scope. but what is transferred to pc is like my post. i'll try again better code to ensure it is not just an extrapolation... i hope you are right..
DSRemote? where can i get that? i followed visa programming guide, and that is what i got... i checked on the dso graticule, yes. internal of the dso, its working as your speced, but visa viScanf command sadly returns what is not wanted
that link is the source code, i need Windows executable that can be executed out of the box.
You don't need to be afraid for Linux. It installs as easy as windows and it comes for free.
:WAVeform:PREamble? has all of them combined with extra information as well.
which was meant as a collection of observations and suggestions
this thread is about bug wishlist right?
Yeah, but Rigol's bugs, not your programming bugs.
(Sorry, couldn't resist...)
and then it reveals another bug.
Also, most bugs can be reproduced, at least by a couple of other users with the same device.
But that doesn't explain the difference of 100nS.
But that doesn't explain the difference of 100nS.the 120nS is not fixed, its only specific to my earlier case. whatever the exact value is doesnt matter, "time shift" does exist. and the software bugs i reported above, happened during dso trigger state "STOP", either manually pressing "STOP" or "SINGLE" button on the scope, or automated trigger and stop from the SW, but as i said, its intermitent. during running mode and downloading 1200 pts per channel, the time shift is not visible though. so this is not "everytime" scenario...