This project implements bindings for the ZeroMQ sockets library in LabVIEW. ZeroMQ provides simple yet powerful functionality for data transfer using sockets, including multiple paradigms like publish/subscribe. ZeroMQ automatically takes care of ensuring multi-part messages remain intact and seamlessly splits and recombines packets for optimal efficiency.

ZeroMQ has solutions to many of the most annoying things about sockets, so check it out and see if it can work for you!

Project Activity

See All Activity >

License

BSD License

Follow labview-zmq

labview-zmq Web Site

Other Useful Business Software
Try Google Cloud Risk-Free With $300 in Credit Icon
Try Google Cloud Risk-Free With $300 in Credit

No hidden charges. No surprise bills. Cancel anytime.

Use your credit across every product. Compute, storage, AI, analytics. When it runs out, 20+ products stay free. You only pay when you choose to.
Start Free
Rate This Project
Login To Rate This Project

User Ratings

★★★★★
★★★★
★★★
★★
0
1
0
0
0
ease 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 3 / 5
features 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 4 / 5
design 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 3 / 5
support 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 0 / 5

User Reviews

  • Testing this out and got it working on 64-bit Linux Redhat 8.7 (soon to be 10). Would be nice if the Makefile was updated for 64-bit. Had to modify the VI zeromq.lvlib:zmq_libpath.vi This could easily be modified to have context for the 64-bit Linux OS detection (as I did to extend the code) in the diagram. The conditional disable was modified for TARGET_TYPE==UNIX && TARGET_BITNESS == 64. After that had to remove the Draft Functions (commented them out) to get rid of Error 13 rather than replace the underlying ZMQ library - I don't need these draft functions. After that, super simple to get examples working. We even made the LabVIEW Pub/Sub work with a C++ broker code implementation and demonstrated some high throughput. I would recommend that the developer review the LabVIEW Style Guide for Connector Pane set-up. The standard 4x2x2x4 should be used. It doesn't make the code unusable to have strange minimum required inputs and outputs, but wires do not flow nicely across the Block Diagram. Better compile instructions for handling the Draft Function issues would have been nice. Shame this package hasnt been updated in a long time. It's very useful.
Read more reviews >

Additional Project Details

Registered

2012-06-26