Jump to content

Search the Community

Showing results for tags 'max'.

  • 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 2 results

  1. Hi guys We had software for a FLIR AX5 thermal camera that worked perfectly. The camera started giving problems in the field and we had to replace it with a newer version with the latest firmware. No I can't seem to communicate with the new camera. MAX tells me that it's unable to get attribute. Error 0xBFF69011 Anybody else had this problem and how did you solve it? Thanks in advance.
  2. I had to go to a customer for a very old project of theirs. They still use LV6.1 , tradiotional DAQ , ... After reboot of the PC and login by another user all configured DAQ tasks were gone. There is no documentation on the setup so recreating is not an option. They have an old image of the PC so .... where does MAX (version 2.2) store it's DAQ tasks, scales etc ? Thanks Wim
  • Create New...

Important Information

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