Jump to content

JCAndersen

Members
  • Posts

    4
  • Joined

  • Last visited

About JCAndersen

  • Birthday 01/06/1974

Profile Information

  • Gender
    Male
  • Location
    Denmark

LabVIEW Information

  • Version
    LabVIEW 2020
  • Since
    1998

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

JCAndersen's Achievements

Newbie

Newbie (1/14)

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

Recent Badges

3

Reputation

  1. Thank you dadreamer. You were right. It was that old version you mentioned. Out customer actually found the installer on an old network drive. I was for LabVIEW 6.0, and I have at all running now 🙂
  2. Hi. I have received some code from a customer which is created with LabVIEW 8.2.1. It uses an old add-on tool for accessing an SQL database, but I cannot find that tool anywhere. I can see that the VI's I have are trying to load sub VI's from "<vi.lib>:\addons\SQL\Access" and then a number of different llb files. Can anyone her point me in the direction of which tool kit this comes from? Is it a very old version of the Database Connectivity tool kit or is it something else? Thanks.
  3. Yes, there is many things wrong with this. What about the new adapter icons. What is the point of moving away from the well known product logos and just use the first letter of product name instead? It makes no sense.
  4. I attended my first TestStand course in 2004 and have been working with TestStand on a regular basis since 2008. To me it seems that every one who has replied to this thread until now is making the most common miss assumption about TestStand: "TestStand is a test sequencer". Of cause you are right about that, but it is so much more. With TestStand you get a toolbox for creating your own test management frame work. This means that you as a test developer need to spend some time getting to know you toolbox, just like you had to learn how to program in LabVIEW at some point. An yes, TestStand is a complex toolbox to get your head around. That is the trade off for the flexibility you get. In the posts here I have not seen one challenge that I could not implement and make work in TestStand, just as easy or easier that in a custom LabVIEW sequencer. And when you are on the track with TestStand, you will realize all benefits like batch executions, reporting and property loading. Of cause you can implement and maintain all of this your self, but they are handed to you with TestStand and NI will maintain the fundamental function for you. However I do agree with Chris_Collier that it would be nice if NI provided a course on how to make high level architectures with TestStand. So I guess my point is this: Do not just buy a TestStand license and start using it out of the box as a simple test sequencer. You need to be clear about your goals for the test system, learn how to use TestStand and then learn how to implement you test system with TestStand.
×
×
  • Create New...

Important Information

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