Jump to content

Problem with Network Streams in EXE LabVIEW


Go to solution Solved by Dawid,

Recommended Posts

I'm trying to find a way to communicate between two executable LabView app, because of several reasons I chose (associated with my application) Network Streams. Everything works fine so long as they are the VIs. When I build exe files there is no communication between apps. The apps waits forever for connection (because there is no timeout). Did anybody meet the same problem? I will be very grateful for any advices and comments.

 

 

 

TestStream.vi

TestStream2.vi

post-52806-0-19325000-1414491272_thumb.p

post-52806-0-19450100-1414491276_thumb.p

Edited by Dawid
Link to post
  • Solution

I found the solution!

 

I tried to delete the topic, but I cannot. Anyway the problem was associated with Streams Names, which should be unique. Till you are using streams in LabView there is no need to build "Stream Name" as full URL,

"ni.dex://host_name:context_name/endpoint_name". Context_name is optional when Streams works in LabView, but it's necessary to have this name when you are building exe files. The context_name is the name that identifies which application context the endpoint resides in. If somebody need more info, everything is here: http://www.ni.com/white-paper/12267/en/

  • Like 1
Link to post

If you have multiple instances of an application that uses network streams, you can have each EXE give its stream a unique context name by generating a GUID. There is a way to get it via .NET. 

Link to post

I found the solution!  I tried to delete the topic, but I cannot. 

You can formally request topic moderation by using the Report to Moderator button.  But in this case I would rather we leave the topic as is.  Even if your issue was solved, others may look for help on this subject, and finding what you have already done helps the community.

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Similar Content

    • By drjdpowell
      I am just starting on trying to be able to use Python code from a LabVIEW application (mostly for some image analysis stuff).  This is for a large project where some programmers are more comfortable developing in Python than LabVIEW.  I have not done any Python before, and their seem to be a bewildering array of options; many IDE's, Libraries, and Python-LabVIEW connectors.  
      So I was wondering if people who have been using Python with LabVIEW can give their experiences and describe what set of technologies they use.
    • By Yaw Mensah
      I have installed Labview 2020 on Dedian Buster using the rpm to deb conversion method via alien. Due to Architecture mismatch i deleted the *i386.rpm files before conversion.
      My Problem is that after creating a project at "Build Specification"-> "rigth click" i am only able to select "Source Distribution". Application does not show up as an option. 
      I will be grateful for any suggestions.
      Thank you in advance.
    • By javier_r
      VIPM.io now allows you to post LabVIEW Resources, Ideas, and Tools. For example, you could post a link to a video tutorial or blog article about a package. You can also post ideas, like feature requests or new tools. Best of all, package developers are notified when you post your ideas and resources, and you can comment and discuss posts with the community. Take a look at this video to learn more: https://www.vipm.io/posts/664960df-f111-4e13-989a-24be8207182d/

    • By Shuvankar Das
      I want to connect My ccd camera with labview. The details of my system is given bellow. I cannot connect it please help   OS:  WINDOWS 7, 64bit   LabView Run-Time 2013(64-bit) NI-IMAQ 4.8 NI-IMAQdx 4.3   Camera: QICAM Monochrome Cooled (QIC-F-M-12-C) Model QICAM Resolution 1392 x 1040 Sensor 1/2" Sony ICX205 progressive-scan interline CCD Pixel Size 4.65 x 4.65µm Cooling Type Peltier thermoelectric cooling to 25˚C below ambient Digital Output 12 bit Video Output FireWire (IEEE 1394b) Max. Frame Rate 10 fps full resolution @ 12 bits Pixel Scan 20, 10, 5, 2.5MHz Mount Type C-mount optical format  
       
    • By javier_r
      Hello everybody!
      Wondering how many people have tried the new vipm.io site. We have added a ton of features to make it easy to Discover LabVIEW Tools and there are some cool ones coming soon.
      Check it out and let me know what you think 😀
       
      Javier

×
×
  • Create New...

Important Information

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