数据记录器3在开始扫描时冻结

1.您使用的操作系统是什么？2。您是否正在运行其他一些应用程序以及BLDL软件，因为在BLDL软件运行时始终建议不要运行其他应用程序.3。您是否每次都遇到问题？4.I
假设您已尝试卸载并重新安装SW，问题仍然存在？5。您使用哪种协议进行GPIB，RS232，LAN等通信？



     以下为原文

  1.What operating system are you using?
2.Are you running some other applications along with the BLDL software because it’s always advisable not to run other application while BLDL software is running.
3.Do you experience the problem every time?
4.I assume you have tried uninstalling and re-installing  the SW and the problem still persists?
5.Which protocol are you using for communication GPIB,RS232,LAN etc?

很抱歉延迟回复你。
Windows XP SP32。
没有其他程序在运行3。
是* 4。
是的，未插入/重新安装，包括IO Lib.5。
RS232 * =我玩了一下，如果我做“长”1秒的扫描间隔，我没有问题。
但是，如果我将扫描间隔更改为100mS（我的典型扫描间隔），它会锁定。



     以下为原文

  Sorry for the delay in getting back to you.

1. Windows XP SP3
2. No other programs running
3. Yes*
4. Yes, unintsalled/re-installed including the IO Lib.
5. RS232

* = I have played around a little and if I do "long" scan intervals of 1+ seconds I have no issues. However, if I change the scan interval to 100mS (my typical scan interval) it locks up.

这可能是RS-232问题。
我建议尝试降低波特率，看看是否有帮助。
通常，RS-232在现代PC上不是很可靠。
微软的实施并不是最好的，它们本质上是试图用软件复制硬件握手。
以下是我从另一篇文章中窃取的此类问题的预打包帮助提示：首先要仔细检查的是您的仪器rs-232设置和安捷伦I / O库中的PC设置是否匹配。
如果所有设置都匹配并且您仍然遇到问题，则可能与此有关：-------------------------------
--------------------------------------------------
--------------------------------------------------
--------------------------------------------------
------------------------------------使用安捷伦仪器上的RS-232与运行任何微软的笔记本电脑的问题
OSSymptoms：上传数据时超时，数据损坏，数据丢失，错误消息原因：PC上使用的RS-232 I / O芯片（UART）只有16字节缓冲区。
如果没有实时流量控制，缓冲区溢出可能会发生，从而导致数据丢失。
如果丢失的字符恰好是换行符，则软件永远不会看到行尾终止符，从而导致超时。
其他缺少的字符可能导致返回的数据错误。
Microsoft串行驱动程序未实现真正的硬件流控制。
它实现了软件驱动程序中的所有流控制。
这使得它易受PCI总线锁定，更高优先级中断和中断禁用的影响。
基于软件的流量控制的原因是历史性的，因为早期的硬件设计非常不可靠：16550 UART有无数的克隆，其中大多数都有缺陷。
Microsoft的唯一解决方案是开发一个尽可能少使用功能的软件驱动程序，因此在驱动程序中完成了硬件流控制。
此时Microsoft无法更改驱动程序以解决此问题。
仅在笔记本电脑上观察到这个问题，可能是由于与电源管理和/或PCMCIA适配器相关的软件开销，但理论上它也可能发生在台式机上。
更快的处理器和更慢的RS-232波特率无法成为令人满意的解决方案。
解决方案：不要将RS-232用于关键任务应用程序。
相反（1）考虑使用内置USB和LAN连接的34972A，或者（2）利用34970A的GPIB端口。
1.82357A USB / GPIB转换器可以连接到便携式PC上的USB端口和34970A上的GPIB端口。
此选项适用于具有USB，Windows 2000,98 SE或XP的笔记本电脑。
Windows 3.1,95和NT不支持USB。
2.使用E5810A LAN到GPIB网关。
网关可以连接到34970A上的GPIB端口，然后连接到PC的LAN（或直接连接到PC的LAN端口）。
LAN网关与Windows®98（SE）/ Me / NT / 2000 / XP兼容。
3.安装PCMCIA GPIB卡。
一些供应商提供PCMCIA GPIB卡，通常支持Windows®98（SE）/Me/NT/2000/XP.lhornburg安捷伦科技



     以下为原文

  This is likely an RS-232 issue.  I would suggest trying to lower the baud rate and see if that helps.  In general RS-232 is not very reliable on modern PCs.  Microsoft's implementation isn't the best, they are essentially trying to replicate hardware handshaking with software.  Here is sort of the pre packaged help tip for this type of issue I stole from another post:


First thing to double check is that your instrument rs-232 settings and your PC settings found in Agilent I/O libraries match. If all of the settings match and you are still having problems it could be related to this:
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Problems Using RS-232 on Agilent Instruments with Laptop PCs running any Microsoft OS


Symptoms: Timeouts, corrupt data, missing data, error messages while uploading data

Cause: The RS-232 I/O chip (UART) used on PCs has only a 16-byte buffer. Without real-time flow control, it is possible for buffer overruns to occur, causing a loss of data. If the missing character happens to be a line feed, timeouts can result from the software never seeing the end-of-line terminator. Other missing characters can cause returned data to be wrong.


The Microsoft serial driver does not implement true hardware flow control. It implements all flow control in the software driver. This makes it susceptible to PCI-bus lockouts, higher priority interrupts and interrupt disables. The reason for the software-based flow control is historical, due to the very unreliable early hardware designs: there were a myriad of clones of the 16550 UART, most of them defective. The only solution for Microsoft was to develop a software driver that used as few features as possible, and hardware flow control was therefore done in the driver. Microsoft is unable to change the driver at this point to fix this problem.

The problem has been observed only on laptop PCs, perhaps due to software overhead associated with power management and/or PCMCIA adapters, but theoretically it could occur on desktop PCs too. Faster processors and slower RS-232 baud rates do not help enough to be a satisfactory workaround.

Resolution: Do not use RS-232 for mission critical applications. Instead (1) Consider using 34972A with USB and LAN connectivity built in OR (2) take advantage of the 34970A´s GPIB port.
1.The 82357A USB / GPIB converter can be connected to a USB port on the portable PC and to the GPIB port on the 34970A. This option will work with laptops that have USB, and Windows 2000, 98 SE, or XP. Windows 3.1, 95 and NT do not support USB.
2.Use an E5810A LAN to GPIB gateway. The gateway can be connected to the GPIB port on the 34970A then attached to the PC´s LAN (or directly to the PC´s LAN port). The LAN gateway is compatible with Windows® 98 (SE)/Me/NT/2000/XP.
3.Install a PCMCIA GPIB card. Several vendors supply PCMCIA GPIB cards and typically support Windows® 98 (SE)/Me/NT/2000/XP.lhornburg
Agilent Technologies

谢谢你的回复。
我已经为我的系统购买了Agilent 82357B USB GPIB连接器。
我从另一个工作组借了一个，我的问题就消失了。
问题毫无疑问是RS-232连接的已知问题。再次感谢。



     以下为原文

  Thanks for the great reply. I have purchesed the Agilent 82357B USB GPIB connector for my system. I borrowed one from another work group and my issues went away. The issue was without a doubt the known issues with the RS-232 connection.

Thanks again.