Charles,
I didn't dig through your code much, but what is your iberr constant
after you do the IBRSP() and you get the error? That could give us a
clue as to why it is failing. What version of the driver are you
using in both cases (Win98 and 2K)?
Scott B.
Applications Engineer
National
It could be the card, I'm obviously not an expert on MC's GPIB cards.
An error like this at a GPIB write would make me think that the GPIB
card addressed the device to listen and itself to talk, but for some
reason the GPIB bus/instrument responded incorrectly or the card
responded incorrectly to
Hello Chris,
It sounds like you have the older DOS version of our GPIB driver. The
GPIB.COM is not meant to be executed, but is intended to be loaded in
your config.sys file with a DEVICE=C:\path\GPIB.COM call.
If you are using an AT-GPIB card, note that you are using an obsolete
card on your
Asif,
Glad to know that you were successful, but I'm not sure exactly what
went wrong in the first place. I tested this out and it seemed to
work fine. With LabVIEW 7.1 and VISA 3.1 on Windows XP, I used a
loopback connector and our Basic Serial example to test this out. I
wrote 20 bytes to
Hello,
I cannot be of any help, unfortunately. National Instruments does not
support the I2C bus directly on the parallel port and hence does not
publish any software to do it. Perhaps others who post here can
assist you.
Scott B.
Applications Engineer
National Instruments
Hyperterminal will certainly be helpful to make sure that you are
getting valid data. You might also want to try VISA Interactive
Control from Measurement and Automation Explorer under
Tools...NI-VISA...Interactive Control. You will be able to exactly
simulate the calls that are being made in
This is a good answer; I don't know of any issues where data gets
corrupted somewhere between the VISA and Windows Serial API layers so
there has to be some difference in settings.
Check the baud rate, data bits, etc. I assume that you're using the
exact same setup as far as cable, computer,
Hello Molly,
There are a few things that could be going on here. What method are
you using to communicate between your VI's? I will assume you are
using serial.
If a port is not open, the port will discard the message, which could
be what is happening here. If you are trying to write from
Jeff,
Good luck in your attempts. Remember that the first step is just to
get the device to be recognized as a standard parallel port by your
computer, then VISA should see it just fine. Post here or start a new
thread in Discussion Forums if you need more assistance.
Scott B.
Applications
Hello,
While this may be possible, it isn't recommended. The serial port on
your computer has a UART with a clock that will clock out whatever
byte LabVIEW writes to it one bit at a time along with start bits,
stop bits, and parity bits at the baud rate that you specify. LabVIEW
can certainly
The forums seem to be working okay, I wonder if there is a firewall
issue. You can upload the files to ftp.ni.com in the Incoming folder.
Zip them up and name them BCLioness.zip and post here when you have
done that and I'll take a look at them. Sorry for all the trouble.
Scott
Lori,
Again, this is a very intriguing problem. When the bus is broken
and the offending instrument is on it, do you get the error in MAX
that says that it could not find any instruments, or does it simply
not tell you anything after you hit Scan for instruments? Looking
at your SPY file, I see
Hi Lori,
Your attachments are all showing 0 bytes, could you try them again?
Thanks,
Scott B.
Applications Engineer
National Instruments
Hello, Alan.
A relevant KB is
http://digital.ni.com/public.nsf/websearch/42B604435E3F9604862565E20043CD30?OpenDocument.
As this KB points out, there is no general-purpose set of firewire
VI's for LabVIEW. If you are trying to communicate with a particular
device via firewire, you will need to
Hello,
Could you give me more details about your GPIB setup? How many
instruments do you have on the bus? It sounds like the 4083 is
breaking the GPIB bus where no other instruments can communicate on
the bus when you have the 4083 connected, is this what you're seeing?
What do you mean that
Hello Shreesha,
Standard DNet communication is what the NI-DNET card is designed for.
I'm not exactly sure what you need to do to load a parameter list into
your device, but it seems that you would usually do this inside the
DNet specification by sending standard data packets to the device.
Your
Hello,
I have two questions for you:
-What ModBus VI's are you using? Who wrote them?
-What is the exact error that you receive at runtime while executing
on the LabVIEW Runtime Engine Target?
This sounds like it's an issue of the ModBus VI's depending on
something else that the Runtime Engine
Hello,
It seems that you are trying to test LabVIEW to VISA support by
connecting 2 USB ports on your computer to a USB Hub, sending data out
one USB port and receiving it on the other.
This is not a supported configuration with NI-VISA, the underlying
communications protocol that will support
18 matches
Mail list logo
