LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Data communication using Zmq-socket

Hi,

  I am using the labview 2012 tool with vi packag " ZeroMQ socket Library 3.2.0.100".I am created an installer file of ip- client.vi and it was worked fine in my system only.When it was installed set up of the same to other system, unable to communicate with server.

 

 so please advice me the reason behind this issue

 

  

The screen shot of vi also attached

 

 

 

 

Thanks

 Manoj

 

0 Kudos
Message 1 of 4
(3,606 Views)

Hi mano,

 

what do the error clusters tell you?


Did you already asked the source of this ZeroMQ package?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 2 of 4
(3,601 Views)

Hi GerdW,

           No error reported in the error cluster.The vi running without any error message but it was not sent any message to the server machine.

 When the same installer run in my PC (installer build PC), no error in the communication with server(both sendin and recieving in message),

 

Thanks

Manoj

 

0 Kudos
Message 3 of 4
(3,578 Views)

Unless its changed, that library uses a fixed path to locate the dll. You say that it works on your machine but not a different one -- you just need to make sure your build/installer includes the dll, and make sure that you modify the path used to access the dll. If I remember correctly there is a script in the zeromq folder installed to vi.lib (locate the location of those VIs you are using) which can change the path, but this is only a half-solution.

 

A problem with the library is that since everything is referenced by path, LabVIEW doesn't know to include that dll in your build automatically. The easy way to handle this would be to find all the call library nodes and change them from specify-by-path-input to hardcoded-path. A hardcoded path means labview will include it, as mentioned here: http://digital.ni.com/public.nsf/allkb/862567530005F09C862565C50068363D

 

Another potential solution would be to make sure the dll is in the default search path for your system :http://digital.ni.com/public.nsf/allkb/EBAE870D564CBBE78625788B004E76D3

Except, as I mentioned, the dll is specified by path rather than by name...which has additional consequences:

http://zone.ni.com/reference/en-XX/help/371361H-01/lvexcodeconcepts/locations_for_shared_libraries/

 

0 Kudos
Message 4 of 4
(3,553 Views)