Jump to content


  • Posts

  • Joined

  • Last visited

LabVIEW Information

  • Version
    LabVIEW 2018
  • Since

Contact Methods

Recent Profile Visitors

1,579 profile views

tlerunner's Achievements


Newbie (1/14)

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

Recent Badges



  1. Implement your asynchronous VI as a DQMH. Create API's that send messages to it. Call the API's from TestStand.
  2. Try setting the VISA input and output buffers to something like 1024.
  3. Hi Craig, I was recently tasked with using a PicoScope (5000 series). I got it to work but am puzzled by the interface with the DLL. The DLL writes directly to LabVIEW memory and the data "magically" appears on a LabVIEW wire. See: https://forums.ni.com/t5/LabVIEW/When-is-dataflow-not-data-flow-Updating-LabVIEW-Arrays-through/m-p/4020764#M1150779 and: https://www.picotech.com/support/topic40424.html?sid= Are you using the same approach and has it been reliable? Thanks, Tim
  4. We are looking for an individual with 5 to 10 years of good LabVIEW and TestStand experience who wants to live/work in the Fort Collins, Colorado area. Local candidates will be given priority but we will consider other applicants if they are a good fit. We are a consulting firm with a number of long term customers in Northern Colorado and across the US. Most of our projects are automated test applications but we also do general automation. Our specialty is LabVIEW/TestStand applications typically using National Instruments hardware. If interested, and you love LabVIEW/TestStand, please send me your CV and resume via a private message.
  5. Change the string input to a number and update the case structure and you get the behavior you expect. Interesting that a string case structure with a range only checks the first character of the input. Try 1234 in your VI. I did not know this, been using LabVIEW for 20 years. Learn something new every day, thanks!
  6. Congratulations! Good luck on the next step!
  7. You have received some very good input. I do recommend designing the RT portion of the application to be as stand alone as possible. Losing network communication with the HMI will happen at some point and the RT application should be able to operate safely without any user interaction. It is important that your data communication method between the RT and HMI allow for re-connection without having to stop either application.
  8. Thank you for your replies. 1) We have decided to use MS SQL Server. 2) We have decided to use the generic TestStand database schema with the addition of one table. We want to store the report that TestStand generates in this table as a binary object. Does anyone have any experience doing this? We are leaning toward doing this with text reports but are wondering if the XML or HTML reports would work. 3) We have written a custom retrieval tool in LabVIEW. It queries the database for all tables and their relationships. The database schema can be modified (following a few assumptions) without having to modify the retrieval tool. The table names are displayed in a tree view. The user can select a table in the tree and retrieve the data from the table. The user can apply filters to the retrieved data. It is modeled after the View builder in MS SQL Management Studio. We still need to incorporate the ability to retrieve and display reports. Thanks again!
  9. Hi, I am curious how many TestStand users configure data logging to a database and if so: 1) What database do you use? 2) Do you use the generic TestStand database schema? 3) What tool(s) do you use to review the data once it is stored in the database? Thanks!
  • Create New...

Important Information

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