JKSH

It feels strange to me too. As I understand it, the "no merge" clause makes libraries legally unusable by others.

A quick search reveals that the "no merge" clause is found in numerous different software licenses: https://www.google.com/search?q="merge+the+Software+into+any+other+software" My best guess is that the clause was originally written for standalone applications (meaning that you're meant to run the software as-is, without copying its source code into your own, or linking your own software to its binaries). However, somewhere along the way the clause got copied directly into a library license, without the involvement of a lawyer who understands software licensing.

Perhaps @mabe can clarify? He helped at: 

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?

12 hours ago, VDB said:

The industry is trying to establish unified communication standards for laboratory and bioprocess equipment in the last years

(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?

2 hours ago, Bruniii said:

You are correct, the chassis in this PC is the NI-9162, while on the others PC the 9171 is used. I totally forgot about it...still, it worked for months without problems. May I ask you how did you found out? I cannot see any clue from the screenshot that I shared in this topic!

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 😀

2 hours ago, Bruniii said:

Is the reset on MAX the only "reset" available? Should I remove something after uninstall LabVIEW and before a new installation to clen everything and start fresh, hopefully without this error?

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.

16 hours ago, ShaunR said:

Well.

I got a rudimentary CoAP API working (over DTLS). It's a much better protocol than MQTT, IMHO.

I'm beginning to run out of protocols to implement. 

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.

On 6/28/2023 at 5:26 PM, Bruniii said:

I have updated the DAQmx divers to the same version installed in the working PCs but nothing has changed and I have the same error even after multiple restart of the PC

• 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

On 6/27/2023 at 3:06 PM, Bruniii said:

Can somebody help me, suggesting something else I could try, having only a remote access to the Windows PC?

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

4 hours ago, ShaunR said:

Anyone know of a public V5 server?

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

3 hours ago, Mads said:

I assumed you could add a ldirectory of ipk files as a local feed, and that that would allow you to see it as an option in the software install menu of the RT image....

I tried adding a local folder as a feed...but the package did not show up in the list of available software.

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)

3 hours ago, Mads said:

is there a way to make one package with support for both arm and x64 e.g., or would you always need separate ipk files?

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?

4 hours ago, Dan Bookwalter N8DCJ said:

we bought a perpetual FPGA license , my assumtion , is that means the license will work on all future versions of FPGA

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.

4 hours ago, Dan Bookwalter N8DCJ said:

we need (or highly advised) to get an RT perpetual license if such a thing exists.

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)

4 hours ago, Dan Bookwalter N8DCJ said:

I only have the FPGA Module license , they didnt buy a RT Module.

...then you won't be able to develop software for the cRIO 9035 😞

4 hours ago, Dan Bookwalter N8DCJ said:

I need to start hitting this hard so , any advise is appreciated.

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.

4 hours ago, Dan Bookwalter N8DCJ said:

the Current Value Table looked like it might be somethign I could use , i downloaded everything vi JKI PM , everythign installed fine. But it doesnt show up anywhere. is this a RT only componenet ?

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

25 minutes ago, ShaunR said:

Too obtuse for my smooth brain. You link to a COBOL forum and imply something but I have no idea what you are implying or it's relevance.

Is it a spam post? 

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"

4 hours ago, Mark Yedinak said:

NI Application Web Server

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.

6 hours ago, viSci said:

I have tried getting to the bios (F10 or Del) but cannot even get that to work.

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.

3 hours ago, Dan Bookwalter N8DCJ said:

my guess (and is purely a guess) anything under the FPGA/RT sections of the LabVIEW project get compiled and loaded on the cRIO ? 

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.
 

3 hours ago, Dan Bookwalter N8DCJ said:

Most of what I have seen is using User-Defined Variables , is that the standard/accepted approach ? 

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.

3 hours ago, Dan Bookwalter N8DCJ said:

In the long run , I will be dealing with 7 modules in the chassis , 5 various AI modules (Voltage , mA, TC) and two output modules (SSR and AO). Nothing is highspeed , I just need to start working on this more than I have been able to , and to try and get up to speed a little ...

I suggest you get something going for the Scan Engine first. Add your FPGA after.

3 hours ago, Dan Bookwalter N8DCJ said:

And , when I see examples , mainly just images on the internet for now , I see an Open FPGA VI Reference , once again my assumption is that is a reference to the VI that is on the cRIO , I also assume , since I can rationalize both scenarios , that the vi's referred o as "Main" are loaded to the cRIO , and the "Host" ones run on the PC , I am going from memory so , that will be a bit fuzzy...

Not sure what your question is here, sorry. Just search for "9202" in the NI Example Finder and run an example on your cRIO.

3 hours ago, Dan Bookwalter N8DCJ said:

can a chassis mix RT and FPGA ?

Yes, it's called Hybrid Mode: https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000YIDfCAO&l=en-US

3 hours ago, Dan Bookwalter N8DCJ said:

I was told the plan was to run this in scan mode , but , the one module is an NI 9202 filtered AI module , LV says it is FPGA only ...

That's a shame. 100Hz is definitely possible with the Scan Engine (on supported hardware).

3 hours ago, Dan Bookwalter N8DCJ said:

does bitness between LV and the cRIO have to match

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.

3 hours ago, Dan Bookwalter N8DCJ said:

I also see i need to download the XiLinx drivers

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?

2 hours ago, Dan Bookwalter N8DCJ said:

I cant find how to do a test in Ni-Max like the examples I see on NI.com

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.

2 hours ago, Dan Bookwalter N8DCJ said:

any examples would be greatly appreciated

Use the NI Example Finder: https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000YIKbCAO&l=en-US

Good luck!

On 8/19/2022 at 6:22 PM, Łukasz said:

zmq_labview.c:868:8: warning: implicit declaration of function ‘zmq_leave’; did you mean ‘lvzmq_leave’? [-Wimplicit-function-declaration]
  868 |  ret = zmq_leave( s->sock, group );

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.

3 hours ago, Łukasz said:

RPATH and RUNPATH are set on compilation porcess, so I cannot change them easly. 

You can check it with chrpath --list. If it exists, you can change it with chrpath --replace.