>驱动程序附带的标准示例，例如
获取波形vi挂断并锁定范围。
>例如
由于触发条件而导致的采集超时终止了vi，但使示波器处于无法访问的模式。
>>我想这对于Labview驱动程序开发人员来说更是一个问题，但是悬挂仪器并且不得不重新启动是很尴尬的...我同意范围不应该挂起，但是它可能不会挂起，只是不会对
前面板。
我唯一能想到的是，无论是意外还是故意锁定前面板，然后它们会出现某种故障，使其锁定。
没有查看发送到范围的命令，就没有办法知道。
许多开发环境都有一种设置命令日志的方法，因此您可以看到正在向设备发送的命令。
如果可能的话，我可能会建议启用它，或者单步执行代码以查看它正在做什么。
您还应该与NI人员保持联系。
>以此为例推翻
仪器前面的后退按钮非常有用。
如果这实际上是由SW关闭前面板引起的，那么具有覆盖将无法实现这一目的。
如果这是一个范围问题，那么你所谈论的将是某种NMI。
为了确保它始终有效，它可能必须具有与关闭和重新打开范围相同的效果。
人
以上来自于谷歌翻译
以下为原文
> The standard examples that come with the drivers such as e.g. the Acquire Waveform vi hang up and lockout the scope.
> E.g. a time out in the acquisition because of trigger conditions terminates the vi, but leaves the scope in an unaccessible mode.
>
> I guess this is more an issue for the Labview driver developers, but nevertheless hanging the instrument and having to reboot is awkward ...
I agree that scope should not hang, but then it may not be hung, just not reacting to the front panel. The only thing I can think of is that they are locking the front panel, either accidentally, or on purpose, then they have a failure of some sort, leaving it locked. Without looking at the commands that are sent to the scope, there's just no way to know.
Many development environments have a way to set up a command log, so you can see what commands are being sent to the device. I might suggest turning that on, if possible, or stepping through the code to see what it's doing. You should also be in touch with the NI people.
> Overruling this with e.g. the back-button on the front of the instrument could be very useful.
If this is really caused by the SW turning off the front panel, then having an override would defeat the purpose of doing that. If it's a scope problem, then what you are talking about would be some sort of NMI. To be sure it would always work, it would probably have to have the same effect as turning the scope off and back on.
Al
>驱动程序附带的标准示例，例如
获取波形vi挂断并锁定范围。
>例如
由于触发条件而导致的采集超时终止了vi，但使示波器处于无法访问的模式。
>>我想这对于Labview驱动程序开发人员来说更是一个问题，但是悬挂仪器并且不得不重新启动是很尴尬的...我同意范围不应该挂起，但是它可能不会挂起，只是不会对
前面板。
我唯一能想到的是，无论是意外还是故意锁定前面板，然后它们会出现某种故障，使其锁定。
没有查看发送到范围的命令，就没有办法知道。
许多开发环境都有一种设置命令日志的方法，因此您可以看到正在向设备发送的命令。
如果可能的话，我可能会建议启用它，或者单步执行代码以查看它正在做什么。
您还应该与NI人员保持联系。
>以此为例推翻
仪器前面的后退按钮非常有用。
如果这实际上是由SW关闭前面板引起的，那么具有覆盖将无法实现这一目的。
如果这是一个范围问题，那么你所谈论的将是某种NMI。
为了确保它始终有效，它可能必须具有与关闭和重新打开范围相同的效果。
人
以上来自于谷歌翻译
以下为原文
> The standard examples that come with the drivers such as e.g. the Acquire Waveform vi hang up and lockout the scope.
> E.g. a time out in the acquisition because of trigger conditions terminates the vi, but leaves the scope in an unaccessible mode.
>
> I guess this is more an issue for the Labview driver developers, but nevertheless hanging the instrument and having to reboot is awkward ...
I agree that scope should not hang, but then it may not be hung, just not reacting to the front panel. The only thing I can think of is that they are locking the front panel, either accidentally, or on purpose, then they have a failure of some sort, leaving it locked. Without looking at the commands that are sent to the scope, there's just no way to know.
Many development environments have a way to set up a command log, so you can see what commands are being sent to the device. I might suggest turning that on, if possible, or stepping through the code to see what it's doing. You should also be in touch with the NI people.
> Overruling this with e.g. the back-button on the front of the instrument could be very useful.
If this is really caused by the SW turning off the front panel, then having an override would defeat the purpose of doing that. If it's a scope problem, then what you are talking about would be some sort of NMI. To be sure it would always work, it would probably have to have the same effect as turning the scope off and back on.
Al
举报
