LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

agilent 54622d instrument driver problem

First, there are no limitations in the driver. You don't seem to recognize a difference beween an instrument error and a driver error. The VI does no checking of input values so when you enter an invalid value, you get an instrument error.

 

You already understand that the com port is in use andyou already said that you have Excel talking to the com port. It' just a snall logical leap to realize you have to close Excel before using LabVIEW.

 

As far as the attribute error, one of the com port settings cannot be used with your serial port. I would start by removing the handshake properties. Are you using a USB-RS232 adapter?

0 Kudos
Message 11 of 15
(750 Views)

I do realize that I have to close Excel before using LabVIEW. The reason I brought it up was firstly to illustrate that the com port is working and secondly because the error text with Excel open says that the resource is valid, but VISA cannot currently access it, witch for me gives the impression that all is well except the com port is been used by another program. Then again after closing Excel the error changes to: "The specified state of the attribute is not valid, or is not supported as defined by the resource" whitch implies a more complicated problem. Sorry about my poor wording I hope I managed to convey my point.

 

My computer is an older laptop with a com port, so no adapter.

 

0 Kudos
Message 12 of 15
(744 Views)

So modify the VISA property node in the initialize function to see which one is causing the error. As I said, I would start with the handhaking one. If you have communication working in another program, set the the properties to exactly the same.

0 Kudos
Message 13 of 15
(733 Views)

did you ever get it to work with RS232. I am having the same problem. Do you have your VI sample??

0 Kudos
Message 14 of 15
(637 Views)

Hi ramiro91006,

 

can you give me a bit more detail about the problem you are having. Which error are you getting specifically, and what is your hardware setup? Are you also using the Agilent 54622d?

0 Kudos
Message 15 of 15
(627 Views)