JKSH

Yes you can. The official form is at https://www.ni.com/en/forms/perpetual-software-licenses-labview.html Some things to keep in mind: There is a current promotion (valid till the end of December 2024) where those who used to have an SSP can renew it today as if the SSP never expired in the first place. That means you can get the latest version of LabVIEW, under a perpetual license, at a discounted price (compared to buying it "new"): https://forums.ni.com/t5/LabVIEW/LabVIEW-subscription-model-for-2022/m-p/4398958#M1296289 Quotes/sales are now handled by external distributors, rather than Emerson/NI. Lots of people have reported that they didn't get a response to their quote requests, or didn't get the expected discount applied. If that's the case, message Ahmed Eisawy, the Director of Test Software Commercialization (who wrote the forum post in my link above) and he'll get it sorted out.

I sense a candidate for https://thedailywtf.com/

What communication protocol(s) does your digital X-ray plate use to receive commands and transmit images?

(Not to downplay the importance of standardization, but rather highlighting that it's hard. And as @VDB said the old ones will hang around for a lifetime)

From a console, run ldd on libmain.so. Any missing dependencies?

Your screenshot showed that it's a "USB-9215A" which, according to https://download.ni.com/support/manuals/371568e.pdf, is a USB-9162 + NI-9215 😀 There is the "Reset NI MAX database"... https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P8awSAC Beware, this completely wipes your hardware configuration (e.g. any custom Scales, or custom Channels under "Data Neighborhood") so you'll need to reconfigure them afterwards. I'm running out of ideas, I'm afraid. The only other things I can think of trying are: Try an older version of DAQmx (only possible if you're not using LabVIEW 2020), or contact NI tech support.

Congrats! Fancy giving CBOR a go, if you're looking for something to do? It's designed to work well with CoAP. I'd imagine that the API can be modelled closely after Dr Powell's JSONtext.

What happens when you click "Self-Test" instead of "Test Panels..."? Have a look at Windows Device Manager. Any error messages related to your chassis? If you still can't find any clues, contact NI tech support Anyway, I just realized that your 2 machines actually have different hardware. The one that's not working has a USB-9162, not a cDAQ-9171: https://download.ni.com/support/manuals/371568e.pdf

Open "My System" > "Software" and compare the list for the 2 PCs. I suspect missing/outdated DAQmx drivers.

I don't have experience with S7 myself, but have you seen this toolkit? https://www.ni.com/en-us/support/downloads/tools-network/download.sp7-toolkit-for-labview.html

It's not clear to me whether the EMQX public broker supports v5 or not... https://www.emqx.com/en/mqtt/public-mqtt5-broker ...but their downloadable one does, apparently: https://www.emqx.com/en/try?product=broker

The feed needs to contain a Packages.gz file (which is a gzip'ed copy of a Packages file) that describes the available packages. You can see a sample at http://download.ni.com/#ni-linux-rt/feeds/2022Q4/x64/main/x64/ You can use NI Package Manager to generate this for you! Put all your *.ipk files in a folder on Windows, then use Command Prompt/PowerShell to cd into that folder and call: "C:\Program Files\National Instruments\NI Package Manager\nipkg.exe" feed-create . I don't think you can just use a local folder as a feed -- AFAIK, opkg can only retrieve feeds from a web server: https://readthedocs.web.cern.ch/display/MTA/[NILRT]+How+to+create+a+local+feed+for+Linux+RT Here are my brief notes on how to install an *.ipk on a Linux RT system: https://jksh.github.io/LQ-Bindings/setup-nilrt.html (this page shows 3 ways: Adding a feed using NI MAX, adding a feed via an SSH console, or installing the *.ipk directly without a feed) Not if your package contains compiled code. Each package's control file (and their corresponding entry in the Packages file) must specify the supported Architecture (e.g. "x64"). opkg/NI MAX/SystemLink will only show the packages that are compatible with your device architecture. If the package is architecture-independent (e.g. if it installs TLS certificates or documentation), then you can specify "any" as the Architecture.

This looks kind of similar to the bug that @Darren talks about in the video below (at 30:44). Try this: Disconnect your "CONSIGNES" terminal from the type def, delete the property node, re-connect the terminal to the type def, and then re-create the property node... does that help?

No, each license is for a particular version of the LabVIEW FPGA module. So if you bought LabVIEW FPGA Module 2015, then you can't use it with LabVIEW 2016 or newer. "Perpetual" just means you can keep using that version forever. NI no longer officially sells perpetual licenses. They are now using the subscription model from this year onward: See also https://forums.ni.com/t5/LabVIEW/LabVIEW-subscription-model-for-2022/td-p/4204448 (some people said how they still managed to get a copy of a perpetual license, but it took some arm-twisting)

...then you won't be able to develop software for the cRIO 9035 😞 Start talking to your supervisor and checking your LabVIEW modules. You can't do your project without the Real-Time Module. You did say before they had "an NI Developer suite license"? The Real-Time module should be part of the Developer Suite. No, it's not RT-only. In your Block Diagram pallette, look for Data Communication > Current Value Table. You should also find the files in C:\Program Files (x86)\National Instruments\LabVIEW 20xx\vi.lib\NI\Current Value Table<vi.lib\NI\Current Value Table

Perhaps @X___ is pointing to the timestamps of the latest forum posts?

This announcement might be of interest: https://create.vi/ni-and-jki-partnering-on-package-management-in-labview-d243b13ae3a6 "Features in VIPM Pro 2023+ (Paid): NI Third Party Licensing and Activation Toolkit (TPLAT) Integration"

Which one? NI has a few different web servers: https://forums.ni.com/t5/SystemLink/Relationship-between-quot-NI-Web-Server-quot-quot-NI-System-Web/td-p/3662789 If you're using the new "NI Web Server" rather than the old "NI Application Web Server", try asking at the SystemLink forum.

Try F2 or F12 too? Other than that, Google "Windows 7 lost password". There are various hacks around; I've never tried them with WES7 but I'd imagine that some should work.

Yes. The RT code gets compiled into an .rtexe file which is loaded by the LabVIEW runtime engine, while the FPGA code gets compiled into a bitfile which is loaded into the FPGA. You can use User-Defined Variables, or you can use Controls/Indicators on your top-level FPGA VI: https://www.ni.com/docs/en-US/bundle/labview-fpga-module/page/lvfpgaconcepts/pfi_data_transfer.html For your slow use-case, it probably doesn't matter which one you pick. I suggest you get something going for the Scan Engine first. Add your FPGA after. Not sure what your question is here, sorry. Just search for "9202" in the NI Example Finder and run an example on your cRIO.

Yes, it's called Hybrid Mode: https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000YIDfCAO&l=en-US That's a shame. 100Hz is definitely possible with the Scan Engine (on supported hardware).

No, it doesn't. You can use 32-bit LabVIEW to develop software for your 64-bit cRIO. In fact, 32-bit LabVIEW supports more drivers/toolkits for cRIO than 64-bit LabVIEW. Only if you want to write FPGA code. Do you strictly need to write custom code for the FPGA? If not, then I suggest you skip this. FPGA programming is subtly different and more complex than regular RT programming. If you're new to cRIOs and you only have 1.5 months, then you could end up taking a huge percentage of that time trying to figure out how to use the FPGA. So my question is: What is the maximum sample rate that your AI, AO, and DO need?

NI MAX is for testing DAQmx hardware (like CompactDAQ, for example). DAQmx support was added to CompactRIO-904x and 905x, but cRIO-903x is not supported. You only have Scan Engine and FPGA, so you cannot test your hardware with NI MAX. Use the NI Example Finder: https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000YIKbCAO&l=en-US Good luck!

These warnings look weird to me. The problematic functions are all declared in zmq.h which is included by zmq_labview.c, so you should have no "implicit declarations". I haven't used this library before, but I suspect something went wrong during compilation of lvzmq64.so. You can check it with chrpath --list. If it exists, you can change it with chrpath --replace.

In the beginning, "permanent"/"perpetual" activations were exactly that: You activate it once, and then it would stay activated forever (unless you deliberately deactivate/uninstall it, or your machine dies). A few years ago, NI's activation server changed its behaviour: After you activate something, it would stay activated until early August. Even if you have a perpetual commercial (non-subscription, non-academic) license, you have to re-activate every August. It's a weird system: If I activated at the end of July, I would need to re-activate again within 2 weeks. I don't know if Academic licenses were treated any differently or not (my company had a Developer Suite), but your descriptions sounded like what we had to go through.