Insane error

[Pollux]

I keep geting this "insane" error and LV closes.

Does anybody know where that comes from?

[Aristos Queue]

QUOTE (Pollux @ Aug 13 2008, 04:22 AM)

I keep geting this "insane" error and LV closes.

Does anybody know where that comes from?

It means that some part of your VI has a configuration that LV has no idea what to do with -- such as a bit setting that only has meaning for numerics being set on a string control. Search around on LAVA for "insane object" and somewhere you'll find a thread that talks about identifying the offending item and deleting it. Ultimately this is an NI error that should be CAR'd (by posting at NI.com) so it can be investigated and fixed.

[jzoller]

http://wiki.lavag.org/Insane_Objects

[LAVA 1.0 Content]

QUOTE (jzoller @ Aug 13 2008, 10:23 AM)

http://wiki.lavag.org/Insane_Objects

this is the best part when u end up with a insane error

Most of the time, deleting the offending object and recreating it from scratch is sufficient to fix your VI and allow you to continue working.

So when ever i used to encounter this problem (and the interesting thing is that this insane error is used to happen with 7 and 7.1 version and i never encountered so far with 8.2 and 8.5). i used to delete a wire branch or control or indicator one by one , save the application, rewire the deleted objects and save and run it. And it used to work fine. This used to be tedious process and as a short cut i would copy the entire block diagram in to a new vi then used to delete half of the block diagram objects, which would let me know in a faster way where this insane object is in the BD.

[Neville D]

QUOTE (guruthilak@yahoo.com @ Aug 18 2008, 11:49 PM)

this is the best part when u end up with a insane error

Most of the time, deleting the offending object and recreating it from scratch is sufficient to fix your VI and allow you to continue working.

Since the error message pts to the Table Control, delete and replace it (and the associated wire branches on the diagram too, for good measure) and it should be fixed.

There is an ini key that you can add to LabVIEW.ini to enable a bit more info for these sorts of messages to help identify which object is causing the error and whether its a BD or a front panel issue.

Neville.

[Val Brown]

QUOTE (Neville D @ Aug 19 2008, 08:11 AM)

...There is an ini key that you can add to LabVIEW.ini to enable a bit more info for these sorts of messages to help identify which object is causing the error and whether its a BD or a front panel issue.

Neville.

And that key would be?

[Neville D]

QUOTE (Val Brown @ Aug 19 2008, 08:21 AM)

And that key would be?

LVdebugKeys=True

[Val Brown]

QUOTE (Neville D @ Aug 19 2008, 10:30 AM)

LVdebugKeys=True

Thanks for posting that. I think it's clearest to actually provide the specific response/answer when it's known.

[Neville D]

QUOTE (Val Brown @ Aug 19 2008, 11:06 AM)

Thanks for posting that. I think it's clearest to actually provide the specific response/answer when it's known.

I'd forgotten it. I just googled LV ini keys and found it from http://labview.brianrenken.com/INI/' rel='nofollow' target="_blank">Brian Renken's page.

N.

[JiMM]

QUOTE (Neville D @ Aug 19 2008, 01:30 PM)

LVdebugKeys=True

Any idea what versions of LV this key is valid for?

[crelf]

QUOTE (Neville D @ Aug 19 2008, 02:51 PM)

I'd forgotten it. I just googled LV ini keys and found it from Brian Renken's page.

When in doubt, search the LabVIEW Wiki! Brian's pages are out of date, and he graciously allowed us to use his pages to build a more managable version here. There's also some info of insane objects and how to use the heap-peek here.

[PJM_labview]

QUOTE (JiMM @ Aug 19 2008, 11:54 AM)

Any idea what versions of LV this key is valid for?

Works all the way to up to LabVIEW 8.6 (which is the latest LV release at the time I am making this post).

PJM

[Aristos Queue]

QUOTE (JiMM @ Aug 19 2008, 01:54 PM)

Any idea what versions of LV this key is valid for?

It is valid at least back to LV5.0. I suspect it goes back to 2.5, but I've never tried using LV that far back.