Crash in VISA control - LV 8.20

Here is a crash when manipulating a VISA control in a cluster. This crashes LV 8.0.1 and LV 8.20 on Mac OS X (I haven't tested other OSs). Open the attached control "Error OxfordAddress.ctl". Control click (right click) on the VISA control at the bottom and change the VISA class from GPIB to INSTR. LV crashes and quits. Not good!
The work arond is to delete the VISA control and insert a new one. But LV should not crash and possibly lose work. Being reported here for inclusion in the monthly bug list.
Attachments:
Error OxfordAddress.ctl ‏7 KB

Kalin,
Thanks. My job is to be able to get you guys to reproduce it!! I always figure if you can reproduce it you can fix it! It is not always true and I have a few long standing bugs that are "too hard" to fix. But if I can get a reproducible simple example it is MUCH easier.
Thanks again for following up on this.
Cheers,
-Scott

Similar Messages

LabVIEW crashes when trying to use VISA controls

When I try and place VISA controls onto the front panel or a constant into the block diagram LabVIEW crashes and says that LabVIEW.exe caused an error and that LabVIEW must be restarted. Is there some setup required in order to use VISA or is there something wrong with LabVIEW?

I saw something that sounded exactly like this myself on two PC that where running some kind of "Eveidence Eleminator" software that got its hooks into everything.
I never did get it running on those two machines.
I saw something similar when trying to access a serial port that was hanging off of a USB gizmo.
We downloaded the latest and greatest version of the driver for the USB to serail device
and
upadted NI-VISA to the latest and greatest.
Then everything worked.
It was just like you mentioned, LV looks fine right up until you drop a VISA control.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Error in ni visa control out for usb in labview 2009

Hi,
I am using labview 2009 in which i have made a vi which communicates with a pic controller through USB interface.
the vi is working fine in labview 8.6. I tried it in two PCs. but when i run that vi in a PC with labview 2009 then the VISA CONTROL OUT.vi gives error "0xBFFF003E : Could not perform operation because of i o error.". while the control in.vi works fine in both the labview versions and any other PC that i tried.
I have run the application in total of 4 PCs with same set of cards/interfaces. two of them having labview 8.6 are running fine and giving no error but other two with labview 2009 are giving error.
and it doesn't stop here.... i searched in the vi and did some experiment and found that when i give Request value input to control out.vi as "0x36 "(as required by my PIC program) then it is giving error but when i give other value such as " 0x35 or 34 or 55"(used for other purpose) then it is not giving error.
Can it be a PIC programming problem? (i dont think so as everything is fine in other PC with LV 8.6)
I have already explored the ni forum for this error solution but could not find helpful.
Can anyone solve my problem?

I installed labview 8.6 in that machine and made a small program with only 3 vis (visa open session, visa close session and visa usb control out.vi) which is working in LV 8.6 platform.
Sorry the above statement is not correct actually.
When i run the program in LV 8.6 it giving that same error but this time it is not displayed as pop up window. so i could not judge that error was still there.

Visa Control grayed out when executable used with Run-time Engine

When I run an executable on a machine with only the Run-time Engine the Visa Control for Com Ports is grayed out. I'm guessing that I am missing a library, but do not know which one.

You need to install the VISA run-time. If you are just using VISA for serial communication, then there is an option on the app builder (Installer Settings>Advanced) for Serial Port Support. This will add a much smaller version of the VISA run-time engine to the installer you create. If you are using GPIB, etc., you have to install the hardware driver (i.e. NI-GPIB) and the full VISA run-time engine.

Finder crash when I control click on desktop or file - help please

Hi all,
My finder crashes when I control click on desktop or any file in a folder/directory. Do I have a preferences file that went bad or something? I already ran FSCK.
Thanks for the help.
Mitch

I had the same problem and I found the fix, thanks to Francine on your post:
I went into "/Users/yourname/Library/Contextual Menu Items" and into "/Library/Contextual Menu Items". I archived the contents of each, dropped the archives onto the desktop (in case I wanted them again) and trashed the contents of those 2 folders. Restarted and everything worked great getting the contextual menus up again on Finder items using Control-Click. I then replaced the appropriate archive into the "/Library/Contextual Menu Items", unarchived it (hoping to find the culprit item) and trashed the archive, restarted and again all worked fine again. I then repeated the process with the "/Users/yourname/Library/Contextual Menu Items" folder and again restarted and again everything worked fine! So found no culprits and the contextual menus work as they always did before the problem.
Hope this helps. PaulWR.

USB device name not shown in VISA control

Dear All,
I'm trying to control a lighting controller unit which used as a configurable power supply for a LED light panel.
The model is TMS Lite TMS-LC-15-4CH-A1.
It is not a popular device i guess so it doesn't have a labview driver like Agilent, GwInSTEK etc.
As usual i install the usb driver and demo software then i'm able to control the device using demo software.
Then i open my labview 2012 and select a VISA open, i created a VISA control and i expect the device ID to be shown for me to select. (Just like what i usually do for most of the agilent devices).
However this time it does not shown.
I'm stuck and i really hope someone can help.
Thanks!!!

Is it possible that the demo software you got to work isn't releasing the COM port resource? Have you tried rebooting the computer, and then looking in MAX and the VISA control for the COM port? Doing this after running the demo software may prevent it from being found if the demo software doesn't release the resource.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

Crashes consistently when control clicking a selected object

CS4 InDesign crashes consistently when control clicking a selected object. Preferences have been reloaded, the program has been reinstalled, all without any effect towards this issue. Any suggestions?

Yeah, it was InDesign Hangs when right clicking on graphic.
There was a lot of head-scratching and the rather unsatisfying conclusion was when the OP removed ancient applications that might have been a choice for "Edit Original," then the problem went away.
I guess the conclusion is that right-clicking on an image iterates over the possible apps that can open an image (for Edit With and Edit Original) and does [something], and for some reason that [something] was hanging. Not clear what the app was. But presumably if you right click the file in the Finder and look at the list provided by Open With, it is similar.
Or you could try the suggestions I offered to the OP in that thread that it looks like he never used.

XP Style NI-VISA Control

I'm upgrading a bunch of old 7.0 utility programs that use the Classic control palette. Most of these involve some sort of RS-232 based I/O, and used the old-style serial I/O functions. I've been upgrading them to use VISA, and noticed that there is no System version of the VISA I/O control.
I searched the forums, and didn't find any examples or solutions for an 'XP' style VISA control. The UIs I've upgraded looked sort of goofy with all of the controls as System and a Modern style VISA selector, so I tinkered around a bit and created a custom version of the NI-VISA control.
Maybe there is a way to do this natively, but I couldn't find it
See attached (LabVIEW 8.6.1f1)
Now is the right time to use %^<%Y-%m-%dT%H:%M:%S%3uZ>T
If you don't hate time zones, you're not a real programmer.
"You are what you don't automate"
Inplaceness is synonymous with insidiousness
Attachments:
XP Style VISA Control.ctl ‏6 KB

Philip, could you add these to the UI Interest Group?
Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!

VISA control putting devices into remote mode

So, I drop a VISA control on my fp. What I think is happening is when it populates, it is sending an *IDN? command to all the devices in the measurement and automation explorer. The problem with this is, some of the devices are in local mode, but if they detect something coming in over GPIB, they automatically switch to remote. I haven't tested it, but I have replaced the VISA control with a string control whos proper GPIB value is set from an INI file. I'm assuming this will solve the problem.
However, is it possible to have the VISA control on the fp and populate without it sending these devices into remote mode?
Message Edited by for(imstuck) on 05-18-2010 11:48 AM
CLA, LabVIEW Versions 2010-2013

Ravens Fan wrote:
I don't understand what you mean by "So, I drop a VISA control on my fp. What I think is happening is when it populates, it is sending an *IDN? command to all the devices in the measurement and automation explorer".
I don't know of any reason why that should happen. Try running NI-SPY or Portmon before doing this and see if you can capture a *IDN? command going out when it shouldn't be.
K, I'll do that. I guess what I assumed is when it (VISA ctl) populated its self, it went out and tried to find what instruments were actually there in order to know what to put in the VISA control drop down (i.e. GPIB0::1::INST,GPIB0::2::INST, etc). I assumed it may be doing this with an *IDN? command. I'll run the capture and see what's happening. For some reason when I start my program up, it's clearly sending other devices into remote mode by sending them something over GPIB that I'm not controlling. I know this because if I highlight execution, my code is in the idle state when these devices somehow get switched.
Hopefully NI-Spy will show me something.
CLA, LabVIEW Versions 2010-2013

Usb visa control bulk in error

i am trying to send data from my pic18f4550 programed using flowcode to the pc on labview using the usbrawbulk control example but i am unable to send or recieve the data the error i keep getting is the timeout error
i am using proteus virtual usb simulator and i have generated the .inf driver file from visa driver wizard
1)how can i get the brequest and brequesttype hex values to send and recieve data for the pic18f4550
2)how can i use the labview visa read and write to communicate and fix the current error
and thank you
Attachments:
visaprob.jpg ‏616 KB

Hi,
I am not sure I can provide exact infomormation, but I recoomend you to read about here:
- brequest and brequesttype: http://www.beyondlogic.org/usbnutshell/usb6.shtml
You can find examples about LabVIEW USB Raw communication:
- http://zone.ni.com/devzone/cda/tut/p/id/4478
- http://zone.ni.com/devzone/cda/epd/p/id/3637
- http://zone.ni.com/devzone/cda/epd/p/id/3622
- https://decibel.ni.com/content/docs/DOC-2022
- http://zone.ni.com/reference/en-XX/help/371361G-01/lvvisaprop/usb_raw/
I hope you can find useful information there.
Best Regards,
Peter Vago
AE Hungary

Premiere CS6 Crashes in Effects Controls

I have a 2012 iMac with the AMD 6770M 512MB and Premiere allows me to enable GPU accel. but with it turned on, everything I adjust something in the effects control, it freezes the program and requires a force start. It works fine if I disable GPU accel. but it would be unfortunate to lose that power. Any thoughts?

Update.
Imported same files in to CS5... works with no crashes, albeit with poor AVCHD playback performance...
Would like to have an Adobe response on this sort of thing.

Visa control of an executable running on the host PC

I write executables for my customer using LabVIEW. My customers often use other programming environments, such as Visual BASIC or C. They also control instruments remotely using the VISA layer. They are comfortable with the concepts of sending commands to instruments using VISA. I have a request from a customer to also be able to control my executable using the VISA layer. They would treat my executable as if it were another instrument. They would manually launch the executable on their PC. Then they want to address it from their programming environment (maybe Visual BASIC, or C, or Matlab) using the TCPIP::localhost::instr address and send commands to my executable program. In my executable I would monitor for these commands, and then respond to them as needed. My question is, is there an easy way to do this? A simple example would help me tremendously. The example I am looking for would be a LabVIEW executable that would monitor the "address" TCPIP::localhost::instr for a *IDN? command. An outside test program would send this command to the VISA address TCPIP::localhost::instr. When the executable receives the command, it would reply with "Hello." If I can get this far, then I can use this model to implement the commands that are required to control the executable. Thank you for any help.

Thanks for the response.
Yes, making my executable "look like" a VXI PnP instrument is exactly what I want to do...
If I have to program this from scratch, I agree that this is a tall order. But I was hoping that NI already implimented what I need...
Certainly, they have the portion that allows me to send commands to an instrument and read responses from an instrument using VISA. My question is if there is a way to use the same VISA read routine in my executable to monitor and wait for a command to come from somewhere else, and when the command comes in, can I then respond to it using the VISA write routine?
I am assuming that this is not possible, but maybe I am wrong?
If it is not possible, perhaps someone has done something similar that I can use, such as the TCP read and write, which I have never used before.
My end goal is to provide my customer with a well known and easy way to send the commands to my executable. (By using a VISA write.) This way I know that they already have the capability in their existing programs, and they will be able to do this will little effort from their side.
So it would be ok for me to use a TCP read (or any other approach) in my executable as long as it can intercept the VISA write that was sent from my customer's program (which is not written in LabVIEW).
Asked from another ponit of view altogether, is there a way to impliment the equivilent of NI-Spy in a LabVIEW executable. This would at least allow me to monitor all VISA traffic, and I can scan the traffic for commands that are intended for my executable. That would solve 1/2 of the problem, and would be a start.
Thanks again for the response.

Crash involving Logic Control?

hi all,
I'm trying to nail down a persistent crash in Logic 8.0.2 > OS 10.5.5. the actions involved in making the crash happen are many and varied, but the only thing which is a constant is that upon reboot, I am sent to the Control Surfaces Setup page - all my previous settings are intact, with the sole exception that the Marker button is switched off.
I trashed the com.apple.logic.pro.cs file today, and noticed that when it reformed itself, my Mac 8 core believes it to be a SD2 file. I'm wondering if this could be anything to do with my woes, or if anyone recognizes this crash behavior.
Also, for the most part, it's the "good" crash, where Logic saves its state before expiring.
Thanks
Malcolm

Hi Scripps,
I had the same thing happening a few weeks ago. I went ahead and dedicated the afternoon to wipe my system drive and reinstall LP8, I did upgrade to 10.5.6 also. Seems to be stable now.
One thing I noticed, just before the crash, 4 (or so) cores would redline and the playhead would skip a bit, it also seemed to be a combination of 3rd party plugs and logic with higher sample rates... in my case UAD-2 @ 96k.
I am not in the studio at the moment, but I do have a few notes, I will have a look and post if I find something helpful.
Good luck!
-delton
Message was edited by: deltonfoster

Executables crash if VISA sessions are implemented

I'm using LabView 6i version 6.0 on a Windows XP machine. I have several applications I've created which run fine under LabView, but the executables I build from them all crash. I don't get any compiler errors. I tried to build one of the serial communications examples which came with LabView, and that exe also crashes when I attempt to run it. This leads me to believe that the problem isn't specific to what I've written.
I wrote a very simple piece of test code that doesn't have any VISA functions, and the exe I generate from that runs OK. I have other executables I've built in the past that don't have any VISA code, and their executables still run OK as well.
Any known issues with VISA and building executables with LabView 6i V6.0?
Solved!
Go to Solution.

B_Harmon:
I haven't used v6 in years, I can't recall how to include the Visa RTE.
Below is a link to NI's ftp site for 6.0.2, I am not sure what exactly to download from there, hopefully it will help you.
ftp://ftp.ni.com/support/labview/updates/windows/6.0.2/
-AK2DM
~~~~~~~~~~~~~~~~~~~~~~~~~~
"It’s the questions that drive us.”
~~~~~~~~~~~~~~~~~~~~~~~~~~

Computer crashing and nvidia control panel missing options

Hey, I bought 2x msi gtx 970 and put them in sli mode. They worked fine for a while but yesterday I started having problems. I was playing shadow of mordor and suddenly my screen went black and my computer restarted. It worked fine afterwards tho. Then today I played some LoL and after playing for like 15 minutes or so it happened again. But now also after the computer restarted my nvidia control panel was missing options. There were only setup g-sync, set up stereostopic 3d and view rating for games. I'm not sure if this happened yesterday too. I tried reinstalling the drivers (tho I'm not 100% sure I did a perfectly clean install) and the options came back but the crash happened again and the options disappeared also again. I have 850w corsair tx850 so I think that should be enough power? My mobo is asus P8Z77V-Deluxe and cpu intel i7 3770k @ 4.3ghz. So what is the problem?
EDIT: after I restarted my computer again the options in the control panel reappeared
EDIT2: I ran furmark with both sli on and sli off for about 50 minutes and oddly enough my computer didn't crash. Everything ran well. Here's some statistics from sli: GPU1: 1316MHz @ 99% load, temp 80 C, voltage 1.193V, GPU2: started at 1303MHz and then dropped to 1277MHz @ 97% load, temp 62 C, voltage 1.206V. Another weird thing is that the crashes in lol kept happening even after this and always around 15-20 mins to the game. I would say it's an issue with lol but it happened once with shadow of mordor too. I haven't played any other games. Also it's weird that this started happening only recently, not from the beginning. I do recall downloading some update to geforce experience recently, don't know if that matters.
Also I'd like to know that are those temperatures normal for air cooling in sli and/or are they too high?
EDIT3: Just noticed that everytime I try to run pci-express render test on gpu-z my computer crashes instantly and apparently trying to run furmark now also crashes the computer

Quote from: Nichrome on 16-October-14, 00:56:09
Hello,
Could you please be more accurate on your spec: >>Posting Guide<< RAM, frequencies, timings and so on.
Would be worth trying bit more powerful PSU. Not saying this one is insufficient, but it's always best to rule something out for 100% sure.
Remove OC from the CPU and RAM (RAM to be 1333MHz and CPU to run stock). Or try >>Clear CMOS Guide<<
Make sure that you're running latest BIOS for the motherboard <Contact ASUS about it>
Temps are completely fine for SLI on air. Top card always is much hotter than the other. However you could reapply thermal paste on both cards, run single card for 1h and record its temps, then do the same for the 2nd card (in single card mode so the other is out of the PC) and use the cooler one on top.
I feel so dumb right now. Seems like one power cord from the psu to my gpu wasn't properly attached and now that it's completely connected everything seems to work. I'll update this thread if that didn't fix the problem. But anyways thanks for your fast response

Crash in VISA control - LV 8.20

Similar Messages

Maybe you are looking for