Jump to content

Search the Community

Showing results for tags 'drivers'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


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


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

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Personal Website

Company Website

Twitter Name

LinkedIn Profile

Facebook Page



Found 5 results

  1. Hi All, This may be my naivete, but I wanted to know if there is a way to dynamically load the motors (DLLs). Or do I have to load each motor type DLL separately for the front panel (.Net container) of the child class of a motor class? Cheers, M
  2. Hello LAVA community! We've built a free, open-source visual programming IDE that comes with out-of-the-box support for SCPI and most popular instrument brands (NI, Keysight, Tektronix, Rhode & Shwarz, etc). We're looking for beta users and feedback to make this Desktop app as useful as possible. It's completely free and does not require any coding or command-line knowledge. In particular, we're looking for feedback on how this early version of Flojoy compares to LabVIEW and TestStand. Here are a few getting started links: Download Flojoy (for Mac, Windows, or Linux) Flojoy examples for Tektronix instruments Flojoy examples for other hardware devices and instruments [Advanced] How to build your own Flojoy drivers and blocks in Python YouTube channel If you have questions or need help connecting to an instrument, please simply reply below or join our Discord chat. If you don't see your instrument supported in Flojoy's blocks, let us know and we may be able to add it for you. Screenshot of Flojoy desktop app:
  3. We use USB-connected Microsoft Smart Card Reader. The devise crashes sometimes. It does not happen often thus search for the reason could take time. The only way to get the devise functioning again, is to open Device Manager, click Uninstall then Scan for hardware changes (that installs the Reader again). Is there any method to do this from LabVIEW? I.e. send commands to reinstall the USB device? I know this could be a bad fix. However, it can help in long-time tests (while we are searching for reason of these crushes). Thank you
  4. 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
  5. Hello. I am trying to connect some Beckhoff EtherCAT modules to a cRIO and at the beginning everything was looking good, but now I have some serious troubles with the EtherCAT drivers. When I am trying to start or deploy a project everything is crashing, cRIO is rebooting, PC to cRIO communication is lost and nothing is working. The problem is with the EtherCAT drivers, because if the EtherCAT drivers are disabled everything is working. Does anybody has any idea what should I try? Did somebody managed to use Beckhoff EtherCAT modules with a cRIO and LabVIEW 2009? Any help or reply is much appreciated. Kind regards, Greg
  • Create New...

Important Information

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