Jump to content

Search the Community

Showing results for tags 'crash'.

  • 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


Facebook Page


Location


Interests

Found 8 results

  1. Here is another bug I discovered in LV2019+ which reliably crashes LV. Simply connect a set to the map input of the Map Get / Replace Value node on the IPE: This VI is executable in LV2019 SP1 f3, which means that you can actually build that into an executable without noticing. I have reported this, but there is no CAR yet.
  2. Hi, My LabVIEW 2016 32 bit is crashing a lot. I can guess it is related to: 1. incompatibility with DAQmx 9.1.5 and the related device driver which I need for LabVIEW 8.5.1 which I also use (NI's support jumped on that issue yet I think it is not related) 2. an addon that I use to access OpenCV leaving some references open in the dlls 3. Controls with same label or with no label (I believe that this is the issue -LV can't recover correctly in such cases) However, I don't want to guess like NI's support that it is point 1 and do nothing to prove it. I expect t
  3. Hey y'all, Wanted to look for some feedback on some code I made for troubleshooting crashes and hangs for medium to large LabVIEW applications. Wanted a way for a user experiencing a crash/hang to have a simple way of narrowing down where the problem is occurring. The VI is named Crash Logger.vi and it only requires the VI itself to use. No type def's, additional VI's, or other necessary parts. The reason for this is so that a user can drop it in multiple parts of their application and have it log the current state and some information on system state to narrow down where a crash/hang
  4. Hi everyone. I wrote wrapper in Visual Studio for OpenCV calibrateCamera() function. Every operation like converting 1D array of points to vector<vector<Point2f>> etc, works ok, except most important thing. When function ()calibrateCamera is called, LabVIEW crashes. When this line is commented out, dll works ok (at least labview is still alive). Im out of ideas. I suspect that this is problem with memory management but i dont have an idea where it cames from. Function do not operate directly on data passed from LabVIEW. Ultimately I can compile code as exe and call it via cmd, b
  5. Hi, I have several USB instruments (Agilent/Keysight optical power meters) which I can talk to via USB. To minimise the time "wasted" by transferring data between the instruments and the PC I would like to query them in parallel. Unfortunately, LabVIEW doesn't agree with that strategy and reliably crashes when doing so. It doesn't matter which command I send, so here's a sample snippet, where I just query the instrument ID repeatedly. I don't even have to read the answer back (doing so won't make a difference): This will kill LabVIEW 2012 and 2014, both 64bit without even popping up th
  6. Hi all ! Currently building a TS custom interface for one of my customer, I decided (this time) to manage user rights directly using TS user manager. Since I applied this solution, LV randomly crashes (or not crash) without giving any message that could help on resolving the issue. This is not the first time I create TS custom interfaces, but this time there are few new things compared to other HMI I built : newer LV | TS versions than usually (LV 2011 SP1.f2 and TS 2010 SP1.f1) user rights are managed using TS user manager For my user manager, I used a functional global to retain the
  7. Has anyone noticed this on LabVIEW 2011? I know 1 other person who has experienced this. Want to know if it's pervasive. Doing a string search in the development environment of your VIs cause LabVIEW to crash
  8. I have posted on the NI forum (here) but didn't get any response sine 5 days. I have came across a nasty bug that caused Labview 2010 SP1 (Running Win 7 Ultimate x64 bit) to crash without any warning. To replicate the bug do the following: Add a numeric control and another indicator to the front panel Switch to block diagram and add a feed back node Connect the initializer terminal of the feed back node to the output of the control Now do ANY of the following to cause the bug: Press the run button (which is broken due to not connecting the input of the feed back node) it will turn to a n
×
×
  • Create New...

Important Information

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