austinman

This was posted at NI and relevant to this thread: Monnie Anderson, a very early National Instruments employee who retired not long after NI went public in 1995, passed away this morning. He was one of early LabVIEW's most important internal users, the inventor of the Error IO cluster convention, provider of extraordinary customer support, and all around LabVIEW enthusiast and evangelist. He is memorialized in LabVIEW with three densely packed connector panes, named: the 16-terminal "monnie pleaser"; the 20-terminal "monnie super pleaser"; and the 28-terminal "monnie would be pleased-er".

Hi Priya, I cannot run one VI as there are missing subVIs in STrace.vi. I have attached a VI where I have combined the 2 block diagrams. This is not an ideal solution. A better way would be to use each VI as a subVI, then place each subVI on a calling VI. To do this you will need to create a connector pane for each of your VIs. There are plenty of online tutorials that explain how to do this. One last comment. This site is intended for LabVIEW advanced users. You may find more appropriate help on the ni.com web site. There is also a Facebook group (https://www.facebook.com/groups/430271233771850/) that may be helpful. STRace and Mic Combined.vi

6 days and 1 tax return later, and my BS alarm still hasn't shut down.

Thanks for your input, and sorry for not responding sooner. For some reason LAVAG does not like to send me notifications, even when enabled. which means I have to manually check for responses. It sounds like we are on the same page, in that there are different solutions for different problems. As someone who teaches LabVIEW Core 1 and 2 on a regular basis, I find the basic producer/consumer can be overwhelming to new developers. My feeling is the producer/consumer, and state machine, are a good foundations on which to start. As skills and application complexity increase the QMH is the next step, and so on. Hopefully all the loops have matching decor.

@drjdpowell Agreed, the Producer/Consumer does have limitations, but it is good starting point for LabVIEW developers. Out of curiosity, what architecture/design pattern would you suggest a new(ish) LabVIEW developer use in place of the Producer/Consumer?

It sounds like you have made the 'Service Use Only' tab the default value for the Tab control. Select the 'Manual Adjust' tab, right click on the tab, and from the short-cut menu select Data Operations>>Make Current Value Default.

A search of Google and YouTube with 'labview for loop' results in a number of ways to learn about the LavIEW's For Loop. A similar search will work for learning about array functions in LabVIEW.

As you have discovered, one of the limitations of the Event Structure is that it will only process one event at a time. A search of YouTube with 'labview producer consumer' returns a number of videos that discuss using multiple loops with the event structure. If you have access to the LabVIEW Core 2 material the producer-consumer design pattern is discussed there. Using multiple loops enables your program to keep processing events while performing other tasks (e.g. prompting the user for input).

A Picture Ring control (configured as an indicator) sounds like a good candidate, and available in 2011.

This advice may not be much use for your imminent interview, but for the future it may prove useful. If you are looking for a job/career that focuses on using LabVIEW, then you should seriously consider gaining a LabVIEW certification. Certified LabVIEW Developer is the sweet spot. The NI web site has lots of information, including preparation material. Check it out at: http://sine.ni.com/tacs/app/main/p/ap/ov/lang/en/fmid/499

There are tookits available that can convert XML to LabVIEW data. For example JKI's Easy XML Toolkit: http://jki.net/tools may work for you.

I have worked with a couple of organizations where developers had similar constraints on using open source libraries/code (in any development language). They had processes in place to verify open source code was 'safe' that were so time consuming it was easier for a developer to create their own.

I saw another comment in one of the ni.com forums expressing similar frustration. Looks like someone sent the emails without checking that the back end systems were ready.

I received an email from NI today, offering a 50% discount on the price if you register by Sept. 1st. When I tried to register with my user name the web site showed my NI Week 2016 registration information. Anyone else received the email and tried to register?

Hima, UDP is a lossy protocol. There is no guarantee that all the data will arrive at the listener. This could be one reason you are seeing data loss. Have you considered usiing TCP/IP, a much more robust protocol?