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
Similar Messages
-
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.2Dear 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 -
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 KBInsane 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 -
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 -
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 Freezer1984 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 -
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 KBThanks 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 -
I get this message when I try to save or find problems with program. After I hit the ok button 10 times it comes to failure screen and then shuts down.
Robby,
This error is related to what LabVIEW refers to as an 'insane object.' These errors, along with some possible solutions, are discussed in the following Knowledge Base article:
Knowledge Base 1F398NU0: What Does an "Insane Object" Error Mean and What Should I Do?
I recommend looking through this article and trying the various solutions listed there. Also, it appears that there was a bug in LabVIEW 6.0.x that caused these types of issues. If you are using this version of LabVIEW, you may want to consider upgrading. LabVIEW versions 6.1 and later have fixed this issue.
JohnM -
CRUSB CAN converter - DLL problem
Hi,
I am trying to read CAN data using Diga CRUSB converter. There is no labview component available thus I am forced to access data using DLL.
The problems start at retrieving the information about the device.The function is as follows:
I tried using clusters like:
The problem is that each time I try running the program, Labview crushes because of memory problems or fpsane.cpp error (when saving the unfinished vi before running).
I am not sure whether the structure used is correct or if I am missing something important.
Please find the DLL and PDF under http://www.diga.biz.pl/zip/crusb_v1/CRUSB_DLL_1_5_0.zip.
Could you please help me with this problem?Howdy!
I am not sure I have an answer but something to try would be to make your cluster of strings have dummy data in the strings. LabVIEW handles memory for you so as long as you stay in LabVIEW you do not need to worry about allocating memory. However, you are stepping outside of LabVIEW by calling into a DLL. Therefore you might need to preallocate memory for the strings. To do this, it might work if you created your strings with data in them to overwrite.
I have had some luck with this on arrays, but I have not done much with passings strings to DLLs, so this is mere conjecture on my part.
Good Luck,
Bob
Bob Young - Test Engineer - Lapsed Certified LabVIEW Developer
DISTek Integration, Inc. - NI Alliance Member
mailto:[email protected] -
"investigate previous internal error" every time I start LV 8.2.1
Hi,
Every time I start LV 8.2.1 I get a message "The last time you ran LabVIEW, an internal error or crash occurred at fpsane.cpp, line 401" and it asks if I want to investigate now. I don't have any problems while running the application, compiling it or building an installer. Does anyone have any idea what this is and if it's important?
Thanks,
Danielle
"Wisdom comes from experience. Experience is often a result of lack of wisdom.”
― Terry PratchettAlthough the VI runs, it may have a strange entry somewhere.
I did get that message a couple of times. From what I can recall it was when running omething & I had to kill the execution, or shut down LV completely. Upon re-start of LV a similar message popped up. The message did not re-appear at the next start. Maybe I inadvertently fixed it without knowing..
Try loading your VI, running it once. Saving it. Shut down LV. Restart LV. And check to see if the message continuous to appear. (you may have to repeat the steps once).
Oh... Do you have any Disable Structure which has some unfinished code iside it? I do recall that... Who knows.. (???)
RayR -
BUG found while running Matlab Script
Hi there,
I am trying a very simple vi exacmple for learning MathScript. My labview is 2011 and my matlab is 2011b, they both install in the same computer. My OS is windows 7 (64bit). I am trying to writing the following script to the block
t=0:0.01:3;
y=sin(t);
while y will be the output name of the MathScript. I connect this symbol to the a graph and run the program. For the very first time, it call out the matlab platform and run the program directly and the result was shown in the graph. However, whenever I want to modify the script and trying to save the vi, it reports some error and the program get terminated "DAbort 0x1A7102DF in fpsane.cpp". It is so weird. If I open the closed VI again, it can run without any problem for the first modificaiton, but the problem comes again if I modify the script again after the first run.Sorry, I currently don't have matlab installed, so I cannot test your VI containing the matlab script.
If I copy the text of your matlab script to a MathScript node instead, everything works just fine.
It is possible that the problem is within matlab and not a LabVIEW problem. I cannot tell.
MathScript is a LabVIEW toolkit that can run scripts with a matlab like syntax. You need to purchase it seperately (windows), but you can also download an evalution copy to try for free. The version for Mac and linux seems to be free but I have note tried. Are you a student? The LabVIEW student editions also include MathScript.
LabVIEW Champion . Do more with less code and in less time . -
Trying to investigare the error´s below but no solution was found. Would be grateful for descriptions and possible solutions. My front panel does not update (redraw) its lower part on the sceen. Same thing when not running the vi and then also the right vertical scroll bar does not work. Here are the errors to investigate:
fpsane.cpp (401)
KCode.cpp (509)
BadLinkerObjs.cpp (195)
support.cpp (6165)
Attachments:
front_panel_not_updated.JPG 268 KBSadly, there are bugs (!!) in LabVIEW, even if you are using the Spring (Service Pack 1) release. If LabVIEW crashes on you, it generally suggests you allow it to send an Error Report -- go ahead and do that, as (if nothing else) it alerts the Developers to on-going problems. In my (limited) experience, trying to track down the errors yourself is rarely productive -- most of the reported failures seem to be deep inside LabVIEW's "internals".
If you keep getting errors, and if you can figure out the "trigger" for the error, then it is not unreasonable to call NI's Support line and ask for help. If you can find a small piece of code that reliably causes the error, you can ship this off to the Applications Engineer (who can then bring it to the Developers and say "Here, Fix This!"). I've managed to find a few demonstrable "bugs", some of which were fixed in the subsequent Release ...
Bob Schor -
We've just moved from 8.2 to 8.5, including a recompile of all our .vi's.
LVMerge seemed like an exciting new feature - unfortunately, it crashes on us on all but the most trivial .vis. Only a few, specially-created (tiny, very simple) vi's do not result in a crash for us. The crash is usually not accompanied by an error message, but occasionally a message about fpsane.cpp (line 367) comes up - this is probably a separate problem, related to an (already-noted) issue in the knowledge base about locking tabs (although I'm not sure why opening in lvmerge would result in locking a tab).
We've tried a lot of different conditions - running straight from the GUI, the command line, subversion's context menu (identical to running from the command line). We've tried copy/pasting just the controls into a new .vi (for all three of the merging .vis), ommitting the code. Nothing seems to help.
We're running Windows XP, LV 8.5, using subversion for source control.
Anyone else having this issue? Any workarounds?
Regards,
DonHi Don,
I would suggest going to www.ni.com/ask and creating an email service request. You are welcome to post the files that are causing you problems to the forum, but an individual service request is probably the best avenue to resolve this issue.
Brian R.
District Sales Manager
Washington DC
National Instruments -
LabVIEW 2010 F2 - Crash - Localization issue ?
Hi fellows !
I am using LabVIEW 2010 F2 (French localized version) and I am facing this strange behavior. Can you confirm that this is a bug and / or this is because I am using a localized version of LabVIEW ?
When using the Modifications:VI property node (CTRL+SHIFT+B) and connecting its output to a case structure everything works fine (it looks like that).
But now if I change the Modifications:VI property to Modifications:Front Panel and let the output of the property node connected to the case structure, LabVIEW crashes or the broken arrow appears.
If I click on the broken arrow or try to save the VI (CTRL+S), I get the following error message :
Fpsane.cpp line 442
Thanks for your help.
Regards,
Da Helmut
Attachments:
err.PNG 11 KB
test.png 14 KB
test.vi 7 KBHi,
Thanks for the answer.
There is another bug with LabVIEW 2010 (F4 this time).
To reproduce it you have to create a (strict) type definition that consists of a cluster and put a constant which is linked to this typedef on the BD (just select the .ctl file in the BD) and then delete the type definition from the hard drive.
Close the VI that has the constant in the BD.
Re-open the VI, and in the BD, right click on the cluster constant and select "View as Icon". Now you get LabVIEW crashed. (ok it is useless doing that on a non existing typedef but this is crashing LabVIEW, so I thought this should be reported).
Keep me informed if you have any further informations about that.
Regards,
Da Helmut -
I sent an error report about this, but I was able to reproduce the bug outside my project, so I'll post it here, with all the screenshots and attachments I need to
I'll explain the procedure I used, but it's possible that a lot of steps are not needed...
Initial state (step1.png):
I have a chunk of code that includes a stacked sequence, and some wires as input. These wires ARE LABELED.
In the same VI, I have an empty state-machine kind of structure: a string case inside a while loop.
I move the stacked sequence and what's around it into the state machine (step2.png)
If I save the VI at this point, I get a crash at fpsane.cpp, line 442. If I wait long enough for the auto-save to kick in, I also get a crash.
But let's look at some symptoms... Notice on step2.png how a selection rectangle for the labels still appear at their initial location. If I unselect everything, the labels reappear on the wires, but if I try to select them, the selection rectangle still appears where it was before the move.
The crash upon saving will happen every time... Now, if I make the labels invisible before moving the chunk of code, and set them back to visible after moving the code, everything works fine.
Some specs:
LabVIEW version 10.0.1
XP 32bit SP3
Intel(R) Core(TM)2 CPU 6700 @ 2.66GHz
2 GB RAM
Edit:
If that can be of any help, this is what I received from NI after sending the bug report:
RE: (Reference#7320545) LabVIEW 10.0.1%2032-bit error log file: textmgr.cpp line 1197
In case you want to cross-reference this post to it or something... "you" referring to the NI people.
Attachments:
step1.png 44 KB
step2.png 14 KBInteresting!
If you deselect the wire labels before moving the wires there is no issue and the labels move with the wires. This is unexpected behavior. Cute bug!
this happens when moving any visably labeled wire into or out of any structure that can contain a dropped wire.
Try it yourself! the workaround is obvious- deselect wire labels before drag-drop
Jeff
Attachments:
Odd.vi 34 KB
Maybe you are looking for
-
Std report T.Code to view the Employees those are assigned to the Project
Dear Guru's, We are assigning Employeeu2019s in u201CActivityu201D u201CPersonal assignment Tabu201D, for these employees we are booking the u201CTime sheetu201D against u201CNetwork activityu201D. Are there is
-
The latest update to CC has caused brush lag across all versions of Photoshop. How can I fix this?
Ever since this past week's update to CC, I have noticed a decrease in performance across all versions of Photoshop I have installed, CS6 and CC. Many of the brushes I have, both in Photoshop's default and my own custom sets, lag horribly when drawi
-
Error while installing 11gR1 RDBMS software on 11gR2 GI
I am getting the following error while installing 11gR1 (11.1.0.6) RDBMS software on 11gR2 GI. 0. Oracle Enterprise linux 5.4 x_86_64 bit 1. cluvfy verfication is successful 2. 11gR2 GI looks fine - logged in to asm in all nodes, check the asm disksg
-
im looking to get a mac notebook and im wondering if the downloaded movies and tv shows i have can be copied to the laptop to take on the road. i currenly have them stored on an external HD right now. The other laptop may be windows (work related) an
-
Hi, I see well how to format a cell with conditions. But a whole line ? In a list of data ordered by month (8 columns) , I would like to colour the line when the month is 12. But still don't see how. Your help would be great. Thank you