All Activity

I used to sell a product called the SQLite API For LabVIEW. It supported encryption. It's no longer available as SQLite removed the hooks and forced most people to use the SEE. SEE is a different source tree that they give you access to after you have paid for it. SQLCipher uses a modified source code tree and rewrites the SQLite source - they basically put the hooks back in again. Whichever way you choose, you will have to compile the binaries yourself and support them. You won't be able to just download the binaries from the SQLite website. It's been a while, and I haven't looked at the source recently, but I vaguely remember there were only a small number of API calls (maybe 2 or 3) that you needed to use

I found a nice solution Encrypted SQLite - A Gift - NI Community would love to hear your experience if you have used something like this.

Has anyone used Encryption with the SQLite Library in LabVIEW? If so, I’d love to hear: Which one you used (SEE or SQLCipher or other approch) Whether replacing the SQLite DLL was enough, or if the VIs needed changes Any gotchas around keys, deployment, or performance Also, what’s the recommended approach if I want to use SEE/SQLCipher/Other with this library? More specifically, if I want to use encryption together with this SQLite Library, what would be the recommended approach? Is it sufficient to replace the SQLite DLL with an encrypted build? Are additional API calls (e.g. sqlite3_key) needed in LabVIEW? Any advice on best practices for production deployments? I understand that encryption is not part of standard SQLite, and I’m mainly looking for guidance from anyone who has already gone down this path. Thanks in advance for any insights or lessons learned.

2026 it's still messed up.

In LV 2025 the ability to open reentrant clones on the cRIO is supported in the LV IDE. I have confirmed that I can open the front panel and probe the BD of reentrant clones running on my cRIO with Linux RT. There is a bug however that inhibits this ability until the execution properties window of the reentrant vi is opened and the code restarted.

Experiencing strange behavior on a cRIO where I have a heater controller that uses 3 PID vi's. The execution properties of the PID vi's are set to Preallocated clone Reentrant. When running from the project the individual PID vi's do not initially open as clones. Only after opening the properties and then restarting do things start working properly. This is a repeatable issue that reoccurs each time the code is deployed to the cRIO from the project. I suppose I could just save the PID vi multiple times with different name but that is a poor solution and cumbersome since the PID vi is in the NI_PID_autopid.lvlib.

Also I have Find IP address and Find token vi's in LabView 2023. For Find IP address you need to install: https://www.vipm.io/package/plasmapper_lib_pl_dns_client/?utm_source=vipm_desktop P1 meter find ip address.vi P1 meter API v2 get token.vi

Labview 2023 P1 meter labview 2023.vi

Can anyone please save it as LabVIEW 2023 🙂 Thanks

A follow up on this: the issue seemed to be with the PXIe-7820R module. We tried another one and it worked. Don't know why. Physical damage? Firmware mismatch? I have no idea but it is annoying since the module was brand new. But my specific problem is solved now.

It is not that LabVIEW MAY unregister the reference, but that it WILL unregister the reference as soon as the top level VI in whose hierarchy the reference was created goes idle. This is by design and the only way to prevent that is to either keep that hierarchy active until any other user of that refnum has finished or delegate creating of the refnum to the place where it is needed, for instance through a LV2 style global maintaining the reference in a shift register and when being called for the first time it will create the refnum if the shift register contains an invalid refnum. True Actor Framework design kind of mandates that all refnums are created in the context of where they are used not some other global instance that may or may not keep running for the time some Actor is using the refnum.

Thanks for the feedback. Will try to check what the problem with VIPM 2026 might be. As to commercial information I saw that you have sent an email to info (at) citengineering.nl and will make sure that the person in question will respond to that.

It seems this is related to the execution level of the constructor. Since the constructor was executed in the scope of the VI I use for testing, once that VI finishes and stops, LabVIEW may unregister the reference before the actor stops. LabVIEW reference about user event registration:

Edit: No, I't doesn't works

I’m working on a project using the Actor Framework to remotely control an oscilloscope. The actor responsible for the oscilloscope overrides the Actor Core to run a loop that acquires data, which is then sent to the root actor for processing. The issue is that when stopping the root actor, the oscilloscope actor throws an error when trying to send the data (which is expected, since the root actor no longer exists). However, the problem is that when executing Stop Core—where the acquisition and UI loops are stopped—for some reason error 1 is generated and the actor does not shut down properly. On the other hand, when sending the Stop message, it does stop correctly. Any ideas? Thanks in advance! Generic Oscilloscope.zip

I guess it's issue with VIPM 2026.. I tried with other machine with 2023 VIPM and it installed fine. Now I'm looking for licensing details of Lua and looks CIT Engineering is not there any more.. Any leads on this @Rolf Kalbermatter?

Hello everyone, I'm having an RTSI issue between two PCIe 6323 cards. I upgraded my PC from Windows 7 or 10 and LabVIEW 2013 to Windows 11 and LabVIEW 2022 Q3. My high-speed acquisition is no longer working. I was using the counter on one card as a clock source for the other card via /Dev1/Ctr2InternalOutput. But it seems this option no longer exists in newer versions of DAQmx. I consistently get error -89125: DAQmx Start Task.vi "Unable to find registered trigger lines between devices on this route. If you have a PXI chassis, correctly identify the chassis in MAX and ensure it has been configured correctly. If you are using PCI devices, make sure they are connected with an RTSI cable and that the RTSI cable is registered in MAX. Otherwise, make sure there is a trigger line available on the shared trigger bus between the devices. Source device: Dev2 Destination device: Dev1" I can't find the RTSI option in NI-MAX. Does it still exist? Is it possible to synchronize the two cards using an internal counter? Thank you for your help Translated with DeepL.com (free version)

Can you tell me more about what the problem is with VIPM? Which VIPM version is that? And what error if any do you get?

Hey Rolf, one of such project popped up in our side and has old scripts in LuaVIEW.. Unfortunately the VIPM is not happy to open Lua4LabVIEW_Toolkit-2.0.5-2.ogp downloaded from https://www.luaforlabview.com/download.htm Seems it's not listed in VIPM.io as well. By any means you know last LabVIEW version it's successfully installed? We are trying with LV2023 64 bit. -BR- Ajay.

Sorry I never got back to you here. That error looks like the extention dll is missing. I would check to see if it is at the path specified in teh error message.

Mapping Enums onto SQLite Text type is intentional. The "Parameters" feature didn't exist back in version 1.7.3. Note that if you are converting data selected from the database, you can convert either Integer or Text as Enums, but with Paramaters (going into the database) one has to make a choice of type for Enums, and the choice I made is Text. You can still make Enums Integers, but you will have to use another method, such as "Prepare Statement".

I am looking for an existing LabVIEW desktop 2023 digital delay locked loop model I can use in an SDR.

I see. I recall that there was an update to the Python integration model in 2022.

@X___ Unfortunately it won't save as 2021, as Python object interaction is not available in this version (see screenshot). For reference, the 'Labview_Python_Bridge' works by creating and interacting with a Python Class/Object.

Hi, we just changed the version of SQLite from 1.7.3.65 to 1.16.0.115 and we found out this library have a bug, we believe. This happen when we try to query a record cluster including enum value. In the Execute SQL (Variant Cluster results).vi/Parse Parameters.vi, originally, the enum is return as Int; now it returns as String. This makes the output variant after goes through variant to data converter become invalid data. Sincerely, Thang Nguyen