All Activity

Aha! Yes. Apologies.

Last week, Matlab R2023a was released. The changelog document for this (6-month cadence) release is 600 pages long!!! How come NI releases main development software with a 1-page changelog and makes it almost unusable with more issues than before??? How many NI engineers does it take to change an icon?

*ahem* Not that I'm suggesting that you do bother haha.

At least we'd know where we stood rather than being strung along in uncertainty.

Switching a large project to a more recent version of LabVIEW is quite risky. Even when it's justified by a new feature the risk is high, arguably even higher as new features are rarely fully stable / bug-free on the first release. Basically by changing version you're trading a bug-set that you probably got used to - and hopefully worked-around - for a new - and unknown - bug-set. Highly risky.

That's unsettling. When my current project is done, I was planning to upgrade to 2023Q1 64-bit (currently using 2019SP1 32-bit). Apparently, I will have to put more scrutiny in my evaluation first.

As you are the only one that has commented on it al all (indirectly). I think that's a resounding "don't bother". Also means I don't have to look too closely at DTLS just yet

Well. It's more likely a very resounding "I have no idea if I'm ever going to need that. For now I just refrain from commenting on the matter!" 😎

So. that's a resounding "don't bother" on the CoAP then

If Emerson buy NI, you can look forward to no LabVIEW at all.

I am looking forward to reading "Undo doesn't work anymore" in 2024Q3 and "colors are all gone" in 2027Q5... 🍿🍹

The error message is telling you that your "Axis" enum control doesn't have an item called "X" (upper case) You can edit the item list of your enum by right clicking on it on the front panel and select "Edit Items...." or change or simply remove the "X" in the case structure selector value on the block diagram

Hello everyone, I'm new to LabView and I got this error while writing the program. In this block I have three cases for each axis of the accelerometer (default X, Y and Z). I can't find the right way. Does anybody know how to solve this problem? The app I am writing on this tutorial from youtube.

Thank you, I found this tool in Advanced Signal Processing Toolkit

I just went to 2022Q3 64-bit about a month ago with a fairly basic program. USB cDAQ chassis with DAQmx and XNet on Windows 10. It had several classes, reentrant-ness, subpanels and data logging. I haven't seen any weirdness yet. My next step is to dive in upgrading our Linux RT remote controllers and our sequence editor, and report generation. This is a much larger project and one more likely to find issues.

This last month, I installed LabVIEW 2023Q1 64bit and here are my experiences so far. My experiences has been the same on my laptop and on a PXI system so I'm confident to a degree it's not a hardware problem. 1: When creating an Override VI, the new VI has the default Untitled 1 icon. The icon from the VI of parent class is not transferred. I've reported this as bug to NI and they confirmed it, except that they are not committing to any hot fix yet. I've not tested the 2023Q1 32bit. 2:. Class Corruption. On average, I've encountered daily a failed to load class because the class definition is corrupted. I use git so reverting the .class file is an easy fix. Any new class properties or changes is obviously lost. 3: Insane VI objects, are encountered and easily recreated. Perhaps this happens to me easily mainly due to my habits of programming. I tend to drag and drop controls and indicators , or code between VIs. I've noticed that sometimes after I finish the drop the object is not shown on block diagram. This "not dropped object" will cause the entire VI to be flagged as Insane Block diagram. Problem is that I've not noticed the problem and thought maybe the drag & drop event was my fault by me letting the mouse early. Obviously all work on the VI is lost. 4: LabVIEW sudden crash. Self explanatory. LabVIEW just disappear and is offloaded. Sometimes a new LabVIEW instance will not relaunch if I open it by double clicking on last project. Im going to switch to LabVIEW 2022Q3 or 2023Q1 32bit for now. I'd be very interested to know if anyone else has had this experience or not.

you can find the description of all the VIs of the toolkit here : https://www.ni.com/docs/fr-FR/bundle/labview-advanced-signal-processing-toolkit-api-ref/page/lvasptconcepts/aspt_default_page.html

It seems it's a VI from the Advanced Signal Processing toolkit : https://www.ni.com/fr-fr/support/downloads/software-products/download.labview-advanced-signal-processing-toolkit.html#411230 I'm not familiar with this product... but anyway, in the video, this VI is removed.

why don't you post the link to the youtube video? maybe this VI comes from a package that is not installed by default

I'm trying to write a program based on one YouTube video and I don't understand where to look this function. Who can tell me what it is called?

Ok, this is not gonna work like this. The sample code you show uses gobjects to start its own loop and do event handling all through it. gobjects is basically a glib task handling system. It's in fact its own execution system and is for instance used as base of gtk and in extension GNOME. But these are build on top of gobjects. LabVIEW has its own execution system and marrying two of them together is a major exercise in coding. In fact it is almost never done since it is so difficult to do right. You will need to try to find the lower level interface of this aravis library. It will require you to call lots of functions with the arv_ prefix and similar, but you must avoid anything that starts with g_. Basically you would need to start writing something like IMAQdx with many of its functions but instead of calling into IMAQdx you call into the arvis library. It's doable but not for the faint of heart. Basically trying to interface to image acquisition hardware and libraries is very difficult. Always! And there is a reason these libraries cost money and there are very few freebies here. The Arvis library itself seems to be free. Its LGPL licensing can be problematic for anyone wanting to use it for a commercial program. And while it states to be LGPL there are actually files in there that state to be GPL. So licensing is not completely clear cut there. Incorporating GPL software in anything other than GPL software is basically impossible.

CMakeLists.txtThis is what I'm working with at the moment. The image aquisition works out fine. The only issue is that it's not event driven. Instead of only grabbing an image when a new one has been written to shared memory I'm grabbing the image constantly. I know what @Rolf Kalbermatter means by refactoring the code into the functions. The issue is that in order to grab a frame I new to access the camera(aravis "object") which is instanciated in the connection process. I don't see how I could wrap this so I can make use of these functions in Labview. main.c client.c test.vi

Here is a List API. Seems complicated but it's a "managed" list with lots of features. Overkill for what you need but it demonstrates a point. You could use it for your data but then you'd have a dependency. I'm guessing you don't want dependencies at this point. You'll notice it has two items in the cluster - Name and Variant (variant is a general type and think of it as your Cluster). The important part is that it has a "Name". This is a poor replacement for the Cluster Name (functionally) but it does enable lookups, even by regular expressions. It serves a very similar purpose but operates at run-time instead of design time The name is just a string label. It can be anything. Granted it's not as simple as an enum but it does give much more flexibility and doesn't require design time editing of the control to make changes. The tradeoff is complexity. Now you have a way of making a list behave like a database but you need specific functions to look up and return data. This, from one of the list examples, returns all items with a numerical label: Intuitively you will realise that having duplicate data is not very useful unless you can distinguish between the original and manipulated. Up until now you have used the Cluster with an unbundle which has served you well but are now finding that you need to edit the cluster every time you add new variant of your data. The label gives you that ability at run-time instead of design time with a small increase in complexity. However. Your biggest issue is compartmentalization - separating config from data. Now. What if only the List (aka data array) wasn't tied to a particular data type? Then, by thinking carefully about the labels you use, you would be able to differentiate between the different data types, different devices and different configs There are other ways to approach this. But from where you are at present I would suggest this way - at least until you are more confident with your abilities. The database I suggested earlier requires a different mind-set and classes are a huge learning curve. This is a modest step from where you are to where you want to be.

I totally Agree and in fact i had that format originally. However, arrays gets rid of the cluster names and replace them wit the first item's name and for me keeping track was becoming difficult even with documentation. it was just easier to have the clusters that can have different name. I know that i could also use a simple enum for indexing but that would add an extra data that needed to add to my system. I also have a duplicate of BG and HRS as an original data and manipulated data. This way when want i can revert back by replacing the data with the original. I am very new to programming and do not have experience in data organisation and almost nothing about labVIEW classes and the NI documentation is just too simple and is not covering any real life application. That is why I was asking for help. Cheers,