Compatibilité Labview 2009 Windows / Labview 8.5 Linux

Bonjour à tous
J'ai une petite question à laquelle je suis certain bon nombre d'entre vous avez une réponse
J'utilise deux PC avec Labview 2009 WIndows sur chacun qui communique avec la fonction UDP.
Seulement voilà, la trame qui va d'un PC à un autres, je souhaiterais la faire passer par une passerelle, un troisième PC, toujours en UDP mais lui équipé de Labview 8.5 sous Linux.
Le truc c'est que cela fonctionne pendant une minute ou deux et après la communication s'arrête au niveau du PC Linux Labview 8.5
J'aimerais donc savoir si la communication UDP entre Labview 8.5 Linux et Labview 2009 Windows est bien possible
Je vous remercie énormément pour vos réponses....
A très bientôt.
Vincent

Bonjour,
Si vous voulez vérifier la compatibilité entre Linux et Windows, le mieux serait d'utiliser les exemples LabVIEW. Ces exemples se trouvent dans Aide>Recherche d'exemples...>Réseau>TCP & UDP. Vous pourrez ouvrir "Client de données simple" (ou "Simple Data Client") sur votre LabVIEW Linux et "Serveur de données simple" (ou "Simple Data Server") sur votre LabVIEW Windows.
Après l'avoir configuré selon votre configuration, exécutez en premier le Serveur de données simple sur Windows puis le Client de données simple sur Linux.
D'après l'aide de la fonction UDP Open de LabVIEW 2011 une mention a été ajoutée par rapport à l'aide des version 8.5 et 2009. Il semblerait qu'il y ait un comportement particulier aux version non Windows de LabVIEW lorsque vous cablez l'entrée "net address". Dans le cas où les exemples ne fonctionneraient pas, je vous conseil d'essayer en supprimant cette entrée et de ne vous baser que sur le port de communication.
Cordialement,
Mathieu P. | Certified LabVIEW Associate Developer
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
Journées techniques : des fondamentaux aux dernières technologies pour la mesure et le contrôle/comm...

Similar Messages

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

Convert code from LabVIEW 2009 to LabVIEW 8.6

Hi Everyone,
Could a kind person with LabVIEW 2009 please save the attached code in LabVIEW 8.6.
The code is of the Creating an Office 2007-like Ribbon in LabVIEW community page.
It would be very helpful!
PS. Will reward kudos.
Kind Regards
James Hillman
Applications Engineer 2008 to 2009 National Instruments UK & Ireland
Loughborough University UK - 2006 to 2011
Remember Kudos those who help!
Solved!
Go to Solution.
Attachments:
LabVIEW Ribbon.zip ‏306 KB

Any problems let me know and I will look at again
David
www.controlsoftwaresolutions.com
Attachments:
New Folder (2).zip ‏108 KB

Labview 2009 to labview 8.5

i want to open labview 2009 vi in labview 8.5.
Solved!
Go to Solution.

You can't.
You will have to open it in LV 2009 or later and do a "Save for Previous Version" to save it back to LV 8.5.
If you don't have a newer version. Post your VI in the Downconvert thread saying it is LV 2009 and you want LV8.5.

Downconversion LabVIEW 2009 to LabVIEW 8.5

I'd like to convert these three files from LabVIEW 9.0 to LabVIEW 8.5.
Thank you
Attachments:
RS232_Hyper Terminal_Communication_Example.vi ‏102 KB
Find_Serial_Port.vi ‏28 KB
State Machine LLB.llb ‏102 KB

Saved to 8.5
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
Attachments:
RS232 Example.zip ‏143 KB

Labview 2009 32 bit not running on xp 64 bit

Hi all,
I tried to upgrade to LabVIEW 2009 from LabVIEW 8.6 on 64-bit windows XP machine. Following about a 2 hour removal of 8.6 and subsequent installation of LV 2009 it turns out that the device drivers are not compatible with a 64-bit machine. On launching LabVIEW 2009 (32-bit) an error box appears stating that it is corrupt or missing files and to correct this using control panel etc. I have tried this and still the same error occurs and LV refuses to start.
All the license files are correct and the compnents are activated.
Anyone know how to fix this? Or should I go back to 8.6 and cancel my upgrade subscription?
Secondly, I am using a firewire camera and was informed that Ni-IMAQ legacy are no longer supported and to go to ni.com/ifo and enter legacy1394 to see how to download drivers etc for this. I end up on a page that says "not authorized".
Any help gratefully appreciated.
Solved!
Go to Solution.

Leeser wrote:
I agree that XP64 and LV 2009 are not compatible as I installed LV 2009 on another 32-bit machine with no problems. I was just surprised as there were no problems or issues that I came across for 8. on XP64. Ah well, a uninstallation and reinstallation lies in wait for me on Monday morning!!
As an aside why call it LV 2009 instead of LV 8.7 or even LV9.0...sounds reminiscent of an operating system!!
Regards,
Leeser
LabVIEW 2009 is according to the internal version scheme actually equivalent to LabVIEW 9.0. Why they changed the naming? I guess marketing told them to do so. Why then? Well marketing has some funny ideas sometimes. I guess since THE software provider in this world has started to do this since about Windows 2000 someone must have thought it to be the best idea since sliced bread and decided to do it for LabVIEW too.
Another guess is that in about 2010 there would have been something like 9.1, and 10.0 would then come out in 2011 and that sounded somehow to someone like a bad scheme so they decided to change it now. But maybe it will be forgotten and everybody returns to the old versioning at the begin of next year when 9.0.1 will come out, which would then otherwise be LV 2009.1??? Or maybe LV2009 SP1?
It has already happened with LabVIEW 6i (iMacs, iPhones, iAnything), LabVIEW 7 Express and LabVIEW 8.20 (following 8.0.1 and marking the 20th anniversary of LabVIEW, and being internally LabVIEW 8.2). All some marketing fun or hysteria.
Rolf Kalbermatter
Message Edited by rolfk on 08-17-2009 11:08 AM
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

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!

LabVIEW 2009 SP1 Run-Time Engine (Minimum) (32-bit) for Windows - Supported Features

Hi,
Can some one please point out what features are supported by the LV RTE (Minimum ) [LabVIEW 2009 SP1 Run-Time Engine (Minimum) (32-bit) for Windows]
1) Is there a limit on the size of the exe which can be run on it?
2) Will this support additional modules like DAQ etc.,? Or do we have to chose the regular installer ( 170 Mb ) for that purpose?
3) If a list of what it does or does not support is available, it would be extremely helpful.
Thanks In advance.
Regards,
Vijay

Anand,
I did go through both the links that you had sent earlier before posting on the forum. For eaxample refer the following link where it says,
http://joule.ni.com/nidu/cds/view/p/lang/en/id/1599
It does not contain the full run-time engine, but will allow some executables to run.
1) What do they mean by 'some' executables. Is there a list of yay's and no's available?
2) Can someone from NI reply to this and shed more knowledge?
Regards,
Vijay

Labview 2009 .exe not working with windows 2000

I created a simple vi with Labview 2009 to reset a counter in registry key. I changed it to an exe. The program runs fine on any machine with XP but it does not work on the machine I need it on which is running Windows 2000 SP4. I installed the 2009 runtime but I continue to get an error when it starts up saying the vi is not executable and that I need the full development to fix the errors. But like I said it works every where else. I've tried other exe wrote in LV2009 on this machine and they work. Is there something in my vi that is not compatible with Windows 2000?
Thanks
Solved!
Go to Solution.
Attachments:
Serial Number Reset Cell 2.vi ‏15 KB

There was an issue with building DLLs on Windows 2000 - http://digital.ni.com/public.nsf/allkb/431C9BD8F3482033862576A90073441F. Since you say you are trying an EXE, this may not be applicable.
George M
National Instruments

Can i build an application with Labview 2009 for Windows 7?

Hello
i use Labview 2009 SP1 and the application builder 2009 SP1. If i install the application on win7 this message is display:
Labview Run Time Engine depends on pruduct with upgrade code (...) version 9.0.301, language {} which is not in distribution.
Solved!
Go to Solution.

Is this an issue with Windows 7 having both installation folders for 32 bit (C:\Program Files (x86)) and 64 bit (C:\Program Files)?
I had an application built on an XP machine and installed on a Windows 7 machine which was looking for files in C:\Program Files when they were actually installed in C:\Program Files (x86) - because it was 32-bit application. After installation I had to move the files from 1 location to the other to make it work.

LabVIEW 2009 build memory usage exceeds Windows limit

We have a large application that builds without problems using 8.6.1, but failed to build using LabVIEW 2009 with the error "Not enough memory to build this application".
We solved the problem by adding the parameter /3GB to the Windows XP boot.ini file. This increases the available memory for a Windows XP application from 2Gb to 3Gb.
It appears that LabVIEW 2009 uses more memory during the build process and, in our case, this took it over the 2Gb limit.

We are also facing the same problem...
can National Instruments help us ??????
Following error is occuring while creating exe.
"Build was unsuccessful
An error occurred while saving the following file:
D:\BIS_Main_2009_V3.XY\branches\BIS_Main_2009_V3.61_Trans\User Interface Panels\Inspection.vi
Invoke Node in AB_Source_VI.lvclass:Close_Reference.vi->AB_Build.lvclass:Copy_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_Build.lvclass:Build_from_Wizard.vi->AB_UI_Frmwk_Build.lvclass:Build.vi->AB_UI_FRAMEWORK.vi->AB_Item_OnDoProperties.vi->AB_Item_OnDoProperties.vi.ProxyCaller
<APPEND>
Method Name: <b>Save:Target Instrument</b>"
Please suggest!!!

How to install Labview 2009 on Windows 7

This might be a Windows 7 configuration. I tried "Run as administrator" or Run in Compatibility mode" the setup.exe file. Windows 7 does not allows to copy files in the System32 folder, so I can't install Labview.
Is somone can help to install Labview 2009 on Windows 7?
Thank you

Seems as though you're seeing something different than what I first thought.
LabVIEW should install to a drive other than "C" without trouble.
I had a look around to see if anyone else had seen this problem, and I found something interesting here: http://windowstipsandfixes.blogspot.com/2008/10/error-1310-cant-write-to-configmsi.html
Specifically with regards to resetting the Windows installer with the following:
msiexec /unreg
msiexec /regserver
Other than that, I'm not sure what might be causing the problem you're seeing.
Patrick Allen

Font size on Windows 7 with LabVIEW 2009

Hello,
after installing labview 2009 on windows7, I have a problem with the font size of my old application written in 8.6.
the Application Font has seemed to default to another style under windows7 so I searched the forum for the default font under XP when I used lv 8.6. Tahoma 13pt seemed to the correct choice, however when i changed all default fonts to Tahoma 13pt it helped and they look very similar, but the Tahoma under windows7 is slightly longer that the original and it looks like there is some sort of font smoothing going on... perhaps windows is doing its "cleartype" thing by default and influencing its length (thou i thought this shouldnt be the case).
This small difference is causing havoc in my GUI as objects are being resized in a bad way.
Please see the screenshot for an example of my concerns
Another question on the side... is there a Font I can use that will keep the appearance and size over all OSs?
Any help would be appreciated...
Best Regards
Alex.
:. LV2010 SP1 ... W7 .:
Attachments:
Font Difference.png ‏3 KB

Actually this problem affect LabVIEW itself even while editing!
Many of NI's screens suffer from the same problem. Configuring events is one of the most obvious cases. Since teh edit events screen does not allow for resizing, there are some events that you can only guess what they are.
I tried reporting this but the AE wanted me to spoon feed screen shots and ....
I think what really irks me over this problem is that I purchased a laptop with the biggest screen available just to let me do LV and in the end LV can't handle the laptop.
Double -
Ben
Message Edited by Ben on 05-06-2010 10:13 AM
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

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.

Support in LabVIEW 2009 for IMAQ legacy drivers on 64-bit windows

Hi,
I have been trying to use a VI that was created in LabVIEW 7.0 that makes use of IMAQ 1394 VI's in LabVIEW 2009. When I first tried to run the VI an error told me that the VI's in question were missing, to overcome this problem I thought I should attempt to replace them with legacy VI'. After downloading the legacy installer, I then realised that these VI's would not function on a 64-bit version of windows even though I have a 32-bit version of LabVIEW.
I was wondering if there is an alternative way of replacing these VI's or a way of implementing the lagacy VI's? Would it be suitable to replace the IMAQ 1394 VI's with IMAQdx VI's?
Thanks for your time,
Alistair Martin

Hi Alistair,
The following KB states that it should be possible to do what you require: http://digital.ni.com/public.nsf/allkb/3358528DF8648DC2862571F500586140?OpenDocument
The KB also links to some development articles for upgrading and using IMAQdx to acquire from 1394 cameras.
I hope this helps,
Kind Regards,
Applications Engineer

Compatibilité Labview 2009 Windows / Labview 8.5 Linux

Similar Messages

Maybe you are looking for