All Activity

Thank you @Rolf Kalbermatter. Your suggestion works as expected, and the code is much simpler than in the previous version. As I understand it, performing the opposite operation would not be easy since we can't resize the array. I wonder if there is any other function to allocate memory on the C side using LabVIEW, or if `NumericArrayResize` from extcode.h is the only option?

That's very good.

那不正是 Hu 做的吗？问题是边框的颜色不是单一的。

I did that too but it broke a VI connection in one of the analysis VIs...

I am new with lab view and I need help with a project. It reads the dates from an esp32 and 2 senzors one is dht11 and the second is a mq135 I dont know how to make this: -Periodically records and saves measured values at predefined time intervals. -On demand, it reads and displays measured values for previous time intervals. -To display of measured values via the Internet on a web browser. I am stuck with this points. I need help ASAP! Proiect1SDMM.vi

We do not have too many Chinese readers on this forum, so you will probably have more success if you try in English

At first: I havn't found more information. I installed LabVIEW 2021 SP1 f6. It look like a complete reinstallation of LabVIEW (not only a patch). Excapt that it changed the user.lib palette everything seems to be like before.

用Windows API指定要透明的颜色就可以了，例如你这个程序可以指定白色部分透明，运行程序的时候界面上就只会看到两个布尔控件。

Undo and Redo implemented in the sequence editor I designed.

I'm in charge of developing a sequence editor at my company, and I've noticed that the application I'm developing takes an unusually long time to start up taking about six or seven seconds, is it because I'm nesting too many actor in my program?

Thanks Rolf, I put 19 back on it.

You consequently have hidden the actual type number of your sbRIO in your pictures. I think I can see in one place a 963x but it is not sure. And most 963x except the 37 and 38 are VxWorks based and as such LabVIEW 2019 is the latest to support that. It also requires you do install CompactRIO software not later than 19.6. The 9637 is supported since LabVIEW 2015 and CompactRIO 15.5, but the 9638 requires at least LabVIEW 2019 and CompactRIO 19.5.

It's been a while I've worked on sbRIO devices. usually MAX is how you setup the sbRIO but that options seems to be gone. Am I missing something? this sbRIO had 2019 on it before I formatted the drive , now I can browse to it but options to install are no longer present. I downloaded System Configuration/setup from NIPKG manager and all *.ipk files but a bit lost on how I can put an OS on this sbRIO. Any help is appreciated. Editing to add: Some information on only LabVIEW 2019 and older can be installed the old way https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000001DthyCAC&l=en-US 2020 and newer installation is done differently. What I'm concerned is if all sbRIOs are supported with new method. I'm guessing not https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000x2jQCAQ&l=en-US end of edit.

NI Package Manager is advertising a LabVIEW 2021 SP1 f6 version that I would like to learn about before installing it, but I am unable to find anything online. Does anyone have a better search engine (or insider trick on how to get the Package Manager to be helpful)?

I'm not sure what you mean by "not fully transparent" but if you want to get rid of the border you can do something like this. sr_test1.zip

My front panel doesn't always rule. For example, rounded corners。

Rolf/Log Thanks guys for the input , I will have to do a little testing , but , sounds encouraging. Regards Dan

I have not used that Windows API before. Why don't you just resize the window to as big as the area you want to remain?

I want to make the front panel transparent according to the background color to remove the unwanted parts. When I set the windows behavior of the VI to floating, the program is OK. But when I set thewindows behavior of the VI to the modal, there is a transparent border, and it is not fully transparent. Is there any good solution? The VI of the test is in the test1.rar file. test1.rar

Hi, I made a Tcl script which compresses the property/method information for classes by removing everything inherited from a parent class (this reduces the file size to 18 304 lines); also, I selected classes suitable for FPGA VI - now the text file is below 7 000 lines, and I see no method or property duplicated there. For full class set, 163 methods for VI-like classes weren't reduced because VI class used type LVObjVI and its children used LVObjUnknown; and some properties weren't reduced bacause a child has their access configured differently from its parent, like for both the property was read/write, but the default direction was different (this affects properties: 225 AutoLog.Path, 226 AutoLog.AtFinish, 227 AutoLog.PrintAtFinish, 242 Def Err Handling, 283 AutoPreallocate, 634640e Value, 6346410 DefVal, 6346411 Val(Sgnl), 23f44800 Name, 5436bc00 Texture Generator Mode, 5436bc01 Texture Generator S Plane, 5436bc02 Texture Generator T Plane, 7c86e800 TypeClass, 7c86e80a Value, 7c86e811 UserData). lvc_tree.tcl is the script which can be run on the large (over 4MB) file in the lv_classes.zip I posted on May 18th; the 56kB text file is already "compressed". I found 8 more classes used in FPGA VI-s - they aren't in the file: EIONode, EIOPropertyNode, EIOMethodNode, EIOGrowableMethodNode, LocalResourceManager, niFpgaContainer, nifxpmath_Interpret, niFpgaIPINode. fpga-cl-known-xf.txt lvc_tree.tcl

Nice! I did not know about this.

Yes. Yes. It will still use the runtime engine, which is part of the installation. Here is a KB article with more information on how to bundle different report classes with your executable: Create a Stand-Alone Application Including Report Generation VIs - NI

It should. The Report Generation Toolkit VIs are either built in (HTML Report) or access the according Word or Excel Active X component. However the Office ActiveX component is version sensitive. LabVIEW uses dynamic dispatch to access these interfaces, but uses early binding for that. It means it determines the actual method IDs to call at compile time rather than at runtime based on the method name. This has as consequences that the calling is slightly faster but any version difference in the ActiveX interface leads the LabVIEW method call into the abyss. So your Office installation on the target machine has to use the same version as what was used on the machine on which you build the application. The change to use late binding would have been fairly trivial for anyone having access to the LabVIEW source code, but alas was never considered a strong enough issue to let a developer spend a few hours on it. If I would have had to do it I would probably have left the early binding option in there and added an extra retry to try late binding at runtime if the initial methodID call would fail. Or even fancier, let the ActiveX method call have a menu option to select if it should do early binding, late binding or a combination of both with retry if the early bind call initially fails.

Pretty simple except if you need to resize the array in the C code. You can let LabVIEW create the necessary code for the function prototype and any datatypes. Create a VI with a Call Library Node, create all the parameters you want and configure their types. For parameters where you want to have LabVIEW datatypes passed to the C code, choose Adapt to Type. Then right click on the Call Library Node and select "Create C code". Select where to save the resulting file and voila. This would then look something like this: /* Call Library source file */ #include "extcode.h" #include "lv_prolog.h" /* Typedefs */ typedef struct { LStrHandle key; int32_t dataType; LStrHandle value; } TD2; typedef struct { int32_t dimSize; TD2 Cluster elt[1]; } TD1; typedef TD1 **TD1Hdl; #include "lv_epilog.h" void ReadData(uintptr_t connection, TD1Hdl data); void ReadData(uintptr_t connection, TD1Hdl data) { /* Insert code here */ } Personally I do not like the generic datatype names and I always rename them in a way like this: /* Call Library source file */ #include "extcode.h" #include "lv_prolog.h" /* Typedefs */ typedef struct { LStrHandle key; int32_t dataType; LStrHandle value; } KeyValuePairRec; typedef struct { int32_t dimSize; KeyValuePairRec elt[1]; } KeyValuePairArr; typedef KeyValuePairArr **KeyValuePairArrHdl; #include "lv_epilog.h" void ReadData(uintptr_t connection, KeyValuePairArrHdl data); void ReadData(uintptr_t connection, KeyValuePairArrHdl data) { int32_t i = 0; KeyValuePairRec *p = (*data)->elt; for (; i < (*data)->dimSize; i++, p++) { p->key; p->dataType; p->value; } }

If I build and exe using LabVIEW 2019 Pro , that utilizes the report generation toolkit , can it be run on a PC with just the LabVIEW runtime engine , and , some of these PC's may have LabVIEW 2019 Full installed on them. Will it run in that case ? Regards Dan