Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Bryan last won the day on August 20 2020

Bryan had the most liked content!

Community Reputation


About Bryan

  • Rank
    Extremely Active

Profile Information

  • Gender
  • Location
    Central Pennsylvania
  • Interests
    Stuff and things.

LabVIEW Information

  • Version
    LabVIEW 2018
  • Since

Recent Profile Visitors

3,000 profile views
  1. AutoIT is the first tool that comes to mind. I'm not familiar with it personally, but know some people who have used it in the past. I don't know if there are any issues using it with LabVIEW, but I know it has been used to automate control of other types of Windows applications.
  2. Here's an example of converting a text string to bytes to an "ASCII Hex" string.
  3. Another SVN user here (With TortoiseSVN as standalone and also with an SVN server). Was introduced to it years ago and have had no reason yet to move to any others. I like it for its (relative) simplicity when compared with others. For LabVIEW, you can configure it to use the LVCompare and merge tools, (there are some blurbs online you can search for that tell you how to configure it). Drawbacks that I've found (in my current employment) is lack of organization in the repository (poor pre-planning). They use one repository for EVERYTHING and it's gotten huge and didn't plan
  4. You could also create your own VI that establishes a connection to the database where the credentials are stored as constants and remove the block diagram. To do this, you have to create a project, then source distribution with that VI (always included). Then, in the settings for that VI in the distribution, you select the option to remove the block diagram. This is currently the most secure method of hiding LabVIEW source that I'm aware of. The only problem is that if the credentials ever need to be changed, you have to change it in the source VI, re-build the source distribution and
  5. Sorry, I missed that detail. The LabVIEW program automates the targeting and actuation of firearms. (To the FBI/NSA agent monitoring this post - this is what is known as a joke).
  6. My LabVIEW FPs are color schemed ONLY in red, white, and blue, with animated U.S. Flag GIFs or Bald Eagles used in each custom control. But my BDs are bloated to 3X my monitor size...
  7. Shaddap-a you face!
  8. Bryan

    Dear NI

    I agree, I have garnered great disdain for Winblows over the years as far as the negative impacts to our testers from updates mandated by IT departments, obsolescence, the pain to install unsigned drivers, just to name a few. I would hate to see NI stop support for Linux as it has been growing in popularity and getting more user friendly. Linux is a great and stable platform, though not for the faint of heart. It takes more effort and time to build the same thing you could do in shorter time with Windows. However, If LabVIEW were open source and free, you could theoretically build syst
  9. If you're using 32-Bit LabVIEW, you may have to copy it to the "x86" Program Files Directory at: C:\Program Files (x86)\National Instruments\LabVIEW 2015\user.lib
  10. Hopefully this alleviates any concerns about LabVIEW becoming unsupported in the future in favor of NXG.
  11. The checkbox for it is right there in your image, you're looking at the "Report Format:" drop-down. "Generate PDF Report" is on the left side of the dialog window and looks currently un-checked.
  12. I just found out this morning that "Runstate.Execution.TSDatabaseLoggingDatalink{GUID}" isn't a valid location for TestStand 2010 (and not sure what other versions). For 2010 at least, it is "Runstate.Execution.TSDatabaseLoggingDatalink{Database Schema Name}". After a lot of futzing around yesterday, I simply added a statement expression step after "Log to Database" in the "Log to Database" callback sequence. Note: I didn't want to create a new local variable in the sequences of each tester, so I used Step.Result.Status to temporarily hold my value (Probably not a good practice, haha):
  13. I figured I would post a resolution to my own problem for anyone who may run into the same thing. While searching for something unrelated today, I stumbled across my answer. TestStand creates a connection to the configured database with the first UUT that is tested and maintains that connection while UUTs are continuously tested. Only when the sequence is stopped is when the database connection is released. I was able to come up with my solution by essentially compiling what I found in my searches. In my situation - "hiccups" in network connectivity or with the SQL server cause t
  14. TestStand Version(s) Used: 2010 thru 2016 Windows (7 & 10) Database: MS SQL Server (v?) Note: The database connection I'm referring to is what's configured in "Configure > Result Processing", (or equivalent location in older versions). Based on some issues we've been having with nearly all of our TestStand-based production testers, I'm assuming that TestStand opens the configured database connection when the sequence is run, and maintains that same connection for all subsequent UUTs tested until the sequence is stopped/terminated/aborted. However, I'm not sure of this and
  • Create New...

Important Information

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