Output Coercion

[EdDickens]

Has anybody ever seen a coercion dot on the output of a function?

As you see in the image, all but one of the outputs from the "Index Array" function have a coercion dot. All the indicators are doubles and the context help window verifies all the wires are doubles.



Any ideas?

Ed

Message Edited by Ed Dickens on 01-22-2006 08:53 AM

[altenbach]

I've seen similar things in the past. It's probably just a graphics glitch, and not a coercion.

(did you change the default coercion dot color from grey to orange?)

Message Edited by altenbach on 01-22-2006 10:39 AM

[EdDickens]

Yes, I change the dots color to red. Shows up better for me.

I'm sure it's just a graphics glitch too, don't know how else to explain it. But if I delete a wire, the dot goes away and comes back when re-wired. And it's really strange that the first element does not have the dot and the rest do. I'm thinking it has something to with the Shared Variable.

So what do you make of this image>



Ed

Message Edited by Ed Dickens on 01-23-2006 08:29 AM

[altenbach]

Yes, it is very strange. However, I've seen similar things pre-LabVIEW 8.0 (and thus prior to the shared varaible). I wish I could find an old example.

[Travis_M.]

Hello,

This is quite strange, I tried to reproduce this with a shared var of type double[ ] and wired the output of the read to an expanded index array with no luck.  I am curious about how your shared variable is set up.  Are you using a custom type, or using an array of double[ ]  for the type?  If you build a completely new project with a shared variable of type double[ ] and wire the output of that to an index array does this produce the same thing?  Graphics problem, or unnecessary conversion problem I'll be happy to file this if there is a problem with LabVIEW.  Please let me know if you can provide any additional information or a way to reproduce this.

Hope to hear back from you - have a great day!

[EdDickens]

I can't reproduce it either. I can't even reproduce it in the same project using the same variable. I was able to reproduce it by copying the Index Array function from that particular subVI.  I was even able to get rid of the dots by deleting the function and dropping a new one and wiring it in. I'm sure I tried that already, but maybe not.

The SV is just a double array, single process with no FIFO.

I've run into a few other odd behaviors with this application, and we've traced them back to a bad install of the last beta version of 8 that released. I had it installed and it really caused some problems. I had to uninstall all NI related software/drivers and start over, but it didn't quite cure everything. The Shared Variables is one thing I'm still having problems with. I need to format the drive and really start over, but I don't have the time.

Ed

[Ben]

Ed wrote " I need to format the drive and really start over, but I don't have the time."

Note to self: NEVER, NEVER, NEVER try a Beta version on a work machine.

The closest thing I have seen to this (but not exactly the same) involved type def's and the coercion dot was indicating the data was being cast as a type def or vise versa. Does "ctrl-h" with the wiring tool show any difference between thewire types? (No LV8 on this machine)

Ben

[Travis_M.]

Hello,

Indeed this has been seen before -- we have corrected a problem with these coercion dots on an older version of LabVIEW.  Those situations were mostly in times where the LabVIEW compiler could not distinguish the type of wire to an indicator (such as a wire from an uninitialized shift register).

With regards to the reinstall, you should not need to reformat your entire drive to start over.  If you suspect there are remains of a beta on your machine, we might have some additional ways to remove all NI software (and ALL of its components) from your machine as a last resort before a reformat.  When you get the time, I would first try the documented ways such as through add/remove programs and the blast utilities.  If that doesn’t help please create a service request to contact us directly (www.ni.com/support).  However, in this case I believe that the problem with the dots is likely a result of some sort of VI corruption and not a result of a bad LabVIEW install.  With these cases, as well as with insane objects, often deleting and replacing the bad object will correct the problem.

Hopefully this helps!  Keep me posted (so to speak) if anything else comes up-