Jump to content

Search the Community

Showing results for tags 'cin'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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

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


Location


Interests

Found 1 result

  1. I have some old code that has CIN calls from LabVIEW 7.0. When I open the code, it throws errors because the old code uses CIN; which is not supported by LV 2010. Here is my problem, the CIN calls are from an old hardware driver that is unavailable. (The developer is not responding and doesn't have the software online) I have the .lsp files that were used to create the nodes but I have no way of knowing (that I know) which lsp is being used in which CIN node. ON top of this, I am not even sure that the Call Library Function node will work with compiled LSP files. Does NI maybe have a good utility for porting these over? Thank you! - Michael
×
×
  • Create New...

Important Information

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