NiHSDIO error in labview 8.2. error in niHSDIO Get Session Reference.vi
I get an error in the niHSDIO Get Session Reference.vi.
the error is on the wire from refnum to the refnum input of the register session function. It says "This wire connects to a polymorphic terminal that cannot accept this datatype."
I've installed all the required drivers of the latest version:
visa 3.4
ivi compliance package 2.5
NI-DAQmx83
NIHSDIO 1.4.2
measurement and automation 4.1
I still get this error.
thanks
kevin
Kevin,
please verify that the error occurs within the blockdiagram i attached.
If it does, verifiy that the RefNum is set to "Session Reference". You
can do that by rightclicking on the constant, select "Select Session
Reference Class" >> "Session Reference".
Another point is that the instrument handle you are passing to this VI
has to be valid. If not, it should create error "-1073807346". But as
you know: better check twice
Norbert B.
NI Germany
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
Attachments:
sessionrefHSDIO.gif 6 KB
Similar Messages
-
LabVIEW File Permissions Error (8) when trying to delete a .SVN checkout directory
This one has me stumped...
Our test platform: Windows XP SP2, LabVIEW 8.2.1, TortoiseSVN client 1.45 Build 10425
We would like to delete our checkout folder and download a clean version from our SVN server using LabVIEW.
When we try and delete the folder using the standard LabVIEW Delete VI (see attached snap) we always receive Error 8 - LabVIEW: File permission error. You do not have the correct permissions for the file. This is interesting because I've checked the entire directory hierarchy and I'm the sole owner under Windows XP - I'm also our domain admin.
In an effort to debug this further, we removed the contents of the directory, apart from the hidden .svn. We checked the .svn tree for any outstanding files and removed them. We then re-ran the LabVIEW code to delete the dir. Still no joy. We then looked at the Windows dialog for the attributes of the checkout folder. It appear that the folder has read-onlly attributes - with a greyed-out tick in the checkbox. Also trying to delete the folder under the Windows command line doesn't work either. It only seems to work when you delete the folder through the Windows GUI.
Any thoughts anyone?
-Chroma
Attachments:
LV Delete Code.png 27 KBLabVIEW has the nasy habit of locking a directory where it opened a file in or just browsed.
Maybe this bug is biting you
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! -
Hi,
I am trying to run niScope Get Session Reference.vi on my system. But I got an error in the niScope Get Session Reference.vi. It requires a refnum and the niScope Get Session Reference.vi provided by NI does not provide a valid input for this function. For the convenience I have attached the error massage with this. I am using Labview 2012 and I have installed all the drivers correctly. Can anyone help me to solve this problem? Thank you very much!
Attachments:
Untitled.jpg 286 KBHi James,
Sorry for the delay. Here are my screen shots. Thank you so much!
Attachments:
Block Diagram.jpg 226 KB
Front Panel.jpg 426 KB -
after writing an html report on a floppy disk and removing it, labview shows an error message window: disk not present.
My pc is based on asus motherboard. Labview 7 and Windows 2000 sp4 installed.
The error message continue also if i stop the application that generated report on a: .
I've got this problem only on a pc: on other machines i don't have this problem (Labview only continues to access floppy but it doesn't show any window).
Find below an example: first press the button to create a report on a: then remove the floppy, after 30-35 sec i've got the error message
Attachments:
prova.vi 55 KBHi,
I tried your vi: I don't get any error message after removing the disk but LV7 keeps on accessing the drive at regular intervals even if you stop the vi and close it!!! This is not supposed to happen.
The only way to stop it is exit LV7.
If you don't use the file dialog and you wire a full path, you don't get any problem.
I also created a very simple vi that conditionally writes a text file on a: and I got the same behaviour.
This problem occurs only with LV7, I tried the same examples in LV6.1 and everything was fine.
If anybody wants to try I attach this simple example,
Alberto
Attachments:
salva_testo1.vi 22 KB -
Nickled and dimed once again by obscure errors. This is LabVIEW 10.0.1 on Redhat EL 5.5 32-bit.
I removed an enum from the project that is also used in a typedef control cluster. Since many VIs use this typedef I have to go to each VI and save in order to remove the phantom dependencies (i.e. popup can't find enum ctl when opening VIs). In the process of opening every VI and saving LabVIew is crashing on me reliably but not everytime just after I press cancel when it tries to find the enum ctl.
Here are the errors. Sometimes the address is null....I believe LabVIEW src code should check for null/bad pointers but does not in this case.
GenNAryOp_ArrayBase : naryop, setdef? ninp=1
Compiler error. Report this problem to National Instruments Tech Support.
copy cvt str/pict/tag, csrc=0xFF
Compiler error. Report this problem to National Instruments Tech Support.
copy cvt, csrc=0x21
Compiler error. Report this problem to National Instruments Tech Support.
copy cvt bool, csrc=0x30
Compiler error. Report this problem to National Instruments Tech Support.
copy cvt str/pict/tag, csrc=0xA
Compiler error. Report this problem to National Instruments Tech Support.
copy cvt, csrc=0x50
LabVIEW caught fatal signal
10.0.1 - Received SIGSEGV
Reason: address not mapped to object
Attempt to reference address: 0x0xffffffff
Upon reopening LV I see this.
The last time you ran LabVIEW, an internal error or crash occurred at source/typedesc/DSTM.cpp, line 211.Hello wbdoyle,
I'm sorry you are seeing that error. Did you close and save the type def that included the enum? This should prevent you from having to go through and save each VI that includes the type def. Are you using the System Exec VI? Also, are you performing any data acquisition with the VI you are referencing? The error you are seeing indicates that the LV compiler isn't handling something in your VI and I want to pinpoint exactly what is happening.
Thanks!
Regards,
Anna L
Applications Engineer
National Instruments -
Winsockread Error in LabVIEW PDA
Hi all. I am currently trying out the VI server example given in the LabVIEW PDA toolkit but i keep getting this error "WinsockRead error Error Code: 10054.
The LabVIEW example project I am using is "VI Server- Pocket PC.lvproj" and I have loaded the "CallByRef Wave - Pocket PC.vi" into the PDA. I have a WIFI connection to a PC and have manually assigned IP address to both the PDA (192.168.100.101) and PC (192.168.100.100). I have verified my WIFI connection is working by using the "ping 192.168.100.101" command on my PC.
Also, I am configured my VI server correctly by selecting the enabling the TCP/IP protocol and ActiveX under the VI Server Configuration. The port number I used is 3363. I have also added the PDA IP address (192.168.100.101) to the Machine Access List.
When I try to run the example program on the PDA with the IP address "192.168.100.100" and a port number of 3363, I will get the error. Can anyone give advice on what I have missed out or done wrongly?
I forgot to mention that the remote program "TargetWave.vi" on the PC is loaded in memory and opened in LabVIEW also.
Thanks in advance.D.Com,
I just thought of something else to try. You said you are using port 3363. The program was initially set up to use Port 3865. Did you change the VI server properties (From the project, right click on the my computer icon>>properties>>VI server: Configuration) to port 3363 or just the control on the front panel of the CallByRef Wave.vi? Both must be set to the same port.
Secondly, you may have to open a port in your firewall if you are using WindowsXP SP2. Initially I would completely disable the firewall and see if that solves the problem. If it does, then enable the firewall and create an exception of the port you've specified (3363).
As for using the trial version, this should have no impact on the performance of the toolkit.
Best Regards,
Chris C
Applications Engineering
National Instruments
Chris Cilino
National Instruments
LabVIEW Product Marketing Manager
Certified LabVIEW Architect -
Error in LabView.exe after each start
I installed LabView 7.0 in an older computer (Pentium III, 500 MHz, 512M RAM, Windows 2k sp4) along with GPIB and E-series PCI cards. Each time I open LabView it crashes and says "LabView.exe has generated errors and will be closed by Windows. An error log is being generated." The error log is attached, but means nothing to me. It crashes with regularity within 30 sec of opening LabView but I seem to be able to run .vi's during that time. I've tried:
1) Reinstalling
2) updating video card driver and ActiveX
3) installing on a different drive
none of these help.
Any help you may have would be appreciated.
Attachments:
LabVIEWlog.txt 1 KBHello,
The file you attached is a LabVIEW.ini file, where the configuration settings are stored. Please find the error log file, and this should give you a better idea what might have caused the error.
There are two types of log files. There are those created by LabVIEW and those created by Windows.
The log file created after internal LabVIEW errors is called LabVIEW_Failure_Log.txt and it is stored in your temporary LabVIEW directory. By default, this directory is located at C:\Documents and Settings\(User Name)\Local Settings\Temp (Windows 2000).
NOTE: By default, the Local Settings folder is a hidden folder. In order to view hidden files and folders in Windows Explorer, select Tools » Folder Options » View. In the Advanced Settings field, select Show
hidden files and folders.
If you have modified the location of you temporary directory, the log file will be located there. To view or change LabVIEW's temporary directory path, go to Tools » Options » Paths » Temporary Directory. For more information on the error information contained in the LabVIEW_Failure_Log.txt file, visit the LabVIEW Internal Error Support Page linked below.
If you receive an error message saying that LabVIEW has generated errors and will be closed by Windows, there will be a different log file created. This is a log file created by Windows, and by default it is a Dr. Watson's error log file. These log files are saved as .log file under ...\WINNT folder for NT based systems, and as .wlg under ...\Windows\Drwatson folder for Windows 9.x systems.
If you open just LabVIEW, without trying to open a VI, will you still receive the crash? If so, can you create a new simple VI similar to the VIs that crash LabVIEW and run it? Do you call any hardware driver or o
ther dlls with the VIs that cause LabVIEW to crash?
Zvezdana S.
National Instruments -
Error installing LabVIEW 2011 on Win 7
I'm getting an error installing LabVIEW 2011 Professional:
I found a thread concerning missing MSIs, which suggested that one run setup.exe with the /log function, so I did, but I don't think it actually says anything useful.
I also found a Microsoft download page for WindowsInstaller-KB893803-v2-x86.exe, which is the thing that's supposed to be missing. This seems to be an old version of the installer (most recent compatible OS = WinXP SP2), so I don't really feel like installing this on my Windows 7 system.
Help!! Thanks in advance.
-- PhilipHi Keller,
I'm Jamie an Applications Engineer at NI UK.
It does seem that you are missing some of the necessary support files required for the installer to run correctly, the details of which are available in the KnowledgeBase article here. Did you download the install files or are you installing from disk?
In addition to the setup.exe file, ensure that you have copied the following folders to the target PC or destination folder when creating an installer with LabVIEW.
bin
license
supportfiles
Hope this helps get you up and running with LabVIEW 2011, let me know if you experience any further issues.
Thanks
Jamie
Jamie S.
Applications Engineer
National Instruments -
Fix overlapping controls in error cluster (LabVIEW 2013)
In LabVIEW 2013, the "Error In.ctl" and "Error Out.ctl" have overlapping controls. If you run the VI Analyzer, you get an error from this arrangement. That shouldn't happen in something that's built-in.
Has an answer been determined for this?
I am getting this error for a few objects, but the error is not consistent and there doesn't seem to be alot of information on it.
See the attached images.
The Standard "error out" cluster is reporting 2 overlapping errors,
Status indicator
code indicator.
My "BioSig Control" is reporting 3 overlapping errors,
Bump/Offset F3
Yoke Connection Control
Programmer Connection
My question, are these really errors? or is this a defect in the analyzer and these indicators pose no threat to VI performance?
-Regards
eximo
UofL Bioengineering M.S.
Neuronetrix
"I had rather be right than be president" -Henry Clay
Attachments:
Overlapping control error labview.PNG 56 KB
Overlapping control error labview error output.PNG 5 KB -
Prologix LabVIEW write/read error
Hello,
I am a student/research assistant working on a LabVIEW program that was passed on to me from another student. I am not sure what happened between taht time and now but I am having problems with a write/read step from a Prologix GPIB. I have attached the vi code as well as several screen shots. I have checked the read/write module without running the program and I get a green arrow but still get a error code. After running the program, I get an error that is visible in the block diagram. I am really not sure what to do about this. By the way, I am taking measurements from a Homodyne setup. I will appreciate any help or suggestions. Thank you for your time.
Solved!
Go to Solution.
Attachments:
Prologix_LabVIEW_Block.jpg 150 KB
Prologix_LabVIEW_read_write.jpg 224 KB
Prologix_LabVIEW_write_read_buffer.jpg 216 KBI wanted to add more attachments
Attachments:
PiezoMeas1_prologix.vi 37 KB
Prologix_LabVIEW_Front.jpg 139 KB
Prologix_driver_software.jpg 175 KB -
Run-time error "5010": Labview: VI execution ...
I get Run-time error "5010": Labview: VI execution terminated by server. This error occurs sporatically. I am running Visual Basic 5.0 application that communicates to Labview 6.1 VIs. It is using NI-Imaq to do vision analysis of parts. I just need to know what to look for that may be causing this error. I am also running it on a PXI system with 64 MB of memory.
Hello,
I recommend you to do direct function calls to NI-IMAQ and NI Vision function libraries from Visual Basic as this will be a lot more efficient and improve rubustness of your application. During the installation of both software, you have the option to include support files for Visal Basic. Once these components are installed you should see the shipping examples in the following directories (if installed in the default path):
(NI-IMAQ) C:\Program Files\National Instruments\NI-IMAQ\Sample\VB
(NI Vision) C:\Program Files\National Instruments\MeasurementStudio\VB\Samples\IMAQ
There are additional examples that can be found in the Code Library (see the link on the left sidebar).
Let me know if you have further questions regarding this issue.
Regards,
Yusuf C.
Applications Engineering
National Instruments -
Intrument Gives error when Labview VI is loaded
I have a minor issue with one of my instruments that i control with labview. I can control it via Serial or GPIB control. When i load up my vi for the first time and my instrument is set to GPIB address 1 there is a slight delay loading up the program and I get an error light on my instrument. This means some info is being sent on the GPIB bus. After the slight delay the program finishes loading and the error light goes off telling me something else was sent to my instrument. This error occurs ONLY when my instrument is set to address 1. Any other address and everything works as expected. To combat this error in my vi i just send a *cls to clear everthing before i write again because the error seems
to send something that will mess up my first sent command. I ran NI spy to see what is happening when i load my VI's.
This is what NI SPY shows labview is doing on the GPIB card when i load up my VIs
1. viOpenDefaultRM (0x00154348)
2. viGetAttribute (0x00154348, 0x3fff018f, VI_TRUE)
3 viGetAttribute (0x00154348, 0x3fff0190,2 (0x0))
4 viSetAttribute (0x00154348, 0x3fff0190,2 (0x0))
5 viFindRsrc (0x00154348, "?*INSTR", 0x00157108,3 (0x3), "COM1")
6 viFindnext (0x00157108, "LPT1")
7 viFindNext (0x00157108, "GPIB0::1::INSTR")
8 viClose (0x00157108)
9 viSetAttribute (0x00154348, 0x3FF0190,0 (0x0)
Step 5 is where i get the error and labview hangs for a second. After it passes my error light goes off and it will continue to load. This issue only occurs when i have my instrument set to GPIB address 1. There seems to be some kind of conflict that occurs. Could it possibly be the software used in the instrument?The viFindRsrc VISA call finds all VISA resources connected to your computer. Line five is where LabVIEW polls the Serial Port, not your instrument, so I'm not sure why you would get an error there.
Since the error only occurs when your device is at PAD 1, I'd suggest checking for address conflicts. Is your GPIB0 device at address 1? Do you have any other devices connected to you system?
Also, what are all of the getAttribute and setAttribute commands? I don't get those when I run VISA Resources VI.
I hope this helps! -
What does LabVIEW mean by "Error 71: File Datalog Type Conflict"
What does LabVIEW mean by "Error 71: File Datalog Type Conflict" (Hex code:47)
Thank you.Please provide us further information on when you are getting the error and what the functionality of the VI is. That would help us to troubleshoot your issue.
Is the error caused by a similar situation as the one descibed in this KnowledgeBase?
Best regards,
Philip C.
National Instruments
- Philip Courtois, Thinkbot Solutions -
LabVIEW FPGA Module Error Code 10 when creating bitfile
I am recieving the following error message when trying to compile a vi:
Internal Error
An internal LabVIEW FPGA Module error occurred at the following stage: Creating Bitfile.
Error Code: 10
Error Text: Create Folder in nirviRecursiveCreateFolder.vi-
>nirviRecursiveOpenFile.vi->nirviWriteBitFileInformation.vi-
>nirviCompileDownload.vi->hardware_template.vi
If this problem persists, please contact National Instruments.
Any help would be appreciated. I am not very familiar with LabView, and am trying to run code generated by a grad student several summers ago. If more information is needed, let me know and I will try to provide it.
ThanksArkolbus-
It sounds like the compiler is having some trouble creating a folder that it needs to generate the bitfile. First, check all of the usual things: are you an administrator? do you have worte access to the "FPGA Bitfiles" folder in your project?
If it looks like you should be able to write the file, you can try posting your project (zipped) and let someone on the boards try to compile it (be sure to let us know what the versoin is). If we can compile it without issue you may want to try repairing your FPGA module installation.
Xaq "Bulldozer" -
Internal error or labview crash in 7.1ver thread.cpp(2842) whats reasons and how to fix it
Hi
Everybody ,
I am working with pci-6723 and labview 7.1 yesterday when iwas testing , the programme was running , suddenly the power has gone , since i have not connected my system to UPS system got shutdown , and when i booted pc its higlighted this error , now to what extent this problem affects to my software, and how to fix it.
"Internal error or labview crash in 7.1ver thread.cpp(2842) whats reasons and how to fix it"
Thanks in advance
RajeshHello Rajesh,
Do you get this error frequently or you got it only once after the power shutdown? Are you making a call to a DLL in multithreaded environment? Try mass compiling the VI by going to Tools->Advanced->Mass Compile. Also please follow the suggestions provided in this knowledge base entry regarding thread.cpp and see if that will fix the problem:
http://digital.ni.com/public.nsf/websearch/01B186B5CEB1D07786256747000F4319?OpenDocument
If you continue to have this error, is there any way you can send me a pared-down example demonstrating what your program does, so I can at least investigate to see if I can narrow down the cause of the thread.cpp failure?
Thanks and good luck!
Shakhina P.
National Instruments
Maybe you are looking for
-
Dynamic generation of Adobe Interactive Form
Hi all. hope you can help. My required scenario : We have a 4.6c SAP system that is generating a delivery note with some formatting on the note. The idea is to use the ADS to create a PDF based on a template we create (That can be modified later as
-
I am using Windows 7 ultimate and Firefox 4. I tried Alt + enter which does not work.
-
Best way to do an Insert or Update
I am doing some insert/updates via php to oracle. Each one will have to return an id to php. If its an insert it will return the new id (generated by a trigger and sequence) if its an update it will return the id. Is the best way to do this with a se
-
Can ARD be used to collect projects from a drop box where clients can store their work? Is this more of a server question? I just want my students to have a central location where they can store their project and then all I have to do is pick it up.
-
hi, i created a pl/sql block using ed <filename.sql> and tried to execut it useing @<filena.sql> or run <filename.sql>.for the 2nd command the message i got is "nothing in buffer to run" and for the 1st comm i got nothing. i dint event get prompt. i