CRoebuck

OK,

you need to pass the class data out of the LabVIEW action step to a TestStand variable (of data type Object Reference) and then pass it as an input param to the next LabVIEW step that needs the class data however I am not sure if that is available to you using TestStand 4.2, not sure if TestStand 4.2 allows LabVIEW classes to be passed as an object ref.

Chris

Hi there Mirash

Firstly what version of TestStand are you working with ?

From what I remember ,there are a few issues with dynamic dispatch not working as it should from TestStand. You have to provide a wrapper around the vi's and let LabVIEW dynamically dispatch. If you try to do this from TestStand you end up always calling the parent method.

You also need to specifiy the LabVIEW class as part of the step settings else come deployment time the TestStand deployment utility see multiple vi's with the same name and throws an error. (It doesn't see the .lvclass part of the name)

Good luck

Chris

Hi,

That's what I thought, but when we asked to NI France on the feedback they had on the use of LVOOP with TestStand, they answered that nobody tried in France and asked the US R&D. We have no answer yet. We are worried of dealing with youth bugs. I'd like to start my new project this way, but the rest of team think the risk is too important.

bye

Hi there,

Me and my team have used LVOOP (Factory pattern) with TestStand very recently. It works but with a very big "BUT", You must use TestStand 2010 SP1 and must specify the LabVIEW project being used for each step configuration, if you wish to make naked calls to dynamically dispatch vi's in TestStand (passing in the LVOOP class from TestStand. If you use an older version the DD doesn't work and you end up always calling the parent implementation.

If you must use TestStand < 4.5 then you will need to put your dynamic dispatch vi's in a wrapper vi and let LabVIEW do the dispatch (I have no idea if the deployment works, TestStand probably see's lots of vi's with the same name and gives up.

Chris

Hi

I recently moved to the Mac platform and am looking for a low cost graphic design / image editing tool that I can use to create / edit images for a blog.

Anybody had any good (or bad) experiences that they would like to share ?

Chris

In additon to getting your hands on LabVIEW drivers (if available) or writing your own you're also going to need some way of interfacing to the equipment (JDS Uniphase stuff)

Typically this is going to be via one of the following methods;

USB

LAN

GPIB

In the case of GPIB then you're going to need a GPIB interface for your PC, National Instruments do an high speed USB-GPIB interface, see here; http://sine.ni.com/nips/cds/view/p/lang/en/nid/201586

USB and LAN are less costly interfaces but can be more complicated to chain if you have many instruments to control.

Chris

JKI is donating the following items:

A(nother) signed copy of LabVIEW For Everyone. We're not quite as connected as Fabiola--or at least we don't plan as well--so this one will be signed by Lisa Wells (1st ed) and Jim Kring (3rd ed) but not by Jeffrey Travis. Call this the "Second Place" LabVIEW for Everyone .

An AppleTV. Rent & buy movies and TV shows, share your own music & movies, watch Netflix titles instantly, and more!

Maybe some other stuff! If you don't buy your ticket, you'll never know!

Now THAT is cool. Can I just double and tripple check that you recieved payment for my ticket ?

Steen,

Looks like a really neat toolkit that scores highly in the "ease of use" stakes.

Going to give it a real test over the next few days and will feedback on my experience.

Hope you're well. Are you attending NI Week this year ?

Regards

Chris

Hey, I just bought one !

Having travelled from the UK to the CLA event in March I'm hooked and coming back in August for some more.............Bar-B-Q

Can't wait

Hey,

I thought I'd re-awaken this thread just to see how you guys are getting on with your Macbook Pro's ? I'm about to invest in a new laptop and am thinking of a MBP running OS X and WIn 7 (under BootCamp).

Just wonder how you early adopters were getting on. Any issues (I'm not doing any DAQ so only USB , and LAN control of Instruments). Probably going to run LabVIEW under Win and OS X

Thanks

Chris

Hi all

OK here's my problem. I worked on a LabVIEW code project for 3 years from version 1.0 thru version 15.3 (Started in LabVIEW 7.0 and is now 8.2). The project is an RX and TX Test for an RF module. The code uses many GPIB instruments (VISA) and some Serial (VISA) and also 2 IVI drivers (Arb and DMM) and also an external DAQ board that comes supplied with a "LabVIEW" driver (Actually VI wrapper around naked DLL calls but hey....it works). About 12 months ago I handed off the project another developer. Recently he came to me with this problem having made lots of changes....

Sometimes when launching the code WIndows displays a dialog stating that "MWU Test has encountered a problem an needs to close"......then the software closes. This is a windwos dialog not a LabVIEW message.

This can happen 5 or 6 times in a row but at different points during the test, sometimes after 1 minute sometimes after 3 minutes, sometimes never !

Once the test has run through once the site remains stable for weeks or months at a time with no repeat of the error. When installed on high spec PC's the problem seems to get worse.

IF the code is run using the LabVIEW IDE then the problem never occurs, only when using LVRT.

The last time I saw the error I captured the Windows error log which was as follows;

Anybody familiar with these error logs.....does it say what is causing my problem ?

<?xml version="1.0" encoding="UTF-16"?>

<DATABASE>

<EXE NAME="MWU Test.exe" FILTER="GRABMI_FILTER_PRIVACY">

<MATCHING_FILE NAME="MWU Test.exe" SIZE="7458816" CHECKSUM="0x372712AF" BIN_FILE_VERSION="16.2.0.0" BIN_PRODUCT_VERSION="16.2.0.0" PRODUCT_VERSION="16.2" COMPANY_NAME="Filtronic ICS" PRODUCT_NAME="MWU Test" FILE_VERSION="16.2" INTERNAL_NAME="MWU Test" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="16.2.0.0" UPTO_BIN_PRODUCT_VERSION="16.2.0.0" LINK_DATE="07/27/2006 10:04:02" UPTO_LINK_DATE="07/27/2006 10:04:02" VER_LANGUAGE="English (United States) [0x409]" />

<MATCHING_FILE NAME="data\lvanlys.dll" SIZE="892928" CHECKSUM="0x7B041BCE" BIN_FILE_VERSION="8.2.0.0" BIN_PRODUCT_VERSION="8.2.0.0" PRODUCT_VERSION="8, 2, 0, 0" FILE_DESCRIPTION="AAL for Win32" COMPANY_NAME="National Instruments" PRODUCT_NAME="LabVIEW" FILE_VERSION="8, 2, 0, 0" ORIGINAL_FILENAME="lvanlys.dll" INTERNAL_NAME="lvanlys.dll" LEGAL_COPYRIGHT="Copyright @ 2005" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="8.2.0.0" UPTO_BIN_PRODUCT_VERSION="8.2.0.0" LINK_DATE="07/12/2006 03:44:01" UPTO_LINK_DATE="07/12/2006 03:44:01" VER_LANGUAGE="English (United States) [0x409]" />

<MATCHING_FILE NAME="data\lvsound.dll" SIZE="24576" CHECKSUM="0xCC0527F4" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="11/22/2002 22:11:37" UPTO_LINK_DATE="11/22/2002 22:11:37" />

<MATCHING_FILE NAME="data\LVWUtil32.dll" SIZE="33280" CHECKSUM="0x4A7372B6" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="11/05/1998 17:14:06" UPTO_LINK_DATE="11/05/1998 17:14:06" />

<MATCHING_FILE NAME="data\lvzlib.dll" SIZE="55296" CHECKSUM="0x646D2CF9" BIN_FILE_VERSION="1.1.4.0" BIN_PRODUCT_VERSION="1.1.4.0" FILE_DESCRIPTION="zlib data compression library" PRODUCT_NAME="ZLib.DLL" FILE_VERSION="1.1.4.0" ORIGINAL_FILENAME="zlib.dll" INTERNAL_NAME="zlib" LEGAL_COPYRIGHT="© 1995-2002 Jean-loup Gailly & Mark Adler" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x1000E" UPTO_BIN_FILE_VERSION="1.1.4.0" UPTO_BIN_PRODUCT_VERSION="1.1.4.0" LINK_DATE="11/08/2002 19:49:34" UPTO_LINK_DATE="11/08/2002 19:49:34" VER_LANGUAGE="English (United States) [0x409]" />

<MATCHING_FILE NAME="data\tc0832.dll" SIZE="67584" CHECKSUM="0xE51DA08F" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="03/14/2035 01:15:49" UPTO_LINK_DATE="03/14/2035 01:15:49" />

<MATCHING_FILE NAME="PLL\lmx2330x.exe" SIZE="99154" CHECKSUM="0xCA65A81D" MODULE_TYPE="DOS" />

<MATCHING_FILE NAME="PLL\lmxload.exe" SIZE="15218" CHECKSUM="0xF701B28" />

</EXE>

<EXE NAME="lvrt.dll" FILTER="GRABMI_FILTER_THISFILEONLY">

<MATCHING_FILE NAME="lvrt.dll" SIZE="10406400" CHECKSUM="0x476318B9" BIN_FILE_VERSION="8.2.1.4002" BIN_PRODUCT_VERSION="8.2.1.4002" PRODUCT_VERSION="8.2.1" FILE_DESCRIPTION="LabVIEW 8.2.1 Run-Time Engine" COMPANY_NAME="National Instruments Corporation" PRODUCT_NAME="National Instruments LabVIEW Run-Time Engine" FILE_VERSION="8.2.1" ORIGINAL_FILENAME="lvrt.dll" INTERNAL_NAME="LVRT DLL" LEGAL_COPYRIGHT="Copyright © 2007 National Instruments Corporation" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="8.2.1.4002" UPTO_BIN_PRODUCT_VERSION="8.2.1.4002" LINK_DATE="02/21/2007 23:10:47" UPTO_LINK_DATE="02/21/2007 23:10:47" VER_LANGUAGE="English (United States) [0x409]" />

</EXE>

<EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY">

<MATCHING_FILE NAME="kernel32.dll" SIZE="984064" CHECKSUM="0xF12E1D4A" BIN_FILE_VERSION="5.1.2600.2945" BIN_PRODUCT_VERSION="5.1.2600.2945" PRODUCT_VERSION="5.1.2600.2945" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.1.2600.2945 (xpsp_sp2_gdr.060704-2349)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xF724D" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.2945" UPTO_BIN_PRODUCT_VERSION="5.1.2600.2945" LINK_DATE="07/05/2006 10:55:00" UPTO_LINK_DATE="07/05/2006 10:55:00" VER_LANGUAGE="English (United States) [0x409]" />

</EXE>

</DATABASE>

Cheers

Chris

QUOTE(crelf @ Apr 23 2007, 01:24 PM)

*sigh* to be back on the shores of Sunderland...

...and of course not forgetting the historic city of Durham and the railway town of Darlington.

Due to continued expansion we require an additional software engineer to join the software engineering team both to support and improve existing test software and to also take an active role in the development of new test applications and data mining tools. You will work closely with production and engineering to ensure projects are delivered on budget and on time. You will be resonsible for the following:

• Decisions taken regarding software applications
  
• Reporting progress/risks to project teams and Senior Software Engineer
  
• Identifying the correct resource and equipment required
  
• Review, identification and instigation of improvement activity within current applications
  
• Reviewing of customer test requirements and indentification of problem areas where test coverage is low
  
• Ensuring maxium availability of all test sites at all times through robustness of applications and identification of failure chains
  

You will be able to demonstrate:

• Proven experience in a scientific or high volume manufacturing environment
  
• Demonstrable strong LabVIEW skills with experience/understanding of TestStand knowledge and GPIB and RS232
  
• Ability to write SQL procedures for the retreival and analysis of data
  
• Experience of ODBC databases for the storage of parametric data
  
• Knowledge of networking in a Windows environment
  
• Natural problem solving capability combined with strong analytical skills.
  
• Strong innovative skills and experience
  

Education/quals

• Ideally LabVIEW certification combined with Scienfic degree in either Physics, Engineering, Mathematics or Computer Science
  

We offer an excellent salary and benefits package, with 25 days annual holiday entitlement in a modern manufacturing environment

For further details see www.Filtronic.Com where you can find further job details and info on how to apply.

......Or reply to this post with CV / Resume' and contact details.

Chris Roebuck

QUOTE(Jim Kring @ Mar 9 2007, 03:56 PM)

Yes, it's one of my (our) favorites. At JKI, we love to end a good meeting with some visionary discussions aided by some quality brew But, we try to do it after all the wire-working is done

May I also recommend Timothy Taylors "Landlord" Fine Pale Ale.

It's not so easy to find but well worth the effort.

Speaking of which, it's Friday, it's 4pm here and I can hear Timothy calling !

QUOTE(crelf @ Jan 24 2007, 02:21 PM)

Although not English (not that I'd admit it anyway due to the recent http://forums.lavag.org/index.php?showtopic=5122' target="_blank">English national catastrophe),

Everyone's a joker.

The wicket was biased in favour of the Ausie bowling style (ie. Striaght) :laugh:

Here's a question for the guys @ JKI

I was browsing your website today during lunch when I..ahem..stumbled accross the careers page (sssshh... don't tell my manager)

What do I see, on the table but North East Englands finest export......Newcastle Brown Ale. http://www.newcastlebrownale.co.uk

You guys are aware it's not a good idea Drink Newcy Brown and Wire at the same time?

Bottoms Up !

Chris

Can you hear her now?

Ok Ok Hat's off to your boys. They put on an impressive display, however everyone one knows that Football is Englands strongest sport

Welcome Chris! Oh, and commiserations on your imminent Ashes series loss...

Same thing happened to me at UTS - we had to complete 4 of 8 tasks (we got to choose which ones to do) and the 8th was a LabVIEW task. I asked the lecturer about it, and he said that it hadn't be written yet, and was just in there as a placeholder for the next semester - I asked if I could write a task and then complete it - and, you guessed it, he agreed. My task is now part of the ciriculum (or, at least, it was last time I looked...)

Hey, I haven't heard any fat lady yet !

Hi

I've been loitering around this forum and Info-LabvIEW for awhile now so I thought I'd better say hello and introduce myself. I'm Chris and I've been LabVIEWing for 8 years (Version 3.1 thru 8.20). I started using LV during an industrial placement year (Part of my Physics Degree) when I was presented with a choice, HP-VEE or LabVIEW. I was unsure (I know, I know) luckily I made the right choice.

Even though I've been using for years I only got round to certification a few months ago (Trying to smarten up the old resume)

My day job involves writing tests (in TestStand but using LV) for RF communications products up to 40Ghz. Throw in a bit of SQL and some I2C and loads of ActiveX and that's my typical day.

I hope I get a chance to contribute to LAVA very soon.

Regards from England

Chris

Anybody know how to unset the modification bitset. I have a vi that traverses a vi's heirachy and saves each vi for the previous version of LV. In this case I am reverting to 7.1 from 8.0.1 due to a serious bug found when using TestStand 3.5 and LabVIEW 8.0 RunTimeEngine. My vi runs fine but when I first open the newly reverted vi's using LV 7.1 the asterix is displayed and the vi thinks it's modified. I could just mass compile using 7.1 but I'm curious how to do it at the same time as the vi is reverted.

Thanks

Chris

Ok I now understand why it's doing this. Baiscally the diagram is created for the previous version but not re-compiled for the previous version.

D'oh !

When you open the VI reference, do you set the option mask 0x01? From the Help:

0x01 Record modifications. An asterisk (*) appears by the VI title to indicate that changes have been made using VI Server. The VI must be in edit mode for LabVIEW to record the modifications.

If the change you made is still not enough, you could simply rewrite the VI Description property or something like that.

Anybody know how to unset the modification bitset. I have a vi that traverses a vi's heirachy and saves each vi for the previous version of LV. In this case I am reverting to 7.1 from 8.0.1 due to a serious bug found when using TestStand 3.5 and LabVIEW 8.0 RunTimeEngine. My vi runs fine but when I first open the newly reverted vi's using LV 7.1 the asterix is displayed and the vi thinks it's modified. I could just mass compile using 7.1 but I'm curious how to do it at the same time as the vi is reverted.

Thanks

Chris

Hi all

I have some "scripting" code to programatically generate a series of vi's , I now want to place all of those created vi's in a certain order (I have an array of paths in the correct order) onto a new block diagram and wire them.

Any clue on how to get a sub vi onto the b d ?

:headbang:

Chris

Hi everyone

I wish to run LabVIEW 6.1 and 7.1 on the same machine, I also want to use TestStand 3.0 with my LabVIEW 7.1 vi's.

I want all my toolkits (Database, SDTK, Internet Developers) to be available to both versions of LabVIEW.

I have a clean machine and the CD's at the ready !

What order should I install things in to get what I want ?

I was thinking LV 6.1 >>> LV 7.1 >> Toolkits >> TestStand 3.0

Any better ideas or suggestions on how I can make this as painless as possible ?

Best Regard

Chris

Hi

Is it possible to customize the various palettes and Project windows in the LabVIEW 8.0 as was possible in the Beta ?

Regards

Chris

There were some screenshots of this layout on an earlier posting regarding LV 8.0

Hi all

I have a vi that returns the information about file modifications as timestamps , I then want to find the oldest (or newest) file from an array of timestamps. I have tried direct comparison without success and am now trying Seconds to Date/Time but with Timestamp data as the source. Anybody suggest an easier way before I start unbundling the timestamp cluster and comparing induvidual elements ?

Thanks

Chris

Has anyone played around with the "Diagram Disable Structure"?  You can create this struct using the New VI Object primitive.  Create it in a target vi (vi cannot be running to create), then copy it to your application.  You can 'comment out' code, or add several flavours of a code snippet, and disable all but one version of it.  Is this the same as the 'conditional disable struct' in the sense that it is only supported on the PDA version?

2349[/snapback]

James

I am having difficulty creating this structure in a target vi , could you just run through the correct steps again. On my installation the target vi crashes the editor when opened !

Regards

Chris