Neil Pate

What you have made looks great, and I absolutely commend your effort. But, I think the area of the shaded part of the Venn diagram that consists of people willing to pay for LabVIEW and want to get into Deep Learning using a new and paid for toolkit is a number approaching machine epsilon. NI has abandoned Academic institutions and is introducing a new licensing model that is predatory and harmful to the long term viability of LabVIEW. It breaks my heart...

Sometimes some weird locking of classes/libraries can occur if you dont perfectly close all opened resources. Totally off-topic, why do you have a reference to the class and also the class object itself? I see you don't actually do anything with this cluster so it could be throw-away code, was just curious about your use case.

I definitely can echo what @JKSHsaid. Several years ago I implemented a data dashboard with WebVI tech (in NXG) and the overall experience was so painful I will never try it again.

Remaking an image editor sounds like a fun weekend project if there is beer involved. But I suspect the end result would be throwaway code! I totally agree with you pushing back on this requirement, it sounds like the potential for massive feature creep. Sorry, I do not know any .net or similar toolkits to embed into a LabVIEW application. Maybe there is some javascript implementation you can embed using a web-browser frame thingy (like https://paint.js.org/) ?

😂 The glass is definitely half-full

I guess this was the extremely ambitiously engineered greening of National Instruments into NI.

I completely empathise!

OK, I did not get that impression at all.

@sprezzaturon it does not really make sense to compare LVOOP to a FGV, they are totally different concepts. Pure LVOOP by itself does not give you any kind of parallel access, enum action driven shift-register type actions you will be used to with an AE. (and a AE is just a FGV with some methods). I think a more apt comparison is to compare an AE to say some kind of Actor (or parallel process etc)

Maybe completely unrelated, but I had a similar issue some time ago. I had some software which just did not run on a certain PC, it gave some weird error message. The error was actually in the LabVIEW "Mean.vi" which is part of the advanced analysis libraries. See this thread for my post. To cut a long story short, I had to add a setting to my PC environment variables. Doing so allowed the Math Kernel libraries to work with my CPU. Something similar to this. MKL_DEBUG_CPU_TYPE=4

He means it is difficult enough that it would be hard to give a fixed price without padding it by 300% and then looking stupid when he presented the quote.

@alvise, the problem is your are trying to fly, hypersonically, before you can crawl. Interacting with a DLL as you have been shown to do has heaps of pitfalls. I would recommend you forget about your video stream for now and just make a super simple example that strips everything to its very basics.

This is actually for a different log file. You get more info using the ini file setting, but actually it's not normally super helpful either.

I have nothing to add to this thread, other than @alvise I think if you get this working you owe a few people some beer 🙂 To those patiently contributing to this thread, I sincerely thank you. This community is so much stronger due to you folks. Please never leave!

Nice! While you are there please convince Elon to buy NI and turn it back into an engineering company 🤣

Ah.. it is this (found here) NI_AppBuilder_Logging=True The result of adding this key is a details file gets created next to the .lvproj file. It can sometimes be useful to see what file a build is choking on.

Hi everyone, I am trying to debug a (exe) build that is breaking for reasons I don't yet understand. In the past I added some setting to my LabVIEW.ini file to get extra detailed information about the build process, but I cannot find that key listed anywhere. Can someone remember what it is? It was something like EnableDetailedBuildInfo, but it has been years since I needed it last so have got no chance of actually remembering the details.

Even better, thanks! After my brief investigation yesterday I was not super enthusiastic to mess around with ini files and signing things.

Thanks Antoine, that is a really useful link. I knew about the Project Providers, but thought it was just for things like adding stuff to the right-click menu. I will dig in 🙂

I have never needed to do this, but for some reason am now curious. Can anyone point me in the direction of where to look for documentation of how to add buttons like this?

I am probably going to get my details a bit mixed up here, but I ran into something quite similar to this last year. I think we were trying to either export a MAX config (or programatically reimport it or something) and it did not include our 408x based PXI cards. The official response from NI was that the System Configuration API does not support these cards! I will dig through my email tomorrow when I am back at my work PC.

Hi, Does anyone know how to make a simulated DAQ device using LabVIEW code? I am thinking about creating one programatically as part of some unit tests.

Thanks for the update @smarlow this is interesting to know. Not the best example of UI design!

Wow that looks like a huge effort, nice work! Really curious to take a look when you get around to releasing it.