Share this post

Link to post

Share on other sites

Wezarp will be on the LVTN very soon. In the meantime we can send you a quote. Just ask at sales@wezarp.com

The price is 2450 Euros for one development computer. Then you will be able to create any NI LabVIEW application including Wezarp server and deploy all the executables you want without any runtime to pay.

Share this post

Link to post

Share on other sites

Your video says "Multi-client and multi-control are compliant" at 3:30. However, if one client changes windows, that forces the other clients to change to the same window too. Can different clients work on different windows at the same time?

Share this post

Link to post

Share on other sites

Concidering purchase of Wezarp... As you all know this product is expensive... but for me, the time savings from updating current software vs just insert this VI and recompile justifies the cost.

I downloaded the demo and tried it... seems to work really good, had small issue, but tech support was awesome (this gives me a comfy feeling about the company) that said, would really appreciate the opinion of other LabVIEW professionals. If you have tried Wezarp, pleased chime in... or if you just have an opinion about this type of software chime it also....

Similar Content

hello all,
Firstly I am very new to labview so i apologise in advance if i ask some stupid questions.
i am running a vi on my rio ( simple analog in/out express vi s) and another vi on my PC. i am communicating between them through shared variable and it works perfectly, only thing is i have to manually run both vi s.
my question is, is there a simple way to start the vi on myrio from the vi on my PC?
PS:- i tried to work with vi server but i failed because of my limited knowledge.
any help will be much aprreciated.
Thanks & Regards,
Parth

ShaunR's recent topic on Security reminded me of a situation we explored in the summer and need to revisit at some point. We were looking for a method to protect the communication with a cRIO.

The situation is that we need to communicate between a cRIO and a host on an unsecured network (manufacturing environment.) We concluded that we needed some form of encryption as well as a standard login mechanism but identified that having a single symmetrical key would not provide enough protection (for various reasons and specific use cases.)

Therefore, we looked into SSL and LabVIEW Web Services because it already includes that library and all the security features that we need. We figured out that it would definitely offer the protection required but that would mean rewriting most of existing code to use Web Service instead or establish some for of communication through a new Web Service. Considering the amount of unknown and risks associated with modifying our code, we looked into an alternative and came up with the following scheme:

In short, we would use a Web Service for the initial login and create a new symmetrical key which would be passed to the host and to the main application on the target (cRIO) and would be used to encrypt/decrypt all data during the session. This way, we could still program all of our code in LabVIEW and easily download/deploy the services and applications to the Target using NI standard tools but benefit from proper security and only have to add fairly simple wrappers to some sections of our existing code.

I wonder if anyone else has already gone down that route to add protection to an existing application. Would you suggest a different implementation method or an easier path to a similar result? Is there some obvious pitfalls in this approach that we do not see?

I'm developing an application that uses some PCIe hardware. My daily developing computer is a laptop docked to a dock station. Now, I would like to develop testing my subVIs in the remote desktop that has installed the PCIe hardware. I know I can enable remote debugging, compile and transfer the executable, then execute and connect from my laptop, but this is very inefficient and slow process to test subVIs.

I could install the full development environment in the remote desktop, develop in this machine with remote connection (or even directly on this computer, as it's next to my laptop), but this is not the way I would like to work with every similar project.

Do you have any better approach to debug remote desktop applications? I have heard something about using VI server and executing remote panels or similar, but I have never done such a thing.

Hypothetically, if one created a LabVIEW executable that used a remote application reference to interact with the LabVIEW IDE, how much of the scripting function set would work?

I've already discovered "New VI" doesn't work, but what about the non-creative functions, such as programmatically showing a block diagram, traversing the block diagram, inspecting nodes and other objects etc.? It seems to me that it should be ok to perform inspection, just not manufacture, right?

So why are a load (if not all) of the scripting methods denied when attempted from a remote interface?