VLC and LabView 2009

I am trying to use the latest ActiveX VLC v1.1.4 in LabView, and every time I insert the VLC ActiveX Object, LabView crashes. I've read other posts which noted success by either: 1) using a web browser ActiveX object calling VLC or 2) finding a unique older version of VLC which doesn't cause their particular version of LabView to crash.
I have yet to find a version of VLC which works with LabView 2009, and I'd prefer not to call a web browser ActiveX component just to play a video with VLC.
Has anyone had success integrating a VLC ActiveX object in LabView 2009?
Thanks,
Stephen McClanahan

just try the attached vi. Maybe this is what you are looking for.
attached is 2010 and lv86 version.
If you don't have Wait Until Next ms Multiple__ogtk.vi look in the archive or download openg libraries.
cosmin
Attachments:
vlc.vi ‏13 KB
vlc ver86.zip ‏17 KB

Similar Messages

Remote Panels and LabVIEW 2009

Hello,
I have updated my real-time PXI application to LabVIEW 2009 (Pro) and I'm now trying to connect to it with remote planels. I can only have one remote panel opened. The second one gives me the "Remote Panels connection exceeds maximum numbers of licences" The problem wasn't occuring in LabVIEW 8.5 and I have the remote panel license (unlimited) is actived in the license manager.
How this can be resolved?
Regards,
Patrick
Solved!
Go to Solution.

Have you transfered the license files to the controller since the switch to 2009? There should be a .lic file under ni-rt>>system>>shared>>licenses on the controller. Is that present on your system?
Justin Parker
National Instruments
Product Support Engineer

FTDI virtual com port driver (VCP) and Labview 2009 - random connection loss

Hi,
I am using an FTDI chip to go from USB to serial communication (FTDI Driver: 2.06.00). It seems to work at first but then after some time the connection gets lost ("connection for the given session has been lost" or "I/O error"). This happens in MAX as well as the built executable of the program I am running. Latest VISA drivers are installed - 4.6. I have tried flushing the buffer before and after communication with both visa clear and visa buffer flush vis. The lost connection seems to happen randomly.
I have seen other threads about this issue but they never reach a resolution. One thing i notice is that there are two FTDI devices in this system and only one fails, however when I unplug the working device the one that fails is able to connect again.
To sum up here are the system specs:
Windows XP SP3
FTDI 2.06.00 and older 2.04.02 drivers both fail.
2 FTDI devices on the system - they do get assigned different COM ports
Labview 2009 run-time
VISA 4.6 run-time
Thanks for any help.

We use Targus ACH63US Super Mini USB 2.0 4-Port Hub. It doesn't require external power but if you have a high power device you will have to plug the Targus hub into two usb ports on your pc (one provides power and the other does power and data transfer). They provide the usb Y cable to do this.

Differences between LabVIEW Education Edition and LabVIEW 2009 + NXT Module

Recently saw the announcement regarding LabVIEW Education Edition.
From the information available at this time it's hard to tell the difference between this product and just adding the NXT module to standard LabVIEW 2009 if your only interest in LabVIEW is for NXT programming. Anymore details about this new product would be appreciated as well as info on how it's different from the alternative. Are there some unique VIs not present in the standard NXT module? Obviously the pricing is very different, but for a student the academic version of LabVIEW is actually lower cost than this new Education Edition.

Inh-
LabVIEW Education Edition (LVEE) includes the NXT Module and the API to interface with Vernier products. LVEE is geared towards middle school and high school classrooms to get students interested in math and science. It includes curriculum for teachers that may not be familiar with programming and LabVIEW in general to use the NXT bricks and the LabVIEW environment.
LabVIEW with the NXT module only has the NXT API and not the Vernier API. It will not include the course work and as extensive example programming useful for teaching.
For additional information on LVEE, please take a look at the Getting Started with LabVIEW Education Edition or go to ni.com and search for “labview education edition”.
Regards,
Mike S
NI AE

LabVIEW 2009 and its sp1

I have the LabVIEW 2009 and LABVIEW 2009 SP1. Do I have to install 2009 first and then 2009 SP1? Or the 2009 SP1 also includes the full 2009. The reason I am asking is that I installed my 2009 on a computer, which took forever by the way. After the 2009 installation is completed, I installed the 2009 SP1, and it took pretty much the same amount of them, so I am wondering did I have to install both?
Yik
Kudos and Accepted as Solution are welcome!

Thanks!
Kudos and Accepted as Solution are welcome!

NI-Fieldpoint support in Windows 7 and LabView 8.6

We have a "classic" FieldPoint system with an ethernet controller. We want to be able to read/write from/to the FieldPoint network using a computer with LabView 8.6 and Window 7. Is NI-FieldPoint supported in LabView 8.6 and Windows 7?
Regards,
nate
Solved!
Go to Solution.

Hi natewkidd,
I feel like there is some confusion between the operating systems running on a development machine (like Windows 7) and the real-time operating systems that run on our real-time controllers (like the FP-2000). I will do my best to clear up this confusion by first answering your questions.
1) What is the difference between LabView Real-Time 2009 and LabView 2009?
LabVIEW Real-Time 2009 is actually a software package officially known as the LabVIEW 2009 Real-Time Module that is installed after the LabVIEW 2009 development software to allow the user to develop and deploy real-time applications to real-time targets such as your FP-2000. You can think of the LabVIEW 2009 Real-Time Module almost as a plug-in for LabVIEW 2009 to allow for real-time application development and deployment.
2) If I have a FP-2000 on the ethernet network and want to use a computer running Windows 7 and LabView 2009 to record and display data, will I still be able to communicate with the FieldPoint network using the FieldPoint Read/Write VIs from my Windows 7 machine?
If you were just going to use the FP-2000 as a network module (NOT deploying a real-time application to run on the FP-2000 itself), you should be able to communicate with it using just the FieldPoint Read/Write VIs from your Windows 7 machine with LabVIEW 2009 and the NI-FieldPoint 6.0.5 driver. In this situation, you actually do not need the Real-Time Module since you are not deploying the application to the real-time target.
Regarding the FP-2000 not being supported beyond LabVIEW 8.5.1, this is because the memory on the controller is not large enough to hold the software that is installed on the controller with LabVIEW 8.6.x Real-Time Module and the LabVIEW 2009 Real-Time Module. For more information on this please check out this KnowledgeBase article.
I hope this is helpful! Let me know if you have any further questions.
Thank you for choosing National Instruments.
Aaron Pena
National Instruments
Applications Engineer
http://www.ni.com/support

Why does labview 2009 32-bit closes up with no error message?

Hello.
I am developing an application using a PCI-6534 board, Windows XP SP3, and LabVIEW 2009 32-bits. In this application I am generating a 300 Hz signal using the P2.0 digital line. I am trying to make digital acquisition using the P0 port (8 bits), using N-sampling. The program that generates the 300 Hz clock, works with no problem. However, when I start running the program that performs the data acquisition, LabVIEW suddenly closes up with no error message. The LabVIEW windows just disappear from the screen.
As for me it looks like a LabVIEW bug.
In case anyone decided to help me, I could attach the programs so that you could check them.
What can I do to solve this problem?
Thank you.

I had the same problem with one of our applications. I supplied gigabytes of process monitor and desktop execution toolkit logs, but nothing was resolved. I upgraded from WS2003 and LV2009sp1 to W7 64b and LV2010, per NI's recommendation but the problem persists. I had the corresponding service ticket open for 3 months where NI said the application ran fine for them on W7 with 2010. (long story)
I understand your frustration, and I recommend getting your local application engineer involved as an advocate with application support.. If you pay for service, pound on them to provide it. My $0.02.

Exchanging 2 D array between VBA and labview

I have a project : half part is VBA writen, half part is Labview coded. Both parts are writen to operate manually. The first one prepares data and charts them on charts sheets, the second one smooths data with ready made labview curves fitting VIs. So I want operator could use them seamless, that means calling labview from VBA 2007 code collecting X,Y data into a 2 D array, then send it to labview DLL smooth the curves and send back an array with smoothed data to excel through VBA.
My concern is how to declare 2D array parameters in VBA and in Labview in order to work fine (array of variants or doubles, parameters declared by ref or by val)
I have seen similar topics in NI forum but they dealt with VB.net and not VBA .
I run office 2007 and labview 2009 full dev. system with application builder.
Regards

bassevellois wrote:
Thank you for the answers.
The examples provided with labview for ActiveX exchanges are not very clear. I want to use labview as ActiveX server and Excel through VBA as client.
There's only one example that I know of that ships with LabVIEW and it shows how to access LabVIEW from VB using LabVIEW's ActiveX server. It opens a VI and runs it. Doing it from VBA is very similar. You want to add the reference to the ActiveX Server in your VBA project. If you're controlling the LabVIEW development environment directly, then the library to include in your list of references will be "LabVIEW x.x Type Library". If you are controlling a LabVIEW-build app, then the library name will be whatever you specified when you built the app.
I have no idea of creating and exposing classes, methods or properties needed in VBA from my Labview VI which was at the beginning a standalone application.
I don't quite understand what you are referring to. The ActiveX Server in LabVIEW and a LabVIEW-built app are pre-defined. You do not export anything from your LabVIEW VI. The available properties and methods are a function of the LabVIEW ActiveX Server, not of your VI. If you are building an app then you just need to enable the ActiveX server for the application, and that's done in the build specification.
How to reproduce my example:
Make sure you've enabled the ActiveX Server in LabVIEW.
Download the attached 2D_VBA_Test VI to your C:\Temp folder. You can save it anywhere, but you'd have to change the path in the Excel VBA macro.
Download the attached Excel workbook.
Open the workbook and click the button. If LabVIEW is not running it should launch LabVIEW, and open the VI and populate the front panel array with the values from the spreadsheet.
Attachments:
2D_VBA_Test.vi ‏6 KB
VBA to Excel.xls ‏24 KB

Favor to ask : can you open this labview 2009 Vi and save it for me in a Labview 8.6 readable vi ?

Hi guys,
I have a favor to ask : May somebody would be nice enough to open this Labview 2009 VI and save it in a Labview 8.6 readable VI ? You'll probably have some missing blocks cause I use specials ones but I don't want to have to re-make all the VI.
Thanks you very much
G.
Solved!
Go to Solution.
Attachments:
Control3.vi ‏29 KB

notimperial wrote:
Probably not the right place to do this, but could someone onpen this in labview 2010 and save it in a format compatible with labview 2009?
Thank you in advance
You are right we have a thread for this here.
http://forums.ni.com/t5/LabVIEW/Downconvert-VI-Requests/m-p/1067229
Here is your vi please use the downconvert thread next time.
Tim
Johnson Controls
Holland Michigan
Attachments:
WFMreaderIII.vi ‏53 KB

Run-time engine problem in Labview 2009 and Labview 2010

I have a problem with Labview 2009 and Labview 2010. I updated my Labview 2009 into 2010. But it turned out to be a trial one, because i did not have the serial number. So I uninstalled the Labview 2010. however, the funny stuff came over. I cannot use my Labview 2009. So i uninstalled Labview 2009 again. But eventually, I could not reinstall Labview 2009. Every time i had a runtime error and i could not proceed with the installation. in addition, any installation related to Labview is not permitted and the same error came up every time. it is very annoying.
So, What is the deal?
I attached the error here. Any comments or advice are welcomed and appreciated.
Attachments:
error.docx ‏2305 KB

By chance is this machine's language set to any non-English locale? You would check the locale setting by:
Opening Control Panel.
Opening "Regional and Language Options".
Looking Under "Regional Options" >> "Standards and Formats"
If it is set to something besides English, trying setting it to English and please report back what locale it was set to (or if this even solves the problem).
Regards,
- WesW

Potential Bug with LabVIEW 2009, Report Generation Toolkit, and MS Office 2003

We have discovered an issue with the above listed software. Specifically this pertains to Print Report.vi in the Report Gen palette. Basically, we have discovered that with Office 2003 installed the VI will error out. We've been using it in an executable, and the executable physically fails (and asks us to report an error to Microsoft). With Office 2007 we don't have a problem. We've tried building the examples into executables, and those work because they are printing HTML reports.
Also, we have converted back to LabVIEW 8.6 and rebuilt the executable and installed and it works perfectly. Its on the combination of LabVIEW 2009 and Office 2003 that seems to fail.

yeah, we had seen that, and been told about it by another user. we tried, to no avail. we still have ended up having to migrate back to 8.6.1 to get the executable to run properly.

LabVIEW 2009 x64 and application builder

Hi
My organisation has just got a site licence for LabVIEW so I have just installed 2009 x64.
My question is this:
If I build applications written using LabVIEW 2009 x64, will they only run on 64 bit computers? I would test this but both my computers are 64 bit machines. I have had a brief look through the build specs but there doesn't seem to be anything about 32/64 bit compatibility.
thanks.
J
Solved!
Go to Solution.

Does this help?
http://digital.ni.com/public.nsf/allkb/71E9408E6DEAD76C8625760B006B6F98
Q. Can I run an executable built with LabVIEW 64-bit on a 32-bit PC?
A. You cannot run the LabVIEW 64-bit Development System, Run-Time Engine, or executables on a 32-bit PC.
Q. Can I run an executable built with LabVIEW 32-bit on a 64-bit PC?
A. Windows can run 32-bit executables on a 64-bit PC. Therefore, the LabVIEW 32-bit Development System, Run-Time Engine, and executables can be run on Windows 64-bit.
Q. Can I have both LabVIEW 32-bit and LabVIEW 64-bit installed on the same 64-bit machine?
A. Yes.
Q. Can I build a 32-bit version of an executable from the LabVIEW 64-bit application builder?
A. There currently is not an option to create a 32-bit version of an executable from the LabVIEW 64-bit application builder.

LABVIEW 2009 and lvanlys.dll

Hi,
I'm relatively new to LABVIEW and I'm building an application with LABVIEW 2009. The application works well on my PC. However, the application is
intended to be ran on another machine. I then tried two approaches. First, I copied the executable file onto the second machine and second, I created
an installer file. Both methods resulted in an error when the executable was ran on the second machine. Here is the error:
"Missing external function lvanlys.dll Mean_Head.C in VI NI_AALBase.lvlib:Mean.vi". I'm hoping anyone out there knows the solution to this.
Thanks!
Bobby C

I'm not sure that link is appropriate since it talks about LabVIEW 7.1 installer and windows NT.
For LabVIEW 8 or higher, make sure that the data folder is part of the install. Done correctly, there will be your application, the data folder, and in the data folder, lvanlys.dll.

Installing 64 bit version of toolkit and modules for Labview 2009 64 bit?

Hello I recently contacted NIabout installing Mathscript and Signal processing toolkits for my Labview 200964 bit that I am running on Windows 7. I was sent the following link as aresponse: http://zone.ni.com/devzone/cda/tut/p/id/10383. From this link it is my understanding that I cannot run any programs thatcontain an astrestik, since they only work for 32 bit version of Labview? In particular I really need to use Mathscript. Is there any workarounds? Do I have to also install the Labview 2009 32 bit version? Doesanyone know when Labview will allow me to run everything in the 64 bit versionof Labview? Thanks.
Kevin

Hello Kevin,
There is no workaround available, and there are no released dates as to if/when Windows 7 x64 support for the toolkits in question will be introduced.
The LabVIEW Mathscript RT Module is not supported in LabVIEW 64-bit as mentioned at the bottom of the following page: http://zone.ni.com/reference/en-XX/help/371361F-01/lvhowto/labview_mathscript/ .
Vivek Nath
National Instruments
Applications Engineer
Machine Vision

Getting Error 08 when attempting to build exe using LabVIEW 2009 (32 bit) and Windows 7

Testing development platform on Window 7 vs XP. I received following message while building an executable using 2009 32 bit on Windows 7 machine. Same build will work on an XP machine.
Error 8 occurred at Copy in AB_Engine_Copy_Error_Files.vi->AB_Application.lvclass:Copy_Error_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_EXE.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_Application.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: File permission error. You do not have the correct permissions for the file.
=========================
NI-488: DMA hardware error detected.
C:\Program Files (x86)\National Instruments\Shared\LabVIEW Run-Time\2009\errors\Internet Toolkit-errors.txt
Any suggestions?
Thanks

For any who may be having this problem here is a little more information and what I did to get around the issue. (so far)
First I tried a simple vi with a while loop in a project and made an executable build. This worked. I double checked on an XP machine the project that I was having problems with. The executable was built successfully. I changed back to the Windows 7 machine. On the program compatibility trouble shooter I started the LabVIEW 2009 (32 bit) in the XP service pack 2 mode and selected run as administrator. The build was successful.
Note: was logged in as administrator and program would build a simple executable in Windows 7. The executable that would not build had more complex code that included serial communication and calls to lvanlys.dll and nilvaiu.dll.
This may not be a complete fix to the problem but at least in this one case it worked.

VLC and LabView 2009

Similar Messages

Maybe you are looking for