Jump to content

Bryan

Members
  • Content Count

    277
  • Joined

  • Last visited

  • Days Won

    6

Bryan last won the day on August 20 2020

Bryan had the most liked content!

Community Reputation

19

About Bryan

  • Rank
    Extremely Active

Profile Information

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

LabVIEW Information

  • Version
    LabVIEW 2018
  • Since
    1999

Recent Profile Visitors

2,693 profile views
  1. 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
  2. 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).
  3. 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...
  4. Shaddap-a you face!
  5. 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
  6. 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
  7. Hopefully this alleviates any concerns about LabVIEW becoming unsupported in the future in favor of NXG.
  8. 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.
  9. 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):
  10. 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
  11. 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
  12. I use "Synkron" and "Create Synchronicity" for daily backups of my laptop to a USB HD. Edit: They're both free.
  13. Well to be fair, some companies have done the same thing to their employees who have never claimed any experience with a particular item/software/etc.. I've worked a couple of places where it has been: "Oh, you double-clicked the icon for "X" application? You're now the resident EXPERT!". Not too long ago, we had a "Kaizen" event where we had moved a piece of equipment in a production cell. I knew nothing about said piece of equipment but it was Windows-Based, so I figured I would go ahead and reconnect the keyboard, mouse, monitor and power it up just to make sure that it still boote
  14. @pawhan11 That sounds exactly how SVN was set up where I currently work - Including having LabVIEW ISOs/Installers stored within. (I wonder if we work at the same company.) One of the drawbacks you've mentioned and I've found with SVN is the ability to search for directories/files/etc. There are tools out there I believe to do this, but, since I'm not an administrator, I can't implement anything myself. Something I've done is use the SVN commands to generate a text file listing of ALL of the SVN contents... then if I need to search for something, I use Notepad or Notepad++ to search for
×
×
  • Create New...

Important Information

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