LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

I can't fix my insane object error!

Hi all,

I'm getting the following error messages when I try to save my VI after running it:

Insane object at FPHP+208BC in "backup.vi":{sub}(0x10): Scale (DDO)

" " FPHP+20634 " " Waveform Chart (DDO)
" " FPHP+20E78 " " Scale (DDO)
" " FPHP+20CB0 " " Waveform Chart (DDO)

I read all of the info on insane objects available on the web site, and followed the instructions to fix the problem when it first appeared last week. I deleted and recreated the last charts and scales that I made, and eventually I recreated every chart and scale. This seemed to fix the problem, as I had no more error messages...until this morning.

I'd like to avoid having to recreate everything all over
again if possible. It's probably best that I send the VI to someone to take a look at and try to fix. We're using an opto22 interface for our readings, if that helps at all. Hopefully someone can help me fix this problem....

Thanks,

Andrew Poyton
McMaster University
Hamilton, Ont.
0 Kudos
Message 1 of 3
(2,733 Views)
Send your VIs to tech support, who can fix that for you. www.ni.com/ask.

You'll need to include any subVIs: from the File Menu choose Save with
Options, & choose Development Distribution.

Mark
0 Kudos
Message 2 of 3
(2,733 Views)
Andrew,
I was having a very similar error this morning. It turns out that the source of my problem was the range on the y-axis on one of my waveform charts was messed up. I had it set to autoscale and had been running the program and it plotted some really huge numbers because of a calculation error in one of my formulas. In any case, it seemed to run fine despite plotting bogus information, but when I went in to make changes and then tried to save I received the error messages similar to your situation and could not save. I fixed it as follows: I simply changed the values on the upper and lower end of the y-axis to something reasonable like +10 and -10. Then I tried to save and it worked just fine.

So you might take a good look at your waveform plots and check
the values on all of the ranges. I hope that helps you.

tony
0 Kudos
Message 3 of 3
(2,733 Views)