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

Similar Messages

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 .

Convert from LV8.6 to LV8.5

Hi,
Would someone please convert this project from LV8.6 to LV8.5 as I only have version 8.5?
Thanks
Tom
Attachments:
Project.zip ‏758 KB

Hi Teeeeg,
Here you are. Let me know if this works.
Thanks,
Owen.S
Applications Engineer
National Instruments
Attachments:
Gear_Inspection_Software Folder8.5.zip ‏1384 KB

Error reports converting a vi from LV8 to LV7.1

Neatly working VI in LV8.0 for some reason I am converting it into earlier version of LV7.1. When I opened from LV7.1, I got the error message (report attached).
Hope somebody help me out to avoid coding from scratch.
Kousy

NO Blk diag_LV8.vi - this has no block diagram but i could not find any problem saving it into earlier version 7.1
Perf Print Report.vi - this is the vi i have not able to save it into 7.1 version. Even I have tried removing all the graphs I have used + printing options etc. still it is throwing out the same error msg.
Kousy
Attachments:
NO Blk diag_LV8.vi ‏13 KB
Perf Print Report.vi ‏520 KB

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 ?

Error when generating report in exe built from LV8.6

Hi all,
Using LV8.6 and report generation toolkit 1.1.3 i have one application in that i am generating report in 'word' and 'exel'. I have built that application as a EXE. in that exe i am unable to generate report. i am getting following error:
Possible reason(s):
LabVIEW: File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on Linux. Verify that the path is correct using the command prompt or file explorer.
=========================
NI-488: Nonexistent GPIB interface.
Complete call chain:
Get LV Class Default Value.vi
NI_report.lvclass:New Report.vi
Conditionally Formatted Word Table.vi
r.vi
Regards,
Santhosh M

yes i have includeed all the class and dependents but still it is giving problem i will send my code pls build the exe and run it, thentel about that...
Regards,
Santhosh M
Attachments:
Test.zip ‏11 KB

Error 1050, when calling MATLAB 7.1 from LV8.0 - Function Definitions not allowed.

I am trying to call a MATLAB M-file from LabVIEW 8.0. I keep getting Error Code 1050:
"Error 1050 occurred at LabVIEW: Error occurred while executing script. Error message from server: ??? Error: Function definitions are not permitted at the prompt or in scripts.
. in rickfito.vi->impedo.vi
Possible reason(s):
LabVIEW: Error occurred while executing script"
I tried running the sample MATLAB script example on the knowledge base, and everything works fine.
I am guessing that this error is happening because I have functions defined in the MATLAB script. But i thought this is better programming techinque. Also, the MATLAB window opens up when I start the VI.
Is there a way around this? I really do not want to remove the function definitions on the script.
Thx,
Pelo...

First, see if the Matlab Script Node is trying to open any files. If
so, then make sure that the current Matlab directory is set to the
directory where that file is located. The Matlab script node in LabVIEW
does call the Matlab script server and executes the function in the
Matlab script node through Matlab. Therefore, even though LabVIEW may
be in the correct directory where the file is located, make sure Matlab
is as well.
The error may also occur if there is a disruption
in the script server between MATLAB and LabVIEW and the connection was
never re-established (possibly by closing MATLAB prematurely). Close
both LabVIEW and MATLAB then relaunch them both and run the VI.
MATLAB®
is a registered trademark of The MathWorks, Inc. Other product and
company names listed are trademarks and trade names of their respective
companies.
-Bob
-Bob

Downconvert file from version 10 to 8.2

Kindly downconvert attached file to Labview 8.2 version.
Thanks in advance.
Solved!
Go to Solution.
Attachments:
t1.vi ‏43 KB

LV 8.2
Attachments:
t1LV82.vi ‏46 KB

Recompiled from LV6.1 to LV7.0, now I can't configure CIN

I have a VI using a CIN that works in LV 6.1 and in LV7.0 (no CIN load errors). BUT, I can't configure the CIN in LV7.0, even after reloading the .lsb file. All the inputs are unnamed as well (the pop-up says simply 'input'). But the vi still works. I have all the source code for the .lsb files.
Any ideas what's happening here?
Thanks.

vituning wrote:
> I have a VI using a CIN that works in LV 6.1 and in LV7.0 (no CIN load
> errors). BUT, I can't configure the CIN in LV7.0, even after reloading
> the .lsb file. All the inputs are unnamed as well (the pop-up says
> simply 'input'). But the vi still works. I have all the source code
> for the .lsb files.
What sort of configuration would you want to do on a CIN node? Are you
sure you don't confuse this with the Call Library Node?
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

From Lv9.0 to Lv7.1

Anyone can help to converse the files from Lv9.0 to 7.1? Thank a lot
Solved!
Go to Solution.
Attachments:
lv9.vi ‏14 KB
lv9_1.vi ‏15 KB

attached
Attachments:
lv9.vi ‏48 KB
lv9_1.vi ‏62 KB

Upgrading from LV6.1 to LV7.1 crashes w/r nipalk.sys

I am using a PXI-1010 chassis with a PXI-8175 controller. This controller had WIN 2000 and LabVIEW 6.1 installed with no problems. I also had no problems installing the LabVIEW 7.1 full developement system until I tried to installed the 101 modules from the full Device Driver Reference CD. When system now continously reboots with a dialog message box stating "\SystemRoot\System32\DRIVERS\nipalk.sys device driver could not be loaded Error Status 0xc000012f". How do I fix this problem?

Hello Jimmy,
System crashes such as the one you are experiencing are usually caused due to driver layer software. You said that the system continuously reboots. Does this mean that you are unable to do anything with the computer, or does it reboot after you perform some action?
What I recommend is making sure that you have all of the latest drivers installed on your machine by looking for the latest driver versions at Drivers and Updates. The problem could be something as simple as a driver layer incompatibility.
If the problem continues to persist evern after verifying the latest version of the drivers, post back to the thread with some further information. In particular, helpful information to troubleshoot such issues include driver versions, particularlly NI-PAL, detailed computer specifications, all hardware involved, how the problem is replicated, detailed error description, and a dump from the crash if possible.
Best of luck.
Jared A

How I export from HDV to SD (DVD)... What about HD versions suitable for Macs and Pcs?

Hi,
      I have just finished editing a short movie based on some high res stills combined with some 1080i HDV footage.
   After completing the edit in CS4 (in a HDV 1080i environment) I went through Adobe Media Encoder in order to downsize and converting into an m2v file ready for my Encore project.
   As you probably well know this is far from satisfactory in terms of the down sampling capabities shown by AME as well as the lack of proper colour conversion.
So, after giving up on the Dan Isaacs method, AVI synth didnt seem friendly to this user... as well as the inability of CS4 to frameserve..
My solution was to exported the Microsoft AVI using the HUFFYUV codec at 100% - With Progressive scan, when ever I interlaced my output it showed obvious interlacing in my player, odd or even fields first...
I then used VirtualDub to do the down sizing
Finally Procoder 3 to convert to m2v.
The results still have no proper colour conversion properties but look much sharper than the regular CS4 encode using AME
   OK, that took an eternity to discover and still leaves me with another problem.
I want to export straight from CS4 to media type that can be played on both PC and Macs in HD.
Before I go down another gruop of dead ends and trial and error discoveries, could anyone here suggest a recomended and successful workflow?
   Many thanks,
Phil.

let me see if I can help out a little here.
The problem with converting 1080i to SD in software is that FCP seems to do a not-very-good job of downsampling the image, particularly when you are going directly to DV. Details get blurry, and other compression artifacts become quite noticeable. I have also experienced trouble with the HDV fields not getting processed correctly if I go to SD mpeg directly from an HDV timeline or movie file.
Your best bet is one of the following workflows:
Export a 1080i HDV or AIC movie file and re-import to FCP. Place this clip into an anamorphic SD sequence. It doesn't matter if the sequence is DV or Uncompressed if you send the sequence directly to Compressor from FCP, because this will ignore any rendered material and use an uncompressed image buffer as it encodes the mpeg. Do not letterbox your widescreen video if you are going to DVD - widescreen DVD video should always be full-frame anamorphic.
Your other option is to attempt to use Compressor to down-res the sequence or a self-contained movie of your HDV, starting with one of the advnace format conversion presets in Compressor. However, you'll have to cutstomize the preset by turning on the frame controls, and testing the settings to make sure you are happy with the result. Turning on frame controls will increase the ratio of your encoding time anywhere from 4 to 20:1.
I have tried all of these methods, and none of them look as good as capturing the downconverted video from the deck after mastering to HDV tape.
Hope this helps -
Max Average

Creating Builds Programmatically LV8.0.1

Salut.
From LV8.0.1 help :
QUOTE
Creating Builds Programmatically
You can use the BuildTargetBuildSpecification VI located in the vi.lib\AppBuilder directory to build source distributions programmatically from build specifications. If you have the Application Builder installed, you can use the VI to build stand-alone applications, shared libraries, Windows installers, and zip files programmatically. The VI is not available on the Functions palette.
Note The LabVIEW Professional Development System includes the Application Builder. If you use the LabVIEW Base Package or Full Development System, you can purchase the Application Builder separately by visiting the National Instruments Web site.
The BuildTargetBuildSpecification VI creates a build from a build specification that you specify in the Name of build specification input. If you do not specify a build specification, the VI creates builds from all build specifications in the specified LabVIEW project. You must specify the path and filename of the project to use in the Path to project input.
If you want the VI to create a build from a build specification located in a target that is not My Computer, specify a target in the Name of target input.
After you run the VI, you can view the path to the completed build files in the Generated files output.
END QUOTE
1-
QUOTE After you run the VI, you can view the path to the completed build files in the Generated files output.END QUOTE
Does someone know how to also get the created installer files? (i only get the exe output files)
2- How can i start the build status feedback window when using the BuildTargetBuildSpecification.vi?

Hi jacemdom,
I hope you're doing well. I have tested building an Installer specification on my end, and I am seeing the same results. The correctly passes in the appropriate build specification reference, but no files are actually generated as you have noticed. I am currently looking for more documentation for you on the BuildTargetBuildSpecification as it is a relatively new feature. Regarding the status window with this VI, it looks like that feature is currently unsupported. I will verify this an update you with what I find. Have a great day!
Thaison V
Applications Engineer
National Instruments

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:

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

Downconvert firls from LV8.6 to LV7.1

Similar Messages

Maybe you are looking for