Search the Community
Showing results for tags 'rex'.
lEver wanted to communicate with VI which are across context boundaries? Those typical boundaries, are different LabVIEW project LabVIEW into LabVIEW EXE, EXE to EXE PC to PC across a network or even the internet Usually to get around these boundaries, we have to flatten to some easier transport mechanism like a string and then unflatten on the other end. There are a whole other host of situations and and reasons why cross context boundary communication is useful and not just a simple slam dunk using existing primitives in LabVIEW REx (Remote Export Framework) is a useful framework that you can take advantage of to eliminate the typical boundaries Instead of spend 45 minutes trying to describe it, see the linked videos below, (also in the PPT) until more written content gets made. Basic Demo - Current App http://screencast.com/t/JbW2mM3jx Creating & Using a New Command http://screencast.com/t/GhkE2CEx4Ip Send into EXE http://screencast.com/t/bxbI0B4l8Xs EXE to EXE http://screencast.com/t/xCJw2B39mFQr Debugging Ports / Services http://screencast.com/t/E0RXrgM3Yex Using Service Dump Info http://screencast.com/t/oTUSH5aFqo9S Network Communication http://screencast.com/t/KuTPTKA8rmC1 Rebuild of EXE (addendum) http://screencast.com/t/36oWmrybjRMj ******************* 1/12/15 Update: attached new VIPC which upgrades REx to 220.127.116.11 to address the issues w/ things not moving into the tools menu properly Remote Export – REx Framework.pptx REx Installation Full.vipc 01/31/22 Update: Added update to Error handling on response, required ni_lib_rex-1_15.0.30.vip