Gribo

It doesn't exist in LV2015.

Of course someone can. General questions get general answers. Can you provide more details? NI has the LabVIEW core 1 course available.

I'll give it a shot later today. Might require Wireshark.

You can reverse engineer the protocol with NI-trace. It is quite trivial.

You know that these glyphs are in the C:\users\<username>\Labview Data\Glyphs folder as .png files, right?

Take into account that MXI has its own set of limitations. You cannot hot-plug an MXI connection reliably, It is a single source (NI only, AFAIK).

You might want to consider MXI (Either optical or copper) as an alternative. It avoids another layer of drivers. Desktop PCs with Thunderbolt exist, (Mac pro, other high end workstations from Dell or HP).

What is the difference between these two methods? If a .NET library is included in a project, does LV load it before the VI is run?

You should check that both the DLL and LV have the same bitness, 32 bits or 64 bits, not mixed. You might be able to bypass the entire problem, if you can create a raw printer file. 1. Create a raw file - usually label printers use a text based encoding (for example, Zebra printers use ZPL, other vendors have similar formats). This will be your template file. 2. If you are using Windows, create a printer share. 3. Set the fields in the template. 4. copy the file to the share - using the system call, issue a copy <filename> \\localhost\<share name> command.

What are you trying to do, print something? Can you post a link to this driver?

I am using EmguCV. You need to convert the mat into a bitmap, and if you are using the .NET PictureBox control, you have to create a graphics object, then use the ToBitmap method of the MAT to draw it.

Do you get a response to IDN query via MAX VISA Test panel? If not, check your hardware. For the VISA write, make sure your string is set to '\' Codes display, and add a \n - line feed, not a literal \n.

Type object is in the System namespace. Click .NET connectivity -> Invoke node -> Select class -> System -> Type -> Missing

Here you go. This is not a production code. You will have to close references when you are done with a specific object. 2 things to note: 1. Excel, like VB is 1 based. 1st index is 1. 2. Don't leave an empty property node input. Wire a 'missing' type to any gray (optional) input that you don't use.

The DAQmx objects depend on the VISA version installed on the PC. Somewhere between 2010 and 2015 there was a change and recompilation was required.

You should use the Excel .NET API. You will see your data as it is added to the spreadsheet. Also, you can do this with OpenOffice/LibreOffice if you don't want to pay for Excel.

Where do you write to the different queues? Does it work with only one PLC?

If you know there are no more bytes in the buffer, then you can ignore that error. That is, if the packet size is fixed, and you are receiving correctly, you don't have to reach the timeout. Also, you can set the timeout to a value less than 10 seconds, if you know that all transactions occur before the time is up.

Shameless plug: Here is another example of WebSockets:

Get one, worst case, your slightly older laptop will get a memory upgrade.

Way too many meters of LMR200 inside a 1U enclosure to be comfortable with. Hey, it works!

The Excel .NET API behaves better with LabVIEW than the ActiveX one. From your point of view, they are the same, so why not use .NET?

Don't mix 32 and 64 bit pieces of software, it will not end well.

At the risk of sounding petty: I am using Windows, so the first thing that comes to mind are the GUI Conventions: LabVIEW Undo is ctrl+z, LabVIEW Redo is ctrl+shift+z, while Window's Redo is ctrl+y. There are many more such (minor) design choices. The application should use the OS conventions, not force its own way. And, as an ambidextrous person, Scissors should be designed for both hands.

I have managed to solve it by replacing the EMGU ImageBox control with the standard .NET PictureBox.