81150A pulsar.exe崩溃

我们将两个81150A集成到一个长期自动化测试系统中，并且每个月左右测量被其中一个“崩溃”中断。我相信确切的措辞是：“Pulsar.exe中发生了本机异常。”
其中一个是触发另一个，它们由PC定期重新配置。
在某些循环中，“主”81150正在接收软件触发器，其间隔为几秒，但通常根据测试周期以突发模式操作半分钟到15分钟。
我们现在已经看到两个发电机都出错了。
最初我们认为这是一个I / O问题（使用labview来控制它们）并且已经使用USB，GPIB和LAN全部用于控制/触发并且现在全部用它们发出错误。因为我们不想太多停机时间
（当我们重新启动实验时发生了崩溃）我们没有更新固件并且是2.04或2.05，而我认为最新版本是2.09。
我们没有更新固件的另一个原因是建议不要降级，一些团队成员担心更新会引入其他问题而我们无法回复。我的主要问题是：是否曾见过此行为
，是否是为解决此问题而专门设计的最后几个固件更新？
如果是这种情况，那么我可以自信地告诉我的同事我们应该在下次停机时更新固件。



     以下为原文

  We have two 81150A's integrated into a long-term automated test system, and every month or so the measurement is interrupted by one of them 'crashing'.

I believe the exact wording is: "A native exception has occurred in Pulsar.exe."

One of them is triggering the other, and they are reconfigured periodically by a PC.  There are certain cycles in which the 'master' 81150 is receiving software triggers with intervals on the order of seconds, but generally it is operated in a burst mode for half a minute to 15 minutes depending on the test cycle.  We have now seen that error on both generators.  Initially we thought it was an I/O problem (using Labview to control them) and have used USB, GPIB, and LAN all for control/triggering and sen the error with all of them now.

Because we've not wanted too much downtime (when there's a crash we restart the experiment) we haven't updated the firmware and are on 2.04 or 2.05, whereas I think the most recent revision is 2.09.  Another reason we haven't updated the firmware is that it's recommended to NOT downgrade, and some team members fear that additional issues could be introduced with an update and we couldn't go back.

My primary question is:  Has this behavior been seen before, and were any of the last few firmware updates specifically designed to address this issue?  If that's the case then I can tell my colleagues confidently that we should update the firmware at the next downtime.