Real-Time Measurement and Control

cancel
Showing results for 
Search instead for 
Did you mean: 

Linux plug-in for Real-Time Target

We have installed the Linux plug-in for Firefox per the NI tutorial (Doc ID: 3NIDOLTQ), as suggested by NI App Engr. However the remote front panel is still not displaying properly from the Linux PC (works great from the WinXP machine). Our Linux expert (not me) thinks the problem could be with the directory structure on the Linux PC. Would anyone that has this working be able to provide advice on whether anything special must be done as far as that is concerned? The target is a PXI-8104 RT controller.

 

Thanks!

 

0 Kudos
Message 1 of 12
(4,595 Views)

Hi,

 

I'll need a bit more information about the problem before I can try and find a solution.

 

1. What flavor of Linux are you using?

2. What version of LabVIEW are you running?

3. Can you post a screen shot of your remote front panel or the error you are getting?

4. Is the plug-in installed in the exact path specified in the linked KnowledgeBase article?

 

Thanks!

Tanya Visser
National Instruments
LabVIEW Group Manager
0 Kudos
Message 2 of 12
(4,578 Views)

Hi Tanya,

 

Here are my answers:

 

1. CentOS 5.5 x86_64 (OSS version of RHE 5.5) and Firefox 3.0.5

 

2. LabView 2009 SP1

 

3. This may a bit difficult, since the equipment is located in a classified lab. It can be done but, essentially, all we see is an empty Remote FP frame, with no error messages. The frame has the title, etc, that I created with the Web Publisher.

 

4. No.  But it is installed in the directories that Firefox thinks it needs to be in to be recognized as an installed plugin. I'll have to go get the specific directory, but I think they get installed in /usr/lib64/mozilla/extensions/wrapped-plugins/

 

Thank you!

Mark

 

0 Kudos
Message 3 of 12
(4,573 Views)

Hello, Mark!

What does "about: plugins" (without space) in firefox address string (Ctrl+L) show? It must show NI Netscape plugin <=9.0.

Check ApplicationName.ini and niwebserver.conf if they exist for ports and access lists.

Check open ports for PC in iptables and listen ports on the target.

 

0 Kudos
Message 4 of 12
(4,550 Views)

 

I'm sorry, Mark. If You see the frame, all'is ok with ports... But firefox plugins installed checking is not superfluous and perhaps html code too.

 

0 Kudos
Message 5 of 12
(4,535 Views)

Tanya, I have some more info on our Linux configuration:

 

Installed Plugins:

File name: nswrapper_64_64.LV90NPlugin.so

MIME Type: application/x-labviewrpvi90

Description: LabView as Plug-in

Suffixes: rpvi90

Enabled: Yes

 

Directory Info:

 

firefox - 3.0.18

/usr/lib/firefox-3.0.18/extensions/LV90NPlugin.so

/usr/lib/moxilla/plugins/LV90NPlugin.so

/usr/lib/moxilla/plugins-wrapped/nswrapper_32_64.LV90NPlugin.so

 

/usr/lib64/moxilla/plugins/LV90NPlugin.so

usr/lib64/moxilla/plugins-wrapped/mswrapper_32_64.LV90NPlugin.so

usr/lib64/moxilla/plugins-wrapped/nswrapper_64_64.LV90NPlugin.so

usr/local/lib/Labview-2009/LV90NPlugin.so

 

[all the above typed in manually, but I think I got it right]

 

Mark

 

 

0 Kudos
Message 6 of 12
(4,520 Views)

Did You tried

nspluginwrapper -v -a -i

command for loading 32 bit plugin, Mark?

And how about "about: plugins" in the browser address? Are You shure that plugin installed and loaded?

It is not meaningful to litter system, copying a file of dynamic library repeatedly. It is enough to choose one directory. If one person uses, it is enough to copy in a directory ~/.firefox/plugins LV90NPlugin.so file. Perhaps libstdc ++. so.5.0.3 with libstdc ++. so.5 link must be copied in the same directory (i'm not shure about RH distributions) too.

And finally, at plug-in loading, a lot of information can be received from the console at start of the browser.

0 Kudos
Message 7 of 12
(4,502 Views)

Thanks for keeping up with this issue, Kolan, I greatly appreciate it.

 

We'll try your suggestions tomorrow and let you know the results.

 

0 Kudos
Message 8 of 12
(4,481 Views)

Tanya,

 

I can't believe this, but I just now realized - and MikeS @ NI confirmed - that we must have the LabView 2009 SP1 Run-Time Engine installed on the Linux PC! For some reason I had the idea that it was _not_ required.

 

I have downloaded the RTE for Linux and we will install/test first thing tomorrow morning. Will let you know results as soon as possible. Hopefully this is the fix.

0 Kudos
Message 9 of 12
(4,440 Views)

Tanya,

 

Turns out we _did_ (and still do) have the Linux version of LV RTE installed - so that wasn't the problem.

 

The only other thing we can think of is a 32 vs. 64 bit issue...however I do not see any mention of 64 bit with respect to the Linux flavor RTE...?

 

If that's not it, then we're out of ideas...

 

 

0 Kudos
Message 10 of 12
(4,425 Views)