在示波器上怎么捕获和保存多个通道

问：当捕获每个通道时，它们是否存储在单独的缓冲区中？
你提到只有一个缓冲区。
我想能够打电话：WAVeform：数据？
并一次检索3个通道的所有数据。
A - 每个通道有一个缓冲区。
范围触发后，您需要一个如下序列：WAV：SOUR CHAN1：WAV：DATA？
：WAV：SOUR CHAN2：WAV：DATA？
：WAV：SOUR CHAN3：WAV：DATA？
问：我们正在运行测试，以找出从示波器远程检索波形数据的最佳和最快的方法。
通过使用在作用域上运行的python脚本或通过远程发送命令。
A - 是否要将数据保存到文件中或从范围缓冲区中获取数据以进行处理？
每个命令都非常不同。
假设GBit LAN和LAN上相对较少的其他流量将以大致相同的速度运行，在作用域上运行Python或远程运行它。
它们都在示波器上通过相同的“插座”。
Q - 如果我通过屏幕界面选择“触发多用途”和“保存所有波形”，则示波器将每个通道数据串联存储在.H5等文件中。
范围到底在做什么？
使用时似乎没有开销：DIGitize。
然后我们通过python脚本将它们传输到目的地。
A - 同样，您是要将数据保存在文件中并传输这些文件，还是仅获取数据进行处理并保存？
从示波器中吸取数据比保存到文件和传输文件更快。
传输的文件将大于其中的原始数据。
转换范围上的数据相对较慢。
HDF5是最慢的。
问：在您看来，通过远程发送命令而不是使用脚本来获取数据是否更快。
当我通过屏幕界面选择“触发多用途”和“保存所有波形”时，我可以发送哪些命令以实现示波器执行的相同操作？
谢谢A - 远程运行示波器并在捕获数据时传输数据会更快，然后要求示波器将其全部保存，然后再转移。
文件转换和节省时间会杀了你...... Al



     以下为原文

  Q - When each channel is captured, are they stored in separate buffers tho? You mentioned that there is only one buffer. I would like to be able to call :WAVeform:Data? and retrieve all the data for the 3 channels at once.

A - There is one buffer per channel. Once the scope has triggered, you need a sequence like:
:WAV:SOUR CHAN1
:WAV:DATA?
:WAV:SOUR CHAN2
:WAV:DATA?
:WAV:SOUR CHAN3
:WAV:DATA?

Q - We are running tests to figure out the best and fastest way to retrieve waveform data from the scope remotely. Either by using a python script running on the scope or by sending commands remotely.
A - Do you want to save the data into files or get the data from the scope buffer for processing? The commands for each are very different. Running Python on the scope, or running it remotely, assuming GBit LAN and relatively little other traffic on the LAN will run at about the same speed. They both go through the same 'socket' on the scope.

Q - If I select "Multipurpose on trigger" and "save all waveforms" via the screen interface, the scope stores each channel data in series in a file such as .H5. What exactly is the scope doing here? There doesn't seem to be the overhead that there is when using :DIGitize. We then transfer them files via a python script to the destination.

A - Again, do you want to save the data in files and transfer those files, or just get the data for processing and save then? Sucking the data from the scope will be faster than saving into files and transferring the files. The transferred files will be larger than the raw data that is in them. Converting the data on the scope is relatively slow. HDF5 is the slowest.

Q - In you opinion, should it be faster acquiring data by sending commands remotely instead of using the script. Which commands can I send in order to implement the same action that the scope is performing when I select "Multipurpose on trigger" and "save all waveforms" via the screen interface? Thanks

A - Running the scope remotely and transferring the data as it is captured will be faster then asking the scope to save it all, then transferring it later. The file conversion and save time will kill you...

Al

我只想尽快从范围中获取数据。
目前每通道/信号250KB。
你告诉我，最快的方法是使用：DIG，然后是WAVEFORM：DATA？。
我不同意，因为在这种情况下触发器达到10 Hz时我们会丢失波形。
但是，如果我将范围保存为文件（在这种情况下为HDF5）并稍后传输，我们就不会丢失任何数据，即使触发器为10 Hz !!!!
我还认为这种HDF5格式是最快的，因为它是最小的可用文件格式，只包含带有一些标题信息的电压数据。
我在每次触发后尝试了以下操作，并且它太慢了，我们正在丢失数据:: WAV：SOUR CHAN1：WAV：DATA？
：WAV：SOUR CHAN2：WAV：DATA？
：WAV：SOUR CHAN3：WAV：DATA？
现在有趣的是，为什么在范围创建和保存文件时，它比尝试直接从范围缓冲区提取数据要快得多？
我们使用专用的GBit LAN，因此网络速度不是问题。
这个：DIGitize命令需要太长时间。
是否足以使用以下方式轮询寄存器：ADER？
查看缓冲区何时已满，然后使用：WAVEFORM：DATA？进行传输。
通过这样做，它似乎更快，我没有丢失任何数据。
这是在使用“多用途触发器”保存文件时，范围在幕后做的吗？
此外，是否有命令将每个通道数据本地存储在示波器上，例如在每次触发后？
看起来只有4个波形存储器，但是我可以使用更多的存储器吗？
非常感谢



     以下为原文

  I just want to suck the data from the scope as fast as possible. 250KB per channel/signal at present.  You told me the fastest way to do this was by using :DIG and then WAVEFORM:DATA?. I disagree, because we are loosing waveforms when the trigger reaches 10 Hz in that case. 

If I however get the scope to save the data as files (HDF5 in this case) and transfer later , we are not loosing any data, even when the trigger is at 10 Hz!!!!. I thought also that this HDF5 format would be the fastest as it is the smallest of the available file formats containing only the voltage data with some header information. 

I have tried the following after every trigger, and again it is too slow and we are loosing data:
:WAV:SOUR CHAN1
:WAV:DATA?
:WAV:SOUR CHAN2
:WAV:DATA?
:WAV:SOUR CHAN3
:WAV:DATA?

The interesting thing now is why is it when the scope is creating and saving the files that it is much faster than trying to pull the data directly from the scope buffers? We are using a dedicated GBit LAN so network speed is not an issue. 

This :DIGitize command is what takes too long. Is it suffice to poll the register using :ADER? to see when the buffer(s) is full and then transfer using :WAVEFORM:DATA?. By doing this, It seems much faster and I am not loosing any data. Is this simply what the scope is doing behind the scenes when it is saving the files with "multipurpose on trigger" ? 

Also, are there commands to store each channel data locally on the scope for example after every trigger? There are only 4 waveform memories it seems but is there more memory I can use? Many thanks

您显然找到了一个适合您的解决方案，并且不太喜欢我的答案，所以请注意......当然，您无法保证您的解决方案能够提供相同级别的性能，或者根本无法工作
，在加载范围SW的新版本之后的某个未来日期，或在不同的范围模型上。
问 - 此外，是否有命令将每个通道数据本地存储在示波器上，例如在每次触发后？
A - 你在“本地”是什么意思？
下面讨论了4个波形存储器，并且有文件。
还有分段模式，在前一个线程中讨论过。
问 - 看起来只有4个波形存储器，但是我可以使用更多的存储器吗？
答 - 我不明白这个问题。
4“波形存储器”与波形缓冲器无关，它们用于将文件数据加载到数学范围内或与实时数据进行比较。
人



     以下为原文

  You have apparently found a solution that works for you, and don't like my answers much, so have at it... There is, of course, no guarantee that your solution will provide the same level of performance, or work at all, at some future date after a new version of scope SW has been loaded, or on a different model of scope.

Q - Also, are there commands to store each channel data locally on the scope for example after every trigger?

A - What do you mean "locally"? There are the 4 waveform memories, discussed below, and there are files. There is also segmented mode, discussed in a previous thread.

Q - There are only 4 waveform memories it seems but is there more memory I can use?

A - I don't understand this question. The 4 "waveform memories" have nothing to do with the waveform buffers, They are used for loading file data back into the scope for math or comparison with live data.

Al

我不是说我不喜欢你的答案。
我还不清楚为什么与尝试直接从缓冲区远程获取数据相比，范围制作文件并实时存储它们的速度更快。
这没有意义。
我想在保存文件时确切了解范围内的范围，我可以尝试在我的代码中实现相同的功能吗？



     以下为原文

  I am not saying that I don't like you answers. I am still unclear as to why it is faster for the scope to make the files and store them in real time in comparison to trying to acquire remotely the data directly from the buffers. It doesn't make sense. I would like to understand exactly what is the scope doing under the hood when it is saving the files and I can try and implement the same in my code?

当您使用“多用途”之类的东西来捕获和存储数据时，您正在使用写入SW的内置宏。
它不必解析任何命令，与LAN进行任何交互或其他任何操作。
数据被捕获并传输到磁盘，就是这样。
如果这就是你所需要的，你应该利用它。
通常，可以编写一个小的，定义明确的任务，以便比需要与例如用户交互的更一般的任务更快。
我与之交谈的大多数客户都希望以最快的方式获得深度跟踪，10 MPoints或更多，超出处理或存储范围。
他们无法冒险填充范围内的磁盘，他们可能希望动态地进行一些处理或数据缩减。
人



     以下为原文

  When you use something like "Multipurpose" to capture and store data, you are using a built-in macro that was written into the SW. It doesn't have to parse any commands, do any interaction with the LAN, or anything else. Data is captured and transferred to the disk, that's it. If that's all you need, you should take advantage of it. In general, a small, well-defined task can be written to be faster than a more general task that requires interaction with, for instance, a user.

Most customers that I talk to are interested in the fastest way to get deep traces, 10 MPoints or more, off the scope for processing or storage. They can't risk filling up the disk in the scope, and they may want to do some processing, or data reduction, on the fly.

Al

好的，谢谢你的帮助。



     以下为原文

  Ok, thanks for your help.