Jump to content

Bryan

Members
  • Content Count

    266
  • Joined

  • Last visited

  • Days Won

    5

Bryan last won the day on March 24

Bryan had the most liked content!

Community Reputation

13

About Bryan

  • Rank
    Extremely Active

Profile Information

  • Gender
    Male
  • Location
    Central Pennsylvania

LabVIEW Information

  • Version
    LabVIEW 2018
  • Since
    1999

Recent Profile Visitors

2,313 profile views
  1. 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 would like someone to either confirm or correct this assumption. The problem we're having is that: Nearly all of our TestStand-based production testers have intermittently been losing their database connections - returning an error (usually after the PASS/FAIL banner). I'm not sure if it's a TestStand issue or an issue with the database itself. The operator - Seeing and only caring about whether it passed or failed, often ignores the error message and soldiers on, mostly ignoring every error message that pops up. Testers at the next higher assembly that look for a passed record of the sub assemblies' serial number in the database will now fail their test because they can't find a passed record of the serial number. We've tried communicating with the operators to either let us know when the error occurs, re-test the UUT, or restart TestStand (usually the option that works), but it's often forgotten or ignored. The operators do not stop the test sequence when they go home for the evening/weekend/etc. so, TestStand is normally left waiting for them to enter the next serial number of the device to test. I'm assuming that their connection to the database is still opened during this time. If so, it's almost as though MS SQL has been configured to terminate idle connections to it, or if something happens with the SQL Server - the connection hasn't been properly closed or re-established, etc. Our LabVIEW based testers don't appear to have this problem unless there really is an issue with the database server. The majority of these testers I believe open > write > close their database connections at the completion of a unit test. I'm currently looking into writing my own routine to be called in the "Log to Database" callback which will open > write > close the database connection. But, I wanted to check if anyone more knowledgeable had any insight before I spend time doing something that may have an easy fix. Thanks all!
  2. I use "Synkron" and "Create Synchronicity" for daily backups of my laptop to a USB HD. Edit: They're both free.
  3. 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 booted after the move. A couple of people had seen me do this and now every time there's an issue with it, I'm called to look into it. (Sorry to go OT)
  4. @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 key words in the file. Once found, I then I have the mapping to find it in the SVN Repository. Something I would want to do if it were me - would be to set up a new repository (or reconfigure the current - if able) to use the proper multi-project structure that SVN recommends.
  5. Our logging routines are home grown. Of course, we're not logging EVERYTHING, mostly just overall test results and not each bit of data collected from a UUT. Our older testers log production pass/fail data to CSV files (older testers) or the company's MS SQL database. I've wanted to use SQLite for local logging, but the push back that I got was that it adds a dependency - having to create or install a viewer to access the logged data. Most of the other Engineers that would be accessing that data want something that's ASCII based and easy to read and import into other formats that wouldn't require anything other than common applications to access. (E.g. Excel, Notepad, etc.). They like the KISS method.
  6. I haven't used many VCS systems aside from the very few variants that have existed at my current and previous employers where I had access for LabVIEW development. Since some of those places didn't view LabVIEW as a programming language, I wasn't often granted permissions to have access to their VCS systems. So, my experience is limited. I spent a lot of time in Visual Source Save, but that's not going to help you here. However, I was able to grasp SVN + TortoiseSVN pretty quickly. I've also (for a very short period of time) had a little experience with Trac, though not enough to be a resource for knowledge on it. Additionally, I recall that VisualSVN Server was easy to install and manage an SVN server. I've tried to grasp Git - but having been using TortoiseSVN + SVN for so long that I struggled to quickly grasp Git, so I abandoned it.
  7. Bryan

    NI PCIe-5140s

    I was able to find a Declaration of Conformity dated some time in 2011, and that it's a 12-bit digitizer via a Google search, so it shouldn't be that old. You may have to get into contact with NI to find out more on this card. Unless the card was such a flop for NI that they chose to erase all evidence of it's existence - never to be spoken of again.
  8. The Internet is loaded with examples of file sharing, so I don't really want to reinvent the wheel by writing up a tutorial. A Google search will yield tons of tutorials and examples and you can even search based on your computers' operating systems. For W10, Microsoft has the following article: https://support.microsoft.com/en-us/help/4092694/windows-10-file-sharing-over-a-network
  9. Are you meaning a *.txt file generated from a LabVIEW program saved onto a remote PC? You should be able to set up a shared folder with appropriate permissions on your remote PC and have LabVIEW save the file to the share. I won't get into the details since there's gobs of info on the internet on how to set up shares. Once it's set up, you can just have your LabVIEW program point to the path of the shared folder. For example: If your remote PC name is "REMOTEHOST", you name the shared directory as "LabVIEWDATA", and your text file name is going to be "TestData.txt", the file path for your text file would be (on a Windows machine): "\\REMOTEHOST\LabVIEWDATA\TestData.txt". You can optionally replace the "REMOTEHOST" with the IP address of the remote machine, but if it's a DHCP assigned address, it could change on you in the future.
  10. I'm not sure that you're going to be able to (easily) do what you want to do without some advanced programming to automate/manipulate Microsoft Excel (for instance, using ActiveX or dotNET), even then - I'm not sure it's possible to do what you're trying to do as it involves Microshaft software, over which LabVIEW will have limited ability to control. I agree with 'crossrulz'. Whomever is pushing this requirement may need to reevaluate the need for this functionality.
  11. There is a "Flush File" function in the "File I/O >> Adv File Funcs" menu that you can have execute after every write. However, If you already have Excel open to view the CSV file, I don't believe that Excel will automatically update your spreadsheet contents every time the file changes if that is what you're trying to do. I haven't tried that myself. If the above doesn't work, it may be that Excel doesn't constantly monitor the file and automatically update. You could try using the "Refresh All" button in Excel under the "Data" menu, but you'd have to do this manually. Additionally, you'd have to open your reference to the file with permissions configured in such a way that it doesn't block other applications from using the file if another already has it open. Someone more experienced in Excel and actively monitoring file contents may be able to provide more info.
  12. We all know that they wouldn't be the first company to do that and certainly not the last. It's happened in places I worked before where we were forced to use some obscure, and non-user friendly software applications that were not the industry norm for reasons unknown. If I were to speculate, it was because someone in the upper echelon had been dazzled or were/knew someone who could financially gain by way of it. These applications were, as was said, enterprise level agreements/suites/etc. and likely cost the company a lot of money both in purchasing/agreements as well as the time wasted for learning curves and inefficient usage. Before I joined my current company, "Thou shalt use LabVIEW" was the command from above. Not all were pleased with the mandate at the time and some still aren't, but it's one of the top reasons that helped me to get a job there.
  13. We've been using these Scales by Sartorius. They were Denver Instruments scales incorporated into Sartorius. I don't recall the measurement resolutions, but I do know that they are extremely sensitive. They're USB devices detected by Windows as a Serial COM port device and we use serial commands to interface them (e.g. NI VISA). However, we have had some that stop responding to serial commands over time. Sartorius wasn't much help with the issue though. In the end we ended up taking one apart and rerouting a ribbon cable or otherwise messing with cables to get it to communicate more reliably. We do have another scale that we haven't been able to fix with that method that is just currently sitting on a shelf as it's warranty ran out and we just keep it for manual measurements.
  14. @rharmon@sandia.gov I'm glad to hear that you're making progress! Hopefully TrippLite is able to help.
  15. Yeah... that was my bad. Sorry about that.
×
×
  • Create New...

Important Information

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