Jump to content

The Engineering Bear

  • Posts

  • Joined

  • Last visited

Profile Information

  • Gender
  • Location
    Austin, TX

LabVIEW Information

  • Version
    LabVIEW 2016
  • Since

The Engineering Bear's Achievements


Newbie (1/14)

  • Week One Done
  • One Month Later Rare
  • One Year In Rare

Recent Badges



  1. Thank's y'all for the feedback! I realized that I had been uploading a non working version, but that just gave me some time after NI Week to work in some of your suggestions! The one I'm most curious about is switching from OS to Target_Type. Using Target_Type definitely has more options, but then how would you specify things like file path so that the user knows where to find it/make sure they don't put it some where they aren't supposed to? -Bear
  2. 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 is occurring. I've gotten some feedback from friend's regarding making it a global variable that wrote to variables and had a separate VI to do the logging, but this takes away the "ease of use" I am going for for the user. I've included an example application to show how it can be used for a simple state machine. I'd love getting more insight into what I could do better though which is why I'm coming here! Let me know what y'all think! - Bear Crash Logger Project and VI.zip Crash Logger.vi
  • Create New...

Important Information

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