LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

I am using serial communication and always having error 1073807246, I try to solved using the idea given in the ni site but it still doesnot work. Looking for your help?

I am using labview 6i. The ahrdware I am communictating is light modualtor.
0 Kudos
Message 1 of 5
(3,194 Views)
"Here is the definition of the error from LabView:

"VISA: (Hex 0xBFFF0072) The resource is valid, but VISA cannot currently access it"


Are you able to communicate with the hardware manually using a sw like "HyperTerminal"? If so, configure the serial port setting to the same as that to communicate manually.


It appears that you are using a valid comm port, but it cannot talk to the hardware for some reason. It could be as simple as a bad connection (wiring / soldering / etc) to the hardware.


The first thing I would check is the ability to communicate manually. If it works manually and you duplicate the settings, it should work. If you can;t communicate manually, then you'll have to do some troubleshooting..

-JLV-
Message 2 of 5
(3,194 Views)
I don't think this error would be produced by a bad connection (that would more likely give a timeout when the read command didn't get back what it expected). Are you sure that no other software is trying to access the same serial port at the same time? If you've been using Hyperterminal or anything else to test communication, you need to close it before communicating in LabVIEW. Also, are you absolutely sure you're using the right VISA resource name for the port you want?
0 Kudos
Message 3 of 5
(3,194 Views)
How to find out the right visa resource name?
you mean com 1,com2 etc or ?
another problem is my program doesnot have error when i run first time then after somtime it produce error
what si the reason behind this?
0 Kudos
Message 4 of 5
(3,194 Views)
In LabVIEW versions up to 5.1, the VISA resource name for COM1 on a PC is "ASRL1::INSTR", for COM2 "ASRL2::INSTR" etc. I believe LabVIEW 6 and later allow you to use the COM names as aliases but I'm a late adopter 😉 In any case I believe the ASRL notation should still work (someone else can probably help here). However, if you say your program communicates OK to start with then the resource name you are using is correct.

If you're seeing the error you mentioned after some time, I wonder if you are opening lots of VISA sessions but not closing them again, so eventually VISA runs out of resources? Generally you should open a VISA session in your program before you start communicating, wire that session through all the VISA VI's you use, and
only close the session when your program finishes.

If you're seeing some other intermittent error such as a timeout, consider timing issues - maybe your instrument sometimes takes slightly longer to respond, or you try to read data while the instrument is only half-way through sending it, etc. You may need to think about how to make your program more robust against these problems.
0 Kudos
Message 5 of 5
(3,194 Views)