"insane object" at Panel (FPHP)

[Jens Benecke]

Hi,

I have written a Labview + Matlab combination (Labview does the GUI and
queries instruments via GPIB, Matlab does the simulation). However, when
I run my program, if I want to save it after running it first, the whole
Labview process crashes with

"Insane Object at FPHP+DC in "komplett.vi": {dsitem} (0x400): Panel (FPSC)"

Ctrl+RUN (recompiling) results in the same thing. Clicking OK yields an
error in fpsane.cpp line 269 and would I please report this to
www.ni.com/failure, which results in a text like "this error should not
happen" but doesn't really help me resolving it. Sending a feedback mail
to NI via the contact website results in a Lotus Notes Webserver
Exception. Writing to NI by email hasn't produced an answer yet.

I tr
ied creating the VI again from scratch (on the same machine though)
which didn't change anything. I'm running 6.0i (updated to 6.0.2, didn't
change anything) on Windows 2000 on an Athlon 900. Next thing I'll try
is the Linux version of Labview if I can get it somewhere (yes, it does
exist).

I'm out of ideas, and this is my diploma thesis, and it must be finished
next week. So I'm a little bit in a hurry =;)


Any ideas? What can I do to resolve this? I put up the two VIs at
www.jensbenecke.de/labview (the associate files would be too big, you'd
need the HP oscilloscope and lots of Matlab code for it anyway) if
anybody wants to have a look.


THANK you in advance!


--
mfg, Jens Benecke /// http://www.linuxfaq.de, http://www.linux.ms
This mail is an attachment? Read http://www.jensbenecke.de/misc/outlook.html
http://www.hitchhikers.de - Die größte kostenlose Mitfahrzentrale im Internet

[Super Fly]

Generally if you get an insane object error it means something in your code has become corrupt. If caught eary you can generally delete the most recent object and replace them, however if you make many changes and forget you should really start the code from scratch being sure to not use ANYTHING from the original VI. No copy and pasting of anything.

[Jens Benecke]

Super Fly wrote:

> Generally if you get an insane object error it means something in your
> code has become corrupt. If caught eary you can generally delete the
> most recent object and replace them, however if you make many changes
> and forget you should really start the code from scratch being sure to
> not use ANYTHING from the original VI. No copy and pasting of
> anything.

Hi,

thanks for your reply. A few more questions:

- Can I open the new and the old VI at the same time or will the corruption
spread over the whole Labview session?

- Is it possible that one VI does not corrupt when it is called stand-alone,
but does throw up when it is called by another VI (with correct and the
same values, I checked that)?

- Can I assume that neithe
r the OS or the Labview installation is to blame?


Thanks!

--
mfg, Jens Benecke /// http://www.linuxfaq.de, http://www.linux.ms

"Microsoft may provide updates that will be automatically downloaded onto
your computer. These updates may disable your ability to copy and/or play
content and use other software on your computer."
-- http://bsdvault.net/article.php?sid=527&mode=&order=0

[Jens Benecke]

Super Fly wrote:

> Generally if you get an insane object error it means something in your
> code has become corrupt. If caught eary you can generally delete the
> most recent object and replace them, however if you make many changes
> and forget you should really start the code from scratch being sure to
> not use ANYTHING from the original VI. No copy and pasting of
> anything.

Hi,

I tried recreating the VI from scratch (ie. printed out the old VI,
closed Labview, opened it again, copied the elements from paper). It
didn't help. I still get the exact same error. Every time after I run
the VI (once or several times) and then want to save. Labview still
crashes and has to be killed by the task manager.

I'm beginning to suspect the Matl
ab script node is severely buggy and
broken.


--
mfg, Jens Benecke /// http://www.linuxfaq.de, http://www.linux.ms
http://www.hitchhikers.de - Die größte kostenlose Mitfahrzentrale im Internet

[Super Fly]

Are you fairly confident that the program run successfully without the matlab code? Is is possible to narrow it down to that single node? Can you also attach the code so we can look at what you are doing?

[Jens Benecke]

Super Fly wrote:

> Are you fairly confident that the program run successfully without the
> matlab code? Is is possible to narrow it down to that single node?
> Can you also attach the code so we can look at what you are doing?

Yes.

I changed the code to write a "startup.m" Matlab script, call the matlab
binary with this code (which writes another file), and read this file into
Labview.

Works perfectly (although it's slow, of course), until now.


I have a feeling that Labview's .vi files are kind of a "brain dump" (or
rather memory dump) of the current state of the VI. i.e. once something
goes wrong, it _stays_ wrong. Removing the Matlab script node in the old
code didn't keep it from crashing when I wanted to save. But recr
eating the
whole thing and not even _creating_ a Matlab node (but spending twenty
square centimeters on sticking together Matlab code strings and writing a
file, then calling Matlab externally, and reading in the resulting data
file) did.

I wish there were a concrete source code view of VIs. Simple, deterministic
plain text.
I'm not saying it's easy, but there are programs that can create a
connection plan for thousands of elements out of VHDL code, and this
doesn't look too different for me.


Thank you all for your help!


--
mfg, Jens Benecke /// http://www.linuxfaq.de, http://www.linux.ms
This mail is an attachment? Read http://www.jensbenecke.de/misc/outlook.html
http://www.hitchhikers.de - Die größte kostenlose Mitfahrzentrale im
Internet

"Microsoft may provide updates that will be automatically downloaded onto
your computer. These updates may disable your ability to copy and/or play
content and use other software on your computer."
-- http://bsdvault.net/ar
ticle.php?sid=527&mode=&order=0

[Jens Benecke]

Super Fly wrote:

> Are you fairly confident that the program run successfully without the
> matlab code? Is is possible to narrow it down to that single node?
> Can you also attach the code so we can look at what you are doing?

The code is up at www.linux.ms/labview/. There's the main script
(komplett.vi), a (working) sub-VI (messung.vi) and my new
non-matlab-script-node version (komplett_hoffentlich.vi).

I have also uploaded the auxiliary files in this directory. If you
actually understand what I'm trying to accomplish, and have some more
ideas, I'd be happy to hear about them. Have fun! 🙂


--
mfg, Jens Benecke /// http://www.linuxfaq.de, http://www.linux.ms
http://www.hitchhikers.de - Die größte kostenlose Mitf
ahrzentrale im Internet

[R.G.S.]

Jens Benecke wrote:
> Super Fly wrote:
>
>
>>Generally if you get an insane object error it means something in your
>>code has become corrupt. If caught eary you can generally delete the
>>most recent object and replace them, however if you make many changes
>>and forget you should really start the code from scratch being sure to
>>not use ANYTHING from the original VI. No copy and pasting of
>>anything.
>
>
> Hi,
>
> I tried recreating the VI from scratch (ie. printed out the old VI,
> closed Labview, opened it again, copied the elements from paper). It
> didn't help. I still get the exact same error. Every time after I run
> the VI (once or several times) and then want to save. Labview still
> crashes and has to be killed by t
he task manager.
>
> I'm beginning to suspect the Matlab script node is severely buggy and
> broken.
>

I can't help much, but there are a couple things to try.
1) replace the matlab script with a very simple matlab script
(i.e. calc the mean of a vector of numbers), and call it from your
labview code. (i.e. try to eliminate matlab from the possible
causes).
2) if (1) does not cause the crash, reproduce the matlab script
with the same IO (but no complex calculations, just use default values). This will isolate
whether its the parameter passing that causes the crash.

3) if you still see the crash regardless of what you do with matlab,
then start stripping down your labview code to the smallest example
that still causes the crash. Maybe rewriting the code, and changing
controls/indicators etc may solve the problem.

Cheers,
bob