I'm controlling a Patlite USB signal tower using their supplied .dll. I downloaded the .dll and used to wizard to create wrapped vis and it worked fine in LabVIEW 2021. I followed the exact same procedure on a different machine using LabVIEW 2024 Q1 and the wrapped vis are nonexecutable. I get the following message:
The .dll is there and I've verified the required support files are there as well. Anyone dealt with this type of issue before? Thanks.
For the writes:
add the following VIs to your benchmark code:
Binary:
TDMS:
When measuring execution times, put the last timing node in a frame after the file close frame. Post back with those results.
Hi all,
I am trying to build a VI where I am displaying voltages and current on a waveform graph.
I want to reset the waveform graph by clearing the data every 5 min.
I need a way to clear the the data on the waveform graph after every 5 min. So the data doesn't get crowded on the graph as the VI will be running for a long period of time.
Other issue I am having is that the new values that get sent on CAN are getting plotted on the left side of the graph.
As a standard graph would update values on the right side, this is not the case.
I am attaching the part of the VI below. Can someone please help me out with this?
Hello, M_S_C.
My recommendation is to use the tools that DAQmx provides to create your tasks directly in the Executable. DAQmx has functions that can build and configure Tasks for you. The only "trick" is that you need to find the "Physical Device" that you want to use.
There are ways to do this using DAQmx. However, in helping another user on this Forum this week, I discovered that the technique I'd been using for about a decade to do this seems to have stopped working sometime in the last six months. I'm going to try to track this down next week.
Bob Schor
Is there any way I can point those question marks to the correct libraries? I've used LabVIEW for years but never played around with the menus/function palettes.
It seems to be pointing to the correct files when I try to find them via the palette editor.
When I right-click a VI in the palette, and try to open it, it gives this error:
Any ideas?
Hi, I have a Labbview program of a USB3 machine vision camera with an image file saving path and an option for file saving with date and time. These functions are working well but are not displaying on the front panel. Also, I can't save images automatically. The VI is attached. can someone help me?
To get your board work with LabVIEW: NONE.
That are all examples for specific algorithms that might work with your board or not. But you first need the USB driver for your board and a board level support package and according FPGA framework support for the LabVIEW environment. You also obviously will need the LabVIEW FPGA Toolkit which is a licensed ($$$) package just as LabVIEW itself.
You really need to contact NI or Digilent directly for this as we do not know this hardware and don’t know which installer is needed. It may be part of a normal software installer but at least the USB driver seems to have its own installer and only a support person of NI or Digilent can know that.
You can of course keep posting here and hope someone in the know happens to read this thread and answers but if you want to get this working before the end of the year and not just after you finished with your graduation, a bit more proactive action by getting on a phone and start talking with the actual support people from NI and Digilent, will be required in this case.
Hi,
I apologise for the disturbance. I am currently working on synchronizing multiple AI channels and will be using the X-6363 USB, where ai0 acts as the master channel and all other channels function as slaves.
I have downloaded the shipping example, which uses two sample clocks. However, I am uncertain about which sample clock source would be most appropriate for my setup—whether I should use the onboard clock or counters. Additionally, in the synchronization type option on the front panel, I noticed that it lists "X series (PXIe) < SC Express." Could you please guide whether this setup would also support the X-6363 USB?
For your reference, I have attached the LabVIEW code (LV19 version) to this message.
Thank you for your time and assistance.
Kind regards
HA
I think a lot of people who are very concerned about the problems with OpenGL have never actually experienced any problems with OpenGL. They then come to Vulkan and try to write their first bit of graphics code and wonder why Vulkan is built the way it is. "I had to write so much code!" they scream, as they slowly realize what building a complete game engine with a vague list of very open-ended goals will actually entail.
I have a png image 1280x853 and I need to make it bigger, for example 1380x953, by adding a black contour.
I have tried multiple combinations of IMAQ overlay and IMAQ copy, but nothing seems to work.
Thanks in advance.
I don't have any concerns with OpenGL but it's in C++ so I'd rather write a native C++ application if I were to use it..
I suspect that the strings in the spreadsheet file are UTF-8. However I don't know what XLR8 returns.
Maybe you can make use of one of the attached files.
Hi everyone,
I need to create a continuous counter in LabVIEW. The counter should increment whenever the input value exceeds a specified threshold. Additionally, the program should periodically check the status of this condition after a set interval.
I can upload my VI for reference if required.
Looking for guidance on how to implement this efficiently. Any tips or suggestions on how to proceed would be greatly appreciated!
Thanks in advance!
@PincoG wrote:Hi Rolf,
did you already developed a product around it?
I'm still busy. I got a very experimental Client interface working but am still fighting with the Data Read and Write interface. LabVIEW is extremely strict typed as far as your Diagram Code goes. The only datatype that allows dynamic interfacing is the Variant but that is not documented anywhere how to interface from C Code. That means I need to implement specific VIs for every single datatype I want to support, starting from bytes, words, longs, quads, and the unsigned variants of them, booleans, floating point in single and double precision, timestamps and strings. And then 1-dimensional arrays of them and 2-dimensional ones of all of them too. And that still won't support compound datatypes like structures!! Handling all of that on the C side to convert to and from the Open62541 data type system is highly complex and error prone. I tried several different approaches, the first few were relatively simple but extremely inefficient, then I ventured into trying to maybe figure out how LabVIEW Variants work on the C side of things, but I had to conclude that the almost complete lack of official documentation makes that an exercise in vain.
Currently I'm busy implementing a new approach that should work fine for most datatypes except structures/clusters and at the same time be pretty performant too, but the C side of things gets rather complicated that way. I'm close to have the scalar datatypes working and then need a little more time to get the 1D types working reliable. Once 1D works too, 2D is a relatively simple addition, mainly adding according accessor VIs on the LabVIEW side.
Your code is highly flawed with unnecessary sequence structures, complicated constructs (e.g. how you parse the data) and way too many local variables (causing race conditions). The diagram that is way too big to efficiently debug. It is incorrect and unnecessary to reset all to default at the end. If things need to be initialized, it should be done at the start of the program. Your orange shift register is not initialized, so the contents will grow forever in consecutive runs.
It is rare that voltage and current values are integers, so why is most of your code blue??? No, there should not be any dynamic data anywhere!
It is extremely hard on the memory manager if you prepend new data to existing arrays. Appending is much more efficient. It would be sufficient to have a single shift register with a 2D array to hold all data. Keep it simple!
A graph is just a passive indicator for whatever data is held in the shift register.. You built your arrays there, so all you need to do is manipulate the contents.
If you just want to chart the last N values, all you really need to do is use a char instead! Charts have a scalar input (among many other possibilities) and have a fixed history where the oldest values are dropped once the history buffer is full. No shift registers or arrays needed.
For fun, I implemented a quick idea that will consider all numerical "fields" (20 consecutive numeric digits or less) are considered are treated as numeric for the sorting logic.
Probably needs a few tweaks, but seems more universal than code found elsewhere here.
Yes, the "scan-format" operation could be avoided but this is more readable)
Yes, code would be nice (since I, for one, have no idea what it is you want to do). A small compact Demo Project, with all TypeDefs and sub-VIs included, would be ideal, especially if "Save(d) for Previous Version" including LabVIEW 2019 and 2021.
Bob Schor
I like the concept.
Here's my hack at it.
I'm puzzled why, if you are running LabVIEW 2018, you are installing VAS from LabVIEW 2020. When I install a version of LabVIEW, I install the Drivers and "other packages" from the same version at the same time. As it happens, looking in NIPM for the installed packages will often show me the packages for the later versions (for example, I just looked at my current Laptop, which has LabVIEW 2019 (the first install) and LabVIEW 2021 (installed later), and mostly see 2021 versions when looking in NIPM (NI VAS, NI Vision Common Support for LabVIEW 2019 and 2021, Vision Support (both versions), IMAQdx Drivers (both versions), Vision Assistant, and VDM (very few packages, in fact, show 2019 Version numbers in the far right column).
Bob Schor
I'm using a RT system and and i want to find the available visa resources of the RT. Other than read find visa resource function in RT and send it to host as array any other way is there?
