Jump to content

Search the Community

Showing results for tags 'atmel aviiva camera'.

  • 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. Hi all, I am using a Atmel Aviiva camera in my application. I need to change some camera parameters permanently. So , as I learnt through web, I can do it by editing the associated *.icd file. But the aviiva files look different. They contain the camera parameters for all interface types. (i.e., PCIe 1430, PCIe 1433 and so on). So to edit the exact parameter I need to find the interface type being used now. How do I get the interface type programmatically? Is this information stored anywhere? Or Is there any available method other than this to permanently edit the IMAQ camera parameters? Thanks in advance for your help. Prabhu
×
×
  • Create New...

Important Information

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