Gribo

Here are my ugly hacks: Only one active panel at a time. If user input is required for a dialog, it is on top, all other panels are disabled. In Windows, a system call to bring the window on top is used, instead of LV's bring to front. This gets me somewhat more consistent results than the LV function. If there are two (or more) active panels, the newest one is enabled, the others are disabled.

Also, you use the wrong slash, it should be /

Iperf3 gets ~95% of the theoretical speed of a 1G Ethernet easily and reliably on Windows, without being CPU bound. It requires multiple threads to get there, A single thread will be limited by the scheduler. It doesn't matter much whether it is TCP or UDP.

Yes.

Pass it through a not operator?

OpenG has a 'Get parent VI reference' VI, It might help you.

Can you post the entire error message, and not just the .NET error code? Is there another process that might be using the device?

Instead of Access, you can use SQL server Express. The server can be 32 or 64 bits, local or remote, as long as the ODBC driver matches LV's bitness, you should be fine. If you used only NI DB connectivity library, conversion effort will be minimal, mainly syntax differences between the 2 systems.

You will have to implement or choose a protocol that both sides can speak. 32 doubles at 200Hz means 52KB/sec, Which is relatively modest. Are there any hard real time requirements? What happens if you lose some values?

That is how LV looks on a 4K monitor.😁

In one word, QMH. You will have to design your application with an event handler and a queue. You will also have to think what sort of events to handle and how to stop your acquisition loop. There are few templates for such design built into LabView.

Your event structure should be in a While loop. one of the events should generate a stop signal for the loop.

Since it is just a raw printer commands file, you can do the following (I have done it in the past with Zebra and TSC label printers): 1. Share the printer. On Windows, its Printer properties, sharing and create a share. 2. Test by running the following command: copy <filename> \\<hostname>\<sharename> . You can use localhost, if it is on the local PC. 3. In Labview, use the .NET Copy command, as LV copy doesn't support local shares for some reason.

Do these files contain printer commands? If so, you can share the printer and issue a copy command from the VI to the share.

What is your topology? Is it a single RS485 link per slave, or are they on the same bus? If they are on the same bus, you will have to think of the communication protocol, is it token based, is it CSMA/CD? That is up to you, as the designer.