Jump to content
News about the LabVIEW Wiki! Read more... ×

Flavio Formica

Members
  • Content Count

    11
  • Joined

  • Last visited

Community Reputation

0

About Flavio Formica

  • Rank
    Active

Profile Information

  • Gender
    Male
  • Location
    Italy

LabVIEW Information

  • Version
    LabVIEW 2017
  • Since
    1997

Contact Methods

Recent Profile Visitors

117 profile views
  1. Ok, and if you click on the Next page button, nothing happens. Correct? Or do you receive an error message?
  2. Sorry Ludo, I lost something. You mean that my engine is not working on your example? Or it is not working at all, with its own pages? In the fist case, maybe, some configuration went wrong. In the second one, there might be some bug in my example... Let me know, I'm curious to find the issue
  3. Hi Ludo, quite odd. I tried several times on any web browser without any issue. Have you got some error message or simply empty page? I'm using that code on different projects, so I think it may be some config problem (I hope….)
  4. As far as the EXE is concerned I agree with Hooovahh. I was able to create an exe an made it work correctly just checking the right paths for external files (i.e., support files or server publishing folder). Unfortunately exe clones did not work properly. I guess that the unique id for the control and indicator components were involved in the issue. Still working on a solution...
  5. Hello guys, I developed something thay may help those who intend to use the Front Panel Publisher for their projects. It may be thought as an addon to the main project. The goal is to create an engine that launches and publishes several independent sessions of the panels you want to publish on web. Each session is unique and fully functional. Vis in the session communicate with engine and web pages through temporary files dinamically created and destroyed. Unused sessions are automatically destroyed after a customized (through config file) timeout has occurred to preserve server resources. The operational flux is: a web page writes a temporary file notificating the (LabVIEW) engine a new request has occurred by a 32bit random number. The engine copies the files having the panels that must be published to a target location with a unique extension (the 32bit number). Support and web pages are also copied to a new folder in the web server operating directory (I used xampp for publishing the pages, but this mechanism should work for other web severs as well). The engine launches the vis with the publishing panels; the first one writes a temporary file that is intercepted by a web page that creates an iframe where to send the front panel page. That page periodically checkes if info in that file has changed. When that occurs refreshes the iframe with the new page. This solution comes from a couple of odd behaviours noted during tests: 1. reentrant clones are not well supported by websockets. Often data are updeted in the wrong istance when more clones are open. 2. all pages that should be published must be opened at the same time (in the same session), otherwise odd behaviours in websockets may occur. You cannot stop a published vi otherwise all the other "clones" (even if they are not generated by reentrancy) are affcted by closures or lack of updating I was able to use this engine for several sessions on different PCs and even android stuff at the same time. Suggestions and corrections will be always well appreciated. Some minor changes were introduced in the main FrontPanel Publishing project. Now the cfg file can be retrieved from a custom folder, so that you can work with different "clones" with the same configuration. I used the last Hooovahh's version to make these changes. Finally I must send my deepest thanks to Marco Gualberto, who used his long term web skills to create the very simple and effective web pages of this project. FrontPanel PublisherEngine.rar
  6. No, Hooovahh, I used your last available version. I did some other tests on different OSs (all those I could use) and I can say that: Remote PC feature works fine if the original vi is running on: Win7 or Win Server 2016 (I suppose also all the previous versions). It does NOT work on Win 10 (trying to investigate why. I think it may be interesting to find the reason). When an old Win 8 PC will be back I'll try that OS too. Also, works fine on IE, Chrome, Firefox, Opera, and NOT on Edge. Trying to find Safari to test it also. The fact that the issue is only on Win 10 AND Edge makes me think that some hidden policies indroduced by Microsoft in Win 10 are involved. I'll keep in touch as soon as I got new info.
  7. Ok, I found something. Using WIn7 as server machine everything works. Using Win10 no. Odd behaviour.... I must find out what changes between those OSs....
  8. Here are the modifications I was talking about... but they did not work...
  9. Sorry Hooovahh, but I'm facing K4zz's same issue. I also connected the external PC IP address to the Host Connection in Publisher.vi and the XAMPP page (with symbolic link enabled) to the Webpage Root link, but, still, I can receive only a static image on the remote PC. Both PCs are under Win10 (1709 release). I do not know what I am missing... Help please... I know it's my fault, but I cannot see where I am doing wrong....
  10. I agree.... That would be a reasonable compromise
  11. Hello everyone, first of all congratulations for this project that is the most similar to our needs I have found. Despite the investments, NXG is at present too young and poor to become a real web publisher for LabVIEW stuff (at least in my honest opinion). I am starting to play on this project in order to find how much it can fit our needs and I immediately found an odd behaviour: though it works pretty fine (I am using Example2.vi as first test) on IE, Chrome, Firefox and Opera, it never works on Edge whatever configuration you might try. Has anyone some explanation for that issue? I tried on two different PCs (both Win10) with the same result. Let me know if anyone has ideas on that. Thanks Flavio
×

Important Information

By using this site, you agree to our Terms of Use.