LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

VIs developed under XP not working on Linux

Solved!
Go to solution

Hello,

 

After calling my NI national support an engineer told me that the code developed under XP is compatible with LV running under Linux (OpenSUSE 11.0).

But some of my VI crash LV under Linux (see some of them in enclosed VIs). Each time, when restarting LV, the investigation pop-up says that the crash comes from "fontmgr.cpp".

 

Is there any solution to force LV to open these VIs ? I wouldn't like to re-build them entirely...

CLA, CTA, LV Champion
View Cyril Gambini's profile on LinkedIn
This post is made under CC BY 4.0 DEED licensing
0 Kudos
Message 1 of 10
(3,371 Views)
Solution
Accepted by topic author CyGa

Hi Zyl7

 

 

See if this helps: http://digital.ni.com/public.nsf/allkb/F19E053DE554BE04862573D300018F37

TN
Currently using LV 8.5
logo
Message 2 of 10
(3,353 Views)
I couldn't test it, because i'm using LV 8.5, but it will probably solve your case. If you get the same error, attach your VI's in LV 8.5 version, so i can test them.
TN
Currently using LV 8.5
logo
0 Kudos
Message 3 of 10
(3,351 Views)
Code is compatible across OS's unless you use platform specific functions. There are a lot of VIs and CTLs missing but one of your VIs is using .NET. This is windows only. The LabVIEW help shows OS limitations for a function.
0 Kudos
Message 4 of 10
(3,349 Views)

Thanks THN !

It solves the problem. But as soon as I close the terminal, LV closes too. Is there any way to launch LV without this command or enabling to close the terminal when LV is started ?

CLA, CTA, LV Champion
View Cyril Gambini's profile on LinkedIn
This post is made under CC BY 4.0 DEED licensing
0 Kudos
Message 5 of 10
(3,326 Views)
That's simply setting an environment variable. You could include that in your startup scripts. See the documentation on the OS on how to do this.
0 Kudos
Message 6 of 10
(3,313 Views)

Well, that's something i dunno..better wait for a NI Engineer reply.

 

I wasn't excepting that too. But if you search for that issue, you will probably thing more stuff about it.

TN
Currently using LV 8.5
logo
0 Kudos
Message 7 of 10
(3,310 Views)

Thanks for your reply.

Do you have any source talking about this ? I can't find anything on startup script / Labview /lang=C ...

CLA, CTA, LV Champion
View Cyril Gambini's profile on LinkedIn
This post is made under CC BY 4.0 DEED licensing
0 Kudos
Message 8 of 10
(3,278 Views)

Hi Zyl7,

 

 

Not really, i can't find any more support related to it. You better try ask that to a NI Engineer, that's a bit strange since your mainly error has been solved. There must be some other kind of conflict between what you've done in linux and bringing it to windows. I've search some other things related, but it probably won't help much.

 

http://digital.ni.com/public.nsf/allkb/4600B3F9007FF4D78625727D0059D878

 

http://www.ni.com/linux/support.htm

 

 

Try to get the last Labview version, if you don't already have it.

 

 

Sorry, but i really can't help you much more.

TN
Currently using LV 8.5
logo
0 Kudos
Message 9 of 10
(3,271 Views)

zyl7 wrote:

Thanks for your reply.

Do you have any source talking about this ? I can't find anything on startup script / Labview /lang=C ...


You're not going to find something specificy to that. You need to search for how to setup environment variables in your shell. The document that was initially pointed to by THN tells you how to set the environment variable within a terminal window. This only applies to that terminal window. However, you can include the setting of the environment variable as part of your profile so that once you're logged in then any terminal window you launch will have that environment variable set. This can be verified by opening a new terminal and listing the environment variables.

 

As I indicated, this is a Linux thing. You need to find out what shell you're using, and what GUI you're using so that you can determine which file to modify. For example, if you're using the bash shell you'd likely modify the .bash_profile.

 

It's possible that some NI engineer who works with LabVIEW Linux will know the answer, but you'll probably get a faster answer if you just Google, or hit some of the Linux boards and search around some of the FAQs. 

0 Kudos
Message 10 of 10
(3,240 Views)