TestStand/LV VISA error

Hello Support,
I am encountering a VISA error while trying to Initialize a COM port using a LV-VI from Teststand. I have (3) GPIB devcies that Init properly, from the same VI. See attachments.
I am able to Init the COM port, after going into MAX and verifying VISA alias name, no actions made within MAX.
However, the problem comes back when I shutdown the system.
Dirk
Attachments:
VISA Flush COM Port error.jpg ‏315 KB
VISA Init COM Port error (VI-wiring Diagram).jpg ‏291 KB

Hello DAY-TE,
Looking at the VISA Init COM Port error wiring diagram it looks like you are initializing the port and then using VISA Open afterwards. The Initialize VI for your device should already be handling opening the resource. Check the documentation for the reset VI because resetting the device might not necessarily close the the resource so using the VISA Open would be redundant and therefore cause an error.
Ian M.
National Instruments

Similar Messages

TestStand 3.1 Run Selected Steps generates Visa error -1073807346?

When using Run Selected Step in TestStand 3.1 to interactively execute previous steps in a sequence a Visa error (-1073807346 The given session or object reference is invalid.) is generated even though the selected step has previously executed with no errors.
Some history:
The sequence in question was developed with TestStand 2.0 and LabView 6.1 and does not exhibit the above mentioned issue. The error began after migration to TestStand 3.1 and LabView 7.1. The sequence executes without errors in all other conditions.

Hi,
When your sequence halts, does that mean it's closed the visa sessions and if so when running the selected steps are you running the setup with the open visa sessions or are you just reusing the sessions stored in the Station Globals (I assuming when you said globals you were referring to Station Globals).
Regards
Ray Farmer
Regards
Ray Farmer

Visa error handling in serial communication

Greetings,
I have a problem with the serial communication in my Labview program.
I have made an application that reads from serial port, searches for beggining characters, and later counts data after that beggining characters into variables in Labview program.
Everything work fine, but problem starts when I unplug the device from computer.
Program blocks and I could not do anything. Even Visa Close does not do anything.
I need to restart my computer to make my application works.
I made some indicators in subVi, and I see that when I unplug the device the error from READ VISA changes.
My question is: How to handle this event(error) to restart or unblock my serial device.
I am attaching a SubVi, that searches for starting characters " KBON,"
Best regards,
Chris
Attachments:
find_start.vi ‏12 KB

Hi Chris,
From the standpoint of VISA capabilities, you should be able to programmatically handle the desconection of the serial port. I am however not certain that your specific serial port hardware is OK with that.
As to how to handle disconnection using VISA:
I recommend using the "timeout" pin of the VISA Configure Serial Port VI
when the timeout is reached and no data is transferred, you will get a timeout error on the error wire.
You can then programmatically handle this error case in your code in a very similarly to this example.
I recommend experimenting to see what error codes your application throws, or alternatively you can use the VISA error codes documentation to create the case structures needed to hande these errors.
In all cases, you should close the VISA reference. Leaving the serial port rescource "open" in your operating system may be the reason why you need to restart your computer every time (as restarting will for sure free up the serial port rescource).
Best Regards,
T Simon
National Instruments
Applications Engineer
Certified LabVIEW Developer - Certified TestStand Architect

TestStand Deployment Utility Error

I am getting the error below when attempting to build a TestStand deployment. I am running TestStand 4.2.1.83 and LabVIEW 2009 Service Pack 1 Version 9.0.1f3. Any help would be appreciated as I cannot find any of the VIs mentioned in the error. Thanks!
Starting Log.
Starting Analysis
Processing Workspace...
Workspace Processed
Finished Analysis
Building...
10:15 AM
Internal error code 6503 Processing VIs...
Could not process LabVIEW VIs. Fix any broken VIs before rebuilding. LabVIEW error:
Exception occured in LabVIEW: LabVIEW: The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located. Select <b>File>>Open</b> to open the VI and then verify that you are able to run it. in Dynamically Call Build VI Distribution LV 8.6 or Above - TestStand.vi->TestStand - Call Build VI Distribution for Unique VI Hierarchies LV 8.6 or Above.vi->TestStand - Package VIs.vi->TestStand - Build.vi->TestStand - Distribution Wizard GUI.vi->TestStand - Deployment Utility Splash Screen.vi
An installer was not created due to an error
The build process is done.
10:15 AM
Aborted
Solved!
Go to Solution.

Hello George Mah,
I found CARs # 258761 and # 3OP9RE6I for TestStand which may be related to this issue and to error 6503. The error was created because VIs with duplicate names were included in a deployment. Would you verify that you do not have any duplicate VIs in your project? Are you noticing anything else strange with your deployments? Have you tried creating a blank deployment that only includes the TestStand engine or a run-time engine?
Regards,
Shawn S. | NIC
Instrument Driver/IVI PSE
National Instruments

When trying to test my serial port instrument I receive Visa error 1073807346, which means that they is not enough information for Visa to access or resource does not exist.

The error I am getting is on Visa open.

I found couple of knowledge base (KB) entries that talk about Visa error 1073807346. The best way to find knowledge bases (KB) is to goto ni.com >> Support >> Advanced Search (option 3) >> type in the keywords in the box "1073807346", you will get them.
Also refer, http://www.ni.com/support/labview/visa/default.htm. Hope this helps.

Visa error unless logged in as admin

I'm installing a LV program on several computers running Win7. It uses VISA to communicate with three separate instruments. If I'm logged in as admin everything runs perfectly but when anyone without admin rights logs in I keep getting VISA error "resources not found". This seems to be the two serial ports on a card, COM1 which is the on board port is working. I installed this on an identical computer yesterday and did not have this problem.
Solved!
Go to Solution.

When you are logged in as the other user, what do the serial ports show up as in Device Manager? What do they look like in MAX?
I wonder if there is a setting, possibly some sort of Windows Group Policy that is locking out serial ports for non-admins.
Is this a real serial port (with DB9 connector) or is this a USB-RS-232 converter which gives a virtual com port? Perhaps if group policy is to disable USB ports for non-admins, it is blocking the converter from working. Just speculating.

Sbrio9636 VISA Error -1073807202

Hello
I have a sbRIO9636 and the test instruments. I just want to connect sbRIO and Test instruments(with RS232).
I am trying to connect RS232 (9 pin) via serial ports..I also have Measurement & Automation Explorer (ver 5.1) to monitor and configure Serial/parallel connections.
The problem is that when I query, it looks like my device is not properly recognized. I only get time-out errors. VISA Error -1073807202. But when I connect the Test instruments directly to PC, NI Max shows COM 1 and can get the data from the test instrumnets. That means, I can get the data from PC , but I can't do the same with sbRIO9636.
How can I ensure that my device is properly recognized? Is my COM1 port activated at all? I can't see COM Port in NI Max for sbRIO9636.
thank you!
Solved!
Go to Solution.

Hey Kellydog
This is a kB what the VISA Error -1073807202 is.
http://digital.ni.com/public.nsf/allkb/10C6C0FBB8E7BD4486257850006CE8FF?OpenDocument
maybe this will fix your problem.
best regards,

Visa Error in MAX for Compact RIO

Hi,
I have a compact rio I haven't used in a few months. In Labview 7.1 and since upgrading to 7.1.1, I can't
connect to the compact rio. In MAX, I can see the crio device. When I open up the device, I get a VISA error
under Devices and Interfaces . 0xBFFF00A7 (VI_ERROR_MACHINE_NAVAIL). I can't ftp or ping to the crio either.
I have NI-RIO 1.2.
I connected to the crio console ....
General Software STPC Embedded BIOS 2000 (tm) Revision 5.2
Copyright (C) 2003 General Software, Inc.
Copyright (C) 2004 National Instruments Corp.
NI cRIO-9002 Controller
00000589K Low Memory Passed
00064512K Ext Memory Passed
Wait.....
PCI Device Table.
Bus Dev Func VendID DevID Class Irq
00 0B 00 104A 0201 Host Bridge
00 0C 00 104A 0210 ISA Bridge
00 0D 00 104A 0229 IDE Controller 11
00 0E 00 104A 0230 Serial Bus 11
00 0F 00 104A 0238 Ethernet 11
00 18 00 1093 70F7 Unknown Device 11
00 1F 00 104A 0981 Ethernet 10
(C) 1996-2003 General Software, Inc.
STPC-5.2-01DE-EB2E
BIOS revision: 1.1.9 (08/10/04)
Firmware revision: 10.1.94
Booting LabVIEW RT from drive...
Fat16
Jumping to 07E0:0000
Checksum: 011BCEEB
LabVIEW RT Boot Loader
(C) Copyright 2002-2003 National Instruments Corporation
STE10/100A Ethernet found.
Initializing network... done. IP address is 152.50.232.157
--------------------- NI-Serial v2.5.4 for LabVIEW RT ---------------------
COM1 - | Built-In Serial Interface
Welcome to LabVIEW Real-Time 7.1
NI-VISA Server started successfully.

Hi, Raltieri,
I noticed from the text that you sent that your cRIO controller has LabVIEW RT 7.1. Since you upgraded your host computer to LabVIEW 7.1.1, you will also need to upgrade the LabVIEW image on your controller to the same version. Try reinstalling the LabVIEW RT component into the cRIO controller (in MAX, under Remote Systems, under your cRIO >> Software), and just make sure that you select 7.1.1 as the version to reinstall. Most likely that is the problem.
Please let me know if that doesn't help.
GValdes
National Instruments

VISA Error -1073807194 When trying to connect to Dynamixel MX-28

VISA Error -1073807194 When trying to connect to Dynamixel MX-28
I'm trying to connect to a Dynamixel MX-28 and receive the above error when I run my VI.
The COM ports detected by the VI match the ones that I see in Windows 7 Device Manager.
Any other ideas?
I've attached the code I'm running below.
Attachments:
Single MX-28 Position Control.vi ‏23 KB

slow wrote:
I had no idea, actually. I'm just learning Labview (and was handed this code by the previous guy). I appreciate the help.
I'm guessing I need to replace the "VISA resource name" and "VISA resource name out" blocks (that are currently in the above linked VI) with the "VISA configure serial port" block?
In a related question, what would be the best way to expand this so that a larger number of servos could be controlled at once?
Would I just make multiple copies of the current blocks (with several position knobs on the front panel)? Would that make the most sense?
LOL I was making fun of the unusual place that NI put the VISA serial config, not being sarcastic about you not finding it. Sorry about that.
The config will go right before your write. If you turn on context help (the little ? in the upper right corner) and mouse over the various things on the block diagram and front panel, you'll see how to use them.
Not really sure about a desing suggestion. An array of position knobs to be indexed accordingly?
Bill
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

VISA error: -1074003961 What does it mean?

When attempting to set parameters with Agilent's Set PWM Parameters.vi on my new 81626 power head I get this VISA error: -1074003961 What does it mean?
I try the exact same VI with my 81623 Power Head and it works fine. Anyone have any answers?
I have a 8163 Mainframe with two 81619 Interface Modules intalled. In the Modules I have a 81623 head installed in slot 1 Channel 1, and a 81626 head in each of the channels of slot 2.
The error follows the 81626 heads. The 81623 head works fine.

Drugar:
That is BFFC0007, which is not a VISA driver code but is an instrument driver error. From vpptype.h, that seems to say that parameter 7 is what is causing the error. I guess you need to look at the C function prototype to figure out what the 7th parameter value should be.
Dan Mondrik
Senior Software Engineer, NI-VISA
National Instruments

VISA error

Hallo NG,
I've programmed a VI that communicates via GPIB with an instrument. Works
fine on the Computer (NT 4.0 with LV 5.1.1 Full Development), where I
developed the VI.
I built an application of this VI. Works fine on the Computer, where I
developed.
When I try to portate it on another Computer (NT 4.0 with Runtime Engine LV
5.1.1) I have the following error
Error -1073807202 occurred at an unidentified location.
Possible reasons:
VISA: (Hex 0xBFFF009E) A code library required by VISA could not be located
or loaded.
Which library is missing ?
Thanks a lot

re: VISA errors.
I'm new to all of this. I needed to replicate an ATE system that was put together for us by a large US consulting company several years ago (before my time). They were pretty good with their documentation, but they neglected to mention that a VISA run time is needed to be installed before their application would work. Probably because they developed the software on the existing systems and the Labview/CVI development system automatically installed VISA. The system uses instruments from Agilent and Tek, and a Keithley KPCI-488 card as the controller. I installed everything as they described and when I ran the application (that had been developed with CVI), got the now classic error bfff009e, "A code library required by VISA could not be located or loaded".
This has got to be one of the dumbest, least clear error messages I've seen in a long time. Not knowing anything else, an educated guess would indicate that it is VISA itself that is generating this error message. It doesn't tell you what specifically is missing so it is almost usless. However, a search of the NI message boards here indicates that it is actually a total lack of VISA at all that causes this error message. Using the search string "a code library" results in 60 hits, most all for the same issue in one way or another. It would seem to me that an error message that simply states instead "VISA is not installed" or some such thing would have saved hundreds of developers countless debugging hours.
I know this is not NI's fault, I have seen the same error message within an XML file of error messages on Agilent's software as well so it must be a "standard" message.
My 2 cents...
Oh and another thing, the CEC488 driver software that comes with the Keithley KPCI-488 card seems to expect the VISA run time to be in the C:\VXIPNP directory and not the C:\Program Files\IVI Foundation\VISA directory. This means that you MUST use Version 4.1 or earlier. (Or maybe install one of these earlier ones then install the latest.) I couldn't get an install of 4.2 to work, but 4.1 does. Maybe if I now install 4.2 it will work because it defaults back to the old installation directory. See the readme for version 4.2.
-RLL

Writed a dll for save string in teststand,get a error from teststand

I'm writed a dll for save string in teststand, the dll can execute by itself well,but when loading by teststand, it always error heppen,I attached all resource here ,please kindly help me on this,thank you in advance.
帖子被alexzheng在06-15-2006 03:19 AM时编辑过了
Attachments:
dll.zip ‏32 KB

HI，
I have resolved the problem, I have wrong define in the write function use : writetextfile(CString filename,CString text,int length)
but the error happen when I transfer those string from teststand to dll,it generation a system level error and automatic close teststand software occur,
after I change the define for :writetextfile(char *filename,char *text,int length) ,it is Ok now.
帖子被alexzheng在06-15-2006 06:44 PM时编辑过了
Attachments:
err1.jpg ‏21 KB
err1.jpg ‏21 KB

Intermittent VISA errors -10073807194 'connection for given session has been lost'

I am using a USB/Serial converter with FTDI chipset (VCP configured) to communicate with a serial device. There is an intermittent problem where the connection disappears, and the VISA error '10073807194' is generated. I have read carefully through the other threads related to this error, but still do not have a solution. Some background information on my set-up:
1) NI VISA 5.1.2
2) LV 2010
3) Windows 7 - 64 bit
Could windows be dropping the connection for the FTDI device when communication errors occur? Has anyone had this experience? We were previously using a prolific converter, and were encountering other communication errors where the read would timeout or only partial responses would be returned, but the VISA connection was not lost. I know the prolific converters can be problematic on 64 bit windows, so I was hoping the new converter would solve the problems.
I will post the code tomorrow, but I open the VISA session and configure the port on start up and close it when the application exits. I am using the bytes at port with the VISA read. However, the code I have has been running fine on two test machines in our office for several months. The above issues have been occuring at a customer's site overseas. We have not been able to reproduce the above problems here. There may be environmental factors at play (improper grounding, noise, etc.)
I should also mention that the original setup has this USB converter running through a hub, but the hub on their setup had to be removed due to reoccurring communication problems with this serial device, as well as other connected devices. We are going to get them to try installing a serial port on one of their PCs, and see if it eliminates the issue.
In the mean time any experience/help troubleshooting would really be appreciated. Thank you!!!
Zalusky

Well, I saw your Kudos to this post
Using "Bytes at port" on the FTDI driver can be very problematic and is the likely culprit for the behavior change. If there is any way to use a term char with the serial protocol change this.
The FTDI driver does have control of the buffer size and latency timer. Read through the documentation in this link. At the very least your polling rate for "Bytes at port" should be greater than the latency timer setting if the expected transfer is less than the buffer size. (shorten the timer )
Jeff

Longer TestStand scripts generate errors 1073807300 and 1073807343

When running longer scripts in TestStand 2.0, errors 1073807300 and 1073807343 are generated after about 30 minutes of running. This is on a Windows 2000 machine with 1GB RAM. This happened about a year ago, and splitting the scripts worked. Now we have added more VXI cards to the system, and the problem has re-occurred with some of the split scripts and others that worked fine before.

Hello Ron,
I would suggest looking at another similar discussion forum posting. It provides useful links to documents discussing this type of error.
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RNAME=ViewQuestion&HOID=5065000000080000001D840000&ECategory=TestStand
I hope that you find these helpful. If you are still encountering problems, please provide more information about your system (ie: what hardware you are using, what process model you are using, how many different devices are operating at a single time, etc).
Regards,
Aaron B.

Open DeviceNet interface error when TestStand call VIs of NI PCI-8532

Hello,
We use NI PCI-8532 was used as DeviceNet master to do functionality test with a slave (AC Drive).
But when open DeviceNet interface, it happen the error.
We can't find the solution and hope to find help from you.
The basic sequence in TestStand is:
1). Call "Open DeviceNet Interface.vi" to open interface and creat interface object.
Interface(master) setting: interface name=dnet0, MAC ID=0, baudrate=125000bps
2). Call "Open DeviceNet IO.vi" to creat DeviceNet IO object.
Device(slave) setting: MAC ID=63
3). Call "Operate DeviceNet Interface.vi" and operation code=start
4). Call "Wait For State.vi"
5). Call "Read DeviceNet IO.vi" to read data from IO object
6). Call "Close Object.vi" to close IO object handle
7). Call "Close Object.vi" to close interface object handle
Remark, these DeviceNet VIs locates at "C:\Program Files\National Instruments\LabVIEW 2012\vi.lib\DeviceNet\VIAPI".
First time to run sequece in TestStand, it can pass to run step 1) to open DeviceNet interface.
But once there is some error with these steps, and it will happen "Open DeviceNet Interface" error (error code=0xBFF62006) when run these steps again.
Then even use LabVIEW DeviceNet example to test, and it happen the same error except restart computer.
The DeviceNet example locates at "C:\Program Files\National Instruments\LabVIEW 2012\examples\NI-Industrial Communications for DeviceNet\Basic Examples\PXI & PCI\MixedCommunication.vi".
Some information more:
PC operate system: Windows XP SP3
LabVIEW version: 2012 SP1
TestStand version: 2012 SP1
PCI 8532 driver version: 2.3.0
Other installed PCI board: PCI 8531 CANOpen

The following errors may be resolved by resetting the CAN, DeviceNET or LIN device:
Error -1074388986 occurred at ...
NI-CAN: (Hex 0xBFF62006) The object is already open in another application. Solutions: Ensure that only one application at a time uses an object , and that you close all objects prior to exiting your application (don't use LabVIEW toolbar's Abort button).
Error -1074388969 occurred at ...
NI-CAN: (Hex 0xBFF62017) This attribute's value must be provided prior to the Open. Solutions: Set the attribute using the Config function before the Open, and do not set the attribute at any later time; Do not configure multiple CAN Objects for the same ID.
SO,you should reset the DeviceNet.
And another similar issue can explain some points of your problem http://digital.ni.com/public.nsf/allkb/7D9383E9BEAD0B21862571640002F687?OpenDocument

TestStand/LV VISA error

Similar Messages

Maybe you are looking for