10-08-2010 10:59 AM
Joe,
Thanks for pointing this out, I assumed that because I used the "Web Publishing Tool" (found on the Tools menu in LabVIEW) I would have the format that I needed. After all, in Windows it works perfectly without changing anything.
To remove the cRIO out of the equation, I am working now with the Real-Time Chart.vi shipping example that is mentioned when opening http://xxx.xxx.xxx.xxx:port/ when enabling the web server in LabVIEW. I am running the Real-Time Chart.vi on a Windows XP + LabVIEW 2010 machine. Then in another Windows XP + LabVIEW 2010 Run Time engine (no LabVIEW) I open the html page that I created using the Web Publishing Tool. I am able to see and control the Remote Panel with no problems.
After reading your post, I went an changed the following line in the html code:
<EMBED src=".LV_FrontPanelProtocol.rpvi100" LVFPPVINAME="Real-Time Chart.vi" REQCTRL=false TYPE="application/x-labviewrpvi100" WIDTH=519 HEIGHT=435 PLUGINSPAGE="http://digital.ni.com/express.nsf/bycode/exck2m">
to call for TYPE="application/x-labviewrpvi2010" this removed the "Missing Plug-in" message from the page, and when opening it in FireFox on the MAC it shows a message inside where the remote panel would show up "Click here to view remote panel". I click and I get the Remote Panel Launcher, but nothing else.
I downloaded the Text Wrangler to edit the plist like you mentioned, do you think this would make any difference on the Remote Panel Launcher not working? If you think it would, what plist file do I need to edit?
Thanks,
Fab
10-08-2010 11:57 AM
Joe and Patrick,
I did a little more exploring. If I look in the Internet Plug-Ins folder, the plugin is called LV100HelperLauncher.plugin, however the MIME Type is called "appication/x-labviewrpvi2010" and as Joe already pointed out the "Web publishing tool" creates the html file pointing to "appilction/x-labviewrpvi100"
So if nothing else comes out of this post, at least, I believe a CAR should be filed because the names are not consistent. Also the "Web publishing tool" needs to be modified so it creates the correct html code. Is this something you could do?And we still need a work around to make the remote panels work on MAX OS X (10.6). I already upgraded my code to LabVIEW 2010 just so I could use remote panels on MAC OS X (10.6).
You don't need a cRIO to reproduce this problem, you just need a Windows machine with LabVIEW2010 and a MAC with MAC OS 10.6.
1) Make sure your Remote Panel Server is enabled. In LabVIEW go to Tools>>Options>>Web Server. In my case I have my root directory at C:\Program Files\National Instruments\LabVIEW 2010\www
and HTTP port is 8000 and Remote front panels is enabled.
2) check what the IP address for your computer is. In my case it is: 192.168.1.106
3) On Windows machine open: ...\LabVIEW2010\examples\general\graphs\charts.llb\Real-Time Chart.vi
4) use Tools>>Web Publishing Tool... to create the html page with the embedded panel, name the html file: Real-TimeChart (without the space) and make sure the Real-TimeChart.html file gets saved in ...\LabVIEW 2010\www\ folder
5) Run the Real-Time chart.vi
6) On the same Windows machine or another Windows machine open with Internet explorer: http://192.168.1.106:8000/Real-TimeChart.html You should see the remote panel
7) Now on the MAC go to the same page. If you are on Safari, you will get the "missing plugin" message. On Firefox there is no message but in the place of the remote panel you have a tiny square.
😎 Go back to the Windows machine and edit the html page, so instead of pointing to "appication/x-labivewrpvi100", have it point to "application/x-labviewrpvi2010"
9) Verify that the remote panel still works on Windows
10) Now on Safari the "missing plugin" message is no longer there. But clicking on the remote panel blank area does nothing.
On Firefox, in the area for the remote panel, you get the message "Click here to view remote panel"
11) Clicking on the message a "Remote Panel Launcher" pops up, but no remote panel.
This used to work fine with LabVIEW 8.6 and MAC OS 10.5. And I really don't want to downgrade neither my OS nor LabVIEW.
Thanks,
Fab
Here is the image of the Remote Panel Launcher:
Here is the image of how the plugin appears in the Plugins folder:
Here is the image of how it appears listed on the Safari plugins:
Thanks,
Fab
10-08-2010 04:09 PM
Ah, I misread your screenshots: there isn't a plist to edit as far as I'm aware. I don't know how Safari and other browsers implement and store their plug-ins; I thought I had read 'plist' in one of the screenshots, but clearly I was wrong.
Certainly the name-mismatch is one problem, but it appears that there is a fundamental incompatibility between LabVIEW for Windows' remote panel server and LabVIEW for Macintosh's remote panel client. My usefulness has reached its end, sadly, since this is outside my area of expertise 😞
Joe Friedchicken
NI Configuration Based Software Get with your fellow OS users
[ Linux ] [ macOS ]Principal Software Engineer :: Configuration Based Software
Senior Software Engineer :: Multifunction Instruments Applications Group (until May 2018)
Software Engineer :: Measurements RLP Group (until Mar 2014)
Applications Engineer :: High Speed Product Group (until Sep 2008)
10-08-2010 04:16 PM
@JoeFriedchicken wrote:
Ah, I misread your screenshots: there isn't a plist to edit as far as I'm aware. I don't know how Safari and other browsers implement and store their plug-ins; I thought I had read 'plist' in one of the screenshots, but clearly I was wrong.
Certainly the name-mismatch is one problem, but it appears that there is a fundamental incompatibility between LabVIEW for Windows' remote panel server and LabVIEW for Macintosh's remote panel client. My usefulness has reached its end, sadly, since this is outside my area of expertise 😞
Thanks Joe,
The incompatibility would be with the LabVIEW webserver, because I have the same problem when the VI is running in cRIO, not in Windows.
Thanks again,
Fab
10-11-2010 02:35 PM
Patrick,
Have you had a chance to reproduce the problem just using the Real-time chart shipping example?
Thanks,
Fab
10-08-2011 10:17 AM
Hi everyone,
I'm facing exactly the same problem.
Is there any update regarding the topic?
Thanks.
Regards,
Lucio
10-10-2011 05:29 PM
Hi Lucio,
Since this issue does seem fairly dependent on the OS and LabVIEW version, could you to verify the ones you're using? From what I'm seeing in this thread, the problem between LV 2009 and Snow Leopard will still exist if you're using both of those platforms.
Regards,
-Dave C
10-16-2011 08:40 AM
Hi Dave,
I am using LabView 2010 SP1 and I have exactly the same problems as above when trying to connect to a remote panel with a Mac OS X 10.6.8 on which I install the run-time engine. I tried installing both the 2010 SP1 and the 2011 versions of the run-time engine for MAC OS X available on the website.
The remote panels work perfectly, instead, when connecting with a Windows machine.
Thanks,
Lucio Monaco
10-17-2011 06:18 PM
Hi Lucio,
As of now I am not able to find anything new. I could find these three links but they do not shed any new light on the issue. I will let you know if I find anything more.
http://zone.ni.com/devzone/cda/tut/p/id/4791
http://digital.ni.com/public.nsf/allkb/70F17A30DE7B865E8625737F006377F8
http://zone.ni.com/devzone/cda/tut/p/id/7350
Regards,
Nathan B
Applications Engineer
National Instruments
10-18-2011 08:22 AM
I went to look at my notes on this project... we ended up using a Windows PC instead of the MAC. Another option is to use a virtual Windows machine in your MAC.