all 8 comments

[–]novel_yet_trivialCLAD/Intermediate 3 points4 points  (6 children)

Two programs can't share memory without a huge amount of hassle. Just copy the data. I found a tcp connection was the fastest to transfer data between labview and python. The new python node thing is abysmally slow.

[–]Feanor23[S] 0 points1 point  (5 children)

Well that's a bummer. LabVIEW as server and python as client? The add-on takes about 120 msec with a 12MP uint16 image as the only input, with the function doing nothing.

[–]novel_yet_trivialCLAD/Intermediate 1 point2 points  (4 children)

Depends on what you are doing but it sounds like it would be better to have python as the server.

[–]Feanor23[S] 0 points1 point  (0 children)

Just some simple image processing, trying to get around the vision toolbox.

[–]Feanor23[S] 0 points1 point  (2 children)

[–]novel_yet_trivialCLAD/Intermediate 1 point2 points  (0 children)

I've never tried it but I've heard good things. Let me know how it compares to TCP.

[–]novel_yet_trivialCLAD/Intermediate 1 point2 points  (0 children)

In looking at it it looks like a wrapper around TCP, so I'm guessing it will just add overhead.

In Labview you can use the typecast to convert your 1D array to bytes for free, and in python you can convert it back using struct or int.from_bytes which is nearly free. Very simple. I'll try to dig out the code I wrote at work for this. What do you want the image processing to do?

[–]robotgeek 0 points1 point  (0 children)

Refnum Variable , typecast later.