Block Diagram Warning

With Warnings turned on, I get an 'Event Data Node: cluster has unnamed or duplicate named elements' warning for every event case with the detail of 'The cluster being bundled or unbundled by name has elements with no name, or elements with the same name.' I cannot find the reason for this to happen. Any clues? LV2011
Solved!
Go to Solution.

I was able to duplicate using two approaches.
1) Enable show warning then restart LV
2) Add a dynamic event node and wire reg to same. After saving we get teh message. Checking using float-over wiretool help shows it is lableld.
Next
1) Register for a value change of a cluster on the FP.
Warnins only show up after a save.
So far it looks like all cluster invloved in the event workings (no not data being passed through) give me the error.
I checked the cluster value change event in LV 6i and it is fine there so....
I call it a bug.
R&D will probably call it a nucence bug but it is a bug.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Similar Messages

What is the best way to keep the block diagram/ front panel clean?

Hello,
I am relatively new to Labview so I'm not able to tell if I'm overcomplicating my programs or making my block diagram too cluttered. I was wondering if there were some ways to tell whether I could simplify my programming just by looking at it (perhaps only experience helps for these things) ?
I have attached my VI here. Currently, it has the capability to monitor the voltage and current from two motors. On display, you can see a indicator with the voltage and current values and there are charts toward the bottom that can display waveforms from different motors with a drop down menu.
The front panel is rather clean in my novice opinion, but the block diagram seems messy to me, just at first glance. I foresee a problem occuring in the future however. In the future, I will have to scale the VI to monitor 50 motors. All the programming will be the same as the one I have now, except it will have 50 indicators and unfortunately 50 times pretty much everything. I would like to avoid this, but I'm not sure how I could.
I am using a USB 6009. I am using its four differential inputs to monitor the voltage and current of two motors. In the future, I will be getting more DAQ units (25 total because 2 motors can be monitored for each DAQ). The new DAQs will help will help with more resource space, but I think complicate things with the additional potential of 24 more DAQ Assistants (as used in my code).
Thanks for any help you might be able to provide!

It usually is mainly experience that will teach you the best methods to make your code look pretty. I don't know anyone who is proud of their first from-scratch application. There are a few resources out there to help with best practices, like this group on ni.com, but you'll learn the most from your own development.
Your front panel looks great. FPs in general are really up to you. You can make it look as ugly or pretty as you want. When you have some duplicate controls and indicator groups, you should utilize clusters and arrays to simplify. You could use a little bit of cleanup in that regard, but not much. Also, personally, I hate reading red text unless it's a warning of some sort.
Your block diagram could use some cleanup in a modularity sense. You have a lot of repeated code, which you could consolidate in to a subVI that is used in multiple locations, or in a For loop. A general rule of thumb is to keep your block diagram within a single monitor. You shouldn't have to scroll. Your application is pretty simple, so it's hard to mess it up
Here are some specifics about your block diagram:
Right click your terminals on the block diagram and uncheck "View As Icon". You're welcome.
Duplicate operations on each waveform "(x*2-4)/16": create subVI and/or run the waveforms through a For loop.
You do a lot of 2-element arrays and then indexing. Just replace those with a Select node based on the numeric.
All of your code is running every time, including your property nodes at the bottom, which is unnecessary. As you learn LabVIEW architectures, you will learn how to bypass this with initialization and exiting code, but for now you should put a case structure around those for only when the motor numbers change.
I'm not sure how you're timing your main loop, but you should put a delay in there because you don't need the DAQmx node to be pulling as fast as your CPU will allow.
There are free intro videos you can watch to learn what NI would suggest in terms of coding and teach you some of the basic features and such. Here's a three hour course, and here's a six hour course.

'Control terminals on connector pane not on top level block diagram.' comment on CLD report

Hello All
Could anybody enlighten me please , what does that comment mean on CLD report
'Control terminals on connector pane not on top level block diagram.
Does it mean that some terminals are hidden within some case structures and not showing on block diagram without going into case structures or by 'top level block diagram' it means
main.vi and controls on main.vi must also be connected to its connector pane?
Thank you
K.Waris
Solved!
Go to Solution.

For one thing it means that they run VI analyzer on your VIs since that is a verbatim warning that you receive. It simply means a terminal which is wired to the ConPane is not on the top level diagram, ie. inside a case structure.
As to why it is often not a good idea to do this read this classic thread:
http://forums.ni.com/t5/LabVIEW/case-structure-parameter-efficiency/m-p/382516#M191622

Close front panel but leave open block diagram

Is there a way to do this? I would like to have my block diagrams of a few subvi's open but front panels closed so my task bar isn't so cluttered. It's not a big deal, I was just curious
CLA, LabVIEW Versions 2010-2013

Chris_VH wrote:
No current way unfortunately.
A colleague and I actually just put in a product suggestion for this yesterday.
So if they fix this do I give you or them credit for the solution?
CLA, LabVIEW Versions 2010-2013

I created boolean references in my main vi block diagram and copied them to my sub vi front panel. when wire my reference in my main vi to one the input node of the sub vi the wire is broken. the error says its a class conflict why?

i created boolean references in my main vi block diagram and copied them to my sub vi front panel. when wire my reference in my main vi to one the input node of the sub vi the wire is broken. the error says its a class conflict why?

Expanding and clarifying what BJD said;
After you create the temporary sub-VI that BJD mentioned, open its front panel and copy the reference control that LV created when it created the sub-VI.
This reference control will be correct class etc that you need. Use the control to replace the original control that you were attempting to wire up.
The technique of "create sub-VI...copy" always works for me.
There is one more thing that you should watch out for.
The mechanical action of the boolean can not be set for latch action when attempting to read the value using a value property node.
Trying to help,
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Block diagram wont open properly

I have written a big labview program for my application. I have been workig on it for 6 months. I keep adding the peice of code every day and save it with a new name every week.
At one point when I added some code into my program, the block diagram started acting weird and wont let me work on the program easily. For If I add an add function, it would take time and insert this function a couple of inches away where I pionted my cursor. Another issue was that; if I add a while loop or for loop or any other structure it would take time and one added it would add a couple of inches away and expand the main program window (Block Diagram) too.
since then, I started using my company's laptop to develop the code. I have no issues with that lap top till today.
But now when I tranfer this program back to my desk top. It wont open the Block Diagram and wont let me edit it. When I try to open the block diagram. the window appear black out and the LabView stops working.
Is this issure ralted to the graphics of my compute or any thing else? Please help me. Thanks
Mansoor

There is a maximum size that a VI can be. What that exact size is I don't know. It does sound like you have one HUGE VI. If that is the case you really need to think more about using subVIs. It will make your program much easier to maintain and extend.
Also, rather than renaming it once a week you should consider using source code contol. Even if you are the only developer it is a much better way to manage your code. SVN is free and very easy to set up. If you do use source code control make sure you separate the compiled code from the source code. This is an option in the VI properties.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot

How can I open a vi and show the block diagram?

Hi,
I am opening an vi using "Open VI Reference" and "Invoke Methodpen FP", but I want to open the vi and show the block diagram, but I haven´t found any method (Invoke Method) to do that and any property.
Any idea?
Thanks!
Gracinda

OK, I can come up with a reason. I have written a program that will search the entire VI Hierarchy of a program and update all of the descriptions for all VIs with the top level program part #, the name of the top level program that the VI is used in, the company copyright info, the ITAR notice, company address, the name of the engineer performing the update, along with the date and time. This will also place as a background image on all the VIs, a watermark of the company name, legality stuff and the copyright. It works very slick in that if there are thousands of sub-vis, such as what I'm working on now, it goes through all of them, makes sure the data is there as per company policy without having to open every one of them look at them and update or not whichever the case may be. The one portion that is tough is that the program will detect if there is a description written about what funtion the VI performs and if there is not a description, then it pops up a dialog requesting the user to write a description. The problem is that without looking at the block diagram for the VI, it can be nearly impossible to write a description for the functionality of the VI. So is there a way to programmatically open a VI, show its block diagram (this would only be in the case of a missing description) and then upon completion of the updates, close the block diagram? (I already open and close the VI programmatically in order to read the VI DESC and update as needed, but that is in the background and of course you can't see the block diagram).
Thanks,
Dan

Urgent Help! How can i execute in the same block diagram two separate labview codes each one with diferent execution timings?

Dear All.
I have 2 application progrlams in the same block diagram. the intention is to use the 2 programs at different excuting time for different application, and each have stop and start button ofcourse i will have master stop. But when i run the program, it only works one program at time , that is the 1st block which i make it active only , when i tried to make active the second block it will not work, only works when i stoped the1st one. So, this it to request ur hlep how can i solve my problem. here i have attached some of my program.
Regards!
Solved!
Go to Solution.
Attachments:
2_block application.vi ‏14 KB

Usually you set up a task that has all the channels from all the modules configured. When a loop starts it reserves that task and the cDAQ can't be used by other loops unless you start and stop tasks.
You can have one loop acquire all the data and if you want certain channels to go to other loops you can use the producer/consumer design pattern. If you wanted a third loop you would add another queue and the third loop would dequeue that data. See attached.
Eric
Attachments:
prod-cons.vi ‏69 KB

Error cluster constant appears different in two locations on a block diagram

I am a newbie to LabVIEW. I have taken Core 1 & 2 and Machine Vision and I have not com across this before.
The image on the right is obviously an Error cluster constant used in the block diagram to create an Error cluster and wire it to an error out terminal. As far as I can tell the image on the left is about the same thing, but why does it look different? The different appearance causes raises a concern that there is a difference in behavior that I do not understand. LabVIEW help suggets that both are Error constants. When I create a new error constant, it always ends up appearing like the right image above. I have not been able to create someting looking like the image on the left.
Could someone please confirm what the image on the left is on a blck diagram?
Thanks,
Bill
Solved!
Go to Solution.

The image on the left is an error cluster control. It has a front panel presence and can be set either via the front panel or through a property node or local variable. The image on the right is an error cluster constant. It is a static value.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot

In block diagram connecting wire getting blur while saving the VI in LabVIEW 2009

Hello,
I am using Labview 2009, And while I am saving a simple VI connecting wires are getting blurry. What could be the problem?? Is it affect my program while running?
Solved!
Go to Solution.

Go into Tools>>Options, select the Block Diagram page and find the section called Constant Folding. If the CF for wires check box is checked, then this is most likely the reason. You can uncheck the check box and it won't affect the way your code runs.
If this isn't the case, you should upload an image of what it looks like.
Try to take over the world!

How can i avoid to see the source code when any user open block diagram third time without password

i have a probelem regarding source code control. my problem is that when user open block diagram of any sub vi in vi. i would like to make a such a vi which source code can not open after seeing the block diagram thrice time and i dont want to make password to see the block diagram so what can i do ?
give me the perfect solution for this type of problem.

First protect you diagram
create a tap on your FP and create a picture of your diagram and put it on the second tap
DON'T expect answers if you only want perfect one's
Greetings from Germany
Henrik
LV since v3.1
“ground” is a convenient fantasy
'˙˙˙˙uıɐƃɐ lɐıp puɐ °06 ǝuoɥd ɹnoʎ uɹnʇ ǝsɐǝld 'ʎɹɐuıƃɐɯı sı pǝlɐıp ǝʌɐɥ noʎ ɹǝqɯnu ǝɥʇ'

Is there a way to add shapes to the shape library, and does anyone make a shape library for electronic block diagrams?

Hello!
I'm trying to use Pages or Keynote to make electronic block diagrams. The shapes library looks like it would be perfect for the job, but the shapes are limited. I know I can make a custom shape, but I live with slight brain damage, which means the mouse is NOT my friend. If I try to make custom shapes, they look like a kindergartener's scrawl, so that's not a solution.
All of the online forums I've been to so far say to use Visio (ick!) and if your desired symbol is not there, make it yourself. Well, several symbols are not there, and the first paragraph explains why this is a non-starter.
I would gladly pay some reasonable fee for electronic shapes, such as amplifiers, mixers, oscillators, etc. if someone made them. But from the help file I can't even see a way to add those shapes to the Apple shape library, so I'm not sure, other than copy and paste, how to handle outside shapes. Copy and paste is pretty labor intensive anyway, but if it's my only option, well, so be it.
Any suggestions? Aside from Visio, that is...
Thanks!
Jim

Hi Jim,
When you say the "Apple shape library" do you mean the Shapes button on the toolbar in Pages?
I don't think there is a way to add to the Shapes in Pages. However, you can create a custom template with shapes that you frequently use. Save a document with your shapes then Menu > File > Save as Template...
This will be saved in My Templates folder, and you can open it with Template Chooser. You will still have to Copy and Paste a shape into the document you are working on. No way around that!
I don't use Keynote, so I may be missing something in your question.
Regards,
Ian.

Saved block diagram wont open

I am a new labview user so this may be obvious, but I have a problem nonetheless:
I have drawn a simple program and saved it but when I open it again, only the front panel opens and not the block diagram as well, which I wish to edit. I am openning labview on the same machine, same version etc. what do I need to do to get this working properly?
Thanks to anyone for their help

Hi Dougonlabview,
Just press Ctrl+E. This will bring you to the diagram. Pressing Ctrl+E again will bring the front panel back on top.
Regards,
Mathieu Steiner, Test System Engineer, Safran Engineering
CLD, ISTQB

How do I take a screenshot of a block diagram to be used in a MS Word document?

I am using labview 5.0 and I am working up a user manual on the VI I have created. I would like to include screenshots of the block diagram and explain what I have done for future revisions of the VI by other programmers.

You can "print" your vi. When you do that, you have the option to save it instead as an html or rtf file. LabVIEW will create images of your diagram that you can use for your user manual.
Also, you can simply select your diagram or part of the diagram using the "Position/Size/Select" tool, copy it and then paste it on your word document, like any regular cut and paste. It will paste as an image. If you want, you can paste the image in another application directly like Paint or Microsoft Photo Editor, so you can modify it accordingly to your needs.
Best regards;
Enrique
www.vartortech.com

How to add text to the block diagram

How do you add plain text to the block diagram for documentation and can I change the background color to yelllow or something else that may be helpful? see image below
Windows is a 64 bit extension to a 32 bit graphical shell for a 16 bit patch to an 8 bit operating system originally coded for a 4 bit microprocessor, written by a 2 bit company that can't stand 1 bit of competition. Byte that Microsoft!
Solved!
Go to Solution.

Just double-click in an emtpy area and start typing. Use the coloring tool to color the text background.
(there is also a "free label" in the decorations palette, but that seems like a detour )
LabVIEW Champion . Do more with less code and in less time .

Block Diagram Warning

Similar Messages

Maybe you are looking for