Looking for a LabVIEW "Comparison Tool"

[jp2labview]

nrp wrote, "is the zero in the create user event cluster for the timeout?"

LOL. I have no idea! The Course Manual just says to put one there, and doesn't go into describing why it was put there or what the actions do. This manual is from NI for their LV product, which they should be embarrassed about.

altenback wrote, "You have a breakpoint set!"

Yes, I set this trying to find out what was going wrong, but it hasn't helped any.

Currently, I'm comparing the printouts of the two VIs. Very tedious, but it's all I've got!

[LabViewGuruWannabe]

Do you have a link to this course manual?

This is the first time I've heard someone say that NI should be embarrased about their products, and I think that after you've spent some real time learning to use LabVIEW, just like any programming language, you will soon think to yourself, "Wow, I remember when I didn't know how to do that, and now its so easy."

I would suggest skipping this exercise and going on to something simpler. Once you get a better understanding of the basic structures by themselves (like case statements and event stuctures) you can then play with putting them together in a more advanced program.

B-)

[altenbach]

---

jp2labview wrote:
Yes, I set this trying to find out what was going wrong, but it hasn't helped any.

---

That would have been useful to know. 😄

As has been mentioned, LabVIEW professional has a comparison tool. One possible problem are type mismatches. For example the VI shown in the image has all input coerced to something else. Try to see exactly what kind of inputs it expects and what kind of inputs it actually gets.

 

Message Edited by altenbach on 11-14-2007 10:42 AM

[jrpe]

On a side note, when debugging VIs it won't work very well to study printouts. There are some features of nodes that cant be seen visually, and you need to check their Properties menu to see if they are in fact equivalent. Probably the best way for you to find the difference between the two programs is to run them with highlight execution enabled. Then you can either see where your program fails, or at the very least, where exactly your program stops behaving like the solution program.

As previously mentioned, if there are a lot of VIs that you dont understand and you just dropped in there to follow the instructions, and if you are new to labview, you may want to start with some easier programs that are less involved. Figure out what each vi does (Ctrl + H turns on context help which is useful) and you will learn a lot faster.

Its like when you learn to drive a car, you start by practising in a parking lot, checking out each feature, before you eventually get out on the highway where you have to make use of all those features at the same time.

[TCPlomp]

I have followed the same course and had no problem (but I knew LabVIEW already)
If you want to post images of your code you can look here
The '0' as questioned is just a default value nothing special.

Can you tell us if your breakpoint is hit?
If no than you are in another case in the consumer loop, to find out which place a probe over this:

at the output of the Command wire.

Good luck,

Ton


Message Edited by TonP on 11-14-2007 08:03 PM

[MichaelAivaliotis]

For those that want to follow along and possibly help, all the course materials for this discussion are available here (LV7.1):

ftp://ftp.ni.com/support/customer_education/Course_Material/LV_Intermediate_1/Version_7.1/CD%20Image

[jp2labview]

For the record, I took LabVIEW Basics 1 & 2 early this year, and now I am moving on to the Intermediate courses.

I'm getting lots of replies - more than I seem able to reply to.

The breakpoint *is* being reached whenever I hit the "stop" button.

I don't really understand all of what the manual is trying to do, but I was told to just follow along. So, when it comes to debugging, I'd like to see what their version looks like and compare it to what I did. Perhaps (probably) I connected a wire to the wrong terminal.

altenback: How did you include replies like that? [code]This is a reply?[/code]

[jp2labview]

I tried fixing some things, but I'm still having the same problems.

When running the code, I Play through once completely. This works. I Play about half way, then Stop, then try to Play again. The application stops responding.

I go to the Block Diagram, and enable Highlight Execution. Here, I see that I am somehow stuck in an endless loop under the ["Initialize", Default] case [add] in the "consumer loop" [/add] and there is an Error being propagated: ERR (-816).

When I put a probe on the error wire, I get the following:

---

error out [1] wrote:

Error -816 occurred at Timed structure(s): Fade

Possible reason(s):

LabVIEW: Timed structure aborted or attempted to execute another iteration of the following aborted Timed Loop.

Timed structure(s): Fade

---

This is something I knew, but the solution that was provided with the course seems to work just fine when I do this.

I'm pretty sure I did something wrong, but I don't know how to tell what that was.

Message Edited by jp2labview on 11-14-2007 02:55 PM

[citizenDAK]

>  To tst: I tried doing the compare, but when I went to Select... the file to compare it with, the C:\Solutions folder was not among the choices. [...]

First, open both VI's to be compared.  (May need to rename one of them, if they're both versions of the same file.)

Only after that, you can open the Tools -> Compare VI's dialog.  (The SELECTION list is limited to in-memory VI's, it seems.)

[p.s.  I have LabVIEW 9-sp1 Pro open at the moment.  Perhaps this limitation was later removed, I haven't checked.]

[camerond]

You might not find the OP replying, it's been almost 6 years since the last post in this thread.

Cameron