Jump to content

Search the Community

Showing results for tags 'vipm'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Software & Hardware Discussions
    • LabVIEW General
    • LabVIEW (By Category)
    • Hardware
  • Resources
    • LabVIEW Getting Started
    • OpenG
    • Code Repository (Certified)
    • LAVA Code on LabVIEW Tools Network
    • Code In-Development
  • Community
    • LAVA Lounge
    • LabVIEW Feedback for NI
    • LabVIEW Ecosystem
  • LAVA Site Related
    • Site Feedback & Support
    • Wiki Help

Categories

  • *Uncertified*
  • LabVIEW Tools Network Certified
  • LabVIEW API
    • VI Scripting
    • JKI Right-Click Framework Plugins
    • Quick Drop Plugins
    • XNodes
  • General
  • User Interface
    • X-Controls
  • LabVIEW IDE
    • Custom Probes
  • LabVIEW OOP
  • Database & File IO
  • Machine Vision & Imaging
  • Remote Control, Monitoring and the Internet
  • Hardware

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Personal Website


Company Website


Twitter Name


LinkedIn Profile


Facebook Page


Location


Interests

Found 7 results

  1. This is an offshoot of https://lavag.org/topic/19414-can-i-save-as-a-vipb-file-in-vipm-and-keep-the-old-palette-if-i-change-the-source-directory/. That thread discusses hand-modifying the XML data in a *.vipb file, which Jim Kring himself seems to accept as a viable solution in some cases. However, when I try that, VIPM says, "VI Package Builder was unable to open the build spec due to an error." I initially thought this was new behaviour introduced in VIPM 2016, but downgrading to VIPM 2014 SP2 didn't change anything. I'm now unable to downgrade any further, as my PC is convinced that 2014 SP2 is still installed (even though it's not...) Could someone kindly try the attached *.vipb file and see if it opens? It's a bare minimum default file, with only a description summary added. I've hand-modified the summary from "Lorem ipsum" to "Larem ipsum" and now VIPM refuses to open it. Thanks! Dummy.vipb
  2. This maybe has been ask/answered/discuss before but here it is. Is there any VIPM alternative out there? If not, It will be very interesting to start a discussion whether an open source version is feasible and how many members in the community are willing to work on it. I know JKI has a great product already but seems like development has come to halt wrt VIPM. Any comments?
  3. Hi all, I have been trying to use VIPM to distribute drivers that rely on a .NET framework that is unsigned (i.e not in the global assembly cache). My issue is that after the package is installed, none of the VIs will work because LabVIEW cannot locate the .net assembly. However, if I launch labview by opening the library VIPM installed, all of the VIs will work, and LabVIEW is able to locate the the .Net framework and it appears in the main application instance. I need to be able to use the installed vis all the time, not just when LabVIEW is launched in this particular way. Here is a link to all the all the files I used: https://www.dropbox.com/sh/yjt2a0t8msxhgfn/AAC4VVW-hPawwXtGMrZ6wuIra?dl=0 Here are the steps I went through: 1) We put all the .NET dlls and the LabVIEW.exe.config file in the Labview directory. 2) We installed the package on our computer. 3)We closed everything and relaunched Labview from the start menu. Then accessed the BioRobotics/Vicon palette. 4)We placed the Get Ref subVI on the block diagram, opened it up, and ran it it. 5) We got the following error: We also get a similar error for any VI that uses a method associated with the .NET dll. 6) However, if we again start with everything closed and launch Labview by clicking on the VICON.lvlib located in the vi.lib 7) Then repeat steps 3 and 4. We do not get any errors in the VIs on the palette, and the .Net assembly loads fine. We can even close the library and everything still works. Somehow opening the library first makes LabVIEW know to load the ViconDataStreamSDK_DotNet assembly when using functions on the Vicon palette. If anyone does attempt to build a new package, it is worth noting that I included the dlls in the source files, and in the same folder as the vipb: Thanks! Callan
  4. Let me start with some context We have to differentiate from a Production environment (to produce data) and Development environment (to develop test and debugging). Our code (very simplified) is organized in this way - Tests (Actual vi that will produce results) - System files (support vi, drivers, common functions etc.) Both are under source control We have decided to make VIPM's (residing in vi.lib) for all System files and leave the Tests files where they are (random folder under source control). This means the all the vi's inside Tests will have links to the System Files (inside vi.lib now) and that works pretty well for the Production Environment, but when we want to use the Tests in the development environment (Tests and System Files in a random folder) we need to re-link all the Tests to point to the local files and not the System Files inside vi.lib. The question is: Is there any way to manually update the references of the Tests so we can choose from where we want to get the System Files?
  5. Does anyone have any ideas as to why I would be getting the following message while trying to install the OpenG Toolkit through VIPM? I'm using LabVIEW 2014 SP1 (32-bit) and Windows 7 Enterprise SP1 (64-bit)
  6. I tried to install one of my packages using VI Package Manager 2013 and was surprised to see the error message "This package is not compatible with any LabVIEW version on this computer." The package is supposed to be compatible with any LabVIEW version >= 8.6 and I have 2013 installed. After some Googling, I found this: http://digital.ni.com/public.nsf/allkb/9A84C532AB9268BD86257CEF00794E70 It turns out that I had compiled the package using VIPM 2014 and thus it is not compatible with VIPM 2013. I suppose that this makes sense but the error message shown in VI package manager is very misleading. So in conclusion... Keep VIPM up to date otherwise you might get misleading error messages when trying to install new packages.
  7. We develop a number of test systems for use in China at our production facility and when we ship it for whichever engineer is on site at the time to debug. Now because the PXI racks that are used may well have been bought in China we can not guarantee that the PXI rack will all the required software and drivers so we make sure that any software or drivers are included in the package we send as as access to the internet can be tricky or just so slow as to be unusable. The question is that we a number of components that we install from the VIPM but that is not allays possible via the internet in China, is there a way to download the installer files and then use them locally on the PXI rack on site. My thanks in advance.
×
×
  • Create New...

Important Information

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