Jump to content

JKSH

Members
  • Posts

    499
  • Joined

  • Last visited

  • Days Won

    36

JKSH last won the day on December 22 2023

JKSH had the most liked content!

1 Follower

Profile Information

  • Gender
    Not Telling
  • Location
    Western Australia

LabVIEW Information

  • Version
    LabVIEW 2020
  • Since
    2011

Recent Profile Visitors

13,857 profile views

JKSH's Achievements

  1. Then I'm afraid I don't know what's going on.
  2. Try logging in as admin (or use su admin on the terminal)
  3. 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:
  4. 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.
  5. I sense a candidate for https://thedailywtf.com/
  6. What communication protocol(s) does your digital X-ray plate use to receive commands and transmit images?
  7. (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)
  8. From a console, run ldd on libmain.so. Any missing dependencies?
  9. 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.
  10. 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.
  11. 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
  12. Open "My System" > "Software" and compare the list for the 2 PCs. I suspect missing/outdated DAQmx drivers.
  13. 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
  14. 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
  15. 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.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.