12-01-2014 01:57 PM
Hello,
I am wondering that if we can read packets sent over webSockets (as described in: .Net WebScoekts)? The way we would like to use it currently is that the c++ software reads sensor data, packs them and sends them over websockets (on the local machine) and a client software will pick them up and display them on a GUI which we prefer to be LabView.
I know LabView supports data communication over Tcp/Ip but I am wondering that if this is posible or not with WebSockets as well.
Thanks and have a great day,
Hatef
Solved! Go to Solution.
12-01-2014 02:42 PM
WebSockets is a .NET 4.5 feature. LabVIEW 2014 ships with .NET 4.0
With 2012SP1 I imagine you may have difficulties but, it might be possible.
12-01-2014 02:56 PM
So LabView does not have a built-in vi's and features that read data from WebSockets? (Kind of similar to what it has for Tcp/Ip)
12-01-2014 03:32 PM
You will have to implement the WebSocket negotiation yourself per the relevant RFC.
There are few projects around that use WebSocket for various functions (SVG based remote panels etc) which are not limited to LV2014.
12-03-2014 03:42 PM
Thanks Gribo,
yes, I will implement the negotiations myself, but can you please point me towards the projects that you mentioned?
Thanks.
12-03-2014 06:03 PM
Actually, I recently posted a native LabVIEW WebSockets implementation to the NI Community.
You can check it out here: https://decibel.ni.com/content/docs/DOC-40572
Unfortunately I can only build the package in LV2013 but when I get to work tomorrow I can save the VIs for previous version and zip them up for you.
12-04-2014 02:13 AM
Here is one (Shameless self promotion ) http://lavag.org/topic/17873-cr-labview-google-maps-websocket-interface/
12-04-2014 03:30 AM
As promised, here is my library saved for LV2012.
11-13-2015 12:23 AM - edited 11-13-2015 12:30 AM
Thank you Sam_Sharp, but there are some VIs missing. Could upload them in LV2012?
11-13-2015 04:00 AM
I have since packaged my library into a VI Package - please try the attached package (built in LV2012). You'll need the latest version of VI Package Manager.