Gribo

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.

I didn't know hell froze..

The next easiest alternative is to find the browse button's coordinates.

You can try the mouse down event, then set the match pattern and start path. That fires before the browse window appears.

What is the question?

Their software library requires a license and there is no online documentation. Can you share more details?

No, I have manually created a template build specification which includes the folders that I want, then I copy it.

I have uploaded a new version. The test VI now creates a chart with random data. LibreOffice 6 is way faster than 5, it feels as fast as the Excel .NET API.

After playing a bit with LabVIEW, and remembering to cast a value, and not its class, I managed to get to your level. I will post an update in an hour or so.