Antoine Chalons

ufff... before VIPM there was an open source "equivalent", it's the OpenG Commander

There is no shame in asking for help, it's only if you never ask questions that you'll remain ignorant all your life It's probably all about settings in the INI files next to your EXEs. Have a look at this discussion. First your 2 EXEs have to use different ports ; to set the port, use "server.tcp.port=3385" in the INI file next to your EXE Then the VIs in EXE A that need to be accessed from EXE B needs to be declared in the b.INI with something like "server.vi.access = "+vi_name.vi;+other_vi_name.vi;...etc..." Hope this helps

I sometimes use LabVIEW on a mac and can help for testing, ping me if you'd like me to run some tests for you.

Do you think a discount on your Developer Suite annual fee based on how many unresolved CAR you own is a good idea? Or maybe you'd prefer a bug bounty program? See here

I've been lucky to never have to deal with that kind of challenges :-o

As much as what you say is true, it's no reason to discourage people from trying

1) I don't really know the answer for sure, I saw that though :http://www.ehe-lab.com/OpenCV_Wrapper.html, I admit I have no idea how openCV compares to Cognex, Keyence, Matrox, Halcon, NI VDM, etc... 2) NI's OCR and pattern matching are far behind the competitors, so if there is a way to integrate something that give better results I am very interested 3) If I can be of any help I'll be glad, I have to say though that I've never coded in any other language than LabVIEW so integrating dll into LabVIEW is not my cup of tea. Cheers

I don't think that's the way to calculate this... the 48kHz is the max line rate, if you want 10fps with 2048 lines and 4096 columns, I'd calculate like this : 2048*4096*10/(1024*1024)=80MBytes According to this you're fine with GigE. One advice if you go with GigE and NI avoid the PCIe 8231 and 8235 and prefer the PCIe 8236 and 8233. We've have had a huge amount of problems with 8231 and 8235 and replacing them with 8236 or 8233 (even without using the PoE) was always a solution. NI technical support could never explain nor solve the issue and I'm still pretty bitter about this.

I avoid GigE like the plague, I know lots of people go this way (even my co-workers) but I simply don't trust it. I've never had had any issues with Camera Link so I stick to that. It does add extra cost for the frame grabber, but at least I'm confident I won't have disconnection issues. USB3 seams to be the next thing for cheap application but I wouldn't jump on it too early. CoaXPress seams to be the high speed successor for GigE but NI doesn't support it (yet??).

What problems are you afraid of with a MacOS version of LabVIEW? I use VMWare on my Mac to run a Windows version of LabVIEW and I'm happy with it.

I tend to agree with you but clearly that's not Olivier's point of view... Saphir's probes (see LVTN) are full of XControls [edit] of course if it's only for one project... it may not be worth at all

maybe an XControl could help you with this, no?

you are a Mac user and you'd like LabVIEW to look beautiful on retina displays? vote here

we've asked this from NI multiple times but they say it would be too much work to fully support reading and displaying dxf files, we came up with an compromise that was acceptable for our customers, they have to export their dxf without arcs and then we can parse the dxf files to generate overlays that we display on in IMAQ image. would that work for you knowing it requires the Vision Development Module licence?

looks great! does it work with FP decorations?

maybe take a look at this discussion on JKI forum. hope this helps