Jump to content

LogMAN

Members
 View Profile  See their activity

  • Posts

    717

  • Joined

  • Last visited

  • Days Won

    81

 Content Type 

Posts posted by LogMAN

  3. Unable to download certain packages through VIPM

    in Application Builder, Installers and code distribution

    Posted

    Yes this could be the same issue.

    In my case, however, the issue is with SQLite Library (JDP Common Utilities installs normally). Strangely, the reported package URL works in the browser. Only VIPM is not able to download the file.

    That said, I just tested it again and now it works for version 1.16.0 but not for 1.15.0. Again, there is no issue downloading the file with the reported URL: http://download.ni.com/evaluation/labview/lvtn/vipm/packages/drjdpowell_lib_sqlite_labview/drjdpowell_lib_sqlite_labview-1.15.0.114.vip

    image.png.2bcfc3f647fdd59d00d28cb3dd3c0c1c.png

    image.png.f3f929f976edb9fdd2f1e77250123e3f.png

  4. Unable to download certain packages through VIPM

    in Application Builder, Installers and code distribution

    Posted · Edited by LogMAN

    Cross-post: Unable to download certain packages through VIPM - VI Package Manager (VIPM) - VIPM Community

    Does anyone else have trouble downloading certain packages through VIPM?

    For example, I'm unable to download SQLite Library 1.16.0 because "VIPM could not download the package ... from the remote server."

    I checked the error details and was able to locate the package on the server: https://download.ni.com/#evaluation/labview/lvtn/vipm/packages/drjdpowell_lib_sqlite_labview/

    image.png.acd02496197f7870afbe3e7e1fda858d.png

    I tried different versions of VIPM, including 2019 and 2025.1 (build 2772) with no avail.

    Other packages do not appear to be affected. Can someone confirm?

    I'm able to download the package directly from the server with no issues so the problem is with VIPM.

  5. LabVIEW 2025 installation on Ubuntu

    in LabVIEW Community Edition

    Posted

    Just installed it on my Ubuntu 22.04 machine, no problem.

    Did you actually install LabVIEW according to the instructions @Bryan posted? Your logs only show the package feed being added to apt.

    Make sure to follow the instructions from step 5 onwards. In particular, "sudo apt install ni-labview-2025-community".

    Quote

    With the release of version 2023Q1, LabVIEW is installed using package feeds, which is the usual method of installing software on Linux distributions.

    1. Download the  .zip file for the LabVIEW version and edition (Community, Full, Pro.) you wish to install.
    2. Open the .zip file and extract the package file (.rpm or .deb) for your Linux distribution and version. 
    3. Install the package (e.g., For Ubuntu 20.04 use: sudo apt install ./ni-labview-2023-pro_23.1.0.49229-0+f77-ubuntu2004_all.deb)
    4. When the package has installed, refresh the feeds for your package manager.
      • For example, with Ubuntu use: sudo apt update
    5. The package manager now includes feeds for the repositories that contain the edition of LabVIEW you wish to install.
    6. Install LabVIEW with the Linux distribution package manager (apt, zypper, or yum)
    7. The package name is in the format: ni-labview-<version>-<edition>
      • The name of the .rpm/.deb file you extracted has the same name formatting, with extra numbers and supported OS. 
      • LabVIEW 2023 Professional Edition is called with ni-labview-2023-pro
      • Ubuntu use: sudo apt install ni-labview-2023-pro
      • You can use the search tools in package manager to find the correct package (e.g. apt search labview-2024)
    8. Reboot the PC
    9. Note: The LabVIEW Run Time Engine (RTE) package name is labview-2023-rte.
    10. (Optional) Offline help can be installed with the ni-labview-offline-manual package.
      • e.g., sudo apt install ni-labview-offline-manual
      • Please note: The offline help application is known to be unstable on Ubuntu 22.04.

    -- Install LabVIEW on Linux Operating Systems - NI

     

  10. Please check the wiki and let me know if you can access it without issues.

    in Wiki Help

    Posted

    Thanks!

    On 1/10/2025 at 8:16 PM, Michael Aivaliotis said:

    I encourage everyone here on LAVA to find whatever LabVIEW topic they are passionate about and start adding some pages or even fleshing out some existing content that needs improvement. One way to start would be to find some information that you always wish NI had easily available on their website but could never get easy access to. Then create that on the Wiki.

    Second that! The new wiki is also much more responsive, so editing has become a much more enjoyable experience ;)

    That said, here is another issue I stumbled upon: When attempting to edit https://labviewwiki.org/wiki/User_group (or the associated talk page), the server responds with "Server Error 403 Forbidden" and blocks the IP.

    image.png.a66dc3dc3a1ae5a2cf5d1163e34d004d.png

  11. Please check the wiki and let me know if you can access it without issues.

    in Wiki Help

    Posted

    There are quite a few pages affected. Find below a complete list of the ones found with a quick script. Affected conferences are:

    • Americas CLA Summit 2019
    • GLA Summit 2020
    • NIWeek 2019
    • NIWeek 2020

    If the channel cannot be restored, it would be great to have the videos for upload to a new channel that is not linked to the domain if anyone still got them. Just ping me and I'll upload them if you don't want to put them on your own channel. Otherwise, feel free to update the pages with the new video IDs.

    • Popular Post
    • Popular Post

    Build JSON with this structure

    in Code Repository (Certified)

    Posted

    The examples you provide are invalid JSON, which makes it difficult to understand what you are actually trying to do.

    In your VI, the input data is a 2D array of string but the JSON output is completely different. Your first step should be to define the types you need to produce the expected JSON output. Afterwards you can map your input data to the output data and simply convert it to JSON.

    The structure of the inner-most object in your JSON appears to be the following: 

    {
  "Type":"ABC",
  "IP":"192.168.0.0",
  "Port":111,
  "Still":1,
  "Register":"Register",
  "Address":12345,
  "SizeLength":1,
  "FET":2,
  "Size":"big",
  "Conversion":"small"
}

    In LabVIEW, this can be represented by a cluster:

    image.png.47695f3cb674cd296dbc6ff214cb345c.png

    When you convert this cluster to JSON, you'll get the output above.

    Now, the next level of your structure is a bit strange but can be solved in a similar manner. I assume that "1", "2", and "3" are instances of the object above: 

    {
    "1": {},
    "2": {},
    "3": {}
}

    So essentially, this is a cluster containing clusters:

    image.png.b77745180b08477dbbca70017104a3be.png

    The approach for the next level is practically the same: 

    {
    "TCP": {}
}

    image.png.ef7f5db459239de4f3b35b6650faab93.png

    And finally, there can be multiple instances of that, which, again, works the same: 

    {
    "EQ1": {},
    "EQ2": {}
}

    image.png.f47946926340ff6c58df351eb482218e.png

    This is the final form as far as I can tell. Now you can use either JSONtext or LabVIEW's built-in Flatten To JSON function to convert it to JSON

    image.png.13218118e2a15aabca179f0fc658343e.png 

    {"EQ1":{"TCP":{"1":{"Type":"ABC","IP":"192.168.0.0","Port":111,"Still":1,"Register":"Register","Address":12345,"SizeLength":1,"FET":2,"Size":"big","Conversion":"small"},"2":{"Type":"ABC","IP":"192.168.0.0","Port":111,"Still":1,"Register":"Register","Address":12345,"SizeLength":1,"FET":2,"Size":"big","Conversion":"small"},"3":{"Type":"ABC","IP":"192.168.0.0","Port":111,"Still":1,"Register":"Register","Address":12345,"SizeLength":1,"FET":2,"Size":"big","Conversion":"small"}}},"EQ2":{"TCP":{"1":{"Type":"ABC","IP":"192.168.0.0","Port":111,"Still":1,"Register":"Register","Address":12345,"SizeLength":1,"FET":2,"Size":"big","Conversion":"small"},"2":{"Type":"ABC","IP":"192.168.0.0","Port":111,"Still":1,"Register":"Register","Address":12345,"SizeLength":1,"FET":2,"Size":"big","Conversion":"small"},"3":{"Type":"ABC","IP":"192.168.0.0","Port":111,"Still":1,"Register":"Register","Address":12345,"SizeLength":1,"FET":2,"Size":"big","Conversion":"small"}}}}

    The mapping of your input data should be straight forward.

    • Like 3

  16. how to "recieve" .net struct in labview

    in LabVIEW Community Edition

    Posted

    Glad to hear you got it working!

    The reason it doesn't update is explained in the documentation: https://www.ni.com/docs/en-US/bundle/labview/page/loading-net-assemblies.html#d62572e60

    Quote

    After LabVIEW loads an assembly into memory, the assembly stays in memory until you close the application instance that loaded the assembly. While an assembly is in memory, LabVIEW does not detect changes that you make to the assembly on disk. Therefore, before LabVIEW can access any changes to the assembly, you must update the assembly version in memory.

    • Thanks 1

  17. how to "recieve" .net struct in labview

    in LabVIEW Community Edition

    Posted

    Welcome to the LAVA!

    14 hours ago, jayfly said:

    Is there a way to allow for labview to exchange a struct and get the value back from the .net method?

    Wire your struct to a Property Node to access public properties and fields. You can set it to either read or write a value.

    image.png.f7225049a47b6e64fa2d4300f79ed640.png

    14 hours ago, jayfly said:

    In the dll code if I change the input to myStruct data1 (without the ref) I am able to invoke it but once I make it ref (as shown in the code) I get an error - 1316

    Please be careful when changing signatures. LabVIEW does not automatically detect when the type of an argument changes. You'll have to manually update all calling sites to match the new signature which can lead to bad behavior.

    That said, calling by ref or by value both work. Here is a complete example for both of them: 

    namespace DemoLib
{
    public struct MyStruct
    {
        public string Message { get; set; }

        public int Number { get; set; }
    }
  
    public class MyClass
    {
        public string GetMessage(MyStruct data)
        {
            return data.Message;
        }

        public int GetNumber(MyStruct data)
        {
            return data.Number;
        }

        public string CreateMessageByRef(ref MyStruct data)
        {
            data.Message = "Hello from CreateMessageByRef";
            return data.Message;
        }

        public int CreateNumberByRef(ref MyStruct data)
        {
            data.Number = 42;
            return data.Number;
        }
    }
}

    image.png.c36aef6f790a1c9cd070c9c8c2608824.png

    Example.vi

    • Like 1

  19. PostgreSQL Library

    in Database and File IO

    Posted · Edited by LogMAN

    I just went through the examples and everything appears to be working.

    Edit: Running on Windows 11, using LabVIEW 2019 (32-bit)

    As someone who is familiar with your SQLite library, it feels very familiar :)

    Thanks for sharing! :beer_mug:

    • Like 1

  20. LabVIEW licensing

    in LabVIEW General

    Posted

    Welcome to the forums!

    1 hour ago, Cat said:

    If I have a "perpetual" license with 1 year service duration for LabVIEW, at the end of that year, if I don't renew the service, can I still use LabVIEW like always, as if I still had my old permanent license?

    Yes this is exactly how the good old perpetual license works. Even without SSP the license is valid indefinitely.

    At my work we also stayed with LabVIEW 2019 for our codebase. The old licenses are still valid and haven’t been renewed.

    We have an additional subscription license for support reasons, though.

    • Like 1

  21. License an application with expiration date in always offline systems

    in Application Builder, Installers and code distribution

    Posted

    5 minutes ago, Bruniii said:

    I simply want to make inconvenient to keep using it and, most importantly, to go to a third party client and distributed the application forever even if our partnership doesn't go thorough.

    A couple of ideas:

    • Include a license file that clearly explains what they can and cannot do (e.g., no distribution, no use without a valid license, 30 day trial period, etc.)
    • Use a hardware dongle to prevent copies (you can just encrypt the executable, which can then only be started when the dongle is present. No programming required.)
    • If the application is not licensed (e.g., during a 30 day trial period
      • Automatically shutdown the application after 30 minutes
      • Limit the number of data points they can collect (e.g., limit file size to 1 Mib or 100k samples)
      • Turn off certain features (e.g., limit the types of reports that can be produced)

    Of course, it depends on what value the application represents and how "useful" it is outside your partnership. At some point, however, you will have to trust them enough to not misuse your software outside what is being agreed. If you don't trust them enough to uphold such an agreement, it is probably better not to go into a partnership...

  23. Writing Timed Loops in FPGA Modules

    in Real-Time

    Posted · Edited by LogMAN

    I'm not familiar with FPGAs so this might not work, but there is a Timed Loop in LabVIEW: https://www.ni.com/docs/en-US/bundle/labview-api-ref/page/structures/timed-loop.html

    Edit: Just noticed this note in the article linked above:

    Quote

    If you use the Timed Loop in an FPGA VI, you must use a single-cycle Timed Loop. A single-cycle Timed Loop executes one subdiagram per FPGA clock cycle. Single-cycle Timed Loops do not support frames.

    This might be relevant too: https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P8sWSAS&l=en-US

×
×
  • Create New...

Important Information

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

  I accept