Fpsane.cpp error

Hello,
Following an fpsane.cpp error, all open vi's crash and when they are reloaded they are temporarily reloaded in mandarin chinese. After a minute or so the language reverts back to english. Has anyone ever seen an error like this before?
Thanks,
Chase
Test Engineer - Subzero Freezer

1984 is most likely correct about the corrupt files. The fpsane.cpp error usually indicates something has become "very corrupted" as listed in the explanation of the error:
http://digital.ni.com/public.nsf/allkb/AFA28DCC3DE89839862566B200594E8C
Have you located the origin of the error?
Applications Engineer
National Instruments

Similar Messages

DAbort 0x1A7102DF in fpsane.cpp when opening a 2011 vi in a machine with 2012 vs

DAbort 0x1A7102DF in fpsane.cpp
Error message appears when i try to open a vi with LV2012 created in other computer with 2011 version.
Does anyone know how to fix it?.

Does the VI open correctly on the 2011 machine?
Do new VIs work correctly on LV 2012? What about opening shipped examples?
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

"fpsane.cpp" in line 269 appears when trying to save ma VI after the 1st run!

Hi LV-users,
this is a problem some of you may had before. But I still don't know how to solve this problem.
LV crashes when I try to save my VI after the 1st run telling me about the fpsane.cpp-error. It also tells about "INSANE object at FPHP+3EE4 in my VI" and it says
"{sub } (0x10)wave chart" and so on.
I wonder if their is a mistake in a sub VI, maybe because I'm working with references for my wave charts and their histograms which have to be saved if the acquired datapoints are not within tolerance.
I already upgrades my LV-Version to 6.02 and so on...I read about this solution in the Discussion Forum.
I added my VI and Sub VIs using references.
Can anybo
dy give me some advice?
Thanks, Kathrine
Attachments:
2405_D_Kurven_in_Cluster.vi ‏199 KB
Kurven_Sichtbar.vi ‏38 KB
3_Historie_speichern_B.vi ‏51 KB

Insane error are not due to your programming. There are several good pages on our site that discuss solving these errors. Goto www.ni.com >> support >> advanced search (it is at the bottom--click on the words). This lauches the best way to search our site because under option 2, you can limit your search to resources of interests. Enter insane in the all the words field and search everything. One of the first hits is a knowlegbase that discusses solving this issue.
Jeremy Braden
National Instruments

LV crashes when I try to save a VI - "fpsane.cpp line 269 error"

Dear LV users:
“Fpsane.cpp, line 269 error”
I have this error when I modify the VI and try to save it. Often I run it once and save it without problem. When I modify it again and try to save it, the error appears and LV crashes.
First I made a 6.0.2 upgrade and later I followed the “solving troubles” procedure at NI home page, like empty the TEMP directory and so on.
Later I sent my VI to NI support and I received the confirmation that they were able to reproduce the error, but not able to isolate it. Also they wrote that “Maybe can be a problem with the charts” and “it could be a bug in LV 6.0.2 which is fixed in LV 6.1”.
They saved my VI as a 6
.1 version and there were no problems (any error).
The problem is:
“ LV 6.1 is the next release (newest version) of LV and it will be released this year (the date is not fixed). That's not an update like LV 6.0.2 but a new version of LV. It must be purchased”
So I have a trouble here. I have some VIs that contains some parts in common. Now they are crashing too. I’m not confident anymore to make tests and modifications, since LV will crash again. What I’m doing after run my VI is exiting LV and open the VI again. Only after I can realize (and save) the modifications. This way is really a pain in a neck....
Please, can someone tell me a good way to isolate this problem or to solve it? I really don’t want to wait LV 6.1 nether to buy it to solve this “bug”....
Thank you in advance
Rodolfo
OS: Nt4 sp 6
LV 6.0.2

Dear LV users
Sorry for not have included the VI.
"test time save format.vi" is a learning program that contains some ideas to be used in another one. The error (fpsane.cpp) that appears here also was detected in LV 6. On the first time after grouping/edit some controls.
This error occurs when you modify the VI and try to save it. Often you run it once and save it without problem. When you modify it again and try to save it, the error appears. This is the same problem that happened with 2 other VI, even with one LV original example (after grouping).
The same error happened in another computer (also running NT4). All libraries were rebuilt during the installation of LV 6.02 and the TEMP directory is empty.
I hope that this vi will help us.
Thanks ag
ain
Rodolfo
Attachments:
Test_time_save_format.zip ‏92 KB

LabVIEW 8.6 fpsane.cpp 434

I had an internal error when I started working on updating a medium sized application (roughly 500 vi) from Labview 8.5.1 to LabVIEW 8.6. I am trying to use the classes and objects to reorganize my application to get a eaiser maintained solution. I had about 8 classes with controls that were strict type def'd before. I allowed the strict type defs to carry forward into defining the class object. I'm a rank beginner with the OOB stuff so I'm not sure if I broke something by doing something crazy or unnecessary.
Here is the error printout, which I did allow the app to send it in to NI. But I haven't actually asked for help on it yet. I'm not sure that it's a killer bug.
#Date: Thu, Feb 05, 2009 2:53:35 PM
#OSName: Windows NT
#OSVers: 5.1
#AppName: LabVIEW
#Version: 8.6
#AppKind: FDS
#AppModDate: 06/26/2008 01:25 GMT
Insane object at BDHP+C77BB9C, UID 1089, in "NI_Gmath.lvlib:Matrix left divisionMM_general_direct.vi": {flags } (0x1000): Call Library Function Node (NODE)
c:\builds\penguin\labview\branches\Saturn\dev\source\panel\fpsane.cpp(434) : DWarn: Insanities(0x00001000) exist in ReportInsanities, 'NI_Gmath.lvlib:Matrix left divisionMM_general_direct.vi'
$Id: //labview/branches/Saturn/dev/source/panel/fpsane.cpp#10 $
0x00F3566A - LabVIEW <unknown> + 0
0x00F35E28 - LabVIEW <unknown> + 0
0x005AA7BA - LabVIEW <unknown> + 0
0x005ABC4A - LabVIEW <unknown> + 0
0x005AB190 - LabVIEW <unknown> + 0
0x005AB4F5 - LabVIEW <unknown> + 0
0x005AB7D8 - LabVIEW <unknown> + 0
0x006AA3A3 - LabVIEW <unknown> + 0
0x006AA9D5 - LabVIEW <unknown> + 0
0x006AAD7B - LabVIEW <unknown> + 0
0x006AAD31 - LabVIEW <unknown> + 0
0x006AAFEA - LabVIEW <unknown> + 0
0x006AB4AA - LabVIEW <unknown> + 0
0x011CE3BA - LabVIEW <unknown> + 0
0x01225F28 - LabVIEW <unknown> + 0
0x0122D155 - LabVIEW <unknown> + 0
0x01228903 - LabVIEW <unknown> + 0
0x00B0A055 - LabVIEW <unknown> + 0
0x00AD4792 - LabVIEW <unknown> + 0
0x116F804C - <unknown> <unknown> + 0
0x09C5CB60 - <unknown> <unknown> + 0
0x00ADC260 - LabVIEW <unknown> + 0
0x0008D8EC - <unknown> <unknown> + 0
*** Dumping Bread Crumb Stack ***
#** sanity checking heap: "N:\ATEST\Automation\PAT_2.0\Working_Source\PAT_Ver2\Matrix left divisionMM_general_direct.vi"
#** sanity checking: "N:\ATEST\Automation\PAT_2.0\Working_Source\PAT_Ver2\Matrix left divisionMM_general_direct.vi"
#** compile: "N:\ATEST\Automation\PAT_2.0\Working_Source\PAT_Ver2\Matrix left divisionMM_general_direct.vi"
*** End Dump ***
Insane object at BDHP+C77BB9C, UID 1089, in "NI_Gmath.lvlib:Matrix left divisionMM_general_direct.vi": {flags } (0x1000): Call Library Function Node (NODE)
c:\builds\penguin\labview\branches\Saturn\dev\source\panel\fpsane.cpp(434) : DWarn: Insanities(0x00001000) exist in ReportInsanities, 'NI_Gmath.lvlib:Matrix left divisionMM_general_direct.vi'
$Id: //labview/branches/Saturn/dev/source/panel/fpsane.cpp#10 $
0x00F3566A - LabVIEW <unknown> + 0
0x00F35E28 - LabVIEW <unknown> + 0
0x005AA7BA - LabVIEW <unknown> + 0
0x005ABD95 - LabVIEW <unknown> + 0
0x005AB190 - LabVIEW <unknown> + 0
0x005AB4F5 - LabVIEW <unknown> + 0
0x005AB7D8 - LabVIEW <unknown> + 0
0x006AA3A3 - LabVIEW <unknown> + 0
0x006AA9D5 - LabVIEW <unknown> + 0
0x006AAD7B - LabVIEW <unknown> + 0
0x006AAD31 - LabVIEW <unknown> + 0
0x006AAFEA - LabVIEW <unknown> + 0
0x006AB4AA - LabVIEW <unknown> + 0
0x011CE3BA - LabVIEW <unknown> + 0
0x01225F28 - LabVIEW <unknown> + 0
0x0122D155 - LabVIEW <unknown> + 0
0x01228903 - LabVIEW <unknown> + 0
0x00B0A055 - LabVIEW <unknown> + 0
0x00AD4792 - LabVIEW <unknown> + 0
0x116F804C - <unknown> <unknown> + 0
0x09C5CB60 - <unknown> <unknown> + 0
0x00ADC260 - LabVIEW <unknown> + 0
0x0008D8EC - <unknown> <unknown> + 0
*** Dumping Bread Crumb Stack ***
#** sanity checking heap: "N:\ATEST\Automation\PAT_2.0\Working_Source\PAT_Ver2\Matrix left divisionMM_general_direct.vi"
#** sanity checking: "N:\ATEST\Automation\PAT_2.0\Working_Source\PAT_Ver2\Matrix left divisionMM_general_direct.vi"
#** compile: "N:\ATEST\Automation\PAT_2.0\Working_Source\PAT_Ver2\Matrix left divisionMM_general_direct.vi"
*** End Dump ***
Insane object at BDHP+C77BB9C, UID 1089, in "NI_Gmath.lvlib:Matrix left divisionMM_general_direct.vi": {flags } (0x1000): Call Library Function Node (NODE)
c:\builds\penguin\labview\branches\Saturn\dev\source\panel\fpsane.cpp(434) : DWarn: Insanities(0x00001000) exist in ReportInsanities, 'NI_Gmath.lvlib:Matrix left divisionMM_general_direct.vi'
$Id: //labview/branches/Saturn/dev/source/panel/fpsane.cpp#10 $
0x00F3566A - LabVIEW <unknown> + 0
0x010088F2 - LabVIEW <unknown> + 0
0x0100CC3E - LabVIEW <unknown> + 0
0x0100D9E9 - LabVIEW <unknown> + 0
0x0100DF9B - LabVIEW <unknown> + 0
0x0100E4BB - LabVIEW <unknown> + 0
0x00D56559 - LabVIEW <unknown> + 0
0x013F61C1 - LabVIEW <unknown> + 0
0x00D54B61 - LabVIEW <unknown> + 0
0x006AA616 - LabVIEW <unknown> + 0
0x006AA9D5 - LabVIEW <unknown> + 0
0x006AAD7B - LabVIEW <unknown> + 0
0x006AAD31 - LabVIEW <unknown> + 0
0x006AAFEA - LabVIEW <unknown> + 0
0x006AB4AA - LabVIEW <unknown> + 0
0x011CE3BA - LabVIEW <unknown> + 0
0x01225F28 - LabVIEW <unknown> + 0
0x0122D155 - LabVIEW <unknown> + 0
0x01228903 - LabVIEW <unknown> + 0
0x00B0A055 - LabVIEW <unknown> + 0
0x00AD4792 - LabVIEW <unknown> + 0
0x116F804C - <unknown> <unknown> + 0
0x09C5CB60 - <unknown> <unknown> + 0
0x00ADC260 - LabVIEW <unknown> + 0
0x0008D8EC - <unknown> <unknown> + 0
*** Dumping Bread Crumb Stack ***
#** sanity checking heap: "N:\ATEST\Automation\PAT_2.0\Working_Source\PAT_Ver2\Matrix left divisionMM_general_direct.vi"
#** Saving: "N:\ATEST\Automation\PAT_2.0\Working_Source\PAT_Ver2\Matrix left divisionMM_general_direct.vi"
*** End Dump ***

Hi,
Looks like you have an insane object error. Check out the following: http://digital.ni.com/public.nsf/allkb/AFA28DCC3DE89839862566B200594E8C?OpenDocument
Since the errors are DWarns (warnings), you probably don't have anything to worry about unless they keep coming up. Usually they will be fixed automatically. If it comes up repeatedly, let us know.
Regards,
Jeremy_B
Applications Engineer
National Instruments

Fpsane.cpp

After changing the History chart length in waveform chart and trying to save the vi, an error message popped up and it reads as follows,
Fatal Internal Error: "fpsane.cpp", line 397
LabView 8.0
Can anyone tell me what the problem is?

I also get this error, which is totally annoying.
I am currently working with some classes into a shared variable. After I add the variable to to routine, the LabView becomes really slow and crashes finally with the mentioned error.
This bug seriously hampers my development progress!
Bart
Logfile:
#Date: 2008 Feb 19 10:27:30 AM
#OSName: Windows NT
#OSVers: 5.1
#AppName: LabVIEW
#Version: 8.2
#AppKind: FDS
#AppModDate: 07/27/2006 11:08 GMT
.\diagram\proptype.cpp(306) : DWarn: typeprop caused typeprop a third time! give up
$Id: //labview/branches/Europa/dev/source/diagram/proptype.cpp#79 $
0x0080305A - LabVIEW <unknown> + 0
0x00D128A8 - LabVIEW <unknown> + 0
0x00D13E4A - LabVIEW <unknown> + 0
0x00C2AA85 - LabVIEW <unknown> + 0
0x00F31429 - LabVIEW <unknown> + 0
0x00F72B79 - LabVIEW <unknown> + 0
0x0123EF6B - LabVIEW <unknown> + 0
0x055D6CA4 - lvMax <unknown> + 0
0x0559CF80 - lvMax <unknown> + 0
0x748B560C - <unknown> <unknown> + 0
*** Dumping Bread Crumb Stack ***
Loading Z:\bart\LabVIEW\projects\CDM waveform monitor\1.05 LV8.2\Main window 800x600.vi
*** End Dump ***
.\diagram\proptype.cpp(306) : DWarn: typeprop caused typeprop a third time! give up
$Id: //labview/branches/Europa/dev/source/diagram/proptype.cpp#79 $
0x006C03F6 - LabVIEW <unknown> + 0
0x006C01C2 - LabVIEW <unknown> + 0
0x006C06CC - LabVIEW <unknown> + 0
0x00C38C46 - LabVIEW <unknown> + 0
0x00C48ADE - LabVIEW <unknown> + 0
0x00C497C6 - LabVIEW <unknown> + 0
0x004CCB39 - LabVIEW <unknown> + 0
0x004D7C95 - LabVIEW <unknown> + 0
0x004DAF97 - LabVIEW <unknown> + 0
0x004E10B1 - LabVIEW <unknown> + 0
0x00C14A89 - LabVIEW <unknown> + 0
0x00C14C90 - LabVIEW <unknown> + 0
0x00C172E6 - LabVIEW <unknown> + 0
0x008032EF - LabVIEW <unknown> + 0
0x00D128A8 - LabVIEW <unknown> + 0
*** Dumping Bread Crumb Stack ***
Loading Z:\bart\LabVIEW\projects\CDM waveform monitor\1.05 LV8.2\Main window 800x600.vi
*** End Dump ***
.\diagram\proptype.cpp(306) : DWarn: typeprop caused typeprop a third time! give up
$Id: //labview/branches/Europa/dev/source/diagram/proptype.cpp#79 $
0x006C03F6 - LabVIEW <unknown> + 0
0x006C01C2 - LabVIEW <unknown> + 0
0x006C070A - LabVIEW <unknown> + 0
0x00B7BA47 - LabVIEW <unknown> + 0
0x00CA8CCF - LabVIEW <unknown> + 0
0x006C055A - LabVIEW <unknown> + 0
0x006C01C2 - LabVIEW <unknown> + 0
0x006C06CC - LabVIEW <unknown> + 0
0x00C38C46 - LabVIEW <unknown> + 0
0x00C48ADE - LabVIEW <unknown> + 0
0x00C497C6 - LabVIEW <unknown> + 0
0x004CCB39 - LabVIEW <unknown> + 0
0x004D7C95 - LabVIEW <unknown> + 0
0x004DAF97 - LabVIEW <unknown> + 0
0x004E10B1 - LabVIEW <unknown> + 0
*** Dumping Bread Crumb Stack ***
Loading Z:\bart\LabVIEW\projects\CDM waveform monitor\1.05 LV8.2\Main window 800x600.vi
*** End Dump ***
.\diagram\proptype.cpp(306) : DWarn: typeprop caused typeprop a third time! give up
$Id: //labview/branches/Europa/dev/source/diagram/proptype.cpp#79 $
0x006C03F6 - LabVIEW <unknown> + 0
0x006C01C2 - LabVIEW <unknown> + 0
0x006C06CC - LabVIEW <unknown> + 0
0x00C38C46 - LabVIEW <unknown> + 0
0x00C14B7B - LabVIEW <unknown> + 0
0x00C14C90 - LabVIEW <unknown> + 0
0x00C172E6 - LabVIEW <unknown> + 0
0x008032EF - LabVIEW <unknown> + 0
0x00D128A8 - LabVIEW <unknown> + 0
0x00D13E4A - LabVIEW <unknown> + 0
0x00C2AA85 - LabVIEW <unknown> + 0
0x00F31429 - LabVIEW <unknown> + 0
0x00F72B79 - LabVIEW <unknown> + 0
0x0123EF6B - LabVIEW <unknown> + 0
0x055D6CA4 - lvMax <unknown> + 0
*** Dumping Bread Crumb Stack ***
Loading Z:\bart\LabVIEW\projects\CDM waveform monitor\1.05 LV8.2\Main window 800x600.vi
*** End Dump ***
.\diagram\proptype.cpp(306) : DWarn: typeprop caused typeprop a third time! give up
$Id: //labview/branches/Europa/dev/source/diagram/proptype.cpp#79 $
0x006C03F6 - LabVIEW <unknown> + 0
0x006C01C2 - LabVIEW <unknown> + 0
0x006C06CC - LabVIEW <unknown> + 0
0x00B7BA5D - LabVIEW <unknown> + 0
0x00803579 - LabVIEW <unknown> + 0
0x00D128A8 - LabVIEW <unknown> + 0
0x00D13E4A - LabVIEW <unknown> + 0
0x00C2AA85 - LabVIEW <unknown> + 0
0x00F31429 - LabVIEW <unknown> + 0
0x00F72B79 - LabVIEW <unknown> + 0
0x0123EF6B - LabVIEW <unknown> + 0
0x055D6CA4 - lvMax <unknown> + 0
0x0559CF80 - lvMax <unknown> + 0
0x748B560C - <unknown> <unknown> + 0
*** Dumping Bread Crumb Stack ***
Loading Z:\bart\LabVIEW\projects\CDM waveform monitor\1.05 LV8.2\Main window 800x600.vi
*** End Dump ***
.\diagram\proptype.cpp(306) : DWarn: typeprop caused typeprop a third time! give up
$Id: //labview/branches/Europa/dev/source/diagram/proptype.cpp#79 $
0x006C03F6 - LabVIEW <unknown> + 0
0x006C01C2 - LabVIEW <unknown> + 0
0x006C06CC - LabVIEW <unknown> + 0
0x00B7BA5D - LabVIEW <unknown> + 0
0x00CAA12C - LabVIEW <unknown> + 0
0x00CA8FA3 - LabVIEW <unknown> + 0
0x00CA9515 - LabVIEW <unknown> + 0
0x00CA9F42 - LabVIEW <unknown> + 0
0x00D13F2F - LabVIEW <unknown> + 0
0x00C2AA85 - LabVIEW <unknown> + 0
0x00F31429 - LabVIEW <unknown> + 0
0x00F72B79 - LabVIEW <unknown> + 0
0x0123EF6B - LabVIEW <unknown> + 0
0x055D6CA4 - lvMax <unknown> + 0
0x0559CF80 - lvMax <unknown> + 0
.\typedesc\TDOMIdRefnum.cpp(1373) : DWarn: Insane dataspace: contexts do not match for udclass type at data=0x08f820f0
$Id: //labview/branches/Europa/dev/source/typedesc/TDOMIdRefnum.cpp#23 $
0x00501B06 - LabVIEW <unknown> + 0
0x0050339B - LabVIEW <unknown> + 0
0x0112DFDA - LabVIEW <unknown> + 0
0x010C452B - LabVIEW <unknown> + 0
0x010C452B - LabVIEW <unknown> + 0
0x00C501E2 - LabVIEW <unknown> + 0
0x0076BB5A - LabVIEW <unknown> + 0
0x0076FCD9 - LabVIEW <unknown> + 0
0x00C05721 - LabVIEW <unknown> + 0
0x0076CFE5 - LabVIEW <unknown> + 0
0x00C05721 - LabVIEW <unknown> + 0
0x0076CD42 - LabVIEW <unknown> + 0
0x007707DC - LabVIEW <unknown> + 0
0x00CA9A5E - LabVIEW <unknown> + 0
0x00CAA33B - LabVIEW <unknown> + 0
*** Dumping Bread Crumb Stack ***
sanity checking heap Z:\bart\LabVIEW\projects\CDM waveform monitor\1.05 LV8.2\Main window 800x600.vi
sanity checking Z:\bart\LabVIEW\projects\CDM waveform monitor\1.05 LV8.2\Main window 800x600.vi
*** End Dump ***
Insane object at FPHP+10C in "Main window 800x600.vi": {dso } (0x200): Panel (FPSC)
.\panel\fpsane.cpp(392) : DAbort: Fatal insanities(0x200) exist in ReportInsanities, 'Main window 800x600.vi'
$Id: //labview/branches/Europa/dev/source/panel/fpsane.cpp#35 $
0x0076CEF3 - LabVIEW <unknown> + 0
0x007707DC - LabVIEW <unknown> + 0
0x00CA9A5E - LabVIEW <unknown> + 0
0x00CAA33B - LabVIEW <unknown> + 0
0x00CA8FA3 - LabVIEW <unknown> + 0
0x00CA9515 - LabVIEW <unknown> + 0
0x00CA9F42 - LabVIEW <unknown> + 0
0x00D13F2F - LabVIEW <unknown> + 0
0x00C2AA85 - LabVIEW <unknown> + 0
0x00F31429 - LabVIEW <unknown> + 0
0x00F72B79 - LabVIEW <unknown> + 0
0x0123EF6B - LabVIEW <unknown> + 0
0x055D6CA4 - lvMax <unknown> + 0
0x0559CF80 - lvMax <unknown> + 0
0x748B560C - <unknown> <unknown> + 0
*** Dumping Bread Crumb Stack ***
sanity checking heap Z:\bart\LabVIEW\projects\CDM waveform monitor\1.05 LV8.2\Main window 800x600.vi
sanity checking Z:\bart\LabVIEW\projects\CDM waveform monitor\1.05 LV8.2\Main window 800x600.vi
*** End Dump ***
Message Edited by Bart_NLD on 02-19-2008 03:37 AM

Windows LV6.0 running on Linux Wine: config.cpp error (line 404)

Have anyone tried to run LabView (Windows version) under Linux using the Wine "emulator"?
Trying this on Debian Woody, with a Win98 install of LabView 6.0 returns:
config.cpp error (line 404)
I tried to search for such a file on both Win/Linux partitions: there's none.
So how am i gonna check this line 404?
Any clue would be strongly welcome!

I agree with Labviewguru about getting Labview for Linux. The only
problem is that you have to dish out $2000 or $3500. They don't have a
Base package.
I'm not sure if NI recomends a particular window manager but I do know it
will run on any of them. In an extreme case I used it on a PII 233MHz,
64MB ram, and a 300 MB disk. It was a Slackware distro using the fvwm2
window manager. Ran great. Presently I run it with Gnome.
My point is that if you have to buy a LV for Linux license, at least you
can save money buy putting it on a machine that's been used as a paper
weight for several years.
-kevin
In article <[email protected]>,
"Labviewguru" wrote:
> I don't believe you can run LabVIEW in an e
mulation environment. There
> is too much system control that LabVIEW needs a handle on to be able to
> run on an emulator.
>
> The reason you are not able to find and troubleshoot that file is
> because it is part of the source code for LabVIEW, and doesn't exist
> except in a super secret vault which may or may not be located in Austin
> Texas...
>
> Are you aware that there is a version of LabVIEW for Linux? I believe
> that they recommend running KDE or similar GUI, but check on the support
> website for that at ni.com/linux.
>
> I hope that was enough of a clue...

Labview 6.0.2 patch does not remove my "image.cpp" error

I have an industrial PC with the following characteristics:
* Sharp LQ10D367 10.4" TFT screen, running a VGA driver (16 colours only option)
* ROBO 608, Industrial SBC motherboard with onboard video driver, from Chips and Technologies, 69000; 2MB onboard video memory
The standard VGA driver is the most recent driver, and in fact the only one available for this hardware.
Labview 5.1 runs without problem on this machine, but when I loaded Labview 6 (with the 6.0.2 patch) it came up with an "image.cpp error, line 4150" every time I tried adding a graph to the front panel. Changing the screen acceleration properties did not make any difference.
Though I have gone back to version 5.1
for the time being, my application would benefit substantially from the current version.
Are there any fixes for this, or is Labview 6 simply not compatible with VGA screen drivers?
Thanks,
Jo

I have LV6.0.2 running on an Arcom SBC with the Chips and Technology 69000
HiQVideo 2MB display chip. This chip is not capable of rendering 3D graphics.
I have noticed the CPU will go to 100% usage if I open a sub-VI panel with lots
of the new 3D graphics on it, as the display chip passes rendering off to the
main processor.
Perhaps you could try replacing the LV6 3D graphics with the older versions
that are available on the Controls pallet. At 16 colors the new graphics look
terrible anyway.
I am running the chip at 1024 X 768 screen resolution and 65K colors with
no other problems.
Regards,
Alan Brause
"Jo" wrote in message news:[email protected]..
> I have an industrial PC with the following characteristics:
>
> * Sharp LQ10D367 10.4" TFT screen, running a VGA driver (16 colours
> only option)
>
> * ROBO 608, Industrial SBC motherboard with onboard video driver,
> from Chips and Technologies, 69000; 2MB onboard video memory
>
> The standard VGA driver is the most recent driver, and in fact the
> only one available for this hardware.
>
> Labview 5.1 runs without problem on this machine, but when I loaded
> Labview 6 (with the 6.0.2 patch) it came up with an "image.cpp error,
> line 4150" every time I tried adding a graph to the front panel.
> Changing the screen acceleration properties did not make any
> difference.
>
> Though I have gone back to version 5.1 for the time being, my
> application would benefit substantially from the current version.
>
> Are there any fixes for this, or is Labview 6 simply not compatible
> with VGA screen drivers?
>
> Thanks,
> Jo

Failure: "image.cpp", error 11602

I'm developing an application in LabView and with the Web publishing tool I can visualizethe results in Internet. The problem is that I open the explorer (Netscape or Internet Explorer) the following message appears in the screen: "Failure, "image.cpp", error 11602, please contact with NI" and the explorer is close... It's labview 6.1

eddie wrote:
>
> I'm developing an application in LabView and with the Web publishing
> tool I can visualizethe results in Internet. The problem is that I
> open the explorer (Netscape or Internet Explorer) the following
> message appears in the screen: "Failure, "image.cpp", error 11602,
> please contact with NI" and the explorer is close... It's labview 6.1
A good general starting point is www.ni.com/failure . Worth looking at
the specific tips (if any) for this error, and the general tips.
Mark

Getting CURL.cpp - Error?

Hi,
I updated to Mountain Lion and when using a audio converter, Sound Grinder 3.4.4, I get an error that reads as follows:
CURL.cpp - error "No URL" when getting Full Path, in getFolderFullPathAs CString0, line: 248
Can't find any thing regarding it so if someone can enlighten me of what this is and if there is a way to fix it I would appreciate it.
Thanks!

Funny I posted this and bang I figured it out. Seems Apple is getting as bad as PC's with their convoluted errors that make zero sense. Basically Sound Grinder's path to save a file, which was set in the preferences, was deleted by the new install. So once I told it where to save it was fine.
Thanks for the quick reply by the way!

Image.cpp error

When I try to print the labview panel & diagram on my new canpn pixma iP1000 printer I get the following message. I am using LV6.0
"image.cpp error" in line 11035. Please contact ni.com. Anyone can help!

hi labview 1958,
please look here:
Failure: image.cpp, line 11035 in LabVIEW 6.0
Greets!

CPP error line 638

Hi I'm having problems with the CPP ERROR at line 638, my application includes profibus and vision. In the past when I had CPP ERRORS I had found if I sequenced the profibus VI this would eliminate the problem, however the problem has returned. I thought maybe it would be the IMAQ for the vision, so I bypassed the vision altogether, it is still in the code but not currently called or used. This hasn't helped either, I was wondering if the issue could be with too many VI's running at the same time, perhaps a memory allocation problem, but I don't know at this point.
This has been most frustrating I'm running out of I deals
Thanks
Jeffery Orn

Hello Colorado,
Normally when you are starting up LabVIEW after a crash or another error happens, LabVIEW will give you the cpp file name and the line number. You then have the option to investigate the error. This will send a report to NI so that we can work on finding why the error happens and what we can do to fix it. You should probably send that error to NI if you have not done so already.
Since the cpp file and the version of LabVIEW is missing from you post, you may want to include it. It would probably be helpful to others who may have run into this error.
I hope this helps.
Steven T.

I am gettign objheap.cpp error

i had a cluster ( pretty large one ), i added few more controls to the cluster. when i tried to open the main vi where this custer is a contol in the FP, further the cluster is used for processing(updating , reading etc)in the code.
When i try to open the main vi with the modified cluster i get objheap.cpp error and the labview closes by itself when i press ok. What could be the reason for this problem.
Is there any precaution i need ahere to when working with large clusters.

Did you get a line number? That would go a long way to finding the reason for the error.
I believe that your VI has become corrupted due to the number of controls on your front panel. Not counting the controls in the clusters, how many objects do you have?
The following link points to another link that discusses the interal errors of LabVIEW. It might help.
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RNAME=ViewQuestion&HOID=50650000000800000007510000&ECategory=LabVIEW.Datalogging+and+Supervisory+Control

How do I stop .cpp errors on opening firefox

when I open firefox I get a series of message boxes as follows:
353 regWithoutKeyname.cpp
49 dfxpRecord.cpp
234 dfxpInit.cpp
65 dfxpUniversal.cpp
86 winmmDfx.cpp
The number is the title of the box and the text is the file name. An OK button appears in each box and once pressed the next box appears.
How do I stop this from occurring ?

'''How to stop Firefox startup .cpp error dialog windows''':
* 353 ..\..\UTIL\reg\regWithoutKeyname.cpp
* 49 .\dfxp\dfxpRecord.cpp
* 234 .\dfxp\dfxpInit.cpp
* 65 \dfxp\dfxpUniversal.cpp
* 86 .\winmmDfx.cpp
'''It has nothing to do really with Firefox or plug-ins!'''
It happens in safe-mode as well. I also experienced the same problem in IE.
'''It is an Audio related problem'''
To my astonishment I could not find an answer anywhere until I realized that once upon a time I had installed DFX Audio Enhancer!
'''You have most likely [http://www.fxsound.com/index.php?vendor=23&subvendor=1&plus=2&refer=dfx11 DFX Audio Enhancer] installed''' and corrupted. Possibly due to a a deep registry clean scan which removed some keys.
'''''Simply reinstall DFX Audio Enhancer and you problem is solved!'''''
Fire fox error messages

The last time you ran LabVIEW, an internal error or crash occurred at fpsane.cpp, line 444. WHY?

I keep getting this error every time I open LabVIEW 10. Everything seems to be working fine whenever I'm using it but for some reason, LabVIEW would not close properly and linger in the background. I still see the icon in the task bar and I would sometimes close it with task manager in order to re-use LabVIEW. Does anybody out there know how to fix this problem?
Attachment:
Solved!
Go to Solution.
Attachments:
lvlog2010-11-30-09-23-36.txt ‏3 KB

Thanks Hinz,
I believe I was able to solve this particular problem myself by using "LVdebugKeys". I was able to isolate the offending VI using the debug and it came out that an old "Write Test Data to File vi." does not work well with LV2010. I replaced this vi and it no longer gives me the error.
Thank you for your help.
Attachments:
Write Test Data To File.JPG ‏3 KB

Fpsane.cpp error

Similar Messages

Maybe you are looking for