notification problem! Is it a bug?

[astroboy]

I am puzzled over the wiring problem, using the notification features. I do not understand what the error explains. Could it be a bug?

I have done the same similar wiring, using notifier and copied the same wiring  in the new file. Nothing  was found to be faulty.

Take a look at the attacheds.

[Darren]

Notice how the tunnel causing the problem is white?  That means it's an output tunnel (as the error mentions), even though it doesn't look like it.  The reason is that you have two tunnels sitting right on top of each other.  See for yourself...click the offending tunnel with your positioning tool and use the arrows to move it up...you'll see another tunnel underneath it.  Delete the extra tunnel and wire from the one that's left, and you should be fine.

Oh, and by the way...the VI Analyzer Toolkit (http://www.ni.com/toolkits/vi_analyzer.htm) ships with a test called the Hidden Tunnels test that would have detected this problem for you.

Good luck,

-D

Message Edited by Darren on 01-17-2006 11:17 PM

[astroboy]

Oh I see

Thanks. I have been looking for the errors only to find that it's the tunnel node!

Thanks for linking me to LabVIEW VI Analyzer Toolkit. But I don't understand why the VI analyser is not packed together with Labview since it is a part of debugging. Why the extra cost to pay!?

I am sure that C++ or VB programming software does not with extra cost for another debugger program. Why squeeze extra cost out of companies as we know that the softwares are most expensive than others although they are the best in terms of speedy development and building applications.

regards,

Clement

[Darren]

So I helped you figure out your problem, but just because NI charges extra for the VI Analyzer Toolkit I only get 3 stars?  I see how it is... 😉

Seriously though, I can't speak for our marketing department, but there is a line they have to draw at some point as to what functionality is included in LabVIEW and what functionality comes at an extra price in the form of a module or toolkit.  Every company has to do this to some degree.  I would argue that some of the "features" that come along with an MSDN subscription are invaluable to some Visual Studio developers, yet Microsoft charges for those.  At any rate, the VI Analyzer is included in the NI Developer Suite, so it's not as if every LabVIEW user is having to pay the individual price for each LabVIEW toolkit they want and need.

Again, my perspective on this issue isn't really that valuable, since I'm only writing the software, I'm not making the decisions as to how it is marketed and sold.

-D

[devchander]

Hey Darren,

These 5 stars from me are intended to  keep u in good spirits while posting 'weekly nuggets'!

ciao

Dev

[rolfk]

---

@astroboy wrote:

Thanks for linking me to LabVIEW VI Analyzer Toolkit. But I don't understand why the VI analyser is not packed together with Labview since it is a part of debugging. Why the extra cost to pay!?

I am sure that C++ or VB programming software does not with extra cost for another debugger program. Why squeeze extra cost out of companies as we know that the softwares are most expensive than others although they are the best in terms of speedy development and building applications.

---

This analogy does not work well. In C you have code analyser Toolkits as well, but none of them has ever been included in any C compiler I have used. There are some open source code analysers and some commercial ones but they have definitely always been independant of the C development environment (Borland, Watcom, MSVC, GCC, MPW, Xcode)  I used.
And the compiler errors for syntax errors can sometimes be so cryptic that it is almost impossible to understand what is wrong. In comparison LabVIEWs compiler error indication is at most times clear and obvious and sometimes to the point of being brutal.

So in C you either have to pay too, or go at least through the hassles of installing some more or less simple to install open source analyzer (and some of them can really be a hassle to install). I wouldn't know about VB as I prefer to work with professional software, but I'm sure that VB does not have a code analyzer on board out of the box.

Rolf Kalbermatter

Message Edited by rolfk on 01-18-2006 09:59 AM

Message Edited by rolfk on 01-18-2006 10:00 AM

[Ben]

Rolf wrote

" I wouldn't know about VB as I prefer to work with professional software, ..."

Thanks Rolf! I have a new print out to decorate my cubicle wall.

Ben

BTW

Darren,

WE will take care of you. "incorrect" ratings are corrected by the "frequent flyers".

Ben