Lecroy 9310 downconvert LV2009 to LV8.2

Hello all,
I would like to downconvert a Lecroy 9310 oscilloscope driver from the LV2009 version to LV8.2 (link to driver page: http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=E3B19B3E9608659CE034080020E748... I am also wondering if this driver works for an "old" Lecroy 9310, as the driver description mentions a digital oscilloscope, when mine has a cathodic screen.
ETA: direct link seems broken, here is the link to the driver page (I need the Labview driver, not the LabWindows): http://sine.ni.com/apps/utf8/niid_web_display.model_page?p_model_id=12187
Solved!
Go to Solution.
Attachments:
lc930x1x.zip ‏1299 KB

Thanks for this quick answer !
I can open the driver VI, but unfortunately all the subVIs are missing, I suspect they where missing from the original driver (LV2009) too (I'm especially interested in the "LCDSO Read Single Wave").
I don't know if these subVIs are standard components in LV2009. The surprising thing is that looking at the front panel design, this driver seems quite old (before LV8.2 anyway) and would then have been upgraded only by compilation with newer Labviews. It should then be self-sufficient in LV 8.2 ?
I tried to find these subVIs online, but they are only referred to in old forums posts pointing towards unavailiable NI driver download pages (I guess the old drivers are replaced by the new).
Do you know where to find these subVIs ?

Similar Messages

VI Conversion from LV5 -- LV2009 (or LV8.5)

Hello,
could someone please convert the VI so that I can open it with LV 2009 (of LV8.5)?
Thank you very much!
Solved!
Go to Solution.
Attachments:
MonoMove.vi ‏65 KB

All of the subVIs are missing. Without them the VI is pretty useless. The subVIs are from some library called "hr630".
You should post this in the Upconvert VI Requests thread.

Downconvert firls from LV8.6 to LV7.1

Hi everyone,
can someone please convert the function FIRLS (Labview version 8.6 (found on this site)) down to LabView version 7.1?
I know, there is a solution using the MathScript but I hope there's a way without an Matlab installation.
Greetings
Thank you!
Attachments:
lms_adaptive_filt_lab_code.zip ‏206 KB

Thank you very much for your prompt answer.
I knew that there must be a difference between "MathScript" and "Matlab Script".
But since I can`t find MathScript in my LabView 7.1 it might not be installed in this version.
I think I still need the conversion.
Greetings from cold Germany (-19°C)
Bon

Save for previous error on FPGA vi (LV2009 - LV8.6)

Hi all,
I have an RT project i want to back save from LV2009 to LV8.6. When trying to save for previous, all FPGA subVI's are saved correctly but the top level FPGA vi returns error 1536:
LabVIEW: To save a password-protected VI for a previous LabVIEW version, you must enter the password.
However, no VI is password protected :-s
All other top level VI's in the project referencing the FPGA VI also return this error.
I searched this forum but found no similar topic, so maybe i'm missing something
Can someone please help?

I am getting the same error. LV 2009 on Windows Vista. There are only 4 VIs (FPGA Main, FPGA subVI, Host Main, Host SubVI) and a Shared Variable Library file. The SV library file and on the FPGA subVI get copied into the new directory along with the LVbit file but nothing else. I am not even sure what VI is having trouble on.
Joji

Report Generation Toolkit V9.0.0 : Print Report.vi doesnt print

Hi,
i have migrated my Labview 8.5 Project with Report Generation Toolkit V1.1.2 to a Labview 2009 System with Report Generation Toolkit V9.0.0.
In this Project I use the Report Generation Toolkit for printing out a Standard Report with e few Tables and Graphs.
Now the VI Print Report.vi delivers the Error -41002 with the Text "Invalide Printer Name". I have, of course installed the propper Printer on the machine.
I don´t connect a string to the "Printer name" input of the VI, because i want to use the default printer.
In my oppinion, there´s a bug in the Print Report.vi: if you don´t wire the "Printer name" input, the vi should use the default printer, but in this case the vi connects the empty input string to the input of the method node it calls.
I fixed this bug, but the method node still returns the same error.
any ideas?
Thanks!
Solved!
Go to Solution.

Thank you for the link!
For some reasons i can´t find this specific article in the knowledge base (my browser is always rerouted to the german version of ni.com, because i am in Austria). I tried to search with the exact title of this article, and the error message string, but no results...
I have also installed Labview 8.5 and the "old" Toolkits on my new computer in addition to Labview 2009 and the "new" Toolkits and tested my program in 8.5. Here i got an error mentioning the margins and i had to change the margin settings for printing out, then in worked.
After reading the article, i have applied the same changes for the margins in the 2009-version of my program and it works too!
Problem solved!
Thank you very much!
PS:
I first wrote, that there´s maybe a bug in the new version of the Print Report.vi, but i´ve compared it with the old version and it seems to be no bug, sorry!
After all I decided to stay with Labview 8.5 for now, because of another problem:
it´s not possible to "save for previous version" from LV2009 to LV8.5 directly.
Laview crashes, when a VI contains an event structure as i found out by searching through the "known issues", and i have a lot of VIs with event structures!
I have to have the possibility to save my Labview projects for 8.0 and 8.5. The only way is to save for 8.6 and then save from 8.6 to 8.5.
That´s nasty and time-consuming!
Maybe a future update will solve this problem (without producing new ones)

Error saving for previous version 2009 to 8.5

I have a project with a VI containing DAQmx Data Acquisition VIs, timed loops and other standard conrols and indicators. When trying to save for previous version (from LV2009 to LV8.5) an error occurs. All of the dependencies can be saved to previous versions but the main VI cannot. Can anyone help with this problem?
The error message can be seen in the image attached.
Attachments:
error.JPG ‏18 KB

Backsaving creates a folder structure with the backsaved VI and all support files in their relative locations. This might be useful in most cases.
Very often I just need a single VI (without SubVIs) backsaved. I do this programmatically using VI server (open VI reference, then call the "Save For Previous" method, then close the reference). See image below.
To do this for a project you could of course use a recursive file list and go through the whole list (programmatically), saving the VIs in a parallel folder structure (create destination folder before saving the VI).

Start stop event structure queue

Hello,
I would like for the attached vi to start logging/displaying data when the Start button is pushed, not when the VI starts. So I did some research and was led to the Event Structure (this is my 1st time using an event structure). I have been trying all sorts of things over the last few hours so what I have now is probably somewhat convoluted, however, my latest error is that my dequeue is receiving an "invalid refnum".
Could someone guide me on what I am doing wrong?
Thanks.
Solved!
Go to Solution.
Attachments:
InitFile.vi ‏20 KB
CNAP Daq Event Structure.vi ‏109 KB

Hi Nouse,
I had some free time and was bored so took a look at your vi for you. You was on the right track, had started with a good architecture which is half the battle, just needed some fine tuning:
I took your code and added it to this. All that i have taken out is the Sub vi's that get your data, i replaced this with a random number just to see some data on the wavechart and also being logged in your file. A point to notice is that your 'CNAP INIT FILE' vi has no error cluster propogation. If you run this subvi and there isnt the 'C:CNAP\' Directory (As there wasnt on my computer at first) the 'OPEN File' vi errors and halts the program, as you have no error propogation or handling in this vi you cannot handle this error.
I changed the vi slightly and added a 'Start' 'Stop' and 'Exit'. This allows you to start acquiring/logging data, stop (without exiting the program), restart acquiring/logging or exiting the program. A point to note is that if you do 'Stop' and then 'Start' again, relatively quickly your 'CNAP INIT FILE' Vi will append a previously written file, which is fine, but it will also send out a new start time. So your readings in the same file will start from 0 time. You may want to catch this and not update the new start time if appending an old file.
I have attached the VI in both LV2009 and LV8.6 as you never stated your version.
Hope this helps,
Rgs,
Lucither
Message Edited by Lucither on 03-27-2010 03:32 AM
"Everything should be made as simple as possible but no simpler"
Attachments:
Data Logger VI 2009 and 86.zip ‏229 KB

Warnings when I downconvert from LV8.6 to LV8.0

I tried to downconvert some VIs from LV8.6 to LV8.0.
For this VI, after "save to previous version", I received those messages:
    The object "Multiply" does not support output configuration in the previous version.
    The object "Multiply" does not support output configuration in the previous version.
    The object "Subtract" does not support output configuration in the previous version.
    The object "Add" does not support output configuration in the previous version.
    The object "Multiply" does not support output configuration in the previous version.
    The object "Divide" does not support output configuration in the previous version.
    The object "Subtract" does not support output configuration in the previous version.
    The object "Divide" does not support output configuration in the previous version.
    The object "Divide" does not support output configuration in the previous version.
I don't have with me LV8.0 and I want to know how to manage those warnings.
Jean-Marc
LV2009 and LV2013
Free PDF Report with iTextSharp

No, these warning can be safely ignored unless you have manually configured the output type of these functions to be different from the default (which is "adapt to type"). Even then, it is probably not a big deal and you could insert an conversion bullet if needed.
In newer LabVIEW versions you can define the output type via the properties dialog (right-click...properties...output configuration). For example you could define that the multiplication between two DBL would result in a I32 output. If you do this, the output terminal will get a blue dot.
In a better world, these warning should only occur for nodes where you have actually configured the output. Currently, they seem to appear always and for no good reason other than confuse the newcomer. They simply alert you that the downconverted function has slightly less functionality. This is irreleveant if you did not use the functionality in the new version.
(See also)
LabVIEW Champion . Do more with less code and in less time .

IMAQdx datatypes in LV8.2 & LV2009

I've been converting a project containing IMAQdx functionality from LV8.2 to LV2009 and run up against a problem. I've narrowed it down to the registering a Frame Done event using the IMAQdx Session, and then trying to access the dynamic variables in that event.
This is the code in LV8.2:
(I know it won't actually run, but notice that the CtlRef indicator, whilst being coerced, is actually accessible)
Exactly the same bit of code in LV2009 gives a broken wire error, as follows:
The error on the wire is "You have connected two terminals of different types. The type of the source is User Defined Refnum Tag. The type of the sink is typedef 'IMAQdx.ctl' IMAQdx (IMAQdx, IMAQdx)."
Poking around a little, I have tried wiring a Property Node to the CtlRef event node, but I can't work out which property to use to get the camera reference. Any ideas? Is this the right way to fix this problem? Or is there something else I've not spotted?
I've attached the VI for ease of checking (LV8.2).
Thanks for any help!
Solved!
Go to Solution.
Attachments:
Test_IMAQ.vi ‏8 KB

I see the same behaviour, let me check what's going on here.
But you could do it also as follows:

Downconvert from LV10 to LV2009

Can somebody please downconvert the LabView file "SMP_read_PNT.vi" from version LV10 to LV 2009 ?
Thanks, Matthias
Solved!
Go to Solution.
Attachments:
SMP_read_PNT.vi ‏24 KB

LV2009
Attachments:
SMP_read_PNTLV9.vi ‏18 KB

Convert LV2010 vi file to LV8.5 or LV2009

Kindly convert this vi to V2009.
Thanks,
Mathan
Solved!
Go to Solution.
Attachments:
GetUID.vi ‏31 KB

Here you go
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
Attachments:
GetUID.vi ‏24 KB

Open a different vi than the startup vi from a build application in LV2009

When building an application (exe file), I have to select a vi as "statup vi" in the build specification. This vi opens its front panel and executes when I execute the application.
But I can still open the front panel of other vis by using a command line argument:
myapp.exe "myvi.vi
The startup vi still opens and runs, and the vi "myvi.vi" opens its front panel as well. That was before LV2009.
Since I upgraded from LV8.5 to LV2009, my shortcuts do not seem to work anymore. I also tried using a longer path with the new LV2009 exe structure:
myapp.exe "subdirectory\myvi.vi" since the vi is in a subdirectory. It does not work either.
1-How can I open a vi when launching a build application, like it was possible before LV2009
2-How can I (Why can I not) use the File/Open... menu item of a front panel window to open a vi that resides in side the build executable?
Thanks for any help.

Thanks Norbert for (incredibly) fast reply.
Well: in the advanced page of the build specification, we still see
the option "pass all command line arguments to application". If
disabled, only the arguments after "--" (two hyphen) are passed to the application
itself (according to the help for this dialog window). So I assume that the arguments before the two hyphens are interpreted by the runtime engine. In previous versions of LV putting a vi path (inside or outside of the exe) would open its front panel - even though doing a quick search I could not find documentation about this feature...
Is there any documentation about which arguments are
accepted by the runtime engine when the mentioned option is disabled?
Can we not give a vi that should open (anymore)?
Baptiste

How to install an older instrument driver (GPIB) LV2009 eval, 23 days remaining!

Hi..
Still having fun (I think) here trying to "evaluate" LV2009.
I'm sort of happy with the higher level stuff, front pannels, block diagrams, flow control with error signaling etc, so now time to move on and try to talk with the real world.   The Front Panel development UI is a bit of a dog, but I'll live with that.
Anyway...
I have a Marconi 6960 RF power meter (and similar kit) I can use for this "evaluation" and have found a so called driver in the NI developer zone some(i forget)where. It's a zipfile (no problem) with 4 files in. .c .h .fp and .doc    Sadly, the .doc though documents the functions of the driver, gives me no clue as to how to install it in LV2009. It also talks about LabWINDOWS V2.0, and dates from 1997.
(As an asside, most of what I will have to do, will relate to "older" or "Legacy" GPIB or RS232 connected instrumentation, and maybe one or two USB toys. There is no choice, LV is expensive enough if we go this route. But it's not even peanuts compared to the value of some of the instrumentation it will need to work with.)
Looking arround this board, I'm not realy any the wiser as to what to do with it. (This downloaded "driver" code.) It obviously needs compiling, but with what, and then integrating in LV2009, but how?
I found a link in one sort of related message, something about a driver import wizard, but the link is blocked by some spotty IT type this end, so that is of no help.
The inbuilt help from within LV2009 is sufficiently vague, or over complicated as to be of little use too.
What I need, is a simple, put that there, do this, do that type of procedure.
Again, stumped by simple details, and this is the area I will probably be spending most of my LV life in, from what's being muttered about "upstairs" in the big boss's office earlier.
Any help appreciated.
Regards.
DJB.
Just been "diverted" onto a hardware repair job, so no hurry, for now.
OK... Who let the smoke out?

Hi Dennis.
Yes, I found that page (and many others) but the info there is sufficiently vague, or so OTT for someone who does not know their way arround the darker recesses of LV (yet) to figure out.   It tells me a lot, but it does not tell me in sufficient detail *exactly* how to install a driver that someone else has created, or for that matter, how to find out what "Drivers" are installed already.
As you or someone pointed out, that code was also written way back for another system "LabWINDOWS/CVI" (whatever that was) but it shows up when you search for "Drivers for LabVIEW". It is also listed as supported by LV7.0 and LV8.0.   Those IDN pages also do not yet (that I can see) make any mention of LV2009. Is it just me that sees this as somewhat inconsitant and confusing for a new user, when NI are pushing LV2009 at this time?
Someone is now going to tell me that reusing existing older drivers *is* straightforward, but will be vague as to exactly how.
The only "exposure" to LV we've had here in the past/present, is as users of pre-compiled tools and utilities from some of our principles. And it has to be said, all of them are without exception, extreemly buggy, so much so, I personally wouldnt say they were fit for even internal Beta testing, as they don't handle "unexpected events" at all well. And some of these utilities could if they screw up, seriously damage hardware in some instances.
We've also found many many times, that anything using "VISA" IO drivers (that word again) is almost garanteed to be troublesome to get or keep working, especialy as one lab/workshop PC might have tools and programs from several vendors on it, and they must all work indipendantly when needed (not at the same time!) without interference from other vendors code or preferences. For some reason, VISA seems to make that all but imposible.
We have a situation at the moment, where we suspect a "Clash of the VISA's" as we can't reproduce what a customer has reported in the way of bad behaviour of a semi automated test system, but we see other errors relating to the serial IO used, throwing up internal LV runtime error messages, and blank spaces where the *Real meaningfull* comments should be. It's all pre-compiled code, so we have no way of supporting or debugging it, but try tell the end user that, who's test facility is now at a standstill, untill I can call the East coast USA later today (from the UK) not that I expect a constructive reply till sometime tomorrow, at best. By then, there'll be Director to Director phone call's going on!
I've also just been informed, that the workshop PC in question, will not now run something else we need, since we earlier installed the program the user is using (made by the instrument vendor) and all it's baggage, so yet another "Fixit" re-install of VISA (this time from Agilent) is needed to complete another job, and that in turn will break something else. It's a nightmare!
Sorry, but in my book, VISA is a no go for "Serious" multi vendor use. It's too fragile. In our industry (EMC and product safety testing) "Legacy" GPIB rules, almost without oposition. USB and LAN connections may be alternatives where the instrument supports them. With some true RS232 point to point low speed dedicated links where needed (often via passively powered fibre optic convertors too) for some measuring instruments.
But, at this time, all I want to do, is talk/control a simple existing GPIB instrument (a MI 6960, that I know all too well) and I thought (wrongly as it turns out) that I had found a needed "Driver".   If I have to create one from new, I will, one way or another.   But it makes a mockery of the so often quoted aspect of LabVIEW, being quick to construct and deploy a test/trial/control system etc, with an existing vast library of tried and tested instrument/device drivers. From what I see so far, it's anything but, as it's in the same ball park as all the other RAD IDE's etc (Even Delphi!) in that respect. The devil is in the detail, and if that detail as often does not exist, it's a task and a half to create it, and get it right.
Sorry if I ruffle any feathers, but I've been arround RF test & instrumentation systems at the hardware and software level for more years (decades) than I care to admit. Each and every time someone comes up with a "better" way to do something (usualy involving even more computing power!) It's anything but quick and easy, and the end result is in all honesty, not realy different to how it was done, before "enforced newness" was applied.
Regards to All, I've still got the day job to do, so sadly I can't sit in front of this and mess with software all day. Much as I need to, and often would preffer to!
DJB.
OK... Who let the smoke out?

Downconvert from labview 9.0 to labview 8.5

Hi everybody,
Please help me to downconvert the attached file from LV9.0 to LV8.5 (or LV8.0)
Thank you for your help in advance!
Attachments:
PVCAM take3.zip ‏1501 KB
pl exp setup cont.vi ‏16 KB

You might have to do some relinking, but they have been saved in 8.5.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
Attachments:
PVCAM.zip ‏1899 KB

LV2009: opening and extensively editing a v8.6 VI, saving, then error code 3

My question is about this known "Error code 3" bug that surfaces when trying to load a vi originally created in LV8.6 then saved and reloaded in LV2009. There is a suggested workaround but it doesnt seem to help me.
Using LV2009 I have extensively modified a vi that was created in LV8.6 - I saved it - and now I am trying to reload it but I am faced with Error code 3. Is there any way at all I can somehow open up the wire diagram at least?
Thanks,
TZ

It is really offended..
I get the same error message, and cannot open it.
Sounds like ... euh... not so good news I'm trying to put it mildly..
See error message below:
Message Edited by Ray.R on 10-08-2009 06:23 PM
Attachments:
badNews.PNG ‏7 KB

Lecroy 9310 downconvert LV2009 to LV8.2

Similar Messages

Maybe you are looking for