我弄清楚发生了什么。
这是一个奇怪的案例，几乎是一个错误。
要进行测量，它实际上会清除当前测量值并等待下一次触发发生，但由于PC上的当前进程正在等待该响应，因此它无法触发将触发返回测量的范围的事件。
如果查询只询问当前配置的测量延迟是什么，而不是永远停止，那将会好得多。
干杯，
以上来自于谷歌翻译
以下为原文
I figured out what's happening.
It's one of those strange cases that's almost a bug. To do the measurement it actually clears the current measurement and waits for the next trigger to occur, but because the current process on the PC is waiting for that response, it cannot trigger the event that would trigger the scope that would return the measurement. It would be much better if the query just asked the currently configured measurement what the delay is, instead of just stalling forever.
Cheers,
我弄清楚发生了什么。
这是一个奇怪的案例，几乎是一个错误。
要进行测量，它实际上会清除当前测量值并等待下一次触发发生，但由于PC上的当前进程正在等待该响应，因此它无法触发将触发返回测量的范围的事件。
如果查询只询问当前配置的测量延迟是什么，而不是永远停止，那将会好得多。
干杯，
以上来自于谷歌翻译
以下为原文
I figured out what's happening.
It's one of those strange cases that's almost a bug. To do the measurement it actually clears the current measurement and waits for the next trigger to occur, but because the current process on the PC is waiting for that response, it cannot trigger the event that would trigger the scope that would return the measurement. It would be much better if the query just asked the currently configured measurement what the delay is, instead of just stalling forever.
Cheers,
举报
