GPIB控制各种设备怎么将数据存储在Excel中

>我正在尝试制作的程序>将通过> GPIB控制各种设备并将数据存储在Excel中。假设您已经有设计和计划，请安装gpib卡，IO库和任何您需要的驱动程序
使用。
连接你的仪器并使用仪器管理器的“查找仪器”按钮来验证它的allworks.Using VEE是一件轻而易举的事。
从菜单中选择一个对象，将其放在工作区上并将其连接起来。
如果您选择在仪器上使用“驱动程序”方案，那么仪器交易就像从菜单中选择并填写详细信息一样简单。
如果你选择使用Direct IOtransactions，你应该熟悉该仪器的SCPI支持。一个“驱动程序”场景不是你想到的一个audiodriver或视频驱动程序，而是一个“虚拟仪器”（有点）
。
有些小组驱动程序确实是虚拟仪器。
其中有Plug＆amp;
播放驱动程序和现在的IVI-COM驱动程序。
VEE Panel驱动程序多年来一直没有得到支持，但它们仍在使用中，您可以在旧仪器中找到它们。
您将在yourIO Libs磁盘上获得大量的P＆amp; P驱动程序，您几乎可以找到任何一个（可能）.IVI-COM是最新标准（我认为）。通常我会跳过驱动程序但是
这就是我。
我宁愿阅读仪器的命令参考并使用Direct IO。
如果你使用驱动程序，你可能会得到更快的开发.VEE语言本身可能不会给你带来任何问题。
有一些不同的“对象”连接在一起形成程序的流程图。
数据流入这些对象的左侧和右侧。
“序列”引脚位于对象的顶部和底部（用于控制对象何时执行），但一般的共识是从左到右编写程序并让数据流指示序列。有时候你需要序列引脚。作为一种语言
，VEE相当不错。
有一些抱怨点，但大部分都是次要的。
我认为唯一认真的是它只限于一个无符号类型（8位类型）。
当你需要进行dobit-twiddling时，它会变得非常烦人。用Excel进行交互是相当轻松的。
它几乎与任何其他组件编程模型一样，但它不适合VEE的视觉范例。
这不是问题，只是烦恼。
如果您熟悉使用脚本语言进行自动编程，那么这不会是一个问题。如果没有，那么有一些基本概念：1）使用CreateObject或GetObject（通常为Create）创建对象。
2）将数据加载到对象中并从对象中提取。
3）调用对象方法来操作数据。
4）这些方法有时由Properties控制。如果您熟悉自动化编程，请记住VEE没有关键字Nothing和ForEach。
这不是问题 - 通常。
要设置一个等于Nothing的对象变量，只需删除它，任何值得一提的集合都有.Count和.Item成员，这样你就可以构建一个手动ForEach循环。如果你的Excel安装有VBA帮助可用，它将使得更容易处理Excel *。
使用.NET时，细节会有所改变，但它仍然是组件。例如，没有什么比帮助 - >打开示例更好。
查看ActiveXAutomation，您将找到六个详细说明Excel Automation的示例。
这些将立即开始，让你在一段时间内熟悉基础知识。最后 - 但同样重要的是 - 你已经找到了关于VEE，仪器，配置和编程设备的任何问题的一个来源 - 测试或其他 - 对
这里。
当然，总有TheArchive。
自1998年以来在VRF上发布的几乎所有消息（以及任何附加的示例程序）都可通过网络或电子邮件24/7在线获得（这是此消息底部的链接）.



     以下为原文

  > The programs that I am trying to make
> would control various equipment over a
> GPIB and store the data in an Excel.

Well assuming you already have a design and a plan, install your gpib card,
IO libraries and any drivers you'll use. Hook up your instrumentation and
use the Instrument Manager's "Find Instruments" button to verify it all
works.

Using VEE is pretty much a breeze. Pick an object from a menu, drop it on
the workspace and wire it up. If you choose to use a "driver" scenario with
your instruments then instrument transactions are as easy as picking them
from a menu and filling in the details. If you choose to use Direct IO
transactions, you should be familiar with the instrument's SCPI support.

A "driver" scenario is not what you would think of in terms of an audio
driver or video driver, but rather a "virtual instrument" (sort of). Years
ago there were panel drivers that really were virtual instruments. Then
there were Plug & Play drivers and now IVI-COM drivers. VEE Panel drivers
have not been supported for many years now but they're still in use and you
can find them for older instruments. You'll get a ton of P&P drivers on your
IO Libs disk and you'll be able to find one for almost anything (probably).
IVI-COM is the latest standard (I think).

Personally I usually skip the drivers but that's just me. I'd rather read
the instrument's command reference and use Direct IO. You'll probably get
faster development if you use drivers though.

The VEE language itself probably won't give you any problems. There are a
handful of different "objects" that are connected together to form sort of a
flow chart of your program. Data flows in on the left and out on the right
of these objects. "Sequence" pins are on the top and bottom of objects (used
to control when the object executes) but the general consensus is to write
programs from left to right and let the data flow dictate sequence.
Occasionally you need the sequence pins though.

As a language, VEE is rather nice. There are some grumbling points but for
the most part they're minor. The only one I think is serious is that it is
limited to only one unsigned type (an 8-bit type). When you need to do
bit-twiddling it can get very annoying.

Interaction with Excel is fairly painless. It's like almost any other
component programming model, but it doesn't fit VEE's visual paradigm very
well. That's not a problem, just an annoyance. If you're familiar with
Automation programming with a script language, then this won't be a problem.
If not, then there are a few basic concepts:

  1) You create objects with CreateObject or GetObject (usually Create).
  2) Data are loaded into the object and extracted from the object.
  3) Object methods are called to operate on the data.
  4) These methods are sometimes controlled by Properties.

If you are familiar with Automation programming, bear in mind that VEE
doesn't have the keywords Nothing and ForEach. That's not a problem either -
usually. To set an object variable equal to Nothing simply delete it, and
any collection worth mentioning has both .Count and .Item members so you can
build a manual ForEach loop.

If your Excel installation has VBA help available it will make dealing with
Excel *far* easier.

The details change a little when using .NET but it's all still component
stuff.

As for examples, nothing beats Help->Open Example. Look in ActiveXAutomation
and you'll find six examples that detail Excel Automation. These will get
you started in no time and get you familiar with the basics in only a little
while.

And last - but certainly not least - you have already found the one source
for any questions about VEE, instrumentation, configuration and programming
advice - test or otherwise - right here. And of course, there's always The
Archive. Nearly every message published on the VRF since 1998 (and any
attached example program) is available on line 24/7 via the web or email
(it's the link at the bottom of this message).
-SHAWN-