Hi Francisco,
Yeah that will work ok - you can use the "NAN" comparison node to verify if a DVR is valid if you want to ask permission instead of forgiveness :)
I updated zmq_proxy.vi to do this - you can grab it straight from the repo. If that works I'll do a package rebuild later.
Cheers,
Martijn
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've also been using the proxy without the capture socket and I modified my installed library similarly to op (I used zmq_socket_check.vi). My project will now expand with external collaborators, so I'd very much appreciate a new .vip build and release with the fix included.
I think the zmq_proxy_steerable.vi has the same issue and is also missing the steerable socket on the connector pane. Aside from this, generally I'd recommend always using the 4-2-2-4 pattern though, as it makes the client code much nicer to read.
Thanks for all the work on the project!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I'm running zmq_proxy.vi with no input in the 'capture terminal'.
The intention is to pass a NULL socket, but I could not find a way to do that.
This produces an internal error in the 'In place element structure' , which causes the 'lvzmq_proxy' node to not execute.
If I just ignore the error (in a nasty way, as attached), everything is fine and the lvzmq_proxy node runs well.
Is there a tidy way of doing this without this quick fix?
I'm sure I'm missing the proper way of passing a NULL socket.
Thanks,
Francisco
ps: thank you Martijn for your amazing work!
Hi Francisco,
Yeah that will work ok - you can use the "NAN" comparison node to verify if a DVR is valid if you want to ask permission instead of forgiveness :)
I updated zmq_proxy.vi to do this - you can grab it straight from the repo. If that works I'll do a package rebuild later.
Cheers,
Martijn
Hi Martijn,
It works smoothly, you can integrate it.
Thanks for the swift response!
Best,
Francisco
Hi Martijn,
I've also been using the proxy without the capture socket and I modified my installed library similarly to op (I used zmq_socket_check.vi). My project will now expand with external collaborators, so I'd very much appreciate a new .vip build and release with the fix included.
I think the zmq_proxy_steerable.vi has the same issue and is also missing the steerable socket on the connector pane. Aside from this, generally I'd recommend always using the 4-2-2-4 pattern though, as it makes the client code much nicer to read.
Thanks for all the work on the project!
I finally got around to booting up my old LabVIEW computer to build the package. I uploaded v3.6.2 with the proxy change.
Cheers,
Martijn
Thanks, it seems to work!
Best regards,
Tomaž