Labview "Fatal Internal Error "memory.cpp" line 1038
This is an example file provided by NI and can be found in Labview 8.2\examples\instr\niHSDIO: Dynamic Generation.lib. Inside this library, there is a file called "Dynamic Generation.vi". If I copied "Dynamic Generation.vi" to other place, the labview will crash. Error message:
"Fatal Internal Error. "memory.cpp". Line 1038. Labview version 7.1.1. You will lose any unused work, please contact NI, etc, etc"
In the mean time, the Windows freeze. Mouse right click no response. No status bar at the bottom of the screen. The whole desktop is blank. All icons on the desktop disappeared. I have to log-off and re-login to re-active everything.
I also tried to copy other VI's in other library files. Same thing happened.
I was using Labview 8.2.1 when I had this crash, though I have Labview 7 installed in the same computer.
When I "copy the file to some other place", I mean: Click the *.vi file, ctrl-c and ctrl-v to some other directory.
..."re-entrant" "file I/O" "QSM_State Machines"
I have trouble with writing (appending) to text file in a QSM that is in an "occurence mode" of operation whereby the queue waits for outside engueue to go ahead and do a task. The task is simply to write to a file a line of text.
Outside producers give the queue its go ahead and data is sent along etc...
WHat I am seeing in the logging functions are multiple errors (Error 1)
Somehow Labview is not noticing that the reference is valid or it is invalidating the reference.
Q is Should I just let the QSM loop to keep it alive and would that work?
What is the rule concerning queue waiting for an event? Does the VI get flagged as idle and is that why the ref appears to be dropped? THere is no reason I can think of for the ref to be dropped. It is opened in the init frame then kept in a shift register.
and available at each iteration in the QSM.
The example works in a simple loop but not a loop that is waiting on an occurence. Why?
The only work around I can manage is to use the path and open the reference when it is not valid which feels kind of silly if you get my drift
Anyone seen this before?
...VI "FindInstrumentDrivers.vi" was stopped at node "" at a call to "IDF_WsIdOpen.vi"
This what I get trying to download Instrument Drivers in LabVIEW 8.2. LabVIEW 8.6 doesn't succeed either. any ideas?
Could just be an intermittent server problem. Does this happen all the time? At what point does it fail? When you first launch it, after you login? The network traffic indicates that it uses port 3339. Is this being blocked by your firewall?
...How to change "ASRL2:... " to "COM1"?
I have used com port in my vi. And When I run it in edit mode, the selection of com displays "COM1,COM2,LTP1".
But when I build it, and run it in another PC, it displays "ASRL2:...".
How can I modify my vi to make it display COM1... in another PC?
And If I only want to display all serial port such as COM1,...Programmatic "undo" for "FitControlToPane" ?
(using LV8.2) I'm trying to develop a GUI that lets the user toggle a Tab-control between "Full Pane" and a reduced size/position - sorta-like the "Full Screen" option on many Video apps. The effect of the invoke-node method "FitControlToPane" is perfect (- :smileyhappy: -), but how to undo that effect? After FitControlToPane, "Scale Object with Pane" is selected in the IDE, yet I can't find a "property" for it. :smileysad: FitControlToPane also changes the visibility of vertical and horizontal scroll-bars - are these [VI Properties] programmatically settable?
FitControlToPane also changes the visibility of vertical and horizontal scroll-bars - are these [VI Properties] programmatically settable?
Feel kinda silly now, having advised someone else to search LabVIEW's HELP first! :smileytongue:
- found Scrollbar Visibility can be set via (LV8.2)\ VI \Panel(reference)\Panes.HorizScrollbarVisibility.
Still hunting for an elusive "Set Scaling Mode" method...
(The Tab Control's "AutoGrow?" property doesn't seem to do anything!?)Message Edited by tbd on 04-03-2007 12:56 AM
ht...Adding an "IMAQ Image.ctl" to the "Display State.ctl" of an XControl prevents LabVIEW from creating a probe of "Display State.ctl"
I am working on an extended IMAQ Display control using LabVIEWs XControl capabilities.
I need a copy of the original image passed to add some overlays which must not affect the original image. To achieve this I am creating a backup image in the "Init.vi" and deleting it in the "Uninit.vi". I am storing the reference of this image in the "Display State.ctl" which is part of every XControl.
As soon as I am adding an "IMAQ Image.ctl" to the Display State cluster, it is no longer possible to generate a probe of the Display State cluster for debugging purposses. I am always getting the message: "Failed to load or create probe."
Deleting the "IMAQ Image.ctl" from the cluster makes the probe working again.
Is it a bug or am I doing something wrong?
I am working with LabVIEW 8.5 and Vision 8.5.
Hello Mr. Bartsch,
is it possible for you to post a small example to reproduce the behaviour? It would be helpful to get a description in which way you use the typedef files.
I found a example/knowledge base where some informations were included to XControl and LV but not with Vision.
<a href="http://digital.ni.com/public.nsf/allkb/1DC1ADD2A136DA298625712C00635758?OpenDocument" target="_blank">http://digital.ni.com/public.nsf/allkb/1DC1ADD2A136DA298625712C00635758?OpenDocument</a>
I need a data step that is equivalent to
put '&&&&&&a=' "&&&&&&a";
Yet the number of & is a variable, I need to write a Macro, so far I
got only half of the code('&&&&&&a.='), I don't know how to put
the other half ("&&&&&&a.") into Macro
%do i= 1 %to &k.;
==================================================..."VI was stopped at node " " at a call to "In Port Old 6.x.vi""
Hi. I am having problems with a VI that was initially developed for LABView 6i. I have upgraded to LABView 8.2 but whenever I run the program in LABView 8.2 I get the error message that my VI was stopped at node " " at a call to "In Port Old 6.x.vi". The VI generally aquires data from a measurement instrument via an RS232 COM port.
I have searched the forum and the only reference to this problem mentioned that it can be solved by making "minor modifications" to the polymorphic In Port VI in LABView 8.2 but I have no idea how to do this.
I would be most grateful if anyone can help me to do this. I am a newbie to LABView programming so I would require as much detail as possible. Thanks.
Have you followed the guidelines found on this document?
<a href="http://digital.ni.com/public.nsf/allkb/39129B46944215B686257069006CEC4E?OpenDocument" target="_blank">http://digital.ni.com/public.nsf/allkb/39129B46944215B686257069006CEC4E?OpenDocument</a>
Contains information on how to proceed and how you can change the VI's needed to new ones.
Hopes this helps!
Hello. Thanks for your response. I did see the link. Part of the document says:
Hi. I am having problems with a VI that was initially developed for LABView 6i. I have upgraded to LABView 8.2 but whenever I run the program in L...how to connect "IMAQ Get Buffer.vi" output terminal of "Image Out" to the input terminal of "Image" of "IMAQ ColorImageToArray.vi"
Thanks a lot for helping me till this stage.I am again stuck up with some problem.Please help me this time also.
Actually i am making changes in already existingblock diagram and also i am new to this labview programming.And also time is very crucial.
So i want to know if there is any way to connect the output of Image out terminal of IMAQ Get Buffer.vi to the input terminal of Image of IMAQ ColorImageToArray.vi.
In the actual block diagram the output of Image out terminal of IMAQ GetBuffer.vi is connected to the input terminal of Image of IMAQ ImageToArray.vi.
I want to change this becos i want to take RGB image as input and seperate R, G, B components.
Please explain in terms of bloack diagram.
...LabVIEW crashed when openning XControl Facade, and Init VI
...Problems with "&" changing to "&"
A lot of Firefox users I know, says they have problems with validation
where the ampersand sign has to be written as & to be valid. I don't
have Firefox my self and don't wont to install it only because of this,
so I hope some of you gurus can enlighten me with this :)
In what circumstances can the "&" in the source code be involuntary
changed to "&" by a browser when or other software, when editing and
uploading the file to the web server?
E.g. writing a string like "sc_project=402887&java=0&security"
is cha...How to use "GetLastInputInfo" in "user32.dll"
I need to logout user if he doesn't make action during 5 minutes, "GetLastInputInfo" method in the "user32.dll" library, return the tick of the last action, so I can know the inactivity time of the login user.
But I try to using "Call Dll function" item in Labview 8.1, and each time I run VI, Labview crash.
Next, is information about the method :
Syntax###############################BOOL GetLastInputInfo(PLASTINPUTINFO plii);
Parameters###############################plii : [out] Pointer to a LASTINPUTINFO structure that receives the time of the last input event.
Private Type LASTINPUTINFO cbSize As Long dwTime As Long End Type
Return Value###############################If the function succeeds, the return value is nonzero.If the function fails, the return value is zero.
Remarks###############################This function is useful for input idle detection. However, GetLastInputInfo does not provide system-wide user input information across all running sessions. Rather, GetLastInputInfo provides session-specific user input information for only the session that invoked the function.
You can see also my VI source.
http://forums.ni.com/attachments/ni/170/31...plug-in "not installed" in my LabVIEW project's "Build Specifications"
I moved my LabVIEW project from one computer to another, now when I click on any item under the project's "Build Specifications", I get an error reading "The plug-in for the selected item is not installed on your system." Does anybody know how to fix this? I have no idea what this "plug-in" is.Attached is a screenshot.
...fatal internal error: "memory.cpp", line 566
I'm using labview 7.0 and i'm compiling the program with the application builder.
When I launch the compiled program the second time I see the following error
and the program can't start.
The error is : fatal internal error: "memory.cpp", line566
and after another window with the following message appear:
AppName: bpp_220107.exe AppVer:0.0.0.0 ModName: lvrt.dll
ModVer: 18.104.22.16800 Offset: 003556ce
Finally the window in the attachments appears.
Please send me any helpful info.
Thanks a lot.
...Fatal Internal Error : "ctrlop.cpp", line 1860
This error is linked to the Type Def Controls. With little luck you can get around this error by removing the type def controls to get the vi causing the error open. After it is open the controls can be replaced with the original controls and saved.
Any idea why this error happens to begin with?
Fatal Internal Error Line 1860.jpg:
http://forums.ni.com/attachments/ni/170/275566/1/Fatal Internal Error Line 1860.jpg
The same error occured in 8.2.1.
Steps to initiate error.
1.) Open type defined control cluster
2.) Modifiy control
3.) Apply settings
4.) Close calling vi with out saving
5.) Open calling vi and this error will occur
I have code that duplicates this but I am not able to post it here.
I was not able to reproduce this on my machine. However, I do believe that there may be a bug here because I have filed a Corrective Action Request for something very similar. Could you perhaps be more specific on you step to reproduce (hold my hand)? Also, the error log that Travis described helps us too.
For example, I:
1) Opened a new VI and put a few different things in a cluster control.
2) Right-clicked on the cluster boarder and went advanced>>customize. Changed type to type def, saved the control and then the VI
3) &...Fatal internal error : "memory.cpp", line 1704
When I am trying to open my solution, an error occurs and Labview stops running. This happens only when I try to open one of my VIs. (Other VIs don't give any error.)
This error appeared after I saved my solution and close it then I try to open it again. The program normally saved and closed the solution but didn't open it again.
I need urgent help.
Thanks.Message Edited by turkey on 02-02-2007 01:08 AM
First of all I want to thank you for your interest.
You have wanted me to send you the VI that error occurs. But it is the main part of a big project and I hope you understant that this is a top secret machine vision project and I cannot publish it. If it will be sufficent, maybe I can send only the main VI (not subVIs).
Sorry for that situation.
?stanbul/TurkeyMessage Edited by turkey on 02-05-2007 09:46 AM
I have taken the reply below from RMA support of NI Arabia. As you see, that error is a bug till Labview 7.1 and resolved in Labview 8. Also there is another way to resolve it. If this error occurs agin, I will try this solution and I should send you the VI. (I ha...Fatal Internal Error : "OMUDClassMgr.cpp". Line 1128
I received the following message:
Fatal Internal Error : "OMUDClassMgr.cpp", 1128
LabVIEW version 8.2.1
I was trying to build an application using the application builder.
Has anyone else had this issue? What needs to be done to fix this.
This was reported to R&D (#4ALB7O89) for further investigation. Are you able to reproduce this problem with the same VI? Are you able to build an application with a simple VI?
...The .NET assembly expected to be at "" was loaded from "NULL"
I use NET Components in a LabVIEW 8.2.1. VI and all work very fine. Now I convert it to LabVIEW 8.5 and I always get a warning, when open it.
The Warning is :
The .NET assembly expected to be at "" was loaded from "NULL".
As example I add my CallbackVI in the Attachment. If somebody has an idea to remove this warning I would be thankful.
Thanks in advance
Oh I was glad to early.
The problem was only solved one time. When I changed something and saved again, I had again the troubles.
I will recreate the VIs now. I already done, but it didn't helped. Now I read, that old one should be closed.
...The use of the "XY graph" with the "Read Traces"
I'm trying to plot on "XY Graph" some informations wich are taken directly from the "Read Traces", and the problem is that the Start timestamp wich i enter to the "Read Traces" don't correspond to the beginning of the X axeof the graph.
Can some one help me please.
Question pour le forum NI.doc:
http://forums.ni.com/attachments/ni/170/334716/1/Question pour le forum NI.doc
Have you found an issue about your problem?
Could you attach you code(.vi) please?
Hi R_DUVALThank you for your help but I found the solution to my problem.Best Regards
...Difference between "FP Close" and "FP Hidden"
What is the difference between "Front Panel Close" and "Front Panel Hidden" ?
"FP Close" works similar to "FP Hidden" at programming mode but not at the executable !
Is this normal ?
At the executable "FP Close" seems to terminate the current vi.
One more question:
"FP Close" prevents the code that follows from been executed.
It is a "violent" way to stop your current vi, but not the whole application.
Am i right ?
To add one additional thing: I made some tests now on how the Close/Hide differs for SubVIs, and saw no difference. So regardless of hiding or closing the FP of a SubVI, the execution of the VI keeps going on until either the VI is stopped or the MainVI gets unloaded.Attached you can find my test: Sub.VI is the Vi called by closeFP.VI using VI-Server. You can toggle several functions of the Sub, but please note that Sub does not get unloaded until closeFP is stopped.Norbert
...Re: Fatal Internal Error : "memory.cpp", line 638
Second that motion. Is there a patch for those of us stuck in 7.1 or 7.1.1? The time cost (not necessarily the money cost) to upgrade to newer versions is sometimes prohibitive.
Hi Instrumento and ASteiner,
Thank you for posting to the forums. Hopefully, each of you have been able to find alternative methods to avoid this error in LabVIEW 7.1. Unfortunately, due to the frequency of updates that we provide, we do not normally have patches for individual or groups of bug fixes. Instead we look to correct the bug and maintain that fix through all future releases. Therefore, any LabVIEW version 8.0 and onward should provide that this will not occur.
The best suggestion that I can provide for a LabVIEW 7.1 user would be to look in the LabVIEW 8.0 Upgrade notes and reference that CAR ID I provided previously. Often times through this means we will provide any workaround method that was developed when this issue was identified.
I hope this helps! Have a great day!
...How to define "byte stream type" for "open file"?
I created some numbers (type "double") in Matlab and stored in a file. What value should I use to specify the "byte stream type" for "open file" in Labview? Should I put something like "DBL" or "I32". I don't know where to find the list of legal "types" in Labiew help.
Thanks so much!
Looks like 7.1:<img src="http://forums.ni.com/attachments/ni/170/347924/1/read%20file%207.png"> The Matlab "double" is 64 bits (8 bytes). It doesn't make much sense to use an integer datatype to read a floating point value, so you would use DBL in LabVIEW. The numeric data types table can be found <a href="http://zone.ni.com/reference/en-XX/help/lv/71/lvhelp/Numeric_Data_Types_Table/" target="_blank">here</a>. By the way, this assumes you saved the file as raw binary, as opposed to a .mat file, which is something different. Message Edited by smercurio_fc on 08-08-2008 11:21 AM
read file 7.png:
http://forums.ni.com/attachments/ni/170/347924/1/read file 7.png
Thank both of you!
I'm using Labview 6.1 base "Read File", just like the picture above. I've specified the byte stream type as DBL; however, the output is an array of string. What should I do with the string? I've tried to use "Decimal String To Number" but I got an output of "0".
I've also tried the "Read From SGL File" in Labivew and ...Race Condition: "Elapsed Time" and "Boolean Crossing"
We are experiencing a pretty strange issue here and we are not sure how to solve it. The attached VI's are a simplified version of the code, but that exhibits the same behavior:
The MAIN vi controls a boolean that is an input of the SUB vi. The SUB vi analyzes this boolean, and if its state is different than the last one read, a timer is reset. While the required time (2 sec) has NOT elapsed, the SUB vi outputs the last remembered value after the time has elapsed, the SUB vi finally outputs the new value.
Now, the problem appears when depending on how we change the input boolean (for instance, if you change its state as soon as the "elapsed time pulse" is generated), the new value is NEVER sent to the SUB vi's output. In other words, depending on the moment the input is changed, the SUB vi doesn't get the change and never resets the timer.
How can we solve this issue? Is there any special configuration that needs to be done in the used functions?
Thank you very much for all help.
...Unconfigured, Bad Status "A", Bad Status "B"
Greeting All. I recently upgraded to LabVIEW 8.5.1, including LabVIEW-RT.My application acquires data from an AI-110 -- Compact FP module.Anyhow, to make a long story short, my program started to malfunction.[After lots of pain and suffering,] I learned that the call fo FP Read produces the error:Unconfigured, Bad Status "A", Bad Status "B"The error is frequent, and I cannot help to think that it is considerably diminishing the performance of all other tasks.Any Ideas?
Can you post your code?
Certainly. Attached, you'll find a VI that resembles my worker-VI - which I use in my project.I run this VI inside of a state machine. It is initialized at the onset of execution.Thereafter, it is called upon [to read data] at 2Hz.The session is closed at the end.Thanks.