你好，1。很遗憾，我们没有这项服务。
最好的办法是编写一个异常处理程序来捕获错误并重新建立连接。
2.重新建立连接时，它将使用不同的端口。
这就是导致你看到错误的原因。
另一个选择可能是使用看门狗定时器。
我写了一篇关于此的博客文章：[http://powersupply.blogs.keysight.com/2015/04/lets-see-watchdog-timer-in-action.html]请注意，GPIB和USB将从亏损中恢复
无需重新建立连接。
以上来自于谷歌翻译
以下为原文
Hello,
1. Unfortunately, we do not have this service. The best thing to do would be to write an exception handler to catch the error and re-establish a connection.
2. When you re-establish a connection, it is going to use a different port. That is what causes the errors that you see.
Another option may be use a watchdog timer. I wrote a blog post about this:
[http://powersupply.blogs.keysight.com/2015/04/lets-see-watchdog-timer-in-action.html]
Please note that GPIB and USB will recover from a loss without you having to re-establish a connection.
你好，1。很遗憾，我们没有这项服务。
最好的办法是编写一个异常处理程序来捕获错误并重新建立连接。
2.重新建立连接时，它将使用不同的端口。
这就是导致你看到错误的原因。
另一个选择可能是使用看门狗定时器。
我写了一篇关于此的博客文章：[http://powersupply.blogs.keysight.com/2015/04/lets-see-watchdog-timer-in-action.html]请注意，GPIB和USB将从亏损中恢复
无需重新建立连接。
以上来自于谷歌翻译
以下为原文
Hello,
1. Unfortunately, we do not have this service. The best thing to do would be to write an exception handler to catch the error and re-establish a connection.
2. When you re-establish a connection, it is going to use a different port. That is what causes the errors that you see.
Another option may be use a watchdog timer. I wrote a blog post about this:
[http://powersupply.blogs.keysight.com/2015/04/lets-see-watchdog-timer-in-action.html]
Please note that GPIB and USB will recover from a loss without you having to re-establish a connection.
举报
